Judge every overnight change against this direction before shipping.
Alabobai operating goal
Build the company that produces.
The standard is not a prettier SaaS homepage. The standard is a user-ready Digital Production System: trusted, cinematic, proof-backed, self-healing, and strong enough to be evaluated like core company infrastructure.
Judge every overnight change against this direction before shipping.
Judge every overnight change against this direction before shipping.
Judge every overnight change against this direction before shipping.
Continuous work loop
One highest-leverage improvement per run.
The loop should not spray random polish across the site. It should identify the most damaging weakness, fix it properly, verify it, and leave the next run smarter.
Audit the weakest surface
Start from user trust, product clarity, visual authority, proof, conversion, and technical reliability. Pick the one target with the highest leverage.
Replace claims with production
Every improvement must show Alabobai doing work: command, decomposition, browser or build action, approval checkpoint, output, and receipt.
Raise the visual standard
Neutral readable text, preserved rose-gold material, cinematic layout, disciplined whitespace, responsive polish, and no generic SaaS drift.
Verify before the next run
Typecheck, visual QA, route checks, motion guardrails, screenshot review, and a written receipt of what changed and what remains.
Hard gates before anything ships.
These are the rules that keep Alabobai from drifting into cheap SaaS presentation, empty spectacle, or unsupported authority.
No brown body text. No orange drift.
Rose gold is a material, not a paragraph color. The interface must feel like Alabobai, not a template with metallic paint.
Finished output must be visible.
The site should not explain autonomy in abstract language. It should show Alabobai producing documents, code, sites, research, media, approvals, and receipts.
No fake metrics or unsupported proof.
If a number, badge, testimonial, or enterprise claim cannot be substantiated, it does not ship. Authority comes from receipt-backed work.
Wake up to receipts, not promises.
The overnight system must leave visible work: committed improvements, screenshots, QA output, remaining risks, and the next best target.