On this page
§4.1
Metadata
§4.1.1 Specification-level metadata
Each specification MUST have a trail.toml file in its specification directory containing:
name = "KACS"
description = "Kernel Access Control Subsystem — tokens, security descriptors, access checks, and integrity controls."
name: The short display name of the specification. MUST match the name component of the directory (case may differ).description: A one-line description of what the specification covers.
No other fields are required at the specification level.
§4.1.2 Version-level metadata
Each version MUST have a trail.toml file in its version directory containing:
status = "draft"
date = "2026-04-24"
status: The lifecycle state. See §3.2 for valid values and transition rules.date: The date of the most recent change to this version, inYYYY-MM-DDformat.
No other fields are required at the version level.
§4.1.3 File-level metadata
Every markdown file within a specification MUST have YAML frontmatter containing at minimum:
---
title: Page Title
---
The title field is the display name of the section. No other frontmatter fields are required.
ⓘ Informative
Trail uses the
title field for navigation, page headers, and search indexing. The title does not need to match the filename -- 2-acls.md may have title: Access Control Lists.
Peios Learn
Built with Trail