Nishi Family › Compare › Code Quality Standards

Nishi Compare · capabilities, evidence and delivery

Code Quality Standards

Compare capabilities and delivery evidence. Source discovery, qualification, deployment and accepted outcomes are separate; an open contract names work still to verify.

The Aug-2026 metric canon -- ISO 25010 and ISO 5055, McCabe, Halstead and the Maintainability Index, Chidamber-Kemerer, Martin package metrics, SQALE, behavioural code analysis, mutation score, CWE and OWASP, fitness functions, connascence -- each MAPPED to NishiLang or DECLARED INAPPLICABLE, then measured full-population over 18,945 organs and 49,593 import edges. An honest position, not a score.

Overview

The purpose, declared position and evidence coverage of this domain. Source presence and completed acceptance are different measures.

Where we are. Measured 2026-08-20 over the full population. STRONG and proven: fully acyclic import graph (nontrivial SCCs 0 over 18945 nodes and 49593 edges), propagation cost 0.4 percent against published Linux 5-18 percent, cursor-sentinel lint 0 hits over 18681 sources, dead-code ratchet keyed on a SET OF NAMES so a rise names the function, magic-constant fixer whose neutrality is provable by byte-identical rebuild, mutation harness that rebuilds the SUBJECT not just the test, and a capability-loss diff that must name every lost run before any promotion. WEAK and equally proven: NO complexity instrument exists at all, base-class adoption is 338 of 3139 gate sources at 10.8 percent with 2801 hand-rolled and therefore unmeasured, the ISO 5055 scanner implements 5 of about 140 rules and scanned 4000 of 18802 organs so its 19144 candidates are a floor over a 21 percent prefix, there is no debt ratio and no hotspot instrument, and duplication is known as a LEVEL with no trend because a trend needs two censuses in time.

Where we need to go. Close the Maintainability factor of ISO 5055 that our own scanner filed as a gap and nobody built, then make every axis on this page a RATCHET rather than a census -- so the position is defended by mechanism instead of by a seat remembering to re-run it. The field's tools measure and report; the exceed we already hold is that ours REFUSE. Extend that shape to complexity and coupling rather than adding more dashboards.

The unit. 1 u = one measured axis shipped as organ plus gate plus published row, the pmdash and charsim calibration.

Latest recorded release

2026-09-05 · CQ12

NAS: after the cache-key bump /api/build nx_magic BUILT 56120 B sha 6c1fa169 (the stage now carries name_src x4); nx_contentdiff vs live 40039 B: 3 runs lost, every one named and superseded (the allocator-lib contention message swapped for its newer twin, the old propose note replaced by the name_src note, the NX-UNNAMED marker reworded to point at the table) against 80 gained; /api/promote accepted it inside its calibrated band without the loss flag, PROMOTED prev=1; nx_magic_gate 51 of 51 GREEN on the NAS through nx_job_run; nx_offc_install refreshed the runner twin

Release history and work log

Release entries describe recorded changes; they do not establish that every capability passed evaluation.

16 of 24 capability source symbols found|8 of them authored stronger-claims|8 open|coverage 666/1000|adoption 10 full / 6 partial

Evidence profile — what the gaps on this board actually are

Measured by nx_swcompare_evidence, read back by nx_evprofile_lib. Every figure is a count with its denominator — there is deliberately no score, no grade and no percentage anywhere in this band, because a stored scalar is a field a seat can edit and a counted partition is not.

proven able to fail counts the gates that have a RECORDED RED — nx_gate_bite mutated the gate subject, rebuilt it, watched the gate go red, and that record is inside the shared TTL. never bitten is its complement over the same denominator: those gates ran and were green, and nothing has ever shown them able to detect anything, so their green is a statement about this run and not about the gate. green at 0/0 is a separate and much weaker observation — the gate printed GREEN on a zero denominator, so its own tooth counter says it examined nothing. A gate can be green, non-zero, and still never bitten; that is the common case and it is now visible instead of implied.

partition: grounded + unsupported = 15 vs present 15 · named + unnamed + withheld = 9 vs open 9 · both reconcile

liar-kill conj=GPQN · all four conjuncts held

graded document: BUILDROOT tree, 20139 bytes · gates map: PRIMARY · stamped 32d 23h ago · STALE against the shared TTL of 604800s — this is evidence about a build nobody can vouch for now · source ../knowledge/status/evstamp_codequality.verdict

Gap class	What it is, and the work it names
STALE	This profile is older than the shared TTL, or its clock ran backwards. It is reported as unusable rather than as fresh, because being wrong in the direction of refusing is the safe direction.

This band reports the referee counts. The per-axis worklist rows — which axis is unsupported, which watch is ready to flip, which gap is unnamed — are printed by nx_swcompare_evidence codequality itself and are not carried on the stamp, so this page names the classes and the producer names the rows. That split is stated rather than hidden: a count without a worklist is not actionable, and this band is honest about which half of that it is.

Production map

Follow the dependencies, declared acceptance criteria and recorded priorities. Inspect source binding before treating a rank as executable work.

Ranking source binding: PLAN_MATRIX_BOUND_ONLY. Recorded priorities require current acceptance evidence and resource checks before execution.

Ranking matches the captured plan and matrix only. Latest execution outcome, research freshness, accepted delivery and investment return are unverified.

Recorded priority estimates

Order from nx_compare_rank (nx_dr_ocm: (deficit + cost-of-delay + option + enables) x sponsor x self-sufficiency x momentum / cost). FINISH rows are rungs whose symbol is present but whose organ is short of full adoption: listed before new work by this heuristic. Priority is not measured delivery cost or execution readiness. Stamp: # asof=1790081939 domain=codequality target_version=0.1 rungs=14 done=4 open=10 finish=1 ranker=nx_dr_ocm

#	Stage	Rung	Priority	Derivation
F	FINISH	Duplication trend not just level (CQ7) fg_trend dossier	REGISTERED-DARK	callable, authorised, completed MCP invocation not established by supplied journal window; lifetime history unknown (direct execution may be recorded elsewhere; this scan does not establish lifetime use); no execution surface runs it either (clock, cron, daemon, roster, actlog and surfaced forks checked)
#1	0.1	Halstead volume and a Maintainability Index (CQ2) cw_halstead dossier	933	v=7 m=2 c=15
#2	later	Whole-corpus ISO 5055 scan (CQ4) cw_uncapped dossier	1000	v=10 m=1 c=10
#3	later	Chidamber-Kemerer re-targeted to organ-as-class (CQ8) h_ck_suite dossier	933	v=7 m=2 c=15
#4	later	Complexity ratchet in the build door (CQ3) cw_ratchet dossier	600	v=3 m=2 c=10
#5	later	Technical debt ratio with a remediation cost model (CQ9) dbt_ratio dossier	333	v=5 m=1 c=15
#6	later	Hotspot instrument over action-grain history (CQ6) al_hotspot dossier	300	v=3 m=2 c=20
#7	later	Base-class adoption ratchet (CQ5) gl_ratchet dossier	200	v=2 m=1 c=10
#8	later	Connascence of meaning across organs (CQ10) h_connascence dossier	50	v=1 m=1 c=20
#9	later	Split the complexity distribution by generated versus authored (CQ1a) mc_generated dossier	0	v=0 m=2 c=10
#10	later	A numeric bound is DERIVED or EVIDENCED, never bare -- the estate-wide census and ratchet over every const that sizes a pool, cap, buffer, table or threshold (CQ13) bound_evidence_census dossier	0	v=0 m=2 c=30

Declared roadmap — contract, acceptance, executor, effort

Rung	Closes with	Definition of done (pre-declared)	Executor	Est.
Cyclomatic complexity per function (CQ1)	mc_scan_file	SHIPPED 2026-08-20, gate GREEN 17 of 17, seq251 CLOSED. Measured 103,733 functions: p50=3 p90=12 p99=43 max=2996, above the cited bar of 10 is 12,639. THE KEYSTONE, and it was our own filed gap seq251. Build v(G) = e - n + 2 over each NishiLang function's control-flow graph. ACCEPT RULE declared in advance: on a hand-built fixture of 6 functions with known v(G) covering straight-line, single if, if-else, while, nested if, and a multiway dispatch, the organ must return the hand-computed value for all 6, AND must reproduce the multiway-decision exemption behaviour by REPORTING the raw count rather than silently applying an exemption. A neg-control function whose v(G) the organ gets wrong must be shown to fail before the tooth is trusted	Organ	1.5 u
Split the complexity distribution by generated versus authored (CQ1a) after CQ1	mc_generated	The measured tail is dominated by GENERATED and TABLE code, so the 12,639 functions above the cited bar are an UPPER BOUND on AUTHORED complexity debt. COMPOSE the incumbent detector -- nx_unwired already carries uw_generated as a head-mark test -- and never write a second one. ACCEPT RULE declared in advance: FIRST measure and publish the MARKER'S ADOPTION across the corpus, because of the four worst files exactly one carries an uppercase GENERATED head-mark, one says Generated by in lowercase, one says AUTO_APPLIED and one is an unmarked hand-authored data table. If adoption is too low for the split to be honest, this rung ships the ADOPTION NUMBER plus an UNKNOWN bucket rather than a split that silently miscounts. A GENERATED-CODE SPLIT IS ONLY AS GOOD AS THE MARKER'S ADOPTION	Organ	1 u
Halstead volume and a Maintainability Index (CQ2) after CQ1	cw_halstead	Operators and operands are lexically separable in NishiLang so Halstead transfers. ACCEPT RULE: the organ must emit n1 n2 N1 N2 and V as SEPARATE fields and must NOT emit a single MI number without also emitting which variant it used -- there are at least three published formulas differing in the comment coefficient 2.4 versus 2.46 versus dropping the comment term entirely, so an unlabelled MI is a number nobody can reproduce. It must also refuse to average cyclomatic complexity across modules, which is the documented defect that makes MI hide its own outliers	Organ	1.5 u
Complexity ratchet in the build door (CQ3) after CQ1	cw_ratchet	Make CQ1 a REFUSAL not a report, in the shape nx_magicratchet already proved: self-baseline on first sight so it is non-breaking by construction, print the bar in every verdict so it is never an invisible threshold, and NAME every offending function. ACCEPT RULE: bite-proven both directions -- raising a function's complexity above its baseline must produce a REFUSE naming that function, and restoring it must produce ALLOW	Organ	1 u
Whole-corpus ISO 5055 scan (CQ4)	cw_uncapped	Remove the 4000-organ cap so the scanner covers all 18802 organs. ACCEPT RULE: the run must report truncated 0 and organs_scanned equal to organs_present, and the candidate total must be republished with the OLD 21-percent-prefix figure beside it so the correction is visible rather than silently swapped. Derive the buffer from the input, never raise a guessed cap	Organ	1 u
Base-class adoption ratchet (CQ5)	gl_ratchet	2801 of 3139 gate sources are hand-rolled and invisible to the exit-verdict and negative-control laws. ACCEPT RULE: the baseline is a SET OF NAMES not a count, so a regression names the gate and the file -- the lesson already paid for by nx_unwired on a shared tree where a count-only ratchet cannot say whose regression it is. Must not block: census and name, never refuse	Organ	1 u
Hotspot instrument over action-grain history (CQ6) after CQ1	al_hotspot	CodeScene needs commit history joined to an issue tracker; we have something FINER -- every tool call and refusal with its reasoning. ACCEPT RULE: this must be a new READER of the existing journal, never a new collector, and it must reproduce by measurement a hotspot set that a human agrees with on a period whose work is already recorded. It must publish its HORIZON next to every verdict, because a history-based instrument that does not state its window reads as completeness	Organ	2 u
Duplication trend not just level (CQ7)	fg_trend	One census is a level; a trend needs two in time. ACCEPT RULE: the organ must APPEND to a durable log on a beat and must refuse to emit a trend from a single sample, reporting UNOBSERVABLE instead -- an axis that cannot see must abstain rather than acquit. Field bar for context: block duplication up 81 percent and refactored lines down from 21 to 3.8 percent across 623 million AI-era changes	Organ	1 u
Chidamber-Kemerer re-targeted to organ-as-class (CQ8) after CQ1	h_ck_suite	WMC RFC and LCOM re-targeted to organ granularity; DIT and NOC stay DECLARED INAPPLICABLE and must be printed as such rather than as zero. ACCEPT RULE: each metric ships with its re-targeting stated in the output itself, so no reader can mistake an analogue for the original. A metric that cannot state its own mapping does not ship	Organ	1.5 u
Technical debt ratio with a remediation cost model (CQ9) after CQ4	dbt_ratio	A SQALE-style ratio needs a per-finding remediation cost and a cost-to-develop constant. ACCEPT RULE: the cost model lives in a CONF as data, never in code, and the ratio must never be published without the constant it divided by -- a rating derived from an unstated denominator is the invisible-bar defect this estate has already paid for once	Organ	1.5 u
Connascence of meaning across organs (CQ10) after CQ4	h_connascence	Our import graph sees connascence of NAME and nothing else. The measurable next form is connascence of MEANING: the same magic literal agreed upon in two organs with no shared binding. ACCEPT RULE: must find a planted cross-organ shared literal and must NOT fire on two independent uses of a structurally forced constant such as an argv index. False-positive rate measured on real data and driven to zero without losing the planted true positive	Organ	2 u
Emission provenance index (CQ11)	em_query	SHIPPED 2026-08-23, gate GREEN 9 of 9, both organs LIVE in nx_catalog. The question which function emits this text and which constant bounds this buffer, answered in ONE CALL over a composed-emission index of the whole corpus -- 148010 blocks, 1360 bound constants, 5176 reads, partition reconciled by the gate. ACCEPT RULE declared in advance and met as written: a positive control must name a real emitter by file line and function, a runtime-assembled fabricated literal must return zero sites and exit 1 so the gate cannot pass by indexing its own fixture, a bound query must name both the definition and a read site, and the blind spot for byte-code emissions must be printed in the stamp. Built only after nx_codewiki_ask, nx_capsearch, a full-corpus literal grep and nx_forkcensus were each asked and each missed	Organ	1 u

Milestones

Milestone	Rungs	Cumulative
Q0 · The Maintainability factor closes	CQ1,CQ2	3 u
Q1 · Every measured axis is a ratchet not a census	CQ3,CQ4,CQ5	5 u
Q2 · The estate sees its own quality trajectory	CQ6,CQ7	7 u

