index

Rebuild a collection’s index.md — the generated leaf that lists its blueprints so a human or an agent can navigate without scraping the tree.

What it does

Reads the framework’s declared collections, walks each one’s single level of sub-folders, and rewrites each index.md wholesale: one markdown link per blueprint with its one-line summary, grouped by sub-folder or flat.

specs/index.md

# specs

<!-- index: specs (regenerated) -->

## playback
- [Watch a Video](playback/watch-a-video.md) — play a video reliably, signed in or not.
- [Resume Playback](playback/resume-playback.md) — returns a viewer to the exact second they stopped.

It regenerates, it doesn't author

Each line is the blueprint’s summary, verbatim. A blueprint with none is flagged, never invented — an index that quietly writes a plausible one-liner for you is an index you can no longer trust.

When to run it

After blueprints are added, renamed, moved, or removed.

Nothing depends on it being current: a stale index is a nuisance, not a failure. It annotates rather than gates, like everything derived in Eidos.

How it runs

It ships a build-index.py that does the whole walk deterministically where a shell is available, and falls back to doing it by hand on a sandboxed host. Either way the output is the same.

Note

There’s nothing hand-written in an index.md to preserve. Anything you type into one is lost on the next run — which is the test for whether something belongs in a generated leaf at all.

Related

• Generated Leaves — this and the canvas, together.