Company Autopilot / public build record

The company that keeps working when I walk away.

I am documenting whether my agents can advance real company work during an eight-hour day away from the computer. The proof will include what shipped, what reached my phone, what failed, and what survived independent verification.

Eight hours away. Real work advances. My phone handles the exceptions.

01Native work

Real tasks enter from the systems that already own them.

02Bounded agents

Safe work advances in isolated lanes with explicit authority.

03Phone decisions

Only judgment, approval, and true exceptions reach me.

04Supported effects

Approved actions execute through the existing product or provider.

05Read-back

Receipts and an independent check decide whether the work counts.

A percentage that has to earn every point.

The sum of weights for completed milestones in the documented public-showcase journey. Work in progress earns zero points.

The percentage measures production of the public proof artifact. Operational acceptance stays binary.

Complete In progress Unstarted
01
Public showcase contractPR #129
10 pts
03
Living journey ledger and deterministic scoreSource ledger
5 pts
04
Reconciled rehearsal window
15 pts
05
Qualifying eight-hour operating day
25 pts
06
Sanitized evidence and redaction bundle
15 pts
07
Mobile public experience
15 pts
08
Reusable share package
5 pts
09
Verified public deployment
5 pts

Four systems worth seeing. None get promoted by a voice note.

Candidate 01

Video Review OS

A local clipping and review system with several clip modes, first-frame previews, transcripts, and searchable source material.

Candidate 02

An ad from one screenshot

A screenshot enters Kai Marketing OS. Codex and Kai turn the idea into the finished ad, including the video.

Candidate 03

LinkedIn auto-posting

The publishing system is running. Public proof still needs exact post receipts and external read-back.

Candidate 04

Daily system alerts

The systems report what changed. The accepted operating day must prove that those alerts produce the right decisions.

July 23, 2026

The shareability problem became concrete.

A friend sent me somebody else's AI dashboard and called it badass. I had built broader operating machinery, but nobody could inspect it in one place. The missing object was a public, proof-backed story.

Later that day, a voice note named the four candidate demos above. The next score change still requires a reconciled rehearsal. Writing more copy earns zero points.

Next checkpoint: a reconciled rehearsal window.

Inspect the contract ↗