Skip to content
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
202 commits
Select commit Hold shift + click to select a range
7e89a96
docs(orchestration): propose resource-efficient automatic continuation
jermur788 Nov 3, 2026
d0bcaac
docs(research): compare portable AI project orchestration approaches
jermur788 Nov 3, 2026
01072aa
docs(research): assess DeepSeek Superagent and Letta combination
jermur788 Nov 3, 2026
60b7fc5
docs(research): prepare neutral cloud review of orchestration engine …
jermur788 Nov 3, 2026
c4f9d1d
docs(orchestration): define authorized isolated continuation spike
jermur788 Nov 3, 2026
7221634
docs(research): extract continuation lessons from Argus OpenHands Dee…
jermur788 Nov 3, 2026
519ec03
docs(research): map T3 continuation seam and Argus manager integratio…
jermur788 Nov 3, 2026
72a9c3b
docs(orchestration): gate continuation spike on source reuse research
jermur788 Nov 3, 2026
f2df524
docs(research): reconcile upstream-first study and DeepSeek run progr…
jermur788 Nov 3, 2026
b1ee6eb
docs(orchestration): pause stub continuation spike for upstream-first…
jermur788 Nov 3, 2026
aa58795
docs(research): add complete browser-side architecture gate handoff
jermur788 Nov 3, 2026
9ba220a
docs(research): complete Argus vs T3 and live upstream overlap decisi…
jermur788 Nov 3, 2026
db9553b
docs(orchestration): complete research gate and narrow synthetic cont…
jermur788 Nov 3, 2026
00d261b
docs(research): triage upstream orchestration fixes and existing PRs
jermur788 Nov 3, 2026
abb82c1
docs(research): check upstream interrupted-review PR and behavioral v…
jermur788 Nov 3, 2026
9b0ebae
docs(architecture): define finite agent decision budget and escalatio…
jermur788 Nov 3, 2026
93c3370
docs(orchestration): require bounded review cycles and human escalati…
jermur788 Nov 3, 2026
633668e
docs(upstream): specify independent behavior tests for PR 28777 witho…
jermur788 Nov 3, 2026
4e9888f
docs(handoff): add self-contained browser chat task A
jermur788 Nov 3, 2026
1323a33
docs(handoff): add self-contained browser chat task B
jermur788 Nov 3, 2026
9f7a1c7
docs(manager): reconcile completed upstream PR review and next verifi…
jermur788 Nov 3, 2026
7232722
docs(manager): reconcile reported local PR28777 test pass and evidenc…
jermur788 Nov 3, 2026
d1138b8
docs(manager): capture reported PR verification and exact evidence-ex…
jermur788 Nov 3, 2026
9d48cc1
docs(manager): inspect local PR 28777 evidence and prepare upstream f…
jermur788 Nov 3, 2026
16f2341
docs(manager): close upstream review evidence access gap
jermur788 Nov 3, 2026
2a32761
docs(manager): record approved upstream PR28777 contribution comment
jermur788 Nov 3, 2026
d2a5c9d
docs(review): independently assess continuation security and define n…
jermur788 Nov 3, 2026
13daa5a
docs(review): independently recheck continuation security repair and …
jermur788 Nov 3, 2026
c328d3f
docs(review): independently approve bounded continuation hardening an…
jermur788 Nov 4, 2026
9f14e41
docs(coord): create DeepSeek overnight serial queue with supervision …
jermur788 Nov 4, 2026
59d5f88
docs(coord): seed append-only routing decisions and overnight worker …
jermur788 Nov 4, 2026
e2393b8
docs(manager): reconcile DeepSeek overnight results routing and pendi…
jermur788 Nov 4, 2026
5f79901
docs(spec): adopt staged continuation safety, default-off gate and st…
jermur788 Nov 4, 2026
e836b68
docs(task): queue default-off gate, independent review and safe upstr…
jermur788 Nov 4, 2026
70aa2c7
docs(manager): adopt user-approved gate and production revocation dir…
jermur788 Nov 4, 2026
85561db
docs(coord): seed route and verification ledger for approved staged c…
jermur788 Nov 4, 2026
d3d059c
docs(coord): link approved gate task to new routing ledger
jermur788 Nov 4, 2026
daf81d9
docs(manager): source review gate and authorize isolated upstream rec…
jermur788 Nov 4, 2026
9ecd2a5
docs(task): authorize separate isolated fork-upstream conflict resolu…
jermur788 Nov 4, 2026
05285e7
docs(state): reconcile reviewed gate and launch isolated upstream con…
jermur788 Nov 4, 2026
c94cdce
docs(manager): accept upstream v0.1.7 reconciliation trial with integ…
jermur788 Nov 4, 2026
42c32f6
docs(task): define UI/restart/evidence verification gate for reconcil…
jermur788 Nov 4, 2026
b646098
docs(state): accept reconciled upstream trial and preserve main-promo…
jermur788 Nov 4, 2026
eb92ad9
docs(state): record approved fork-only reconciliation draft PR and re…
jermur788 Nov 4, 2026
81e9391
docs(state): publish canonical current state for Overall Manager cont…
jermur788 Nov 4, 2026
011023d
docs(coord): mirror canonical handoff protocol for shared manager con…
jermur788 Nov 4, 2026
978b381
docs(manager): publish authoritative Overall Manager continuation han…
jermur788 Nov 4, 2026
01dbcbd
docs(manager): point historical coordination notes to current shared …
jermur788 Nov 4, 2026
57f370a
docs(manager): point historical coordination notes to current shared …
jermur788 Nov 4, 2026
e2fdad8
docs(manager): point historical coordination notes to current shared …
jermur788 Nov 4, 2026
754bdf6
docs(manager): point historical coordination notes to current shared …
jermur788 Nov 4, 2026
7b285fe
docs(manager): add concise under-500-word handoff for Jas
jermur788 Nov 4, 2026
de8f3e8
docs: scope evidence V0 pruning completeness pre-merge repair
jermur788 Nov 4, 2026
97e0369
docs: reconcile PR21 verification and require bounded pruning repair
jermur788 Nov 4, 2026
3a8651c
docs: hand off PR21 verification and required Evidence V0 repair
jermur788 Nov 4, 2026
bf728de
docs: pin isolated Evidence V0 P2 repair branch
jermur788 Nov 4, 2026
2f58108
docs: pin isolated Evidence V0 P2 repair branch
jermur788 Nov 4, 2026
28c8f33
docs: add paste-ready DeepSeek orchestration handoff for Evidence V0 P2
jermur788 Nov 4, 2026
466ae70
docs: require paste-ready DeepSeek orchestration and tiered escalation
jermur788 Nov 4, 2026
b37b794
docs: require DeepSeek orchestrator for Evidence V0 repair task
jermur788 Nov 4, 2026
6abc12d
docs: record mandatory DeepSeek orchestrator and paste-ready routing …
jermur788 Nov 4, 2026
7babf4b
docs: pin paste-ready DeepSeek orchestration as manager entrypoint
jermur788 Nov 4, 2026
5040531
docs: propose concise DeepSeek-only orchestrator handoff template for…
jermur788 Nov 4, 2026
8ebda55
docs: tighten proposed DeepSeek-only orchestrator handoff
jermur788 Nov 4, 2026
f151a3e
docs: adopt DeepSeek orchestration-only routing and subscription supe…
jermur788 Nov 4, 2026
3df0429
docs: publish accepted DeepSeek-only orchestration handoff template
jermur788 Nov 4, 2026
9c58bfc
docs: point coordination protocol to accepted orchestrator template
jermur788 Nov 4, 2026
39aa336
docs: independently source-review Evidence V0 P2 repair for promotion
jermur788 Nov 4, 2026
4bc0a99
docs: reconcile P2 source acceptance and record PR21 promotion decisi…
jermur788 Nov 4, 2026
af5201a
docs: hand off P2 repair source acceptance and PR21 promotion authority
jermur788 Nov 4, 2026
f6cd5cb
docs: clarify upstream baseline and add separate P2 repair checkpoint
jermur788 Nov 4, 2026
7de46f6
docs: record user-approved P2 PR21 source promotion, keep merge gate …
jermur788 Nov 4, 2026
6d9ee44
docs: hand off completed P2 PR21 draft promotion and separate main-me…
jermur788 Nov 4, 2026
cd99676
docs: record Option A approval and guarded PR21 promotion outcome
jermur788 Nov 4, 2026
0d00fed
docs: issue post-merge PR21 DeepSeek-only verification handoff
jermur788 Nov 4, 2026
a4b31aa
docs: record PR21 merged into fork main, verify ancestry and post-mer…
jermur788 Nov 4, 2026
9a5eb3a
docs: update Overall Manager handoff after verified PR21 fork-main merge
jermur788 Nov 4, 2026
4191036
docs: append verified PR21 fork-main merge outcome to P2 review
jermur788 Nov 4, 2026
61cb855
docs: reconcile PR21 post-merge worker qualification and local eviden…
jermur788 Nov 4, 2026
fcb1e9d
docs: reconcile post-merge local runtime qualification and unpublishe…
jermur788 Nov 4, 2026
1d9e6aa
docs: prepare DeepSeek-only postmerge evidence and residual gate handoff
jermur788 Nov 4, 2026
edf7d69
docs: update Overall Manager handoff for postmerge local PASS and evi…
jermur788 Nov 4, 2026
209cfe7
docs: reconcile PR21 local evidence closure and unresolved publicatio…
jermur788 Nov 4, 2026
3c87b9e
docs: classify postmerge evidence closed locally, mode client-local p…
jermur788 Nov 4, 2026
59e0d45
docs: hand off locally closed evidence, client-local mode PASS, and p…
jermur788 Nov 4, 2026
1ca4ed8
docs: prepare authorized local-only PR21 sanitized evidence subset ta…
jermur788 Nov 5, 2026
2c189e1
docs: record local-only sanitized evidence staging authorization and …
jermur788 Nov 5, 2026
900f2ed
docs: hand off authorized local-only PR21 evidence staging and no-upl…
jermur788 Nov 5, 2026
5ef0186
docs: reconcile local PR21 candidate and flag missing metadata checks…
jermur788 Nov 5, 2026
7573524
docs: bounded 80-entry metadata checksum correction handoff for priva…
jermur788 Nov 5, 2026
47b33cb
docs: classify PR21 private staging and request metadata checksum com…
jermur788 Nov 5, 2026
c0bd477
docs: update manager handoff after private candidate staging and chec…
jermur788 Nov 5, 2026
2d62f50
docs: keep private worker-host paths out of public correction packet
jermur788 Nov 5, 2026
82b4c61
docs: accept reviewed 80-entry private PR21 evidence checksum correction
jermur788 Nov 5, 2026
d65ab7f
docs: mark reviewed PR21 private evidence 80-entry integrity PASS; re…
jermur788 Nov 5, 2026
d743bac
docs: manager handoff records completed private candidate integrity a…
jermur788 Nov 5, 2026
e94f2b4
docs: mark PR21 private checksum correction completed and stop redisp…
jermur788 Nov 5, 2026
a8ddba2
docs: resolve historical PR21 checksum coverage finding after local r…
jermur788 Nov 5, 2026
7943235
docs: mark local-only PR21 evidence staging task complete and private
jermur788 Nov 5, 2026
38aa12b
docs: record user decision to keep PR21 evidence private
jermur788 Nov 5, 2026
1ff93cf
docs: carry forward private PR21 evidence decision in manager handoff
jermur788 Nov 5, 2026
5b8698e
docs: source-anchored D4 transactional revocation design proposal and…
jermur788 Nov 5, 2026
794161a
docs: inspect D2 continuation schema exposure and define built shippi…
jermur788 Nov 5, 2026
e914270
docs: stage2 bounded handoff task-stage2-d4-atomicity-feasibility-202…
jermur788 Nov 5, 2026
1da6bf9
docs: stage2 bounded handoff task-stage2-d2-built-mcp-shipping-audit-…
jermur788 Nov 5, 2026
be0928b
docs: stage2 bounded handoff task-stage2-upstream-experiment-reconcil…
jermur788 Nov 5, 2026
c5e62f3
docs: record Stage2 browser-first source review and bounded local han…
jermur788 Nov 5, 2026
ba637f8
docs: Stage2 browser reconnaissance, D4/D2 contracts and prepared loc…
jermur788 Nov 5, 2026
5c6f6b4
docs: manager Stage2 D4/D2 browser review and read-only T3 Code hando…
jermur788 Nov 5, 2026
b5ea942
docs: complete single DeepSeek orchestration handoff for three Stage2…
jermur788 Nov 5, 2026
b1460b3
docs: link complete Stage2 DeepSeek multi-lane handoff in 01_CURRENT_…
jermur788 Nov 5, 2026
111f43f
docs: link complete Stage2 DeepSeek multi-lane handoff in OVERALL_MAN…
jermur788 Nov 5, 2026
6eb48cd
docs: reconcile returned Stage2 A/B/C evidence and manager decisions
jermur788 Nov 5, 2026
d0a6d95
docs: integrate Stage2 defer-start result into proposed D4 safety con…
jermur788 Nov 5, 2026
81d63fb
docs: record measured D2 schema bytes and packaged release qualificat…
jermur788 Nov 5, 2026
0cf59c0
docs: close completed Stage2 lane feasibility with scoped evidence
jermur788 Nov 5, 2026
cc99211
docs: close completed Stage2 lane audit with scoped evidence
jermur788 Nov 5, 2026
30c77e5
docs: close completed Stage2 lane preview with scoped evidence
jermur788 Nov 5, 2026
439d9a5
docs: reconcile returned Stage2 A/B/C scopes and D4 product gates
jermur788 Nov 5, 2026
8b0f707
docs: reconcile Stage2 returned A/B/C lanes and D4 policy decision gate
jermur788 Nov 5, 2026
ebf147e
docs: close Stage2 A/B/C consolidated handoff after reviewed return
jermur788 Nov 5, 2026
b233793
docs: adopt user's D4 A+B no-new-run and prepared-start revocation co…
jermur788 Nov 5, 2026
4f24253
docs: update governing continuation spec with accepted D4 A+B safety …
jermur788 Nov 5, 2026
500d340
docs: prepare bounded isolated D4 A+B implementation and independent …
jermur788 Nov 5, 2026
3b09f02
docs: mark D4 research options superseded by accepted A+B product con…
jermur788 Nov 5, 2026
e703ed3
docs: record user's accepted D4 A+B contract and next isolated task
jermur788 Nov 5, 2026
b030f01
docs: manager handoff after user accepted D4 A+B contract
jermur788 Nov 5, 2026
79deecd
docs: reconcile isolated D4 A+B implementation and unproven full-serv…
jermur788 Nov 5, 2026
f97d3cc
docs: prepare bounded D4 true server-root assembly and async release …
jermur788 Nov 5, 2026
fea8ea7
docs: close isolated D4 implementation task; full-root verification r…
jermur788 Nov 5, 2026
0d6b2b1
docs: record isolated D4 implementation PASS with required full-root …
jermur788 Nov 5, 2026
34500c1
docs: manager D4 isolated implementation return and remaining full-ro…
jermur788 Nov 5, 2026
197d4e4
docs: D4 A+B isolated implementation returned; preserve assembly veri…
jermur788 Nov 5, 2026
824a2f7
docs: D4 A+B isolated implementation returned; preserve assembly veri…
jermur788 Nov 5, 2026
4717944
docs: record D4 real full-server K1/K2 PASS and remaining K3/D2 limits
jermur788 Nov 5, 2026
caab7e7
docs: close D4 full-root K1 K2 verification and retain K3 partial
jermur788 Nov 5, 2026
c61fa52
docs: D4 K1 K2 full-root runtime PASS after reviewed assembly return
jermur788 Nov 5, 2026
5780f2d
docs: mark initial D4 manager review superseded by successful full ro…
jermur788 Nov 5, 2026
00266d4
docs: accept isolated D4 K1 K2 full-root qualification and close veri…
jermur788 Nov 5, 2026
b6efcfd
docs: close reviewed D4 K1 K2 full-root passes and set integration de…
jermur788 Nov 5, 2026
1ecd25d
docs: mark D4 K1 K2 root checks passed and K3 partial, separate integ…
jermur788 Nov 5, 2026
d04f811
docs: present integration options after accepted isolated D4 K1 K2 ve…
jermur788 Nov 5, 2026
a78890a
docs: link post-D4 upstream integration decision brief
jermur788 Nov 5, 2026
5158a76
docs: link post-D4 upstream integration decision brief
jermur788 Nov 5, 2026
386b0d2
docs: correct numbered manager integration transition steps
jermur788 Nov 5, 2026
1a0f470
docs: adopt user-authorized isolated upstream catch-up trial governin…
jermur788 Nov 5, 2026
6b64ab1
docs: prepare user-authorized one-writer isolated upstream catch-up t…
jermur788 Nov 5, 2026
4d9e662
docs: record approved isolated upstream catch-up trial and next local…
jermur788 Nov 5, 2026
0f29897
docs: manager handoff for user-authorized isolated upstream catch-up …
jermur788 Nov 5, 2026
b825ba3
docs: mark upstream-first isolated trial approved by user, not dispat…
jermur788 Nov 5, 2026
6d85fb3
docs: user-authorized overnight conditional autonomy with three gated…
jermur788 Nov 6, 2026
99144a6
docs: complete paste-ready overnight gated DeepSeek U R H autonomy ha…
jermur788 Nov 6, 2026
3af738e
docs: amend upstream trial with authorized gated overnight local-only…
jermur788 Nov 6, 2026
1de7d3c
docs: amend upstream trial with authorized gated overnight local-only…
jermur788 Nov 6, 2026
0f3c3e1
docs: require per-decision durable DeepSeek routing and quota ledger
jermur788 Nov 6, 2026
88a9439
docs: make overnight DeepSeek routing-decision ledger a pre-dispatch …
jermur788 Nov 6, 2026
f47875f
docs: correct routing ledger formatting in overnight paste-ready handoff
jermur788 Nov 6, 2026
2c5e72f
docs: record overnight U-R-H conditional authority and mandatory rout…
jermur788 Nov 6, 2026
8140188
docs: manager handoff overnight gated U-R-H and per-routing-decision …
jermur788 Nov 6, 2026
8c00b54
docs: reconcile completed upstream trial, batched test evidence and o…
jermur788 Nov 6, 2026
edd4dc9
docs: gate R promotion on full durable routing ledger after completed…
jermur788 Nov 6, 2026
3834bd4
docs: close U trial and hold overnight R on routing ledger validation
jermur788 Nov 6, 2026
d9b59f8
docs: close U trial and hold overnight R on routing ledger validation
jermur788 Nov 6, 2026
a7e781a
docs: reconcile overnight G-U batch equivalence and hold R on routing…
jermur788 Nov 6, 2026
2d46eed
docs: update overnight paste-ready handoff after U already returned
jermur788 Nov 6, 2026
865bc6c
docs: reconcile completed U trial, timed-out wrapper and routing gate…
jermur788 Nov 6, 2026
a1b1e31
docs: reconcile completed U and hold local R on durable routing-decis…
jermur788 Nov 6, 2026
c6d86ac
docs: reconcile Stage R tests, independent-review gate and Opus routi…
jermur788 Nov 6, 2026
63e76c1
docs: require cross-provider Stage R review and Opus routing audit be…
jermur788 Nov 6, 2026
720fddd
docs: reconcile Stage R tests but hold G-R on cross-provider review a…
jermur788 Nov 6, 2026
1e2d1e5
docs: manager handoff Stage R test return with cross-provider and Opu…
jermur788 Nov 6, 2026
f9b09a5
docs: hold G-R for cross-provider review and unauthorized Opus routing
jermur788 Nov 6, 2026
de7884f
docs: update overnight packet after Stage R return and hold H until c…
jermur788 Nov 6, 2026
0096b48
docs: record user's confirmation that Stage R Opus fallback was approved
jermur788 Nov 6, 2026
e8ecf42
docs: correct Current State to owner-approved Stage R Opus fallback; …
jermur788 Nov 6, 2026
243ca24
docs: correct manager handoff — Stage R Opus owner-approved, independ…
jermur788 Nov 6, 2026
98e329f
docs: retract earlier unsupported Opus deviation after owner confirms…
jermur788 Nov 6, 2026
b2a681a
docs: correct R handoff to owner-approved Opus fallback
jermur788 Nov 6, 2026
8a6b5ab
docs: clarify approved Stage R Opus while preserving review gate
jermur788 Nov 6, 2026
4ce9d58
docs: clarify approved Stage R Opus while preserving review gate
jermur788 Nov 6, 2026
3487a7d
docs: reconcile Maria feedback and current conflict state on upstream…
jermur788 Nov 6, 2026
3bdf1d7
docs: record Maria upstream PR 28777 reply in overall manager handoff
jermur788 Nov 6, 2026
65948c4
docs: prepare cooperative upstream PR conflict and regression task wi…
jermur788 Nov 6, 2026
9e55c5c
docs: record prepared cooperative upstream conflict-and-test task wit…
jermur788 Nov 6, 2026
5a85268
docs: hand off parallel upstream cooperative regression fix task and …
jermur788 Nov 6, 2026
3b52d5a
docs: timestamp standalone upstream cooperative task packet preparation
jermur788 Nov 6, 2026
e3d32e5
docs: timestamp standalone upstream cooperative task packet preparation
jermur788 Nov 6, 2026
ad242b4
docs: reconcile completed overnight U R H qualification and remaining…
jermur788 Nov 6, 2026
e0ad342
docs: close overnight U R H gates and preserve D2 packaged/K3 live re…
jermur788 Nov 6, 2026
d908de7
docs: manager handoff final U R H complete, packaged D2 and real prov…
jermur788 Nov 6, 2026
143e30e
docs: prepare but do not authorize packaged authenticated D2 verifica…
jermur788 Nov 6, 2026
369bdfb
docs: reconcile staged D1 D5 spec with completed isolated U R H, ship…
jermur788 Nov 6, 2026
6420ba1
docs: record R new-root K1 K2 pass and bounded H K3 without changing …
jermur788 Nov 6, 2026
1849a21
docs: close overnight U R H amendment after final worker handoff
jermur788 Nov 6, 2026
c0d5838
docs: link proposed packaged D2 qualification without authorizing new…
jermur788 Nov 6, 2026
469c29c
docs: link proposed packaged D2 qualification without authorizing new…
jermur788 Nov 6, 2026
568ca6b
docs: complete new Overall Manager transition handoff after U R H qua…
jermur788 Nov 6, 2026
b3bfed6
docs: link current manager state to new T3 Fork successor handoff
jermur788 Nov 6, 2026
5fa835f
docs: link current manager state to new T3 Fork successor handoff
jermur788 Nov 6, 2026
bf7f23c
docs: record browser D4/D2 recovery diagnostics and preserve hold
jermur788 Nov 7, 2026
acdd6f3
docs: reconcile D4 D2 browser findings into current state (hold)
jermur788 Nov 7, 2026
f50397f
docs: link browser recovery diagnostics from manager handoff
jermur788 Nov 7, 2026
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
186 changes: 186 additions & 0 deletions 01_CURRENT_STATE.md