Rung	Closes with	Definition of done (pre-declared)	Executor	Est.
Purpose names for rule 11: a literal is named by VALUE AND CONTEXT from a table, never restated (CQ12) after CQ3	mg_name_lookup	nx_magic reads knowledge/magic_names.conf (value, context needle, name, why) and resolves every site once from the same context window map prints; consts dedupe by NAME so one value with two meanings becomes two consts; map, propose and apply all carry name_src=table or mechanical and the mechanical rows are the worklist; done-rule: nx_magic_gate GREEN with the first-row-wins, star-row, one-value-two-names, unlisted-value and absent-conf controls, and nx_magic propose on a real organ shows table names beside mechanical ones	Organ	1.5 u
A numeric bound is DERIVED or EVIDENCED, never bare -- the estate-wide census and ratchet over every const that sizes a pool, cap, buffer, table or threshold (CQ13) after CQ12	bound_evidence_census	DONE-RULE PRE-DECLARED 2026-09-05 (operator, same day: this needs estate-wide fixing from the first byte up -- numbers need evidence on why they are set or need to be dynamic, no guessing). The measured trigger is lang LN60: a compiler pool declared at 4096 with a comment asserting it could not be derived stopped a real build at 4097, the third such incident in one file, while the sibling pool beside it had been derived for months. Rule 11 and nx_magic already name and hoist LITERALS; this rung is the next axis -- for every hoisted const that feeds a sys_mmap size, an array bound, a loop cap, a chunk size, a retry count or a threshold, classify its PROVENANCE: DERIVED (the initialiser is an expression of another named quantity or a pass over the input), EVIDENCED (the adjacent comment names a measurement, a spec section, a published bar or a conf key), or BARE (a number with no witness). Done when: (1) the census organ walks every .nx in both trees, publishes the partition with sums on this page (counts are not a worklist -- it NAMES every BARE site file:line), and its own fixtures plant one of each class and bite; (2) BARE is a named-set ratchet like nx_unwired (a rise names the file and const), never a count-only threshold; (3) the three known-good classes each carry a positive control in the gate so a classifier that calls everything BARE cannot pass; (4) the /compare page renders DERIVED/EVIDENCED/BARE per domain so the number a domain plans against carries its own reason. Deliberately NOT a rewrite campaign: the ratchet drains BARE by evidence or derivation at each site as it is touched, and a cap that is genuinely unknowable is EVIDENCED by naming the one purpose it serves and making its exhaustion announce (CLAUDE.md, a buffer cap is not a number to tune)	Organ	3 u

Ladder verdict. NOT DECLARED. This board names no dated best-in-class or frontier target and no rung roles (sotatarget and rungrole rows on its plan); the ranker labels it NO-LADDER until it does, and until then its rungs climb toward a target nobody has written down. Bars read NO-BAR against the current month 2026-10.

Bar freshness, counted
Class	Count	Note
bars	0	sotabar rows on the plan
fresh	0	the bar month is the current month
attested	0	an older bar with a this-month barscan reporting no newer entry
stale	0	a this-month scan saw a newer month the bar ignores
unattested	0	nobody looked this month
malformed	0	a sotabar row missing a field
duplicate	0	bar ids an earlier row already carries
bars, summed	0	RECONCILED: the parts sum to the total 0
current month	2026-10	the month every bar is judged against

Treatment verdict. NOT DECLARED. No rung on this board declares its three-step treatment (a treat row naming the MCP row, the API route, the primitive it composes, the workflow that composes it and the agent beat that runs it); the ranker labels every rung TREATMENT-UNDECLARED until it does.

Inspect a rung and its prerequisites

Declared nodes 14. Rank input binding: PLAN_MATRIX_BOUND_ONLY. Dependency order is authored. Implementation, acceptance evidence, authority and resource readiness are unverified. No action is recommended or dispatched here.

Plan SHA-256 b7f1899377c4a54b5a3b8dc3681618ce973a50066318935a0dc1cedb6e17628d. Target rows 0; role rows 0. Existing risks and release worklog retain their own scope; no node completion is inferred.

Runtime observation coverage: 0 of 14 rungs have current, identity-bound execution observations. Observation may report RED. Accepted completion remains unknown; source presence, qualification and deployment do not establish it.

Use Enter or Space on a rung to inspect its contract. Prerequisite links locate another rung in this list; open its summary to inspect it. Estimates are authored effort, not forecasts.

CQ1 — Cyclomatic complexity per function
Prerequisites: None declared; this does not establish execution eligibility.
Contract: mc_scan_file
Acceptance: SHIPPED 2026-08-20, gate GREEN 17 of 17, seq251 CLOSED. Measured 103,733 functions: p50=3 p90=12 p99=43 max=2996, above the cited bar of 10 is 12,639. THE KEYSTONE, and it was our own filed gap seq251. Build v(G) = e - n + 2 over each NishiLang function's control-flow graph. ACCEPT RULE declared in advance: on a hand-built fixture of 6 functions with known v(G) covering straight-line, single if, if-else, while, nested if, and a multiway dispatch, the organ must return the hand-computed value for all 6, AND must reproduce the multiway-decision exemption behaviour by REPORTING the raw count rather than silently applying an exemption. A neg-control function whose v(G) the organ gets wrong must be shown to fail before the tooth is trusted
Authored effort: 1.5. Executor kind: Organ. Responsible, accountable and verifier not established. Inspect retained worklog.
Runtime observation: UNKNOWN; outcome UNKNOWN; observed epoch -1. Declared owner: . Receipt , SHA-256 . Identity-bound observation is not accepted completion. Qualification and deployment remain unverified by this projection.
CQ1a — Split the complexity distribution by generated versus authored
Prerequisites: CQ1 (acceptance unverified)
Contract: mc_generated
Acceptance: The measured tail is dominated by GENERATED and TABLE code, so the 12,639 functions above the cited bar are an UPPER BOUND on AUTHORED complexity debt. COMPOSE the incumbent detector -- nx_unwired already carries uw_generated as a head-mark test -- and never write a second one. ACCEPT RULE declared in advance: FIRST measure and publish the MARKER'S ADOPTION across the corpus, because of the four worst files exactly one carries an uppercase GENERATED head-mark, one says Generated by in lowercase, one says AUTO_APPLIED and one is an unmarked hand-authored data table. If adoption is too low for the split to be honest, this rung ships the ADOPTION NUMBER plus an UNKNOWN bucket rather than a split that silently miscounts. A GENERATED-CODE SPLIT IS ONLY AS GOOD AS THE MARKER'S ADOPTION
Authored effort: 1. Executor kind: Organ. Responsible, accountable and verifier not established. Inspect retained worklog.
Runtime observation: UNKNOWN; outcome UNKNOWN; observed epoch -1. Declared owner: . Receipt , SHA-256 . Identity-bound observation is not accepted completion. Qualification and deployment remain unverified by this projection.
CQ2 — Halstead volume and a Maintainability Index
Prerequisites: CQ1 (acceptance unverified)
Contract: cw_halstead
Acceptance: Operators and operands are lexically separable in NishiLang so Halstead transfers. ACCEPT RULE: the organ must emit n1 n2 N1 N2 and V as SEPARATE fields and must NOT emit a single MI number without also emitting which variant it used -- there are at least three published formulas differing in the comment coefficient 2.4 versus 2.46 versus dropping the comment term entirely, so an unlabelled MI is a number nobody can reproduce. It must also refuse to average cyclomatic complexity across modules, which is the documented defect that makes MI hide its own outliers
Authored effort: 1.5. Executor kind: Organ. Responsible, accountable and verifier not established. Inspect retained worklog.
Runtime observation: UNKNOWN; outcome UNKNOWN; observed epoch -1. Declared owner: . Receipt , SHA-256 . Identity-bound observation is not accepted completion. Qualification and deployment remain unverified by this projection.
CQ3 — Complexity ratchet in the build door
Prerequisites: CQ1 (acceptance unverified)
Contract: cw_ratchet
Acceptance: Make CQ1 a REFUSAL not a report, in the shape nx_magicratchet already proved: self-baseline on first sight so it is non-breaking by construction, print the bar in every verdict so it is never an invisible threshold, and NAME every offending function. ACCEPT RULE: bite-proven both directions -- raising a function's complexity above its baseline must produce a REFUSE naming that function, and restoring it must produce ALLOW
Authored effort: 1. Executor kind: Organ. Responsible, accountable and verifier not established. Inspect retained worklog.
Runtime observation: UNKNOWN; outcome UNKNOWN; observed epoch -1. Declared owner: . Receipt , SHA-256 . Identity-bound observation is not accepted completion. Qualification and deployment remain unverified by this projection.
CQ4 — Whole-corpus ISO 5055 scan
Prerequisites: None declared; this does not establish execution eligibility.
Contract: cw_uncapped
Acceptance: Remove the 4000-organ cap so the scanner covers all 18802 organs. ACCEPT RULE: the run must report truncated 0 and organs_scanned equal to organs_present, and the candidate total must be republished with the OLD 21-percent-prefix figure beside it so the correction is visible rather than silently swapped. Derive the buffer from the input, never raise a guessed cap
Authored effort: 1. Executor kind: Organ. Responsible, accountable and verifier not established. Inspect retained worklog.
Runtime observation: UNKNOWN; outcome UNKNOWN; observed epoch -1. Declared owner: . Receipt , SHA-256 . Identity-bound observation is not accepted completion. Qualification and deployment remain unverified by this projection.
CQ5 — Base-class adoption ratchet
Prerequisites: None declared; this does not establish execution eligibility.
Contract: gl_ratchet
Acceptance: 2801 of 3139 gate sources are hand-rolled and invisible to the exit-verdict and negative-control laws. ACCEPT RULE: the baseline is a SET OF NAMES not a count, so a regression names the gate and the file -- the lesson already paid for by nx_unwired on a shared tree where a count-only ratchet cannot say whose regression it is. Must not block: census and name, never refuse
Authored effort: 1. Executor kind: Organ. Responsible, accountable and verifier not established. Inspect retained worklog.
Runtime observation: UNKNOWN; outcome UNKNOWN; observed epoch -1. Declared owner: . Receipt , SHA-256 . Identity-bound observation is not accepted completion. Qualification and deployment remain unverified by this projection.
CQ6 — Hotspot instrument over action-grain history
Prerequisites: CQ1 (acceptance unverified)
Contract: al_hotspot
Acceptance: CodeScene needs commit history joined to an issue tracker; we have something FINER -- every tool call and refusal with its reasoning. ACCEPT RULE: this must be a new READER of the existing journal, never a new collector, and it must reproduce by measurement a hotspot set that a human agrees with on a period whose work is already recorded. It must publish its HORIZON next to every verdict, because a history-based instrument that does not state its window reads as completeness
Authored effort: 2. Executor kind: Organ. Responsible, accountable and verifier not established. Inspect retained worklog.
Runtime observation: UNKNOWN; outcome UNKNOWN; observed epoch -1. Declared owner: . Receipt , SHA-256 . Identity-bound observation is not accepted completion. Qualification and deployment remain unverified by this projection.
CQ7 — Duplication trend not just level
Prerequisites: None declared; this does not establish execution eligibility.
Contract: fg_trend
Acceptance: One census is a level; a trend needs two in time. ACCEPT RULE: the organ must APPEND to a durable log on a beat and must refuse to emit a trend from a single sample, reporting UNOBSERVABLE instead -- an axis that cannot see must abstain rather than acquit. Field bar for context: block duplication up 81 percent and refactored lines down from 21 to 3.8 percent across 623 million AI-era changes
Authored effort: 1. Executor kind: Organ. Responsible, accountable and verifier not established. Inspect retained worklog.
Runtime observation: UNKNOWN; outcome UNKNOWN; observed epoch -1. Declared owner: . Receipt , SHA-256 . Identity-bound observation is not accepted completion. Qualification and deployment remain unverified by this projection.
CQ8 — Chidamber-Kemerer re-targeted to organ-as-class
Prerequisites: CQ1 (acceptance unverified)
Contract: h_ck_suite
Acceptance: WMC RFC and LCOM re-targeted to organ granularity; DIT and NOC stay DECLARED INAPPLICABLE and must be printed as such rather than as zero. ACCEPT RULE: each metric ships with its re-targeting stated in the output itself, so no reader can mistake an analogue for the original. A metric that cannot state its own mapping does not ship
Authored effort: 1.5. Executor kind: Organ. Responsible, accountable and verifier not established. Inspect retained worklog.
Runtime observation: UNKNOWN; outcome UNKNOWN; observed epoch -1. Declared owner: . Receipt , SHA-256 . Identity-bound observation is not accepted completion. Qualification and deployment remain unverified by this projection.
CQ9 — Technical debt ratio with a remediation cost model
Prerequisites: CQ4 (acceptance unverified)
Contract: dbt_ratio
Acceptance: A SQALE-style ratio needs a per-finding remediation cost and a cost-to-develop constant. ACCEPT RULE: the cost model lives in a CONF as data, never in code, and the ratio must never be published without the constant it divided by -- a rating derived from an unstated denominator is the invisible-bar defect this estate has already paid for once
Authored effort: 1.5. Executor kind: Organ. Responsible, accountable and verifier not established. Inspect retained worklog.
Runtime observation: UNKNOWN; outcome UNKNOWN; observed epoch -1. Declared owner: . Receipt , SHA-256 . Identity-bound observation is not accepted completion. Qualification and deployment remain unverified by this projection.
CQ10 — Connascence of meaning across organs
Prerequisites: CQ4 (acceptance unverified)
Contract: h_connascence
Acceptance: Our import graph sees connascence of NAME and nothing else. The measurable next form is connascence of MEANING: the same magic literal agreed upon in two organs with no shared binding. ACCEPT RULE: must find a planted cross-organ shared literal and must NOT fire on two independent uses of a structurally forced constant such as an argv index. False-positive rate measured on real data and driven to zero without losing the planted true positive
Authored effort: 2. Executor kind: Organ. Responsible, accountable and verifier not established. Inspect retained worklog.
Runtime observation: UNKNOWN; outcome UNKNOWN; observed epoch -1. Declared owner: . Receipt , SHA-256 . Identity-bound observation is not accepted completion. Qualification and deployment remain unverified by this projection.
CQ11 — Emission provenance index
Prerequisites: None declared; this does not establish execution eligibility.
Contract: em_query
Acceptance: SHIPPED 2026-08-23, gate GREEN 9 of 9, both organs LIVE in nx_catalog. The question which function emits this text and which constant bounds this buffer, answered in ONE CALL over a composed-emission index of the whole corpus -- 148010 blocks, 1360 bound constants, 5176 reads, partition reconciled by the gate. ACCEPT RULE declared in advance and met as written: a positive control must name a real emitter by file line and function, a runtime-assembled fabricated literal must return zero sites and exit 1 so the gate cannot pass by indexing its own fixture, a bound query must name both the definition and a read site, and the blind spot for byte-code emissions must be printed in the stamp. Built only after nx_codewiki_ask, nx_capsearch, a full-corpus literal grep and nx_forkcensus were each asked and each missed
Authored effort: 1. Executor kind: Organ. Responsible, accountable and verifier not established. Inspect retained worklog.
Runtime observation: UNKNOWN; outcome UNKNOWN; observed epoch -1. Declared owner: . Receipt , SHA-256 . Identity-bound observation is not accepted completion. Qualification and deployment remain unverified by this projection.
CQ12 — Purpose names for rule 11: a literal is named by VALUE AND CONTEXT from a table, never restated
Prerequisites: CQ3 (acceptance unverified)
Contract: mg_name_lookup
Acceptance: nx_magic reads knowledge/magic_names.conf (value, context needle, name, why) and resolves every site once from the same context window map prints; consts dedupe by NAME so one value with two meanings becomes two consts; map, propose and apply all carry name_src=table or mechanical and the mechanical rows are the worklist; done-rule: nx_magic_gate GREEN with the first-row-wins, star-row, one-value-two-names, unlisted-value and absent-conf controls, and nx_magic propose on a real organ shows table names beside mechanical ones
Authored effort: 1.5. Executor kind: Organ. Responsible, accountable and verifier not established. Inspect retained worklog.
Runtime observation: UNKNOWN; outcome UNKNOWN; observed epoch -1. Declared owner: . Receipt , SHA-256 . Identity-bound observation is not accepted completion. Qualification and deployment remain unverified by this projection.
CQ13 — A numeric bound is DERIVED or EVIDENCED, never bare -- the estate-wide census and ratchet over every const that sizes a pool, cap, buffer, table or threshold
Prerequisites: CQ12 (acceptance unverified)
Contract: bound_evidence_census
Acceptance: DONE-RULE PRE-DECLARED 2026-09-05 (operator, same day: this needs estate-wide fixing from the first byte up -- numbers need evidence on why they are set or need to be dynamic, no guessing). The measured trigger is lang LN60: a compiler pool declared at 4096 with a comment asserting it could not be derived stopped a real build at 4097, the third such incident in one file, while the sibling pool beside it had been derived for months. Rule 11 and nx_magic already name and hoist LITERALS; this rung is the next axis -- for every hoisted const that feeds a sys_mmap size, an array bound, a loop cap, a chunk size, a retry count or a threshold, classify its PROVENANCE: DERIVED (the initialiser is an expression of another named quantity or a pass over the input), EVIDENCED (the adjacent comment names a measurement, a spec section, a published bar or a conf key), or BARE (a number with no witness). Done when: (1) the census organ walks every .nx in both trees, publishes the partition with sums on this page (counts are not a worklist -- it NAMES every BARE site file:line), and its own fixtures plant one of each class and bite; (2) BARE is a named-set ratchet like nx_unwired (a rise names the file and const), never a count-only threshold; (3) the three known-good classes each carry a positive control in the gate so a classifier that calls everything BARE cannot pass; (4) the /compare page renders DERIVED/EVIDENCED/BARE per domain so the number a domain plans against carries its own reason. Deliberately NOT a rewrite campaign: the ratchet drains BARE by evidence or derivation at each site as it is touched, and a cap that is genuinely unknowable is EVIDENCED by naming the one purpose it serves and making its exhaustion announce (CLAUDE.md, a buffer cap is not a number to tune)
Authored effort: 3. Executor kind: Organ. Responsible, accountable and verifier not established. Inspect retained worklog.
Runtime observation: UNKNOWN; outcome UNKNOWN; observed epoch -1. Declared owner: . Receipt , SHA-256 . Identity-bound observation is not accepted completion. Qualification and deployment remain unverified by this projection.

