Separate the stream from the state
The event log records what happened. Canvases, artifacts, tasks and pins are rebuildable projections of it — never the other way round.
Siteplan is a CMS and application foundation built on Django and Wagtail. It treats an AI agent as a first-class actor next to a human — sharing the same event stream, the same workspace and the same audit trail, while holding its own scoped authority.
One Django ASGI process · Postgres as truth · Redis for fan-out · HTMX and Alpine on the front end
Most "AI features" in business software are a sidebar: the agent cannot see the work, cannot act on it, and leaves no accountable trace. Siteplan starts from the opposite premise — the agent is an actor in the system, with identity, permissions, limits and an audit record.
The event log records what happened. Canvases, artifacts, tasks and pins are rebuildable projections of it — never the other way round.
Agents never authenticate, never receive staff flags and never hold a socket. They are invoked, checked at append time, and granted coarse, expiring capabilities.
A conversation ends. An artifact does not. Publishing promotes a canvas version into a pinned, refreshable, viewer-scoped report that outlives the topic that produced it.
The shell never becomes a wall of chat. Column one is where things live, column two is how work happens, and column three is what the work produced.
This is the acceptance scenario the whole design is written against. If a step needs a concept the domain model does not have, the model is wrong — not the scenario.
User, so assigning work to an agent is the same operation as assigning it to a colleague.ArtifactVersion and appends ARTIFACT_PUBLISHED. The canvas is not consumed, so refinement continues.Siteplan is installed on-premise and built as a foundation, not a hosted toy. The architecture is chosen so that the same application can run locally under a trusting administrator, in a sandbox, in a container, or on a remote VM — by policy, not by rewrite.
Agents are powerful because they are bounded. Every irreversible action is approval-gated, every run is attributed to a human owner, and every tool call passes through one mediated dispatch.
Read the visionThe actor model, the topic tree, the product layer, and the single loop that ties a request to a durable artifact.
Django ASGI, Channels, the append path, projections, the executor seam, and the two runtime families.
The versioned widget protocol, stable widget identity, i18n keys, data binding, and the reference scenario end to end.
Pluggable runtimes, policy-driven placement, governed dynamic apps, and the principles that decide every trade-off.