Authoring Pipeline Draft

This published route proves the local authoring pipeline can move from a generated shell to article-owned data, a static data-backed figure, a hydrated proof inspector, a readiness packet, and catalog inclusion without leaving the static-first boundary.

Question

How can an explorable essay stay static-first while still giving each article room for typed data, custom figures, hydrated islands, and proof records?

Local Model

The local model is a five-layer stack: MDX owns prose and placement, shared article chrome owns the publication frame, route-local figures own interaction logic, checked-in data artifacts feed the browser, and verification gates keep each claim testable.

Mechanism

The first article-specific data artifact replaces the generated mechanism placeholder with a source-backed map of platform layers, local owners, and proof gates.

Pipeline Proof Ladder

The ladder is derived from BLUEPRINT.md sections 5, 7, 14, and 19: platform layers, the article folder contract, data-pipeline rules, and the build sequence.

Layer	Owner	Gate
Content layer	`index.mdx`	Focused browser coverage verifies the published route renders the article-specific proof ladder.
Article folder contract	`data/ and figures/`	Focused unit coverage verifies the data file, loader, artifact index, and source boundary stay article-owned.
Data artifact layer	`data/pipeline-proof-ladder.json`	Zod parsing rejects missing, reordered, or malformed proof-ladder steps.
Verification layer	`authoringPipelineDraft.test.ts and authoring-pipeline-draft.spec.ts`	The autoresearch closeout keeps unit, browser, scaffold, typecheck, and build gates passing.

Figure 1. Authoring Pipeline Proof Ladder Flow A static React/SVG figure consumes the article-owned pipeline proof ladder and turns local content, folder, data, and verification owners into a visual proof path.

Content layerindex.mdxFocused browser coverage verifies the published route renders the article-specific proof ladder.
Article folder contractdata/ and figures/Focused unit coverage verifies the data file, loader, artifact index, and source boundary stay article-owned.
Data artifact layerdata/pipeline-proof-ladder.jsonZod parsing rejects missing, reordered, or malformed proof-ladder steps.
Verification layerauthoringPipelineDraft.test.ts and authoring-pipeline-draft.spec.tsThe autoresearch closeout keeps unit, browser, scaffold, typecheck, and build gates passing.

Figure 1. Authoring Pipeline Proof Ladder Flow proof metadata

Source: blueprint-001
Locator: BLUEPRINT.md sections 5, 7, 14, and 19
Gate: Focused unit and browser checks verify the data-backed static figure and source-gate wrapper.

FigureProof renders title, caption, and source metadata around PipelineProofLadderFlow.
PipelineProofLadderFlow consumes data/pipeline-proof-ladder.json without client hydration.
Playwright verifies non-empty SVG nodes, links, and proof-gate legend records.

Proof Gate Inspector

The interactive inspector keeps the proof ladder local: each selection exposes the article owner, claim, and gate backed by the checked-in data artifact.

Interactive Figure 2. Authoring Pipeline Proof Gate Inspector A hydrated React island consumes the article-owned pipeline proof ladder and lets readers inspect each local owner, claim, and gate without introducing remote state.

Pipeline proof layer

1 Content layer2 Article folder contract3 Data artifact layer4 Verification layer

Content layer

Owner: index.mdx
Claim: The published route owns prose, section placement, and visible proof calls while staying static-first.
Gate: Focused browser coverage verifies the published route renders the article-specific proof ladder.

Selected pipeline layer: Content layer

Interactive Figure 2. Authoring Pipeline Proof Gate Inspector proof metadata

Source: blueprint-001
Locator: BLUEPRINT.md sections 5, 7, 14, and 19
Gate: Focused unit and browser checks verify the scoped hydrated inspector and source-gate wrapper.

FigureProof keeps source metadata outside the hydrated React island.
PipelineProofGateInspector hydrates only the proof-layer controls with client:visible.
Playwright verifies the selected layer state, data artifact detail, and reset path.

Limits

This published route proves local authoring mechanics and catalog inclusion only. It does not claim production deployment, remote source fetching, CMS workflow, generated starter packages, or broader article completion.

Source Boundary

The prose in this pass comes from the registered platform blueprint: core architecture, article folder ownership, MDX placement rules, precomputed data artifacts, and the build sequence from a new Astro project to a tested essay route. The catalog entry is accepted for this route only.

Source Boundary

Boundary Record

Source: blueprint-001
Path: /Users/eduardodiniz/tutorials/BLUEPRINT.md

Accepted

Uses registered BLUEPRINT.md guidance and checked-in static-first starter templates only.
The pipeline proof ladder is an article-owned data artifact derived from BLUEPRINT.md sections 5, 7, 14, and 19.
The pipeline proof ladder flow is an article-local static figure that consumes the article-owned proof ladder without client hydration.
The pipeline proof gate inspector is an article-local hydrated island derived from the article-owned proof ladder and BLUEPRINT.md sections 5, 7, 14, and 19.

Not Claimed

Rejects production deployment proof, remote downloads, CMS workflow, generated reports, generated starter packages, and additional article-specific figures or interactions beyond the accepted proof-ladder flow and inspector until separately proven.

Publish Readiness

The publish decision accepts the published frontmatter, catalog inclusion, source boundary, proof ladder data, static flow figure, hydrated inspector, and focused validation records. Deployment proof, CMS workflow, remote source fetching, and generated starter packages stay outside this proof.

Promotion readiness

Authoring Pipeline Promotion Readiness Gate

Ready: 6/6 gates are clear before a published status boundary is changed.

Route Metadata Passed

Frontmatter slug and status must match the promotion-readiness target before changing publication state.
Authoring Preview Registry Passed

The local authoring registry must expose source IDs, figure count, status, and readiness gates for the target article.
Accepted Figure Workbench Coverage Passed

Every target figure must have accepted workbench coverage with CI-safe browser and baseline visual QA contracts.
Public Catalog Boundary Passed

Draft targets must remain excluded from the public catalog; published targets must appear in it.
Release Record Statuses Passed

Checklist, proof, verification, workflow, and handoff records must be accepted before publication.
Focused Validation Commands Passed

The promotion packet must name every focused command required before any status change.

Required Commands

npm run test -- src/content/essays/authoringPipelineDraft.test.ts src/lib/articlePromotionReadiness.test.ts src/lib/articlePreviewRegistry.test.ts src/data/figureWorkbenchCoverage.test.ts Proves article metadata, readiness evaluation, registry metadata, and accepted figure workbench coverage.
npm run test:browser:ci -- tests/article-preview-registry.spec.ts Proves the authoring-preview registry exposes the ready row and copy-ready command packet.
npm run test:browser:ci -- tests/authoring-pipeline-draft.spec.ts Proves the published article route renders the promotion-readiness gate and local proof surfaces.
npm run test:browser:ci -- tests/figure-authoring-workbench.spec.ts Proves accepted workbench coverage for the article-specific static and hydrated figures.
npm run typecheck Proves Astro content and TypeScript imports after the promotion-readiness packet is wired.
npm run build Proves the static route builds with the promotion-readiness gate rendered.
npm run quality:changed -- --summary-json /tmp/tutorial-tut322-quality-summary.json Proves changed platform, article, registry, and browser surfaces through the shared focused runner.
python3 scripts/validate_tutorial_scaffold.py Proves tutorial scaffold metadata and ledgers stay aligned.
git diff --check Proves tracked text changes have no whitespace errors before closeout.

Artifact Index

Authoring Pipeline Draft Artifact Index

The index names the local content, data, primitive, and verification files that must stay aligned before the route claims publication readiness.

1. Content shell Accepted

The content shell records MDX placement, config, assets, and route-local figure scaffold paths from the article folder contract.
- Artifact
  
  index.mdx
  
  Kind
  
  content
  
  Gate
  
  The article folder contract keeps index.mdx in the local published packet.
- Artifact
  
  essay.config.ts
  
  Kind
  
  configuration
  
  Gate
  
  The article folder contract keeps essay.config.ts in the local published packet.