Large diffs are not rendered by default.

220 changes: 220 additions & 0 deletions 02_COORDINATION_HANDOFF_PROTOCOL.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,220 @@
# T3 Fork — Coordination and Automatic Handoff Protocol

**Classification:** STABLE COORDINATION INSTRUCTIONS, mirrored to shared GitHub from the project's governing Coordination/Handoff Protocol. Update this deliberately if the governing protocol changes; do not silently reinterpret it.
**Current state:** [01_CURRENT_STATE.md](01_CURRENT_STATE.md). **Manager continuation:** [OVERALL_MANAGER_HANDOFF.md](OVERALL_MANAGER_HANDOFF.md).

## Purpose

Make multi-worker and multi-manager development continue with minimal manual relay while preserving explicit authority, repo safety, and verifiable state.

## Canonical-state rule

Chat history is not project state.

Canonical continuation should come from:
1. Project Instructions;
2. Current State / Roadmap;
3. governing spec;
4. Runtime task state;
5. latest authoritative handoff;
6. inspected repository/runtime evidence.

Historical handoffs may explain how the project arrived here, but they must not override newer accepted state.

## When a handoff is mandatory

Create a handoff automatically after any substantial:
- implementation task;
- investigation that changes architectural understanding;
- review with material findings or pass verdict;
- verification/qualification gate;
- integration/merge;
- blocker that changes sequencing;
- provider/thread/worktree transition where another worker will continue;
- manager-chat transition;
- long phase whose accumulated state would otherwise require rereading chat history.

