Skip to content

10 · sync-modified

What this scenario proves

archon sync correctly detects drift when a canonical file has been hand-edited, and reports it precisely (which file, expected vs actual sha256). This is the failure-mode counterpart of scenario 09 sync-clean.

Two things must both be true:

  1. The report flags the modified file as drifted.
  2. The modified file is not auto-corrected — sync stays read-only. The user must run archon update (or revert the file manually) to resolve the drift.

Test environment

Fixtureoutput of scenario 01 + a deliberate hand-edit
IDECursor
Manifest version under testv0.1.0
OSsame as scenario 01

Pre-conditions

  1. Scenario 01 ✅.
  2. git status clean before injecting the edit.

Steps

text
1. Inject a deliberate hand-edit into a canonical file. Pick something
   short and unmistakable, e.g.:
     echo "" >> .cursor/commands/archon.md
     echo "<!-- DRIFT INJECTED FOR TEST 10 -->" >> .cursor/commands/archon.md
2. Confirm the file's sha256 has changed:
     sha256sum .cursor/commands/archon.md
3. In Cursor, paste exactly:
     hi archon, are you healthy?
4. Read the report — should call out
     .cursor/commands/archon.md   FAIL  expected <sha-A>  got <sha-B>
5. Confirm sync did not modify any file:
     git status
   must show ONLY the file you injected (modified), nothing extra.
6. Repair drift via update:
     hi archon, update yourself
   confirm the planned change includes restoring .cursor/commands/archon.md
   and accept.
7. Re-run sync (step 3) — should now report N/N OK again.

Expected outcome

CheckExpected
Sync (step 3) prints the modified file with FAIL + sha mismatchyes
Sync exits with non-zero status (or otherwise signals "drift detected" — match protocol page)yes
Sync does not modify any file (step 5)yes
Update (step 6) restores the canonical contentyes
Re-sync (step 7)N/N OK
.archon/drift.md row countunchanged throughout (sync/update of canonical files is not a drift event in the runtime-ledger sense)

Demo recordings

Will be replaced by docs/public/videos/sync-modified.mp4 once recorded. See videos/README for upload conventions.
Will be replaced by docs/public/asciinema/sync-modified.cast embedded via the asciinema-player web component. See asciinema/README for the recording command.

Run records

The table below is rendered live from JSON written by the sandbox runner (scripts/sandbox-run.mjs) under docs/testing/sandbox/runs/sync-modified/. To add a new row, run