Learning and practice paths

No structured learning path is declared for this plan. Existing research, roadmap and worklog remain available above.

Rung dossiers — every record that bears on a rung, in one place

Joined by symbol, never typed. Each dossier is assembled on every publish from the rows this board already carries: the plan's rung row, the matrix row that carries its contract symbol (its status re-measured by the one symbol ruler), the gate the organ declares and the verdict the evidence referee recorded on its last run, the reference marks in the rung text, the design rows that name the rung and the work log filed against it. The capability matrix links each cell to its dossier and each dossier links back to its cell and forward to the rungs it stands on; a dependency naming no rung on this plan is written as UNRESOLVED rather than linked. Absences are named: NO-MATRIX-ROW, NO-GATE-DECLARED, UNRECORDED.

Gate verdicts: UNSTAMPED — no per-gate verdict artifact is published for this domain yet (nx_swcompare_evidence codequality writes it beside its stamp); every gate below reads UNRECORDED until it runs.

Gate declarations: knowledge/organ_gate.conf read from this working directory (1 rows) and from the estate root (196 rows); rows in both counted once: 0; declarations read: 197. Every declaration in either copy counts, so a stub beside the publisher can never hide the root.

CQ1 Cyclomatic complexity per function · cell PRESENT · gate NO-GATE-DECLARED

Contract	`mc_scan_file` · executor Organ · 1.5 u · stands on nothing
Definition of done	SHIPPED 2026-08-20, gate GREEN 17 of 17, seq251 CLOSED. Measured 103,733 functions: p50=3 p90=12 p99=43 max=2996, above the cited bar of 10 is 12,639. THE KEYSTONE, and it was our own filed gap seq251. Build v(G) = e - n + 2 over each NishiLang function's control-flow graph. ACCEPT RULE declared in advance: on a hand-built fixture of 6 functions with known v(G) covering straight-line, single if, if-else, while, nested if, and a multiway dispatch, the organ must return the hand-computed value for all 6, AND must reproduce the multiway-decision exemption behaviour by REPORTING the raw count rather than silently applying an exemption. A neg-control function whose v(G) the organ gets wrong must be shown to fail before the tooth is trusted
Matrix cell	Cyclomatic complexity per function (McCabe) · `runtime/nx_mccabe_lib.nx` · PRESENT decl
Gate	NO-GATE-DECLARED — `knowledge/organ_gate.conf` carries no row for `nx_mccabe_lib`; declare `nx_mccabe_lib TAB <gate>` and the ship loop proves it and the verdict lands here.
Work log	2026-09-05 retract CORRECTION FROM THE codeeffectiveness LANE 2026-09-05: this board's CQ1 rung and matrix row have read SHIPPED with the gate GREEN 17 of 17 since 2026-08-20, while nx_catalog on the serving tree read nx_mccabe and nx_mccabe_gate SOURCE-ONLY the whole time -- the claim was true of a laptop build and unbacked on the surface that runs. Closed on the serving tree today: nx_mccabe BUILT through /api/build (36760 B sha e2526b1a, src_path confirmed), PROMOTED prev=1, REGISTERED, _offc twin installed, and re-measured full population (19467 files, 112258 funcs, above-10 14247 = 126 permille, p50=3 p90=13 p99=46, partition sums exactly). nx_mccabe_gate build is QUEUED as BQ-nx_mccabe_gate behind the I/O storm, so the gate-GREEN half of the claim stays UNBACKED on the NAS until it fires. This is the motivating case for codeeffectiveness rung CE4: bind every SHIPPED claim to a live catalog or gate verdict rather than prose. 2026-09-05 land CORRECTION CLOSED (2026-09-05, codeeffectiveness lane): nx_mccabe_gate is now BUILT, PROMOTED and REGISTERED on the serving tree and returns GREEN 17 of 17 against the promoted nx_mccabe, so the SHIPPED-with-gate-GREEN claim this rung has carried since 2026-08-20 is finally true where it runs. Fresh full-population census the same day: 19467 files, 112258 functions, above-10 14247 = 126 permille, p50 3 p90 13 p99 46 max 2996, partition sums; against the 2026-08-20 figures (103733 functions, 121 permille, p90 12, p99 43) complexity is RISING on every percentile.

CQ1a Split the complexity distribution by generated versus authored · cell NO-MATRIX-ROW · gate NO-MATRIX-ROW

Contract	`mc_generated` · executor Organ · 1 u · stands on CQ1
Definition of done	The measured tail is dominated by GENERATED and TABLE code, so the 12,639 functions above the cited bar are an UPPER BOUND on AUTHORED complexity debt. COMPOSE the incumbent detector -- nx_unwired already carries uw_generated as a head-mark test -- and never write a second one. ACCEPT RULE declared in advance: FIRST measure and publish the MARKER'S ADOPTION across the corpus, because of the four worst files exactly one carries an uppercase GENERATED head-mark, one says Generated by in lowercase, one says AUTO_APPLIED and one is an unmarked hand-authored data table. If adoption is too low for the split to be honest, this rung ships the ADOPTION NUMBER plus an UNKNOWN bucket rather than a split that silently miscounts. A GENERATED-CODE SPLIT IS ONLY AS GOOD AS THE MARKER'S ADOPTION
Matrix cell	NO-MATRIX-ROW — no matrix row carries `mc_generated`; the ranker reads this rung as unmapped and no cell can flip for it. Add the row and the join completes on the next publish.
Gate	the gate join needs a matrix row: no organ is named for this rung
Work log	no log row names this rung yet

CQ2 Halstead volume and a Maintainability Index · cell WATCHING · gate NO-GATE-DECLARED

Contract	`cw_halstead` · executor Organ · 1.5 u · stands on CQ1
Definition of done	Operators and operands are lexically separable in NishiLang so Halstead transfers. ACCEPT RULE: the organ must emit n1 n2 N1 N2 and V as SEPARATE fields and must NOT emit a single MI number without also emitting which variant it used -- there are at least three published formulas differing in the comment coefficient 2.4 versus 2.46 versus dropping the comment term entirely, so an unlabelled MI is a number nobody can reproduce. It must also refuse to average cyclomatic complexity across modules, which is the documented defect that makes MI hide its own outliers
Matrix cell	Halstead volume and Maintainability Index · `runtime/_hdl_build/nx_cwe_scan.nx` · WATCHING decl
Gate	NO-GATE-DECLARED — `knowledge/organ_gate.conf` carries no row for `nx_cwe_scan`; declare `nx_cwe_scan TAB <gate>` and the ship loop proves it and the verdict lands here.
Work log	no log row names this rung yet

CQ3 Complexity ratchet in the build door · cell WATCHING · gate NO-GATE-DECLARED

Contract	`cw_ratchet` · executor Organ · 1 u · stands on CQ1
Definition of done	Make CQ1 a REFUSAL not a report, in the shape nx_magicratchet already proved: self-baseline on first sight so it is non-breaking by construction, print the bar in every verdict so it is never an invisible threshold, and NAME every offending function. ACCEPT RULE: bite-proven both directions -- raising a function's complexity above its baseline must produce a REFUSE naming that function, and restoring it must produce ALLOW
Matrix cell	Complexity ratchet that can REFUSE a build · `runtime/_hdl_build/nx_magic.nx` · WATCHING decl
Gate	NO-GATE-DECLARED — `knowledge/organ_gate.conf` carries no row for `nx_magic`; declare `nx_magic TAB <gate>` and the ship loop proves it and the verdict lands here.
Work log	no log row names this rung yet

CQ4 Whole-corpus ISO 5055 scan · cell WATCHING · gate NO-GATE-DECLARED

Contract	`cw_uncapped` · executor Organ · 1 u · stands on nothing
Definition of done	Remove the 4000-organ cap so the scanner covers all 18802 organs. ACCEPT RULE: the run must report truncated 0 and organs_scanned equal to organs_present, and the candidate total must be republished with the OLD 21-percent-prefix figure beside it so the correction is visible rather than silently swapped. Derive the buffer from the input, never raise a guessed cap
Matrix cell	Whole-corpus ISO 5055 coverage without a scan cap · `runtime/_hdl_build/nx_cwe_scan.nx` · WATCHING decl
Gate	NO-GATE-DECLARED — `knowledge/organ_gate.conf` carries no row for `nx_cwe_scan`; declare `nx_cwe_scan TAB <gate>` and the ship loop proves it and the verdict lands here.
Work log	no log row names this rung yet

CQ5 Base-class adoption ratchet · cell WATCHING · gate NO-GATE-DECLARED

Contract	`gl_ratchet` · executor Organ · 1 u · stands on nothing
Definition of done	2801 of 3139 gate sources are hand-rolled and invisible to the exit-verdict and negative-control laws. ACCEPT RULE: the baseline is a SET OF NAMES not a count, so a regression names the gate and the file -- the lesson already paid for by nx_unwired on a shared tree where a count-only ratchet cannot say whose regression it is. Must not block: census and name, never refuse
Matrix cell	Base-class adoption ratchet keyed on a name set · `runtime/nx_gatelaw_gate.nx` · WATCHING decl
Gate	NO-GATE-DECLARED — `knowledge/organ_gate.conf` carries no row for `nx_gatelaw_gate`; declare `nx_gatelaw_gate TAB <gate>` and the ship loop proves it and the verdict lands here.
Work log	no log row names this rung yet

CQ6 Hotspot instrument over action-grain history · cell WATCHING · gate NO-GATE-DECLARED

Contract	`al_hotspot` · executor Organ · 2 u · stands on CQ1
Definition of done	CodeScene needs commit history joined to an issue tracker; we have something FINER -- every tool call and refusal with its reasoning. ACCEPT RULE: this must be a new READER of the existing journal, never a new collector, and it must reproduce by measurement a hotspot set that a human agrees with on a period whose work is already recorded. It must publish its HORIZON next to every verdict, because a history-based instrument that does not state its window reads as completeness
Matrix cell	Behavioural code analysis: hotspots and change coupling · `runtime/_hdl_build/nx_actlog.nx` · WATCHING decl
Gate	NO-GATE-DECLARED — `knowledge/organ_gate.conf` carries no row for `nx_actlog`; declare `nx_actlog TAB <gate>` and the ship loop proves it and the verdict lands here.
Work log	no log row names this rung yet

CQ7 Duplication trend not just level · cell LANDED · gate NO-GATE-DECLARED

