mkdocs.yml

site_name: Agent Control Standard
site_url: !ENV GITHUB_PAGES_URL
site_description: >-
  An industry standard for building trustworthy AI agents - instrumentable, traceable and inspectable
   to enable enterprise-wide adoption with confidence.

# Repository
repo_name: GenAI-Security-Project/agent-control-standard
repo_url: https://github.com/GenAI-Security-Project/agent-control-standard
edit_uri: edit/main/docs/

# Copyright
copyright: Copyright &copy; 2025-2026 The OWASP GenAI Security Project and the ACS contributors. Documentation licensed under <a href="https://creativecommons.org/licenses/by-sa/4.0/">CC BY-SA 4.0</a>.

docs_dir: docs

theme:
  name: material
  custom_dir: overrides
  logo: assets/icon.svg
  features:
    - search.suggest
    # edit this page for each doc page
    - content.action.edit
    # enable synchronized tabs
    - content.tabs.link
  palette:
    # The media queries pick the reader's system preference on first load. The toggle
    # then overrides it, which is the same two-state behavior the landing page has.
    - media: "(prefers-color-scheme: light)"
      scheme: default
      toggle:
        icon: material/weather-night
        name: Switch to dark mode
    - media: "(prefers-color-scheme: dark)"
      scheme: slate
      toggle:
        icon: material/weather-sunny
        name: Switch to light mode
  font: false
  favicon: assets/icon.svg

plugins:
  - search

# Additional configuration
extra:
  social:
    - icon: /fontawesome/brands/github
      name: Join the discussion on GitHub
      link: https://github.com/GenAI-Security-Project/agent-control-standard/discussions

nav:
  # The landing page links into the docs, so the docs need the return path. The URL is
  # absolute rather than derived from site_url because site_url names the /docs/ subpath,
  # which cannot address its own parent. It survives the agentcontrolstandard.org
  # cutover, when the custom domain makes this URL redirect rather than break.
  - ACS home: https://genai-security-project.github.io/agent-control-standard/
  - Trustworthy Agents: README.md
  - ACS: acs.md
  - Topics:
    - Core concepts: topics/core_concepts.md
    - ACS in Action: topics/ACS_in_action_example.md
  - Concepts:
    - Overview: concepts/README.md
    - Agents: concepts/agents.md
    - Identity:
      - Overview: concepts/identity.md
      - Identity for Agents: identity/overview.md
      - Standards: identity/standards.md
    - Session Lifecycle: concepts/session-lifecycle.md
    - Intent: concepts/intent.md
    - Capability: concepts/capability.md
    - Skill: concepts/skill.md
    - Provenance: concepts/provenance.md
    - Trust Basis: concepts/trust.md
  - Specification:
    - Conformance Profiles: spec/conformance.md
    - Instrument:
      - Overview: spec/instrument/README.md
      - Supported Hooks: spec/instrument/hooks.md
      - ACS specification: spec/instrument/specification.md
      - Instrument MCP: spec/instrument/extend_mcp.md
      - Instrument A2A: spec/instrument/a2a/extend_a2a.md
    - Trace:
      - Overview: spec/trace/README.md
      - Supported Events: spec/trace/events.md
      - Trace with OpenTelemetry: spec/trace/extend_opentelemetry.md
      - Trace with OCSF: spec/trace/extend_ocsf.md
      - OCSF Implementation Examples: spec/trace/OCSF/implementation_examples.md
    - Inspect:
      - Overview: spec/inspect/README.md
      - AgBOM with CycloneDX: spec/inspect/extend_cyclonedx.md
      - AgBOM with SPDX: spec/inspect/extend_spdx.md
      - AgBOM with SWID: spec/inspect/extend_swid.md
  - About: about.md

extra_css:
  - stylesheets/extra.css

# Mermaid, served from this repository rather than fetched from a CDN.
#
# mkdocs-material's bundle lazily loads mermaid from https://unpkg.com/mermaid@11/
# whenever it meets a diagram, which puts third-party executable code in a visitor's
# browser on every page that has one. That defeats the premise of the third-party guard
# in tests/, and the version there is a range rather than a pin, so unpkg decides which
# 11.x a reader runs. Declaring the library here defines `window.mermaid` before the
# theme checks for it, and the theme's own guard clause then skips the fetch.
#
# Pinned at 11.17.2. The byte-for-byte digest is asserted by tests/test_site_config.py,
# so a silent swap fails the build rather than shipping.
extra_javascript:
  - assets/javascripts/mermaid.min.js
  - assets/javascripts/mermaid-init.js

markdown_extensions:
  # Emojis
  - attr_list
  - pymdownx.emoji:
      emoji_index: !!python/name:material.extensions.emoji.twemoji
      emoji_generator: !!python/name:material.extensions.emoji.to_svg
  # Syntax Highlighting
  - pymdownx.highlight:
      anchor_linenums: true
      line_spans: __span
      pygments_lang_class: true
  - pymdownx.inlinehilite
  - pymdownx.snippets
  - pymdownx.superfences:
      custom_fences:
        # The class is deliberately NOT `mermaid`. mkdocs-material scans for that
        # class, and finding it does two unwanted things: it fetches the mermaid
        # library from https://unpkg.com at runtime, and its own rendering pass empties
        # the block before drawing anything, which is why the one diagram already in
        # this documentation has never rendered on the published site. Naming the class
        # something the theme does not recognise leaves both to
        # assets/javascripts/mermaid-init.js, which renders from the copy of the library
        # this repository serves. Authors still write ```mermaid fences.
        - name: mermaid
          class: acs-diagram
          format: !!python/name:pymdownx.superfences.fence_code_format
  # Callouts
  - admonition
  - pymdownx.details
  # Tabs
  - pymdownx.tabbed:
      alternate_style: true