Files
command-center/omp-docs/decisions/index.md
T
Frank 671222b881 docs(60): point-of-use corrections from the 2026-10-20 review
Measured fixes, one line each, from the review of everything that landed on
2026-10-20 (issue #60). Each page keeps its own facts; nothing was moved.

- inventory/index, index: the census blurb says what the page actually covers
  (tracked-vs-box-only per file), not "all userspace configuration"
- dotfiles-deploy: the wallpaper re-fetch recipe resolves the CDN URL through
  the wallhaven API — /w/<id> answers text/html, so curl -L never yields a
  JPEG; description widened to the whole page, tools/index blurb matched
- okf-maintenance: the link example and the mistake bullet now agree with
  okf-spec, which RECOMMENDS absolute bundle paths (they said the opposite)
- decisions/index: the unlisted-page gate is kb-coverage.py, not kb-lint
- AGENTS.md: the three skill-config subsections are pointers again; the pages
  own issue tracker, labels and domain docs
- swayidle-lock.service: Description names what the unit does (arms the idle
  lock over noctalia-shell IPC); suspend belongs to noctalia's inhibitor
- common.pkgs: git-lfs re-justified by the tracked .gitattributes filter
  contract; the swayidle comment drops its lid-policy claim
2026-10-21 00:54:06 -07:00

1.2 KiB

Architecture decision records

Decisions this repo has made and will not silently revisit. One file per decision, named NNN-<slug>.md, listed here — an unlisted page fails scripts/kb-coverage.py and does not exist as far as any agent is concerned.

No ADRs yet. The first one lands the moment a decision stops being reversible.

Format

Same shape as the dank/dankvoice decision records, which read well under time pressure:

  • # <Decision as a claim> (YYYY-MM-DD) — a title you can disagree with.
  • Root — the situation and the evidence that forced the question, with measured output rather than recollection where measurement exists.
  • Decision — what was chosen, and the rule an agent must follow because of it.
  • Rejected — the alternatives and the specific reason each was turned down, so nobody spends an afternoon rediscovering them.
  • Verification — what was run to prove the decision holds, and where that proof lives.

Frontmatter is required like any other page in this bundle (type: decision), and an ADR that a code change has superseded gets an amendment section appended rather than a rewrite: the point of the record is that the reasoning is still readable.