Your prototype worked. Then the project got bigger than the context window — and now every session starts with you re-explaining what you already built. 4SYNC ARCH keeps a project's memory, decisions and current state in plain files your agent reads at the start of every session. In your repo, in git, readable by you.
your-project/ ├─ your-project.yaml # manifest: boot · close ├─ 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 ├─ MERGE_PLAN.md # task ledger + journal └─ ABBA.md # agent bulletin board
4SYNC — A Return on Context Harness (ARCH)
A small stack of plain files plus a manifest that tells any agent how to start a session and how to end one. There is no runtime, no service and no account. Your agent reads the files; the files are yours.
Return on Context (RoC) is a build philosophy that seeks to gain maximum value for each token spent. RoC is the antithesis of “tokenmaxxing.” Stock markets don't reward companies for spending the most money, they reward those that make the most money.
The config file that saved every session's context bloated 50× into the thing that consumed it. Breaking it to bits — small files, hard write rules — is where ARCH began. The whole record, dated, straight from git.
Read the origin story → CASE STUDY · AUGUST 2026Nine named agents, none with memory between shifts, one written canon of about 600,000 tokens — larger than any context window. The files are the state; the machinery keeps them true. Months in production, receipts in the ledgers.
Read the case study → WHITE PAPER · JULY 2026The metric the whole system serves: maximum value for every token spent — the inverse of tokenmaxxing, measured rather than asserted. Dates the coinage to March 2026. By Michael S. Massey.
Read the white paper →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 a session fetches depth on demand instead of loading the world up front.
config/CANON_INDEX.yaml · append a rowEvery session loads the same small stack in the same order — kernel, status, map, ledger. Identity first, so the operating rules land before the backlog does.
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 project with a seed document and the first session authors its own identity from it. This site's own instance was born exactly that way.
═══ ARCH — BOOT RECEIPT ═══ instance your-project/ manifest your-project.yaml This instance declares 5 file(s) to load, in this order: 1 your-project.yaml 6,240 B ~1,560 tok 2 config/KERNEL.yaml 11,080 B ~2,770 tok 3 config/STATUS.yaml 9,315 B ~2,328 tok 4 config/CANON_INDEX.yaml 4,720 B ~1,180 tok 5 MERGE_PLAN.md 18,410 B ~4,602 tok ═══════════════════════════════════════════════ boot stack 49,765 B ~12,440 tok 2 session(s) holding undeposited state: · a71c3f04 last wrote 07-14 09:22 · 3e90bb17 last wrote 07-15 16:41 ← LIVE NOW
Nothing here is a service you call or a process you run — it is all files, and a routine for keeping them true.
The whole stack: the manifest, the five-file loader, the task ledger, the bulletin board, the hooks and the close-time tooling. Copy it into a project, run one session, and it configures itself from your seed document.
git clone https://github.com/SandmanCircles/4SYNC-ARCH.git
The struggle is real. Complexity drives cost, as do mistakes. Mitigate that risk with ARCH Support.
Your instance is the deliverable — yours from the first commit.
$200/HR · PROJECTS QUOTED FIXED-FEE Contact ARCH Support →Make a new, empty folder — not an existing repo, and not Downloads or Desktop. Genesis writes that folder's absolute path in permanently. Open a Claude session there and paste this:
Clone https://github.com/SandmanCircles/4SYNC-ARCH into this folder, then read CLAUDE.md and 4SYNC.yaml and run the genesis they declare. I haven't filled in SEED.md — interview me through it.
Your session reads the protocol, walks you through the seed conversationally, then plays back what it understood — project name, purpose, and that permanent root path — and waits for your explicit go before writing anything. That playback is the only thing you have to read.