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.
40 lines
1.9 KiB
Markdown
40 lines
1.9 KiB
Markdown
# Multi-user identity and authority
|
|
|
|
Status: intended foundation behavior; UI attribution alone is not an implemented
|
|
access boundary. Mosaic is intended to support multiple users by default.
|
|
|
|
Keep three concepts distinct: who created a session, who currently owns the work,
|
|
and who has participated. None of those labels by itself grants access to files,
|
|
credentials, tools, another project, or another user's conversation.
|
|
|
|
## Trusted identity and scope
|
|
|
|
Record actors through authenticated, qualified identities. Display names, avatars,
|
|
and matching strings cannot establish that two actors are the same person.
|
|
Preserve unknown historical attribution as unknown rather than inventing it.
|
|
|
|
Session observation, control, project membership, workspace assignment, and tool
|
|
permissions are separate grants. Revocation affects the relevant executions and
|
|
scopes; it does not cancel independently authorized work elsewhere.
|
|
|
|
User context follows relevance and permission. Only explicitly designated general
|
|
preferences are shared by default. Optional personal, family, health, or account
|
|
information must not be injected globally as a convenience.
|
|
|
|
## Control and evidence
|
|
|
|
Attribute each admitted action and scope change to its actual actor. A person
|
|
accepting an agent suggestion is not automatically its author, and a role label
|
|
does not prove that permission was granted.
|
|
|
|
The UI should distinguish owner, observer and controller. Enforcement belongs to
|
|
the trusted runtime/policy path. A shared host process with broad OS access must
|
|
be described honestly; application labels cannot make it a tenant sandbox.
|
|
|
|
ACT-C11 tests the distinction between attribution and permission. Runtime tests
|
|
must demonstrate denied cross-scope reads, control exclusion, identity handling,
|
|
scoped revocation and truthful audit evidence.
|
|
|
|
See [session attachment](session-attachment.md), [context](context.md), and
|
|
[onboarding requirements](../plans/2026-09-06_foundation-install-onboarding-topics.md).
|