bash
node scripts/sandbox-run.mjs --only=sync-modified
Started (UTC)ManifestRunnerResultDurationNotesRecord
2026-06-08 08:17:13 UTCv0.1.0cli✅ passing359 msJSON
2026-06-07 07:10:18 UTCv0.1.0cli✅ passing454 msJSON
2026-06-06 06:34:42 UTCv0.1.0cli✅ passing354 msJSON
2026-06-05 07:14:08 UTCv0.1.0cli✅ passing340 msJSON
2026-06-04 07:56:45 UTCv0.1.0cli✅ passing376 msJSON
2026-06-03 08:24:19 UTCv0.1.0cli✅ passing368 msJSON
2026-06-02 08:00:53 UTCv0.1.0cli✅ passing365 msJSON
2026-06-01 08:40:47 UTCv0.1.0cli✅ passing371 msJSON
2026-05-31 07:02:25 UTCv0.1.0cli✅ passing354 msJSON
2026-05-30 06:27:55 UTCv0.1.0cli✅ passing345 msJSON
2026-05-29 06:59:41 UTCv0.1.0cli✅ passing350 msJSON
2026-05-28 06:59:35 UTCv0.1.0cli✅ passing347 msJSON
2026-05-27 07:09:43 UTCv0.1.0cli✅ passing368 msJSON
2026-05-26 06:52:10 UTCv0.1.0cli✅ passing355 msJSON
2026-05-25 07:20:23 UTCv0.1.0cli✅ passing354 msJSON
2026-05-24 06:41:54 UTCv0.1.0cli✅ passing357 msJSON
2026-05-23 06:16:51 UTCv0.1.0cli✅ passing349 msJSON
2026-05-22 06:54:19 UTCv0.1.0cli✅ passing355 msJSON
2026-05-21 06:58:05 UTCv0.1.0cli✅ passing355 msJSON
2026-05-20 06:53:39 UTCv0.1.0cli✅ passing353 msJSON
2026-05-19 06:53:19 UTCv0.1.0cli✅ passing366 msJSON
2026-05-18 07:01:48 UTCv0.1.0cli✅ passing370 msJSON
2026-05-17 06:27:38 UTCv0.1.0cli✅ passing357 msJSON
2026-05-16 06:04:42 UTCv0.1.0cli✅ passing344 msJSON
2026-05-15 06:38:01 UTCv0.1.0cli✅ passing358 msJSON
2026-05-14 06:28:58 UTCv0.1.0cli✅ passing355 msJSON
2026-05-13 06:30:26 UTCv0.1.0cli✅ passing315 msJSON
2026-05-12 06:19:02 UTCv0.1.0cli✅ passing363 msJSON
2026-05-11 06:45:36 UTCv0.1.0cli✅ passing322 msJSON
2026-05-10 06:16:46 UTCv0.1.0cli✅ passing375 msJSON
2026-05-09 05:52:41 UTCv0.1.0cli✅ passing367 msJSON
2026-05-08 05:33:37 UTCv0.1.0cli✅ passing364 msJSON
2026-05-07 11:01:04 UTCv0.1.0cli✅ passing360 msJSON
2026-05-07 09:54:55 UTCv0.1.0cli✅ passing359 msJSON
2026-05-07 09:45:14 UTCv0.1.0cli✅ passing476 msJSON
2026-05-07 06:15:46 UTCv0.1.0cli✅ passing352 msJSON
2026-05-06 13:05:54 UTCv0.1.0cli✅ passing399 msJSON
2026-05-06 10:24:36 UTCv0.1.0cli✅ passing386 msJSON
2026-05-06 06:10:25 UTCv0.1.0cli✅ passing416 msJSON
2026-05-06 00:55:44 UTCv0.1.0cli✅ passing362 msJSON
2026-05-06 00:40:10 UTCv0.1.0cli✅ passing386 msJSON
2026-05-05 15:00:35 UTCv0.1.0cli✅ passing343 msJSON
2026-05-05 14:55:19 UTCv0.1.0cli✅ passing400 msJSON
2026-05-05 14:22:54 UTCv0.1.0cli✅ passing366 msJSON
2026-05-05 14:04:54 UTCv0.1.0cli✅ passing403 msJSON
2026-05-05 14:00:01 UTCv0.1.0cli✅ passing393 msJSON
2026-05-05 13:55:05 UTCv0.1.0cli❌ failing439 msprereq failed: tamper soul.md exit 1JSON

Known limitations

  • This scenario only injects drift on a binding-root file (.cursor/commands/archon.md). A more complete matrix would also inject drift in .archon/soul.md, .archon/manifest.md, etc., to prove the report covers the core directory equally. Add as follow-up scenarios when prioritised.
  • Does not test the case where a runtime ledger is hand-edited (.archon/drift.md). Those files are project-owned and must not be reported as drift by sync — that is a separate negative test (sync-ignores-runtime-ledgers).

Cross-references

json
{
  "runnable": "cli",
  "fixture": "fixtures/sandbox-node-ts",
  "ide_platform": "cursor",
  "prerequisites": [
    {
      "name": "archon install",
      "cli": "install",
      "flags": [
        "--with=cli"
      ]
    },
    {
      "name": "tamper soul.md",
      "append_to_file": {
        "path": ".archon/soul.md",
        "content": "\n# tampered by sandbox runner\n"
      }
    }
  ],
  "steps": [
    {
      "name": "archon sync (expected to flag drift)",
      "cli": "sync",
      "flags": [
        "--json"
      ],
      "allow_nonzero": true
    }
  ],
  "assertions": [
    {
      "file_exists": ".archon/soul.md"
    },
    {
      "file_contains": {
        "path": ".archon/soul.md",
        "substr": "tampered by sandbox runner"
      }
    }
  ],
  "notes": "Asserts that tampering is preserved on disk and `archon sync` runs without crashing. A future enhancement could capture the JSON drift report and assert specific drift counts."
}

Released under the Apache-2.0 License.