System design

How the architecture holds its boundary

A production system is defined by what it refuses as much as what it accepts. Replace a scattered creator stack with one inspectable record while keeping the Name, exports, approvals, and deal history under the creator’s authority.

Control planes

The Name

The Name is the identity and ownership anchor; domain and public Nameplate bind every room.

Seven connected rooms

Seven rooms share one workspace record: Nameplate, Site, Mail, Posts, Assists, Press kit, and Deals.

Durable publishing pipeline

A durable scheduler and adapter boundary press approved content to channels and record receipts.

Request lifecycle

creator-owned Name and workspace
  → draft or imported source material
  → budget and policy check
  → human approval where required
  → durable scheduled job with jittered retry
  → channel adapter result and cryptographic receipt

Failure model

Invalid schedules, exceeded AI budgets, missing consent, stale revisions, provider failures, and duplicate delivery remain explicit workflow states.

Verification checklist

Domain-first ownership: The creator is the domain registrant and can transfer the Name.
Receipts for effects: Every publish attempt and external effect leaves a durable receipt.
Transactional AI budget: AI use reserves a transactional workspace budget before generation.
Truthful capability state: Pre-launch, preview, local-only, and blocked capabilities are labelled rather than fabricated.

← Back to overview