Tiny local fixes inside one ongoing worker session do not need separate handoffs unless they materially change accepted state.

## Mandatory paste-ready DeepSeek orchestration handoffs (accepted user policy, 2026-11-04)

Whenever the next authorized action needs a T3 Code worker/session, the Overall Manager must provide **one complete, copy-and-paste-ready handoff in the user-facing reply** and preserve the same authoritative packet in Runtime or the branch ledger. Writing or linking a packet never starts a worker. Use the [compact standard handoff template](docs/orchestration-v2/DEEPSEEK_ORCHESTRATOR_HANDOFF_TEMPLATE_V1.md) with task-specific governing spec, base, scope, verification and stop conditions.

**DeepSeek is an orchestration-only resource** for future dispatches: task decomposition, selecting workers, supervising status and usage limits, inspecting evidence, routing bounded repairs/reviews, maintaining authoritative task/ledger records, and completing handoffs. **Do not route implementation, source edits, development test execution or code review to DeepSeek.** Preserve its limited OpenCode subscription for high-leverage coordination. This does not retroactively invalidate already-dispatched P2 work, which ran under the prior task packet.

**Development worker policy:** Assign **all implementation, debugging and test execution** to **Codex GPT-6.1 SOL — Medium** or **Claude Sonnet 5.5 — Medium**, selecting on task fit, actual provider/subscription availability, ownership, and available capacity evidence. Independent reviewer must be a different provider/model from the implementer and read-only. Escalate materially difficult unresolved security/concurrency/integration to **Claude Opus 5.5** at the least adequate effort (normally Low/Medium initially); Opus is not a default. Two genuinely different evidence-backed routine remediation attempts precede expensive escalation when safe; immediate authority/security stops do not wait for retries. DeepSeek remains orchestrator throughout.

