25 lines
1.3 KiB
Markdown
25 lines
1.3 KiB
Markdown
---
|
|
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:
|
|
|
|
1. **Leaf or trunk?** Per `architecture.md` invariant 7.
|
|
2. **Reduces to:** which primitive, concretely, with the shape of the implementation in two lines.
|
|
3. **Prerequisites:** which arc or primitive must exist first. Is that gate open today?
|
|
4. **Cost:** estimated LOC, new dependencies, new disk fields, ongoing maintenance burden,
|
|
and anything it makes permanent (URLs, identifiers, published data).
|
|
5. **Sovereignty test:** apply the one in `roadmap.md` Governors.
|
|
6. **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.
|
|
7. **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.
|