- Artifact
  
  assets/.gitkeep
  
  Kind
  
  scaffold
  
  Gate
  
  The article folder contract keeps assets/.gitkeep in the local published packet.
- Artifact
  
  figures/.gitkeep
  
  Kind
  
  scaffold
  
  Gate
  
  The article folder contract keeps figures/.gitkeep in the local published packet.
- Artifact
  
  figures/PipelineProofLadderFlow/PipelineProofLadderFlow.tsx
  
  Kind
  
  figure
  
  Gate
  
  The article folder contract keeps figures/PipelineProofLadderFlow/PipelineProofLadderFlow.tsx in the local published packet.
- Artifact
  
  figures/PipelineProofLadderFlow/PipelineProofLadderFlow.module.css
  
  Kind
  
  support
  
  Gate
  
  The article folder contract keeps figures/PipelineProofLadderFlow/PipelineProofLadderFlow.module.css in the local published packet.
- Artifact
  
  figures/PipelineProofLadderFlow/PipelineProofLadderFlow.test.ts
  
  Kind
  
  support
  
  Gate
  
  The article folder contract keeps figures/PipelineProofLadderFlow/PipelineProofLadderFlow.test.ts in the local published packet.
- Artifact
  
  figures/PipelineProofLadderFlow/model.ts
  
  Kind
  
  support
  
  Gate
  
  The article folder contract keeps figures/PipelineProofLadderFlow/model.ts in the local published packet.
- Artifact
  
  figures/PipelineProofGateInspector/PipelineProofGateInspector.tsx
  
  Kind
  
  figure
  
  Gate
  
  The article folder contract keeps figures/PipelineProofGateInspector/PipelineProofGateInspector.tsx in the local published packet.
- Artifact
  
  figures/PipelineProofGateInspector/PipelineProofGateInspector.module.css
  
  Kind
  
  support
  
  Gate
  
  The article folder contract keeps figures/PipelineProofGateInspector/PipelineProofGateInspector.module.css in the local published packet.
- Artifact
  
  figures/PipelineProofGateInspector/PipelineProofGateInspector.test.ts
  
  Kind
  
  support
  
  Gate
  
  The article folder contract keeps figures/PipelineProofGateInspector/PipelineProofGateInspector.test.ts in the local published packet.
- Artifact
  
  figures/PipelineProofGateInspector/model.ts
  
  Kind
  
  support
  
  Gate
  
  The article folder contract keeps figures/PipelineProofGateInspector/model.ts in the local published packet.
2. Article data Accepted

Article data records keep checked-in JSON, typed loaders, source boundaries, proof records, and readiness gates local to the draft.
- Artifact
  
  data/source-boundary.json
  
  Kind
  
  data
  
  Gate
  
  Typed data loading and focused tests keep data/source-boundary.json aligned with the readiness packet.
- Artifact
  
  data/article-sections.json
  
  Kind
  
  data
  
  Gate
  
  Typed data loading and focused tests keep data/article-sections.json aligned with the readiness packet.
- Artifact
  
  data/article-artifact-index.json
  
  Kind
  
  data
  
  Gate
  
  Typed data loading and focused tests keep data/article-artifact-index.json aligned with the readiness packet.
- Artifact
  
  data/article-checklist.json
  
  Kind
  
  data
  
  Gate
  
  Typed data loading and focused tests keep data/article-checklist.json aligned with the readiness packet.
- Artifact
  
  data/article-starter-manifest.json
  
  Kind
  
  data
  
  Gate
  
  Typed data loading and focused tests keep data/article-starter-manifest.json aligned with the readiness packet.
- Artifact
  
  data/article-starter-workflow.json
  
  Kind
  
  data
  
  Gate
  
  Typed data loading and focused tests keep data/article-starter-workflow.json aligned with the readiness packet.
- Artifact
  
  data/article-evidence-trail.json
  
  Kind
  
  data
  
  Gate
  
  Typed data loading and focused tests keep data/article-evidence-trail.json aligned with the readiness packet.
- Artifact
  
  data/article-claim-ledger.json
  
  Kind
  
  data
  
  Gate
  
  Typed data loading and focused tests keep data/article-claim-ledger.json aligned with the readiness packet.
- Artifact
  
  data/article-claim-map.json
  
  Kind
  
  data
  
  Gate
  
  Typed data loading and focused tests keep data/article-claim-map.json aligned with the readiness packet.
- Artifact
  
  data/article-proof-manifest.json
  
  Kind
  
  data
  
  Gate
  
  Typed data loading and focused tests keep data/article-proof-manifest.json aligned with the readiness packet.
- Artifact
  
  data/article-verification-matrix.json
  
  Kind
  
  data
  
  Gate
  
  Typed data loading and focused tests keep data/article-verification-matrix.json aligned with the readiness packet.
- Artifact
  
  data/article-release-handoff.json
  
  Kind
  
  data
  
  Gate
  
  Typed data loading and focused tests keep data/article-release-handoff.json aligned with the readiness packet.
- Artifact
  
  data/publication-workflow.json
  
  Kind
  
  data
  
  Gate
  
  Typed data loading and focused tests keep data/publication-workflow.json aligned with the readiness packet.
- Artifact
  
  data/authoring-flow.json
  
  Kind
  
  data
  
  Gate
  
  Typed data loading and focused tests keep data/authoring-flow.json aligned with the readiness packet.
- Artifact
  
  data/pipeline-proof-ladder.json
  
  Kind
  
  data
  
  Gate
  
  Typed data loading and focused tests keep data/pipeline-proof-ladder.json aligned with the readiness packet.
- Artifact
  
  data/figure-proofs.json
  
  Kind
  
  data
  
  Gate
  
  Typed data loading and focused tests keep data/figure-proofs.json aligned with the readiness packet.
- Artifact
  
  data/promotion-readiness.json
  
  Kind
  
  data
  
  Gate
  
  Typed data loading and focused tests keep data/promotion-readiness.json aligned with the ready command packet.
- Artifact
  
  data/sourceBoundary.ts
  
  Kind
  
  loader
  
  Gate
  
  Typed data loading and focused tests keep data/sourceBoundary.ts aligned with the readiness packet.
- Artifact
  
  data/articleSections.ts
  
  Kind
  
  loader
  
  Gate
  
  Typed data loading and focused tests keep data/articleSections.ts aligned with the readiness packet.
- Artifact
  
  data/articleArtifactIndex.ts
  
  Kind
  
  loader
  
  Gate
  
  Typed data loading and focused tests keep data/articleArtifactIndex.ts aligned with the readiness packet.
- Artifact
  
  data/articleChecklist.ts
  
  Kind
  
  loader
  
  Gate
  
  Typed data loading and focused tests keep data/articleChecklist.ts aligned with the readiness packet.
- Artifact
  
  data/articleStarterManifest.ts
  
  Kind
  
  loader
  
  Gate
  
  Typed data loading and focused tests keep data/articleStarterManifest.ts aligned with the readiness packet.
- Artifact
  
  data/articleStarterWorkflow.ts
  
  Kind
  
  loader
  
  Gate
  
  Typed data loading and focused tests keep data/articleStarterWorkflow.ts aligned with the readiness packet.
- Artifact
  
  data/articleEvidenceTrail.ts
  
  Kind
  
  loader
  
  Gate
  
  Typed data loading and focused tests keep data/articleEvidenceTrail.ts aligned with the readiness packet.
- Artifact
  
  data/articleClaimLedger.ts
  
  Kind
  
  loader
  
  Gate
  
  Typed data loading and focused tests keep data/articleClaimLedger.ts aligned with the readiness packet.
- Artifact
  
  data/articleClaimMap.ts
  
  Kind
  
  loader
  
  Gate
  
  Typed data loading and focused tests keep data/articleClaimMap.ts aligned with the readiness packet.
- Artifact
  
  data/articleProofManifest.ts
  
  Kind
  
  loader
  
  Gate
  
  Typed data loading and focused tests keep data/articleProofManifest.ts aligned with the readiness packet.