Contract	`fg_trend` · executor Organ · 1 u · stands on nothing
Definition of done	One census is a level; a trend needs two in time. ACCEPT RULE: the organ must APPEND to a durable log on a beat and must refuse to emit a trend from a single sample, reporting UNOBSERVABLE instead -- an axis that cannot see must abstain rather than acquit. Field bar for context: block duplication up 81 percent and refactored lines down from 21 to 3.8 percent across 623 million AI-era changes
Matrix cell	AI-generated code quality: duplication and refactor trend · `runtime/_hdl_build/nx_forkgrade.nx` · LANDED decl
Gate	NO-GATE-DECLARED — `knowledge/organ_gate.conf` carries no row for `nx_forkgrade`; declare `nx_forkgrade TAB <gate>` and the ship loop proves it and the verdict lands here.
Work log	no log row names this rung yet

CQ8 Chidamber-Kemerer re-targeted to organ-as-class · cell WATCHING · gate NO-GATE-DECLARED

Contract	`h_ck_suite` · executor Organ · 1.5 u · stands on CQ1
Definition of done	WMC RFC and LCOM re-targeted to organ granularity; DIT and NOC stay DECLARED INAPPLICABLE and must be printed as such rather than as zero. ACCEPT RULE: each metric ships with its re-targeting stated in the output itself, so no reader can mistake an analogue for the original. A metric that cannot state its own mapping does not ship
Matrix cell	Chidamber-Kemerer OO suite WMC DIT NOC CBO RFC LCOM · `runtime/_hdl_build/nx_eco_graph_honesty.nx` · WATCHING decl
Gate	NO-GATE-DECLARED — `knowledge/organ_gate.conf` carries no row for `nx_eco_graph_honesty`; declare `nx_eco_graph_honesty TAB <gate>` and the ship loop proves it and the verdict lands here.
Work log	no log row names this rung yet

CQ9 Technical debt ratio with a remediation cost model · cell WATCHING · gate NO-GATE-DECLARED

Contract	`dbt_ratio` · executor Organ · 1.5 u · stands on CQ4
Definition of done	A SQALE-style ratio needs a per-finding remediation cost and a cost-to-develop constant. ACCEPT RULE: the cost model lives in a CONF as data, never in code, and the ratio must never be published without the constant it divided by -- a rating derived from an unstated denominator is the invisible-bar defect this estate has already paid for once
Matrix cell	Technical debt ratio and the A-E maintainability rating · `runtime/nx_debt.nx` · WATCHING decl
Gate	NO-GATE-DECLARED — `knowledge/organ_gate.conf` carries no row for `nx_debt`; declare `nx_debt TAB <gate>` and the ship loop proves it and the verdict lands here.
Work log	no log row names this rung yet

CQ10 Connascence of meaning across organs · cell WATCHING · gate NO-GATE-DECLARED

Contract	`h_connascence` · executor Organ · 2 u · stands on CQ4
Definition of done	Our import graph sees connascence of NAME and nothing else. The measurable next form is connascence of MEANING: the same magic literal agreed upon in two organs with no shared binding. ACCEPT RULE: must find a planted cross-organ shared literal and must NOT fire on two independent uses of a structurally forced constant such as an argv index. False-positive rate measured on real data and driven to zero without losing the planted true positive
Matrix cell	Connascence as the coupling vocabulary · `runtime/_hdl_build/nx_eco_graph_honesty.nx` · WATCHING decl
Gate	NO-GATE-DECLARED — `knowledge/organ_gate.conf` carries no row for `nx_eco_graph_honesty`; declare `nx_eco_graph_honesty TAB <gate>` and the ship loop proves it and the verdict lands here.
Work log	no log row names this rung yet

CQ11 Emission provenance index · cell PRESENT · gate NO-GATE-DECLARED

Contract	`em_query` · executor Organ · 1 u · stands on nothing
Definition of done	SHIPPED 2026-08-23, gate GREEN 9 of 9, both organs LIVE in nx_catalog. The question which function emits this text and which constant bounds this buffer, answered in ONE CALL over a composed-emission index of the whole corpus -- 148010 blocks, 1360 bound constants, 5176 reads, partition reconciled by the gate. ACCEPT RULE declared in advance and met as written: a positive control must name a real emitter by file line and function, a runtime-assembled fabricated literal must return zero sites and exit 1 so the gate cannot pass by indexing its own fixture, a bound query must name both the definition and a read site, and the blind spot for byte-code emissions must be printed in the stamp. Built only after nx_codewiki_ask, nx_capsearch, a full-corpus literal grep and nx_forkcensus were each asked and each missed
Matrix cell	Emission provenance: which function emits this text, which constant bounds this buffer · `runtime/nx_emitmap.nx` · PRESENT decl
Gate	NO-GATE-DECLARED — `knowledge/organ_gate.conf` carries no row for `nx_emitmap`; declare `nx_emitmap TAB <gate>` and the ship loop proves it and the verdict lands here.
Work log	no log row names this rung yet

CQ12 Purpose names for rule 11: a literal is named by VALUE AND CONTEXT from a table, never restated · cell PRESENT · gate NO-GATE-DECLARED

