Launch evidence ledger
Every launch blocker mapped to evidence.
A B2B launch review needs one artifact that says what evidence is missing, where it must be attached, and which claim remains blocked. This ledger turns the launch gap register into proof records with explicit acceptance rules.
32
open evidence records
2
operator-run records
6
fixture-output records
6
customer-acceptance records
Launch-mode evidence
The mode is only as strong as its attached proof.
Each launch motion lists the evidence records and attachment targets that must be accepted before buyer, paid-beta, self-serve, or enterprise wording can move forward.
conditional
Managed private beta
Managed private beta remains conditional until 17 evidence records are attached, accepted, or moved into signed exclusions.
Attachment targets: /api/platform/launch-room; /tmp/thesmios-launch-proof-bundle.json; Approved vendor console evidence or explicit signed exclusion; /api/product/production-proof; Signed order-form exclusions section.
Evidence records: 17
conditional
Invoice-led paid beta
Invoice-led paid beta remains conditional until 20 evidence records are attached, accepted, or moved into signed exclusions.
Attachment targets: /api/platform/launch-room; /tmp/thesmios-launch-proof-bundle.json; Approved vendor console evidence or explicit signed exclusion; /api/product/production-proof; Signed order-form exclusions section.
Evidence records: 20
blocked
Self-serve paid launch
Self-serve paid launch remains blocked until 24 evidence records are attached, accepted, or moved into signed exclusions.
Attachment targets: /api/platform/launch-room; /tmp/thesmios-launch-proof-bundle.json; Approved vendor console evidence or explicit signed exclusion; /api/product/production-proof; /api/platform/billing-evidence; Signed order-form exclusions section.
Evidence records: 24
blocked
Broad enterprise expansion
Broad enterprise expansion remains blocked until 26 evidence records are attached, accepted, or moved into signed exclusions.
Attachment targets: /api/platform/launch-room; /tmp/thesmios-launch-proof-bundle.json; Approved vendor console evidence or explicit signed exclusion; /api/product/production-proof; Signed order-form exclusions section.
Evidence records: 26
Evidence records
| Gap | State | Attachment target | Acceptance rule | Required attachments | Blocked claims |
|---|---|---|---|---|---|
| Authenticated tenant access proofmanaged-authenticated-access - Operator - p1_paid_launchBlocks: Managed private beta; Invoice-led paid beta; Self-serve paid launch; Broad enterprise expansion | Needs customer acceptance | /api/platform/launch-room | Attach customer approval, owner, accepted stage, and scoped exclusions for Authenticated tenant access proof in the launch room. | /api/platform/launch-room; Attach access-control pass output before claiming tenant isolation is proven for the launch tenant.; CONFIRM_LAUNCH_OPERATOR_SEED=thesmios-launch-seed run output; Owner, granted-employer, and denied-employer smoke results; +6 more | Private demo can continue, but a customer tenant cannot be accepted as live.Claim IDs: claim-invoice-billing; claim-vc-issuer; claim-audit-exports; claim-evidence-scanning; claim-status-broadcast; claim-passkeys |
| Credential and evidence sample proofmanaged-credential-evidence - Operator - p1_paid_launchBlocks: Managed private beta; Invoice-led paid beta; Self-serve paid launch; Broad enterprise expansion | Needs customer acceptance | /api/platform/launch-room | Attach customer approval, owner, accepted stage, and scoped exclusions for Credential and evidence sample proof in the launch room. | /api/platform/launch-room; Attach sample credential, evidence, audit export, and privacy fixture output for the tenant or scoped pilot cohort.; check:issuer-fixture output when issuer keys and auth fixtures are configured; check:evidence-fixture output when job runner secret is configured; +6 more | Do not claim production credential signing, evidence controls, audit export, or privacy fulfilment as buyer-accepted.Claim IDs: claim-invoice-billing; claim-vc-issuer; claim-audit-exports; claim-evidence-scanning; claim-status-broadcast; claim-passkeys |
| Evidence scanning, audit export, and data-rights fixturesvendor-evidence-operations - Operator - p1_paid_launchBlocks: Invoice-led paid beta; Self-serve paid launch | Needs fixture output | /tmp/thesmios-launch-proof-bundle.json | Attach passing proof output for Evidence scanning, audit export, and data-rights fixtures before allowing the affected launch modes. | /tmp/thesmios-launch-proof-bundle.json; Evidence, audit-export, and privacy fixture output references recorded against the tenant launch room.; THESMIOS_AUTH_SMOKE_PASSWORD; THESMIOS_TEST_SUBJECT_ID; +6 more | Buyer-accepted malware/quarantine proof before evidence fixture output.; Buyer-accepted audit exports before export fixture output.; Buyer-accepted data-rights fulfilment proof before privacy fixture output.Claim IDs: claim-invoice-billing; claim-right-to-work; claim-vc-issuer; claim-audit-exports; claim-evidence-scanning; claim-status-broadcast; claim-passkeys |
| Operator environment preflightproof-operator-env-preflight - Operator - p1_paid_launchBlocks: Managed private beta; Invoice-led paid beta; Self-serve paid launch; Broad enterprise expansion | Needs operator run | /tmp/thesmios-launch-proof-bundle.json | Attach passing proof output for Operator environment preflight before allowing the affected launch modes. | /tmp/thesmios-launch-proof-bundle.json; Attach the preflight output showing every required operator/fixture variable group is ready before any mutating production proof run.; Locked operator env file with usable LAUNCH_OPERATIONS_SECRET or AUDIT_ADMIN_SECRET; Supabase public config and authenticated smoke fixture variables; +6 more | Do not run operator seeding or fixture proof from this shell; retrieve real secret values from the operator password manager or approved vendor console.Claim IDs: claim-invoice-billing; claim-vc-issuer; claim-evidence-scanning; claim-status-broadcast; claim-passkeys |
| Operator launch seedproof-launch-seed - Operator - p1_paid_launchBlocks: Managed private beta; Invoice-led paid beta; Self-serve paid launch; Broad enterprise expansion | Needs operator run | /tmp/thesmios-launch-proof-bundle.json | Attach passing proof output for Operator launch seed before allowing the affected launch modes. | /tmp/thesmios-launch-proof-bundle.json; Attach returned subject, credential, workflow task, passport share, and smoke actor references in the operator launch record.; CONFIRM_OPERATOR_LAUNCH_PROOF; LAUNCH_OPERATIONS_SECRET or AUDIT_ADMIN_SECRET; +6 more | Strict readiness cannot prove RLS or authenticated role separation on production data.Claim IDs: claim-invoice-billing; claim-vc-issuer; claim-evidence-scanning; claim-status-broadcast; claim-passkeys |
| Support and status notification proofproof-notifications - Operator - p1_paid_launchBlocks: Managed private beta; Invoice-led paid beta; Self-serve paid launch; Broad enterprise expansion | Needs fixture output | /tmp/thesmios-launch-proof-bundle.json | Attach passing proof output for Support and status notification proof before allowing the affected launch modes. | /tmp/thesmios-launch-proof-bundle.json; Attach subscriber intake, dry-run broadcast, support request lifecycle notification attempts, and controlled test-recipient delivery output.; RESEND_API_KEY; STATUS_BROADCAST_SECRET; +6 more | Keep support/status email as dry-run or retained-attempt evidence and use manual customer communication for launch.Claim IDs: claim-invoice-billing; claim-dbs-update-service; claim-vc-issuer; claim-audit-exports; claim-evidence-scanning; claim-status-broadcast; claim-passkeys |
| Support emailstrict-support-email - Operator - p1_paid_launchBlocks: Managed private beta; Invoice-led paid beta; Self-serve paid launch; Broad enterprise expansion | Needs vendor setup | Approved vendor console evidence or explicit signed exclusion | Attach vendor credential setup, controlled fixture output, or explicit signed exclusion for Support email. | Approved vendor console evidence or explicit signed exclusion; Attach subscriber intake, dry-run broadcast, support request lifecycle notification attempts, and controlled test-recipient delivery output.; RESEND_API_KEY; STATUS_BROADCAST_SECRET; +6 more | Accepted customer tenant; Invoice-led paid beta without fixture proof |
| Audit export package proofproof-audit-export - Security - p1_paid_launchBlocks: Managed private beta; Invoice-led paid beta; Self-serve paid launch; Broad enterprise expansion | Needs fixture output | /api/product/production-proof | Attach passing proof output for Audit export package proof before allowing the affected launch modes. | /api/product/production-proof; Attach denied-access, queued-job, generated-package, and signed-download output.; NEXT_PUBLIC_SUPABASE_URL; NEXT_PUBLIC_SUPABASE_ANON_KEY; +6 more | Do not claim buyer audit export evidence is proven on production data.Claim IDs: claim-audit-exports |
| Authenticated access and RLS proofproof-authenticated-access - Security - p1_paid_launchBlocks: Managed private beta; Invoice-led paid beta; Self-serve paid launch; Broad enterprise expansion | Needs fixture output | /api/product/production-proof | Attach passing proof output for Authenticated access and RLS proof before allowing the affected launch modes. | /api/product/production-proof; Attach the pass count proving owner, granted-employer, and denied-employer outcomes.; NEXT_PUBLIC_SUPABASE_URL; NEXT_PUBLIC_SUPABASE_ANON_KEY; +6 more | Do not claim production tenant isolation or verifier access control has been proven.Claim IDs: claim-worker-compliance-passport; claim-right-to-work |
| Authenticated smoke fixture recordsstrict-authenticated-smoke-fixture-records - Security - p1_paid_launchBlocks: Managed private beta; Invoice-led paid beta; Self-serve paid launch; Broad enterprise expansion | Needs fixture output | /api/product/production-proof | Attach passing proof output for Authenticated smoke fixture records before allowing the affected launch modes. | /api/product/production-proof; Attach the pass count proving owner, granted-employer, and denied-employer outcomes.; data_sets; data_set_records; +6 more | Accepted customer tenant; Invoice-led paid beta without fixture proof |
| Evidence file controls proofproof-evidence-controls - Security - p1_paid_launchBlocks: Managed private beta; Invoice-led paid beta; Self-serve paid launch; Broad enterprise expansion | Needs fixture output | /api/product/production-proof | Attach passing proof output for Evidence file controls proof before allowing the affected launch modes. | /api/product/production-proof; Attach clean, suspicious, infected, quarantine, and retention proof output.; NEXT_PUBLIC_SUPABASE_URL; NEXT_PUBLIC_SUPABASE_ANON_KEY; +6 more | Private beta can use the policy scanner, but enterprise file-control proof remains incomplete. |
| Issuer signing proofproof-issuer-signing - Security - p1_paid_launchBlocks: Managed private beta; Invoice-led paid beta; Self-serve paid launch; Broad enterprise expansion | Blocked until external | Approved vendor console evidence or explicit signed exclusion | Attach vendor credential setup, controlled fixture output, or explicit signed exclusion for Issuer signing proof. | Approved vendor console evidence or explicit signed exclusion; Attach discovery responses plus signed VC-JWT and SD-JWT verification output.; NEXT_PUBLIC_SUPABASE_URL; NEXT_PUBLIC_SUPABASE_ANON_KEY; +6 more | Do not claim production credential signing is fully proven for a tenant.Claim IDs: claim-sso |
| Stripe self-serve billingstrict-stripe-self-serve-billing - Finance - p1_paid_launchBlocks: Self-serve paid launch | Needs vendor setup | /api/platform/billing-evidence | Attach passing proof output for Stripe self-serve billing before allowing the affected launch modes. | /api/platform/billing-evidence; Attach unsigned rejection, tampered rejection, and signed fixture event acceptance output.; STRIPE_SECRET_KEY; STRIPE_WEBHOOK_SECRET; +4 more | Self-serve checkout; Automated paid conversionClaim IDs: claim-stripe-self-serve |
| Stripe self-serve billingvendor-stripe-self-serve - Finance - p1_paid_launchBlocks: Self-serve paid launch | Needs vendor setup | /api/platform/billing-evidence | Attach passing proof output for Stripe self-serve billing before allowing the affected launch modes. | /api/platform/billing-evidence; Unsigned webhook rejection, tampered signature rejection, and signed fixture event acceptance.; STRIPE_SECRET_KEY; STRIPE_WEBHOOK_SECRET; +6 more | Public self-serve paid checkout.; Automated subscription lifecycle and webhook-driven paid activation.Claim IDs: claim-stripe-self-serve |
| Stripe self-serve billing proofproof-stripe - Finance - p1_paid_launchBlocks: Self-serve paid launch | Needs contract exclusion | Signed order-form exclusions section | Record Stripe self-serve billing proof as a signed order-form exclusion and mirror it in tenant launch acceptance before removing the blocker. | Signed order-form exclusions section; Attach unsigned rejection, tampered rejection, and signed fixture event acceptance output.; STRIPE_SECRET_KEY; STRIPE_WEBHOOK_SECRET; +6 more | Self-serve checkout; Card-backed activationClaim IDs: claim-stripe-self-serve |
| Privacy and data-rights proofproof-privacy-rights - Customer - p1_paid_launchBlocks: Managed private beta; Invoice-led paid beta; Self-serve paid launch; Broad enterprise expansion | Needs customer acceptance | /api/platform/launch-room | Attach customer approval, owner, accepted stage, and scoped exclusions for Privacy and data-rights proof in the launch room. | /api/platform/launch-room; Attach scoped export, access/export request, erasure request, and fulfilment decision output.; NEXT_PUBLIC_SUPABASE_URL; NEXT_PUBLIC_SUPABASE_ANON_KEY; +6 more | Do not treat DSAR and erasure fulfilment evidence as customer-accepted.Claim IDs: claim-right-to-work; claim-audit-exports |
| Vendor readiness evidenceproof-vendor-readiness - Customer - p1_paid_launchBlocks: Managed private beta; Invoice-led paid beta; Self-serve paid launch; Broad enterprise expansion | Needs customer acceptance | /api/platform/launch-room | Attach customer approval, owner, accepted stage, and scoped exclusions for Vendor readiness evidence in the launch room. | /api/platform/launch-room; Attach the vendor readiness JSON, smoke output, accepted customer exclusions, and any vendor-specific fixture output to the launch room.; RESEND_API_KEY and STATUS_BROADCAST_SECRET for customer notification proof; Stripe secrets and price IDs for self-serve checkout; +6 more | Keep missing vendor-backed automation out of the order form, or sell it only as managed/manual workflow with explicit customer acceptance.Claim IDs: claim-right-to-work |
| Official issuer connectorsvendor-official-issuer-connectors - Security - p2_enterpriseBlocks: Broad enterprise expansion | Blocked until external | Approved vendor console evidence or explicit signed exclusion | Attach vendor credential setup, controlled fixture output, or explicit signed exclusion for Official issuer connectors. | Approved vendor console evidence or explicit signed exclusion; Issuer fixture output plus authority-specific credential, consent, legal basis, and first customer lookup evidence.; HOME_OFFICE_RTW_API_KEY; UKVI_RIGHT_TO_WORK_API_KEY; +6 more | Live Home Office / UKVI checks without approved credentials and employee consent.; Live DBS Update Service checks without customer legal basis and API credentials.; Live E-Verify case submission without approval, MOU, certificates, and tenant credentials.Claim IDs: claim-companies-house; claim-right-to-work; claim-dbs-update-service; claim-e-verify; claim-sanctions-monitoring |
| Enterprise OIDC broker configstrict-enterprise-oidc-broker-config - Enterprise - p2_enterpriseBlocks: Broad enterprise expansion | Blocked until external | Approved vendor console evidence or explicit signed exclusion | Attach vendor credential setup, controlled fixture output, or explicit signed exclusion for Enterprise OIDC broker config. | Approved vendor console evidence or explicit signed exclusion; Attach IdP guide, token prefix, user/group create-read-update-deprovision output, and broker config decision.; ENTERPRISE_OIDC_ISSUER; ENTERPRISE_OIDC_CLIENT_ID; +5 more | Broad enterprise automation; Hands-off SSO/SCIM; Live HRIS or official issuer automationClaim IDs: claim-stripe-self-serve; claim-scim; claim-sso |
| Enterprise SAML IdP configstrict-enterprise-saml-idp-config - Enterprise - p2_enterpriseBlocks: Broad enterprise expansion | Blocked until external | Approved vendor console evidence or explicit signed exclusion | Attach vendor credential setup, controlled fixture output, or explicit signed exclusion for Enterprise SAML IdP config. | Approved vendor console evidence or explicit signed exclusion; Attach IdP guide, token prefix, user/group create-read-update-deprovision output, and broker config decision.; SAML_IDP_ENTITY_ID; SAML_IDP_SSO_URL; +5 more | Broad enterprise automation; Hands-off SSO/SCIM; Live HRIS or official issuer automationClaim IDs: claim-stripe-self-serve; claim-scim; claim-sso |
| Enterprise SSO and SCIM provisioningvendor-enterprise-identity - Enterprise - p2_enterpriseBlocks: Broad enterprise expansion | Blocked until external | Approved vendor console evidence or explicit signed exclusion | Attach vendor credential setup, controlled fixture output, or explicit signed exclusion for Enterprise SSO and SCIM provisioning. | Approved vendor console evidence or explicit signed exclusion; IdP setup guide, tenant token prefix, SCIM create/read/update/deprovision output, and SSO broker decision.; ENTERPRISE_OIDC_ISSUER; ENTERPRISE_OIDC_CLIENT_ID; +6 more | Broad enterprise self-serve SSO.; Hands-off SCIM provisioning across all IdPs.; Brokered SAML/OIDC production login before tenant IdP proof.Claim IDs: claim-stripe-self-serve; claim-scim; claim-sso |
| HRIS connector credentialsstrict-hris-connector-credentials - Enterprise - p2_enterpriseBlocks: Broad enterprise expansion | Blocked until external | Approved vendor console evidence or explicit signed exclusion | Attach vendor credential setup, controlled fixture output, or explicit signed exclusion for HRIS connector credentials. | Approved vendor console evidence or explicit signed exclusion; Attach IdP guide, token prefix, user/group create-read-update-deprovision output, and broker config decision.; WORKDAY_REST_BASE_URL; WORKDAY_ACCESS_TOKEN; +6 more | Broad enterprise automation; Hands-off SSO/SCIM; Live HRIS or official issuer automationClaim IDs: claim-right-to-work; claim-workday; claim-bamboohr; claim-scim; claim-sso |
| Official issuer connector credentialsstrict-official-issuer-connector-credentials - Enterprise - p2_enterpriseBlocks: Broad enterprise expansion | Blocked until external | Approved vendor console evidence or explicit signed exclusion | Attach vendor credential setup, controlled fixture output, or explicit signed exclusion for Official issuer connector credentials. | Approved vendor console evidence or explicit signed exclusion; Attach IdP guide, token prefix, user/group create-read-update-deprovision output, and broker config decision.; COMPANIES_HOUSE_API_KEY; HOME_OFFICE_RTW_API_KEY; +6 more | Broad enterprise automation; Hands-off SSO/SCIM; Live HRIS or official issuer automationClaim IDs: claim-companies-house; claim-dbs-update-service; claim-e-verify; claim-sanctions-monitoring; claim-scim; claim-sso |
| SCIM and enterprise SSO proofproof-scim-sso - Enterprise - p2_enterpriseBlocks: Broad enterprise expansion | Blocked until external | Approved vendor console evidence or explicit signed exclusion | Attach vendor credential setup, controlled fixture output, or explicit signed exclusion for SCIM and enterprise SSO proof. | Approved vendor console evidence or explicit signed exclusion; Attach IdP guide, token prefix, user/group create-read-update-deprovision output, and broker config decision.; THESMIOS_SCIM_TOKEN; ENTERPRISE_OIDC_ISSUER; +6 more | Broad enterprise SSO/SCIM; Hands-off provisioningClaim IDs: claim-scim |
| Self-serve and enterprise exclusionsmanaged-self-serve-enterprise-boundary - Enterprise - p2_enterpriseBlocks: Self-serve paid launch; Broad enterprise expansion | Needs contract exclusion | Signed order-form exclusions section | Record Self-serve and enterprise exclusions as a signed order-form exclusion and mirror it in tenant launch acceptance before removing the blocker. | Signed order-form exclusions section; List excluded claims in the order form and customer launch acceptance record.; Strict readiness passing; Stripe fixture proof before self-serve checkout; +6 more | Self-serve paid checkout; Broad enterprise SSO/SCIM; Official issuer automation without proofClaim IDs: claim-companies-house; claim-dbs-update-service; claim-e-verify; claim-sanctions-monitoring |
| HRIS source connectorsvendor-hris-connectors - Customer - p2_enterpriseBlocks: Broad enterprise expansion | Needs customer acceptance | /api/platform/launch-room | Attach customer approval, owner, accepted stage, and scoped exclusions for HRIS source connectors in the launch room. | /api/platform/launch-room; Customer sandbox import output, identifier reconciliation, and tenant launch dossier references.; WORKDAY_REST_BASE_URL; WORKDAY_ACCESS_TOKEN; +6 more | Live Workday sync before customer sandbox credentials and field mapping proof.; Live BambooHR sync before customer sandbox credentials and field mapping proof.Claim IDs: claim-workday; claim-bamboohr |
| Support and incident fallbackmanaged-support-incident - Operator - p3_customer_acceptanceBlocks: Managed private beta; Invoice-led paid beta; Self-serve paid launch; Broad enterprise expansion | Needs customer acceptance | /api/platform/launch-room | Attach customer approval, owner, accepted stage, and scoped exclusions for Support and incident fallback in the launch room. | /api/platform/launch-room; Attach support owner, escalation route, manual notice process, and dry-run broadcast output.; Named customer support owner; Manual incident communication channel; +6 more | Automated claim without accepted manual fallback |
| Support email and status broadcastsvendor-support-email - Operator - p3_customer_acceptanceBlocks: Invoice-led paid beta; Self-serve paid launch | Needs vendor setup | Approved vendor console evidence or explicit signed exclusion | Attach vendor credential setup, controlled fixture output, or explicit signed exclusion for Support email and status broadcasts. | Approved vendor console evidence or explicit signed exclusion; Status subscription/broadcast output, support notification fixture output, and manual follow-up evidence if email is skipped.; RESEND_API_KEY; Attach the launch proof bundle JSON with public checks passing and fixture-only checks skipped.; +6 more | Automated customer email acknowledgement before sender reputation and fixture delivery are proven.; Incident broadcast delivery to customer recipients before controlled notification proof. |
| Invoice or order-form billing routemanaged-invoice-billing - Finance - p3_customer_acceptanceBlocks: Invoice-led paid beta; Self-serve paid launch | Needs contract exclusion | Signed order-form exclusions section | Record Invoice or order-form billing route as a signed order-form exclusion and mirror it in tenant launch acceptance before removing the blocker. | Signed order-form exclusions section; Attach billing owner, PO terms, invoice contact, plan, seat cap, and renewal/cancellation terms.; Tenant billing profile saved as invoice-only or Stripe-ready; Purchase-order terms or invoice contact; +6 more | Automated claim without accepted manual fallback |
| Customer acceptance evidenceproof-customer-acceptance - Customer - p3_customer_acceptanceBlocks: Managed private beta; Invoice-led paid beta; Self-serve paid launch; Broad enterprise expansion | Needs contract exclusion | Signed order-form exclusions section | Record Customer acceptance evidence as a signed order-form exclusion and mirror it in tenant launch acceptance before removing the blocker. | Signed order-form exclusions section; Attach signer, accepted stage, scoped exclusions, evidence references, and external approval reference.; Signed order form or written approval reference; Customer-approved retention schedule; +6 more | Live tenant; Paid beta; Enterprise expansion |
| Customer acceptance recordmanaged-customer-acceptance - Customer - p3_customer_acceptanceBlocks: Managed private beta; Invoice-led paid beta; Self-serve paid launch; Broad enterprise expansion | Needs contract exclusion | Signed order-form exclusions section | Record Customer acceptance record as a signed order-form exclusion and mirror it in tenant launch acceptance before removing the blocker. | Signed order-form exclusions section; Attach the go/no-go decision before any paid or live production claim.; PATCH /api/platform/launch-acceptance output; Signer name, role, and approval reference; +6 more | Live customer tenant without signed acceptance |
| Customer order-form scopemanaged-customer-scope - Customer - p3_customer_acceptanceBlocks: Managed private beta; Invoice-led paid beta; Self-serve paid launch; Broad enterprise expansion | Needs contract exclusion | Signed order-form exclusions section | Record Customer order-form scope as a signed order-form exclusion and mirror it in tenant launch acceptance before removing the blocker. | Signed order-form exclusions section; Attach the signed order form or approval reference before moving the tenant beyond setup.; Signed order form or written approval reference; Approved worker cohort and compliance modules; +6 more | Live customer tenant without signed acceptance |
Operator handoff
Evidence has a home before the run starts.
The ledger mirrors the operator console outputs so proof files, fixture exports, launch rooms, and dossiers can be attached to the right acceptance record.
Locked operator preflight output: /tmp/operator-env-preflight.json Confirms the shell has usable seed, fixture, vendor, and strict paid-launch variables before mutation.
Launch seed fixture export: /tmp/thesmios-auth-smoke.env Carries generated subject, credential, workflow task, passport share, and smoke actor references without printing values.
Launch proof bundle: /tmp/thesmios-launch-proof-bundle.json One attachable record for public checks, authenticated fixtures, strict readiness, and skipped or blocked proofs.
Customer launch room and dossier: /api/platform/launch-room and /api/platform/launch-dossier?download=1 Customer-specific acceptance record for roles, billing, support, governance, continuity, fixture evidence, and exclusions.
Proof commands
The ledger is part of the launch bundle.
Launch evidence ledger smoke
Ledger page and JSON endpoint are deployed, public-safe, complete, and wired into launch proof bundles.
THESMIOS_SMOKE_URL=https://www.thesmios.com npm run check:launch-evidence-ledger
Launch proof bundle
One attachable evidence JSON covering public, authenticated, mutating, vendor, and strict readiness proof.
THESMIOS_SMOKE_URL=https://www.thesmios.com npm run check:launch-proof-bundle -- --include-fixtures --strict --env-file /tmp/thesmios-auth-smoke.env --output /tmp/thesmios-launch-proof-bundle.json
Tenant launch dossier
Authenticated tenant launch dossier route is protected and ready to package customer-specific acceptance evidence.
THESMIOS_SMOKE_URL=https://www.thesmios.com npm run check:tenant-launch-dossier
Boundaries
Evidence names are not evidence.
The ledger reports evidence names, attachment targets, proof commands, and blocked claims only; it never exposes secret values.
A ledger record is not accepted until the named proof output or customer approval reference is attached to the customer launch room or dossier.
External vendor credentials, customer signatures, and controlled fixture runs remain outside this public artifact.
Order-form exclusions are valid only when signed and mirrored in launch acceptance evidence.
/api/product/launch-evidence-ledger
/api/product/operator-launch-console
/api/product/launch-gap-register
/api/product/launch-claims-guard
/api/product/production-proof
/api/product/launch-clearance
/api/product/vendor-readiness
/api/product/customer-launch-room
/api/platform/launch-room
/api/platform/launch-dossier?download=1
/api/platform/external-evidence
/api/platform/billing-evidence
/api/platform/fixture-evidence
/api/platform/support-communications