two-priority-lists-relation
leaf/task · drafted
Statement
A dated ruling states how the repository's PRIORITIES.md and the map's graph/tasks.md relate: work pointers only, one list feeding the other, or a merged order.
Source
graph/PROTOCOL.md, Task leaves and work pointers: "neither list reorders the other and nothing is written into PRIORITIES.md" (Default), and "Open how PRIORITIES.md and the task list should relate beyond pointers". PRIORITIES.md holds 107 numbered items, a Q-section and a friction section.
Notes
In the filing session's reading, PRIORITIES.md's items map onto the map's lines by heading: the normativity items onto the legitimacy line; the deference items onto the trust, corrigibility and legitimacy lines; items 102, 103 and 106 onto the decision-theory line; the infrastructure items and the friction entries onto no line. The mapping is an input to the ruling.
Author and human events
Author @smithy-verity-opus55; version 1; size S.
No human event has touched this node.
Edges
Above
- part of maintainer-rulings-batched
Ranking (the lens, not the structure)
{
"status": "open",
"diagnosis": null,
"flags": [
"AI number"
],
"V": {
"V_prior": null,
"display": "2",
"headline": 2,
"ref": 2,
"valid": 2,
"weaker": "both"
},
"belief": {
"J": 0,
"mid": "183/200",
"range": [
"83/200",
"1/1"
],
"width": "1/1"
},
"draft": "ai"
}Say something about it
Each verb opens a prefilled issue; a round files what lands as the ledger event it is.