You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit b853293
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: docs/architecture/rfcs/capable-manager-semantic-handoff-v0.md
+12Lines changed: 12 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -490,6 +490,18 @@ Artifact continuity is part of semantic continuity. Reuse the artifact owner to
490
490
Long-running work must remain legible in the existing conversation: what is being attempted, who owns the next step, what is actually blocking, and what conclusion is owed. Provide expandable tool/artifact activity and current semantic context in the frontend; Lark gets a concise equivalent and actionable results. Distinguish a queued worker, unavailable host, permission refusal, website login and undelivered answer. Do not expose raw protocol envelopes or claim fine-grained tool activity on adapters that cannot supply it.
491
491
492
492
The App must also preserve the user's chosen work view across reload and browser history. Manager conversation and Goal overview/tasks/conversation/artifacts use the existing typed workspace route; source loading must not insert duplicate history entries. Preserve the source and Goal identity, retain an unsent draft under its existing owner, and never start or replay a Turn merely to restore navigation. Fresh-entry defaults remain distinct from restoring an explicit view. Packaged navigation recovery qualifies this presentation boundary only; actual receiver adoption, steering and owed-result return retain their independent acceptance requirements.
493
+
The shared App activity control preserves an unsent or unconfirmed adjustment
494
+
across view changes and reload. Composer and inline controls use one TS client
495
+
cache; each inline draft is bound to its original session and Turn. Restoring a
496
+
draft dispatches nothing. Retries of unchanged text retain the same ingress
497
+
identity after unknown delivery or mismatched receipts; confirmed non-delivery
498
+
allows a fresh identity. Editing the instruction starts a distinct request.
499
+
Accepted delivery retires that exact entry without erasing another draft. An
500
+
ended Turn keeps its unsent draft readable and cannot redirect it to newer work.
501
+
Unavailable browser storage preserves page-memory recovery only, not reload
502
+
recovery. Packaged browser transport and the real Chat steering/store tests
503
+
qualify this bounded recovery behavior; live executor adoption, installed App
504
+
readback and Lark steering remain separate acceptance.
493
505
494
506
Reuse existing capability instructions, context hooks, memory and scheduling owners. Reusable methods may inform planning and handoff, with their source/version visible; remembered lessons do not replace accepted task state or current verification. Stable recurring work may use the existing schedule/event path after its task and replay behavior are understood. This RFC does not add a routine engine, compulsory method learning, a new hook family or business-specific automation.
Copy file name to clipboardExpand all lines: docs/architecture/rfcs/loopx-overall-roadmap-v0.md
+7Lines changed: 7 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -625,6 +625,13 @@ Current status is design proposal; no G1 or default-screen promotion.
625
625
-**Exit:** actual manager→worker and worker→worker callers; follow-up messages, lost source session, oversized answer, duplicate callback, successful send with lost ACK and transport restart. CLI, packaged frontend and Lark read back the same result with audience isolation. Ordinary already-authorized work gains no second confirmation.
626
626
-**Migration/rollback:** characterize first, record old writer/reader mappings and deletion payoff; disabling new production must leave old requests drainable. Do not retain two writable lifecycles.
627
627
628
+
The GQ08 App correction path now retains inline adjustments and ingress identity
629
+
across view changes/reload through the same TS client cache as the composer.
630
+
Restoration never dispatches work, and a terminal Turn cannot inherit a new
631
+
Turn's target. Packaged recovery, blocked storage, coexisting drafts and real
632
+
Chat ingress/store regression are bounded evidence; live recipient adoption,
633
+
installed readback and Lark correction still belong to R3 qualification.
634
+
628
635
R3 also qualifies the handoff RFC's hierarchical A6/A8/A13 extension: a managed
629
636
worker requests, validates and integrates another peer's artifact before returning
630
637
to the lead. Reuse the same request and work owners at each level. The ingress
0 commit comments