**Subscription watch and recovery:** Each subscription (e.g. separate Claude pools) is tracked independently at start, dispatch, completion, auth/quota error, and logical transition: `AVAILABLE`, `BUSY`, `COOLDOWN/QUOTA`, `LOGIN-UNAVAILABLE`, or `UNKNOWN`; task in flight; source and provider-reported five-hour reset/window; remaining allowance if actually available. The user's **~10% remaining 30-day DeepSeek allocation with ~10 days remaining** is a dated user report, *not* live measurement. If a worker hits an actual limit, checkpoint its owned work and ledger, reroute to an available authorized model/subscription if safe, or resume after a **provider-confirmed reset** using a real supported T3 continuation mechanism. If the host cannot wait/resume unattended, publish an exact restart-ready handoff; do not claim background automatic restart. Never bypass quotas or invent allowance/reset times.

**Ledger:** Update T3 Project Runtime task/attempt/handoff state as events happen; fall back to an append-only owned branch ledger if Runtime is unavailable. Record UTC time, task and attempt, orchestrator, requested and actual worker provider/model/effort, options rejected and reason, capacity and source (or UNKNOWN), branch/worktree writer, tests/outcomes/failure, independent reviewer, next action. Keep observed facts, orchestrator claims, and retrospective inferences distinct; do not promote worker claims to independently proven success.

