Starter workflow

Static-First Starter Walkthrough

A source-backed article with local data, figures, interaction state, and an accepted catalog publication decision.

The static-first starter is no longer only a template proof. This published route renders the starter as a real article, keeps the source boundary explicit, adds one scoped article-specific interaction, and accepts catalog inclusion for the local proof boundary.

Question

The platform needs a repeatable way to turn source-registered local material into a visible essay route without copying third-party prose, screenshots, artwork, or ignored research downloads.

Local Model

The local model is the existing Astro content collection: one index.mdx file owns prose and placement, essay.config.ts owns the non-frontmatter proof contract, and checked-in data files feed shared static primitives.

Figure 1. Starter Route Shell A static starter route connects registered source material, article-owned data, local proof gates, and scoped article interactions.

Mechanism

The starter route stays static by default. Shared Astro components render article-owned source boundaries, artifact indexes, evidence trails, proof manifests, release handoffs, starter workflow packets, and verification gates without runtime fetches.

Proof Ladder

The first walkthrough-specific data artifact maps the blueprint layers to this published route’s local owners and gates before a small hydrated inspector consumes the same local contract.

LayerOwnerGate
Content layerindex.mdxFocused browser coverage verifies the published route and proof-ladder section render.
Configuration layeressay.config.tsFocused unit coverage checks the proof metadata and published status.
Data artifact layerdata/starter-proof-ladder.jsonZod parsing rejects missing, reordered, or source-mismatched proof steps.
Starter handoff layerdata/article-starter-manifest.jsonStarter manifest and handoff tests verify the data artifact remains article-owned.
Verification layerstarterWalkthrough.test.ts and home.spec.tsFocused Vitest, Playwright, typecheck, build, diff, and scaffold validation pass.
Figure 2. Starter Walkthrough Proof Flow A static React/SVG figure consumes the starter walkthrough proof-ladder JSON and turns the local source, data, handoff, and verification gates into a visual route.
Starter walkthrough proof flowFive ordered nodes connect the article content, configuration, data artifact, starter handoff, and verification layers.1Content layer2Configuration layer3Data artifact layer4Starter handoff layer5Verification layer
  • Content layerindex.mdxFocused browser coverage verifies the published route and proof-ladder section render.
  • Configuration layeressay.config.tsFocused unit coverage checks the proof metadata and published status.
  • Data artifact layerdata/starter-proof-ladder.jsonZod parsing rejects missing, reordered, or source-mismatched proof steps.
  • Starter handoff layerdata/article-starter-manifest.jsonStarter manifest and handoff tests verify the data artifact remains article-owned.
  • Verification layerstarterWalkthrough.test.ts and home.spec.tsFocused Vitest, Playwright, typecheck, build, diff, and scaffold validation pass.
Figure 2. Starter Walkthrough Proof Flow proof metadata
Source
blueprint-001
Locator
BLUEPRINT.md sections 5, 7, 9, and 11
Gate
Vitest, Playwright, static build, and scaffold validation verify the static figure and source-gate wrapper.
  • FigureProof renders the title, caption, and source metadata through the shared FigureFrame shell.
  • StarterProofLadderFlow consumes article-owned proof-ladder data without client hydration.
  • Playwright verifies non-empty SVG nodes, links, and proof gate cards.

Gate Inspector

The first walkthrough-specific interaction hydrates only the layer-selection controls. The source metadata stays in FigureProof, and the island reads the same checked-in proof ladder as the static figure.

Interactive Figure 3. Starter Proof Gate Inspector A hydrated React island consumes the starter walkthrough proof-ladder JSON and lets readers inspect each local owner, claim, and gate without introducing remote state.
Starter walkthrough proof gate inspectorA hydrated proof gate inspector generated from article-owned starter walkthrough proof ladder data.1Content layer2Configuration layer3Data artifact layer4Starter handoff layer5Verification layer
Starter proof layer

Content layer

Owner
index.mdx
Claim
The walkthrough route keeps source-backed prose and visible artifact placement in static MDX.
Gate
Focused browser coverage verifies the published route and proof-ladder section render.
Selected starter layer: Content layer
Interactive Figure 3. Starter Proof Gate Inspector proof metadata
Source
blueprint-001
Locator
BLUEPRINT.md sections 5, 7, 9, and 11
Gate
Vitest, Playwright, static build, and scaffold validation verify the scoped hydrated inspector and source-gate wrapper.
  • FigureProof keeps source metadata outside the hydrated React island.
  • StarterProofGateInspector hydrates only the proof-layer controls with client:visible.
  • Playwright verifies the selected layer state, data artifact detail, and reset path.

Limits

This route proves the starter can become visible published content with one article-specific data artifact, one static data-backed figure, one hydrated local inspector, and an accepted catalog decision. It does not claim deployment proof, a new research topic, remote source fetching, CMS storage, or generated starter packages.

Source Boundary

The accepted source is blueprint-001 at BLUEPRINT.md plus the checked-in starter templates and walkthrough-owned proof records. The published catalog entry is accepted for this route only. No research_downloads assets, third-party copy, remote template fetches, deployment proof, or broad claims about future article topics are accepted.

Publish Readiness

The publish decision accepts the published frontmatter, catalog inclusion, source boundary, article-owned proof ladder, static figure, hydrated inspector, and focused verification records. Deployment, CMS, remote-source, generated-package, and new-topic claims remain outside this proof.

Artifact Index

Static-First Starter Walkthrough Artifact Index

