# The IADVT framework on a real AEVUS project

Original AEVUS teaching walkthrough

## The project

AEVUS AI Playbooks learning release · November 15, 2026

A real AEVUS website project, mapped retrospectively to the IADVT framework. Filled documents are teaching reconstructions from recorded artifacts; they do not establish historical management assignments or recreate original signed records.

Recorded outcome: A learning path from public introductions to verified-account guides and starter builders, with detailed technology-stack lessons protected through existing Launch Studio access.

## How to use it

Start with the need statement.

Follow Intake → Assess → Develop → Validate → Transition. At each stage, inspect the filled examples, then complete the matching blank templates for your own project. Proceed when the gate is satisfied; otherwise revise the affected work. A document alone is not evidence of acceptance.

Read [the sanitized evidence ledger](EVIDENCE-LEDGER.md) for E1–E4. Every filled example identifies its evidence. All files are Markdown; open them in a text editor or import them into your document workspace. Nothing is submitted, signed or saved to an external app.

## I / Intake

Capture the needs, users, outcomes, and constraints.

What are we actually delivering, and to whom?

Input: The request for useful AI learning, downloadable repository/skills builders and a clear free-versus-paid path.

### Step by step

1. Capture the need and users: learners need a practical path from an introduction to a usable starter; distinguish visitors, verified learners and existing members.
2. Record the desired outcome and constraints: verified-account full guides and starter downloads, existing member access, and future classes outside the release scope.
3. Write observable acceptance criteria for each actor, including what an anonymous visitor must not receive.

### Templates and deliverables

- Project brief: [filled example](filled-examples/01-project-brief.md) · [blank template](templates/01-project-brief.md). Define one outcome, its boundaries and the evidence needed to accept it.
- Stakeholder & decision map: [filled example](filled-examples/02-stakeholder-map.md) · [blank template](templates/02-stakeholder-map.md). Identify each actor’s need, review role and decision authority.
- Acceptance criteria: [filled example](filled-examples/03-acceptance-criteria.md) · [blank template](templates/03-acceptance-criteria.md). Make completion observable before work begins.

Gate / decision: Agree the need statement, users, desired learning outcome and access constraints before assessing the approach. The recorded contract establishes the requirements; the project brief is a reconstructed teaching artifact.

Next handoff: Pass the need statement, users, agreed outcomes, constraints and actor-specific acceptance criteria into Assess.

## A / Assess

Review the current state, gaps, risks, and options.

Which approach fits the scope and risks?

Input: The Intake brief, actor map and acceptance criteria AC-01 through AC-05.

### Step by step

1. Review the current state and gaps: compare the requested learning path with existing account and membership rules, then map access for visitors, verified learners and existing members.
2. Assess the risk of leaking lesson/template content through public files, API responses or browser bundles.
3. Compare the options and choose a bounded web release that reuses existing account and membership rules; record the gaps, risks and excluded future classes or operational integrations.

### Templates and deliverables

- Options & decision record: [filled example](filled-examples/04-options-decision.md) · [blank template](templates/04-options-decision.md). Compare alternatives and preserve the reason for a bounded implementation.
- Access & permission matrix: [filled example](filled-examples/05-access-matrix.md) · [blank template](templates/05-access-matrix.md). Specify the server decision for every actor and protected resource.
- Risk & dependency register: [filled example](filled-examples/06-risks-and-dependencies.md) · [blank template](templates/06-risks-and-dependencies.md). Name the failure, its control and the evidence that will reduce uncertainty.

Gate / decision: Review the current state, learning-path gaps, access risks and implementation options before selecting the approach. The options comparison is retrospective teaching analysis; the three-tier choice itself is recorded.

Next handoff: Give Develop the current-state review, identified gaps and risks, agreed access matrix and selected implementation approach.

## D / Develop

Design and build a practical solution in increments.

What can a learner actually use now?

Input: The Assess access matrix, scope exclusions and risk/dependency controls.

### Step by step

1. Design and build the smallest complete increment: introduction → verified session → full guide → generated preview → downloaded starter.
2. Keep protected guide and template data on the server; validate builder inputs and preserve the allowed return route.
3. Add the wiring visual and course notice as reviewable increments, then update acceptance checks for the added surface.