**Template completeness:** start command for DeepSeek; objective and governing spec; actual repo/base/ownership; worker and quota policy; acceptance tests; independent review; ledger location; escalation, stop and final handoff instructions. Preserve one writer per overlapping lane. No worker may merge, rewrite history, incur material paid cost, bypass security or change accepted architecture without applicable authorization.

**Status:** Accepted prospective orchestration/routing policy. The previously issued P2 handoff and its completed historical provider choices are not reinterpreted as violations.

## Worker end-of-task protocol

Before ending substantial work, the worker should:
1. inspect final repo/worktree status;
2. run the acceptance/verification required by the task packet;
3. update the Runtime task if available;
4. append a Runtime handoff if available;
5. return the same essential handoff to the manager;
6. stop without starting an unauthorized milestone.

If Runtime handoff tooling is unavailable, the structured handoff returned to the manager is mandatory and the manager should persist/reconcile it as soon as possible.

## Required handoff fields

### VERDICT
One of the precise project states appropriate to the task, e.g. IMPLEMENTED, STATIC PASS, RUNTIME PASS, REVIEW PASS, VERIFIED, BLOCKED.

### BASE / CHECKPOINT
- starting base;
- branch/worktree;
- final revision/checkpoint;
- relevant upstream revision;
- working-tree cleanliness.