- Artifact
  
  data/articleVerificationMatrix.ts
  
  Kind
  
  loader
  
  Gate
  
  Typed data loading and focused tests keep data/articleVerificationMatrix.ts aligned with the readiness packet.
- Artifact
  
  data/articleReleaseHandoff.ts
  
  Kind
  
  loader
  
  Gate
  
  Typed data loading and focused tests keep data/articleReleaseHandoff.ts aligned with the readiness packet.
- Artifact
  
  data/publicationWorkflow.ts
  
  Kind
  
  loader
  
  Gate
  
  Typed data loading and focused tests keep data/publicationWorkflow.ts aligned with the readiness packet.
- Artifact
  
  data/authoringFlow.ts
  
  Kind
  
  loader
  
  Gate
  
  Typed data loading and focused tests keep data/authoringFlow.ts aligned with the readiness packet.
- Artifact
  
  data/pipelineProofLadder.ts
  
  Kind
  
  loader
  
  Gate
  
  Typed data loading and focused tests keep data/pipelineProofLadder.ts aligned with the readiness packet.
- Artifact
  
  data/figureProofs.ts
  
  Kind
  
  loader
  
  Gate
  
  Typed data loading and focused tests keep data/figureProofs.ts aligned with the readiness packet.
- Artifact
  
  data/promotionReadiness.ts
  
  Kind
  
  loader
  
  Gate
  
  Typed data loading and focused tests keep data/promotionReadiness.ts aligned with the ready command packet.
3. Shared primitives Accepted

Shared primitives render article-owned records while the data stays owned by this published route.
- Artifact
  
  src/components/FigureFrame.astro
  
  Kind
  
  component
  
  Gate
  
  The shared primitive at src/components/FigureFrame.astro renders article-owned records without moving data out of the draft.
- Artifact
  
  src/components/FigureFrame.css
  
  Kind
  
  style
  
  Gate
  
  The shared primitive at src/components/FigureFrame.css renders article-owned records without moving data out of the draft.
- Artifact
  
  src/components/FigureProof.astro
  
  Kind
  
  component
  
  Gate
  
  The shared primitive at src/components/FigureProof.astro renders article-owned records without moving data out of the draft.
- Artifact
  
  src/components/FigureControls.tsx
  
  Kind
  
  component
  
  Gate
  
  The shared primitive at src/components/FigureControls.tsx renders article-owned records without moving data out of the draft.
- Artifact
  
  src/components/FigureControls.module.css
  
  Kind
  
  style
  
  Gate
  
  The shared primitive at src/components/FigureControls.module.css renders article-owned records without moving data out of the draft.
- Artifact
  
  src/components/ArticleSectionNav.astro
  
  Kind
  
  component
  
  Gate
  
  The shared primitive at src/components/ArticleSectionNav.astro renders article-owned records without moving data out of the draft.
- Artifact
  
  src/components/ArticleSourceBoundary.astro
  
  Kind
  
  component
  
  Gate
  
  The shared primitive at src/components/ArticleSourceBoundary.astro renders article-owned records without moving data out of the draft.
- Artifact
  
  src/components/ArticleArtifactIndex.astro
  
  Kind
  
  component
  
  Gate
  
  The shared primitive at src/components/ArticleArtifactIndex.astro renders article-owned records without moving data out of the draft.
- Artifact
  
  src/components/ArticleEvidenceTrail.astro
  
  Kind
  
  component
  
  Gate
  
  The shared primitive at src/components/ArticleEvidenceTrail.astro renders article-owned records without moving data out of the draft.
- Artifact
  
  src/components/ArticleClaimLedger.astro
  
  Kind
  
  component
  
  Gate
  
  The shared primitive at src/components/ArticleClaimLedger.astro renders article-owned records without moving data out of the draft.
- Artifact
  
  src/components/ArticleClaimMap.astro
  
  Kind
  
  component
  
  Gate
  
  The shared primitive at src/components/ArticleClaimMap.astro renders article-owned records without moving data out of the draft.
- Artifact
  
  src/components/ArticleProofManifest.astro
  
  Kind
  
  component
  
  Gate
  
  The shared primitive at src/components/ArticleProofManifest.astro renders article-owned records without moving data out of the draft.
- Artifact
  
  src/components/ArticleVerificationMatrix.astro
  
  Kind
  
  component
  
  Gate
  
  The shared primitive at src/components/ArticleVerificationMatrix.astro renders article-owned records without moving data out of the draft.
- Artifact
  
  src/components/ArticleReleaseHandoff.astro
  
  Kind
  
  component
  
  Gate
  
  The shared primitive at src/components/ArticleReleaseHandoff.astro renders article-owned records without moving data out of the draft.
- Artifact
  
  src/components/ArticleReleaseReadiness.astro
  
  Kind
  
  component
  
  Gate
  
  The shared primitive at src/components/ArticleReleaseReadiness.astro renders article-owned records without moving data out of the draft.
- Artifact
  
  src/components/ArticleStarterManifest.astro
  
  Kind
  
  component
  
  Gate
  
  The shared primitive at src/components/ArticleStarterManifest.astro renders article-owned records without moving data out of the draft.
- Artifact
  
  src/components/ArticleStarterWorkflow.astro
  
  Kind
  
  component
  
  Gate
  
  The shared primitive at src/components/ArticleStarterWorkflow.astro renders article-owned records without moving data out of the draft.
- Artifact
  
  src/components/ArticleStarterReadiness.astro
  
  Kind
  
  component
  
  Gate
  
  The shared primitive at src/components/ArticleStarterReadiness.astro renders article-owned records without moving data out of the draft.
- Artifact
  
  src/components/ArticleStarterHandoff.astro
  
  Kind
  
  component
  
  Gate
  
  The shared primitive at src/components/ArticleStarterHandoff.astro renders article-owned records without moving data out of the draft.
- Artifact
  
  src/components/ArticlePublicationWorkflow.astro
  
  Kind
  
  component
  
  Gate
  
  The shared primitive at src/components/ArticlePublicationWorkflow.astro renders article-owned records without moving data out of the draft.
- Artifact
  
  src/components/ArticlePromotionReadiness.astro
  
  Kind
  
  component
  
  Gate
  
  The shared primitive at src/components/ArticlePromotionReadiness.astro renders article-owned command packets without moving data out of the draft.
- Artifact
  
  src/components/ArticlePublicationQa.astro
  
  Kind
  
  component
  
  Gate
  
  The shared primitive at src/components/ArticlePublicationQa.astro renders article-owned records without moving data out of the draft.
- Artifact
  
  src/components/ArticleAuthoringFlow.astro
  
  Kind
  
  component
  
  Gate
  
  The shared primitive at src/components/ArticleAuthoringFlow.astro renders article-owned records without moving data out of the draft.
- Artifact
  
  src/components/ArticleChecklist.astro
  
  Kind
  
  component
  
  Gate
  
  The shared primitive at src/components/ArticleChecklist.astro renders article-owned records without moving data out of the draft.
- Artifact
  
  src/lib/articlePromotionReadiness.ts
  
  Kind
  
  helper
  
  Gate
  
  The shared helper evaluates article-owned promotion-readiness records before registry packet exposure.
- Artifact
  
  src/lib/articlePromotionReadiness.test.ts
  
  Kind
  
  test
  
  Gate
  
  Focused validation keeps src/lib/articlePromotionReadiness.test.ts tied to promotion-readiness command packets.
4. Verification handoff Accepted

Verification handoff records point to the focused unit, browser, starter, and scaffold gates for the published packet.
- Artifact
  
  tests/home.spec.ts
  
  Kind
  
  test
  
  Gate
  
  Focused validation keeps tests/home.spec.ts tied to the local published packet.
- Artifact
  
  scripts/prove_static_first_starter_instantiation.py
  
  Kind
  
  validator
  
  Gate
  
  Focused validation keeps scripts/prove_static_first_starter_instantiation.py tied to the local published packet.
- Artifact
  
  scripts/validate_tutorial_scaffold.py
  
  Kind
  
  validator
  
  Gate
  
  Focused validation keeps scripts/validate_tutorial_scaffold.py tied to the local published packet.

