ORCH-001: Sync lab clocks → green verify → ready to BREAK (operator bus)

[Natoshi-moto]

ORCH-001 — Make the Lab fresh, synced, then breakable

Status authority: NONE until operator merges
Operator: non-coder, Ring-0 approvals only (copy/paste bus)
Drive seat: Grok (this issue + chat)
Implement seat: Codex
Review/debug seat: Claude Code

Goal (one sentence)

Restore green checks, re-sync STATUS/NEXT_ACTION with reality, park stale PRs, then enter intentional break mode against Noted (T-IDs / adversary block) — not more feature chrome.

Operator defaults (unless operator overrides)

ID	Default
D1 stop-line	ADOPT
D2 next eng	GO-T06-FIRST then measurement harnesses
D3 tension map	DEFER (measure first, no silent “fix” PRs)
D4 Snooper	SPEC-ONLY for now
D5	Docs already on main (PR #59)

Living spine (only this)

A. Green machine  →  B. Control-plane re-sync  →  C. Park PR museum
        →  D. T06 quarantine  →  E. Break-prep (ODS-SEC + adversary block review)

Seat turns (in order)

Turn	Seat	Job	Outcome
T0	Operator	Reply on this issue: DEFAULTS OK or override D1–D5	Unblocks seats
T1	Codex	Restore green verify (npm ci, doctor, verify, tests); open PR if lockfile/docs needed	Green receipt
T2	Claude	Control-plane re-sync proposal (STATUS + NEXT_ACTION + render-status); no fake R017 promotion	Docs PR
T3	Operator	Merge T1 then T2 after Grok/Claude skim	main synced
T4	Codex	T06 quarantine of stale Agent v0.12 paths (bounded); receipts	PR
T5	Claude	Break-prep review: T-01…T-06 map + PR #61 adversary block; attack runbook for operator	Review comment + optional docs PR
T6	Operator + Grok	Start BREAK mode: run / authorize probes (synthetic only)	First FAIL receipts

Hard rules for every seat

1. status_authority: NONE — proposal ≠ accepted.
2. No real money, keys, tokens, third-party attacks.
3. Multi-AI agreement ≠ independent proof.
4. Do not promote round to R017 because GITBRAID or PR R017: replica-independent history attestations and fork evidence #22 exists.
5. Do not start Phase 3 feature surface during this campaign.
6. Silence is not a pass — write UNABLE_TO_VERIFY when needed.
7. Write scope only as named in the turn packet.

Lane map (PRs)

Lane 1 — LIVE (this campaign)

• docs: NOTED-ADVERSARY-BLOCK-001 (proof-of-unsafety block proposal) #61 Adversary block (after break-prep review)
• docs: NOTED-MEMBRANE-HARDENING-001 (mutual distrust plan) #60 Membrane hardening (draft; sequencing only)
• New PRs from T1/T2/T4

Lane 2 — PARALLEL (do not block spine)

• R017: GITBRAID — GitHub-native continuity & skill-RAG (bold draft) #62 GITBRAID (process research; rename later if needed)

Lane 3 — PARK / MUSEUM

• R017: replica-independent history attestations and fork evidence #22 old R017 history attestation
• R018: fixed hybrid post-quantum admission evidence #23 R018 PQ admission
• R014: demonstrate crash-recoverable synthetic settlement #14 R014 durable settlement
• BGEN-EPISTEMIC-AUDIT-001: independent epistemic audit of the Beneficial Genesis record #40–BGEN-CODEX-DEV-CULTURE-CHALLENGE-001: rigorous epistemic challenge of PR #47 #49 BGEN audit/memo drafts
• Declare OPEN-GATE v0 public protocol bet #24 OPEN-GATE protocol
• Bump actions/checkout from 5.0.0 to 7.0.0 #1 dependabot (optional)

Success = ready to BREAK

• ./nexus doctor PASS
• ./nexus verify PASS
• unit tests green after install
• NEXT_ACTION.md names stop-line / break-prep (not stale PR R017: replica-independent history attestations and fork evidence #22 as sole story)
• STATUS.json next_action matches reality (round may stay R016)
• Lane 3 PRs commented PARKED
• Operator has a 1-page break runbook (Claude T5)
• No seat claims the product is safe

Non-goals

• Token/value stories
• Cold-drop marketing package
• Closing T-IDs with prose alone
• Implementing full Snooper UI yet

---

Paste packets for seats live in the first comments and in the operator chat with Grok.

[Natoshi-moto]

PASTE PACKET — T1 CODEX (restore green machine)

Copy everything below the line into Codex CLI / Codex VS Code on a clean checkout of main.

---

You are SEAT-CODEX-IMPLEMENT on Natoshi-moto/Lab.

TASK_ID: ORCH-001-T1-GREEN-VERIFY
TRACKING: https://github.com/Natoshi-moto/Lab/issues/63
BASELINE: origin/main (pull first)
STATUS_AUTHORITY: NONE

CONTEXT:
- Lab doctor currently PASSes.
- ./nexus verify and R013–R016 tests FAIL when node_modules missing because root package.json needs @noble/ed25519.
- Operator is non-coder; you implement only this restore job.

SCOPE (write only):
- package-lock.json if npm ci legitimately updates it
- operations/receipts/ORCH_001_T1_GREEN_VERIFY/ (RECEIPT.md + any logs excerpts)
- Optionally products/noted-host only if you document npm ci there for typecheck — do NOT change app source

FORBIDDEN:
- STATUS.json / NEXT_ACTION.md edits (Claude T2)
- Product features, Agent changes, T06 quarantine (later turn)
- Secrets, tokens, real provider keys
- Claiming security certification

DO EXACTLY:
1. git fetch origin && git checkout main && git pull
2. git checkout -b codex/orch-001-t1-green-verify
3. npm ci
4. ./nexus doctor
5. ./nexus verify
6. python3 -m unittest discover -s tests -v
7. If verify/tests fail for reasons OTHER than missing deps, diagnose; minimal fix only if clearly environment/script path; otherwise stop and report UNABLE_TO_VERIFY with logs
8. Optional: cd products/noted-host && npm ci && npm run typecheck (record pass/fail; do not expand scope if typecheck needs app fixes — report only)
9. Write operations/receipts/ORCH_001_T1_GREEN_VERIFY/RECEIPT.md with:
   - commit SHAs
   - exact commands
   - pass/fail for doctor, verify, tests (counts)
   - NON-CLAIMS: green checks ≠ security audit
10. Open PR to main titled: "ORCH-001 T1: restore green doctor/verify/tests (env + receipt)"
    Body must link issue #63 and paste command outcomes.
11. End turn with DONE / EVIDENCE / RECEIPT / NEXT (hand to operator for merge, then Claude T2)

VERIFY must pass before PR is "ready".

[Natoshi-moto]

PASTE PACKET — T2 CLAUDE CODE (control-plane re-sync, docs only)

Copy everything below the line into Claude Code after T1 is green on main (or stacked on main + T1 merge).

---

You are SEAT-CLAUDE-DEBUG / design-docs seat on Natoshi-moto/Lab.

TASK_ID: ORCH-001-T2-CONTROL-PLANE-RESYNC
TRACKING: https://github.com/Natoshi-moto/Lab/issues/63
BASELINE: origin/main after ORCH-001 T1 merged (or main if T1 needed no code)
STATUS_AUTHORITY: NONE — you propose; operator merges

GOAL:
End STATUS/NEXT_ACTION drift. Official next action must match the living spine:
stop-the-line ADOPTED (operator default) → T06 first → then BREAK/measurement — NOT "only review old PR #22" as the whole story.

OPERATOR DEFAULTS (unless issue #63 says otherwise):
- D1 ADOPT stop-the-line
- D2 GO-T06-FIRST
- D3 DEFER tension-map fixes (measure first)
- D4 Snooper SPEC-ONLY
- Round number stays R016 (do NOT claim R017 accepted)
- Two R017 packets exist: PR #22 (old) vs PR #62 GITBRAID — disambiguate in NEXT_ACTION; do not promote either

SCOPE (write only):
- STATUS.json
- NEXT_ACTION.md (via whatever process; STATUS.md is generated — run render if available)
- STATUS.md only if generated by tool
- operations/receipts/ORCH_001_T2_CONTROL_PLANE/RECEIPT.md
- Optionally experiments/NOTED_PROJECT_OS_001/GROK_PICKUP.md "where we are NOW" section only
- Optionally PROJECT_INDEX.json if control_plane requires round consistency with STATUS

FORBIDDEN:
- Implementing T06 or product code
- Promoting current_round to R017/R018
- Editing frozen snapshots, corpus/raw as instructions
- Closing PRs yourself without operator (you may draft park comment text)
- Softening WHY_NOT_TO_TRUST or HARD_GATES

DO:
1. Pull latest main; branch claude/orch-001-t2-control-plane
2. Read STATUS.json, NEXT_ACTION.md, operations/proposals/NOTED_STOP_THE_LINE_001/, WHY_NOT_TO_TRUST_THIS_PROJECT.md, issue #63
3. Update STATUS.json fields at minimum:
   - next_action_id → something like ACT-ORCH-001-T06-THEN-BREAK-PREP
   - current_mode → e.g. NOTED_STOP_LINE_ADOPTED_BREAK_PREP (string ok)
   - last_completed_action → note R016 still last promoted round; Noted Phase2 + stop-line docs on main
   - active_tasks → [] or single upcoming task id string if you invent TSK-ORCH-001-T06
   - keep current_round R016 and foundation_status OPERATIONAL unless evidence demands otherwise
4. Rewrite NEXT_ACTION.md to ONE operator action: authorize/implement T06 quarantine then enter break-prep; list parked tracks (PR #22/#23, BGEN drafts, GITBRAID parallel)
5. ./nexus render-status if available; ./nexus doctor must PASS
6. RECEIPT.md with before/after next_action_id and non-claims
7. Open PR linking #63
8. Include in PR body ready-to-paste GitHub comments to PARK PRs #22 #23 #14 #24 #40-49 as Lane 3 (operator or Grok will post)

END with DONE/EVIDENCE/RECEIPT/NEXT → operator merge → Codex T4

[Natoshi-moto]

PASTE PACKET — T4 CODEX (T06 quarantine — first real break-prep fix)

Run only after T1+T2 merged to main and operator says GO on issue #63.

---

You are SEAT-CODEX-IMPLEMENT on Natoshi-moto/Lab.

TASK_ID: ORCH-001-T4-T06-QUARANTINE
TRACKING: https://github.com/Natoshi-moto/Lab/issues/63
THREAT: T-06 from operations/proposals/NOTED_SOVEREIGNTY_ASSAULT_001/THREAT_MODEL.md
STATUS_AUTHORITY: NONE

GOAL (layman):
Make sure the old unscrubbed Agent (v0.12) is not sitting around as a normal launch path. Quarantine/remove from launch surfaces; do not claim all privacy risks are gone.

SCOPE:
- products/noted-host/public/nexus/** related to nexus-agent-v0.12, block-registry legacyPath, Nexus_OS.html launch entries
- products/nexus-blocks/** only if required for the same quarantine
- tests or smoke scripts if needed to prove v0.12 not registered as launchable
- operations/receipts/ORCH_001_T4_T06_QUARANTINE/

FORBIDDEN:
- Rewriting whole Agent
- "Fixing" T-01/T-02/T-03 fully in this PR
- CDN vendoring mega-refactor
- STATUS promotion
- Real keys/data

DO:
1. Branch codex/orch-001-t4-t06-quarantine from latest main
2. Inventory every path that references nexus-agent-v0.12
3. Quarantine strategy (pick minimal honest one):
   - Remove or relocate v0.12 files out of launch paths, OR
   - Keep files but strip/replace embedded-data and remove registry/OS launch entries
   Document choice in receipt
4. Ensure live path remains v0.14-scrubbed only
5. Add/adjust a small automated check if cheap (registry must not list v0.12 as active app)
6. npm/test/doctor as applicable for touched package
7. RECEIPT with probe: "can a cold reader still open v0.12 as a first-class app?" before/after
8. PR → main linking #63 and T-06

NEXT: Claude T5 break-prep review

[Natoshi-moto]

PASTE PACKET — T5 CLAUDE CODE (break-prep runbook for operator)

After T4 merged (or in parallel as docs-only if T4 delayed).

---

You are Claude design/debug seat on Natoshi-moto/Lab.

TASK_ID: ORCH-001-T5-BREAK-PREP-RUNBOOK
TRACKING: https://github.com/Natoshi-moto/Lab/issues/63

GOAL:
Produce a layman-operable BREAK runbook so a non-coder operator can direct synthetic attacks and understand FAIL vs PASS. No real third-party attacks. Synthetic fixtures only.

READ:
- WHY_NOT_TO_TRUST_THIS_PROJECT.md
- operations/proposals/NOTED_SOVEREIGNTY_ASSAULT_001/ (esp THREAT_MODEL, ODS_SECURITY_CASES)
- operations/proposals/NOTED_STOP_THE_LINE_001/HARD_GATES.md
- PR #61 adversary block proposal (branch/files)
- products/noted-host scripts (ods-p0, bridge-smoke, agent-prompt-smoke)

WRITE (docs only unless tiny fix needed for runbook accuracy):
- operations/break-prep/ORCH_001_BREAK_RUNBOOK.md
  Sections: What breaking means / What never to do / Prep checklist / Attack cards for T-01 T-02 T-03 T-06 (and T-04 if easy) each with: goal, steps a human can follow or paste to Codex, expected FAIL today, what evidence to save, what would count as later fixed
- operations/receipts/ORCH_001_T5_BREAK_PREP/RECEIPT.md

FORBIDDEN:
- Claiming any T-ID closed
- Softening gates
- Running attacks against third-party systems
- Shipping the adversary block implementation unless operator separately GOs PR #61 build

PR title: "ORCH-001 T5: break-prep runbook (synthetic only)"
Link #63. NEXT: Operator + Grok enter BREAK mode using the runbook.