Contract	`mg_name_lookup` · executor Organ · 1.5 u · stands on CQ3
Definition of done	nx_magic reads knowledge/magic_names.conf (value, context needle, name, why) and resolves every site once from the same context window map prints; consts dedupe by NAME so one value with two meanings becomes two consts; map, propose and apply all carry name_src=table or mechanical and the mechanical rows are the worklist; done-rule: nx_magic_gate GREEN with the first-row-wins, star-row, one-value-two-names, unlisted-value and absent-conf controls, and nx_magic propose on a real organ shows table names beside mechanical ones
Matrix cell	Purpose names for literals: a table names a literal by value AND context, the tool applies the name and marks every one it could not name · `runtime/_hdl_build/nx_magic_lib.nx` · PRESENT decl
Gate	NO-GATE-DECLARED — `knowledge/organ_gate.conf` carries no row for `nx_magic_lib`; declare `nx_magic_lib TAB <gate>` and the ship loop proves it and the verdict lands here.
Work log	2026-09-05 land operator 2026-09-05 (your magic numbers everywhere until you make the estate truly intelligent): nx_magic apply used to name every hoisted literal <PFX>_MAGIC_<value>, a placeholder that restates the value; the seat then renamed by hand, once, in one file. The resolver now lives in nx_magic_lib (mg_names_load, mg_ctx_window, mg_ctx_has, mg_name_lookup) over knowledge/magic_names.conf (67 seed rows: the character bytes, the JSON separators as written by wc, the digit base, I64_BYTES beside BITS_PER_BYTE discriminated by the operator beside the 8, MODE_0644 and MODE_0755, PERMIL and PERCENT and DECIMAL, the mmap reserves, the HTTP statuses); nx_magic resolves each site once, dedupes consts by name, prints name_src per row and names_conf, names_rows and named_sites in every envelope; a mechanical const keeps its NX-UNNAMED marker and a table-named one carries NX-NAMED; nx_magic_gate 34 to 51 teeth GREEN on the NAS (first-row-wins, the star row, one value two names, an unlisted value, an absent conf, the centred long-line window) 2026-09-05 measure /api/build nx_magic after the seven resolver edits returned BUILT 40062 B sha baba2a4d with src_sha256 34e87b83 (the NEW source) -- and the staged artifact carried ZERO of the new strings (nx_txtscan count name_src = 0; nx_contentdiff vs live: 86 runs both sides, one allocator message swapped, nothing gained): the third sighting today of /api/build serving a pre-edit artifact for a changed source. Remedy taken as documented: a real provenance comment appended to the source so the closure key cannot match the fossil, then rebuilt; the receipt's src_sha256 is NOT evidence the bytes are fresh -- only a string the new source alone can carry is 2026-09-05 land NAS: after the cache-key bump /api/build nx_magic BUILT 56120 B sha 6c1fa169 (the stage now carries name_src x4); nx_contentdiff vs live 40039 B: 3 runs lost, every one named and superseded (the allocator-lib contention message swapped for its newer twin, the old propose note replaced by the name_src note, the NX-UNNAMED marker reworded to point at the table) against 80 gained; /api/promote accepted it inside its calibrated band without the loss flag, PROMOTED prev=1; nx_magic_gate 51 of 51 GREEN on the NAS through nx_job_run; nx_offc_install refreshed the runner twin 2026-09-05 measure FIRST DOGFOOD on the promoted nx_magic, nx_swcompare_lib.nx at threshold 2: 379 sites over 49 distinct values became 57 distinct NAMES (the one-value-two-names split fired live: 48 as RV_CH_ZERO x2 beside RV_DIGIT_BASE x3, 10 as RV_CH_LF x11 beside RV_DECIMAL x2), names_rows=64, named_sites=187 of 379 (493 permil) with RV_CH_COMMA x95, RV_CH_COLON x13, the brackets x8 each and RV_I64_PAIR x5 named from the table; the mechanical residue named its own next rows (the JSON and HTML writers spell bytes as wc(fd, N): 34, 92, 32, 35, 60, 62) and 13 rows were added to the conf as DATA, no rebuild -- the second run measures the gain 2026-09-05 measure SECOND DOGFOOD after 13 conf rows landed as DATA (no rebuild): same file, same 379 sites, names_rows=77, named_sites 187 to 201 (493 to 530 permil); the writers' bytes now read RV_CH_QUOTE, RV_CH_BACKSLASH, RV_CH_SPACE, RV_CH_HASH, RV_CH_LBRACE, RV_CH_RBRACE; the residue is organ-specific (RV_MAGIC_2 x59 as the halves and pairs of this lib, 4 x20, 3 x14, 5 x14, 700 and 999 and 600 as this lib's own thresholds) and is the owner's naming, which the note in every envelope now asks for by pointing at the table 2026-09-05 retract the measure row above named the wrong mechanism: the 40062 B stage was NOT a build-cache hit and the provenance comment was NOT the fix -- the sovereignty lane measured the true cause the same evening (nx_hostctl cmd_buildrun staged the PREVIOUS artifact after the builder refused, a false-green BUILT, third occurrence) and DEPLOYED the root fix (hostctl ab32babd via /api/deploy); this seat's second build simply ran after the refusal cleared. The receipt-level lesson stands: a BUILT receipt with a fresh src_sha256 is not evidence the bytes are fresh; only a string the new source alone carries is 2026-09-05 measure ON THE LIVE SURFACE: the regen launched after the CQ12 rows landed republished /compare/codequality at 106941 B (from 98876) and the docroot page carries the CQ12 matrix row and plan rung (nx_txtscan count of the row label = 2); nx_compare_rank codequality reads 13 rungs, done=3, CQ12 counted done because its symbol resolves in the matrix row; referee grade and operator ACCEPT row still owed before the rung reads complete 2026-09-05 retract EVIDENCE REFEREE RUN 2026-09-05 on codequality read grounded=14 ungrounded=1 verdict=RED, failing conjunct grounded: the Proof-carrying change row named symbol cd_contains in runtime/nx_contentdiff.nx and that symbol does not exist in the organ (its functions are cd_slurp, cd_show_other, cd_show_gained, cd_show_lost and main) -- a published EXCEED claim whose symbol was absent from the organ its own row names, standing since the board was admitted. Corrected as DATA: the row now names cd_show_lost, the function that NAMES each lost run, which is exactly the capability the row claims; the referee re-run is the acceptance. Same pass: codequality.gates created (nx_magic_gate 51 of 51 on the NAS), ref cwe547 mirrored and pinned (93193 B, h369b05d6) and cited inline on the CQ12 row

CQ13 A numeric bound is DERIVED or EVIDENCED, never bare -- the estate-wide census and ratchet over every const that sizes a pool, cap, buffer, table or threshold · cell NO-MATRIX-ROW · gate NO-MATRIX-ROW

Contract	`bound_evidence_census` · executor Organ · 3 u · stands on CQ12
Definition of done	DONE-RULE PRE-DECLARED 2026-09-05 (operator, same day: this needs estate-wide fixing from the first byte up -- numbers need evidence on why they are set or need to be dynamic, no guessing). The measured trigger is lang LN60: a compiler pool declared at 4096 with a comment asserting it could not be derived stopped a real build at 4097, the third such incident in one file, while the sibling pool beside it had been derived for months. Rule 11 and nx_magic already name and hoist LITERALS; this rung is the next axis -- for every hoisted const that feeds a sys_mmap size, an array bound, a loop cap, a chunk size, a retry count or a threshold, classify its PROVENANCE: DERIVED (the initialiser is an expression of another named quantity or a pass over the input), EVIDENCED (the adjacent comment names a measurement, a spec section, a published bar or a conf key), or BARE (a number with no witness). Done when: (1) the census organ walks every .nx in both trees, publishes the partition with sums on this page (counts are not a worklist -- it NAMES every BARE site file:line), and its own fixtures plant one of each class and bite; (2) BARE is a named-set ratchet like nx_unwired (a rise names the file and const), never a count-only threshold; (3) the three known-good classes each carry a positive control in the gate so a classifier that calls everything BARE cannot pass; (4) the /compare page renders DERIVED/EVIDENCED/BARE per domain so the number a domain plans against carries its own reason. Deliberately NOT a rewrite campaign: the ratchet drains BARE by evidence or derivation at each site as it is touched, and a cap that is genuinely unknowable is EVIDENCED by naming the one purpose it serves and making its exhaustion announce (CLAUDE.md, a buffer cap is not a number to tune)
Matrix cell	NO-MATRIX-ROW — no matrix row carries `bound_evidence_census`; the ranker reads this rung as unmapped and no cell can flip for it. Add the row and the join completes on the next publish.
Gate	the gate join needs a matrix row: no organ is named for this rung
Work log	2026-09-06 queue FLAGGED 2026-09-05 from the gameengine lane; the compiler instance is being fixed there (lang LN60, count_global_tokens in nx_parse.nx) and this rung owns the estate-wide census + ratchet. Instruments to compose, never re-implement: nx_magic map/propose (literal sites), nx_law_warden countfile, nx_unwired (the name-set ratchet shape), nx_absent for the whole-population walk; the new judgement is the provenance class of a const, which none of them measures today

dossiers=14 cells_joined=12 no_matrix_row=2 (sum 14) gates_recorded=0 gates_unrecorded=0 no_gate_declared=12 (sum 12 of cells_joined) evgates=UNSTAMPED

Capability comparisons

Compare the field, search individual capabilities and open their source and adoption evidence. Documented presence does not establish comparative quality.

Position map — centrality and distinctiveness

The four-quadrant map the field uses for brand strategy (Dawar and Bagga, HBR June 2015), re-derived from this matrix on every publish. Centrality is the share of the category's feature mass a player covers, each feature weighted by how many hold it; distinctiveness is the average lead over each rival on the rows the player holds; breadth is the depth-weighted share of the whole matrix (the bubble); depth is how deeply the rows held are held; momentum is the day-over-day move off the spine (green rising, red falling, grey until day two); the dashed path runs first day → previous day → today. Dividers are the category means. Axes are fitted to the field of play, so read the tick numerals, not the frame. Rival marks are documented presence, so a rival's position reads the record, never its quality. The picture grades its own readability below; the table beside it is the same data for a screen reader or a second method.

Rows. 24 feature rows mapped of 24 matrix rows; 0 substrate rows (kernels, bounds and instruments the plan's rungrole marks substrate) are the estate's scaffolding, not category features, and stay off the map

Views. 2D cut: centrality, distinctiveness · 3D cube: centrality, distinctiveness, breadth · axes registered: centrality, distinctiveness, breadth, depth, momentum · a board picks its own in knowledge/compare/codequality.cdmap (cut|x|y, cube|x|y|z); absent = the HBR defaults

bubble area = breadth · ring = momentum (green rising, red falling, grey until day two) · dashed = category means · axes fitted to the field of play: centrality 0–1000, distinctiveness 250–550 of 0–1000 permil (the full range put every player in one corner)
readability of the 2D cut, self-graded by the layout ruler: label overlaps 0 · labels over marks 0 · off-canvas 0 · unresolved labels 0 · mark overlaps 0 (a fact of the data: two players that close are that close) · data spread 679 permil of the plot · quadrant words unseated 0
text contrast, measured with wcag2-ratio (floors from contrast.conf), light theme: labels 16.24 (floor 4.50) · notes 16.24 (floor 4.50) · quadrant words 5.89 (floor 4.50) · tick numerals 5.89 (floor 4.50) · axis titles 5.59 (floor 4.50) · dark theme: labels 13.78 (floor 4.50) · quadrant words 5.55 (floor 4.50) · axis titles 5.97 (floor 4.50) · dark classes under their floor 0 (one figure serves both themes: a dark shortfall is a token to fix, never a class to hide) · classes refused under their floor 0 (a refused class is not drawn; the scale classes are measured, never hidden) · export: SVG PNG (receipt, rendered by the estate's own rasteriser from this page)

axes fitted: centrality 0–1000 · distinctiveness 250–550 · breadth 0–700 permil · farther bubbles are painted first, nearer ones over them · the floor shadow is each bubble's (x, y) at height 0
readability of the 3D cube, self-graded by the layout ruler: label overlaps 0 · labels over marks 0 · off-canvas 0 · unresolved labels 0 · mark overlaps 1 (a fact of the data: two players that close are that close) · data spread 300 permil of the plot

Nishi SonarQube CodeScene NDepend PIT
10 panels over 5 registered axes, every pair once (the lower axis on x, the higher on y) · each panel fitted to its own field of play, first and last tick numerals shown · no labels in a small cut, the legend names the colours; the grade below reports the mark terms only (MM summed over the panels, spread averaged)
readability of the small multiples, self-graded by the layout ruler: label overlaps 0 · labels over marks 0 · off-canvas 0 · unresolved labels 0 · mark overlaps 5 (a fact of the data: two players that close are that close) · data spread 555 permil of the plot

Player	Quadrant	centrality	distinctiveness	breadth	depth	momentum	Rows held	Days on spine	First seen
Nishi	Aspirational	705	489	555	833	0 since 2026-09-23	16	10	2026-09-15
SonarQube	Aspirational	867	430	625	833	0 since 2026-09-23	18	10	2026-09-15
CodeScene	Mainstream	764	311	458	733	0 since 2026-09-23	15	10	2026-09-15
NDepend	Mainstream	823	392	569	803	0 since 2026-09-23	17	10	2026-09-15
PIT	Peripheral	102	375	69	833	0 since 2026-09-23	2	10	2026-09-15

Day	Matrix rows reviewed	Players recorded
2026-09-15	24	5
2026-09-16	24	5
2026-09-17	24	5
2026-09-18	24	5
2026-09-19	24	5
2026-09-20	24	5
2026-09-21	24	5
2026-09-22	24	5
2026-09-23	24	5
2026-10-08	24	5

How to read this evidence. A Nishi source mark records whether the named symbol is declared in the selected source file. It does not establish working behavior or accepted delivery. A watching tag names an expected source entry; discovering it updates source coverage only. A dark tag means the file exists but the named symbol was not found: inspect the source and contract before assuming the capability is missing or renaming code. Peer codes are authored assessments; unassessed means no comparison is established, not absence. Qualification, deployment identity, runtime observations and acceptance must carry their own evidence. Adoption records the catalog's observed path through source, build, promotion, registration and invocation; libraries use importer evidence and gates use declared execution surfaces. A full catalog path does not establish quality, freshness or a successful user outcome. Partial and unknown states retain their stated next action. Census stamps: importers asof 1790637268, gate census asof 1790104131 (unix seconds; -1 = census absent).

Capability matrix — measured against source

◉ authored stronger claim; source present● present◐ partial○ absent? unassessed; excluded from relative comparison · click any capability for its evidence

Peer cell coverage: authored assessed 96, unassessed 0. Authored assessments are not verified outcomes.

Capability	Nishi	SonarQube	CodeScene	NDepend	PIT
ISO 5055 automated source-code quality measures Measured: `cw_scan_file` exists in `runtime/_hdl_build/nx_cwe_scan.nx`, verified at emit. MEASURED: covered_of_4=3 (Reliability Security Performance) with Maintainability the declared gap, rules_implemented 5 of ~140. SonarQube is Best for breadth of implemented rules. Ours is real ISO 5055 conformance measurement at 3.6 percent rule coverage and it says so in its own output [iso25010] Adoption: `REGISTERED-DARK` — PARTIAL: callable, authorised, completed MCP invocation not established by supplied journal window; lifetime history unknown (direct execution may be recorded elsewhere; this scan does not establish lifetime use); no execution surface runs it either (clock, cron, daemon, roster, actlog and surfaced forks checked). not adopted: callable, authorised, completed MCP invocation not established by supplied journal window; lifetime history unknown (direct execution may be recorded elsewhere; this scan does not establish lifetime use); no execution surface runs it either (clock, cron, daemon, roster, actlog and surfaced forks checked) Pros Implementing source symbol found; runtime acceptance separate; ahead of PITCons behind SonarQube (leads); not adopted yet: callable, authorised, completed MCP invocation not established by supplied journal window; lifetime history unknown (direct execution may be recorded elsewhere; this scan does not establish lifetime use); no execution surface runs it either (clock, cron, daemon, roster, actlog and surfaced forks checked)	●	◉	●	●	○
Cyclomatic complexity per function (McCabe) Measured: `mc_scan_file` exists in `runtime/nx_mccabe_lib.nx`, verified at emit. SHIPPED 2026-08-20 and this row was a watch contract the same morning -- nx_mccabe_lib plus a thin main plus a gate at GREEN 17 of 17, closing the seq251 filing. MEASURED FULL POPULATION over 18,879 files and 103,733 functions with 0 unreadable: p50=3 p90=12 p99=43 mean=5 max=2996, and the histogram SUMS EXACTLY to 103,733. Above the CITED bar of 10: 12,639 functions or 121 permille. THAT COUNT IS AN UPPER BOUND ON AUTHORED COMPLEXITY DEBT and the direction is stated -- the tail is dominated by GENERATED and TABLE code (v(G) 2996 in nx_triangulation_arith_500, 1001 in generated_primitives_1000, 652 in an HTML entity table, 644 in a font bitmap), 139 functions sit at 100 or above, and splitting generated from authored is rung CQ1a because the estate's existing marker detector uw_generated matches only one of the four worst files. No bar was invented here: the distribution is published first, percentiles are derived from the CDF, and 10 is reported never enforced. McCabe TRANSFERS CLEANLY -- it needs a control-flow graph of one procedure with a single entry and exit, which NishiLang functions have [mccabe76]. NIST SP 500-235 formalises the limit of 10 and the multiway-decision exemption [nist500235]. The gap was REAL when this page was admitted on the morning of 2026-08-20 -- nx_capsearch returned no complexity organ and our own ISO 5055 scanner had filed it as seq251 -- and it was CLOSED the same day rather than left standing as a contract. This sentence is kept rather than deleted because a page that quietly erases the gap it just closed teaches nobody anything Adoption: `LIB-WIRED importers=9 nonval=8` — fully adopted (top of its ladder). dossier Pros Implementing source symbol found; runtime acceptance separate; ahead of PIT; fully adopted on the estate ladderCons behind SonarQube (leads), CodeScene (leads), NDepend (leads)	●	◉	◉	◉	○
Halstead volume and Maintainability Index DARK — `runtime/_hdl_build/nx_cwe_scan.nx` EXISTS but does not declare `cw_halstead`: something shipped at this path under another name, and this mark would read open forever. Repoint the contract to the real entry point (the plan rung AND this row) or rename the function; the flip follows on the next beat, and the `comparewatch-` plane row reads DARK until then. TRANSFERS: operators and operands are lexically separable in NishiLang. Absent here. Publish the contested-formula caveat WITH the number when it lands -- the MI coefficients are an empirical fit, not a law [mi_contested] dossierwatching cw_halstead Pros none measured yetCons behind SonarQube (leads), CodeScene, NDepend (leads); open contract; expected source declaration not established	○	◉	●	◉	○
Acyclic dependencies and propagation cost Source present; authored stronger claim: `aname` in `runtime/_hdl_build/nx_eco_graph_arch.nx`, verified at emit. EXCEED and MEASURED 2026-08-20 over 18,945 nodes and 49,593 edges: nontrivial SCCs=0, organs-inside-cycles=0, propagation-cost 0.4 percent vs published Linux 5-18 percent. NDepend computes cycles and is Best among the named tools; none of them publishes a MacCormack propagation cost. SUBJECT DECLARED: this was measured on the LAPTOP TWIN at 18945 nodes, while the ecosysdesign page's figures come from the NAS store at 16222 organs. So zero cycles is a claim about THIS corpus and is NOT by itself proof that the one 2-organ cycle ecosysdesign records has gone from the NAS tree. Two corpora, two answers, both declared rather than merged -- which is the same discipline this page applies to everyone else rival marks uncited — the Yes, Best or Part codes on this row are an observation read with no reference mark behind them Adoption: `RUN-BY:fork:nx_arch_board` — fully adopted (top of its ladder). Pros Source symbol found; stronger capability claim is authored; ahead of SonarQube, CodeScene, PIT; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)	◉	○	●	◉	○
Afferent and efferent coupling with instability I Measured: `h_srcpath` exists in `runtime/_hdl_build/nx_eco_graph_honesty.nx`, verified at emit. MEASURED at organ granularity: Ca for nx_syscalls.nx is 15,026 (79 percent of organs), nx_tier.nx 2,878, nx_gate_verdict.nx 1,245. Ca==0 for 12,931 nodes so I=1.0 for 68 percent of the graph and I=0 at the base -- a textbook stable-base and instable-periphery shape. Ce outliers: 132 organs import 14 or more parents, worst 26. NDepend is Best because it implements the full Martin set [martin94] Adoption: `REGISTERED-DARK` — PARTIAL: callable, authorised, completed MCP invocation not established by supplied journal window; lifetime history unknown (direct execution may be recorded elsewhere; this scan does not establish lifetime use); no execution surface runs it either (clock, cron, daemon, roster, actlog and surfaced forks checked). not adopted: callable, authorised, completed MCP invocation not established by supplied journal window; lifetime history unknown (direct execution may be recorded elsewhere; this scan does not establish lifetime use); no execution surface runs it either (clock, cron, daemon, roster, actlog and surfaced forks checked) Pros Implementing source symbol found; runtime acceptance separate; ahead of PITCons behind NDepend (leads); not adopted yet: callable, authorised, completed MCP invocation not established by supplied journal window; lifetime history unknown (direct execution may be recorded elsewhere; this scan does not establish lifetime use); no execution surface runs it either (clock, cron, daemon, roster, actlog and surfaced forks checked)	●	●	●	◉	○
Abstractness A and distance from the main sequence D Measured: `an` exists in `runtime/_hdl_build/nx_eco_graph_arch.nx`, verified at emit. DECLARED INAPPLICABLE and scored Part for exactly the half that transfers. A = abstract classes divided by total classes; NishiLang has no abstract classes so A has neither numerator nor denominator, and D as the absolute value of A plus I minus 1 divided by root 2 therefore cannot be computed. I IS computed and published in the row above. Any substitute for A would be a different metric wearing Martin's name [martin94] Adoption: `RUN-BY:fork:nx_arch_board` — fully adopted (top of its ladder). Pros Implementing source symbol found; runtime acceptance separate; ahead of CodeScene, PIT; fully adopted on the estate ladderCons behind NDepend (leads)	●	●	○	◉	○
Chidamber-Kemerer OO suite WMC DIT NOC CBO RFC LCOM DARK — `runtime/_hdl_build/nx_eco_graph_honesty.nx` EXISTS but does not declare `h_ck_suite`: something shipped at this path under another name, and this mark would read open forever. Repoint the contract to the real entry point (the plan rung AND this row) or rename the function; the flip follows on the next beat, and the `comparewatch-` plane row reads DARK until then. SPLIT VERDICT stated honestly. DIT and NOC are INAPPLICABLE -- there is no inheritance tree of types, our base class is a shared-function import with depth 1 by construction and no subclass count. CBO maps onto the import graph and is effectively covered by the coupling row. WMC RFC and LCOM are RE-TARGETABLE to organ-as-class but are NOT computed, and an untargeted metric is better absent than approximated [ck94] dossierwatching h_ck_suite Pros none measured yetCons behind SonarQube (leads), CodeScene, NDepend (leads); open contract; expected source declaration not established	○	◉	●	◉	○
Mutation score as the test-quality standard Source present; authored stronger claim: `gb_try` in `runtime/_hdl_build/nx_gate_bite.nx`, verified at emit. EXCEED in KIND, behind in COVERAGE. PIT is Best and is the reference implementation of mutation score [pitest]. Ours mutates the SUBJECT as well as the test, which is the failure mode that makes naive mutation testing vacuous. Estate sweep 2026-08-07: 76 gates, BITES 41 INCONCLUSIVE 23 UNCONTROLLED 12, partition sums. Published as a BOUND with its direction -- a bigger budget only moves INCONCLUSIVE to BITES, so 539 permil is a FLOOR, and the log is 13 days stale with 9 of its 12 UNCONTROLLED rows since remediated Adoption: `RUN-BY:actlog` — fully adopted (top of its ladder). Pros Source symbol found; stronger capability claim is authored; ahead of SonarQube, CodeScene, NDepend; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)	◉	○	○	○	◉
Duplication across the corpus Measured: `fg_find_line` exists in `runtime/_hdl_build/nx_forkgrade.nx`, verified at emit. Cross-tree fork graded over 2,845 pairs MEASURED 2026-08-07 and DELIBERATELY NOT RE-RUN THIS SESSION (the box sat above its admission ceiling at load 18.19 so this is a DATED figure and the only number on this page that was not re-measured today): identical 207, bidirectional 2,638, A-SUPERSET 0. The empty A-SUPERSET class is the finding -- an auto-adopt leg was built against a class that does not exist, which only a full population could reveal. SonarQube is Best for in-tree clone detection which we do not have as a standing beat rival marks uncited — the Yes, Best or Part codes on this row are an observation read with no reference mark behind them Adoption: `REGISTERED-DARK` — PARTIAL: callable, authorised, completed MCP invocation not established by supplied journal window; lifetime history unknown (direct execution may be recorded elsewhere; this scan does not establish lifetime use); no execution surface runs it either (clock, cron, daemon, roster, actlog and surfaced forks checked). not adopted: callable, authorised, completed MCP invocation not established by supplied journal window; lifetime history unknown (direct execution may be recorded elsewhere; this scan does not establish lifetime use); no execution surface runs it either (clock, cron, daemon, roster, actlog and surfaced forks checked) Pros Implementing source symbol found; runtime acceptance separate; ahead of PITCons behind SonarQube (leads); not adopted yet: callable, authorised, completed MCP invocation not established by supplied journal window; lifetime history unknown (direct execution may be recorded elsewhere; this scan does not establish lifetime use); no execution surface runs it either (clock, cron, daemon, roster, actlog and surfaced forks checked)	●	◉	●	●	○
Dead code
defined and never called Source present; authored stronger claim: `uw_defcomplete` in `runtime/_hdl_build/nx_unwired.nx`, verified at emit. EXCEED: whole-corpus, and the ratchet baseline is a SET OF NAMES so a rise names the function and the file rather than printing a number. RE-MEASURED 2026-08-20: 1,199 unwired over 18,680 files. The standing figure of 398 was taken over a 7,132-file corpus -- a DIFFERENT population, not a regression, and the organ says so itself by refusing to attribute the delta rival marks uncited — the Yes, Best or Part codes on this row are an observation read with no reference mark behind them Adoption: `BUILT-UNPROMOTED` — PARTIAL: compiled, never promoted to the serving root: /api/promote it. not adopted: compiled, never promoted to the serving root: /api/promote it Pros Source symbol found; stronger capability claim is authored; ahead of SonarQube, CodeScene, NDepend, PITCons not adopted yet: compiled, never promoted to the serving root: /api/promote it	◉	●	●	●	○
Magic constants as a maintainability rule Source present; authored stronger claim: `mg_first_ns` in `runtime/_hdl_build/nx_magic_lib.nx`, verified at emit. EXCEED: map, propose and APPLY -- the fixer hoists each literal to a named const and proves neutrality by byte-identical rebuild. Static analysers flag magic numbers; none of the named tools ships a fix whose safety is provable. Ratcheted per file, and the bar is now printed in every verdict after it was measured invisible on 2026-08-17 rival marks uncited — the Yes, Best or Part codes on this row are an observation read with no reference mark behind them Adoption: `LIB-WIRED importers=3 nonval=2` — fully adopted (top of its ladder). Pros Source symbol found; stronger capability claim is authored; ahead of SonarQube, CodeScene, NDepend, PIT; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)	◉	●	○	●	○
Base-class adoption as the OO discipline measure Measured: `gl_strip` exists in `runtime/nx_gatelaw_gate.nx`, verified at emit. THE WEAKEST AXIS AND THE MOST HONEST NUMBER HERE. 338 of 3,139 gate sources inherit the shared verdict base -- 10.8 percent -- and 2,801 are hand-rolled and thus UNMEASURED by the exit-verdict and negative-control laws. Partition sums 338 plus 2,801 equals 3,139. DISCARDS-VERDICT is 0, so the once-feared class is empty [ck94] Adoption: `GATE:LIVE trial=GREEN` — fully adopted (top of its ladder). Pros Implementing source symbol found; runtime acceptance separate; ahead of PIT; fully adopted on the estate ladderCons behind SonarQube (leads), NDepend (leads)	●	◉	●	◉	○
Architecture fitness functions in the delivery path Source present; authored stronger claim: `gv_verdict` in `runtime/nx_gate_verdict.nx`, verified at emit. EXCEED: a fitness function is an objective automatable integrity assessment of an architectural characteristic [fitnessfn], and our gates ARE that by construction -- gv_check makes declared equal executed, the exit code carries the verdict, and negative controls are named so a census can find them. The named tools report metrics; they do not refuse a deploy on an architectural predicate Adoption: `LIB-WIRED importers=2826 nonval=854` — fully adopted (top of its ladder). Pros Source symbol found; stronger capability claim is authored; ahead of SonarQube, CodeScene, NDepend, PIT; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)	◉	●	●	●	●
Proof-carrying change: capability-loss refusal on promote Source present; authored stronger claim: `cd_show_lost` in `runtime/nx_contentdiff.nx`, verified at emit. EXCEED with no competitor. Every promotion diffs the staged binary against the live one and NAMES each lost run; the strict oracle is GREEN only at zero loss while the calibrated promote door permits a small named loss. Nothing in the field imposes a per-promotion capability-loss proof. This is the strongest single result on this page Adoption: `RUN-BY:fork:nx_rebuild_drain` — fully adopted (top of its ladder). Pros Source symbol found; stronger capability claim is authored; ahead of SonarQube, CodeScene, NDepend, PIT; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)	◉	○	○	○	○
Technical debt ratio and the A-E maintainability rating DARK — `runtime/nx_debt.nx` EXISTS but does not declare `dbt_ratio`: something shipped at this path under another name, and this mark would read open forever. Repoint the contract to the real entry point (the plan rung AND this row) or rename the function; the flip follows on the next beat, and the `comparewatch-` plane row reads DARK until then. ABSENT and honestly so. SQALE-style debt ratio needs a per-rule remediation cost in developer-minutes and a cost-to-develop-one-line constant, defaulting to 30 minutes per line, to normalise by LOC [sonarqube_debt]. We have a debt LEDGER with severities but no remediation-cost model, so no ratio and no rating. Note also that SonarQube's Reliability and Security ratings are worst-issue-severity based, NOT ratio based -- a distinction routinely conflated dossierwatching dbt_ratio Pros none measured yetCons behind SonarQube (leads), CodeScene, NDepend; open contract; expected source declaration not established	○	◉	●	●	○
Behavioural code analysis: hotspots and change coupling DARK — `runtime/_hdl_build/nx_actlog.nx` EXISTS but does not declare `al_hotspot`: something shipped at this path under another name, and this mark would read open forever. Repoint the contract to the real entry point (the plan rung AND this row) or rename the function; the flip follows on the next beat, and the `comparewatch-` plane row reads DARK until then. ABSENT, and our substrate is UNUSUALLY WELL SUITED to it. CodeScene is Best and needs a version-control history joined to an issue tracker [codered22]; we have no branches, but we DO have ACTION-GRAIN history -- every tool call and refusal with its reasoning. That is finer than commit grain, so the hotspot instrument here should be a new READER of an existing journal, not a new collector. Correction carried: the vendor docs define change frequency as the IDENTIFICATION axis with code health overlaid separately, not the popular complexity-times-churn product dossierwatching al_hotspot Pros none measured yetCons behind SonarQube, CodeScene (leads); open contract; expected source declaration not established	○	●	◉	○	○
Connascence as the coupling vocabulary DARK — `runtime/_hdl_build/nx_eco_graph_honesty.nx` EXISTS but does not declare `h_connascence`: something shipped at this path under another name, and this mark would read open forever. Repoint the contract to the real entry point (the plan rung AND this row) or rename the function; the flip follows on the next beat, and the `comparewatch-` plane row reads DARK until then. ABSENT everywhere, including in the named tools, and worth stating as a limit on this whole page: connascence holds that a substantial class of coupling is dynamic and NOT statically analysable at all [connascence]. Our import graph measures connascence of NAME at module granularity and nothing else. Static coupling being excellent is therefore necessary and not sufficient dossierwatching h_connascence Pros none measured yetCons behind NDepend; open contract; expected source declaration not established	○	○	○	●	○
Weakness classes: CWE Top 25 and OWASP Top 10 Measured: `cw_capshape` exists in `runtime/_hdl_build/nx_cwe_scan.nx`, verified at emit. CATEGORY ERROR NAMED RATHER THAN SCORED. Both standards measure REPORTED vulnerabilities in SHIPPED software -- CWE Top 25 scores 39,080 CVE records by frequency times severity [cwe_top25] and OWASP ranks by incidence across 2.8 million applications, explicitly ignoring frequency within an application [owasp_top10]. Neither can be pointed at a repository, so there is no such thing as our CWE Top 25 score. What DOES transfer is ISO 5055, the CWE canon re-expressed as source measures, which is the first row on this page Adoption: `REGISTERED-DARK` — PARTIAL: callable, authorised, completed MCP invocation not established by supplied journal window; lifetime history unknown (direct execution may be recorded elsewhere; this scan does not establish lifetime use); no execution surface runs it either (clock, cron, daemon, roster, actlog and surfaced forks checked). not adopted: callable, authorised, completed MCP invocation not established by supplied journal window; lifetime history unknown (direct execution may be recorded elsewhere; this scan does not establish lifetime use); no execution surface runs it either (clock, cron, daemon, roster, actlog and surfaced forks checked) Pros Implementing source symbol found; runtime acceptance separate; ahead of CodeScene, NDepend, PITCons behind SonarQube (leads); not adopted yet: callable, authorised, completed MCP invocation not established by supplied journal window; lifetime history unknown (direct execution may be recorded elsewhere; this scan does not establish lifetime use); no execution surface runs it either (clock, cron, daemon, roster, actlog and surfaced forks checked)	●	◉	○	○	○
AI-generated code quality: duplication and refactor trend Measured: `fg_trend` exists in `runtime/_hdl_build/nx_forkgrade.nx`, verified at emit. THE MOST RELEVANT OUTSIDE BAR WE HAVE, because this corpus is almost entirely AI-authored. Field measurement over 623 million changes: block duplication up 81 percent from 2023 to 2026, refactored code down from 21 percent of changed lines to 3.8 percent, cross-file connectivity down 35 percent [gitclear26]. We can measure our duplication level but NOT its trend -- one census is a level and a trend needs two in time. Naming this as absent is the point: an AI-built estate that cannot see its own duplication trajectory is flying on a single sample Adoption: `REGISTERED-DARK` — PARTIAL: callable, authorised, completed MCP invocation not established by supplied journal window; lifetime history unknown (direct execution may be recorded elsewhere; this scan does not establish lifetime use); no execution surface runs it either (clock, cron, daemon, roster, actlog and surfaced forks checked). dossiernot adopted: callable, authorised, completed MCP invocation not established by supplied journal window; lifetime history unknown (direct execution may be recorded elsewhere; this scan does not establish lifetime use); no execution surface runs it either (clock, cron, daemon, roster, actlog and surfaced forks checked) Pros Implementing source symbol found; runtime acceptance separate; ahead of NDepend, PITCons behind CodeScene (leads); not adopted yet: callable, authorised, completed MCP invocation not established by supplied journal window; lifetime history unknown (direct execution may be recorded elsewhere; this scan does not establish lifetime use); no execution surface runs it either (clock, cron, daemon, roster, actlog and surfaced forks checked)	●	●	◉	○	○
Whole-corpus ISO 5055 coverage without a scan cap DARK — `runtime/_hdl_build/nx_cwe_scan.nx` EXISTS but does not declare `cw_uncapped`: something shipped at this path under another name, and this mark would read open forever. Repoint the contract to the real entry point (the plan rung AND this row) or rename the function; the flip follows on the next beat, and the `comparewatch-` plane row reads DARK until then. SEPARATE from the ISO 5055 row above because coverage and conformance are different questions. The scanner declares truncated 1 with maxfiles 4000 against organs_present 18802, so every figure it publishes is a floor over a 21 percent prefix. The envelope IS printed and honest -- the defect is that nobody divided by the right denominator. Derive the buffer from the input rather than raising a guessed cap rival marks uncited — the Yes, Best or Part codes on this row are an observation read with no reference mark behind them dossierwatching cw_uncapped Pros none measured yetCons behind SonarQube (leads), CodeScene, NDepend; open contract; expected source declaration not established	○	◉	●	●	○
Complexity ratchet that can REFUSE a build DARK — `runtime/_hdl_build/nx_magic.nx` EXISTS but does not declare `cw_ratchet`: something shipped at this path under another name, and this mark would read open forever. Repoint the contract to the real entry point (the plan rung AND this row) or rename the function; the flip follows on the next beat, and the `comparewatch-` plane row reads DARK until then. The shape we already proved on magic constants applied to complexity: self-baseline on first sight so it is non-breaking by construction, print the bar in every verdict so it is never an invisible threshold, and NAME every offending function. Marked EXCEED because the named tools report complexity and none of them refuses a promotion on it -- measuring and refusing are different capabilities and only the second changes behaviour rival marks uncited — the Yes, Best or Part codes on this row are an observation read with no reference mark behind them dossierwatching cw_ratchet Pros none measured yetCons behind SonarQube, CodeScene, NDepend; open contract; expected source declaration not established	○	●	●	●	○
Base-class adoption ratchet keyed on a name set DARK — `runtime/nx_gatelaw_gate.nx` EXISTS but does not declare `gl_ratchet`: something shipped at this path under another name, and this mark would read open forever. Repoint the contract to the real entry point (the plan rung AND this row) or rename the function; the flip follows on the next beat, and the `comparewatch-` plane row reads DARK until then. The census exists and reads 338 of 3139; what is absent is the RATCHET. Baseline must be a SET OF NAMES not a count -- on a shared tree with concurrent seats a count-only ratchet reports a regression without saying whose, a lesson already paid for once by the dead-code lane. Census and name, never refuse rival marks uncited — the Yes, Best or Part codes on this row are an observation read with no reference mark behind them dossierwatching gl_ratchet Pros none measured yetCons behind SonarQube, NDepend; open contract; expected source declaration not established	○	●	○	●	○
Emission provenance: which function emits this text, which constant bounds this buffer Source present; authored stronger claim: `em_query` in `runtime/nx_emitmap.nx`, verified at emit. SHIPPED 2026-08-23 in one leg: organ plus gate plus row, nx_emitmap_gate GREEN 9 of 9 end to end against the deployed binary, nx_catalog reads LIVE for both, daily clock row emitmap declared. MEASURED FULL POPULATION at corpus_complete 1: 18698 sources and 118659045 bytes yield 148010 composed emission blocks, 1360 CAP or MAX constants and 5176 reads of them, and the gate checks that the counted rows equal the stamp the organ wrote, so the partition is a claim that was tested. ONE CALL NOW ANSWERS WHAT TOOK A DOZEN MANUAL READS ON 2026-08-23: find names every function whose COMPOSED emitted text contains a phrase, as file line and function; bound names a constant's definition and every line that reads it. BUILT ONLY AFTER THE INCUMBENTS WERE ASKED AND MISSED, recorded rather than assumed: nx_codewiki_ask ranks prose and returned json_emit and nx_bodyparts, nx_capsearch ranks titles and returned a truncation gate and a body generator, a literal grep over the whole corpus found the motivating empty-object reply body at 11 sites and none of them in the transport because that body is emitted as byte codes not a literal, and nx_forkcensus indexes only elf path literals. THE UNIT IS THE COMPOSED EMISSION, NOT THE LITERAL, harvested by the same rs_line_lits the refusal-shape census already trusts, because a message built from three literals on consecutive lines is one message. THE BLIND SPOT IS DECLARED IN EVERY ANSWER AND IN THE STAMP: bytes emitted as numeric codes are not indexed, so a brace pair composed from codes cannot be attributed and the organ says so instead of answering from the nearest literal -- indexing byte-code emissions is the named next rung. Every bound is announced: the corpus slot table refuses rather than truncates and the preview cap counts every cut block in the stamp. EXCEED with the why: none of the four named tools answers which function emits a given message from a composed-emission index -- they report rule findings on code, not the provenance of emitted text. The nearest shape in the field is a code-search indexer, which is a different product class and is not a column here Adoption: `RUN-BY:clock` — fully adopted (top of its ladder). dossier Pros Source symbol found; stronger capability claim is authored; ahead of SonarQube, CodeScene, NDepend, PIT; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)	◉	○	○	○	○
Purpose names for literals: a table names a literal by value AND context, the tool applies the name and marks every one it could not name Source present; authored stronger claim: `mg_name_lookup` in `runtime/_hdl_build/nx_magic_lib.nx`, verified at emit. LIVE 2026-09-05 (nx_magic PROMOTED 56120 B, dogfood on nx_swcompare_lib.nx: 201 of 379 sites named from the table, one value with two meanings split live): knowledge/magic_names.conf rows value, context needle, name, why; nx_magic resolves each site from the window it prints, dedupes consts by name (one value with two meanings becomes two consts), reports name_src per const and the table's reach in every envelope, and marks a mechanical const NX-UNNAMED beside a table-named NX-NAMED; gate 51 of 51 on the NAS. SonarQube reports a magic number (S109) and CodeScene, NDepend and PIT do not name one -- none carries a meaning table the fix can apply; the weakness class is CWE-547 hard-coded constants [cwe547], and the exceed is claimed on the promoted nx_magic naming 201 of 379 sites on a real organ from the table. Adoption: `LIB-WIRED importers=3 nonval=2` — fully adopted (top of its ladder). dossier Pros Source symbol found; stronger capability claim is authored; ahead of SonarQube, CodeScene, NDepend, PIT; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)	◉	○	○	○	○