### RESULT
- concise description of what changed or was learned;
- files/components affected;
- intentional exclusions.

### VERIFICATION
- exact tests/checks run;
- important counts/results;
- runtime/UI/restart/provider evidence where required;
- checks not run and why.

### FAILURES / RISKS
- real failures encountered and repairs;
- unresolved risks;
- blocker classification where applicable.

### REVIEW
- reviewer/provider/model for material reviews;
- findings;
- repairs;
- re-review result.

### INTEGRATION STATE
- not integrated / PR open / merged / verified integrated head;
- whether content drift exists;
- whether cleanup remains.

### NEXT
- exact next authorized action;
- whether user action is needed;
- explicit stop condition if no further work is authorized.

## Manager handoff-consumption protocol

When a worker returns a handoff, the manager should automatically:
1. compare it with the governing spec/task packet;
2. inspect repo/runtime evidence proportionate to risk;
3. reject unsupported status claims;
4. classify defects/blockers;
5. route routine repairs or independent review without asking the user;
6. update Current State and Runtime task/handoff state when appropriate;
7. integrate if already authorized and acceptance is satisfied;
8. verify the integrated head where required;
9. issue the next authorized task packet.

The manager should not stop simply to report that a worker finished.

## Automatic continuation state machine

`TASK ISSUED -> IMPLEMENTATION -> REVIEW/VERIFY -> REPAIR IF NEEDED -> RE-REVIEW -> INTEGRATE IF AUTHORIZED -> VERIFY INTEGRATED HEAD -> UPDATE CANONICAL STATE -> NEXT AUTHORIZED TASK`

