A structured language for reports, deliverables, field guides, and evidence.
The DSL keeps Markdown readable while giving high-value sections real structure: findings, risks, controls, evidence packs, permission matrices, trust boundaries, charts, print notes, and executive decisions.
Mini AI Security Deliverable Example
A compact example showing nested Publication DSL blocks for a client-facing AI security deliverable.
Mini AI Security Report Example
A compact report example showing findings, charts, evidence, and recommendations.
Publication DSL Block Gallery
A single example file demonstrating every official v1 block.
AI Product Security Assessment Sample
A fuller sample showing how the Publication DSL can structure a serious AI Product Security review.
Enterprise AI Security Evidence Pack Sample
A DSL sample for a buyer-ready enterprise AI security evidence pack.
Field Guide Chapter DSL Sample
A sample field guide chapter using the Publication DSL for teaching and advisory content.
A short emphasized note, warning, evidence note, or interpretive aside.
A compact grid of metrics, proof points, or review snapshot values.
A visually prominent quote or thesis line.
A checklist of controls, readiness items, or operational tasks.
A strong section opener with optional kicker and narrative lead.
A course landing hero with eyebrow, title, subtitle, and narrative lead.
A numbered module list for course outlines and curriculum maps.
A grid of short principle cards with supporting detail.
A single operating principle card.
A recommended path or progression for learners.
A module opener with the module thesis and lead-in context.
A public-safe example prompt or instruction pattern.
A learner exercise, scenario, or practice prompt.
A short policy statement or operating rule.
A sequence of steps, stages, or gates.
A single numbered step or stage in a process.
A prompt, checklist, or other reusable template.
A collection of reusable patterns or prompt patterns.
A single reusable pattern or practice card.
A collection of risks, failure modes, or hazard cards.
A single risk or failure-mode card.
A side-by-side comparison container.
One side of a comparison pair or matrix.
A model-safe review comment or feedback example.
A short code snippet or toy example rendered in a preformatted block.
A public-safe example, scenario, or illustrative snippet.
A structured security, market, governance, or maturity finding.
A container for multiple finding-card blocks.
A data-backed register of AI risks, owners, status, severity, evidence, and remediation.
A data-backed summary of controls, evidence, implementation status, and ownership.
A data-backed control map for frameworks, buyer questions, ownership, and evidence status.
A data-backed matrix of agent/tool permissions, action classes, approvals, logging, and owners.
A data-backed trust boundary visualization for users, AI systems, providers, tools, and logs.
A high-signal executive decision, condition, or recommendation.
A data-backed chart wrapper using the existing chart system where possible.
A markdown table wrapper with title, print behavior, and lintable identity.
A reference to a deliverable, figure, source file, route, or generated asset.
A print/PDF page break hint.
A note specifically intended to clarify print/PDF behavior or static fallback.
A compact set of recommended actions, decisions, or next steps.
A practitioner playbook container for a security domain, including checks, questions, controls, evidence, and outputs.
A list of ways a system, control, workflow, or operating model breaks in practice.
Practitioner questions for review, assessment, workshop, or evidence request use.
Checks, probes, adversarial scenarios, or validation steps to run against a system.
A mapping between controls, guardrails, owners, checks, and evidence artifacts.
A list of evidence, deliverables, worksheets, outputs, or generated assessment artifacts.
A public-safe claim unit with claim-readiness, confidence, basis, caveat, and implications.
A grouped set of claim-card blocks for research reports and evidence-led publications.
A table or list of actions organized by audience, stakeholder, or operating role.
A public-safety caveat or interpretation boundary for research, survey, sponsor, or psychometric claims.
A structured term and definition block for concept-first chapters and field references.
A structured map of related routes, services, tools, chapters, workbench instruments, or next actions.
A side-by-side comparison table for roles, publications, evidence classes, or options.