Rival-claim provenance. Every Yes, Best or Part mark in a rival column is a claim about someone else's product. A cited row carries a reference mark that resolves to a pinned mirror (the refs gate measures that); an uncited row is an observation read and is badged in its evidence until a reference lands. The badge is the receipt, never the proof: a mark proves a mirror exists, not that the mirror supports the code. The rows are counted below.

Rival claims, counted
Class	Count	Note
rows with rival marks	21	rows carrying a Yes, Best or Part in a rival column
cited	14	a reference mark resolves to a pinned mirror
uncited	7	an observation read, badged until a reference lands
rows, summed	21	RECONCILED: the parts sum to the total 21

Delivery and evidence

Inspect risks, technical debt, rendered observations, experiments and references. Read scope and limitations alongside every result.

Risk register

Risk	Likelihood x impact	Mitigation
A complexity number is published before the instrument is bite-proven and becomes the bar everyone plans against	likely x high	CQ1's accept rule requires all 6 hand-computed fixture values AND a neg-control that must fail first. An uncalibrated classifier reports numbers never verdicts, and CQ3 is deliberately a separate rung so measuring and refusing cannot ship in the same unreviewed step.
A Maintainability Index is shipped as one number and nobody can reproduce it	likely x medium	CQ2 forbids emitting MI without naming its variant. Three published formulas disagree on the comment coefficient and one drops the term entirely, so the same code scores three different values under the same metric name.
The base-class ratchet is read as a mandate and 2801 gates get mechanically migrated	possible x high	CQ5 censuses and names, it never refuses. The record already forbids the mass-rebuild reading of a large undeployed count, and a migration that drops a load-bearing conjunct has already happened once on this estate.
The hotspot reader treats the action journal as complete history	possible x medium	CQ6 must publish its horizon with every verdict. The journal starts when capture started, so anything older is invisible BY CONSTRUCTION and a silent window reads as completeness.
Publishing a floor as a score	possible x high	The ISO 5055 candidate total is a floor over a 21 percent prefix and the mutation rate is a floor bounded by budget. Both are labelled as bounds WITH their direction on the page, and CQ4 exists to remove the prefix rather than to relabel it.