Only leave this flow for a genuine stop condition.

## Stop conditions requiring the user

Stop for:
- product choice;
- material architecture trade-off;
- meaningful scope expansion;
- irreversible/destructive decision;
- unresolved security or integration conflict;
- paid infrastructure/material cost decision;
- conflict between current user intent and accepted project direction.

Do not stop for routine:
- test failures;
- implementation defects;
- review findings;
- migration fixes;
- lint/typecheck issues;
- CI retries/reconciliation;
- evidence collection;
- already-authorized integration.

## Task-packet requirements

Substantial task packets should be self-contained and include:
- TASK;
- ROUTING;
- BASE/CONTEXT;
- GOVERNING SPEC;
- GOAL;
- IN SCOPE;
- OUT OF SCOPE;
- OWNERSHIP;
- ACCEPTANCE;
- VERIFICATION;
- STOP CONDITIONS;
- HANDOFF.

A packet must work without manager-chat history.

## Parallel work

Use parallel workers only when ownership is non-overlapping or isolated by worktree/component. One writer per overlapping lane. Independent read-only review/research may run in parallel. The manager owns reconciliation and integration order.

## Manager transition protocol

Before creating a fresh manager chat:
1. update Current State / Roadmap;
2. ensure active tasks have current status and latest handoffs;
3. record the authoritative repo base and active milestone/gate;
4. archive or clearly mark stale source files as historical;
5. create a concise Overall Manager handoff only for details not already captured canonically.