Source: blueprint-001
Accepted: The artifact index accepts checked-in article files, data loaders, shared primitives, and focused verification paths from the local published packet.
Not Claimed: No untracked generated output, remote source fetch, CMS artifact, deployment artifact, or catalog distribution path beyond the local published route entry is claimed by the artifact index.

Claim Ledger

Authoring Pipeline Draft Claim Ledger

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

1. Source registration Accepted

The published route ties platform claims to the registered blueprint source before it renders article-owned proof records.

Source

blueprint-001, BLUEPRINT.md sections 5, 7, 14, and 19

Artifact

source_registry.yaml

Decision

Keep source identity in source_registry.yaml and mirrored article data.

Gate

Focused unit and scaffold checks keep source IDs tied to blueprint-001.
2. Article data ownership Accepted

Checked-in JSON and typed loaders remain article-owned under data/ before shared primitives render them.

Source

blueprint-001, BLUEPRINT.md sections 5, 7, 14, and 19

Artifact

data/article-claim-ledger.json

Decision

Keep readiness records local to the draft instead of introducing a global data registry.

Gate

Unit coverage parses article-owned data and verifies the rendered readiness packet.
3. Evidence route Accepted

The evidence trail maps local source claims to artifacts and gates visible in the readiness section.

Source

blueprint-001, BLUEPRINT.md sections 5, 7, 14, and 19

Artifact

data/article-evidence-trail.json

Decision

Use data/article-evidence-trail.json as the draft evidence route for this pass.

Gate

Browser coverage renders the readiness section while preserving published catalog inclusion.
4. Release decision Accepted

The release handoff records local readiness only; deployment remains outside this proof.

Source

blueprint-001, BLUEPRINT.md sections 5, 7, 14, and 19

Artifact

data/article-release-handoff.json

Decision

Keep the release decision published until a separate catalog-publication task.

Gate

Release handoff data names accepted local gates and rejected publication boundaries.
5. Claim map route Accepted

The claim map connects claims, evidence, verification, and handoff records for the local packet.

Source

blueprint-001, BLUEPRINT.md sections 5, 7, 14, and 19

Artifact

data/article-claim-map.json

Decision

Keep traceability in data/article-claim-map.json for the readiness pass.

Gate

Focused tests verify claim map IDs against evidence, verification, and handoff IDs.
6. Proof manifest route Accepted

The proof manifest names the source, data, figure, interaction, and readiness proofs accepted for the draft.

Source

blueprint-001, BLUEPRINT.md sections 5, 7, 14, and 19

Artifact

data/article-proof-manifest.json

Decision

Use data/article-proof-manifest.json as the local proof inventory for this pass.

Gate

Focused tests verify proof entries for the data artifact, static figure, hydrated inspector, and validation packet.

Source: blueprint-001
Accepted: The claim ledger accepts local source registration, article data ownership, evidence, claim map, proof manifest, and release-handoff records for the published readiness packet.
Not Claimed: No deployment proof, remote source fetch, CMS workflow, generated package, or broader article-completion claim is accepted by the claim ledger.

Claim Map

Authoring Pipeline Draft Claim Map

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

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

Trace source registration from blueprint-001 through evidence, verification, and the source-boundary handoff.
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

Trace article data ownership from checked-in data artifacts through source-data verification and claim-ledger handoff.
3. 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

Trace the evidence trail through browser-visible readiness records and release handoff evidence.
4. 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

Trace the published release decision through closeout gates and queue-state handoff records.
5. 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

Trace the claim map artifact through source-data gates and its own handoff record.
6. 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

Trace the proof manifest artifact through source-data gates and its proof-manifest handoff record.

Source: blueprint-001
Accepted: The claim map accepts local links from each selected claim to evidence, verification, handoff, and artifact records in the published readiness packet.
Not Claimed: The claim map does not claim global provenance routing, remote source verification, deployment proof, or CI dashboard state.

Evidence Trail

Authoring Pipeline Draft Evidence Trail

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

1. Platform claim Accepted

The published route uses the five-layer platform stack: MDX content, shared shell, article figures, data artifacts, and verification gates.

Source

blueprint-001, BLUEPRINT.md sections 5, 7, 14, and 19

Artifact

index.mdx

Gate

Route, source-boundary, and readiness tests verify the local platform-stack claim.
2. Article data Accepted

Article-owned data artifacts and typed loaders feed the readiness section without runtime fetches.

Source

blueprint-001, BLUEPRINT.md sections 5, 7, 14, and 19

Artifact

data/article-artifact-index.json

Gate

Unit coverage parses checked-in JSON data and verifies rendered readiness records.
3. Verification stack Accepted

The verification matrix records focused unit, browser, starter, typecheck, build, diff, Python compile, and scaffold gates.

Source

blueprint-001, BLUEPRINT.md sections 5, 7, 14, and 19

Artifact

data/article-verification-matrix.json

Gate

Local commands in the verification matrix prove the published packet before closeout.
4. Claim ledger Accepted

The claim ledger records source-backed decisions for data ownership, evidence routing, release handoff, claim map, and proof manifest records.

Source

blueprint-001, BLUEPRINT.md sections 5, 7, 14, and 19

Artifact

data/article-claim-ledger.json

Gate

Focused tests verify claim IDs, source locators, and rendered ledger copy.
5. Claim map Accepted

The claim map links each selected claim to evidence, verification, handoff, and local artifact paths.

Source

blueprint-001, BLUEPRINT.md sections 5, 7, 14, and 19

Artifact

data/article-claim-map.json

Gate

Focused tests verify claim map references against existing evidence, verification, and handoff IDs.
6. Release handoff Accepted

The release handoff accepts published catalog readiness and keeps deployment out of scope.

Source

blueprint-001, BLUEPRINT.md sections 5, 7, 14, and 19

Artifact

data/article-release-handoff.json

Gate

Browser and unit checks verify accepted handoff items and published catalog behavior.
7. Proof manifest Accepted

The proof manifest names accepted local proofs for source boundary, proof ladder data, static figure, hydrated inspector, and validation records.

Source

blueprint-001, BLUEPRINT.md sections 5, 7, 14, and 19

Artifact

data/article-proof-manifest.json

Gate

Focused tests verify proof-manifest entries for the accepted local packet.

Source: blueprint-001
Accepted: The evidence trail accepts local article files, data artifacts, proof records, and verification gates for the published readiness packet.
Not Claimed: The evidence trail does not claim remote evidence collection, production deployment evidence, CMS workflow, or generated starter package proof.

Proof Manifest

Authoring Pipeline Draft Proof Manifest

The manifest records the local source, scaffold, data, figure, interaction, and readiness proofs that are accepted for the catalog inclusion claim.

1. Source boundary proof Accepted

Proof ID

source-boundary-proof

Owner

Article folder

Artifact

data/source-boundary.json

Gate

Focused unit coverage verifies the readiness source boundary and rejected deployment claims.

Evidence

The source boundary accepts the local readiness packet while preserving published catalog behavior.
2. Artifact index proof Accepted

Proof ID

artifact-index-proof

Owner

Authoring scaffold

Artifact

data/article-artifact-index.json

Gate

ArticleArtifactIndex renders the local file inventory and readiness packet paths.

Evidence

Focused unit and browser coverage see article-owned data and figure paths in the readiness section.
3. Claim ledger proof Accepted

Proof ID

claim-ledger-proof

Owner

Claim workflow

Artifact

data/article-claim-ledger.json

Gate

ArticleClaimLedger renders source-backed local claim decisions for the published packet.

Evidence

Focused unit coverage verifies ledger records and rejects generated shell copy.
4. Claim map proof Accepted

Proof ID

claim-map-proof

Owner

Claim workflow

Artifact

data/article-claim-map.json

Gate

ArticleClaimMap renders local links from claims to evidence, verification, handoff, and artifacts.

Evidence

Focused unit coverage verifies claim-map references against existing records.
5. Evidence trail proof Accepted

Proof ID

evidence-trail-proof

Owner

Evidence workflow

Artifact

data/article-evidence-trail.json

