Objective
A measurable outcome. The unit a human and an agent are both pointed at, and the natural place to attach progress. Progress can be typed in, or read from a dataset.
Siteplan's whole design follows from one decision: an AI agent is a first-class actor in the same system as a human. Not a separate service, not a chat panel, not a second permission model — the same room, the same event stream, the same audit trail, with deliberately asymmetric authority.
Siteplan began as a Wagtail CMS that also works as a foundation for building Django applications. That origin is not incidental — it explains the constraints that shape the whole design.
The portal is a CMS. The agent-native layer is built on top of it without replacing it. The existing Wagtail admin, the CRUD views and the current authentication keep working. Nothing in the agent direction requires a second framework, a second schema owner or a second place to log in.
AbstractUser, and
AUTH_USER_MODEL cannot be swapped after the first migration. Agents extend
the existing siteplan_user.User — they do not get their own identity table.
The tenant is an Organization. A company, a charity, a club and a government
body are all the same entity. Organizations can nest, so a holding company has
subsidiaries, and one organization can share a room with another — which covers clients and
vendors without merging their accounts.
What an entity signs up for. It owns the agent roster, the credentials, the user-defined apps and the spend. Can nest, so subsidiaries are structural rather than a second root.
Who works together inside the organization. Deliberately not called a "Department" — the organization names its own, so a company types "Sales" and a club types "Beginners".
Where work happens. Belongs to a team, or directly to the organization when it is company-wide. Holds artifacts that outlive any one conversation.
The conversation unit, and always topical. Its subject is required, so a branch cannot exist without naming what it is about.
Organization. Keeping that vocabulary separate is what stops a five-level
hierarchy with two roots to explain.
Slack's shape — a main stream plus threads hanging off it — splits a discussion into two places and loses topicality. Siteplan makes the fork the only way to branch.
FORKED event in the parent at the exact message being forked, and creates the child with a parent and a fork anchor.ACTIVITY topic holds room-scoped work that belongs to no conversation — a task created directly in a room, an objective changing state. It keeps ordering and replayability without a nullable topic column.The hierarchy says where work happens. It does not say why. Four entities carry that: objectives, tasks, artifacts and datasets.
A measurable outcome. The unit a human and an agent are both pointed at, and the natural place to attach progress. Progress can be typed in, or read from a dataset.
A unit of requested work assigned to a human or an agent. Same row, same audit. A task is not a conversation — it may span several topics and several runs.
Durable, rendered, pinnable content. One row per logical thing, with published versions. An artifact outlives the topic that produced it.
A validated, parameterised query over platform data. Never a SQL string. Executed as the viewer, so a report stays correct for every person who opens it.
Artifacts, objectives, tasks and datasets are organization-owned. Only a pin is scope-specific — and a pin is placement, never an access grant.
A canvas is where content is authored. An artifact is what survives. A pin is where it is placed. Each has a different lifetime, and the chain between them is strict.
| Concept | Lifetime | What it means | What it is not |
|---|---|---|---|
| Canvas | Topic-scoped, scratch | The persistent state of a room while work is in progress, with versions produced by events. | Not pinnable. It is working state with a working title. |
| Artifact | Durable, versioned | A logical thing — a report, a view, a document — that can be published repeatedly. | Not a canvas row. If it were, it would inherit the canvas's scratch lifetime. |
| Pin | Placement only | A sidebar position at personal, room, team or organization scope. | Not an access grant, and not a copy of the artifact. |
Humans and agents are both addressable senders with audit records. They do not share permissions. That distinction is the single most important line in the design.
User.Resolution is one function with three ordered rules. Nothing about it is stored, so it cannot drift from membership.
agent.manage.A run triggered by an event covers "someone caused this". It does not cover "nobody was here". So a scheduled, event-bound or objective-bound trigger is an explicit row — and it is deliberately one hop only.
Chains are what turn a helpful agent into an unbounded bill. Delegation beyond one hop needs an explicit human task. Design rule, section 4.10