### Templates and deliverables

- Delivery backlog: [filled example](filled-examples/07-delivery-backlog.md) · [blank template](templates/07-delivery-backlog.md). Break the scope into observable increments rather than vague activity.
- Scope & change record: [filled example](filled-examples/08-change-record.md) · [blank template](templates/08-change-record.md). Assess additions against acceptance, access and release boundaries.
- Increment review & handoff: [filled example](filled-examples/09-increment-handoff.md) · [blank template](templates/09-increment-handoff.md). Give a reviewer enough context to inspect behavior, not just changed files.

Gate / decision: Review each designed and built increment against its agreed scope before handing it to Validate. Working code, a successful build and user acceptance are separate facts.

Next handoff: Pass the working learner journeys, design decisions, generated artifacts and remaining limitations to Validate for testing against the agreed needs.

## V / Validate

Test against agreed needs and confirm readiness.

What does the evidence prove—and what does it not?

Input: Reviewable increments, acceptance criteria and the generated/downloaded artifacts.

### Step by step

1. Test the working increments against the agreed needs: anonymous denial and authorized user completion, including sign-out and reload.
2. Execute downloaded files with known valid and invalid synthetic inputs; compare protected resource bytes with the intended source.
3. Compare the results with the agreed acceptance criteria; record findings, untested areas and the readiness decision before release authorization.

### Templates and deliverables

- Acceptance & validation matrix: [filled example](filled-examples/10-validation-matrix.md) · [blank template](templates/10-validation-matrix.md). Connect each acceptance criterion to an actual observation and its limit.
- Findings, limitations & disposition: [filled example](filled-examples/11-findings-and-limits.md) · [blank template](templates/11-findings-and-limits.md). Keep unresolved or excluded proof visible instead of calling everything passed.
- Readiness & acceptance decision: [filled example](filled-examples/12-release-readiness.md) · [blank template](templates/12-release-readiness.md). Separate a readiness recommendation, sponsor authorization and observed release.

Gate / decision: The recorded release evidence supported the scoped web release. Staff-entitled lesson access was exercised; a new paid purchase, real lab-agent integration and course enrollment were not tested or launched.

Next handoff: Send Transition the test evidence against agreed needs, readiness decision, explicit limitations and release/support/handoff checks.

## T / Transition

Prepare for release, support, and operational handoff.

Who can operate it, and what happens after launch?

Input: The scoped acceptance decision, release authorization and recorded limitations.

### Step by step

1. Prepare the authorized build, release checklist and recovery path; confirm the released build and inspect the actual live learning and download paths.
2. Prepare support and complete the operational handoff: transfer the access model, support routes, known limits and change evidence to the receiving owner.
3. Assign a benefit-review owner and collect a baseline before claiming business improvement.

### Templates and deliverables

- Release & live-check checklist: [filled example](filled-examples/13-release-and-live-checks.md) · [blank template](templates/13-release-and-live-checks.md). Verify the released result instead of equating a push with a live outcome.
- Operating handover: [filled example](filled-examples/14-operating-handover.md) · [blank template](templates/14-operating-handover.md). Make access, support and change responsibility explicit after delivery.
- Benefits review & next improvements: [filled example](filled-examples/15-benefits-and-improvement.md) · [blank template](templates/15-benefits-and-improvement.md). Measure the business result without inventing ROI or adoption outcomes.

Gate / decision: Prepare release, support and operational handoff using the readiness decision and known limits. The historical release record confirms publication and live checks; ongoing ownership and benefit-review fields are recommendations where no historical assignment or measured outcome was recorded.

Next handoff: Move accepted work into operating support and a reviewed improvement backlog; begin the next Intake when the outcome or scope changes.

## Reuse the pattern

Replace the project, actors, constraints and measures with your own. Assign actual owners. Keep access rules, budget authority and release approval explicit. If the outcome or requirements change, return to the appropriate earlier stage and recheck its evidence.

The IADVT framework structures the delivery conversation. The mapping here is a retrospective teaching reconstruction of a documented AEVUS learning release; no PMI endorsement or certification claim is made.

Official reference: [PMI.org](https://www.pmi.org/). AEVUS learning project: [AI Playbooks](https://www.aevuseng.com/ai-playbooks).