The index names the local content, data, primitive, and verification files covered by the publish decision.

  1. 1. Content shell Accepted

    Publish decision summary for content shell.

    • Artifact
      index.mdx
      Kind
      content
      Gate
      Focused publish decision gate for article mdx.
    • Artifact
      essay.config.ts
      Kind
      configuration
      Gate
      Focused publish decision gate for essay config.
  2. 2. Article data Accepted

    Publish decision summary for article data. Route-visible TypeScript loaders are listed with their JSON data.

    • Artifact
      data/source-boundary.json
      Kind
      data
      Gate
      Focused publish decision gate for source boundary.
    • Artifact
      data/article-artifact-index.json
      Kind
      data
      Gate
      Focused publish decision gate for artifact index.
    • Artifact
      data/article-sections.json
      Kind
      data
      Gate
      ArticleSectionNav uses the checked-in section data rendered by the route.
    • Artifact
      data/article-checklist.json
      Kind
      data
      Gate
      ArticleChecklist and release readiness use the checked-in publish-readiness checklist.
    • Artifact
      data/starter-proof-ladder.json
      Kind
      data
      Gate
      Focused unit and browser checks verify the proof ladder data renders in the published route.
    • Artifact
      data/figure-proofs.json
      Kind
      data
      Gate
      Focused unit and browser checks verify the proof-ladder flow and gate-inspector metadata plus rendered source wrappers.
    • Artifact
      data/promotion-readiness.json
      Kind
      data
      Gate
      Focused unit and browser checks verify the starter walkthrough ready command packet.
    • Artifact
      data/article-starter-manifest.json
      Kind
      data
      Gate
      Focused publish decision gate for starter manifest.
    • Artifact
      data/article-starter-workflow.json
      Kind
      data
      Gate
      Focused publish decision gate for starter workflow.
    • Artifact
      data/article-evidence-trail.json
      Kind
      data
      Gate
      Focused publish decision gate for evidence trail.
    • Artifact
      data/article-claim-ledger.json
      Kind
      data
      Gate
      Focused publish decision gate for claim ledger.
    • Artifact
      data/article-claim-map.json
      Kind
      data
      Gate
      Focused publish decision gate for claim map.
    • Artifact
      data/article-proof-manifest.json
      Kind
      data
      Gate
      Focused publish decision gate for proof manifest.
    • Artifact
      data/article-verification-matrix.json
      Kind
      data
      Gate
      Focused publish decision gate for verification matrix.
    • Artifact
      data/article-release-handoff.json
      Kind
      data
      Gate
      Focused publish decision gate for release handoff.
    • Artifact
      data/publication-workflow.json
      Kind
      data
      Gate
      ArticlePublicationWorkflow renders the checked-in publication workflow record.
    • Artifact
      data/authoring-flow.json
      Kind
      data
      Gate
      ArticleAuthoringFlow renders the checked-in authoring flow record.
    • Artifact
      data/articleArtifactIndex.ts
      Kind
      loader
      Gate
      Route import validates and exports the checked-in artifact index data before rendering.
    • Artifact
      data/articleChecklist.ts
      Kind
      loader
      Gate
      Route import validates and exports the checked-in article checklist data before rendering.
    • Artifact
      data/articleClaimLedger.ts
      Kind
      loader
      Gate
      Route import validates and exports the checked-in claim ledger data before rendering.
    • Artifact
      data/articleClaimMap.ts
      Kind
      loader
      Gate
      Route import validates and exports the checked-in claim map data before rendering.
    • Artifact
      data/articleEvidenceTrail.ts
      Kind
      loader
      Gate
      Route import validates and exports the checked-in evidence trail data before rendering.
    • Artifact
      data/articleProofManifest.ts
      Kind
      loader
      Gate
      Route import validates and exports the checked-in proof manifest data before rendering.
    • Artifact
      data/articleReleaseHandoff.ts
      Kind
      loader
      Gate
      Route import validates and exports the checked-in release handoff data before rendering.
    • Artifact
      data/articleSections.ts
      Kind
      loader
      Gate
      Route import validates and exports the checked-in article sections data before rendering.
    • Artifact
      data/articleStarterManifest.ts
      Kind
      loader
      Gate
      Route import validates and exports the checked-in starter manifest data before rendering.
    • Artifact
      data/articleStarterWorkflow.ts
      Kind
      loader
      Gate
      Route import validates and exports the checked-in starter workflow data before rendering.
    • Artifact
      data/articleVerificationMatrix.ts
      Kind
      loader
      Gate
      Route import validates and exports the checked-in verification matrix data before rendering.
    • Artifact
      data/authoringFlow.ts
      Kind
      loader
      Gate
      Route import validates and exports the checked-in authoring flow data before rendering.
    • Artifact
      data/figureProofs.ts
      Kind
      loader
      Gate
      Route import validates and exports the checked-in figure proofs data before rendering.
    • Artifact
      data/promotionReadiness.ts
      Kind
      loader
      Gate
      Route import validates and exports the starter walkthrough promotion-readiness packet before rendering.
    • Artifact
      data/publicationWorkflow.ts
      Kind
      loader
      Gate
      Route import validates and exports the checked-in publication workflow data before rendering.
    • Artifact
      data/sourceBoundary.ts
      Kind
      loader
      Gate
      Route import validates and exports the checked-in source boundary data before rendering.
    • Artifact
      data/starterProofLadder.ts
      Kind
      loader
      Gate
      Route import validates and exports the checked-in starter proof ladder data before rendering.
  3. 3. Shared primitives Accepted

    Published route-visible shared primitives are listed as app-file dependencies instead of implicit component ownership, and route-local figure support files are covered explicitly.

    • Artifact
      src/components/ArticleArtifactIndex.astro
      Kind
      component
      Gate
      Focused publish decision gate for artifact index component.
    • Artifact
      src/components/ArticlePromotionReadiness.astro
      Kind
      component
      Gate
      ArticlePromotionReadiness renders the local ready command packet without changing deployment boundaries.
    • Artifact
      src/components/FigureFrame.astro
      Kind
      component
      Gate
      The route imports shared figure chrome for the starter proof ladder and gate inspector.
    • Artifact
      src/components/FigureFrame.css
      Kind
      support
      Gate
      FigureFrame imports this shared chrome stylesheet directly.
    • Artifact
      src/components/FigureProof.astro
      Kind
      component
      Gate
      FigureProof renders source metadata around the static starter proof-ladder figure.
    • Artifact
      src/components/FigureControls.tsx
      Kind
      support
      Gate
      FigureProof imports FigureMetadataList from the shared figure controls module.
    • Artifact
      src/components/FigureControls.module.css
      Kind
      support
      Gate
      FigureControls imports this CSS module for the metadata and figure text primitives.
    • Artifact
      src/components/ArticleSectionNav.astro
      Kind
      component
      Gate
      ArticleSectionNav renders the visible section list from article-owned section data.
    • Artifact
      src/components/ArticleSourceBoundary.astro
      Kind
      component
      Gate
      ArticleSourceBoundary renders accepted and rejected boundaries from article-owned data.
    • Artifact
      figures/StarterProofLadderFlow/StarterProofLadderFlow.tsx
      Kind
      figure
      Gate
      The figure consumes data/starter-proof-ladder.json without client hydration.
    • Artifact
      figures/StarterProofLadderFlow/StarterProofLadderFlow.module.css
      Kind
      support
      Gate
      StarterProofLadderFlow imports this CSS module directly.
    • Artifact
      figures/StarterProofLadderFlow/StarterProofLadderFlow.stories.tsx
      Kind
      support
      Gate
      Storybook renders the route-local starter proof ladder figure for authoring review.
    • Artifact
      figures/StarterProofLadderFlow/StarterProofLadderFlow.test.ts
      Kind
      support
      Gate
      Focused figure tests exercise the route-local starter proof ladder model and static markup.
    • Artifact
      figures/StarterProofLadderFlow/model.ts
      Kind
      support
      Gate
      StarterProofLadderFlow imports this local model builder directly.
    • Artifact
      figures/StarterProofGateInspector/StarterProofGateInspector.tsx
      Kind
      figure
      Gate
      The island consumes data/starter-proof-ladder.json with client:visible hydration.
    • Artifact
      figures/StarterProofGateInspector/StarterProofGateInspector.module.css
      Kind
      support
      Gate
      StarterProofGateInspector imports this CSS module directly.
    • Artifact
      figures/StarterProofGateInspector/StarterProofGateInspector.stories.tsx
      Kind
      support
      Gate
      Storybook renders the route-local starter proof gate inspector for authoring review.
    • Artifact
      figures/StarterProofGateInspector/StarterProofGateInspector.test.ts
      Kind
      support
      Gate
      Focused figure tests exercise the route-local starter proof gate model and hydrated markup.
    • Artifact
      figures/StarterProofGateInspector/model.ts
      Kind
      support
      Gate
      StarterProofGateInspector imports this local model builder directly.
    • Artifact
      src/components/ArticleEvidenceTrail.astro
      Kind
      component
      Gate
      Focused publish decision gate for evidence trail component.
    • Artifact
      src/components/ArticleClaimLedger.astro
      Kind
      component
      Gate
      Focused publish decision gate for claim ledger component.
    • Artifact
      src/components/ArticleClaimMap.astro
      Kind
      component
      Gate
      Focused publish decision gate for claim map component.
    • Artifact
      src/components/ArticleProofManifest.astro
      Kind
      component
      Gate
      Focused publish decision gate for proof manifest component.
    • Artifact
      src/components/ArticleVerificationMatrix.astro
      Kind
      component
      Gate
      Focused publish decision gate for verification matrix component.
    • Artifact
      src/components/ArticleReleaseHandoff.astro
      Kind
      component
      Gate
      Focused publish decision gate for release handoff component.
    • Artifact
      src/components/ArticleReleaseReadiness.astro
      Kind
      component
      Gate
      Focused publish decision gate for release readiness component.
    • Artifact
      src/components/ArticleStarterManifest.astro
      Kind
      component
      Gate
      Focused publish decision gate for starter manifest component.
    • Artifact
      src/components/ArticleStarterWorkflow.astro
      Kind
      component
      Gate
      Focused publish decision gate for starter workflow component.
    • Artifact
      src/components/ArticleStarterReadiness.astro
      Kind
      component
      Gate
      Focused publish decision gate for starter readiness component.
    • Artifact
      src/components/ArticleStarterHandoff.astro
      Kind
      component
      Gate
      Focused publish decision gate for starter handoff component.
    • Artifact
      src/components/ArticlePublicationWorkflow.astro
      Kind
      component
      Gate
      ArticlePublicationWorkflow renders the visible publication workflow record.
    • Artifact
      src/components/ArticlePublicationQa.astro
      Kind
      component
      Gate
      ArticlePublicationQa renders the visible publication QA record.
    • Artifact
      src/components/ArticleAuthoringFlow.astro
      Kind
      component
      Gate
      ArticleAuthoringFlow renders the visible authoring flow record.
    • Artifact
      src/components/ArticleChecklist.astro
      Kind
      component
      Gate
      ArticleChecklist renders the visible checklist record.
  4. 4. Verification handoff Accepted

    Focused local checks, starter proof, and scaffold validation close the publish decision.

    • Artifact
      src/content/essays/starterWalkthrough.test.ts
      Kind
      test
      Gate
      Vitest verifies published route data, proof ladder, figures, and readiness records.
    • Artifact
      tests/home.spec.ts
      Kind
      test
      Gate
      Playwright verifies the published route, proof ladder, static figure, hydrated inspector, and readiness section.
    • Artifact
      scripts/prove_static_first_starter_instantiation.py
      Kind
      validator
      Gate
      The starter instantiation proof rejects placeholders and ignored research_downloads references.
    • Artifact
      scripts/validate_tutorial_scaffold.py
      Kind
      validator
      Gate
      The scaffold validator verifies queue, ledger, and artifact consistency.
