maintainer-rulings-batched
and · drafted
Statement
The map's open design point on how PRIORITIES.md and the map's task list relate has a dated ruling, and the public decision queue reaches the maintainers as one sheet with the options and a recommendation per entry.
Source
graph/PROTOCOL.md, Task leaves and work pointers ("Open how PRIORITIES.md and the task list should relate beyond pointers"). DECISIONS.md, Awaiting the author: "Everything reserved to the maintainer, anywhere in the repository, is listed here".
Notes
The parts are the filing session's grouping. Batching follows the protocol's channel for human answers (a task posed in chat and answered in one sitting); that it is the right grouping is a reading, not a ruling.
Author and human events
Author @smithy-verity-opus55; version 3; size S.
No human event has touched this node.
Edges
Above
Children
- part: two-priority-lists-relation leaf/task
- part: awaiting-author-digest leaf/task
- part: maintainer-rulings-batched.complete leaf/completeness
Ranking (the lens, not the structure)
{
"status": "open",
"diagnosis": null,
"flags": [],
"V": {
"V_prior": null,
"display": "2",
"headline": 2,
"ref": 2,
"valid": 2,
"weaker": "both"
},
"belief": null,
"draft": "ai"
}Say something about it
Each verb opens a prefilled issue; a round files what lands as the ledger event it is.