Vertical customer lifecyclelifecycle rail
- apply → approve → subscribe → provision → credits → access
- Keyed on (tenant, vertical) — one service, three verticals
- Engine create-or-resolve-by-email seam #120 deployed
How founder-owned products sit on the Seitiate+ business layer, with the engine, the trust layer, and the brain underneath. One picture of the architecture these pages are describing.
Each is an independent product home. The platform is neutral and horizontal — it serves whoever brings serious work through a thin contract.
↓ ↓ ↓thin HTTP seams · products reach the substrate over contracts, never by import
The layer that turns a product surface into a business: billing, credits, access, revenue-share, legal-entity ownership, and the graduation path. The engine runs the product; Notary vouches for trust; Seitiate+ runs the business.
The destination: a founder brings real work, and it can run, take payment, and grow on shared rails. The first path is concierge onboarding; the self-serve machine comes later.
↓ ↓ ↓bridge-not-rewrite · products consume seams over HTTP, never co-build in the engine
Three repos underneath the harbor. The engine runs the agent loop; the trust layer attests what runs; the brain holds institutional memory. None are vertical-specific — they serve whoever attaches.
Harness control plane, talent registry, agent runtime. Codex (memory) · Canon (taste) · Governor (quality, two-layer) · crystallization→seity loop · Society of Thought · LLM orchestrator (9+ BYOK providers).
Elixir foundation: the forward engine core loop — session → signed memory → export → offline verify → retrieval. Integration target, not architecture hope.
Trust backbone through the entire skill lifecycle: risk classification · sandboxing · certification gauntlet · ES256 attestation machinery · provenance chain.
Also the slop filter at vertical intake — the same certification that vets a skill vets a vertical (mechanical → risk-classify → intent check → sandbox → Governor). AI authorship is fine and expected (90%+ of repos); what we filter is slop, not AI. Load-bearing when hosting third-party verticals — "we run real businesses, so what runs is vetted."
Coordination, knowledge, memory, operational tooling. Memo→merge pipeline · task board · agent fleet coordination · NotebookLM institutional memory.
Agentic Contract-CI lives here: governed merge path with independent LLM review, Tier-2 hold, phone approval, audit events — the builder-side proof the substrate governs our own agents.
Serves all verticals; never the Sakme / Sensarra runtime surface.
The seity — accumulated, non-clonable steering judgment bonded to the human, portable across runtimes. We persist the human; we don't ship the agent runtime.
Neutrality — a third party attests what a platform-owner cannot attest for itself.
The provenance stamp that travels — engine-side verification works now; neutral Notary receipts are the next trust-root ceremony. That is the flank.
The intake filter — the same Notary gauntlet that vets a skill vets a vertical before it runs. AI authorship is expected; slop is refused. The economics finish the job: every sandbox run costs the founder real SEIT credits.
We never create verticals — founders do.
A vertical exists only when a real person owns it (their IP, their work, their revenue). Manufacture one ourselves to chase a market and we have rebuilt Sensarra — our thing to operate, not a founder's work on our platform. That is the anti-pattern. We are the harbor; we are never the fleet.