Source
blueprint-001
Accepted
The publish decision accepts checked-in route content, article-owned data, local figures, scoped interaction, route-visible shared component modules and their direct local support modules, shared readiness primitives, and focused verification artifacts.
Not Claimed
No global artifact registry, deployment proof, remote filesystem scan, runtime source crawl, or CMS task store is accepted.

Claim Ledger

Static-First Starter Walkthrough Claim Ledger

The ledger records selected source-backed claim decisions, local artifacts, and gates before publication handoff.

  1. 1. Source registration Accepted

    Starter instantiation proof claim for source registration.

    Source
    blueprint-001, BLUEPRINT.md sections 5, 6, 7, and 9
    Artifact
    source_registry.yaml
    Decision
    Starter instantiation proof decision for source registration.
    Gate
    Focused publish decision gate for source registration.
  2. 2. Article data ownership Accepted

    Starter instantiation proof claim for article data ownership.

    Source
    blueprint-001, BLUEPRINT.md sections 5, 6, 7, and 9
    Artifact
    data/article-claim-ledger.json
    Decision
    Starter instantiation proof decision for article data ownership.
    Gate
    Focused publish decision gate for article data ownership.
  3. 3. Starter proof ladder Accepted

    The walkthrough can add one article-specific data artifact without claiming a new figure or publication readiness.

    Source
    blueprint-001, BLUEPRINT.md sections 5, 7, 9, and 11
    Artifact
    data/starter-proof-ladder.json
    Decision
    Accept the proof ladder as a local data artifact rendered in the published route.
    Gate
    Focused unit and browser checks verify the proof ladder contract.
  4. 4. Starter proof ladder flow Accepted

    The walkthrough can add one article-specific static figure that consumes local proof-ladder data without claiming hydration or publication readiness for that figure.

    Source
    blueprint-001, BLUEPRINT.md sections 5, 7, 9, and 11
    Artifact
    figures/StarterProofLadderFlow/StarterProofLadderFlow.tsx
    Decision
    Accept the proof-ladder flow as a static article-specific figure rendered through FigureProof.
    Gate
    Focused unit and browser checks verify the figure model, source metadata, and rendered SVG.
  5. 5. Starter proof gate inspector Accepted

    The walkthrough can add one article-specific hydrated inspector that consumes local proof-ladder data without claiming a global interaction framework or publication readiness.

    Source
    blueprint-001, BLUEPRINT.md sections 5, 7, 9, and 11
    Artifact
    figures/StarterProofGateInspector/StarterProofGateInspector.tsx
    Decision
    Accept the proof gate inspector as a scoped article-specific interaction rendered through FigureProof.
    Gate
    Focused unit and browser checks verify the inspector model, selected state, source metadata, and reset path.
  6. 6. Evidence route Accepted

    Starter instantiation proof claim for evidence route.

    Source
    blueprint-001, BLUEPRINT.md sections 5, 6, 7, and 9
    Artifact
    data/article-evidence-trail.json
    Decision
    Starter instantiation proof decision for evidence route.
    Gate
    Focused publish decision gate for evidence route.
  7. 7. Release decision Accepted

    Starter instantiation proof claim for release decision.

    Source
    blueprint-001, BLUEPRINT.md sections 5, 6, 7, and 9
    Artifact
    data/article-release-handoff.json
    Decision
    Starter instantiation proof decision for release.
    Gate
    Focused publish decision gate for release decision.
  8. 8. Claim map route Accepted

    Starter instantiation proof claim for claim map route.

    Source
    blueprint-001, BLUEPRINT.md sections 5, 6, 7, and 9
    Artifact
    data/article-claim-map.json
    Decision
    Starter instantiation proof decision for claim map route.
    Gate
    Focused publish decision gate for claim map route.
  9. 9. Proof manifest route Accepted

    Starter instantiation proof claim for proof manifest route.

    Source
    blueprint-001, BLUEPRINT.md sections 5, 6, 7, and 9
    Artifact
    data/article-proof-manifest.json
    Decision
    Starter instantiation proof decision for proof manifest route.
    Gate
    Focused publish decision gate for proof manifest route.
Source
blueprint-001
Accepted
The publish decision accepts local claim ledger records tied to blueprint-001.
Not Claimed
No remote source, CMS workflow, generated starter package, or deployment proof is accepted for claim ledger.

Claim Map

Static-First Starter Walkthrough Claim Map