Release history and work log

The worked plan, on the board. Every leg appends what it measured, landed, retracted, learned and left queued, per rung, so a crash leaves the next seat a ledger here rather than a transcript to mine. Kinds: measure, land, retract, lesson, queue. Newest last.

When	Rung	Kind	Entry
2026-09-05	CQ1	retract	CORRECTION FROM THE codeeffectiveness LANE 2026-09-05: this board's CQ1 rung and matrix row have read SHIPPED with the gate GREEN 17 of 17 since 2026-08-20, while nx_catalog on the serving tree read nx_mccabe and nx_mccabe_gate SOURCE-ONLY the whole time -- the claim was true of a laptop build and unbacked on the surface that runs. Closed on the serving tree today: nx_mccabe BUILT through /api/build (36760 B sha e2526b1a, src_path confirmed), PROMOTED prev=1, REGISTERED, _offc twin installed, and re-measured full population (19467 files, 112258 funcs, above-10 14247 = 126 permille, p50=3 p90=13 p99=46, partition sums exactly). nx_mccabe_gate build is QUEUED as BQ-nx_mccabe_gate behind the I/O storm, so the gate-GREEN half of the claim stays UNBACKED on the NAS until it fires. This is the motivating case for codeeffectiveness rung CE4: bind every SHIPPED claim to a live catalog or gate verdict rather than prose.
2026-09-05	CQ1	land	CORRECTION CLOSED (2026-09-05, codeeffectiveness lane): nx_mccabe_gate is now BUILT, PROMOTED and REGISTERED on the serving tree and returns GREEN 17 of 17 against the promoted nx_mccabe, so the SHIPPED-with-gate-GREEN claim this rung has carried since 2026-08-20 is finally true where it runs. Fresh full-population census the same day: 19467 files, 112258 functions, above-10 14247 = 126 permille, p50 3 p90 13 p99 46 max 2996, partition sums; against the 2026-08-20 figures (103733 functions, 121 permille, p90 12, p99 43) complexity is RISING on every percentile.
2026-09-05	CQ12	land	operator 2026-09-05 (your magic numbers everywhere until you make the estate truly intelligent): nx_magic apply used to name every hoisted literal <PFX>_MAGIC_<value>, a placeholder that restates the value; the seat then renamed by hand, once, in one file. The resolver now lives in nx_magic_lib (mg_names_load, mg_ctx_window, mg_ctx_has, mg_name_lookup) over knowledge/magic_names.conf (67 seed rows: the character bytes, the JSON separators as written by wc, the digit base, I64_BYTES beside BITS_PER_BYTE discriminated by the operator beside the 8, MODE_0644 and MODE_0755, PERMIL and PERCENT and DECIMAL, the mmap reserves, the HTTP statuses); nx_magic resolves each site once, dedupes consts by name, prints name_src per row and names_conf, names_rows and named_sites in every envelope; a mechanical const keeps its NX-UNNAMED marker and a table-named one carries NX-NAMED; nx_magic_gate 34 to 51 teeth GREEN on the NAS (first-row-wins, the star row, one value two names, an unlisted value, an absent conf, the centred long-line window)
2026-09-05	CQ12	measure	/api/build nx_magic after the seven resolver edits returned BUILT 40062 B sha baba2a4d with src_sha256 34e87b83 (the NEW source) -- and the staged artifact carried ZERO of the new strings (nx_txtscan count name_src = 0; nx_contentdiff vs live: 86 runs both sides, one allocator message swapped, nothing gained): the third sighting today of /api/build serving a pre-edit artifact for a changed source. Remedy taken as documented: a real provenance comment appended to the source so the closure key cannot match the fossil, then rebuilt; the receipt's src_sha256 is NOT evidence the bytes are fresh -- only a string the new source alone can carry is
2026-09-05	CQ12	land	NAS: after the cache-key bump /api/build nx_magic BUILT 56120 B sha 6c1fa169 (the stage now carries name_src x4); nx_contentdiff vs live 40039 B: 3 runs lost, every one named and superseded (the allocator-lib contention message swapped for its newer twin, the old propose note replaced by the name_src note, the NX-UNNAMED marker reworded to point at the table) against 80 gained; /api/promote accepted it inside its calibrated band without the loss flag, PROMOTED prev=1; nx_magic_gate 51 of 51 GREEN on the NAS through nx_job_run; nx_offc_install refreshed the runner twin
2026-09-05	CQ12	measure	FIRST DOGFOOD on the promoted nx_magic, nx_swcompare_lib.nx at threshold 2: 379 sites over 49 distinct values became 57 distinct NAMES (the one-value-two-names split fired live: 48 as RV_CH_ZERO x2 beside RV_DIGIT_BASE x3, 10 as RV_CH_LF x11 beside RV_DECIMAL x2), names_rows=64, named_sites=187 of 379 (493 permil) with RV_CH_COMMA x95, RV_CH_COLON x13, the brackets x8 each and RV_I64_PAIR x5 named from the table; the mechanical residue named its own next rows (the JSON and HTML writers spell bytes as wc(fd, N): 34, 92, 32, 35, 60, 62) and 13 rows were added to the conf as DATA, no rebuild -- the second run measures the gain
2026-09-05	CQ12	measure	SECOND DOGFOOD after 13 conf rows landed as DATA (no rebuild): same file, same 379 sites, names_rows=77, named_sites 187 to 201 (493 to 530 permil); the writers' bytes now read RV_CH_QUOTE, RV_CH_BACKSLASH, RV_CH_SPACE, RV_CH_HASH, RV_CH_LBRACE, RV_CH_RBRACE; the residue is organ-specific (RV_MAGIC_2 x59 as the halves and pairs of this lib, 4 x20, 3 x14, 5 x14, 700 and 999 and 600 as this lib's own thresholds) and is the owner's naming, which the note in every envelope now asks for by pointing at the table
2026-09-05	CQ12	retract	the measure row above named the wrong mechanism: the 40062 B stage was NOT a build-cache hit and the provenance comment was NOT the fix -- the sovereignty lane measured the true cause the same evening (nx_hostctl cmd_buildrun staged the PREVIOUS artifact after the builder refused, a false-green BUILT, third occurrence) and DEPLOYED the root fix (hostctl ab32babd via /api/deploy); this seat's second build simply ran after the refusal cleared. The receipt-level lesson stands: a BUILT receipt with a fresh src_sha256 is not evidence the bytes are fresh; only a string the new source alone carries is
2026-09-05	CQ12	measure	ON THE LIVE SURFACE: the regen launched after the CQ12 rows landed republished /compare/codequality at 106941 B (from 98876) and the docroot page carries the CQ12 matrix row and plan rung (nx_txtscan count of the row label = 2); nx_compare_rank codequality reads 13 rungs, done=3, CQ12 counted done because its symbol resolves in the matrix row; referee grade and operator ACCEPT row still owed before the rung reads complete
2026-09-05	CQ12	retract	EVIDENCE REFEREE RUN 2026-09-05 on codequality read grounded=14 ungrounded=1 verdict=RED, failing conjunct grounded: the Proof-carrying change row named symbol cd_contains in runtime/nx_contentdiff.nx and that symbol does not exist in the organ (its functions are cd_slurp, cd_show_other, cd_show_gained, cd_show_lost and main) -- a published EXCEED claim whose symbol was absent from the organ its own row names, standing since the board was admitted. Corrected as DATA: the row now names cd_show_lost, the function that NAMES each lost run, which is exactly the capability the row claims; the referee re-run is the acceptance. Same pass: codequality.gates created (nx_magic_gate 51 of 51 on the NAS), ref cwe547 mirrored and pinned (93193 B, h369b05d6) and cited inline on the CQ12 row
2026-09-06	CQ13	queue	FLAGGED 2026-09-05 from the gameengine lane; the compiler instance is being fixed there (lang LN60, count_global_tokens in nx_parse.nx) and this rung owns the estate-wide census + ratchet. Instruments to compose, never re-implement: nx_magic map/propose (literal sites), nx_law_warden countfile, nx_unwired (the name-set ratchet shape), nx_absent for the whole-population walk; the new judgement is the provenance class of a const, which none of them measures today

On these two registers. Rows are declared in the domain's plan file and carry the debt id, which is the join key back to the sovereign debt plane — that plane, not this page, is the authority on state. Reconciling them automatically (the regen reading the plane and refreshing these rows) is a named, owed rung; until it lands, treat an id here as a pointer to look up, not a status to trust.

