Delivery methodology
Method overview
A reusable delivery methodology combining human-owned product direction with AI-assisted implementation, independent verification, durable handoffs and automated quality gates.
Method ownership: Method owner, product director and release authority
Context and constraints
- Product direction, content decisions and release approval had to remain human-owned throughout AI-assisted implementation.
- Implementation and verification needed distinct roles, durable context and explicit acceptance gates.
Delivery stack
Delivery stack
- Codex
- Claude
- GitHub Actions
- PowerShell
- Astro
- Playwright
Method in practice
- Define separate implementation and verification roles with explicit ownership, handoffs and review gates.
- Apply the method across Astro delivery, interactive 2.5D storytelling, accessibility, content and document production.
- Set repeatable acceptance criteria for content quality, responsive behaviour, accessibility and browser reliability.
Validation and outcome
- The public repository contains durable delivery records, decisions, handoffs, risks and automated quality checks.
- Unit, browser, accessibility, content and build tests cover the resulting portfolio release.
Outcome
Used to deliver and verify the professional Static View and Explore Anzania as one release with a public audit trail and repeatable quality checks.
Public scope
The method, its delivery practices and the available validation trail are documented in the public repository linked above.
Constraints and limits
- This methodology is demonstrated through the portfolio release; it is not a standalone software product or client engagement.