Conventions

Put shared documents in the initiative

Use foundry/initiatives/<slug>/ beneath your configured publication root. Name story files with their ID and subject, such as stories/1-1-account-export.md. A story title such as Story 1.1: Account export ties the file to its ID. Include the story, context, and acceptance criteria.

Use the board for status

Use e11 board show to read state and e11 board set <story> <status> to change state. Treat the board as the current status source. A story’s authored status line does not replace the board.

Find help and customization

The generated help catalog lives at .foundry/_config/e11-help.csv. Invoke e11-help to route a question. Persona and menu fields use TOML in customize.toml. Override those fields under .foundry/custom/.

Write for the reader

Start with the task and expected result. Address your reader as you. Pair each story ID and menu code with its name on first use. Show complete commands and concrete paths. Keep internal storage details in the run-store reference.

Cite platform decisions

Use the exact Cite as: path returned by e11-knowledge. Record source paths for repository decisions. Separate observed behavior from assumptions and proposed changes.

Files a checkout carries covers ownership and commit rules.