SYSTEM ATLAS / GOVERNED CONTINUITY
SemeAI is the continuity layer around intelligent work: context is admitted, evidence is assembled, a candidate approaches an independent Gate, and linked receipts preserve what happened.
SYSTEM POSITION01 / RELEASE FIELD
01PUBLIC ORIENTATION
The Release Field explains the system and exposes real entry paths. It can guide attention, but it cannot release a candidate or admit evidence.
02RELEASE AUTHORITY
The real Gate returns SHOW, REVIEW, or BLOCK while canonical runtime states remain PROCEED, NEEDS_REVIEW, and SILENCE. Only an admitted exact candidate may cross.
03BOUNDED INSTRUMENT
The Benchmark inspects seven fixed public repository signals, produces a deterministic bounded result, and retains a local presentation receipt. Its Gate controls display only.
04ADMITTED CONTINUITY
Genesis, the Engineering Book, and Research connect admitted chronology, implementation method, and claim limits. Commits are evidence; public posts are idea trace; neither proves the other.
05GOVERNED CONTEXT
Supabase identity and PostgreSQL RLS protect the private threshold. SemeAI Local connects evidence, memory, timeline, graph, Gate, and receipts. Axiom Seed witnesses a repository on loopback.
PRODUCT STATE / NO FICTION
Lifecycle labels describe product availability. They never replace Gate states or grant release authority.
01 / RELEASE CONTROL
Map one bounded AI workflow from generation to a real release decision and linked receipt.
02 / EVIDENCE
Inspect seven visible signals without turning a score into intelligence, safety, or readiness.
03 / IDENTITY
A real authenticated context protected by identity and PostgreSQL RLS, with honest empty states.
04 / ONE REAL LOOP
A private orchestration surface joining a real Benchmark receipt to an exact production Gate decision.
05 / LOCAL EMBODIMENT
A loopback repository witness that validates real Benchmark receipts and never becomes Gate.
06 / CONTINUITY STUDIO
TESSER is the public-source local runtime for private retrieval, Ollama candidates, governed release, receipts, and bounded execution.
07 / HISTORY + METHOD
Admitted history, engineering rationale, public experiments, and explicit non-claims.
08 / GOVERNED INTERFACE
A route-aware evidence interface is designed, but SDK and runtime admission remain ahead.
09 / METHODS
Two evidence-backed method candidates. Zero admitted or installable skills.
10 / DISTRIBUTION HYPOTHESIS
Held until acquisition, compatibility, versioning, evaluation, seller identity, and admission gates exist.
WHY THIS MATTERS FOR ADVANCED AGENTS
SemeAI does not solve AGI. It builds the inspectable substrate an advanced agent would need: admitted context, evidence lineage, candidate/release separation, execution accountability, and continuity that survives a single session.
CHOOSE A REAL ENTRY