The new manager should not need the old chat to continue.

## Source hygiene

Maintain a small canonical source set. Prefer updating current-state files over adding endless chronological handoff documents.

Recommended project sources:
- `PROJECT_INSTRUCTIONS` — stable behavior/authority rules (stored in Project Instructions; this markdown is a copy/reference);
- `01_CURRENT_STATE.md` — volatile current base, milestone, decisions, roadmap, immediate next action;
- `02_COORDINATION_HANDOFF_PROTOCOL.md` — stable task/handoff/continuation process;
- governing milestone specs as separate authoritative sources when active.

When a source becomes historical, mark/archive it rather than leaving contradictory “current” instructions discoverable beside the new state.

## Source authority labels

When practical, classify sources as:
- decision;
- spec;
- implementation truth;
- coordination state;
- research;
- reference;
- historical.

When sources conflict, follow the project authority model and surface the conflict rather than silently blending them.

## User-facing reporting

Keep detailed technical evidence in handoffs. User-facing updates after important transitions should state:
1. what changed;
2. what passed/failed;
3. what it means;
4. what happens next;
5. whether the user must act.

If no user action is needed, say so and continue.
29 changes: 29 additions & 0 deletions JAS_T3_FORK_MANAGER_HANDOFF_20261104.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,29 @@
# Jas — T3 Fork Manager Handoff
**Updated:** 4 November 2026
**Status:** Current transition brief; detailed truth lives in linked sources.

## Role and objective
You are the **Overall Manager** for T3 Fork; the user makes final product decisions. Build an upstream-friendly fork with a **provider-neutral Project Runtime**. State, decisions, tasks, handoffs and execution evidence must persist outside chats and individual models. CCF is the first use case; the operations dashboard remains a separate project.

## Read first
- [Current State / Roadmap](01_CURRENT_STATE.md) — authoritative milestone, decisions, blockers.
- [Coordination/Handoff Protocol](02_COORDINATION_HANDOFF_PROTOCOL.md) — task lifecycle, routing, verification, Git safety.
- [Full manager handoff](OVERALL_MANAGER_HANDOFF.md) — context and accepted authority.
- [Pre-merge verification task](docs/orchestration-v2/task-verify-reconciled-v017-before-main-20261104.md).

Inspect live GitHub, Runtime and worktrees before trusting recorded statuses. Worker claims are not proof.

## Current position
- [Fork-only PR #21](https://github.com/jermur788/t3code/pull/21) is **OPEN, DRAFT, UNMERGED**; fork `main` is unchanged. It reconciles upstream **v0.1.7**, resolving seven conflicts. Local evidence reports 40-package typecheck, web build and 2,072 changed-file tests passing; independent Codex review was clean. **No hosted CI or complete production verification** was established.
- [PR #20](https://github.com/jermur788/t3code/pull/20) remains a separate draft research PR.
- [Default-off continuation experiment](https://github.com/jermur788/t3code/tree/experiment/continuation-default-off-gate-20261104) is implemented and reviewed **on an isolated branch**; it is **not in PR #21 or main**.

## Decisions already approved
The experiment must be **server-gated off by default**. Best-effort cancellation is acceptable only in isolated stub testing. Before public release, exclude experimental agent-facing schemas and their extra context cost, and guarantee **no new run creation after durable authorization revocation**. Strict launch semantics still need architectural review; do not change upstream execution internals unilaterally.

## Next authorized action
**Complete pre-merge verification for PR #21**: rendered UI for both route surfaces; file-backed restart and cross-project isolation; Evidence V0 recovery/export after pruning; affected tests, typechecks and budget checks; independent review. Use a fresh isolated worktree. Record routing choices and evidence in Runtime or a durable ledger.

DeepSeek can coordinate routine work; escalate difficult security/integration issues to Codex/Claude-class models. Use two distinct evidence-backed repair attempts before escalation; enforce one writer per code lane.

**Do not merge PR #21, enable production, rewrite history or spend materially without approval.** After verification, update canonical state and request a separate merge decision. Written handoffs do not start workers.
Loading