Alabobai publishes evidence by lane: model execution, account persistence, payment recovery, receipt readiness, configured services, and formal claims that wait for production receipts.
Private early access for founders, operators, and executive teams.
alabobai.ai
Production surfaceSystem Status
01
Intent
The request is translated into a route.
02
Evidence
Sources, constraints, and risks are separated.
03
Output
The next production action is made visible.
8Operational probes
RecoveryPayment mode
OnReceipt capture
Live readiness probe
Deployment inputs are checked with receipt-level accuracy.
Model execution
ConfiguringOpen-weight or approved model lane required.
Public preview
ConfiguringPublic command previews must render without claiming fake completion.
Account persistence
ConfiguringSupabase-backed account history, productions, artifacts, and receipts.
Email delivery
ConfiguringContact intake falls back to mailto if delivery is not configured.
Commerce automation
ConfiguringCheckout uses recovery until automated payment is cleared.
Payment recovery
Configuring/checkout/recover?plan=starter
Payment confirmation
ConfiguringWebhook route pending — payment confirmation still being verified.
Welcome path
ConfiguringCheckout success route: /welcome
Launch blocker receipt
Checking deployment readiness…
Paddle checkout stays in recovery mode until live checkout, prices, credentials, and entitlement confirmation are verified. Enterprise compliance claims stay evidence-gated until formal receipts exist.
Public websiteLocal build, route, link, render, and screenshot checks passed. External uptime monitoring is tracked as a separate evidence lane.Locally verified
Command intakePublic preview intake is wired. Paid saved production connects authenticated entitlement and persistence.Locally verified
Receipt surfacesPublic receipt pages and local render evidence exist. Private account history uses configured storage and sign-in.Locally verified
Live external monitoringThird-party uptime/SLA monitoring becomes public after production probes are wired and visible.Evidence-gated
Payment automationAutomated checkout requires live payment clearance, active prices, and entitlement confirmation. Until then buyers use recovery without a fake checkout.Setup required
Payment recoveryCheckout recovery gives buyers a clear payment-request path, no fake checkout, and protection from dead payment screens.Locally verified
Enterprise complianceSOC 2, HIPAA, ISO, and uptime SLA language appears only after formal verification receipts exist.Evidence-gated
Readiness values come from /api/ready and local QA receipts. Live uptime probes publish after production monitoring is wired.
