Teams running AI agents lose the plot between sessions. 4SYNC is the structure that keeps them synchronized — a durable, inspectable memory of who it is, what's true now, and where everything lives.
your-project/ ├─ manifest.yaml # boot · close · genesis ├─ MERGE_PLAN.md # task ledger + journal ├─ ABBA.md # agent bulletin board └─ config/ ├─ KERNEL.yaml # identity — always on ├─ STATUS.yaml # live state — overwrite ├─ CANON_INDEX.yaml # the map ├─ REFERENCE.yaml # deep canon — on demand └─ HISTORY.md # frozen archive
Context rot happens when one giant file tries to be identity, state, and history at once. 4SYNC splits them — small, hand-maintained, load-bearing.
The kernel carries the operating contract: directives, invariants, and naming — front-loaded so even a truncated read lands the rules that must never be missed.
config/KERNEL.yaml · edit rarelyA live snapshot, overwritten in place. Deploy versions, active focus, blockers — answerable at a glance, never a log.
config/STATUS.yaml · overwriteA pointer index to every deeper document, so any session fetches depth on demand instead of loading the world up front.
config/CANON_INDEX.yaml · append a rowA single manifest bookends every session — no installation, no plugins, no dependencies. The folder itself tells any agent how to wake up, how to close out, and how to be born.
Every session loads the same small stack in the same order — ledger, kernel, status, map — and starts already knowing the plot.
On an explicit ending signal, the session journals what happened, syncs the ledger, and overwrites the snapshot — so the next session inherits an accurate now.
Drop the stack into a fresh project with a seed document, and the first session authors its own identity from it. This site's silo was born exactly that way.
The pattern, templates, and tooling — the five-file stack, the task ledger, the agent bulletin board, and the manifest that bookends every session.
PACKAGING & PRICING AT LAUNCHImplementation and advisory: adopt the pattern, migrate a monolithic context into the stack, and stand up your own multi-agent operation.
ENGAGEMENTS OPEN AT LAUNCHDone-for-you: we run, host, and maintain the system on your behalf — your agents stay synchronized, we keep the structure true.
SCOPE & SLA AT LAUNCH