The map connects selected claim decisions to evidence, verification, handoff, and local artifact routes before publication handoff.

  1. 1. Source registration Accepted
    Claim
    source-registration
    Evidence
    platform-claim, Platform claim
    Verification
    source-data-gates, Source and data gates
    Handoff
    source-boundary-record, Source boundary record
    Artifact
    source_registry.yaml
    Gate
    Focused publish decision gate for source registration route.
  2. 2. Article data ownership Accepted
    Claim
    article-data-ownership
    Evidence
    article-data, Article data
    Verification
    source-data-gates, Source and data gates
    Handoff
    claim-ledger, Claim ledger
    Artifact
    data/article-artifact-index.json
    Gate
    Focused publish decision gate for article data ownership route.
  3. 3. Starter proof ladder Accepted
    Claim
    starter-proof-ladder
    Evidence
    starter-proof-ladder, Starter proof ladder
    Verification
    source-data-gates, Source and data gates
    Handoff
    starter-proof-ladder, Starter proof ladder
    Artifact
    data/starter-proof-ladder.json
    Gate
    Focused unit and browser checks verify the proof ladder data renders in the published route.
  4. 4. Starter proof ladder flow Accepted
    Claim
    starter-proof-ladder-flow
    Evidence
    starter-proof-ladder-flow, Starter proof ladder flow
    Verification
    browser-visual-gates, Browser and visual gates
    Handoff
    starter-proof-ladder-flow, Starter proof ladder flow
    Artifact
    figures/StarterProofLadderFlow/StarterProofLadderFlow.tsx
    Gate
    Focused browser checks verify the proof-ladder flow figure renders without hydration.
  5. 5. Starter proof gate inspector Accepted
    Claim
    starter-proof-gate-inspector
    Evidence
    starter-proof-gate-inspector, Starter proof gate inspector
    Verification
    browser-visual-gates, Browser and visual gates
    Handoff
    starter-proof-gate-inspector, Starter proof gate inspector
    Artifact
    figures/StarterProofGateInspector/StarterProofGateInspector.tsx
    Gate
    Focused browser checks verify the proof-gate inspector hydrates a scoped client island and updates selected state.
  6. 6. Evidence route Accepted
    Claim
    evidence-route
    Evidence
    claim-ledger, Claim ledger
    Verification
    browser-visual-gates, Browser and visual gates
    Handoff
    evidence-trail, Evidence trail
    Artifact
    data/article-evidence-trail.json
    Gate
    Focused publish decision gate for evidence route.
  7. 7. Release decision Accepted
    Claim
    release-decision
    Evidence
    release-handoff, Release handoff
    Verification
    closeout-gates, Closeout gates
    Handoff
    queue-state, Queue state
    Artifact
    data/article-release-handoff.json
    Gate
    Focused publish decision gate for release decision route.
  8. 8. Claim map route Accepted
    Claim
    claim-map-route
    Evidence
    claim-map, Claim map
    Verification
    source-data-gates, Source and data gates
    Handoff
    claim-map, Claim map
    Artifact
    data/article-claim-map.json
    Gate
    Focused publish decision gate for claim map route.
  9. 9. Proof manifest route Accepted
    Claim
    proof-manifest-route
    Evidence
    proof-manifest, Proof manifest
    Verification
    source-data-gates, Source and data gates
    Handoff
    proof-manifest, Proof manifest
    Artifact
    data/article-proof-manifest.json
    Gate
    Focused publish decision gate for proof manifest route.
Source
blueprint-001
Accepted
The publish decision accepts local claim map records tied to blueprint-001.
Not Claimed
No remote source, CMS workflow, generated starter package, or deployment proof is accepted for claim map.

Evidence Trail

Static-First Starter Walkthrough Evidence Trail

The trail maps selected source-backed claims to local article artifacts and verification gates before publication handoff.

  1. 1. Platform claim Accepted

    Starter instantiation proof claim for platform.

    Source
    blueprint-001, BLUEPRINT.md sections 5, 6, 7, and 9
    Artifact
    index.mdx
    Gate
    Focused publish decision gate for platform claim.
  2. 2. Article data Accepted

    Starter instantiation proof claim for article data.

    Source
    blueprint-001, BLUEPRINT.md sections 5, 6, 7, and 9
    Artifact
    data/article-artifact-index.json
    Gate
    Focused publish decision gate for article data.
  3. 3. Starter proof ladder Accepted

    The first walkthrough-specific data artifact is source-backed by the platform blueprint.

    Source
    blueprint-001, BLUEPRINT.md sections 5, 7, 9, and 11
    Artifact
    data/starter-proof-ladder.json
    Gate
    Focused unit coverage parses the data and browser coverage verifies the rendered proof ladder.
  4. 4. Starter proof ladder flow Accepted

    The first walkthrough-specific figure is source-backed and generated from article-owned proof-ladder data.

    Source
    blueprint-001, BLUEPRINT.md sections 5, 7, 9, and 11
    Artifact
    figures/StarterProofLadderFlow/StarterProofLadderFlow.tsx
    Gate
    Focused unit coverage parses the model and browser coverage verifies the rendered static figure.
  5. 5. Starter proof gate inspector Accepted

    The first walkthrough-specific interaction is source-backed and generated from article-owned proof-ladder data.

    Source
    blueprint-001, BLUEPRINT.md sections 5, 7, 9, and 11
    Artifact
    figures/StarterProofGateInspector/StarterProofGateInspector.tsx
    Gate
    Focused unit coverage parses the model and browser coverage verifies the hydrated selected-state behavior.
  6. 6. Verification stack Accepted

    Starter instantiation proof claim for verification stack.

    Source
    blueprint-001, BLUEPRINT.md sections 5, 6, 7, and 9
    Artifact
    data/article-verification-matrix.json
    Gate
    Focused publish decision gate for verification stack.
  7. 7. Claim ledger Accepted

    Starter instantiation proof claim for claim ledger.

    Source
    blueprint-001, BLUEPRINT.md sections 5, 6, 7, and 9
    Artifact
    data/article-claim-ledger.json
    Gate
    Focused publish decision gate for claim ledger.
  8. 8. Claim map Accepted

    Starter instantiation proof claim for claim map.

    Source
    blueprint-001, BLUEPRINT.md sections 5, 6, 7, and 9
    Artifact
    data/article-claim-map.json
    Gate
    Focused publish decision gate for claim map.
  9. 9. Release handoff Accepted

    Starter instantiation proof claim for release handoff.

    Source
    blueprint-001, BLUEPRINT.md sections 5, 6, 7, and 9
    Artifact
    data/article-release-handoff.json
    Gate
    Focused publish decision gate for release handoff.
  10. 10. Proof manifest Accepted

    Starter instantiation proof claim for proof manifest.

    Source
    blueprint-001, BLUEPRINT.md sections 5, 6, 7, and 9
    Artifact
    data/article-proof-manifest.json
    Gate
    Focused publish decision gate for proof manifest.
Source
blueprint-001
Accepted
The publish decision accepts local evidence trail records tied to blueprint-001.
Not Claimed
No remote source, CMS workflow, generated starter package, or deployment proof is accepted for evidence trail.

Proof Manifest

Static-First Starter Walkthrough Proof Manifest

