dossier

Audit an OKF knowledge base for integrity before it ships. Use to verify a generated/edited KB — checks OKF compliance, atomicity, link integrity, provenance/confidence, coverage gaps, and stale content. Produces a severity-ranked report; does not silently fix.

Generate a client's L2 "adoption readout" — the Ladder (DEC-0052's wedge). From a provisioned client's served OKF, run the deterministic 4-axis scorer over their process/workflow atoms, then narrate a sequenced Now/Next/Later transformation roadmap and emit it as a sovereign OKF `artifact` in the CLIENT's own repo. Use after a client is ingested + served (KNOWLEDGE-BRIEF generated) to produce the post-diagnostic readout that lands the wedge ("we'll take you to where we already are") and opens the Agency conversation. Human-curated authoring; reads the client's OWN OKF, never perturbs Dossier's KB.

Architect a world-class, ATOMIC information architecture for a Dossier docs site — turn a flat OKF knowledge base into a navigable, scannable, readable reading experience whose structure is DERIVED FROM THE KNOWLEDGE GRAPH, never hand-maintained. Use when a docs surface is hard to navigate (giant flat sidebars, no section overviews, no wayfinding, every page a dead end), when onboarding a new client's KB to the docs, or when asked to improve docs IA / navigation / readability.

Generate a tailored client landing instance — a typed LandingContent module — from a provisioned client's OKF repo and tenant manifest. Use after a client is ingested and served (KNOWLEDGE-BRIEF generated) to produce a client-specific marketing landing that re-frames Dossier's universal messaging in the client's own vocabulary, with a hero artifact that is a REAL atom from the client's repo. Human-curated authoring, not a hosted runtime.

Author or extract atomic, OKF-compliant concept documents that conform to Dossier's knowledge model. Use whenever turning raw/clean source content (or a topic) into knowledge-base concepts — processes, workflows, roles, decisions, systems, policies, artifacts, terms. Produces one well-formed markdown+YAML file per concept, with full provenance and typed relationships.

Wield the full power of GitHub-Flavored Markdown (GFM) and GitHub's rendering pipeline to design world-class documentation — alerts/admonitions, collapsible sections, tables, task lists, mermaid diagrams, math, footnotes, themed images, auto-anchors, and badges. Use whenever authoring a README, guide, or any markdown that renders on GitHub (and, with the noted caveats, on the Astro Starlight surface). The reference + procedure the documentation-engineer reaches for.

Run the ingestion sweep that pulls a new client's raw knowledge into Dossier — public website (Firecrawl), files (Unstructured), and Microsoft 365/SharePoint (Graph delta + Copilot connectors) — normalized to clean, provenance-stamped markdown ready for extraction. Use when onboarding a client or refreshing their sources.

Scaffold a vertical-specific knowledge-base template from Dossier's knowledge model. Use to stand up a reusable starting taxonomy for an industry/vertical (e.g., Digital Experience Agency) — seed concept stubs, vertical-specific types, and an index — so a new client in that vertical is a fast instantiation, not a from-scratch build.