Honest verdict. Honest position. We are at or beyond the field on proof-carrying change and on structural coupling, and materially behind it on complexity measurement and on the OO metric family. The strong side is measured, not asserted: the import graph is fully acyclic (nontrivial SCCs 0, organs-inside-cycles 0 -- the Acyclic Dependencies Principle satisfied outright, where Linux tolerates within-subsystem cycles), propagation cost 0.4% against published Linux 5-18 percent and Mozilla ~17 percent on the same MacCormack instrument [martin94], the cursor-sentinel lint re-measures to 0 hits over 18,681 sources, and every promotion passes a capability-loss diff that names each lost run -- a proof obligation no named competitor imposes, and the closest thing in the field to a fitness function that can refuse a deploy [fitnessfn]. The weak side is equally measured and is not a tooling gap we can wave away. There is no complexity instrument at all: `nx_capsearch` returns no organ for cyclomatic complexity, and our own ISO 5055 scanner declares the hole itself -- `covered_of_4 = 3` with `gap: Maintainability -- needs cyclomatic/Halstead complexity, filed seq251` [iso25010]. That filing is the single highest-value contract on this board: the estate's own standard-conformance organ named the exact gap and nobody built it. Base-class adoption is 10.8% -- 338 of 3,139 gate sources inherit the shared verdict base, and 2,801 are hand-rolled and therefore UNMEASURED by the two laws that only apply to inheritors. The security position is a floor, not a score: the ISO 5055 scanner implements 5 of roughly 140 rules and scanned 4,000 of 18,802 organs, declaring `truncated 1` -- so its 19,144 candidates are a lower bound over a 21 percent prefix, and its own honesty field says absence of findings is not proof of absence [cwe_top25]. And one number here is a correction of our own record, published rather than quietly replaced: the standing baseline of 7 gates satisfying all three gate laws now reads 98, but almost all of that movement is the DETECTOR learning to credit idioms it used to falsely accuse (the census now itemises return-via-a-name at 1,069), not 91 gates being fixed. A delta whose cause is not published reads as progress that never happened.

Person · product · place — not yet measured for this domain

Every compare carries this layer. Declare knowledge/compare/codequality.ppp (rows surface|nishi or c1..c4|label|url|connect naming OUR live surface and each rival's front door), run nx_ppp_probe domain codequality, and this section fills itself on the next beat: the same ruler on both sides — privacy and CX (third-party hosts, tracker classes, cookies, security headers), design and longevity (design hygiene, computed WCAG contrast, render-blocking resources, unsized media, script weight, theme and motion queries), findability (landmarks, skip link, on-site search, breadcrumb, headings, internal links).

The field — discovered, not chosen

Rows written by nx_field_discover from codequality.seeds: the industry's own lists (Wikipedia wikitext, GitHub topics, awesome lists) read mechanically, every candidate counted across seeds. The matrix columns above are a SEAT'S pick; this band is the population they were picked from, and the stats line measures one against the other. A rival here is a lead, never a verdict — it earns a column when its capabilities are read and pinned.

Discovery receipt. One row per counter the run wrote, in the receipt's own order; the rival rows follow in their own table.

Field discovery, counted
Class	Count	Note
seeds	2
scanned	2
fetched	2
reused	0
failed	0
named	2
candidates	2
mentions	2
capped	0

Rank	Rival	Seeds	Mentions	First seed	Kind	Link
1	SonarQube	1	1	col0-sonarqube	named	https://docs.sonarsource.com/sonarqube-server/user-guide/code-metrics/metrics-definition.md
2	PIT	1	1	col3-pit	named	https://pitest.org/

Exclusive and shared capabilities

One capability is graded on one board; every other board references it. The fleet duplicate census (nx_rivalcensus dupes, on the fleetdupes clock row) reads every board's matrix and names each capability graded as a row on two or more boards, with a home derived from evidence: rung when exactly one board's plan contracts the symbol (that board is starred), gates when no plan contracts it and exactly one board's executed gate map runs the organ's gate (that board is plussed), ambiguous when several boards carry the deciding evidence (a decision for their seats), and none when no evidence decides it, with the reason beside it: unmapped (no board of the duplicate declares a gates map; declare the maps) or unproven (a map exists and runs none of the organ's gates; gate the organ on its proving board, or declare it a shared library by policy). A home elsewhere means this board should carry an @xrow reference to the home board's row rather than a graded row of its own; a home here means the other boards should. The table is this board's slice of one estate-wide census: the shape is shared, the rows are the board's.

This board grades 24 capabilities: 18 exclusive to it and 6 shared with other boards. Shared rows on this page: 6 = home here 0 + home elsewhere 1 + ambiguous 1 + undecided 4 + refused 0 (partition 6); undecided = unmapped 0 + unproven 4 + unevidenced 0; homonyms 0; since the previous census: new 0, resolved 0. Census FRESH age_s=6739.

Capability	Organ	Boards grading it	Home	Rule	Evidence	Standing on this board
cd_show_lost	`nx_contentdiff.nx`	devmgmt, codequality, autodev, capregistry, codeeffectiveness	—	none	unproven	undecided
gb_try	`nx_gate_bite.nx`	devmgmt+, codequality, autodev*, codeeffectiveness	autodev	rung	plan	home elsewhere adopt: `@xrow autodev\|gb_try\|home by rung (fleet duplicate census)`
uw_defcomplete	`nx_unwired.nx`	codequality, failmodes	—	none	unproven	undecided
gl_strip	`nx_gatelaw_gate.nx`	codequality, codeeffectiveness	—	none	unproven	undecided
gv_verdict	`nx_gate_verdict.nx`	codequality, extllm	—	none	unproven	undecided
fg_trend	`nx_forkgrade.nx`	codequality, codeeffectiveness	—	ambiguous	plan	ambiguous

Gaps from the record — what the estate does that no board carries

The record census (nx_goalmap record) reads the invoked-tool population and every plan queue row and files each organ or directive that NO matrix, plan or gates row names. A row here is a callout the boards missed: adjudicate it onto a board or declare it infrastructure. Census state STALE (age 1395844 s), sources read 4 of 7 declared — a BLIND census is a FLOOR: unread sources can only add rows.

kind	name	board	source	evidence

rows shown 0|this board's directives 0|estate-wide un-boarded organs 452 (listed in full on /compare/ecosystem)|census rows 639|malformed 0 (counted, never rendered)

References

Beyond a link list. Every reference below resolves twice — the publisher's copy and, where banked, the estate's own non-rottable library mirror with a content pin — and carries its evidence class plus the exact claim on this page it grounds. Keyed marks like [key] in the matrix notes jump here. A dash means honestly absent, never assumed.

[iso25010] ISO/IEC 25010:2023 Systems and software engineering - SQuaRE - System and software quality models. Second edition 2023-11 prepared by ISO/IEC JTC 1 SC 7. Cancels and replaces ISO/IEC 25010:2011. Nine characteristics. publisher · read in our library knowledge/fetched/cmp_codequality_iso25010.pdf · pin hc1a03cdcf53541c97006d8919007e979fc0c526bafeeaa4cc2e413dbb8599974 · accessed 2026-08-20 · published-standardGrounds: ISO 5055 automated source-code quality measures
[mccabe76] McCabe T.J. A Complexity Measure. IEEE Transactions on Software Engineering vol SE-2 no 4 December 1976 pp 308-320. Definition 1 gives v(G) = e - n + p and the limit of 10 is called reasonable but not magical. publisher · accessed 2026-08-20 · published-paperGrounds: Cyclomatic complexity per function (McCabe)
[nist500235] Watson A.H. and McCabe T.J. Structured Testing - A Testing Methodology Using the Cyclomatic Complexity Metric. NIST Special Publication 500-235 August 1996 119 pages. Adds essential complexity ev(G) and module design complexity iv(G). publisher · read in our library knowledge/fetched/cmp_codequality_nist500235.pdf · pin h1a29f1350d19b16426f90f47d595c11d0102f06bd7703e6e85e7c6c3694a9e73 · accessed 2026-08-20 · published-standardGrounds: Cyclomatic complexity per function (McCabe)
[mi_contested] Kuipers T. and Visser J. Maintainability Index Revisited - position paper. Software Improvement Group and Universidade do Minho. SQM 2007 workshop at CSMR 2007. Shows the MI is a regression fit and that averaging cyclomatic complexity hides the power-law outliers. publisher · accessed 2026-08-20 · published-paperGrounds: Halstead volume and Maintainability Index
[ck94] Chidamber S.R. and Kemerer C.F. A Metrics Suite for Object Oriented Design. IEEE Transactions on Software Engineering vol 20 no 6 1994 pp 476-493. Defines WMC DIT NOC CBO RFC and LCOM over an assumed-full inheritance tree. publisher · read in our library knowledge/fetched/cmp_codequality_ck94.pdf · pin h42f3352655ed330f7375400d98c46f749131cd4fe204ece2675f45bc3fb1874b · accessed 2026-08-20 · published-paperGrounds: Chidamber-Kemerer OO suite WMC DIT NOC CBO RFC LCOM
[martin94] Martin Robert C. OO Design Quality Metrics - An Analysis of Dependencies. October 28 1994 Object Mentor. Defines Ca Ce instability I = Ce/(Ca+Ce) abstractness A and distance D over CLASS CATEGORIES not classes. publisher · read in our library knowledge/fetched/cmp_codequality_martin94.pdf · pin h62a9f2d3450ab6145ff8d23be166d6beb574930cc9e98b704b6a41627b78c46e · accessed 2026-08-20 · published-paperGrounds: Afferent and efferent coupling with instability I
[sonarqube_debt] SonarSource. Understanding measures and metrics - SonarQube Server documentation. Defines sqale_debt_ratio against a default cost to develop one line of code of 30 minutes and the A to E maintainability grid at 5 10 20 and 50 percent. publisher · read in our library knowledge/fetched/cmp_codequality_sonarqube_debt.md · pin h9a518866ffba965ff238c87bb43541ec3667ef759544065242a57b49e075e816 · accessed 2026-08-20 · vendor-docGrounds: Technical debt ratio and the A-E maintainability rating
[codered22] Tornhill Adam and Borg Markus. Code Red - The Business Impact of Code Quality - A Quantitative Study of 39 Proprietary Production Codebases. arXiv 2203.04374 2022. Code Health 1.0 to 10.0 with cut-offs at 8.0 and 4.0 over 30737 files. publisher · read in our library knowledge/fetched/cmp_codequality_codered22.html · pin h21559ccffd891c13641aadd33eeea1731172ec4d0de62e96731bde1435547262 · accessed 2026-08-20 · published-paperGrounds: Behavioural code analysis: hotspots and change coupling
[connascence] connascence.io. The connascence taxonomy - five static forms Name Type Meaning Position Algorithm and four dynamic forms Execution Timing Value Identity - graded on the three axes strength locality and degree. publisher · read in our library knowledge/fetched/cmp_codequality_connascence.html · pin hcde9d7db2b79f56e2c7a857080a0e218b5754f19ae350d20259193dd2f354fd0 · accessed 2026-08-20 · source-readGrounds: Connascence as the coupling vocabulary
[pitest] PIT Mutation Testing - Real world mutation testing. Mutation score is the percentage of seeded faults killed by the suite and line coverage does not check that tests can detect faults in the executed code. publisher · read in our library knowledge/fetched/cmp_codequality_pitest.html · pin hb0c7e0505c51c95b596060ef27babbce08e72d5aaf4557eb002c2637d2bf10cc · accessed 2026-08-20 · vendor-docGrounds: Mutation score as the test-quality standard
[cwe_top25] MITRE. 2025 CWE Top 25 Most Dangerous Software Weaknesses. Scored over 39080 CVE records published between June 2024 and June 2025 as normalized frequency times normalized average CVSS. CWE-79 leads at 60.38. publisher · read in our library knowledge/fetched/cmp_codequality_cwe_top25.html · pin ha2a19f8005c1d3fd26fbdea65b6771c1d81b87281303fdec522512154b85de68 · accessed 2026-08-20 · published-standardGrounds: Weakness classes: CWE Top 25 and OWASP Top 10
[owasp_top10] OWASP Top 10:2025 - the eighth installment and the current released edition. Ranked by incidence across data donated for over 2.8 million applications and explicitly ignoring how many times a weakness occurs within one application. publisher · read in our library knowledge/fetched/cmp_codequality_owasp_top10.html · pin h37db8253029a5a6afd4f8383cda997a0a482e45766110591bf8f5a3b0d423857 · accessed 2026-08-20 · published-standardGrounds: Weakness classes: CWE Top 25 and OWASP Top 10
[fitnessfn] Thoughtworks Technology Radar. Architectural fitness function - Trial ring November 2017. An architectural fitness function provides an objective integrity assessment of some architectural characteristic and may encompass existing verification criteria. publisher · read in our library knowledge/fetched/cmp_codequality_fitnessfn.html · pin hb0101000c0205262537de4c7b2ab35ae60f8c3a8c30202b6599819a0bbb7b986 · accessed 2026-08-20 · vendor-docGrounds: Architecture fitness functions in the delivery path
[gitclear26] GitClear. The Maintainability Gap - 2026 AI Code Quality Research. Over 623 million analyzed changes 2023 to 2026 showing block duplication up 81 percent and refactored lines falling from 21 percent to 3.8 percent. publisher · read in our library knowledge/fetched/cmp_codequality_gitclear26.html · pin he0e722a8a2ded2c8fed645627262b882e8cf62ab8417d2669fef4adff7e20351 · accessed 2026-08-20 · datasetGrounds: AI-generated code quality: duplication and refactor trend
[cwe547] MITRE Corporation. CWE-547: Use of Hard-coded, Security-relevant Constants. Common Weakness Enumeration, read 2026-09-05: a program uses hard-coded constants instead of symbolic names, so a change to one value must be found and repeated at every site -- the weakness class rule 11 and the purpose-name table close publisher · read in our library knowledge/fetched/cmp_codequality_cwe547.html · pin h369b05d6a32041dc73a238874e91966d70c52c2f20d98818775d2ad9ecfe3345 · accessed 2026-09-05 · published-standardGrounds: Purpose names for literals: a table names a literal by value AND context, the tool applies the name and marks every one it could not name

generated by nx_swcompare_matrix (sovereign NishiLang organ) from knowledge/compare/codequality.matrix · source checks show implementation presence; runtime and user-outcome evidence are reported separately · JavaScript supports page controls