Gate

ArticleEvidenceTrail renders local evidence claims for source, data, verification, and handoff records.

Evidence

Focused unit coverage verifies evidence records and source locators.
6. Verification matrix proof Accepted

Proof ID

verification-matrix-proof

Owner

Verification workflow

Artifact

data/article-verification-matrix.json

Gate

Focused unit and browser checks verify the readiness verification matrix.

Evidence

The matrix names the proof ladder data, static flow figure, hydrated inspector, and closeout gates.
7. Release handoff proof Accepted

Proof ID

release-handoff-proof

Owner

Release workflow

Artifact

data/article-release-handoff.json

Gate

Focused unit and browser checks verify the readiness handoff records.

Evidence

The handoff names the local data, static figure, hydrated interaction, and published publication boundary.
8. Proof manifest proof Accepted

Proof ID

proof-manifest-proof

Owner

Release workflow

Artifact

data/article-proof-manifest.json

Gate

ArticleProofManifest renders this local proof inventory with the accepted publication decision.

Evidence

Focused unit coverage verifies proof entries for the accepted readiness packet.
9. Release readiness proof Accepted

Proof ID

release-readiness-proof

Owner

Release workflow

Artifact

src/components/ArticleReleaseReadiness.astro

Gate

Focused browser coverage verifies the visible release-readiness rollup.

Evidence

The rollup consumes article-owned checklist, proof-manifest, verification, and handoff records.
10. Starter manifest proof Accepted

Proof ID

starter-manifest-proof

Owner

Authoring scaffold

Artifact

data/article-starter-manifest.json

Gate

ArticleStarterManifest renders the checked-in starter file and template handoff paths.

Evidence

Focused unit coverage verifies starter manifest paths and source-backed copy.
11. Starter workflow proof Accepted

Proof ID

starter-workflow-proof

Owner

Authoring scaffold

Artifact

data/article-starter-workflow.json

Gate

ArticleStarterWorkflow renders the starter-to-draft workflow with source registration and local data wiring gates.

Evidence

Focused unit coverage verifies workflow steps and rejects unresolved generated copy.
12. Starter readiness proof Accepted

Proof ID

starter-readiness-proof

Owner

Authoring scaffold

Artifact

src/components/ArticleStarterReadiness.astro

Gate

ArticleStarterReadiness summarizes starter manifest and workflow readiness for the local draft.

Evidence

Browser coverage renders the starter readiness rollup inside the publish-readiness section.
13. Starter handoff proof Accepted

Proof ID

starter-handoff-proof

Owner

Authoring scaffold

Artifact

src/components/ArticleStarterHandoff.astro

Gate

ArticleStarterHandoff joins starter readiness with release handoff records for the next authoring step.

Evidence

Browser coverage renders the starter handoff packet with the route published.
14. Figure proof data proof Accepted

Proof ID

figure-proof-data-proof

Owner

Article figures

Artifact

data/figure-proofs.json

Gate

Figure proof data records only the article-specific static flow and hydrated inspector proofs.

Evidence

Focused tests parse figure proof data and verify source metadata for the article-specific figures.
15. Figure proof loader proof Accepted

Proof ID

figure-proof-loader-proof

Owner

Article figures

Artifact

data/figureProofs.ts

Gate

The figure proof loader exports article-specific route proof bindings parsed through the shared schema.

Evidence

Focused tests import figure proof bindings and verify the remaining FigureProof wrappers.
16. Pipeline proof ladder proof Accepted

Proof ID

pipeline-proof-ladder-proof

Owner

Article data

Artifact

data/pipeline-proof-ladder.json

Gate

Focused unit and browser checks verify the source-backed proof ladder renders in the published route.

Evidence

The proof ladder maps BLUEPRINT.md sections 5, 7, 14, and 19 to the published route's local owners and gates.
17. Pipeline proof ladder flow proof Accepted

Proof ID

pipeline-proof-ladder-flow-proof

Owner

Article figure

Artifact

figures/PipelineProofLadderFlow/PipelineProofLadderFlow.tsx

Gate

Focused unit and browser checks verify the data-backed static figure.

Evidence

The proof-ladder flow consumes data/pipeline-proof-ladder.json and renders through FigureProof with blueprint-001 metadata.
18. Pipeline proof gate inspector proof Accepted

Proof ID

pipeline-proof-gate-inspector-proof

Owner

Article interaction

Artifact

figures/PipelineProofGateInspector/PipelineProofGateInspector.tsx

Gate

Focused unit and browser checks verify the data-backed hydrated inspector.

Evidence

The proof gate inspector consumes data/pipeline-proof-ladder.json, hydrates with client:visible, and keeps source metadata in FigureProof.

Source: blueprint-001
Accepted: The readiness pass accepts published source-boundary, verification, handoff, data, static figure, and hydrated interaction proof records.
Not Claimed: No production deployment proof, remote source fetch, CMS workflow, generated starter package, or broader Authoring Pipeline completion is accepted.

Verification Matrix

Authoring Pipeline Draft Verification Matrix

The matrix records the local commands, targets, and evidence behind the accepted published readiness packet.

1. Source and data gates Accepted

Source, data, figure, and interaction checks for the published readiness packet.
- Article unit Accepted
  
  Command
  
  npm run test -- authoringPipelineDraft
  
  Target
  
  authoring-pipeline-published route, config, source boundary, and folder contract
  
  Evidence
  
  Focused unit coverage verifies published status, catalog inclusion, readiness records, and source-local files.
- Pipeline proof ladder contract Accepted
  
  Command
  
  npm run test -- authoringPipelineDraft
  
  Target
  
  data/pipeline-proof-ladder.json and index.mdx#mechanism
  
  Evidence
  
  Focused unit coverage parses the proof ladder and browser coverage verifies the rendered table.
- Pipeline proof ladder flow contract Accepted
  
  Command
  
  npm run test -- PipelineProofLadderFlow authoringPipelineDraft
  
  Target
  
  data/figure-proofs.json and figures/PipelineProofLadderFlow/model.ts
  
  Evidence
  
  Focused unit coverage verifies the static figure proof metadata and model consume the article-owned proof ladder.
- Pipeline proof gate inspector contract Accepted
  
  Command
  
  npm run test -- PipelineProofGateInspector authoringPipelineDraft
  
  Target
  
  data/figure-proofs.json and figures/PipelineProofGateInspector/model.ts
  
  Evidence
  
  Focused unit coverage verifies the hydrated inspector proof metadata and model consume the article-owned proof ladder.
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 static route output and hydrated island bundling.
3. Browser and visual gates Accepted

Browser checks for visible readiness, static figure, and hydrated inspector behavior.
- Focused browser smoke Accepted
  
  Command
  
  npm run test:browser -- tests/authoring-pipeline-draft.spec.ts
  
  Target
  
  /essays/authoring-pipeline-draft/ and /essays/
  
  Evidence
  
  Focused browser coverage verifies the published route, visible readiness section, data-backed figures, inspector hydration, and catalog inclusion.
- Release readiness rollup Accepted
  
  Command
  
  npm run test:browser -- tests/authoring-pipeline-draft.spec.ts
  
  Target
  
  index.mdx#publish-readiness and ArticleReleaseReadiness
  
  Evidence
  
  Browser coverage verifies checklist, verification, and release-handoff readiness metrics for the accepted proof packet.
- Starter instantiation proof Accepted
  
  Command
  
  npm run starter:instantiate:proof
  
  Target
  
  static-first starter templates
  
  Evidence
  
  The starter proof stays green while the real draft article records its local readiness packet.
4. Closeout gates Accepted

Closeout checks for tracked diff, Python scripts, and scaffold ledgers.
- Python compile Accepted
  
  Command
  
  PYTHONPYCACHEPREFIX=/tmp/tutorial-autoresearch-pycache python3 -m py_compile scripts/create_static_first_article.py scripts/prove_static_first_starter_instantiation.py scripts/validate_tutorial_scaffold.py
  
  Target
  
  tutorial Python scripts
  
  Evidence
  
  Python compile validates the script files used by scaffold and starter proof gates.