Local proof packets for the published route's accepted catalog decision.

  1. 1. Source boundary proof Accepted
    Proof ID
    source-boundary-proof
    Owner
    Article folder
    Artifact
    data/source-boundary.json
    Gate
    Focused unit coverage verifies accepted and rejected source-boundary claims.
    Evidence
    The source-boundary record accepts blueprint-001, starter templates, walkthrough proof records, and catalog publication while rejecting deployment claims.
  2. 2. Artifact index proof Accepted
    Proof ID
    artifact-index-proof
    Owner
    Authoring scaffold
    Artifact
    data/article-artifact-index.json
    Gate
    Focused unit coverage parses the artifact index and browser coverage renders its local artifact paths.
    Evidence
    The artifact index names the article route, local data, proof figures, shared primitives, and verification handoff.
  3. 3. Starter proof ladder proof Accepted
    Proof ID
    starter-proof-ladder-proof
    Owner
    Article data
    Artifact
    data/starter-proof-ladder.json
    Gate
    Focused unit and browser checks verify the proof ladder data renders in the published route.
    Evidence
    The proof ladder maps BLUEPRINT.md platform layers to the walkthrough route's owners and gates.
  4. 4. Starter proof ladder flow proof Accepted
    Proof ID
    starter-proof-ladder-flow-proof
    Owner
    Article figure
    Artifact
    figures/StarterProofLadderFlow/StarterProofLadderFlow.tsx
    Gate
    Focused unit and browser checks verify the data-backed static figure.
    Evidence
    The proof-ladder flow consumes data/starter-proof-ladder.json and renders through FigureProof with blueprint-001 metadata.
  5. 5. Starter proof gate inspector proof Accepted
    Proof ID
    starter-proof-gate-inspector-proof
    Owner
    Article interaction
    Artifact
    figures/StarterProofGateInspector/StarterProofGateInspector.tsx
    Gate
    Focused unit and browser checks verify the data-backed hydrated inspector.
    Evidence
    The proof gate inspector consumes data/starter-proof-ladder.json, hydrates with client:visible, and keeps source metadata in FigureProof.
  6. 6. Claim ledger proof Accepted
    Proof ID
    claim-ledger-proof
    Owner
    Claim workflow
    Artifact
    data/article-claim-ledger.json
    Gate
    Focused publish decision gate for claim ledger.
    Evidence
    Publish decision evidence for claim ledger tied to blueprint-001 and local article records.
  7. 7. Claim map proof Accepted
    Proof ID
    claim-map-proof
    Owner
    Claim workflow
    Artifact
    data/article-claim-map.json
    Gate
    Focused publish decision gate for claim map.
    Evidence
    Publish decision evidence for claim map tied to blueprint-001 and local article records.
  8. 8. Evidence trail proof Accepted
    Proof ID
    evidence-trail-proof
    Owner
    Evidence workflow
    Artifact
    data/article-evidence-trail.json
    Gate
    Focused publish decision gate for evidence trail.
    Evidence
    Publish decision evidence for evidence trail tied to blueprint-001 and local article records.
  9. 9. Verification matrix proof Accepted
    Proof ID
    verification-matrix-proof
    Owner
    Verification workflow
    Artifact
    data/article-verification-matrix.json
    Gate
    Focused publish decision gate for verification matrix.
    Evidence
    Publish decision evidence for verification matrix tied to blueprint-001 and local article records.
  10. 10. Release handoff proof Accepted
    Proof ID
    release-handoff-proof
    Owner
    Release workflow
    Artifact
    data/article-release-handoff.json
    Gate
    Focused publish decision gate for release handoff.
    Evidence
    Publish decision evidence for release handoff tied to blueprint-001 and local article records.
  11. 11. Proof manifest proof Accepted
    Proof ID
    proof-manifest-proof
    Owner
    Release workflow
    Artifact
    data/article-proof-manifest.json
    Gate
    Focused publish decision gate for proof manifest.
    Evidence
    Publish decision evidence for proof manifest tied to blueprint-001 and local article records.
  12. 12. Release readiness proof Accepted
    Proof ID
    release-readiness-proof
    Owner
    Release workflow
    Artifact
    src/components/ArticleReleaseReadiness.astro
    Gate
    Focused publish decision gate for release readiness.
    Evidence
    Publish decision evidence for release readiness tied to blueprint-001 and local article records.
  13. 13. Starter manifest proof Accepted
    Proof ID
    starter-manifest-proof
    Owner
    Authoring scaffold
    Artifact
    data/article-starter-manifest.json
    Gate
    Focused publish decision gate for starter manifest.
    Evidence
    Publish decision evidence for starter manifest tied to blueprint-001 and local article records.
  14. 14. Starter workflow proof Accepted
    Proof ID
    starter-workflow-proof
    Owner
    Authoring scaffold
    Artifact
    data/article-starter-workflow.json
    Gate
    Focused publish decision gate for starter workflow.
    Evidence
    Publish decision evidence for starter workflow tied to blueprint-001 and local article records.
  15. 15. Starter readiness proof Accepted
    Proof ID
    starter-readiness-proof
    Owner
    Authoring scaffold
    Artifact
    src/components/ArticleStarterReadiness.astro
    Gate
    Focused publish decision gate for starter readiness.
    Evidence
    Publish decision evidence for starter readiness tied to blueprint-001 and local article records.
  16. 16. Starter handoff proof Accepted
    Proof ID
    starter-handoff-proof
    Owner
    Authoring scaffold
    Artifact
    src/components/ArticleStarterHandoff.astro
    Gate
    Focused publish decision gate for starter handoff.
    Evidence
    Publish decision evidence for starter handoff tied to blueprint-001 and local article records.
Source
blueprint-001
Accepted
The publish decision accepts source-boundary, artifact-index, proof-ladder, static-figure, and hydrated-inspector proofs for the published route.
Not Claimed
No deployment proof, production release decision, remote source fetch, CMS workflow, generated starter package, or new source topic is accepted.

Verification Matrix

Static-First Starter Walkthrough Verification Matrix

The matrix records the local commands, targets, and evidence behind the accepted publish decision.

  1. 1. Source and data gates Accepted

    Source, data, and figure contract checks for the published route.

    • Article unit Accepted
      Command
      npm run starter:instantiate:proof
      Target
      static-first starter templates
      Evidence
      The starter instantiation proof renders a placeholder-free source-backed article from the starter templates.
    • Starter unit Accepted
      Command
      npm run starter:instantiate:proof
      Target
      static-first starter templates
      Evidence
      Focused starter coverage keeps the copied template contract aligned with the real route.
    • Starter proof ladder contract Accepted
      Command
      npm run test -- starterWalkthrough
      Target
      data/starter-proof-ladder.json and index.mdx#proof-ladder
      Evidence
      Focused unit coverage parses the proof ladder and browser coverage verifies the rendered table.
    • Starter proof ladder flow contract Accepted
      Command
      npm run test -- StarterProofLadderFlow starterWalkthrough
      Target
      data/figure-proofs.json and figures/StarterProofLadderFlow/model.ts
      Evidence
      Focused unit coverage verifies the figure proof metadata and model consume the article-owned proof ladder.
    • Starter proof gate inspector contract Accepted
      Command
      npm run test -- StarterProofGateInspector starterWalkthrough
      Target
      data/figure-proofs.json and figures/StarterProofGateInspector/model.ts
      Evidence
      Focused unit coverage verifies the interactive figure proof metadata and model consume the article-owned proof ladder.
    • Starter manifest contract Accepted
      Command
      npm run test -- staticFirstEssay articleStarter
      Target
      data/article-starter-manifest.json and src/content/essay-starters/static-first/
      Evidence
      Focused unit coverage parses the starter manifest and verifies local artifact paths.
    • Starter workflow contract Accepted
      Command
      npm run test -- staticFirstEssay articleStarter
      Target
      data/article-starter-workflow.json and src/components/ArticleStarterWorkflow.astro
      Evidence
      Focused unit coverage verifies all starter workflow steps are accepted for the publish decision.
  2. 2. Static build gates Accepted

    Static build checks for the published route and shared components.

    • Typecheck Accepted
      Command
      npm run typecheck
      Target
      Astro content collection and TypeScript project
      Evidence
      Typecheck validates Astro content imports, data loaders, and TypeScript component boundaries.
    • Production build Accepted
      Command
      npm run build
      Target
      static Astro build
      Evidence
      Production build validates the static route output and hydrated island bundling.
  3. 3. Browser and visual gates Accepted

    Browser and Storybook checks for visible static and hydrated proof behavior.

    • Focused browser smoke Accepted
      Command
      npm run starter:instantiate:proof
      Target
      static-first starter templates
      Evidence
      Focused browser coverage verifies the published route, visible readiness section, figures, and zero horizontal overflow.
    • Starter proof ladder flow browser Accepted
      Command
      npm run test:browser -- -g "static-first starter walkthrough"
      Target
      index.mdx#proof-ladder and StarterProofLadderFlow SVG
      Evidence
      Focused browser coverage verifies visible SVG nodes, links, figure-proof metadata, and no hydrated island.
    • Starter proof gate inspector browser Accepted
      Command
      npm run test:browser -- -g "static-first starter walkthrough"
      Target
      index.mdx#gate-inspector and StarterProofGateInspector island
      Evidence
      Focused browser coverage verifies one hydrated island, selected layer state, data artifact detail, and reset behavior.
    • Release readiness rollup Accepted
      Command
      npm run starter:instantiate:proof
      Target
      static-first starter templates
      Evidence
      Focused browser coverage verifies the release-readiness rollup is accepted while deployment proof remains out of scope.
    • Starter readiness rollup Accepted
      Command
      npm run starter:instantiate:proof
      Target
      static-first starter templates
      Evidence
      Focused browser coverage verifies starter readiness is accepted because all starter records are accepted.
    • Starter handoff packet Accepted
      Command
      npm run starter:instantiate:proof
      Target
      static-first starter templates
      Evidence
      Focused browser coverage verifies the starter handoff packet and local proof counts.
    • Storybook build Accepted
      Command
      npm run build-storybook
      Target
      Storybook static build
      Evidence
      Storybook build validates the article-specific proof figures outside the article route.
  4. 4. Closeout gates Accepted

    Closeout checks for tracked diff and scaffold ledgers.

    • Diff check Accepted
      Command
      git diff --check
      Target
      tracked working tree diff
      Evidence
      Diff check rejects trailing whitespace and patch formatting errors.
    • Scaffold validator Accepted
      Command
      python3 scripts/validate_tutorial_scaffold.py
      Target
      tutorial scaffold ledgers
      Evidence
      Scaffold validation verifies queue, ledger, evidence, lock, and starter proof consistency.
