Book 1 Digital
An interactive digital companion to AI Workflow Foundations, turning a downloadable workbook into a stateful web product with guided completion, saved inputs, export behaviour and privacy-aware pilot feedback.
- Role
- Product design, build orchestration, QA and pilot design
- State
- Controlled-pilot build deployed
- Proof
- Deployed controlled-pilot build
Why this deserved a product
A static workbook can explain a method, but it cannot preserve progress, generate usable outputs, support structured reflection or reveal where readers struggle during a pilot.
Keep the book’s learning sequence intact while adding only the product mechanics that increase completion and evidence: persistence, carry-forward drafts, artifact generation, effort cues and controlled pilot instrumentation.
How the system behaves
The useful part is the operating sequence—not the screen alone.
- 01
Guide readers through the Week 1 learning sequence.
- 02
Persist inputs and completion state between sessions.
- 03
Generate reusable product artifacts from workbook responses.
- 04
Support print/export without exposing editing controls.
- 05
Collect limited pilot feedback with explicit privacy copy.
Trade-offs made explicit
Each build is a negotiation between competing forms of value.
Screens from the build itself
Real product surfaces are included where public sharing is possible.
These screens show the current product state being referenced on this page. They support the product record but do not, on their own, claim user or business outcomes.
Technical surface
Stack
The evidence below separates implemented product state, supporting artifacts and proof that is still pending.
Evidence ledger
What exists, what it supports and where the claim stops.
Deployed interactive workbook
- Claim supported
- The publication has been converted into a browser-based product with persistent learner interaction.
- Evidence detail
- The Week 1 experience is deployed on Cloudflare Pages with guided inputs, saved progress and export behaviour.
- Source
- Live application and production deployment
Controlled pilot instrumentation
- Claim supported
- The build contains an explicit feedback and QA layer rather than relying on informal comments.
- Evidence detail
- Pilot instrumentation, privacy copy and a dedicated pilot-QA route were completed through the M5F passes.
- Source
- M5F-5 to M5F-7 release packages and deployed pilot-QA route
Release trail and source integrity
- Claim supported
- The build evolved through controlled, separately packaged increments rather than one untracked prototype.
- Evidence detail
- Print export, artifact regeneration, portfolio curation, carry-forward drafts, effort cues, instrumentation, privacy and QA were handled as named passes.
- Source
- Versioned clean-source packages and SHA-256 records
Learning and completion findings
- Claim supported
- Pilot results are still required before making claims about completion, learning quality or artifact usefulness.
- Evidence detail
- The next evidence layer is a pilot report connecting observed behaviour to release decisions.
- Source
- Planned controlled-pilot analysis
From intent to working state
A build becomes credible through the sequence of decisions it survives.
- 01 Publication baselineComplete
AI Workflow Foundations completed as a downloadable workbook.
- 02 Digital conversionComplete
Stateful Week 1 web experience, persistence and export implemented.
- 03 Pilot readiness passesComplete
Instrumentation, privacy copy and pilot QA completed through M5F-7.
- 04 Controlled pilotActive
The deployed build is ready for structured learner testing.
- 05 Pilot learning reportNext
Completion, drop-off and artifact-quality findings remain pending.
Where the product is now
The controlled-pilot build is deployed and ready for structured learner testing; the next step is to convert pilot observations into release decisions.
- 01Pilot completion and drop-off findings
- 02Before/after artifact examples
- 03Release 1 learning-outcome report
Continue exploring