- 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 readiness matrix accepts focused unit, browser, starter instantiation, typecheck, build, diff, Python compile, and scaffold validation gates for the local published packet.
Not Claimed: No live deployment, production release, remote status fetch, CI dashboard, external publication service, or deployment promotion is accepted.

Release Handoff

Authoring Pipeline Draft Release Handoff

The handoff records the published route, local proof packets, validation records, and next publication boundary.

1. Published route packet Accepted

The published article packet is source-backed and included in the local essay catalog.
- Published route Accepted
  
  Artifact
  
  index.mdx
  
  Gate
  
  Focused unit and browser checks verify published status, route copy, visible Publish Readiness section, and catalog inclusion.
  
  Evidence
  
  The route sets status published while recording the accepted local readiness packet.
- 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, proof-ladder data, static figure, hydrated inspector, and readiness records while rejecting deployment claims.
2. Validation packet Accepted

Local proof records are accepted for the published readiness packet while deployment remains out of scope.
- Claim ledger Accepted
  
  Artifact
  
  data/article-claim-ledger.json
  
  Gate
  
  The claim ledger records source-backed local decisions.
  
  Evidence
  
  Focused unit coverage verifies claim-ledger copy and source locators.
- Claim map Accepted
  
  Artifact
  
  data/article-claim-map.json
  
  Gate
  
  The claim map links claim, evidence, verification, handoff, and artifact routes.
  
  Evidence
  
  Focused unit coverage verifies claim-map references.
- Proof manifest Accepted
  
  Artifact
  
  data/article-proof-manifest.json
  
  Gate
  
  The proof manifest lists accepted local proof records.
  
  Evidence
  
  Focused unit coverage verifies proof-manifest entries.
- Pipeline proof ladder Accepted
  
  Artifact
  
  data/pipeline-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 article-specific data packet and its source-backed local gates.
- Pipeline proof ladder flow Accepted
  
  Artifact
  
  figures/PipelineProofLadderFlow/PipelineProofLadderFlow.tsx
  
  Gate
  
  Focused unit and browser checks verify the static data-backed figure renders in the published route.
  
  Evidence
  
  The figure consumes data/pipeline-proof-ladder.json, uses FigureProof source metadata, and renders without a client island.
- Pipeline proof gate inspector Accepted
  
  Artifact
  
  figures/PipelineProofGateInspector/PipelineProofGateInspector.tsx
  
  Gate
  
  Focused unit and browser checks verify the data-backed hydrated inspector renders in the published route.
  
  Evidence
  
  The island consumes data/pipeline-proof-ladder.json, uses FigureProof source metadata, and hydrates one scoped client island.
- Evidence trail Accepted
  
  Artifact
  
  data/article-evidence-trail.json
  
  Gate
  
  The evidence trail records local source, data, verification, and handoff evidence.
  
  Evidence
  
  Focused unit coverage verifies evidence trail copy.
- Verification matrix Accepted
  
  Artifact
  
  data/article-verification-matrix.json
  
  Gate
  
  The verification matrix names focused local commands for the published packet.
  
  Evidence
  
  Focused unit coverage verifies verification-matrix targets and evidence.
- Article figure proof packet Accepted
  
  Artifact
  
  data/figure-proofs.json and data/figureProofs.ts
  
  Gate
  
  Focused route checks keep article-specific figure proof data and loader paths aligned after retiring the generated shell figure.
  
  Evidence
  
  Focused unit and browser coverage verify the static flow and hydrated inspector proof packet.
- Release readiness Accepted
  
  Artifact
  
  src/components/ArticleReleaseReadiness.astro
  
  Gate
  
  Release readiness summarizes checklist, proof manifest, verification matrix, and handoff records.
  
  Evidence
  
  Browser coverage verifies the shared release readiness rollup.
- Starter manifest Accepted
  
  Artifact
  
  data/article-starter-manifest.json
  
  Gate
  
  The starter manifest records checked-in starter, article, data, and verification handoff paths.
  
  Evidence
  
  Focused unit coverage verifies starter manifest paths.
- Starter workflow Accepted
  
  Artifact
  
  data/article-starter-workflow.json
  
  Gate
  
  The starter workflow records source registration, data wiring, rendering, and closeout steps.
  
  Evidence
  
  Focused unit coverage verifies starter workflow steps.
- Starter readiness Accepted
  
  Artifact
  
  src/components/ArticleStarterReadiness.astro
  
  Gate
  
  Starter readiness summarizes starter manifest and workflow status for the draft.
  
  Evidence
  
  Browser coverage verifies the shared starter readiness rollup.
- Starter handoff Accepted
  
  Artifact
  
  src/components/ArticleStarterHandoff.astro
  
  Gate
  
  Starter handoff connects starter readiness with the release handoff packet.
  
  Evidence
  
  Browser coverage verifies the shared starter handoff packet.
- Focused browser proof Accepted
  
  Artifact
  
  scripts/create_static_first_article.py
  
  Gate
  
  Focused browser checks render the published route, readiness section, figures, and catalog inclusion.
  
  Evidence
  
  Playwright coverage verifies desktop/mobile behavior and published catalog inclusion.
3. Closeout packet Accepted

Closeout records track validation, run log, evidence ledger, memory, commit, push, and lock release for the selected work.
- Run log ledger Accepted
  
  Artifact
  
  run_log.md
  
  Gate
  
  Run log closeout records selected todo, proof boundary, validation, and next work.
  
  Evidence
  
  Scaffold validation checks the run log and active todo state.
- Evidence ledger Accepted
  
  Artifact
  
  evidence_ledger.yaml
  
  Gate
  
  Evidence ledger closeout records the accepted artifact and proof boundary.
  
  Evidence
  
  Scaffold validation parses evidence ledger records.
4. Next work packet Accepted

Next-work records keep the queue on source-backed article or platform progress after catalog inclusion.
- Queue state Accepted
  
  Artifact
  
  state.md and todo.md
  
  Gate
  
  Queue state advances from this cleanup to the next numeric product todo.
  
  Evidence
  
  Scaffold validation checks active todo sync.
- Starter template Accepted
  
  Artifact
  
  src/content/essay-starters/static-first/
  
  Gate
  
  Starter template follow-up stays separate from this draft data cleanup.
  
  Evidence
  
  Next todo selection keeps template work explicit if needed.

Source: blueprint-001
Accepted: The readiness handoff accepts the published route packet, source-boundary record, article-owned proof data, local static figure, hydrated inspector, and focused browser proof.
Not Claimed: No production deployment proof, remote source fetch, CMS workflow, generated starter package, or new source topic is accepted.

Release Readiness

Release Readiness Rollup

Static rollup across article-owned checklist, proof manifest, verification matrix, and release handoff records.

Checklist: 5/5 Ready; authoring-pipeline-draft-article-checklist
Proof Manifest: 18/18 Ready; authoring-pipeline-draft-article-proof-manifest
Verification Matrix: 12/12 Ready; authoring-pipeline-draft-article-verification-matrix
Release Handoff: 21/21 Ready; authoring-pipeline-draft-article-release-handoff

Checklist authoring-pipeline-draft-article-checklist
Proof Manifest authoring-pipeline-draft-article-proof-manifest
Verification Matrix authoring-pipeline-draft-article-verification-matrix
Release Handoff authoring-pipeline-draft-article-release-handoff

Source
blueprint-001
Accepted
Static release readiness is derived from checked-in article-owned proof, verification, and handoff data.
Not Claimed
No release dashboard, remote status fetch, CMS queue, automated release decision, global readiness registry, or personalized editor state is introduced.

Starter Manifest

Authoring Pipeline Draft 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. Content shell Accepted

The content shell group records MDX, config, assets, and the figures folder from the article folder contract after retiring the generated starter shell figure.
- Article MDX Accepted
  
  Kind
  
  content
  
  Path
  
  index.mdx
  
  Gate
  
  The article folder contract keeps index.mdx in the draft shell.