Source
blueprint-001
Accepted
The publish decision accepts focused unit, browser, starter instantiation, typecheck, build, Storybook, diff, and scaffold validation gates.
Not Claimed
No live deployment, production release, remote status fetch, CI dashboard, or external publication service is accepted.

Release Handoff

Static-First Starter Walkthrough Release Handoff

The handoff records the published route, local proof packets, validation records, and catalog decision.

  1. 1. Article packet Accepted

    The published article packet is source-backed and included in the catalog.

    • Published route Accepted
      Artifact
      index.mdx
      Gate
      Focused unit and browser checks verify published status, route copy, and the visible Publish Readiness section.
      Evidence
      The route keeps status published while recording the accepted publish decision.
    • Source boundary record Accepted
      Artifact
      data/source-boundary.json
      Gate
      Focused unit coverage verifies accepted and rejected source-boundary claims.
      Evidence
      The source boundary accepts blueprint-001, starter templates, walkthrough proof records, and catalog publication while rejecting deployment claims.
  2. 2. Validation packet Accepted

    Local proof records are accepted while deployment proof stays out of scope.

    • Claim ledger Accepted
      Artifact
      data/article-claim-ledger.json
      Gate
      Focused unit coverage parses the claim-ledger data.
      Evidence
      The claim ledger remains article-owned and source-backed by blueprint-001.
    • Starter proof ladder Accepted
      Artifact
      data/starter-proof-ladder.json
      Gate
      Focused unit and browser checks verify the proof ladder data renders in the published route.
      Evidence
      The proof ladder records the first article-specific data artifact and its source-backed local gates.
    • Starter proof ladder flow Accepted
      Artifact
      figures/StarterProofLadderFlow/StarterProofLadderFlow.tsx
      Gate
      Focused unit and browser checks verify the static data-backed figure renders in the published route.
      Evidence
      The figure consumes data/starter-proof-ladder.json, uses FigureProof source metadata, and renders without a client island.
    • Starter proof gate inspector Accepted
      Artifact
      figures/StarterProofGateInspector/StarterProofGateInspector.tsx
      Gate
      Focused unit and browser checks verify the data-backed hydrated inspector renders in the published route.
      Evidence
      The island consumes data/starter-proof-ladder.json, uses FigureProof source metadata, and hydrates one scoped client island.
    • Claim map Accepted
      Artifact
      data/article-claim-map.json
      Gate
      Focused unit coverage parses the claim-map data.
      Evidence
      The claim map routes local claims to local evidence and handoff records.
    • Proof manifest Accepted
      Artifact
      data/article-proof-manifest.json
      Gate
      Focused unit coverage verifies the local proof-manifest entries.
      Evidence
      The manifest records the source boundary, artifact index, proof ladder, static figure, and hydrated inspector.
    • Evidence trail Accepted
      Artifact
      data/article-evidence-trail.json
      Gate
      Focused unit coverage parses the evidence-trail data.
      Evidence
      The trail keeps proof artifacts and verification gates tied to blueprint-001.
    • Verification matrix Accepted
      Artifact
      data/article-verification-matrix.json
      Gate
      Focused unit coverage parses the verification-matrix data.
      Evidence
      The matrix names focused unit, browser, build, Storybook, diff, and scaffold gates for the publish decision.
    • Release readiness Accepted
      Artifact
      src/components/ArticleReleaseReadiness.astro
      Gate
      Focused publish decision gate for release readiness.
      Evidence
      Publish decision evidence for release readiness tied to blueprint-001 and local article records.
    • Starter manifest Accepted
      Artifact
      data/article-starter-manifest.json
      Gate
      Focused unit coverage verifies starter-manifest entries for local route files and figure folders.
      Evidence
      The manifest keeps copied starter ownership explicit.
    • Starter workflow Accepted
      Artifact
      data/article-starter-workflow.json
      Gate
      Focused unit coverage verifies all starter workflow steps are accepted.
      Evidence
      The workflow records copy, placeholder replacement, source registration, data wiring, rendering, and local gate closeout.
    • Starter readiness Accepted
      Artifact
      src/components/ArticleStarterReadiness.astro
      Gate
      Focused publish decision gate for starter readiness.
      Evidence
      Publish decision evidence for starter readiness tied to blueprint-001 and local article records.
    • Starter handoff Accepted
      Artifact
      src/components/ArticleStarterHandoff.astro
      Gate
      Focused publish decision gate for starter handoff.
      Evidence
      Publish decision evidence for starter handoff tied to blueprint-001 and local article records.
    • Focused browser proof Accepted
      Artifact
      scripts/prove_static_first_starter_instantiation.py
      Gate
      Focused desktop and mobile Playwright coverage verifies the visible route, figures, interaction, readiness section, and overflow boundary.
      Evidence
      The browser proof exercises the published route and keeps publication claims scoped to local behavior.
  3. 3. Closeout packet Accepted

    Publish decision summary for closeout packet.

    • Run log ledger Accepted
      Artifact
      run_log.md
      Gate
      Focused publish decision gate for run log.
      Evidence
      Publish decision evidence for run log tied to blueprint-001 and local article records.
    • Evidence ledger Accepted
      Artifact
      evidence_ledger.yaml
      Gate
      Focused publish decision gate for evidence ledger.
      Evidence
      Publish decision evidence for evidence ledger tied to blueprint-001 and local article records.
  4. 4. Next work packet Accepted

    Publish decision summary for next work packet.

    • Queue state Accepted
      Artifact
      state.md and todo.md
      Gate
      Focused publish decision gate for queue state.
      Evidence
      Publish decision evidence for queue state tied to blueprint-001 and local article records.
    • Starter template Accepted
      Artifact
      src/content/essay-starters/static-first/
      Gate
      Focused publish decision gate for starter template.
      Evidence
      Publish decision evidence for starter template tied to blueprint-001 and local article records.
Source
blueprint-001
Accepted
The publish decision accepts the published route packet, source-boundary record, article-owned proof data, local figures, scoped interaction, and focused browser proof.
Not Claimed
No deployment proof, production release decision, remote source fetch, CMS workflow, generated starter package, or new source topic is accepted.

