← Independent product builds
03Interactive workbook · publication-to-product conversion

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
01 Problem

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.

Product decision

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.

02 Product mechanism

How the system behaves

The useful part is the operating sequence—not the screen alone.

  1. 01

    Guide readers through the Week 1 learning sequence.

  2. 02

    Persist inputs and completion state between sessions.

  3. 03

    Generate reusable product artifacts from workbook responses.

  4. 04

    Support print/export without exposing editing controls.

  5. 05

    Collect limited pilot feedback with explicit privacy copy.

03 Product tensions

Trade-offs made explicit

Each build is a negotiation between competing forms of value.

01 Guidance cognitive overload
02 Instrumentation learner privacy
03 Editable work trustworthy completion states
04 Zero-cost hosting backend capability
04 Working surfaces

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.

Book 1 Digital Week 1 preview page showing the workbook sales and preview landing page with benefits, privacy notes and call to action.
Week 1 preview and onboarding surface showing the workbook-to-product conversion in its deployed form.
05 Build and evidence

Technical surface

Stack

ReactViteCloudflare PagesCloudflare WorkersD1
Current proof position Deployed controlled-pilot build

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.

Verified state Available artifact Planned proof
01
Working product Verified state

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
Open live workbook
02
Pilot evidence Verified state

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
Open pilot QA
03
Release evidence Available artifact

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
04
Outcome evidence Planned proof

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
06 Release trail

From intent to working state

A build becomes credible through the sequence of decisions it survives.

  1. 01
    Publication baseline

    AI Workflow Foundations completed as a downloadable workbook.

    Complete
  2. 02
    Digital conversion

    Stateful Week 1 web experience, persistence and export implemented.

    Complete
  3. 03
    Pilot readiness passes

    Instrumentation, privacy copy and pilot QA completed through M5F-7.

    Complete
  4. 04
    Controlled pilot

    The deployed build is ready for structured learner testing.

    Active
  5. 05
    Pilot learning report

    Completion, drop-off and artifact-quality findings remain pending.

    Next
07 Current state

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.

Next evidence to add
  1. 01Pilot completion and drop-off findings
  2. 02Before/after artifact examples
  3. 03Release 1 learning-outcome report

Continue exploring

Other independent builds