housecast
docs
Write the roster. The bundle and the board both derive.
housecast reads roles, personalities, and boundaries authored as YAML, resolves each role's personality meld and boundary allocation, derives the identity primitives, and emits an immutable bundle. The challenge board that grades the result derives from the same file, so every role change moves what gets tested.
These pages are early. Several carry a settled structure and an explicit list of what has not been written yet, and they are mounted verbatim from the repository rather than rewritten for the web.
If you are still deciding whether any of that is your problem, the case for housecast is the better place to start. These pages assume you already decided.
Synced from housecast 0924296, 2026-09-26. A copy, so the repository is the source of truth if the two disagree.
Getting started
The engine
Evaluation
- Grading The human half, and why it ships in an extra.
- Grading surfaces One set of rules across a terminal and a browser.
- Grading evidence The public and private halves of a single run.
- The deck housecast grade deck ROUNDS --run RUNDIR --out DECK builds
- The grading page housecast/grade/page/index.html renders a committed run and
- The grading page, payloads and delivery How grading-page.md gets data, and the test proving it needs
- The grading page palette Where the colour and type come from, and where they deviate
- The grading page, colour and type How grading-page.md treats evidence, verdicts, and scale
- Presenting housecast grade present serves a built deck to a room, taking
- Publishing to PyPI How a housecast-v tag becomes a release
- Non-scores A cell that is decided and is not a verdict, in three reasons
- CI How .forgejo/workflows/ci.yml gates main and pull requests
- MCP loop tasks What a task file under housecast/mcpeval/tasks/ is, and what
- The live room housecast room serve --subjects subjects.json --log
- The room's pages The three pages room.md serves from housecast/room/page/