jason.woltje
193479b52d
Mosaic concepts pages now own the adapted content; source/license metadata under docs/reference/concepts. Adds ACT-1 agent-context planning capture, pinned concept test package + preparation utility, foundation observation notes (durability, evidence, federation, onboarding, workflow), and the #1495 consolidation assessment. TOOLS.md updated for the host-dev launcher.
43 lines
2.1 KiB
Markdown
43 lines
2.1 KiB
Markdown
# Session attachment across interfaces
|
|
|
|
Status: foundation intent agreed; unified attachment is not established by the
|
|
temporary host TUI. See foundation R11, R21, R24 and R25.
|
|
|
|
Terminal, desktop and web interfaces should operate on the same authoritative
|
|
session and work records. Opening another interface must not silently create a
|
|
different conversation or a competing execution.
|
|
|
|
## Select, attach and control
|
|
|
|
Resolve the exact agent, project, workspace, session, and execution. Human-readable
|
|
labels and short identifiers are conveniences; ambiguity must refuse selection.
|
|
Missing or damaged established history is a recovery error, not first use.
|
|
|
|
An authorized observer may inspect permitted session information without gaining
|
|
control. Initially one controller owns input. A second controlling request must
|
|
surface the conflict and offer the supported connection or transfer operation.
|
|
Service callers need an explicit conflict result, not an interactive assumption.
|
|
|
|
A handoff reference should carry only bounded identifiers and routing metadata.
|
|
It must not contain credentials. Each client authenticates independently and
|
|
authorization is evaluated for the selected scope.
|
|
|
|
## Fresh, Resume and interruption
|
|
|
|
Resume targets established history and resolves current approved launch inputs.
|
|
Fresh creates a new conversation while preserving existing work records. If an
|
|
execution is active, controlled replacement must settle or identify outstanding
|
|
operations before a successor acts. Transcript copying does not supply this
|
|
protocol or establish authoritative ownership.
|
|
|
|
Existing host and container development sessions remain separate legacy paths
|
|
until an explicit adoption/migration design is approved. Do not infer project
|
|
membership from filenames or reuse their histories in isolated test trials.
|
|
|
|
ACT-C06 is a synthetic attachment reasoning case. Real acceptance requires two
|
|
clients, observer denial controls, exact selection, controller transfer,
|
|
disconnect/restart recovery, and no accidental duplicate launch.
|
|
|
|
See [multi-user authority](multi-user.md) and
|
|
[foundation](../plans/2026-09-06_agent-project-workspace-foundation.md).
|