From a 211-page PDF to a governed measure system.
This page shows what was actually produced from the 2026 technical notes and compares that output footprint to both a conservative manual-only baseline and a modeled AI-led review workflow. It is meant for team communication, not for claiming audited AI labor savings.
Output footprint
These numbers come from the repo artifacts themselves. They describe the scope of the package that was produced, not a theoretical future state.
Manual-only vs AI-assisted workflow
The point is not that the AI lane removes human review. The point is that it compresses the slowest parts of source digestion, cross-checking, normalization, and communication artifact creation.
What the assisted workflow actually enabled
Manual baseline vs AI-led team-touch
Read these together. The left side shows the modeled manual-only effort to reproduce the same footprint by hand. The right side shows the modeled human review, correction, and packaging effort in an AI-led workflow. Both are models, not audited timesheets.
If one person reproduced the footprint by hand
If AI does first-pass structure and humans review
Why the manual estimate is conservative
What the AI-led model is actually estimating
Observed artifact window
This is elapsed calendar time across the artifacts that exist in the repo. It is not a claim about active labor hours.
Use this as an output window, not a utilization metric
Credibility guardrails
The goal is to help the team communicate velocity honestly: ambitious enough to show the leverage, disciplined enough to avoid hype.
What we can credibly claim
- A 211-page source package was turned into a governed workbook, linked docs, and an interactive explainer.
- The manual baseline is modeled from pages, measure families, and packaging work, not guessed from intuition.
- The workflow was AI-assisted with human review and correction loops.
What we should avoid claiming
- Do not claim exact AI hour savings without human touch-hour tracking.
- Do not present the artifact window as active labor time.
- Do not present this as zero-touch automation or full app delivery.