- Essay config Accepted
  
  Kind
  
  configuration
  
  Path
  
  essay.config.ts
  
  Gate
  
  The article folder contract keeps essay.config.ts in the draft shell.
- Assets folder Accepted
  
  Kind
  
  folder
  
  Path
  
  assets/
  
  Gate
  
  The article folder contract keeps assets/ in the draft shell.
- Figures folder Accepted
  
  Kind
  
  folder
  
  Path
  
  figures/
  
  Gate
  
  The article folder contract keeps figures/ in the draft shell.
2. Article data Accepted

The article data group records checked-in JSON artifacts and loaders that keep the draft source-backed and testable.
- Source boundary Accepted
  
  Kind
  
  data
  
  Path
  
  data/source-boundary.json
  
  Gate
  
  Checked-in data and typed loaders keep data/source-boundary.json local to the published readiness packet.
- Starter manifest Accepted
  
  Kind
  
  data
  
  Path
  
  data/article-starter-manifest.json
  
  Gate
  
  Checked-in data and typed loaders keep data/article-starter-manifest.json local to the published readiness packet.
- Starter workflow Accepted
  
  Kind
  
  data
  
  Path
  
  data/article-starter-workflow.json
  
  Gate
  
  Checked-in data and typed loaders keep data/article-starter-workflow.json local to the published readiness packet.
- Artifact index Accepted
  
  Kind
  
  data
  
  Path
  
  data/article-artifact-index.json
  
  Gate
  
  Checked-in data and typed loaders keep data/article-artifact-index.json local to the published readiness packet.
- Proof manifest Accepted
  
  Kind
  
  data
  
  Path
  
  data/article-proof-manifest.json
  
  Gate
  
  Checked-in data and typed loaders keep data/article-proof-manifest.json local to the published readiness packet.
- Verification matrix Accepted
  
  Kind
  
  data
  
  Path
  
  data/article-verification-matrix.json
  
  Gate
  
  Checked-in data and typed loaders keep data/article-verification-matrix.json local to the published readiness packet.
- Release handoff Accepted
  
  Kind
  
  data
  
  Path
  
  data/article-release-handoff.json
  
  Gate
  
  Checked-in data and typed loaders keep data/article-release-handoff.json local to the published readiness packet.
- Figure proofs Accepted
  
  Kind
  
  data
  
  Path
  
  data/figure-proofs.json
  
  Gate
  
  Checked-in data and typed loaders keep data/figure-proofs.json local to the published readiness packet.
- Figure proofs loader Accepted
  
  Kind
  
  loader
  
  Path
  
  data/figureProofs.ts
  
  Gate
  
  Checked-in data and typed loaders keep data/figureProofs.ts local to the published readiness packet.
3. Starter templates Accepted

The starter templates group records reusable source templates that generated the draft shell and handoff records.
- Starter README Accepted
  
  Kind
  
  documentation
  
  Path
  
  src/content/essay-starters/static-first/README.md
  
  Gate
  
  Starter validation keeps src/content/essay-starters/static-first/README.md aligned with generated article handoff records.
- MDX template Accepted
  
  Kind
  
  template
  
  Path
  
  src/content/essay-starters/static-first/index.mdx.template
  
  Gate
  
  Starter validation keeps src/content/essay-starters/static-first/index.mdx.template aligned with generated article handoff records.
- Config template Accepted
  
  Kind
  
  template
  
  Path
  
  src/content/essay-starters/static-first/essay.config.ts.template
  
  Gate
  
  Starter validation keeps src/content/essay-starters/static-first/essay.config.ts.template aligned with generated article handoff records.
- Starter manifest data template Accepted
  
  Kind
  
  template
  
  Path
  
  src/content/essay-starters/static-first/data/article-starter-manifest.json.template
  
  Gate
  
  Starter validation keeps src/content/essay-starters/static-first/data/article-starter-manifest.json.template aligned with generated article handoff records.
- Starter manifest schema template Accepted
  
  Kind
  
  template
  
  Path
  
  src/content/essay-starters/static-first/data/articleStarterManifest.ts.template
  
  Gate
  
  Starter validation keeps src/content/essay-starters/static-first/data/articleStarterManifest.ts.template aligned with generated article handoff records.
- Starter workflow data template Accepted
  
  Kind
  
  template
  
  Path
  
  src/content/essay-starters/static-first/data/article-starter-workflow.json.template
  
  Gate
  
  Starter validation keeps src/content/essay-starters/static-first/data/article-starter-workflow.json.template aligned with generated article handoff records.
- Starter workflow schema template Accepted
  
  Kind
  
  template
  
  Path
  
  src/content/essay-starters/static-first/data/articleStarterWorkflow.ts.template
  
  Gate
  
  Starter validation keeps src/content/essay-starters/static-first/data/articleStarterWorkflow.ts.template aligned with generated article handoff records.
- Starter readiness component placement Accepted
  
  Kind
  
  template
  
  Path
  
  src/content/essay-starters/static-first/index.mdx.template
  
  Gate
  
  Starter validation keeps src/content/essay-starters/static-first/index.mdx.template aligned with generated article handoff records.
- Starter handoff component placement Accepted
  
  Kind
  
  template
  
  Path
  
  src/content/essay-starters/static-first/index.mdx.template
  
  Gate
  
  Starter validation keeps src/content/essay-starters/static-first/index.mdx.template aligned with generated article handoff records.
4. Verification handoff Accepted

The verification handoff group records focused unit, browser, starter, and scaffold gates for the published packet.
- Article unit test Accepted
  
  Kind
  
  test
  
  Path
  
  src/content/essays/staticFirstEssay.test.ts
  
  Gate
  
  Focused validation keeps src/content/essays/staticFirstEssay.test.ts tied to the published readiness packet.
- Starter unit test Accepted
  
  Kind
  
  test
  
  Path
  
  src/content/essay-starters/articleStarter.test.ts
  
  Gate
  
  Focused validation keeps src/content/essay-starters/articleStarter.test.ts tied to the published readiness packet.
- Starter instantiation proof Accepted
  
  Kind
  
  validator
  
  Path
  
  scripts/prove_static_first_starter_instantiation.py
  
  Gate
  
  Focused validation keeps scripts/prove_static_first_starter_instantiation.py tied to the published readiness packet.
- Browser smoke Accepted
  
  Kind
  
  test
  
  Path
  
  tests/home.spec.ts
  
  Gate
  
  Focused validation keeps tests/home.spec.ts tied to the published readiness packet.
- Scaffold validator Accepted
  
  Kind
  
  validator
  
  Path
  
  scripts/validate_tutorial_scaffold.py
  
  Gate
  
  Focused validation keeps scripts/validate_tutorial_scaffold.py tied to the published readiness packet.

Source: blueprint-001
Accepted: The starter manifest accepts checked-in article files, starter templates, data records, and focused verification paths needed to reproduce the local draft shell.
Not Claimed: The starter manifest does not claim a generated package, remote starter registry, CMS workflow, deployment proof, or starter package catalog release.

Starter Workflow

Authoring Pipeline Draft Starter Workflow

Starter workflow records the source registration, local data wiring, rendered route checks, and closeout gates that turned the copied folder into this draft.

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. Replace generated copy Accepted

Replace generated frontmatter, prose, config, and readiness-record copy before the route claims publication readiness.

Artifact

index.mdx and essay.config.ts

Gate

Focused article tests reject unresolved generated copy and verify rendered route and readiness record text.
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. Wire article data Accepted

Populate local JSON artifacts and matching loaders before shared primitives render the publication record.

Artifact

