Artifacts
Context-hydrated strategic work products.
Artifacts draw from the engagement graph: domains, gaps, decisions, value cases. They can stand alone as reference documents, support decisions, or compose into deliverables. Each section carries provenance.
Evidence-linked generation
Each artifact section populates from the engagement objects that informed it. An architecture blueprint knows which domains it covers, which decisions shaped it, and which gaps it addresses. The evidence linkage survives document handoff.
20 templates across 8 categories
Cross-framework and framework-specific templates: architecture blueprints, current state maps, value case registers, readiness scorecards. Templates are structured activations that pull from engagement evidence. The template defines the structure. The engagement provides the content.
Three ownership modes per section
AI draft: AI generates, strategist reviews. System hydrated: assembled deterministically from engagement objects. Strategist owned: the strategist authors directly. 'Generate All Sections' respects these boundaries.
Deliverable-to-artifact linkage
A deliverable may link to an artifact as evidence of completion. Not every deliverable has an artifact. Not every artifact is linked to a deliverable. The relationship is optional, not structural. Deliverables track commitment. Artifacts hold output.
Object chain
Artifacts draw from across the engagement graph: Domains (capability context), Domain States (maturity evidence), Gaps (computed distance), Decisions (rationale), and Value Cases (commercial justification). They are not terminal outputs at the end of a chain.