Skip to content

Semantic artefact to enterprise publication

Trigger

A specialist artefact is substantively complete and requires enterprise-grade publication.

Intended outcome

A released audience-specific publication whose semantic content is traceable to the approved source and has passed semantic and publication gates.

Workflow steps and gates

Step Accountable role Activity Handover Gate
1 Owning specialist finalises claims, decisions, assumptions, evidence and acceptance criteria semantic publication model Semantic source is complete enough to review; unresolved items are explicit
2 Evidence & Rationale Reviewer checks evidence strength, assumptions, alternatives, rationale and residual risk semantic gate result and located findings Semantic Gate PASS or explicit waiver by named authority
3 Enterprise Publication Editor selects publication archetype and renders audience-specific DOCX/PPTX/XLSX/HTML/SVG outputs rendered publication set with semantic hash All outputs carry the same semantic SHA-256 and required document control
4 Visual Quality Reviewer checks density, hierarchy, legibility, tables, diagrams, document control and package integrity publication gate result and findings Publication Gate PASS; material defects are resolved or explicitly waived
5 Named authority approves consequential publication for release release approval Approval is by an authority independent of the publication editor where governance requires it

Running this workflow: operator and implementer boundary

In Claude Code or Codex CLI, use the prompt in the next section (or adapt it to your programme): it is a provider conversation request, not a shell program named after this workflow. You supply the source materials, actual owners, gate acceptance and any authorisation for changing real systems. The provider agent interprets the registered workflow stages and role contracts, calls supported tools if allowed, and returns explicit evidence and blockers. Stage completion in the diagram or metadata is not proof of a successful external tool call, an approved exception or a released system.

For consequential decisions explicitly start /layered (Claude) or $workflow-layered (Codex); this version does not force every direct/natural-language workflow invocation into Fabric. Human L0 authority remains separate, with Codex requiring the actual human to run any protected authority command in a trusted terminal. See the interaction model, layered engagement and human authority.

How to use this workflow

A practical prompt pattern is:

Apply the semantic-to-enterprise-publication workflow to this situation. For each step, identify the current state, accountable role, required evidence, hand-over artefact, gate status and unresolved blocker. Do not skip a gate merely because the implementation is technically complete.

Operational interpretation

The workflow is most useful when the team keeps each hand-over explicit. The system can help generate or review the artefacts, but the accountable role and approval decision remain organisational responsibilities.