data/figure-proofs.json, data/figureProofs.ts, data/*.json, and data/*.ts

Gate

npm run test -- staticFirstEssay articleStarter verifies data order, IDs, and starter template alignment.
5. Render static primitives Accepted

Render source, proof, starter, release, and workflow primitives as static HTML in the article route.

Artifact

ArticleStarterWorkflow.astro, ArticleStarterReadiness.astro, ArticleStarterHandoff.astro, and index.mdx#next-proof

Gate

Focused browser smoke verifies shared markers and zero nested Astro islands inside the starter workflow, starter-readiness rollup, and starter-handoff packet.
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 starter workflow accepts the local path from copied starter shell to source-registered published route with article-owned data and focused validation.
Not Claimed: The starter workflow does not claim starter package generation, remote source fetching, CMS workflow, deployment proof, or starter package catalog release.

Starter Readiness

Starter Readiness Rollup

Static rollup across article-owned starter manifest and starter workflow records.

Manifest Groups: 4/4 Ready; authoring-pipeline-draft-article-starter-manifest
Manifest Entries: 27/27 Ready; authoring-pipeline-draft-article-starter-manifest
Workflow Steps: 6/6 Ready; authoring-pipeline-draft-article-starter-workflow

Starter Manifest authoring-pipeline-draft-article-starter-manifest
Starter Workflow authoring-pipeline-draft-article-starter-workflow

Source
blueprint-001
Accepted
Static starter readiness is derived from checked-in article-owned manifest and workflow data.
Not Claimed
No starter dashboard, starter package generator, runtime filesystem scan, remote template fetch, CMS task store, global starter readiness registry, or personalized editor state is introduced.

Starter Handoff

Starter Handoff Packet

Static handoff packet across article-owned starter manifest, starter workflow, readiness, and release handoff records.

Starter Manifest: 27/27 Ready; authoring-pipeline-draft-article-starter-manifest
Starter Workflow: 6/6 Ready; authoring-pipeline-draft-article-starter-workflow
Starter Readiness: 10/10 Ready; authoring-pipeline-draft-shared-starter-readiness
Release Handoff: 21/21 Ready; authoring-pipeline-draft-article-release-handoff

Source
blueprint-001
Accepted
Static starter handoff derives from checked-in article-owned starter and release data.
Not Claimed
No starter dashboard, generated starter package, runtime filesystem scan, remote template fetch, CMS task store, global starter handoff registry, or personalized editor state is introduced.

Publication Workflow

Authoring Pipeline Draft Publication Workflow

The workflow records the accepted local readiness packet while the route is published.

1. Draft shell Accepted

The article route renders source-backed draft content, local proof sections, and published frontmatter.

Artifact

index.mdx

Gate

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

The source-boundary record accepts blueprint-001, starter templates, proof-ladder data, static figure, hydrated inspector, and readiness records.

Artifact

data/source-boundary.json

Gate

Focused unit coverage asserts accepted and rejected source-boundary claims.
3. Pipeline proof ladder Accepted

The article-specific data artifact renders visibly before the readiness packet is claimed.

Artifact

data/pipeline-proof-ladder.json

Gate

Focused unit and browser checks verify the proof ladder.
4. Pipeline proof ladder flow Accepted

The static flow figure consumes the proof ladder data through FigureProof without client hydration.

Artifact

figures/PipelineProofLadderFlow/PipelineProofLadderFlow.tsx

Gate

Focused unit and browser checks verify the data-backed static figure.
5. Pipeline proof gate inspector Accepted

The hydrated inspector consumes the same proof ladder data and keeps source metadata outside the island.

Artifact

figures/PipelineProofGateInspector/PipelineProofGateInspector.tsx

Gate

Focused unit and browser checks verify hydration, selected state, reset behavior, and proof metadata.
6. Publish readiness Accepted

The readiness section accepts only the local data, static figure, hydrated interaction, and verification records.

Artifact

index.mdx#publish-readiness

Gate

Focused unit and browser checks verify the visible Publish Readiness section and checklist rollup.
7. Verification matrix Accepted

The verification matrix records the focused local commands for the published packet.

Artifact

data/article-verification-matrix.json

Gate

Focused unit coverage verifies accepted matrix entries for the local proof boundary.
8. Release handoff Accepted

The release handoff records the published route, local proofs, validation records, and rejected publication boundary.

Artifact

data/article-release-handoff.json

Gate

Focused unit coverage verifies handoff items for the local proof boundary.
9. Release readiness Accepted

The release-readiness rollup accepts the local readiness packet while deployment remains out of scope.

Artifact

ArticleReleaseReadiness.astro

Gate

Focused browser coverage verifies the readiness rollup and accepted checklist metric.
10. Starter handoff Accepted

Starter package publication stays deferred; the current run does not create a generated package or remote template workflow.

Artifact

ArticleStarterHandoff.astro

Gate

Future starter-package work needs a separate source-registered proof.

Source: blueprint-001
Accepted: The readiness workflow 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

Authoring Pipeline Draft Authoring Flow

The flow keeps source, artifact, and verification checkpoints in article-owned data for the published route.

1. Source-register the claim Accepted

Register blueprint-001 before the published route renders article-owned claims.

Artifact

data/source-boundary.json

Gate

Source-boundary data and scaffold validation keep the route tied to the registered blueprint.
2. Localize article artifacts Accepted

Keep prose, JSON, loaders, assets, and figures under the article folder contract.

Artifact

data/

Gate

Unit coverage parses article-owned records and rejects unresolved generated tokens.
3. Render static primitives Accepted

Render shared static primitives from checked-in article data in index.mdx.

Artifact

index.mdx

Gate

Browser coverage verifies the publish-readiness section and published catalog inclusion.
4. Close verification gates Accepted

Close focused unit, browser, starter, typecheck, build, diff, Python compile, and scaffold gates before handoff.

Artifact

tests

Gate

Run log, evidence ledger, memory, commit, push, and lock release record the completed proof.

Source: blueprint-001
Accepted: The authoring flow accepts local source registration, article-owned data wiring, static primitive rendering, and focused closeout gates for the published readiness packet.
Not Claimed: The authoring flow does not claim remote source ingestion, CMS workflow, generated package release, production deployment, or catalog distribution beyond the local published route entry.

Article Checklist

Authoring Pipeline Draft Publication Checklist

The checklist accepts the published readiness packet while the route is published and catalog-included.

Frontmatter and catalog Accepted

Frontmatter sets status published, route slug, and source-backed summary while the published catalog includes the route.
Gate: Focused unit and browser checks verify published status and catalog inclusion.
Source boundary Accepted

data/source-boundary.json accepts blueprint-001, checked-in starter templates, the proof ladder data, static flow figure, hydrated inspector, and readiness packet.
Gate: Focused unit coverage asserts accepted and rejected source-boundary claims.
Article-owned data Accepted

data/pipeline-proof-ladder.json and data/figure-proofs.json feed the visible proof ladder, static flow figure, hydrated inspector, and readiness records.
Gate: Focused unit and browser checks verify the data contract and rendered outputs.
Interactive scope Accepted

The only article-specific hydrated island is PipelineProofGateInspector, which keeps source metadata in FigureProof and local selection state inside the island.
Gate: Focused browser coverage verifies one island, selected proof-layer state, data-artifact detail, reset behavior, and layout separation.
Verification stack Accepted

The readiness pass is covered by focused unit and browser checks, starter instantiation proof, typecheck, build, diff check, and scaffold validation.
Gate: TUT-233 closeout records the passing focused app and scaffold gates.

Source: blueprint-001
Accepted: The readiness pass accepts checked-in published frontmatter, source-boundary data, article-owned proof ladder data, the static flow figure, the hydrated inspector, and focused local verification records.
Not Claimed: No production deployment proof, remote source fetch, CMS workflow, generated starter package, or new source topic is accepted.

Question

Local Model

Mechanism

Pipeline Proof Ladder

Proof Gate Inspector

Content layer

Limits

Source Boundary

Publish Readiness

Authoring Pipeline Draft Artifact Index

Authoring Pipeline Draft Claim Ledger

Authoring Pipeline Draft Claim Map

Authoring Pipeline Draft Evidence Trail

Authoring Pipeline Draft Proof Manifest

Authoring Pipeline Draft Verification Matrix

Authoring Pipeline Draft Release Handoff

Authoring Pipeline Draft Starter Manifest

Authoring Pipeline Draft Starter Workflow

Authoring Pipeline Draft Publication Workflow

Authoring Pipeline Draft Authoring Flow

Authoring Pipeline Draft Publication Checklist

More On Shared Topics