00
The Governance Gap

AI builds fast.
Nobody documents what it decided.

Every AI coding tool makes dozens of business decisions silently. Database schema, auth model, billing logic, notification timing — all chosen by an AI that never asked you. SpecFactory captures those decisions before a single line of code exists.

Same product. Different outcomes.

An HOA violation management platform — built two ways.

typical_ai_build.log
$ "Build an HOA violation platform with automated notifications"
PostgreSQL with user_violations tableASSUMED
Auto-fine after 48 hours of non-complianceASSUMED
Email-only notifications, no SMSASSUMED
Single-tenant, shared databaseASSUMED
JWT auth, 24hr expiry, no role hierarchyASSUMED
No appeal process for violationsASSUMED
Violation photos in public S3 bucketASSUMED
7 business decisions. 0 confirmed by a human.
spec-output — Business Rules
After structured decision extraction with the founder:
72-hour warning window before escalationCONFIRMED
Fines require board vote — no auto-fineCONFIRMED
SMS + email, owner preferenceCONFIRMED
Multi-tenant with RLS, each HOA isolatedDERIVED
Board > Manager > Inspector > ResidentCONFIRMED
30-day appeal window, written submissionCONFIRMED
Private storage, signed URLs, 90-day retentionDERIVED
Violation expiration policyGAP — needs board input
6 CONFIRMED
2 DERIVED
1 GAP
01
3 Months Later

Something breaks. Who decided this?

"Why does our system auto-fine residents after 48 hours?"

without_specfactory.log
$ grep -r "auto_fine" src/
Found in: services/violations.ts:47
// handles violation escalation
No documentation found.
No decision record found.
Who decided this? Unknown.
The AI decided. Six months ago. Nobody recorded it.
spec-output — Decision #14
Decision extraction · Violation Escalation
Fines require board vote — no auto-fineCONFIRMED
Origin: Founder decision, March 2026
Rationale: "Board liability — auto-fines
expose us to legal challenge"
✓ Cross-verified in security requirements
Human decided. Documented. Traceable. Auditable.
02
The Output

Not documents. A build-ready repository.

The spec package is a git repository a developer (or AI) can clone and immediately start building from. Foundation documents, operating rules, build sequence, and project structure assembled and ready.

spec-package/
📁 docs/foundation/
├── Architecture decisions← Founder-confirmed
├── Business rules & domain logic← Founder-confirmed
├── Compliance requirements← Founder-confirmed
├── Security hardening spec← Founder-confirmed
📁 skills/
├── Trigger files + reference docs← Derived
📁 tasks/
├── Build sequence & status tracking← Generated
📁 Operating rules & constraints← Assembled

Your decisions deserve documentation.

The decisions you make tomorrow are already more valuable than the code AI writes today.

Join the Waitlist