Platform Authoring Flow

This published article starts from the article creation pipeline and turns the platform blueprint into a route-visible authoring flow for future explorable essays.

Question

How should the platform move from source registration to a published article route without bypassing the static-first folder contract?

Local Model

The blueprint divides the product into content, publication shell, interactive islands, data artifacts, and verification layers; this article keeps those owners visible inside one generated article folder.

Figure 1. Platform Authoring Flow The article-specific figure maps the source boundary, local artifacts, static route, verification gates, and authoring preview registry handoff.

Source-register the claimdata/source-boundary.jsonFocused article tests verify the source boundary and registered source ID.
Localize article artifactsdata/Focused article tests verify article-owned data, proof metadata, and artifact coverage.
Render static primitivesindex.mdxBuild and build-output checks verify the route renders in the published catalog surface.
Close verification gatestestsFocused unit, browser, typecheck, build, build-output, changed-surface, scaffold, and diff checks guard the publication boundary.
Authoring preview registrysrc/pages/authoring/article-preview.astroFocused registry coverage verifies the published route, source IDs, figure count, catalog inclusion, and remaining draft exclusion.

Figure 1. Platform Authoring Flow proof metadata

Source: blueprint-001
Locator: BLUEPRINT.md sections 5, 7, and 14
Gate: Published article gate for article-specific platform authoring flow figure proof.

FigureProof renders source metadata around PlatformAuthoringFlowFigure.
PlatformAuthoringFlowFigure renders authoring-flow.json as static SVG and shared gate legend markup.
The workbench and article tests verify the source boundary to authoring preview registry handoff.

Mechanism

The generated scaffold carries index.mdx prose, essay.config.ts proof metadata, article-owned JSON, typed data loaders, an article-specific figure, and focused check hints together.

Limits

This article proves the local authoring flow through published catalog inclusion only. It does not claim deployment freshness, remote source fetching, CMS workflow, or automatic article promotion.

Source Boundary

The accepted source boundary is BLUEPRINT.md sections 5, 7, and 14 plus the checked-in static-first starter templates; research downloads and remote sources stay out of scope.

Next Proof

The next proof is to use this published local route as the authoring preview registry path for broader article creation work after focused route, registry, scaffold, typecheck, build, and build-output checks pass.

Artifact Index

Platform Authoring Flow 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

Published article summary for content shell.
- Artifact
  
  index.mdx
  
  Kind
  
  content
  
  Gate
  
  Published article gate for article mdx.
- Artifact
  
  essay.config.ts
  
  Kind
  
  configuration
  
  Gate
  
  Published article gate for essay config.
- Artifact
  
  assets/.gitkeep
  
  Kind
  
  scaffold
  
  Gate
  
  Published article gate for assets placeholder.
- Artifact
  
  figures/.gitkeep
  
  Kind
  
  scaffold
  
  Gate
  
  Published article gate for figures placeholder.
- Artifact
  
  figures/PlatformAuthoringFlowFigure/PlatformAuthoringFlowFigure.tsx
  
  Kind
  
  figure
  
  Gate
  
  Published article gate for platform authoring flow figure module.
- Artifact
  
  figures/PlatformAuthoringFlowFigure/PlatformAuthoringFlowFigure.module.css
  
  Kind
  
  style
  
  Gate
  
  Published article gate for platform authoring flow figure style.
- Artifact
  
  figures/PlatformAuthoringFlowFigure/model.ts
  
  Kind
  
  model
  
  Gate
  
  Published article gate for platform authoring flow figure model.
- Artifact
  
  figures/PlatformAuthoringFlowFigure/PlatformAuthoringFlowFigure.test.tsx
  
  Kind
  
  support
  
  Gate
  
  Focused figure tests exercise the route-local platform authoring flow model and static markup.
2. Article data Accepted

Published article summary for article data.
- Artifact
  
  data/source-boundary.json
  
  Kind
  
  data
  
  Gate
  
  Published article gate for source boundary.
- Artifact
  
  data/article-sections.json
  
  Kind
  
  data
  
  Gate
  
  Published article gate for article sections.
- Artifact
  
  data/article-artifact-index.json
  
  Kind
  
  data
  
  Gate
  
  Published article gate for artifact index.
- Artifact
  
  data/article-checklist.json
  
  Kind
  
  data
  
  Gate
  
  Published article gate for article checklist.
- Artifact
  
  data/article-starter-manifest.json
  
  Kind
  
  data
  
  Gate
  
  Published article gate for starter manifest.
- Artifact
  
  data/article-starter-workflow.json
  
  Kind
  
  data
  
  Gate
  
  Published article gate for starter workflow.
- Artifact
  
  data/article-evidence-trail.json
  
  Kind
  
  data
  
  Gate
  
  Published article gate for evidence trail.
- Artifact
  
  data/article-claim-ledger.json
  
  Kind
  
  data
  
  Gate
  
  Published article gate for claim ledger.
- Artifact
  
  data/article-claim-map.json
  
  Kind
  
  data
  
  Gate
  
  Published article gate for claim map.
- Artifact
  
  data/article-proof-manifest.json
  
  Kind
  
  data
  
  Gate
  
  Published article gate for proof manifest.
- Artifact
  
  data/article-verification-matrix.json
  
  Kind
  
  data
  
  Gate
  
  Published article gate for verification matrix.
- Artifact
  
  data/article-release-handoff.json
  
  Kind
  
  data
  
  Gate
  
  Published article gate for release handoff.
- Artifact
  
  data/publication-workflow.json
  
  Kind
  
  data
  
  Gate
  
  Published article gate for publication workflow.
- Artifact
  
  data/authoring-flow.json
  
  Kind
  
  data
  
  Gate
  
  Published article gate for authoring flow.
- Artifact
  
  data/figure-proofs.json
  
  Kind
  
  data
  
  Gate
  
  Published article gate for figure proofs.
- Artifact
  
  data/sourceBoundary.ts
  
  Kind
  
  loader
  
  Gate
  
  Published article gate for source boundary loader.
- Artifact
  
  data/articleSections.ts
  
  Kind
  
  loader
  
  Gate
  
  Published article gate for article sections loader.
- Artifact
  
  data/articleArtifactIndex.ts
  
  Kind
  
  loader
  
  Gate
  
  Published article gate for artifact index loader.
- Artifact
  
  data/articleChecklist.ts
  
  Kind
  
  loader
  
  Gate
  
  Published article gate for article checklist loader.
- Artifact
  
  data/articleStarterManifest.ts
  
  Kind
  
  loader
  
  Gate
  
  Published article gate for starter manifest loader.
- Artifact
  
  data/articleStarterWorkflow.ts
  
  Kind
  
  loader
  
  Gate
  
  Published article gate for starter workflow loader.
- Artifact
  
  data/articleEvidenceTrail.ts
  
  Kind
  
  loader
  
  Gate
  
  Published article gate for evidence trail loader.
- Artifact
  
  data/articleClaimLedger.ts
  
  Kind
  
  loader
  
  Gate
  
  Published article gate for claim ledger loader.
- Artifact
  
  data/articleClaimMap.ts
  
  Kind
  
  loader
  
  Gate
  
  Published article gate for claim map loader.
- Artifact
  
  data/articleProofManifest.ts
  
  Kind
  
  loader
  
  Gate
  
  Published article gate for proof manifest loader.
- Artifact
  
  data/articleVerificationMatrix.ts
  
  Kind
  
  loader
  
  Gate
  
  Published article gate for verification matrix loader.
- Artifact
  
  data/articleReleaseHandoff.ts
  
  Kind
  
  loader
  
  Gate
  
  Published article gate for release handoff loader.
- Artifact
  
  data/publicationWorkflow.ts
  
  Kind
  
  loader
  
  Gate
  
  Published article gate for publication workflow loader.
- Artifact
  
  data/authoringFlow.ts
  
  Kind
  
  loader
  
  Gate
  
  Published article gate for authoring flow loader.
- Artifact
  
  data/figureProofs.ts
  
  Kind
  
  loader
  
  Gate
  
  Published article gate for figure proofs loader.
- Artifact
  
  data/promotion-readiness.json
  
  Kind
  
  data
  
  Gate
  
  Published article gate for promotion readiness data.
- Artifact
  
  data/promotionReadiness.ts
  
  Kind
  
  loader
  
  Gate
  
  Published article gate for promotion readiness loader.
3. Shared primitives Accepted

Published article summary for shared primitives.
- Artifact
  
  src/components/FigureFrame.astro
  
  Kind
  
  component
  
  Gate
  
  Published article gate for figure frame component.
- Artifact
  
  src/components/FigureFrame.css
  
  Kind
  
  style
  
  Gate
  
  Published article gate for figure frame style.
- Artifact
  
  src/components/FigureProof.astro
  
  Kind
  
  component
  
  Gate
  
  Published article gate for figure proof component.
- Artifact
  
  src/components/FigureControls.tsx
  
  Kind
  
  component
  
  Gate
  
  Published article gate for figure controls component.
- Artifact
  
  src/components/FigureControls.module.css
  
  Kind
  
  style
  
  Gate
  
  Published article gate for figure controls style.
- Artifact
  
  src/components/ArticleSectionNav.astro
  
  Kind
  
  component
  
  Gate
  
  Published article gate for section nav component.
- Artifact
  
  src/components/ArticleSourceBoundary.astro
  
  Kind
  
  component
  
  Gate
  
  Published article gate for source boundary component.
- Artifact
  
  src/components/ArticleArtifactIndex.astro
  
  Kind
  
  component
  
  Gate
  
  Published article gate for artifact index component.
- Artifact
  
  src/components/ArticleEvidenceTrail.astro
  
  Kind
  
  component
  
  Gate
  
  Published article gate for evidence trail component.
- Artifact
  
  src/components/ArticleClaimLedger.astro
  
  Kind
  
  component
  
  Gate
  
  Published article gate for claim ledger component.
- Artifact
  
  src/components/ArticleClaimMap.astro
  
  Kind
  
  component
  
  Gate
  
  Published article gate for claim map component.
- Artifact
  
  src/components/ArticleProofManifest.astro
  
  Kind
  
  component
  
  Gate
  
  Published article gate for proof manifest component.
- Artifact
  
  src/components/ArticleVerificationMatrix.astro
  
  Kind
  
  component
  
  Gate
  
  Published article gate for verification matrix component.
- Artifact
  
  src/components/ArticleReleaseHandoff.astro
  
  Kind
  
  component
  
  Gate
  
  Published article gate for release handoff component.
- Artifact
  
  src/components/ArticleReleaseReadiness.astro
  
  Kind
  
  component
  
  Gate
  
  Published article gate for release readiness component.
- Artifact
  
  src/components/ArticleStarterManifest.astro
  
  Kind
  
  component
  
  Gate
  
  Published article gate for starter manifest component.
- Artifact
  
  src/components/ArticleStarterWorkflow.astro
  
  Kind
  
  component
  
  Gate
  
  Published article gate for starter workflow component.
- Artifact
  
  src/components/ArticleStarterReadiness.astro
  
  Kind
  
  component
  
  Gate
  
  Published article gate for starter readiness component.
- Artifact
  
  src/components/ArticleStarterHandoff.astro
  
  Kind
  
  component
  
  Gate
  
  Published article gate for starter handoff component.
- Artifact
  
  src/components/ArticlePublicationWorkflow.astro
  
  Kind
  
  component
  
  Gate
  
  Published article gate for publication workflow component.
- Artifact
  
  src/components/ArticlePublicationQa.astro
  
  Kind
  
  component
  
  Gate
  
  Published article gate for publication qa component.
- Artifact
  
  src/components/ArticlePromotionReadiness.astro
  
  Kind
  
  component
  
  Gate
  
  Published article gate for promotion readiness component.
- Artifact
  
  src/components/ArticleAuthoringFlow.astro
  
  Kind
  
  component
  
  Gate
  
  Published article gate for authoring flow component.
- Artifact
  
  src/components/ArticleChecklist.astro
  
  Kind
  
  component
  
  Gate
  
  Published article gate for checklist component.
4. Verification handoff Accepted

Published article summary for verification handoff.
- Artifact
  
  tests/home.spec.ts
  
  Kind
  
  test
  
  Gate
  
  Published article gate for unit browser.
- Artifact
  
  scripts/prove_static_first_starter_instantiation.py
  
  Kind
  
  validator
  
  Gate
  
  Published article gate for starter instantiation proof.
- Artifact
  
  scripts/validate_tutorial_scaffold.py
  
  Kind
  
  validator
  
  Gate
  
  Published article gate for scaffold validator.
- Artifact
  
  src/lib/articlePromotionReadiness.ts
  
  Kind
  
  helper
  
  Gate
  
  Focused unit tests evaluate promotion blockers and published readiness fixtures.
- Artifact
  
  src/lib/articlePromotionReadiness.test.ts
  
  Kind
  
  test
  
  Gate
  
  Focused unit tests reject incomplete records and accept complete published fixtures.

Source: blueprint-001
Accepted: Published article boundary for accepted artifact index.
Not Claimed: Published article boundary for rejected artifact index.

Claim Ledger

Platform Authoring Flow Claim Ledger

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

1. Source registration Accepted

Published article claim for source registration.

Source

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

Artifact

source_registry.yaml

Decision

Published article decision for source registration.

Gate

Published article gate for source registration.
2. Article data ownership Accepted

Published article claim for article data ownership.

Source

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

Artifact

data/article-claim-ledger.json

Decision

Published article decision for article data ownership.

Gate

Published article gate for article data ownership.
3. Evidence route Accepted

Published article claim for evidence route.

Source

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

Artifact

data/article-evidence-trail.json

Decision

Published article decision for evidence route.

Gate

Published article gate for evidence route.
4. Release decision Accepted

Published article claim for release decision.

Source

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

Artifact

data/article-release-handoff.json

Decision

Published article decision for release.

Gate

Published article gate for release decision.
5. Claim map route Accepted

Published article claim for claim map route.

Source

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

Artifact

data/article-claim-map.json

Decision

Published article decision for claim map route.

Gate

Published article gate for claim map route.
6. Proof manifest route Accepted

Published article claim for proof manifest route.

Source

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

Artifact

data/article-proof-manifest.json

Decision

Published article decision for proof manifest route.

Gate

Published article gate for proof manifest route.

Source: blueprint-001
Accepted: Published article boundary for accepted claim ledger.
Not Claimed: Published article boundary for rejected claim ledger.

Claim Map

Platform Authoring Flow 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

Published article gate for source registration route.
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

Published article gate for article data ownership route.
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

Published article gate for evidence route.
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

Published article gate for release decision route.
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

Published article gate for claim map route.
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

Published article gate for proof manifest route.

Source: blueprint-001
Accepted: Published article boundary for accepted claim map.
Not Claimed: Published article boundary for rejected claim map.

Evidence Trail

Platform Authoring Flow Evidence Trail

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

1. Platform claim Accepted

Published article claim for platform.

Source

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

Artifact

index.mdx

Gate

Published article gate for platform claim.
2. Article data Accepted

Published article claim for article data.

Source

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

Artifact

data/article-artifact-index.json

Gate

Published article gate for article data.
3. Verification stack Accepted

Published article claim for verification stack.

Source

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

Artifact

data/article-verification-matrix.json

Gate

Published article gate for verification stack.
4. Claim ledger Accepted

Published article claim for claim ledger.

Source

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

Artifact

data/article-claim-ledger.json

Gate

Published article gate for claim ledger.
5. Claim map Accepted

Published article claim for claim map.

Source

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

Artifact

data/article-claim-map.json

Gate

Published article gate for claim map.
6. Release handoff Accepted

Published article claim for release handoff.

Source

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

Artifact

data/article-release-handoff.json

Gate

Published article gate for release handoff.
7. Proof manifest Accepted

Published article claim for proof manifest.

Source

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

Artifact

data/article-proof-manifest.json

Gate

Published article gate for proof manifest.

Source: blueprint-001
Accepted: Published article boundary for accepted evidence trail.
Not Claimed: Published article boundary for rejected evidence trail.

Proof Manifest

Platform Authoring Flow Proof Manifest

Accepted local proof packets, owners, artifacts, gates, and release status for the published promotion boundary.

1. Source boundary proof Accepted

Proof ID

source-boundary-proof

Owner

Article folder

Artifact

data/source-boundary.json

Gate

Source boundary stays local to BLUEPRINT.md sections 5, 7, and 14.

Evidence

Typed source-boundary loader plus focused article tests prove blueprint-001 and the accepted/rejected source boundary.
2. Artifact index proof Accepted

Proof ID

artifact-index-proof

Owner

Authoring scaffold

Artifact

data/article-artifact-index.json

Gate

Artifact index must continue listing route-visible article files and support modules.

Evidence

Artifact index loader and focused article tests prove route, data, figure, support, and shared component coverage.
3. Claim ledger proof Accepted

Proof ID

claim-ledger-proof

Owner

Claim workflow

Artifact

data/article-claim-ledger.json

Gate

Claim ledger ownership stays article-local until a cross-article claim registry is separately proven.

Evidence

Claim ledger data parses through the shared schema and remains route-visible in the published proof packet.
4. Claim map proof Accepted

Proof ID

claim-map-proof

Owner

Claim workflow

Artifact

data/article-claim-map.json

Gate

Claim map ownership stays article-local until a reusable registry is separately proven.

Evidence

Claim map data parses through the shared schema and remains route-visible in the published proof packet.
5. Evidence trail proof Accepted

Proof ID

evidence-trail-proof

Owner

Evidence workflow

Artifact

data/article-evidence-trail.json

Gate

Evidence trail ownership stays article-local until cross-article evidence routing is separately proven.

Evidence

Evidence trail data parses through the shared schema and records the local source-backed path through the article packet.
6. Verification matrix proof Accepted

Proof ID

verification-matrix-proof

Owner

Verification workflow

Artifact

data/article-verification-matrix.json

Gate

Verification status does not imply live deployment or production monitoring.

Evidence

Verification matrix records focused commands and evidence for the published promotion packet.
7. Release handoff proof Accepted

Proof ID

release-handoff-proof

Owner

Release workflow

Artifact

data/article-release-handoff.json

Gate

Handoff records the published local route and catalog inclusion without claiming live deployment.

Evidence

Release handoff groups accepted article, validation, closeout, and next-work packets for the published local promotion boundary.
8. Proof manifest proof Accepted

Proof ID

proof-manifest-proof

Owner

Release workflow

Artifact

data/article-proof-manifest.json

Gate

Proof manifest acceptance stays local to source-controlled artifacts.

Evidence

Proof manifest itself lists accepted local proof records and artifact owners for the published route.
9. Release readiness proof Accepted

Proof ID

release-readiness-proof

Owner

Release workflow

Artifact

src/components/ArticleReleaseReadiness.astro

Gate

Release readiness remains a local rendered rollup, not a live deployment claim.

Evidence

ArticleReleaseReadiness consumes the accepted checklist, proof manifest, verification matrix, and release handoff records in the route.
10. Starter manifest proof Accepted

Proof ID

starter-manifest-proof

Owner

Authoring scaffold

Artifact

data/article-starter-manifest.json

Gate

Starter manifest acceptance does not publish a generated package.

Evidence

Starter manifest remains checked in and covered by the starter instantiation proof.
11. Starter workflow proof Accepted

Proof ID

starter-workflow-proof

Owner

Authoring scaffold

Artifact

data/article-starter-workflow.json

Gate

Starter workflow acceptance does not claim CMS or remote authoring behavior.

Evidence

Starter workflow remains checked in and covered by the starter instantiation proof.
12. Starter readiness proof Accepted

Proof ID

starter-readiness-proof

Owner

Authoring scaffold

Artifact

src/components/ArticleStarterReadiness.astro

Gate

Starter readiness remains local to source-controlled starter records.

Evidence

ArticleStarterReadiness renders the manifest/workflow rollup inside the route.
13. Starter handoff proof Accepted

Proof ID

starter-handoff-proof

Owner

Authoring scaffold

Artifact

src/components/ArticleStarterHandoff.astro

Gate

Starter handoff acceptance does not change starter template release status.

Evidence

ArticleStarterHandoff renders the starter and release handoff packet inside the route.
14. Platform authoring flow figure module proof Accepted

Proof ID

platform-authoring-flow-figure-module-proof

Owner

Authoring scaffold

Artifact

figures/PlatformAuthoringFlowFigure/PlatformAuthoringFlowFigure.tsx

Gate

Figure module acceptance is local static SVG behavior only.

Evidence

Focused figure tests and workbench coverage prove the article-owned static figure module.
15. Platform authoring flow figure style proof Accepted

Proof ID

platform-authoring-flow-figure-style-proof

Owner

Authoring scaffold

Artifact

figures/PlatformAuthoringFlowFigure/PlatformAuthoringFlowFigure.module.css

Gate

Figure style acceptance does not claim screenshot-baseline coverage.

Evidence

Focused figure tests and build/typecheck cover the article-owned figure style module.
16. Platform authoring flow figure model proof Accepted

Proof ID

platform-authoring-flow-figure-model-proof

Owner

Authoring scaffold

Artifact

figures/PlatformAuthoringFlowFigure/model.ts

Gate

Figure model acceptance stays within checked-in article data.

Evidence

Focused figure tests prove the model IDs, labels, and links used by the static figure.
17. Platform authoring flow figure proof data proof Accepted

Proof ID

platform-authoring-flow-figure-proof-data-proof

Owner

Authoring scaffold

Artifact

data/figure-proofs.json

Gate

Figure proof data acceptance does not claim live rendering outside local build/browser checks.

Evidence

Figure proof data names platform-authoring-flow-draft-figure with blueprint-001 source metadata.
18. Platform authoring flow figure proof loader proof Accepted

Proof ID

platform-authoring-flow-figure-proof-loader-proof

Owner

Authoring scaffold

Artifact

data/figureProofs.ts

Gate

Figure proof loader acceptance stays local to schema parsing and route import behavior.

Evidence

Figure proof loader parses article-owned proof data and exports platformAuthoringFlowFigureProof.
19. Promotion readiness proof Accepted

Proof ID

promotion-readiness-proof

Owner

Publication workflow

Artifact

data/promotion-readiness.json

Gate

Promotion readiness acceptance now targets published local catalog inclusion.

Evidence

Promotion readiness data and evaluator clear the release-record and public-catalog inclusion gates for the published local route.

Source: blueprint-001
Accepted: Accepts source-controlled proof packets required for the platform-authoring-flow-draft published local promotion-readiness gate.
Not Claimed: Does not claim live deployment freshness, CMS workflow, remote source fetching, generated package release, or production monitoring.

Verification Matrix

Platform Authoring Flow Verification Matrix

The matrix records accepted local commands, targets, and evidence that must stay green before this published route changes release status.

1. Source and data gates Accepted

Accepted source, article data, starter, figure, and promotion-readiness checks for the local published route.
- Article unit Accepted
  
  Command
  
  npm run test -- src/content/essays/platformAuthoringFlowDraft.test.ts src/lib/articlePromotionReadiness.test.ts src/lib/articlePreviewRegistry.test.ts src/data/figureWorkbenchCoverage.test.ts
  
  Target
  
  static-first starter templates
  
  Evidence
  
  platformAuthoringFlowDraft.test.ts and related registry/workbench tests pass for article metadata, promotion readiness, catalog exclusion, and figure coverage.
- Starter unit Accepted
  
  Command
  
  npm run article:create:pipeline:proof
  
  Target
  
  static-first starter templates
  
  Evidence
  
  The article creation pipeline proof covers temp-app route generation, starter proof, temp typecheck/build, and static route smoke.
- Starter manifest contract Accepted
  
  Command
  
  npm run starter:instantiate:proof
  
  Target
  
  data/article-starter-manifest.json and src/content/essay-starters/static-first/
  
  Evidence
  
  The starter instantiation proof validates generated starter manifest coverage and artifact handoff records.
- Starter workflow contract Accepted
  
  Command
  
  npm run starter:instantiate:proof
  
  Target
  
  data/article-starter-workflow.json and src/components/ArticleStarterWorkflow.astro
  
  Evidence
  
  The starter instantiation proof validates generated starter workflow coverage and scaffold handoff records.
- Platform authoring flow figure proof packet Accepted
  
  Command
  
  npm run test -- src/content/essays/platformAuthoringFlowDraft.test.ts src/content/essays/platform-authoring-flow-draft/figures/PlatformAuthoringFlowFigure/PlatformAuthoringFlowFigure.test.tsx
  
  Target
  
  figures/PlatformAuthoringFlowFigure/PlatformAuthoringFlowFigure.tsx, figures/PlatformAuthoringFlowFigure/PlatformAuthoringFlowFigure.module.css, figures/PlatformAuthoringFlowFigure/model.ts, data/figure-proofs.json, and data/figureProofs.ts
  
  Evidence
  
  Focused tests cover the article-specific figure model, static markup, proof metadata, and article handoff.
- Promotion readiness gate Accepted
  
  Command
  
  npm run test -- src/content/essays/platformAuthoringFlowDraft.test.ts src/lib/articlePromotionReadiness.test.ts
  
  Target
  
  data/promotion-readiness.json, data/promotionReadiness.ts, src/components/ArticlePromotionReadiness.astro, and src/lib/articlePromotionReadiness.ts
  
  Evidence
  
  Focused tests cover the promotion-readiness schema, evaluation gates, and accepted release-record packet.
2. Static build gates Accepted

Accepted static build checks for Astro content and TypeScript imports.
- Typecheck Accepted
  
  Command
  
  npm run typecheck
  
  Target
  
  Astro content collection and TypeScript project
  
  Evidence
  
  Astro content, route imports, and TypeScript loaders typecheck.
- Production build Accepted
  
  Command
  
  npm run build
  
  Target
  
  static Astro build
  
  Evidence
  
  The static Astro build renders the published route with promotion-readiness records.
3. Browser and visual gates Accepted

Accepted browser, visual, starter, release, and Storybook checks for the published boundary.
- Focused browser smoke Accepted
  
  Command
  
  npm run test:browser:ci -- tests/article-preview-registry.spec.ts tests/figure-authoring-workbench.spec.ts
  
  Target
  
  static-first starter templates
  
  Evidence
  
  Focused browser checks cover the authoring preview route, public catalog inclusion, remaining draft exclusion, and accepted workbench figure coverage.
- Release readiness rollup Accepted
  
  Command
  
  npm run release:readiness:check
  
  Target
  
  static-first starter templates
  
  Evidence
  
  Aggregate local release-readiness preserves manifest, typecheck, starter proof, build, and build-output gates.
- Starter readiness rollup Accepted
  
  Command
  
  npm run starter:instantiate:proof
  
  Target
  
  static-first starter templates
  
  Evidence
  
  Starter readiness remains covered by the generated starter instantiation proof.
- Starter handoff packet Accepted
  
  Command
  
  npm run article:create:pipeline:proof
  
  Target
  
  static-first starter templates
  
  Evidence
  
  Pipeline proof preserves starter handoff metadata while creating a temp article route.
- Storybook build Accepted
  
  Command
  
  npm run build-storybook
  
  Target
  
  Storybook static build
  
  Evidence
  
  Storybook static build covers shared component/story surfaces used by the article platform.
4. Closeout gates Accepted

Accepted closeout checks for diff and scaffold alignment.
- Diff check Accepted
  
  Command
  
  git diff --check
  
  Target
  
  tracked working tree diff
  
  Evidence
  
  Tracked text changes have no whitespace errors.
- Scaffold validator Accepted
  
  Command
  
  python3 scripts/validate_tutorial_scaffold.py
  
  Target
  
  tutorial scaffold ledgers
  
  Evidence
  
  Scaffold validation keeps queue, ledgers, artifact metadata, and prompt guardrails aligned.

Source: blueprint-001
Accepted: Accepts local unit, browser, typecheck, build, changed-surface, starter, Storybook, scaffold, and diff commands as the publication evidence packet.
Not Claimed: Does not claim live deployment freshness, production monitoring, remote source fetching, CMS workflow, or published public-catalog inclusion.

Release Handoff

Platform Authoring Flow Release Handoff

The handoff records accepted local article, validation, ledger, and next-work packets for the published catalog boundary.

1. Article packet Accepted

Accepted local route and source-boundary packet; publication status is published locally.
- Route status boundary Accepted
  
  Artifact
  
  index.mdx
  
  Gate
  
  Focused article tests check slug, status, route copy, and public catalog inclusion.
  
  Evidence
  
  Frontmatter is published and route-visible while deployment freshness remains out of scope.
- Source boundary record Accepted
  
  Artifact
  
  data/source-boundary.json
  
  Gate
  
  Focused article tests verify sourceBoundary fields and route copy.
  
  Evidence
  
  blueprint-001 source metadata and accepted/rejected boundaries are typed and route-rendered.
2. Validation packet Accepted

Accepted article-owned validation, proof, starter, figure, and browser packets for promotion readiness.
- Claim ledger Accepted
  
  Artifact
  
  data/article-claim-ledger.json
  
  Gate
  
  Shared article data schemas and focused article tests cover the loader.
  
  Evidence
  
  Article-owned claim ledger is parsed and route-rendered.
- Claim map Accepted
  
  Artifact
  
  data/article-claim-map.json
  
  Gate
  
  Shared article data schemas and focused article tests cover the loader.
  
  Evidence
  
  Article-owned claim map is parsed and route-rendered.
- Proof manifest Accepted
  
  Artifact
  
  data/article-proof-manifest.json
  
  Gate
  
  articleProofManifest.ts parses the manifest and focused article tests cover promotion records.
  
  Evidence
  
  Proof manifest records accepted proof owners and artifacts.
- Evidence trail Accepted
  
  Artifact
  
  data/article-evidence-trail.json
  
  Gate
  
  Shared article data schemas and focused article tests cover the loader.
  
  Evidence
  
  Article-owned evidence trail is parsed and route-rendered.
- Verification matrix Accepted
  
  Artifact
  
  data/article-verification-matrix.json
  
  Gate
  
  articleVerificationMatrix.ts parses the matrix and focused tests cover accepted statuses.
  
  Evidence
  
  Verification matrix records accepted commands, targets, and evidence.
- Platform authoring flow figure proof packet Accepted
  
  Artifact
  
  figures/PlatformAuthoringFlowFigure/PlatformAuthoringFlowFigure.tsx, figures/PlatformAuthoringFlowFigure/PlatformAuthoringFlowFigure.module.css, figures/PlatformAuthoringFlowFigure/model.ts, data/figure-proofs.json, and data/figureProofs.ts
  
  Gate
  
  Focused figure tests, figure workbench coverage, and browser checks cover the packet.
  
  Evidence
  
  Article-owned figure module, model, style, proof data, and proof loader are accepted with workbench/design coverage.
- Release readiness Accepted
  
  Artifact
  
  src/components/ArticleReleaseReadiness.astro
  
  Gate
  
  Route rendering plus focused article tests cover the release-readiness packet.
  
  Evidence
  
  Release readiness rollup consumes accepted checklist, proof, verification, and handoff records.
- Promotion readiness Accepted
  
  Artifact
  
  data/promotion-readiness.json and src/components/ArticlePromotionReadiness.astro
  
  Gate
  
  Focused promotion-readiness tests cover ready and blocked evaluations.
  
  Evidence
  
  Promotion readiness now clears release-record blockers while preserving the published route boundary.
- Starter manifest Accepted
  
  Artifact
  
  data/article-starter-manifest.json
  
  Gate
  
  npm run starter:instantiate:proof validates starter manifest handoff.
  
  Evidence
  
  Starter manifest stays checked in and covered by starter instantiation proof.
- Starter workflow Accepted
  
  Artifact
  
  data/article-starter-workflow.json
  
  Gate
  
  npm run starter:instantiate:proof validates starter workflow handoff.
  
  Evidence
  
  Starter workflow stays checked in and covered by starter instantiation proof.
- Starter readiness Accepted
  
  Artifact
  
  src/components/ArticleStarterReadiness.astro
  
  Gate
  
  Focused article route tests and starter proof cover this rollup.
  
  Evidence
  
  Starter readiness component renders manifest/workflow coverage in the route.
- Starter handoff Accepted
  
  Artifact
  
  src/components/ArticleStarterHandoff.astro
  
  Gate
  
  Focused article route tests and article pipeline proof cover this rollup.
  
  Evidence
  
  Starter handoff component renders starter and release handoff records in the route.
- Focused browser proof Accepted
  
  Artifact
  
  tests/article-preview-registry.spec.ts and tests/figure-authoring-workbench.spec.ts
  
  Gate
  
  npm run test:browser:ci -- tests/article-preview-registry.spec.ts tests/figure-authoring-workbench.spec.ts
  
  Evidence
  
  Focused browser checks cover authoring preview metadata, catalog exclusion, and accepted workbench coverage.
3. Closeout packet Accepted

Accepted closeout ledgers required for this automation run.
- Run log ledger Accepted
  
  Artifact
  
  run_log.md
  
  Gate
  
  Final scaffold validation checks run-log and queue consistency.
  
  Evidence
  
  Run log records the accepted TUT-300 artifact, validation, and residual boundaries at closeout.
- Evidence ledger Accepted
  
  Artifact
  
  evidence_ledger.yaml
  
  Gate
  
  Final scaffold validation checks evidence ledger structure.
  
  Evidence
  
  Evidence ledger records TUT-300 accepted promotion-record evidence at closeout.
4. Next work packet Accepted

Accepted queue and starter-template handoff for the next numeric todo.
- Queue state Accepted
  
  Artifact
  
  state.md and todo.md
  
  Gate
  
  Final scaffold validation checks active todo alignment.
  
  Evidence
  
  Queue state advances from TUT-300 to the next numeric Platform Authoring Infrastructure todo after validation.
- Starter template Accepted
  
  Artifact
  
  src/content/essay-starters/static-first/
  
  Gate
  
  npm run starter:instantiate:proof and article pipeline proof cover the starter template boundary.
  
  Evidence
  
  The starter template remains the source of the generated starter shell and is protected by starter instantiation proof.

Source: blueprint-001
Accepted: Accepts source-controlled article, validation, closeout, and next-work handoff records for the published local promotion-readiness packet.
Not Claimed: Does not claim live deployment freshness or CMS/remote source workflow behavior.

Release Readiness

Release Readiness Rollup

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

Checklist: 6/6 Ready; platform-authoring-flow-draft-article-checklist
Proof Manifest: 19/19 Ready; platform-authoring-flow-draft-article-proof-manifest
Verification Matrix: 15/15 Ready; platform-authoring-flow-draft-article-verification-matrix
Release Handoff: 19/19 Ready; platform-authoring-flow-draft-article-release-handoff

Checklist platform-authoring-flow-draft-article-checklist
Proof Manifest platform-authoring-flow-draft-article-proof-manifest
Verification Matrix platform-authoring-flow-draft-article-verification-matrix
Release Handoff platform-authoring-flow-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

Platform Authoring Flow 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

Published article summary for content shell.
- Article MDX Accepted
  
  Kind
  
  content
  
  Path
  
  index.mdx
  
  Gate
  
  Published article gate for article mdx.
- Essay config Accepted
  
  Kind
  
  configuration
  
  Path
  
  essay.config.ts
  
  Gate
  
  Published article gate for essay config.
- Assets folder Accepted
  
  Kind
  
  folder
  
  Path
  
  assets/
  
  Gate
  
  Published article gate for assets folder.
- Figures folder Accepted
  
  Kind
  
  folder
  
  Path
  
  figures/
  
  Gate
  
  Published article gate for figures folder.
- Platform authoring flow figure module Accepted
  
  Kind
  
  figure
  
  Path
  
  figures/PlatformAuthoringFlowFigure/PlatformAuthoringFlowFigure.tsx
  
  Gate
  
  Published article gate for platform authoring flow figure module.
- Platform authoring flow figure style Accepted
  
  Kind
  
  style
  
  Path
  
  figures/PlatformAuthoringFlowFigure/PlatformAuthoringFlowFigure.module.css
  
  Gate
  
  Published article gate for platform authoring flow figure style.
- Platform authoring flow figure model Accepted
  
  Kind
  
  model
  
  Path
  
  figures/PlatformAuthoringFlowFigure/model.ts
  
  Gate
  
  Published article gate for platform authoring flow figure model.
2. Article data Accepted

Published article summary for article data.
- Source boundary Accepted
  
  Kind
  
  data
  
  Path
  
  data/source-boundary.json
  
  Gate
  
  Published article gate for source boundary.
- Starter manifest Accepted
  
  Kind
  
  data
  
  Path
  
  data/article-starter-manifest.json
  
  Gate
  
  Published article gate for starter manifest.
- Starter workflow Accepted
  
  Kind
  
  data
  
  Path
  
  data/article-starter-workflow.json
  
  Gate
  
  Published article gate for starter workflow.
- Artifact index Accepted
  
  Kind
  
  data
  
  Path
  
  data/article-artifact-index.json
  
  Gate
  
  Published article gate for artifact index.
- Proof manifest Accepted
  
  Kind
  
  data
  
  Path
  
  data/article-proof-manifest.json
  
  Gate
  
  Published article gate for proof manifest.
- Verification matrix Accepted
  
  Kind
  
  data
  
  Path
  
  data/article-verification-matrix.json
  
  Gate
  
  Published article gate for verification matrix.
- Release handoff Accepted
  
  Kind
  
  data
  
  Path
  
  data/article-release-handoff.json
  
  Gate
  
  Published article gate for release handoff.
- Figure proofs Accepted
  
  Kind
  
  data
  
  Path
  
  data/figure-proofs.json
  
  Gate
  
  Published article gate for figure proofs.
- Figure proofs loader Accepted
  
  Kind
  
  loader
  
  Path
  
  data/figureProofs.ts
  
  Gate
  
  Published article gate for figure proofs loader.
3. Starter templates Accepted

Published article summary for starter templates.
- Starter README Accepted
  
  Kind
  
  documentation
  
  Path
  
  src/content/essay-starters/static-first/README.md
  
  Gate
  
  Published article gate for starter readme.
- MDX template Accepted
  
  Kind
  
  template
  
  Path
  
  src/content/essay-starters/static-first/index.mdx.template
  
  Gate
  
  Published article gate for starter mdx template.
- Config template Accepted
  
  Kind
  
  template
  
  Path
  
  src/content/essay-starters/static-first/essay.config.ts.template
  
  Gate
  
  Published article 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
  
  Published article gate for starter data template.
- Starter manifest schema template Accepted
  
  Kind
  
  template
  
  Path
  
  src/content/essay-starters/static-first/data/articleStarterManifest.ts.template
  
  Gate
  
  Published article 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
  
  Published article 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
  
  Published article gate for starter workflow schema template.
- Starter readiness component placement Accepted
  
  Kind
  
  template
  
  Path
  
  src/content/essay-starters/static-first/index.mdx.template
  
  Gate
  
  Published article gate for starter readiness component template.
- Starter handoff component placement Accepted
  
  Kind
  
  template
  
  Path
  
  src/content/essay-starters/static-first/index.mdx.template
  
  Gate
  
  Published article gate for starter handoff component template.
4. Verification handoff Accepted

Published article summary for verification handoff.
- Article unit test Accepted
  
  Kind
  
  test
  
  Path
  
  src/content/essays/staticFirstEssay.test.ts
  
  Gate
  
  Published article gate for article unit test.
- Starter unit test Accepted
  
  Kind
  
  test
  
  Path
  
  src/content/essay-starters/articleStarter.test.ts
  
  Gate
  
  Published article gate for starter unit test.
- Starter instantiation proof Accepted
  
  Kind
  
  validator
  
  Path
  
  scripts/prove_static_first_starter_instantiation.py
  
  Gate
  
  Published article gate for starter instantiation proof.
- Browser smoke Accepted
  
  Kind
  
  test
  
  Path
  
  tests/home.spec.ts
  
  Gate
  
  Published article gate for browser smoke.
- Scaffold validator Accepted
  
  Kind
  
  validator
  
  Path
  
  scripts/validate_tutorial_scaffold.py
  
  Gate
  
  Published article gate for scaffold validator.

Source: blueprint-001
Accepted: Published article boundary for accepted starter manifest.
Not Claimed: Published article boundary for rejected starter manifest.

Starter Workflow

Platform Authoring Flow Starter Workflow

Published starter workflow for turning the copied folder into a source-registered article.

1. Copy starter Accepted

Copy the starter folder into the essay collection, then replace the starter figure with the article-owned platform authoring flow figure before workbench acceptance.

Artifact

src/content/essay-starters/static-first/ and figures/PlatformAuthoringFlowFigure/

Gate

Starter unit coverage verifies the source folder contract before a new article copies it.
2. Replace placeholders Accepted

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

Artifact

index.mdx and essay.config.ts

Gate

Focused article tests reject unresolved placeholder tokens and verify the rendered route copy.
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: Published article boundary for accepted starter workflow.
Not Claimed: Published article boundary for rejected starter workflow.

Starter Readiness

Starter Readiness Rollup

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

Manifest Groups: 4/4 Ready; platform-authoring-flow-draft-article-starter-manifest
Manifest Entries: 30/30 Ready; platform-authoring-flow-draft-article-starter-manifest
Workflow Steps: 6/6 Ready; platform-authoring-flow-draft-article-starter-workflow

Starter Manifest platform-authoring-flow-draft-article-starter-manifest
Starter Workflow platform-authoring-flow-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: 30/30 Ready; platform-authoring-flow-draft-article-starter-manifest
Starter Workflow: 6/6 Ready; platform-authoring-flow-draft-article-starter-workflow
Starter Readiness: 10/10 Ready; platform-authoring-flow-draft-shared-starter-readiness
Release Handoff: 19/19 Ready; platform-authoring-flow-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

Platform Authoring Flow Publication Workflow

The workflow records accepted local source, QA, release handoff, and catalog milestones for the published route.

1. Published route shell Accepted

The source-backed published route renders article prose, local proof components, and the article-owned figure.

Artifact

index.mdx

Gate

Focused article tests check frontmatter, route copy, imports, and placeholder cleanup.
2. Source boundary Accepted

The route renders the accepted blueprint-001 source boundary and rejected remote/source claims.

Artifact

data/source-boundary.json

Gate

Focused article tests verify source-boundary metadata.
3. Publish readiness Accepted

Publish-readiness routing remains explicit: local records are accepted, but frontmatter is published.

Artifact

ArticlePublicationWorkflow.astro and ArticlePromotionReadiness.astro

Gate

Promotion-readiness focused tests verify ready local gates without catalog inclusion.
4. Claim ledger Accepted

Claim ledger remains article-owned and route-rendered.

Artifact

ArticleClaimLedger.astro and data/article-claim-ledger.json

Gate

Shared schema parsing and focused article route tests cover the claim ledger.
5. Claim map Accepted

Claim map remains article-owned and route-rendered.

Artifact

ArticleClaimMap.astro and data/article-claim-map.json

Gate

Shared schema parsing and focused article route tests cover the claim map.
6. Evidence trail Accepted

Evidence trail remains article-owned and route-rendered.

Artifact

ArticleEvidenceTrail.astro and data/article-evidence-trail.json

Gate

Shared schema parsing and focused article route tests cover the evidence trail.
7. Proof manifest Accepted

Proof manifest records accepted local proof owners, artifacts, gates, and evidence.

Artifact

ArticleProofManifest.astro and data/article-proof-manifest.json

Gate

Focused promotion-record tests cover accepted release statuses.
8. Release handoff Accepted

Release handoff records accepted article, validation, closeout, and next-work packets.

Artifact

ArticleReleaseHandoff.astro and data/article-release-handoff.json

Gate

Focused promotion-record tests cover accepted handoff statuses.
9. Release readiness Accepted

Release readiness consumes accepted checklist, proof, verification, and handoff records.

Artifact

ArticleReleaseReadiness.astro

Gate

Route rendering and focused tests cover the rollup.
10. Starter manifest Accepted

Starter manifest remains checked in and starter-proofed.

Artifact

ArticleStarterManifest.astro and data/article-starter-manifest.json

Gate

npm run starter:instantiate:proof covers the starter manifest.
11. Starter workflow Accepted

Starter workflow remains checked in and starter-proofed.

Artifact

ArticleStarterWorkflow.astro and data/article-starter-workflow.json

Gate

npm run starter:instantiate:proof covers the starter workflow.
12. Starter readiness Accepted

Starter readiness renders the starter manifest/workflow rollup.

Artifact

ArticleStarterReadiness.astro

Gate

Route rendering and starter proof cover the rollup.
13. Starter handoff Accepted

Starter handoff renders starter readiness with release handoff records.

Artifact

ArticleStarterHandoff.astro

Gate

Route rendering and article pipeline proof cover the handoff.
14. Promotion readiness Accepted

Promotion readiness clears local release-record blockers while preserving published status.

Artifact

ArticlePromotionReadiness.astro and data/promotion-readiness.json

Gate

Focused promotion-readiness tests cover the local ready state.

Source: blueprint-001
Accepted: Accepts the source-controlled local publication workflow for platform-authoring-flow-draft published catalog inclusion.
Not Claimed: Does not claim CMS workflow, remote source fetching, live deployment freshness, automatic promotion, or production monitoring.

Promotion readiness

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/platformAuthoringFlowDraft.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 authoring-preview registry metadata, public catalog inclusion, and remaining draft exclusion.
npm run test:browser:ci -- tests/figure-authoring-workbench.spec.ts Proves accepted workbench coverage for the article-specific figure.
npm run typecheck Proves Astro content and TypeScript imports before publication metadata changes.
npm run build Proves the static route builds with the promotion-readiness gate rendered.
npm run release:build-output:check Proves built catalog, RSS, published route, tag route, and remaining draft exclusion output after publication.
npm run quality:changed -- --summary-json /tmp/tutorial-tut301-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.

Authoring Flow

Platform Authoring Flow Authoring Flow

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

1. Source-register the claim Accepted

Published article checkpoint for source registration.

Artifact

data/source-boundary.json

Gate

Focused article tests verify the source boundary and registered source ID.
2. Localize article artifacts Accepted

Published article checkpoint for localized article artifacts.

Artifact

data/

Gate

Focused article tests verify article-owned data, proof metadata, and artifact coverage.
3. Render static primitives Accepted

Published article checkpoint for static route primitives.

Artifact

index.mdx

Gate

Build and build-output checks verify the route renders in the published catalog surface.
4. Close verification gates Accepted

Published article checkpoint for close verification.

Artifact

tests

Gate

Focused unit, browser, typecheck, build, build-output, changed-surface, scaffold, and diff checks guard the publication boundary.
5. Authoring preview registry Accepted

Published article checkpoint for registry preview.

Artifact

src/pages/authoring/article-preview.astro

Gate

Focused registry coverage verifies the published route, source IDs, figure count, catalog inclusion, and remaining draft exclusion.

Source: blueprint-001
Accepted: Published local article boundary for accepted authoring flow.
Not Claimed: Rejects live deployment freshness, CMS workflow, remote source fetching, and automatic article promotion.

Article Checklist

Platform Authoring Flow Publication Checklist

The checklist records the accepted local evidence packet for the published route and catalog boundary.

Frontmatter and catalog Accepted

Frontmatter keeps slug platform-authoring-flow-draft and status published while focused catalog coverage proves the route appears in published catalog data.
Gate: src/content/essays/platformAuthoringFlowDraft.test.ts checks route frontmatter and public catalog inclusion.
Source boundary Accepted

source-boundary.json registers blueprint-001 with BLUEPRINT.md sections 5, 7, and 14 as the accepted local source boundary.
Gate: Typed source-boundary loading and focused article tests reject unresolved starter placeholders and unregistered source drift.
Article-owned data Accepted

Article-owned data files, typed loaders, proof metadata, and artifact-index entries parse through the checked-in article data schemas.
Gate: src/content/essays/platformAuthoringFlowDraft.test.ts checks the route-visible data packet and artifact-index coverage.
Interactive scope Accepted

The article renders the article-owned static PlatformAuthoringFlowFigure through FigureProof and accepted Figure Authoring Workbench coverage.
Gate: Figure workbench and design acceptance records keep this figure inside local static visual QA scope.
Verification stack Accepted

The promotion packet names focused unit, browser, typecheck, build, build-output, changed-surface, scaffold, and diff commands for this published boundary.
Gate: promotion-readiness.json and the verification matrix list the required local commands for the published route.
Promotion readiness Accepted

ArticlePromotionReadiness evaluates route metadata, registry metadata, workbench coverage, catalog boundary, release records, and focused commands together.
Gate: src/lib/articlePromotionReadiness.test.ts and platformAuthoringFlowDraft.test.ts cover blocked and ready evaluations.

Source: blueprint-001
Accepted: Accepts local published-route metadata, article-owned data, source-boundary, static figure, registry, workbench, and focused validation evidence for promotion readiness.
Not Claimed: Does not claim live deployment freshness, CMS workflow, remote source fetching, or automatic article promotion.