symfonic.platform.fallback_journal¶
fallback_journal ¶
Host-owned fallback evidence attributed to an explicit deployment.
This opt-in JSONL journal is separate from execution-event SQL: attribution is not a counter or invented turn identity. POSIX advisory locks coordinate hosts that intentionally share one local file. Remote filesystems are not attested.
DispatchOutcomeJournal ¶
Bases: FallbackJournal
Fsynced, deployment-labelled observations of actual dispatch only.
The host passes this callback explicitly to the agent. It has no route policy and makes no denominator or zero-fallback assertion.
Source code in src/symfonic/platform/fallback_journal.py
FallbackJournal ¶
A synchronous, fsynced metadata callback for a composition root.
Labels must be non-sensitive operator identifiers, not secrets or user input. The caller chooses the local path and provisions its directory. Each call opens/closes its own descriptor; there is no shutdown resource. Each event incurs synchronous fsync; operators own capacity and rotation. Journal failures propagate to the caller (the cutover board retains its existing telemetry-failure behavior). No admission/population claim is made.