System Edition
The Guide, deployed.
The Guide Edition explains every protocol. The System Edition ships the working documents to run them — session templates, context documents, decision logs, and handoff tools ready to open on your first project. The methodology, operational from day one.
What’s included
The System Edition contains everything in the Guide Edition, plus the operator asset pack — the structured working documents that turn each protocol from described method to deployed practice.
Guide Edition — all 8 chapters
Context Architecture
Scope Constraints
Decision Checkpoints
Handoff Protocols
Architecture Integrity
Failure Pattern Reference
Documentation as Control Layer
Implementation Checklist
Added in System Edition
Session Briefing Template
Context Document Template
Scope Definition Worksheet
Decision Log Format
Handoff Summary Template
Architecture Review Checklist
Team Protocol Reference
Failure Pattern Quick-Reference Card
Operator asset pack — examples from a billing integration project
Session Briefing
SESSION BRIEFING ────────────────────────────────────────────── Project Meridian Session #7 · 14 Jan 2025 Context doc v4 / updated end of session 6 ────────────────────────────────────────────── CURRENT STATE Last session: Webhook handler complete. State machine: trial → active → past_due → canceled. Re-entry path not yet tested. Open decisions: Payment recovery — webhook handler or background job. Undecided. Deferred: Proration logic. Set aside until core billing verified in staging. THIS SESSION Scope: Payment recovery flow. past_due → active re-entry path. Integration tests for all state transitions. Out of scope: Proration. Dunning email. Plan upgrade. Any frontend UI. Re-establish: lib/billing/states.ts api/webhooks/stripe.ts Tests: Stripe CLI (not mocks). Ref: decision log, 11 Jan. CONSTRAINTS Architecture: State changes: state machine only. No direct DB writes from handler. Patterns: Errors: throw. Let webhook retry. Checkpoints: Tests pass before new transitions. ────────────────────────────────────────────── [Context document v4 follows]
Decision Log
DECISION LOG ────────────────────────────────────────────── Project Meridian Updated 14 Jan 2025 · Session #7 ────────────────────────────────────────────── [11 Jan] Webhook test approach Decision: Stripe CLI event forwarding, not mocks. Rationale: Mock-based tests passed but missed a schema difference in the actual Stripe event payload. Stripe CLI catches this class of error. Mocks do not. Affects: All webhook integration tests Review at: If test setup time becomes a consistent bottleneck ──────────────────────────────────────────────
Each document is updated when a decision is made — not reconstructed at session end.
The difference between knowing and using.
The Guide Edition tells you exactly what to do and why. The System Edition removes the translation step. Every protocol in the guide has a corresponding working document — something you open, fill in, and use on the actual project. Not a template to adapt eventually. A document you use today. For individual practitioners, that means the methodology is operational from the first session. For teams, the value goes further.
For teams, the value is structural. Without shared session formats, three developers using AI tools on the same codebase produce context that is incompatible by default — handoff summaries that don’t share a structure, decision logs with different coverage, scope documents that reflect individual judgment rather than agreed constraints.
Every context handoff is a negotiation instead of a transfer.
The System Edition establishes a shared operational baseline: handoffs work, decisions are traceable, and the codebase reflects one coherent process rather than three parallel ones.
Who it’s for
Technical leads who need a shared operational standard for a team that is already using AI tools on production codebases. Developers who want to run the methodology from the first week, without building the supporting document infrastructure from scratch. Teams that have moved past the question of whether to use AI tools and are now facing the harder question: how to use them without accumulating structural debt.
If you are working alone and want to understand the full methodology before deploying any infrastructure, the Guide Edition is the right starting point. The operator asset pack adds nothing to your understanding of the method itself.
Get the System Edition.
$39.99 — PDF + working documents. DRM-free. Lifetime updates included.
Instant download · Stripe · DRM-free PDF + documents
Also available on
Product Details
| Format | DRM-free PDF + ZIP archive — 8 working documents (Markdown and DOCX) |
| Delivery | Instant download |
| Updates | Lifetime updates included |
| License | Personal use · Non-transferable |
| Design | FIFTHBEAM |
| Workflow | Prepared using AI-assisted workflows where applicable |