Skip to content
LQ.AI

Recorded design decisions

  • contributor
  • evaluator
  • agent

Every architecture decision record in docs/adr/, with the status each file carries today. The table below is read from the directory at build time, not hand-maintained, so it can’t fall behind whatever files actually exist there.

An accepted record describes an agreed direction — not necessarily what’s built yet. Read a decision alongside the actual code and tests to see which parts of it are available now; “Accepted” means the project has committed to that direction, not that every part of it has shipped.

A status can lag behind the code, and this index doesn’t correct for that. The Status column is rendered exactly as the file states it, including a record that still reads “Proposed” on a decision everyone already treats as settled, or that mentions work as deferred after the deferred part has since landed. When the status word and what you observe in the running system disagree, the code is the more current answer; a stale status is worth fixing in the ADR file itself, not worked around here.

The Citation Ledger & fiduciary-grade output

ADR 0018 Status Accepted

Note
(2026-06-24) — maintainer-accepted; Phase 1 implementation PRs (P1-A1+) carry security review per CODEOWNERS (new content store derived from egress; citation/audit surface)

Transparent validity/treatment layer (WS-G)

ADR 0019 Status Accepted

Note
(2026-06-26) — maintainer-accepted. Implementation PRs (WS-G PR1+) carry security review per CODEOWNERS (new gateway egress operation; citation/audit surface).

Content-source registry & free-source expansion (WS-E)

ADR 0021 Status Accepted

Note
(2026-06-29) — maintainer-accepted (PR #241; the four design forks settled with the maintainer 2026-06-29). Implementation PRs (WS-E PR1+) carry security review per CODEOWNERS (the gateway/** egress boundary, the api/app/autonomous/** governance chokepoint, and a new external-egress surface).

Definition of 1.0

ADR 0029 Status Accepted

Note
(2026-10-04) — committee-ratified at the weekly call (drafted

Tabular bulk operations (redline report + column memo)

ADR 0040 Status Accepted

Note
(2026-10-04) — approved at the committee meeting with the maintainer’s review amendments. Hou Fu confirmed the approval and inclusion of those amendments on 2026-10-10. Implementation acceptance and security review remain separate from this architectural approval.

Community skill catalog served from the local submodule

ADR 0041 Status Proposed

Note
(2026-07-25) — authored in-PR with roadmap item 3.8 (DE-263, community skill installer admin UI); reviewable at PR time. New admin endpoints carry security review per the auth-touching-surface rule in CLAUDE.md / CODEOWNERS.

Each row links the ADR file at the commit this page was checked against, so the status you read here is the status that file carried at that commit. Statuses are rendered exactly as the file states them — an ADR that says “Proposed” is listed as Proposed even where the decision is being followed, because the file is the record.

Next

Section titled “Next”