Proposed — not in force yet — an open question, so citing it as settled is what the reference report catches.
4 of 121 decisions. Back to the full index.
| # | Title | Summary | Status |
|---|---|---|---|
| ADR-118 | A temporary code nothing here mints is its own finding | foreign-temp-codes reports a temporary code cited in this tree that no document in it mints — the branch-side guard, where concretize --check guards the trunk and legacy-spellings reports the aftermath. The rows are partitioned out of unresolved-codes rather than added to it, so each code is counted once under the reading that carries its remedy. Rejected: a directive of its own, since an illustrative code is unresolved for the ordinary reason and unresolved-ok: already covers it; and comparing against origin/main, which needs a network in the lint path and still misses an unmerged branch. | Proposed |
| ADR-119 | luria ack: the code comes from the scan, the reason from a person | luria ack writes an acknowledgement directive at every unacknowledged citing site the scan reports, with the code, the directive name and the location read from Scan and only the reason supplied by a person. It refuses over a document in force, a code nothing cites, and a citation already covered. Rejected: a --fix that writes them in bulk, since a generated reason vouches for nothing; putting it in luria repair, whose contract a judgement cannot satisfy; and an interactive prompt, which no CI or agent caller can answer. | Proposed |
| ADR-120 | Unbound relations reach the lint, so an invariant can be declared over a residue | unbound-relations and unbound-lines are lint classes, so lint.baseline can hold a declared invariant to a residue a project has read and accepted. This removes the all-or-nothing adoption cost without giving any individual row a third reading — ADR-049’s two-readings rule is untouched. Rejected: an unbound-ok: directive, which would retire a row and is the move ADR-049 refused; and closing the issue, which leaves the cost standing. | Proposed |
| ADR-121 | The site delegates frontmatter to Quartz: luria composes it, the note-properties plugin renders it | Quartz 5 parses frontmatter only in its note-properties plugin, and ADR-101’s config left it out — so every published page was untitled (blank search results, graph nodes labelled with paths) and its YAML rendered as a paragraph above the page. The plugin is now configured, and the record table luria drew into each body to make up for frontmatter rendering as nothing is gone: luria composes the staged frontmatter — Quartz’s own keys, a title carrying the code, the record’s facts as labelled properties with root-relative wikilinks — and Quartz renders it. | Proposed |