System Architecture
[Intention: Truth over growth] Canonical behavior is modeled first, adapters second.
Pipeline map
flowchart LR
A[Authority Sources] --> B[Orchestrator]
B --> C[Miner + Sorter]
C --> D[Verifier Gates]
D -->|pass| E[Publisher]
D -->|fail| F[Incident Health + Notify]
E --> G[iOS Rules Sync]
E --> H[Audit Evidence]
F --> H
Responsibility boundaries
| Agent | Responsibility | Output |
|---|---|---|
| Orchestrator | Schedule and state transitions | lifecycle events |
| Miner/Sorter | Harvest and normalize source material | candidate records |
| Verifier | Enforce gates and conflict policy | deterministic verdicts |
| Publisher | Versioned manifest + pack publication | signed metadata |
| iOS app | Consume only admitted packs | local sync trace |
Guardrails
- Idempotent retries for recoverable operations.
- No hidden mutation in business logic modules.
- Every publish path has rollback semantics.