amanuensis

Unresolved

Hot spots

Where unresolved work and unread territory concentrate, as separate measures.

Branch  main Checked  ec5824bceb9c As of  2026-10-07 22:54:09 Stale: 0 with a survey obligation, 65 exempt, of 655 scoped files

Rows are ordered by open critical and high defects, then open medium and low, then the unread fraction.

Hot spots
SubsystemOpen critical + highOpen medium + lowAwaiting verificationUndiscriminatedWeakest evidence qualityUnread filesStale filesUnassessed seam sides
Knowledge tools and workflow API B-031400Code verified0/4300/0
Diff-aware materializer B-040200Code verified0/2400/0
Embedded research surveys and platform trials B-070100Code verified74/7900/0
Packaging, installer, validation, and product docs B-050100Code verified65/15600/0
MCP core, persistence, and lifecycle B-020100—0/1300/0
Survey methodology and agent contracts B-010000—0/3700/0
Report interface design and validation studies B-060000—0/2400/0
Activation evidence and release readiness B-080000—0/3300/0
Conspectus design lanes, their drivers and receipts B-090000—0/9000/0

§What each column measures

Open critical + high and Open medium + low are kept apart because severity is an ordinal ramp of consequence and adding the two ends of it together would let four readability defects outweigh one data-loss path.

Awaiting verification counts repairs recorded against a commit with no evidence yet that they hold. It is not progress and it is not an open defect; it is a claim nobody has checked.

Undiscriminated counts unresolved contradictions, open and unresolved-competition matrices, and concern reviews that recorded a competition. A contradiction between findings in two subsystems is counted in both, because it is undiscriminated territory in both.

Weakest evidence quality is the weakest rung any Confirmed defect review here rests on, not an average: the weakest link is what a reader should re-verify first.

Unread files and Stale files are counted over ledger rows that carry a survey obligation; generated, vendored, and irrelevant paths are outside the denominator.

Unassessed seam sides counts (seam, side) pairs over twice the seams this subsystem is party to: a seam assessed from one side only is half-known, and counting seams would report it as covered. Binding: per-party-proxy; no seam-bound disposition is recorded. An SC-% disposition says a party has assessed some seam concern, never that it assessed this seam.

No Access heat column is shown: no recorded access reaches a subsystem, and a column of zeros would read as a measurement that was taken.