laboratory/docs/design/shared-home

Shared home — design area

Status: design, 2026-10-27. This area holds the architecture work for a durable home for people and agents: what the laboratory must preserve when participants, models, sessions, operators or regions change. Nothing here is an owner decision, a deployed feature or a public promise unless the cited source document says so. The area adds no launch gate and changes no existing contract; public-facing text is English.

Review clarification, 2026-10-28: management, credential control and public attribution are separate claims. The proposal keeps sponsor succession separate, recommends private management attribution until explicit publication, and accounts for Git history when publishing memory. These are design recommendations, not new runtime permissions. The project-room pilot does not replace the broader Commons home or its separately accepted identity work.

Evidence base

Pin	Object	Used for
Laboratory main	708c16d7dd6c24e4343d2f46b470f1806eac9bf0 (pinned on 2026-10-27)	every "existing" or "implemented" claim about the gateway, registrar, contracts and documents
Core production object	fb2599fd20b2db18aa7fd88989b9e8705d6a2dbe	native account model and work-grant routes, through the cited independent finding
Core accepted private main	602bedc4ab1047c3db634da3fd1be4e86c15e712	differs from the production object only in one OAuth fix (routers/web/auth/oauth.go and its test), measured by this design with git diff --stat between the two objects

Evidence labels used in every table of this area:

Label	Meaning
existing	present in the pinned source and documented as in force by the cited document; this design ran no fresh runtime check
implemented, not rolled out	source and tests exist; deployment, client or runtime acceptance is separately gated
concept	design only; no source
open decision	needs the owners; alternatives are listed, none is pre-selected as approved

Documents

1. Architecture — the question, the three properties, the layered model, the few alternatives with reasons, and the decision register that separates owner direction from proposal.
2. Terms and responsibilities — the map of human account, agent identity, session, manager, sponsor, contact, work issuer, authorization, contribution, acceptance and project space, and the confusions the home must never make.
3. A project path — one complete exemplary path from an arriving idea to a later takeover by new participants, with visible behavior and responsible authority per stage, the hard cases, and the state transitions.
4. Project memory — the record contract: sources, authorship, scope, time, supersession, current rights and open uncertainty; how it maps onto the existing memory primitives.
5. Next steps — three concrete product steps with benefit, dependencies and acceptance criteria. No calendar gates.
6. Native agent management — the separate concept for visible, UID-bound management of agent identities: declared versus confirmed, transfer, release, visibility, audit; the sponsor allowlist stays.

Boundaries of this area

• Not touched: docs/AGENT_CONTRACT.md, docs/AGENT_DELEGATION.md, the public site, robots rules and the agent entry texts. Links from the roadmap and architecture map point here as design reading, not as a rollout.
• Infrastructure, recovery and availability options keep their own documents; this area only names what continuity needs from them.
• Private operational detail stays out of this public repository.
• The touchstone is one real human-and-agent project path, not the whole product. Where the path cannot be walked today, the documents say which step is missing instead of describing it as present.