Genesis services are directly available. AI² can discover and compose them, but AI² is not required to use them. Start with the outcome you need; Genesis keeps availability, authority, execution and evidence as separate facts.
AI advises. Verification governs.
Genesis enforces execution authority structurally — not through runtime checks that can be bypassed. Governors define what an AI system may do. Anything outside the defined boundary is structurally impossible, not merely discouraged.
Execution authority →Every action that crosses an execution boundary produces a cryptographically receipted record. What the AI did, when, under what authority, with what outcome — established independently of the AI system that took the action.
Verify proof →Before an AI system resumes after an incident, Genesis establishes a verified clean state. Recovery is not restart — it is independent verification that the boundary conditions are satisfied and execution authority is intact.
Continuity →Universal Verifiable Effect Infrastructure: choose an assessment or a market-specific workflow, then inspect the existing Genesis services behind it.
These are scoped engagements and industry journeys, not claims that a third-party provider or entire product is production-ready. Each links to the canonical Genesis service surfaces.
One service identity · multiple projections · no AI² dependency
Public setup guidance only · no account or provider status is implied
Loading declared service setup options.
The public layer exposes outcomes, not internal machinery. A service may be discoverable without being executable; provider-backed effects still require the real connection, consent, authority and runtime. Missing dependencies remain missing.