Starter Manifest

Static-First Starter Walkthrough Starter Manifest

The manifest names the checked-in article files, data artifacts, starter templates, and verification gates that let the article start from the static-first starter folder.

  1. 1. Content shell Accepted

    Publish decision summary for content shell.

    • Article MDX Accepted
      Kind
      content
      Path
      index.mdx
      Gate
      Focused publish decision gate for article mdx.
    • Essay config Accepted
      Kind
      configuration
      Path
      essay.config.ts
      Gate
      Focused publish decision gate for essay config.
    • Assets folder Accepted
      Kind
      folder
      Path
      assets/
      Gate
      Focused publish decision gate for assets folder.
    • Figures folder Accepted
      Kind
      folder
      Path
      figures/
      Gate
      Focused publish decision gate for figures folder.
    • Starter proof ladder flow figure Accepted
      Kind
      figure
      Path
      figures/StarterProofLadderFlow/
      Gate
      Focused figure model and browser checks verify the data-backed static figure remains article-owned.
    • Starter proof gate inspector Accepted
      Kind
      figure
      Path
      figures/StarterProofGateInspector/
      Gate
      Focused model and browser checks verify the data-backed hydrated island remains article-owned.
  2. 2. Article data Accepted

    Publish decision summary for article data.

    • Source boundary Accepted
      Kind
      data
      Path
      data/source-boundary.json
      Gate
      Focused publish decision gate for source boundary.
    • Starter proof ladder Accepted
      Kind
      data
      Path
      data/starter-proof-ladder.json
      Gate
      Focused unit and browser checks verify the proof ladder data renders in the published route.
    • Figure proofs Accepted
      Kind
      data
      Path
      data/figure-proofs.json
      Gate
      Focused unit coverage verifies the static and interactive figure proof metadata stay tied to blueprint-001.
    • Starter manifest Accepted
      Kind
      data
      Path
      data/article-starter-manifest.json
      Gate
      Focused publish decision gate for starter manifest.
    • Starter workflow Accepted
      Kind
      data
      Path
      data/article-starter-workflow.json
      Gate
      Focused publish decision gate for starter workflow.
    • Artifact index Accepted
      Kind
      data
      Path
      data/article-artifact-index.json
      Gate
      Focused publish decision gate for artifact index.
    • Proof manifest Accepted
      Kind
      data
      Path
      data/article-proof-manifest.json
      Gate
      Focused publish decision gate for proof manifest.
    • Verification matrix Accepted
      Kind
      data
      Path
      data/article-verification-matrix.json
      Gate
      Focused publish decision gate for verification matrix.
    • Release handoff Accepted
      Kind
      data
      Path
      data/article-release-handoff.json
      Gate
      Focused publish decision gate for release handoff.
  3. 3. Starter templates Accepted

    Publish decision summary for starter templates.

    • Starter README Accepted
      Kind
      documentation
      Path
      src/content/essay-starters/static-first/README.md
      Gate
      Focused publish decision gate for starter readme.
    • MDX template Accepted
      Kind
      template
      Path
      src/content/essay-starters/static-first/index.mdx.template
      Gate
      Focused publish decision gate for starter mdx template.
    • Config template Accepted
      Kind
      template
      Path
      src/content/essay-starters/static-first/essay.config.ts.template
      Gate
      Focused publish decision gate for starter config template.
    • Starter manifest data template Accepted
      Kind
      template
      Path
      src/content/essay-starters/static-first/data/article-starter-manifest.json.template
      Gate
      Focused publish decision gate for starter data template.
    • Starter manifest schema template Accepted
      Kind
      template
      Path
      src/content/essay-starters/static-first/data/articleStarterManifest.ts.template
      Gate
      Focused publish decision gate for starter schema template.
    • Starter workflow data template Accepted
      Kind
      template
      Path
      src/content/essay-starters/static-first/data/article-starter-workflow.json.template
      Gate
      Focused publish decision gate for starter workflow data template.
    • Starter workflow schema template Accepted
      Kind
      template
      Path
      src/content/essay-starters/static-first/data/articleStarterWorkflow.ts.template
      Gate
      Focused publish decision gate for starter workflow schema template.
    • Starter readiness component placement Accepted
      Kind
      template
      Path
      src/content/essay-starters/static-first/index.mdx.template
      Gate
      Focused publish decision gate for starter readiness component template.
    • Starter handoff component placement Accepted
      Kind
      template
      Path
      src/content/essay-starters/static-first/index.mdx.template
      Gate
      Focused publish decision gate for starter handoff component template.
  4. 4. Verification handoff Accepted

    Publish decision summary for verification handoff.

    • Article unit test Accepted
      Kind
      test
      Path
      src/content/essays/staticFirstEssay.test.ts
      Gate
      Focused publish decision gate for article unit test.
    • Starter unit test Accepted
      Kind
      test
      Path
      src/content/essay-starters/articleStarter.test.ts
      Gate
      Focused publish decision gate for starter unit test.
    • Starter instantiation proof Accepted
      Kind
      validator
      Path
      scripts/prove_static_first_starter_instantiation.py
      Gate
      Focused publish decision gate for starter instantiation proof.
    • Browser smoke Accepted
      Kind
      test
      Path
      tests/home.spec.ts
      Gate
      Focused publish decision gate for browser smoke.
    • Scaffold validator Accepted
      Kind
      validator
      Path
      scripts/validate_tutorial_scaffold.py
      Gate
      Focused publish decision gate for scaffold validator.
Source
blueprint-001
Accepted
The publish decision accepts local starter manifest records tied to blueprint-001.
Not Claimed
No remote source, CMS workflow, generated starter package, or deployment proof is accepted for starter manifest.

Starter Workflow

Static-First Starter Walkthrough Starter Workflow

