1.3 KiB
1.3 KiB
description
| description |
|---|
| Decide whether a catalog item is a leaf worth building, or a trunk that waits |
Evaluate $ARGUMENTS against the leaf/trunk test in docs/exploration.md.
Research it only as far as needed to answer accurately — what it actually requires, not what its homepage claims. If it is a protocol or spec, state which parts are mandatory versus optional.
Answer these, briefly:
- Leaf or trunk? Per
architecture.mdinvariant 7. - Reduces to: which primitive, concretely, with the shape of the implementation in two lines.
- Prerequisites: which arc or primitive must exist first. Is that gate open today?
- Cost: estimated LOC, new dependencies, new disk fields, ongoing maintenance burden, and anything it makes permanent (URLs, identifiers, published data).
- Sovereignty test: apply the one in
roadmap.mdGovernors. - Fit: does it serve fiction, webcomics, essays, Bengali-language work, or the low-bandwidth ethos — or is it interesting for its own sake? Interesting-for-its-own-sake is a legitimate answer for a cheap leaf and a disqualifying one for anything expensive.
- Verdict: build now / build when gate X opens / trunk, needs an ADR / no.
Write the verdict as one row in the Verdicts table in docs/exploration.md. Do not implement
anything in this pass.