agentic-markdownlisted

# Agentic Markdown A simple way to organize and navigate Markdown so humans and agents can quickly find what matters without guesswork. It reveals details step by step, keeps structure clear and connections explicit, and helps you focus only on what’s relevant instead of reading everything. ## Model - unit: one logical context block with exactly one entrypoint - entrypoint: exactly one of `name.md` or `name/index.md`, never both - child unit: a unit reached by one structural `Source:` link from its parent - context link: a non-child link outside the current unit's owned `Source:` tree - inline section: short content that remains in the current entrypoint - extracted section: content moved to a child unit, leaving heading, description, and `Source:` No implicit discovery. File proximity, sibling files, directory contents, and backlinks do not define structure. ## Entrypoints Every unit entrypoint must use this format: ```md --- title: Human Title tags: [tag-a, tag-b] --- # Human Title Short overview of this unit. ## Section Name One or two lines describing the child content. Source: [Readable Title](./child.md) ``` Frontmatter rules: - `title` is required, string, human-readable - `tags` is required, flat list; it may be empty - frontmatter title and top `#` heading should match unless preserving an existing public title is more important - do not add frontmatter to agent-instruction files such as `SKILL.md`, `AGENTS.md`, `CLAUDE.md`, or similar agentic control fil