Spec changelog

lagom.md spec evolution

Monthly updates to the lagom.md document specification — the structured, AI-native knowledge primitive. This changelog tracks how the spec itself evolves: new element types, schema changes, governance rules, and format conventions. For platform features (rendering, UI, integrations), see the Lagom platform release notes.

Spec vs. Platform: This changelog covers the .lagom.md format definition — the primitive. Changes to the Lagom knowledge management platform (processors, renderers, dashboards, agent integrations) ship separately and are tracked in the platform release notes.
Monthly release

May 2026 v1.1.0

Released May 4, 2026
  • Added
    lagom.decision element type — Structured decision records with options, rationale, status (proposed/accepted/superseded), and date fields. Enables agents to surface past decisions and their reasoning.
  • Added
    lagom.evidence element type — Links decisions and policies to supporting evidence with sourceType, confidence (low/medium/high), and author metadata. Enables trust-weighted retrieval.
  • Added
    lagom.system_reference element type — Declares external system dependencies with connector binding, type (saas/internal/api), and url. Allows agents to resolve which systems a process touches.
  • Added
    lagom.data_reference element type — Declares data sources for workflows with system, query, and schedule fields. Enables automated data pull actions in agent workflows.
  • Changed
    lagom.agent_action gains inputMap field — Agent actions now declare explicit variable-to-parameter mappings via inputMap, making tool bindings deterministic and auditable rather than relying on implicit context injection.
  • Changed
    Governance metadata adds reviewCadence — Frontmatter now supports reviewCadence (monthly/quarterly/annually) as a structured alternative to staleAfterDays. Both remain valid; processors derive staleness from whichever is present.
Monthly release

April 2026 v1.0.0

Released April 1, 2026
  • Added
    Initial spec release — The lagom.md specification v1.0.0, forked from Microsoft Chartifact and extended for operational knowledge documents.
  • Added
    Core document types — sop, policy, playbook, workflow, prompt, and knowledge-base as first-class documentType values in frontmatter.
  • Added
    Element types: lagom.step, lagom.checklist, lagom.policy_rule, lagom.approval_gate, lagom.agent_action — Fenced code blocks with lagom.* language tags define structured elements within Markdown body content.
  • Added
    Governance metadata — Frontmatter fields for owner, status (draft/active/deprecated/archived), lastVerified, staleAfterDays, and reviewer enable freshness tracking and compliance.
  • Added
    Dual-format support — Documents can be authored as .lagom.md (Markdown with YAML frontmatter + fenced blocks) or .lagom.json (direct JSON schema). Both are equivalent and interconvertible.
  • Added
    Variable system — Template expressions like {{client.name}} in element fields enable runtime resolution from context. Variables are declared implicitly by usage and resolved at processing time.
  • Added
    JSON Schema published — Canonical schema at lagom.md/schema/v1/idoc_v1.json for validation tooling, IDE autocomplete, and CI enforcement.
Future releases will appear here monthly