Reading the artifacts.

Read this first

methodology-walkthrough-v0.html maps all 14 chapters of Shrink-Wrap It onto NorthAI's specific situation, with hyperlinks out to each role-specific artifact. Read it before anything else in this directory. Every artifact here is a node in that map.

How this directory is organized

This directory contains 41 v0 artifacts plus this README, for 42 files total. The artifacts are organized by the eight-role roster on team.html. Roles are staged across three phases: Phase 1 (months 1-3, Now), Phase 2 (months 4-9, Inflection, conditional), Phase 3 (months 10+, Scale, conditional).

Real-content artifacts are populated with substantive analysis drawn from the B-stream research threads and the discovery call. They contain real numbers, real analysis, and real recommendations you can act on today. They are v0 drafts, not final documents. The engagement refines them with your inputs.

Format-stub artifacts show the format the live engagement produces but carry placeholder content where founder inputs are required. A format stub is not a gap. It is the honest answer to "what will the engagement produce?" The format shows what to expect. The engagement produces the content.

Methodology threading: Every artifact carries a chapter anchor in its byline that names the primary Book 1 chapter the artifact operationalizes. Real-content artifacts also open with a "From Shrink-Wrap It, applied to NorthAI" callout that connects the framework to NorthAI's specific situation. The methodology-walkthrough artifact is the read-first spine that holds the threads together.

Role roster mapping: Eight roles, six chapters, three phases. Role 1.1 (Federal Posture Lead) owns 7 artifacts. Role 1.2 (Authorization Architect) owns 4. Role 1.3 (Productization Lead) owns 4. Role 1.4 (Raise Narrative Lead) owns 4. Role 2.1 (First-SKU Launch) owns 4. Role 2.2 (Customer Success) owns 4. Role 3.1 (Platform Architect) owns 4. Role 3.2 (NATO Liaison) owns 3. The methodology-walkthrough is a cross-cutting Steward artifact that sits above the role structure.

Artifact inventory

Real-content vs format-stub breakdown

Real-content (20 artifacts): federal-award-footprint, prime-relationship-status, eo-impact-scan, far-dfars-tracker, procurement-forecast-scan, outside-in-mirror, fedramp-20x-path-memo, ato-comparison, 3pao-shortlist, productization-roadmap, tech-vector-sku-spec, 70-30-boundary-diagram, pricing-range-memo, raise-narrative-brief, valuation-thesis-stress-test, contract-paper-template, sla-template, allied-buyer-map, uk-aus-nato-pathway-memo, firewall-precedents, plus methodology-walkthrough.

Format-stub (14 artifacts): vehicle-delta-tracker, compliance-lead-spec, recurring-revenue-tracker, diligence-room-pack, sku-launch-plan, customer-onboarding-playbook, first-invoice-template, expansion-account-playbook, nps-outcome-cadence, second-sku-spec, platform-spec, build-vs-buy-memo, platform-roadmap, l2-to-l3-transition-plan.

The real-content set is heavier than the format-stub set because the B-stream research covered six verified threads before the first artifact was written, and the discovery call produced 35 corpus quotes. Format stubs require inputs only the founders have: current MRR breakdown, hiring constraints, sponsor commitment list, deployment environment detail, and first-customer concentration data.

When the methodology threading is wrong

Chapter anchors are primary assignments, not exclusive ones. An artifact anchored to Ch 11 (What Gets Standardized) may also draw on Ch 12 (Product Boundaries That Hold). The byline shows the primary chapter. Reading the methodology-walkthrough gives the full cross-chapter map.

The v0 classification reflects the state at the time of this analysis. A real-content artifact rated as such today may need reclassification if NorthAI's situation changes (for example, if authorization path is selected before the engagement begins, the fedramp-20x-path-memo shifts from recommendation to confirmation). Flag outdated classifications to the Steward role.

Format stubs are not promises about what the engagement will produce. They show the format. The engagement produces the content based on inputs Tim and Stephanie supply during the engagement. A stub is not a deliverable; it is a template and a prompt for the inputs required.

Phase 2 and Phase 3 artifacts are conditional. They activate on specific triggers listed in the role cards on team.html. None of the Phase 2 or Phase 3 artifacts represent commitments. They exist to show the full arc of what the engagement can produce if those phases activate.