Skip to content

docs(README): repo-roam dev-env zero-diff user story + reproducible neo->honey proof#511

Merged
Jesssullivan merged 1 commit into
mainfrom
docs/repo-roam-user-story
Jun 9, 2026
Merged

docs(README): repo-roam dev-env zero-diff user story + reproducible neo->honey proof#511
Jesssullivan merged 1 commit into
mainfrom
docs/repo-roam-user-story

Conversation

@Jesssullivan

Copy link
Copy Markdown
Owner

Summary

Documents the repo-roam dev-env zero-diff capability in the README — the
"machine doesn't matter" user story and an exact, reproducible proof flow.

  • New Roam an in-progress repo across machines section: what you can do now
    (enroll a ~/git repo; branch + staged + unstaged + untracked + stash + full
    history follow you to every machine, encrypted), how it works (scheduled
    tcfs reconcile with git_sync_mode = "raw"), a copy-paste neo -> honey
    proof flow, and the scripts/repo-roam-fingerprint.sh pass/fail gate.
  • Honest boundary called out: concurrent two-way editing of the same repo is the
    unfinished G5 .git-aware conflict gate (one-writer-at-a-time handoff for now).
  • Adds a PII-free evidence packet docs/release/evidence/repo-roam-canary-20260609/
    for the 2026-06-09 forward-roam canary (dev-env-zero-diff=pass, fsck clean
    both sides, 126 files raw .git roamed).

PII-free: no email addresses, ~/-relative paths, machine names only (neo/honey,
already used elsewhere in the README).

…eo->honey proof

Adds 'Roam an in-progress repo across machines' — the machine-doesn't-matter user
story, how it works (scheduled raw .git reconcile), a copy-paste neo->honey proof
flow with the fingerprint pass/fail gate, and the bidirectional G5 boundary. PII-free
(no email, ~/-relative paths). Includes a scrubbed evidence packet for the
2026-06-09 forward-roam canary (dev-env-zero-diff=pass).
@Jesssullivan Jesssullivan merged commit 92fd119 into main Jun 9, 2026
12 checks passed
@Jesssullivan Jesssullivan deleted the docs/repo-roam-user-story branch June 9, 2026 07:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant