Skip to main content

​
Content Writing Pipeline

How a v2/ documentation page goes from “needed” to “published”. Two pipelines run in sequence:
  1. The project pipeline (this page) – 9 stages, applies to a tab or a section of the docs. Takes a tab from “audience defined” to “all pages shipped.”
  2. The per-page review pipeline (Checks Framework) – 11 phases, applies to a single page once written. Takes a page from “drafted” to “approved for publication.”
The project pipeline writes the pages. The review pipeline ships them. Neither phase ships without the prior phase’s human sign-off recorded in workspace/plan/active/CONTENT-WRITING/decisions/decision-registry.md.
Where this pipeline canonical lives. The full project execution plan (997 lines) and per-stage tooling live under workspace/plan/active/_MY_PROCESS/ + workspace/plan/active/CONTENT-WRITING/. This page is the published reference. Locked structural decisions (D-NAV-01 currently) live in the decision-registry. Per-tab gate status lives in tab-status.md. As of 2026-05-23, no tab has IA Approved – all 5 are stuck at Phase 2 or earlier.

​
Page taxonomy

Every routable v2/ page declares 10 frontmatter fields. The enumerations below are canonical.

​
pageType (7 primary)

​
pageVariant (refines pageType)

overview is a cross-type variant for entry/orientation pages within a section. knowledge-hub is the resource variant for external/community content (no instructional content mixed in).

​
audience (7 tokens)

founder → builder → developer → gateway is the documented graduation path. Per-persona refinements (e.g. builder [studio, ai], orchestrator [operator, commercial]) are an optional array field; full enumeration in the content-pipeline-framework.

​
purpose (15 intent-based values)

orient · explain · learn · choose · evaluate · start · build · configure · operate · troubleshoot · verify · integrate · optimise · reference · update Deprecated aliases that still appear in some files but should not be authored: landing → use orient. overview → use orient. orientation → use orient. setup → use configure. how_to → use build or configure. operations → use operate. tutorial → use learn. evaluation → use choose. decision → use choose. faq, glossary → use reference. changelog → use update. troubleshooting → use troubleshoot.

​
Information types (9, section-level)

factual · conceptual · procedural · analytical · evaluative · structural · change · narrative · technical Information type is section-level, identified by the author at runtime per section. It is not a frontmatter field. The veracity standard that applies to each section is derived from its information type:

​
Other frontmatter fields

The full required minimum frontmatter for every routable page is documented in docs-guide/standards/frontmatter.mdx and enforced (advisory) by the per-page review pipeline.

​
Voice and copy

UK English throughout. The full canonical rules – banned words, banned phrases, banned constructions, opening order, paragraph discipline, per-audience extensions, heading rules, domain terminology – live in docs-guide/standards/voice-and-copy.mdx. Working source with full per-audience prohibited-phrase lists: workspace/plan/active/CONTENT-WRITING/Prompts/voice-rules.md.

​
The 9-stage project pipeline

This pipeline applies to a whole tab (or a section of one). Each stage has a human gate; the next stage cannot start until the prior gate is opened in tab-status.md. Canonical source: workspace/plan/active/_MY_PROCESS/my-process.mdx. Full per-stage inventory (with usefulness scores per item) lives in _MY_PROCESS/index.md. Stage 7 = Phases 0–6 of the per-page review pipeline. Stage 8 = Phase 7 of the per-page review pipeline. Stage 9 = Phase 10. The two pipelines interlock at these points.

​
Locked decisions

No phase may consume a decision that is not in this registry. Decisions made in chat that are not written here do not exist. Proposals and open items go in blocking-items.md, not the registry.

​
Current state (as of 2026-05-23)

Per tab-status.md: Legend: ⬜ not started · 🔄 in progress · ✅ human-approved. Zero tabs have IA Approved. The project pipeline is stalled at Phase 2 or earlier across the entire docs estate. A tab is only “open” for the next phase when its gate is explicitly unlocked by human sign-off recorded in decision-registry.md. Agents may not proceed past a locked gate.

​
Supporting infrastructure

The full inventory lives in _MY_PROCESS/index.md – every item per stage with usefulness score, status, and known issues. Summary by category:

​
AI skills (live as of 2026-05-23)

Note (2026-05-23): the parent audit of all 34 local SKILL.md files found 18 still carry status: draft with empty test logs (see SLICE-02-ai-tools.md for the live status per skill).

​
Prompts

Per-phase pack guides (pre-flight + running order + failure modes) live alongside each prompt at workspace/plan/active/CONTENT-WRITING/Prompts/Prompts-By-Phase/{N-phase}/pack-guide.md.

​
Canonical frameworks

​
Automated scripts (production-ready)

​
Known gaps (2026-05-23, verified)

The pipeline is real but incomplete. Five blockers prevent any tab moving past Phase 2 today.

​
Tab maps do not exist at the canonical location

The per-page review pipeline (content-pipeline-pass-a skill) requires a tab map at v2/{tab}/_workspace/tab-map.mdx before it can run with full adjacency context. No tab map exists at the canonical location for any tab. The Orchestrators tab map exists in workspace output (workspace/plan/active/CONTENTI-PIPLEINE/03-tab-map.md – note the misspelled folder name) but not at the canonical location. Unblocks: project pipeline Phase 5 onwards for any tab. Action: move or symlink the ORCHS tab map into v2/orchestrators/_workspace/tab-map.mdx; produce equivalents for the other 4 tabs.

​
veracity-pass.md is DRAFT and unvalidated

The veracity pass prompt at workspace/plan/active/CONTENT-WRITING/Prompts/Prompts-By-Phase/7-veracity-pass/veracity-pass.md is explicitly DRAFT in its header and in PROJECT-MANAGEMENT-CANONICAL.md. The pack guide requires 3 test runs with human sign-off before production. No test runs are recorded. Unblocks: per-page review Phase 6 (veracity pass). Action: run 3 test passes on pages with governance-controlled values, CLI flag claims, and mixed information types; record results; human sign-off.

​
Frontmatter validator path is wrong in multiple references

page-authoring/SKILL.md and master-checks.mdx reference tools/config/frontmatter-taxonomy.js and tools/lib/docs/frontmatter-taxonomy.js. Neither path appears in the current tools/ tree. The automated frontmatter validator either does not exist, exists under a different name, or has been retired without updating references. Unblocks: automated frontmatter validation in the per-page review pipeline. Action: locate the current frontmatter validator (if any) and update all references, or confirm absence and remove the references from prompts and skill files.

​
page-taxonomy-framework.mdx and page-composition-framework.mdx are scratch notes

Per the parallel slice audit (SLICE-08-snippets.md and prior session findings), both files sit under docs-guide/frameworks/ but are not real frameworks. page-composition-framework.mdx is a literal MDX template scaffold with placeholder description “Describe page-structure-template”. page-taxonomy-framework.mdx has no frontmatter and contains typo’d field labels. Action: either rewrite both as real frameworks (sourcing from v2/orchestrators/_workspace/canonical/Frameworks.mdx) or move both to _workspace/ lane.

​
Three pageType enumerations are in circulation

The canonical 7-type schema (above) is correct. However: docs-guide/frameworks/page-taxonomy-framework.mdx (scratch notes) has different enums; workspace/plan/active/ORCHS/01-CORE-NEEDS-AND-STANDARDS.md frontmatter schema lists deprecated values (landing, faq, troubleshooting as pageType values, not pageVariants); v2/resources/documentation-guide/copy-style/authoring-guide.mdx (public) also lists a subset. Agents following the wrong source will produce wrong frontmatter. Action: lock one canonical pageType enum on this page; have all other sources transclude or be marked deprecated.
  • Checks Framework – the per-page review pipeline that operationalises Stage 7 + 8 + 9 above (11 phases, 9 universal check categories, per-pageType specific checks).
  • docs-guide/standards/voice-and-copy.mdx – canonical voice + copy + heading rules.
  • docs-guide/standards/frontmatter.mdx – frontmatter required minimum + per-tier rules.
  • docs-guide/standards/naming-conventions.mdx – file + folder + script + workflow naming.
  • docs-guide/policies/source-of-truth-policy.mdx – canonical-source contract for every governed surface.
  • workspace/plan/active/_MY_PROCESS/ – full 9-stage project pipeline source.
  • workspace/plan/active/CONTENT-WRITING/ – execution plan, decisions registry, tab status, prompts, frameworks (997 lines + 240 supporting files).
  • workspace/plan/active/master-checks.mdx – meta-checks framework (882 lines) referenced from the per-tab canonical/checks.mdx files.
  • v2/{tab}/_workspace/canonical/checks.mdx – per-tab Cat 1-9 quality spec (exists for gateways, orchestrators, about, delegators, developers1 as of 2026-05-23).
Last modified on May 22, 2026