Expand description
The .flint/ control namespace (boundary-verbs plan §2.0, D0/D11):
the agent’s side of the file protocol.
The app container ships UNCHANGED — no HTTP client, no CLI binary, no library can be assumed in its image. The only interface every agent is guaranteed to have is the shared workspace mount, so the boundary verbs are files. This module owns everything the syncer writes there:
capabilities.json— the marker an agent MUST check before touching a sentinel. Absence ⇒ an old syncer ⇒ sentinels are live ammunition (they would be scanned and published, §2.0).remote.seq— the news ticker (D5), fed from information the barrier already has: zero added bucket requests.- the pre-existing-
.flint/pre-flight (D0.4), which disables sentinel consumption for a workspace that was already using the namespace as data.
Trust statement (plan §1.2): every file here is writable by
every process sharing the mount. Acks are advisory coordination
signals, NOT attestations — an in-pod process can forge one. The
authoritative durability signal is a remote read the pod cannot
forge (gateway GET /status, or the manifest itself).
Structs§
- Boot
Stamp - Capabilities
.flint/capabilities.json(D11). Written atomically at EVERYrunstartup — after claim succeeds, before the first poll — and again during first checkout, so it exists the instant the agent may start.- Remote
Seq .flint/remote.seq— the news ticker (D5).- Sentinel
Posture - The sticky pre-flight verdict (D0.4).
Constants§
- AGENT_
GUIDE .flint/AGENTS.md— the workspace contract, written beside the marker so an agent reads the protocol of the syncer it is talking to (an old syncer writes neither; a fenced one still says so in the marker). The text is the crate’sAGENTS.md; the testagent_guide_names_every_advertised_verbkeeps the two from drifting.- AGENT_
GUIDE_ TEXT - CAPABILITIES
- PUBLISH
- PUBLISH_
ACK - REMOTE_
SEQ - SYNC
- SYNC_
ACK