◇ Public progress report
YOUR PROJECTS. ONE CLEAR PICTURE.

Your portfolio, in focus.

A clear view of what’s moving, what needs you, and what comes next.

Reading your project snapshot…Based on pinned Codex chats

Pinned projects

Open a project for its goals, tasks, and plan.

READY FOR PAYING CUSTOMERS

Readiness needs evidence.

The main score assesses each project's defined first customer release. It is separate from the percentage of tracked milestones completed.

Scope 20 · Experience 25 · Reliability 20 · Operations 15 · Acceptance 20

A passed gate earns its full weight; partial evidence earns half. Blocked and unknown gates earn zero. The score is an assessment rubric, not a probability of success or a measure of code completed.

A release is ready only when all five gates pass and no critical blocker remains. A high score cannot override an open security, physical, commercial or customer-acceptance gate.

Internal foundations and companion workstreams are labeled separately. They do not create additional sellable products. Milestone percentages remain available as a secondary progress measure.

Effort ranges assume 6–8 focused hours per workday with the relevant skills. Approvals, procurement, observation periods and customer availability add elapsed time. The release plan keeps at most two principal efforts active.

Hourly reviews run from this Mac when it is awake and Codex is available. The last-check time is shown on the page; an overdue review is never presented as live data.