Accepted starter workflow for turning the copied folder into a source-registered published article with a publish decision.

  1. 1. Copy starter Accepted

    Copy the starter folder into the essay collection and keep content, data, assets, and figures together.

    Artifact
    src/content/essay-starters/static-first/
    Gate
    Starter unit coverage verifies the source folder contract before a new article copies it.
  2. 2. Replace placeholders Accepted

    Replace frontmatter, prose, and config tokens before the route claims published or published status.

    Artifact
    index.mdx and essay.config.ts
    Gate
    Focused article tests reject unresolved placeholder tokens and verify the rendered route copy.
  3. 3. Register source Accepted

    Tie accepted claims to source registry IDs and keep rejected platform boundaries in article-owned data.

    Artifact
    source_registry.yaml and data/source-boundary.json
    Gate
    Source-boundary parsing and scaffold validation keep the article tied to registered local sources.
  4. 4. Wire article data Accepted

    Populate local JSON artifacts, figure-proof metadata, and matching loaders before shared primitives and article-specific sections render the publication record.

    Artifact
    data/starter-proof-ladder.json, data/figure-proofs.json, data/*.json, and data/*.ts
    Gate
    npm run test -- StarterProofLadderFlow StarterProofGateInspector starterWalkthrough articleStarter verifies data order, IDs, proof-ladder rendering, figure metadata, and starter template alignment.
  5. 5. Render route primitives Accepted

    Render source, proof, starter, release, workflow, static figure, and scoped interaction primitives in the article route.

    Artifact
    FigureProof.astro, StarterProofLadderFlow.tsx, StarterProofGateInspector.tsx, ArticleStarterHandoff.astro, and index.mdx#publish-readiness
    Gate
    Focused browser smoke verifies the data-backed figure, hydrated inspector, shared markers, and zero nested Astro islands inside the starter workflow, starter-readiness rollup, and starter-handoff packet.
  6. 6. Close local gates Accepted

    Run focused unit, type, build, browser, Storybook, diff, scaffold, commit, and push gates before handoff.

    Artifact
    tests/home.spec.ts, run_log.md, state.md, todo.md, evidence_ledger.yaml
    Gate
    Scaffold validation and run-log closeout record the accepted artifact and next unchecked product todo.
Source
blueprint-001
Accepted
The copied starter workflow has reached a visible published route with source registration, article-owned data, local figures, scoped interaction state, and a publish decision.
Not Claimed
No starter package generator, runtime filesystem scan, remote template fetch, CMS task store, or production release decision is accepted.

Publication Workflow

Static-First Starter Walkthrough Publication Workflow

The workflow records the accepted publish decision and catalog inclusion.

  1. 1. Published shell Accepted

    The article route renders real prose, local proof sections, and published frontmatter instead of starter placeholders.

    Artifact
    index.mdx
    Gate
    Focused unit and browser checks verify published status, route copy, section navigation, and article metadata.
  2. 2. Source boundary Accepted

    The source-boundary record accepts blueprint-001, starter templates, and walkthrough-owned proof records.

    Artifact
    data/source-boundary.json
    Gate
    Focused unit coverage asserts accepted and rejected source-boundary claims.
  3. 3. Starter proof ladder Accepted

    The first article-specific data artifact is rendered visibly before any figure proof is claimed.

    Artifact
    data/starter-proof-ladder.json
    Gate
    Focused unit and browser checks verify the proof ladder.
  4. 4. Publish readiness Accepted

    The publish decision accepts only local source, data, figure, interaction, and verification records.

    Artifact
    index.mdx#publish-readiness
    Gate
    Focused unit and browser checks verify the visible Publish Readiness section and accepted checklist rollup.
  5. 5. Claim ledger Accepted

    The claim ledger renders article-owned source claim decisions in the readiness section.

    Artifact
    ArticleClaimLedger.astro
    Gate
    Focused unit coverage parses the claim-ledger data and scaffold validation checks ledger integrity.
  6. 6. Claim map Accepted

    The claim map renders article-owned claim-to-evidence routes in the readiness section.

    Artifact
    ArticleClaimMap.astro
    Gate
    Focused unit coverage parses the claim-map data and scaffold validation checks ledger integrity.
  7. 7. Evidence trail Accepted

    The evidence trail renders local artifacts and gates tied to blueprint-001.

    Artifact
    ArticleEvidenceTrail.astro
    Gate
    Focused unit coverage parses the evidence-trail data and scaffold validation checks ledger integrity.
  8. 8. Proof manifest Accepted

    The proof manifest records the source boundary, artifact index, data proof, static figure, and hydrated inspector.

    Artifact
    ArticleProofManifest.astro
    Gate
    Focused unit coverage verifies accepted proof-manifest entries for the local proof boundary.
  9. 9. Release handoff Accepted

    The release handoff records the published route, local proofs, validation records, and catalog decision.

    Artifact
    data/article-release-handoff.json
    Gate
    Focused unit coverage verifies handoff items for the local proof boundary.
  10. 10. Release readiness Accepted

    The release-readiness rollup is accepted for local catalog publication while deployment remains out of scope.

    Artifact
    ArticleReleaseReadiness.astro
    Gate
    Focused browser coverage verifies the accepted rollup and accepted checklist metric.
  11. 11. Starter manifest Accepted

    The starter manifest records the copied route files, local data, and figure folders.

    Artifact
    ArticleStarterManifest.astro
    Gate
    Focused unit coverage verifies the starter-manifest entries and artifact paths.
  12. 12. Starter workflow Accepted

    The starter workflow records copy, source registration, data wiring, rendering, and local gate closeout.

    Artifact
    ArticleStarterWorkflow.astro
    Gate
    Focused unit coverage verifies all starter workflow steps are accepted.
  13. 13. Starter readiness Accepted

    The starter-readiness rollup is accepted because the starter manifest and workflow records are accepted.

    Artifact
    ArticleStarterReadiness.astro
    Gate
    Focused browser coverage verifies the starter-readiness and starter-handoff rollups stay accepted.
  14. 14. Starter handoff Accepted

    The starter handoff records the local proof pass and still rejects generated packages, dashboards, and remote template fetches.

    Artifact
    ArticleStarterHandoff.astro
    Gate
    Focused browser coverage verifies the starter-handoff packet remains visible and accepted overall.
  15. 15. Starter proof gate inspector Accepted

    The first article-specific interaction is rendered through a scoped hydrated island after catalog publication is accepted.

    Artifact
    figures/StarterProofGateInspector/StarterProofGateInspector.tsx
    Gate
    Focused unit and browser checks verify the inspector model, hydration, selected state, and reset behavior.
Source
blueprint-001
Accepted
The publish decision accepts checked-in published route content, source-boundary records, article-owned proof data, static and hydrated figures, and focused local verification.
Not Claimed
No deployment proof, production release decision, remote source fetch, CMS workflow, generated starter package, or new source topic is accepted.

Authoring Flow

Static-First Starter Walkthrough Authoring Flow

The flow keeps source, artifact, and verification checkpoints in article-owned data before the route claims publication readiness.

  1. 1. Source-register the claim Accepted

    Publish decision checkpoint for source register.

    Artifact
    data/source-boundary.json
    Gate
    Focused publish decision gate for source register.
  2. 2. Localize article artifacts Accepted

    Publish decision checkpoint for localize artifacts.

    Artifact
    data/
    Gate
    Focused publish decision gate for localize artifacts.
  3. 3. Render static primitives Accepted

    Publish decision checkpoint for render static primitives.

    Artifact
    index.mdx
    Gate
    Focused publish decision gate for render static primitives.
  4. 4. Close verification gates Accepted

    Publish decision checkpoint for close verification.

    Artifact
    tests
    Gate
    Focused publish decision gate for close verification.
Source
blueprint-001
Accepted
The publish decision accepts local authoring flow records tied to blueprint-001.
Not Claimed
No remote source, CMS workflow, generated starter package, or deployment proof is accepted for authoring flow.

Article Checklist

Static-First Starter Walkthrough Publication Checklist

The checklist records the accepted publish decision while the route is included in the published catalog.

  1. Frontmatter and catalog Accepted

    Frontmatter names the published route, source-backed summary, and accepted catalog inclusion.

    Gate: Focused unit and browser checks verify published status and published route rendering.
  2. Source boundary Accepted

    data/source-boundary.json accepts only blueprint-001, checked-in starter templates, and walkthrough-owned proof records.

    Gate: Focused unit coverage asserts the accepted and rejected source-boundary arrays.
  3. Article-owned data Accepted

    data/starter-proof-ladder.json and data/figure-proofs.json feed the visible table, static figure, and hydrated inspector.

    Gate: Focused model, unit, and browser checks verify the data contract and rendered outputs.
  4. Interactive scope Accepted

    The only hydrated island is StarterProofGateInspector, which keeps source metadata in FigureProof and local state inside the island.

    Gate: Focused browser coverage verifies one island, selected proof-layer state, data-artifact detail, and reset behavior.
  5. Verification stack Accepted

    The publish decision is covered by starter instantiation proof, focused unit and browser checks, typecheck, build, Storybook, diff check, and scaffold validation.

    Gate: TUT-097 closeout records the passing focused app and scaffold gates.
Source
blueprint-001
Accepted
The publish decision accepts checked-in published frontmatter, source-boundary data, article-owned proof records, scoped interaction behavior, and local verification gates.
Not Claimed
No production deployment proof, remote source fetch, CMS workflow, generated starter package, or new source topic is accepted.

Related Topics

More On Shared Topics

All Essays