Foundations
Your data, your rules, your approval. The five pillars say what WilsonOS is made of. They do not say who may see the work, where its records live, or how the system reaches the outside world. Those concerns cut across everything, so WilsonOS treats them as foundations every pillar stands on: identity and access, and data governance. Connections are part of the Capabilities pillar, but their rules hold everywhere and are repeated here.
People and access
Section titled “People and access”WilsonOS is built for a person with businesses, and then for the people around them: a partner who runs one brand, an assistant who reviews drafts, a client who needs to approve a cover.
Four ideas are kept deliberately apart, because collapsing any two is the usual mistake:
| Is | Is not | |
|---|---|---|
| Person | Someone with credentials who can sign in | An agent |
| Brand | A workspace that holds work | A permission |
| Access grant | A person’s rights on a brand | A property of the person or the brand |
| Agent | Acts on behalf of a person, within a brand | A user, or anything with rights of its own |
Access is granted on the brand, not the file. Every task, deliverable, media item and document inherits from the brand it belongs to, so a new deliverable is visible to the right people without anyone filing a permission, and “who can see this?” always has an answer. A partner gets a grant on one brand and sees nothing of the others; a client gets read-only access; an owner sees everything.
Agents act on your behalf. Everything an agent writes records both facts — Scout, for you, in Code Pineapple — and ownership is assigned by the writer at the moment of writing, never guessed later from a folder name. Because the authority is borrowed, it is bounded: an agent working in one conversation cannot reach another person’s conversations, another brand’s files, or any secret.
Private work belongs to you. Your priorities, commitments and private conversations are scoped to you and the agent, never appear in a brand, and are not visible to a teammate on the same brand. They reach a brand’s shared knowledge only through a promotion you approve.
Conversations have their own membership. Brand access gets you into a brand’s work, not into someone else’s private conversation in that brand. A private conversation has one owner; a shared room has an explicit, live participant list checked on every turn, and the agent acts with the sender’s rights for that turn. If you are not a member, the room is simply absent from your list.
| Role | Intended meaning |
|---|---|
| Owner | Runs the organisation; grants and revokes access; approves what is promoted into shared brand knowledge |
| Member | A teammate with access to one or more brands, working in them as you do |
| Reviewer | Can view, comment on and approve what is shared with them, and nothing else |
A teammate is inside the organisation and works in the Workbench with the brand’s agent. A client is outside it and sees only the versions you share, with the permissions you choose, never the brand’s internal work, other clients, or your conversations. A client’s approval accepts a version; it never authorises publishing it. The intended commercial model is per user; pricing is undecided.
Data governance
Section titled “Data governance”Every kind of data — a task, a brand document, a generated image, a memory entry, a measurement — has exactly one place it lives authoritatively and exactly one path that writes it. Prose people edit, brand documents and code live as files; tasks, media, memory and measurements live in the database. Nothing is written to a table by hand, and nothing is edited in a copy in the hope that the original follows.
For outputs specifically, the registry gives each one its identity, durable storage keeps the bytes, and isolated working copies let agents edit safely. A name or location is a label, never the identity, so files can be renamed or moved without breaking anything that points at them. Governance also covers versions, retention, backup and recovery, and it is why the shared business records — product, offer, campaign and the rest — can connect work across every surface.
Connections, everywhere
Section titled “Connections, everywhere”- Same operations, two interfaces. A person clicks Publish; an agent calls a tool. Both go through the same service and the same permission checks, so exposing something to agents never creates a second source of truth.
- One door per capability. Generation, editing, registration and publishing each have one door that holds the keys and writes a receipt. That is what makes cost caps, receipts and attribution reliable. See Capabilities.
Rules the foundations share
Section titled “Rules the foundations share”- Default deny. A new kind of record starts inaccessible and is opened deliberately. Every record that holds someone’s content carries an owner — not most of them, every one — because a record without an owner cannot be shared, revoked or deleted on request.
- Enforced in the database, not only the app. An app-level check protects only the paths that remember to call it; database rules protect all of them.
- Credentials are never indexed, searched or synced. Secrets sit outside the searchable material by construction.
- Storage and search have different jobs. Search finds relevant records; it never replaces storage, versions or access control.
- Multi-user is the test. Each rule is written for the day more than one person, and more than one customer, uses the system. Anything that only works because a single operator is the only user is a known gap, listed and scheduled, not assumed away.
Rules for everyone building it
Section titled “Rules for everyone building it”Product and design
- A screen answers one question a person would ask out loud.
- Collaboration is a mode inside chat, the Workbench, the Studio and the engines, not a tab of its own.
- Review is shared. An engine that grows its own review screen is a bug.
- A short answer in the chat; the detail one link away.
- Every “yes” is on a specific thing: a version, a price, a spend.
- Money always stops and asks, including in a scheduled run at 3am.
- An engine never approves its own work.
- Personal is unshareable by construction, not by a setting.
Engineering
- One writer per kind of record. Never a raw query, never a hand-edited task file.
- A screen never writes a record; it submits to the one writer path.
- Nothing reaches the outside world directly. Doors hold the keys and write receipts.
- Output is a version on a task, or it did not happen.
- Read the subsystem’s contract before touching the subsystem.
- A compile is not a verification. Drive the interface and look at the result.
- State a fact about the system together with its check.
Related
Sources: input/WilsonOS_Overview.html §05, docs/architecture/overview.md, docs/architecture/identity-access.md §3–4, §7, docs/architecture/data-governance.md, docs/architecture/connections.md, docs/architecture/agents-runtime.md §Per-conversation runtimes (owner vs participant admission), docs/wilsonos-app/multi-tenant-conops.md, docs/DECISIONS.md (ADR-028), WilsonOS Team Brief (prototype), "The non-negotiables" — absorbed (task 494), Don's product direction, 2026-09-16 (task 410 review, §D) · Last verified 2026-10-06

