Antidote architecture¶

Antidote separates research truth, human authority, local runtime behavior, replaceable model execution, and public projections.

flowchart TD
  person[Person and present moment] --> consent[Consent-scoped projection]
  consent --> core[Rust domain and application core]
  core --> plan[Inspectable journey plan]
  plan --> worker[Capability-scoped model worker]
  worker --> artifact[Audio artifact and feature report]
  artifact --> exposure[Deliberate exposure and stop]
  exposure --> response[Person-reported response]
  response --> core
  core --> export[Privacy-reviewed provenance export]

ADR-0002: Own native publication execution and gate Pages deployment¶

Status: accepted

Antidote owns independently runnable paper builds and publishes only a previously reviewed Pages artifact.

ADR-0004: Use a local-first desktop host with an isolated model worker¶

Status: accepted

The Rust core retains domain authority while the Python worker receives only the accepted bounded generation input.

ADR-0008: Adopt Holon's exact-pinned public site suite¶

Status: accepted

Holon owns reusable LaunchKit and Zensical profiles; Antidote owns content, identity inputs, paper composition, integrity, and publication.