Nishi Family › Compare › Nishi Development Record

Nishi Compare · capabilities, evidence and delivery

Nishi Development Record

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

The development record itself -- every tool call, measurement, refusal and resume point captured, mined and proven -- versus a field that versions outcomes (git), operations (jj), or delivery exhaust (DORA platforms). pmdash selects the work; devmgmt records how it was done and turns that record into intelligence. Rows scored from the Aug-2026 four-lane research pass; grounds in devmgmt.refs.

Overview

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

Where we are. Shipped and measured: the transcript parser lane (ch_frames, ch_delta, ch_ingest, ch_gauge_json over 869 files and 2.39 GB), action-journal workflow mining (al_mine_json), trajectory scanning (tj_core), workstream lifecycle (wm_mine_json), DORA from sovereign planes (d_band_deploy), gate-outcome mining (hm_mine_json), sovereign VCS push (sgp_walk, drift-AHEAD -- never promote), proof-carrying change (cd_show_lost), mutation-proven gates (gb_try), the drift census (ps_judge), the one-call ship loop with its durable journal (os_jrnl), content CAS on the shared tree (fsw_expect_val) and seat metering (st_boot). Open: the record is laptop-local and unmineable from the estate, and crash-resume mapping, lost-set mining and crash-write adjudication were each done BY HAND on 2026-08-19 -- twice for the resume map. SHIPPED SINCE, 2026-08-20: DM2 st_resume_map, and DM5 ps_owner_scan with the owner-signal axis (DECLARED, IN-FLIGHT-SUSPECT, UNDECLARED, SRC-UNRESOLVED) plus a declaration surface a seat writes when it builds without promoting, gate-proven 23 teeth and bite-proven in both directions against the pre-change binary. Corrected in the same pass on a sibling seat evidence: the drift census compares against the LAST BUILD ANYBODY RAN, so a BEHIND delta measured on a reference older than its source can be exactly inverted -- REF-FRESH, REF-FOSSIL and REF-UNKNOWN now qualify every BEHIND row, promote_considerable requires UNDECLARED and REF-FRESH together, and the unqualified promote-the-fix label is gone. SHIPPED 2026-08-20 second pass, in the ranker's order: DM3 rm_lostset, DM7 dc_adopt_delta, DM6 d_ship_join and DM8 os_doc_stage, each with an end-to-end gate that forks the DEPLOYED subject (nx_lostset_gate 26 teeth, nx_adoptdelta_gate 28, nx_shipjoin_gate 20, nx_docstage_gate 29), every one bite-proven in BOTH directions -- a mutant that fires on nothing and a mutant that fires on everything -- and every subject restored byte-identical afterwards. DM3 re-derives the 18-row 2026-08-19 lost set from the captured record with zero hand-mining: all 18 exec counts reproduce EXACTLY and 17 of 18 last-seen timestamps match to the minute (the 18th differs by 34 seconds because this miner stamps the RESULT record, where exec_meta actually lives, rather than the call), and the single row still LOST is nx_cc_equiv_staged, precisely the row the hand-mine flagged as unsafe to re-register. DM6 matches an INDEPENDENT hand count on every field over one week of organ_ship.jrnl: ships 40, builds 57, per_week_x100 13267, matched 40, unmatched 0, mean 43s, min 0, max 280. DM8 measured the four contract symbols this session shipped as DOCUMENTED with file and line named, and three internal helpers as UNDOCUMENTED, zero false DOCUMENTED. HORIZON, stated because it is part of the claim: DM3's evidence half is laptop-local by necessity -- exec_meta exists only in the client session transcripts (899 files, 2.36 GB, 869,819 records scanned in 26s), and the NAS capture frames carry the tool NAME but a CONSTANT verb and outcome column, so they cannot answer this question. Transcripts are also not immutable: the hand-mine saw 1,139 files where 899 remain.

Where we need to go. The development record itself -- every tool call, measurement, refusal and resume point -- is captured to the estate, mined by standing organs, and drives the ranker. The field versions outcomes [git-object-model], operations [jj-oplog], or delivery exhaust [devlake-dora]; nobody researched ingests session records as primary evidence, does crash-to-multi-seat resume maps, or coordinates concurrent agent writes. Exceed by making the record the first-class object: capture (DM1), resume (DM2), reconcile (DM3, DM4), guard (DM5), and measure delivery from receipts (DM6).

The unit. 1 u = one measured session-leg (organ + gate + live flip), the pmdash/charsim calibration.
Delivery efficiency is measured from completed outcomes: Extend DM6; crosslink toolchain, deploy and engineshift. Measure cold, unchanged and incremental builds on fixed source/toolchain/host identities, separating queue, execution, verification and publication time. Extend ship-receipt measurements with failed-deployment recovery time, change-failure rate and deployment-rework rate beside lead time and deployment frequency. Report retries, interventions and total cost per verified result; compare like workloads and preserve failures. No faster-build or frontier claim follows from gate count, source presence or a single successful run. Candidate primary benchmark inputs externally retrieved 2026-09-07, not estate-pinned: https://dora.dev/guides/dora-metrics/ and https://bazel.build/remote/caching .

Latest recorded release

2026-09-05 · DM12

FIX TWO LIVE: nx_organ_ship c862f05f PROMOTED (allow_loss=1 for the vanished symbol string osl_should_rebuild_prov, which the program no longer references), gate REBUILT 56/56 GREEN with T51-T56: osl_should_rebuild_pick(gate, target, clo, prov, pick) lets a CURRENT bank veto the import scan's rebuild ONLY when the banked artifact is on disk and is the one PROVE runs (KEEP or SWITCH_B); an UNPROVEN pick (banked artifact gone) leaves the incumbent rebuild standing (neg-control T53); os_gate_freshen computes the pick BEFORE the decision. T39 (a bank alone never vetoes) deliberately kept true of osl_should_rebuild_prov. The rung's own receipt was the measurement: the loop that shipped fix two was the fix-one binary, so it still rebuilt past a CURRENT bank once more; the next ship through c862f05f runs the banked artifact without a compile.

Release history and work log

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

27 of 28 capability source symbols found|0 of them authored stronger-claims|1 open|coverage 964/1000|adoption 14 full / 13 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.

evidence|grounded 25/25|unsupported 0|gates green 3/3|proven able to fail 2/3|never bitten 1|green at 0/0 0|open gaps 1|of them unnamed 0|of them proof withheld 0|flips ready 8

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 = 25 vs present 25 · named + unnamed + withheld = 1 vs open 1 · both reconcile

liar-kill conj=GPQN · all four conjuncts held

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

Gap classWhat it is, and the work it names
FLIP-READYA watch contract symbol is now present in the organ it named: the cell can flip on a pure data edit with no new code. These are the cheapest closures on this board and they belong before any new work.
STALEThis 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 devmgmt 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=1790081933 domain=devmgmt target_version=2.2 rungs=12 done=10 open=2 finish=5 ranker=nx_dr_ocm

#StageRungPriorityDerivation
FFINISHSession-to-NAS capture beat (DM1) ch_beat dossierREGISTERED-DARKcallable, 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); only referenced by nx_claude_harvest_gate -- a mention, not a run
FFINISHLost-set miner (DM3) rm_lostset dossierREGISTERED-DARKcallable, 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); only referenced by nx_lostset_gate -- a mention, not a run
FFINISHCrash-write adjudicator (DM4) ap_landed dossierREGISTERED-DARKcallable, 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); only referenced by nx_atomic_publish_gate -- a mention, not a run
FFINISHDORA on ship receipts (DM6) d_ship_join dossierREGISTERED-DARKcallable, 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); only referenced by nx_shipjoin_gate -- a mention, not a run
FFINISHA citation lands as one publish (DM11) cc_publish dossierREGISTERED-UNAUTHORISEDregistered, no cap ever minted; no execution surface runs it either (clock, cron, daemon, roster, actlog and surfaced forks checked)
#12.2Shell-gap census as a verb on the capture beat (DM10) ch_shellgap dossier400v=2 m=2 c=10
#2laterThe proof runs the artifact the bank vouches for (DM12) osl_pick_banked dossier0v=0 m=2 c=5

Declared roadmap — contract, acceptance, executor, effort

RungCloses withDefinition of done (pre-declared)ExecutorEst.
Session-to-NAS capture beat (DM1)ch_beatA clock row delta-harvests every laptop transcript (ch_delta) and lands frames in a NAS journal; the gauge runs NAS-side over the captured frames. The parser, delta and idempotent ingest already exist -- this rung is composition plus cadence, not a new parserOrgan1 u
Crash-resume map (DM2)
after DM1		st_resume_mapOne call after a crash emits a per-seat lane, last-action, in-flight and resume-point map, validated against the hand-mined 2026-08-19 map (7 seats, both crashes)Organ1 u
Lost-set miner (DM3)
after DM1		rm_lostsetRe-derives the 18-row 2026-08-19 lost set (knowledge/status/toolrows_lostset_20260819.txt) from the captured record with zero hand-mining, exec evidence reconciled against the registryOrgan1 u
Crash-write adjudicator (DM4)ap_landedGiven the 2026-08-19 in-flight write list, emits LANDED or NOT per row matching the hand adjudication with zero false LANDED -- wrong only toward NOTOrgan0.5 u
Owner-scan on BEHIND (DM5)ps_owner_scanEvery BEHIND worklist row carries an owner signal before any promote list publishes; a replay fixture of the nx_oo_extract_gate case is detectedOrgan0.5 u
DORA on ship receipts (DM6)d_ship_joinDeploy-frequency and lead-time computed from organ_ship.jrnl match a hand count over one week of journalOrgan1 u

Milestones

MilestoneRungsCumulative
D0 · Capture and resumeDM1,DM22 u
D1 · NAS-mineable full recordDM3,DM43.5 u
RungCloses withDefinition of done (pre-declared)ExecutorEst.
Adoption-delta emitter (DM7)
after DM5		dc_adopt_deltaReads the daily artifactdrift.log and nx_catalog output and emits the per-class adoption delta, COMPOSING census outputs already written to disk rather than running a new census. Extends nx_deltaclass_lib, whose ledger reader already separates DELIVERED from SCOPE-MOVED from THRASH, so this is a second reader of an old log and adds no new collector and no new load [devlake-dora]. ACCEPT: two consecutive beats emit deltas whose arithmetic reconciles against the underlying logs, and any row whose reference is REF-FOSSIL is excluded from the promotable delta rather than counted in itOrgan1 u
Documentation-adoption stage (DM8)
after DM5		os_doc_stageA shipped symbol must appear in a compare matrix, plan or watch row, or carry a memory pointer. REPORT-ONLY first: a pre-flight that can refuse will be disabled, while one that only informs survives [claude-code-sessions]. WATCH CONTRACT ONLY -- nx_organ_ship is another lane source and this rung licenses no edit to it. ACCEPT: the stage reports DOCUMENTED or UNDOCUMENTED per ship with ZERO false DOCUMENTED, measured against the symbols a session actually shippedOrgan1 u

Milestones

MilestoneRungsCumulative
D2 · The record drives the intelligence loopDM5,DM6,DM7,DM87 u
RungCloses withDefinition of done (pre-declared)ExecutorEst.
Three-party acceptance ledger (DM9)acm_emitCOMPLETE on /compare is derived, never declared: nx_accept emit regenerates runtime/nx_accept_decl.nx from knowledge/store/accept- (the operator) plus referee- (the cjc_panel percept lens, RUN on a full-resolution capture, never typed) plus attest- (the shipping seat), one ga_accept_SUBJECT declaration per subject that carries all three signatures, sorted, no timestamp, byte-identical while the planes are unchanged; every ACCEPTANCE watch row names that file and flips only through it, and a NOT-AGREED always names the missing party (OPERATOR-MISSING or OPERATOR-REJECT, REFEREE-MISSING or REFEREE-BELOW-BAND or REFEREE-TIER-UNADMITTED, SEAT-MISSING). ACCEPT: nx_accept_gate GREEN over /tmp fixture planes (accept-after-reject restores, reject-after-accept revokes, GOOD below the floor is not agreed, a non-operator ACCEPT does not sign, emit idempotent and exactly the agreed set, a hand-added declaration convicted, no verb writes accept-), bite-proven in subject mode, and the live emit UNCHANGED on its second runOrgan1 u

Milestones

MilestoneRungsCumulative
D3 · Completion is three-party agreementDM91 u
RungCloses withDefinition of done (pre-declared)ExecutorEst.
Shell-gap census as a verb on the capture beat (DM10)
after DM1		ch_shellgapnx_claude_harvest gains a shellgap verb that classifies every Bash and PowerShell frame by the sovereign capability it stands in for (MCP-RAW-LANE with the tool name, SSH with the remote verb, PYTHON with the script, WEB with the host, LAPTOP-ORGAN with the organ, LOCAL-FILE-OPS) and publishes the partition with a weekly outside_permil beside ch_gauge_json, so the worklist is a beat not a hand run. MEASURED 2026-09-02 by a declared break-glass scan (knowledge/status/shellgap_census.txt): 240588 frames, MCP-RAW-LANE 15647 of which 14620 in MCP-live sessions = a cap gap closed the same day by a seat-wide 30-day cap; SSH 5202 led by builds over ssh 466 and scp 268; PYTHON 5947; WEB 11044. ACCEPT: the verb reproduces that census's partition on the same corpus with sum equal to frames, and a planted frame lands in exactly one classOrgan1 u

Milestones

MilestoneRungsCumulative
D4 · The record names its own gapsDM101 u
RungCloses withDefinition of done (pre-declared)ExecutorEst.
A citation lands as one publish (DM11)
after DM10		cc_publishSOURCE-LANDED 2026-09-02: nx_compare_cite writes the ref row (pin computed from the mirror) and the inline mark on exactly one matched row under one compare-and-swap publish each, refs first, idempotent. Done when nx_compare_cite_gate proves the receipt, the computed pin, the mark placement, idempotence, and the four refusals (absent mirror, row not found, ambiguous label, pipe in prose) leave both files byte-identicalOrgan0.5 u
The proof runs the artifact the bank vouches for (DM12)
after DM8		osl_pick_bankedGATE-VINTAGE and PROVE must name the SAME file: nx_provcheck reads the sidecar of the LAST BUILD (root B, buildroot/_build) while the resolver prefers the PROMOTED binary (root A) for every gate the loop did not just build, so a CURRENT bank was vouching for one artifact while PROVE ran another. Done when: on a CURRENT bank the loop runs the banked root-B artifact whenever root A differs (BANKED-BUILD-USED, journalled), reports UNPROVEN when the bank matches nothing on disk (BANK-UNMATCHED), and the import scan never forces a rebuild past a CURRENT bank; nx_organ_ship_gate proves the pure decision (T46-T50, two neg-controls) and a CONTAINS-on-CURRENT no-rebuild toothOrgan0.5 u

Milestones

MilestoneRungsCumulative
D5 · The proof names the artifact it ranDM120.5 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
ClassCountNote
bars0sotabar rows on the plan
fresh0the bar month is the current month
attested0an older bar with a this-month barscan reporting no newer entry
stale0a this-month scan saw a newer month the bar ignores
unattested0nobody looked this month
malformed0a sotabar row missing a field
duplicate0bar ids an earlier row already carries
bars, summed0RECONCILED: the parts sum to the total 0
current month2026-10the 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 12. 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 8fb3d4b188fdd6519164bd0a0c2bdb4441e25088d4661d0bb08a569e61b25d00. 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 12 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.

  1. DM1 — Session-to-NAS capture beat

    Prerequisites: None declared; this does not establish execution eligibility.

    Contract: ch_beat

    Acceptance: A clock row delta-harvests every laptop transcript (ch_delta) and lands frames in a NAS journal; the gauge runs NAS-side over the captured frames. The parser, delta and idempotent ingest already exist -- this rung is composition plus cadence, not a new parser

    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.

  2. DM2 — Crash-resume map

    Prerequisites: DM1 (acceptance unverified)

    Contract: st_resume_map

    Acceptance: One call after a crash emits a per-seat lane, last-action, in-flight and resume-point map, validated against the hand-mined 2026-08-19 map (7 seats, both crashes)

    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.

  3. DM3 — Lost-set miner

    Prerequisites: DM1 (acceptance unverified)

    Contract: rm_lostset

    Acceptance: Re-derives the 18-row 2026-08-19 lost set (knowledge/status/toolrows_lostset_20260819.txt) from the captured record with zero hand-mining, exec evidence reconciled against the registry

    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.

  4. DM4 — Crash-write adjudicator

    Prerequisites: None declared; this does not establish execution eligibility.

    Contract: ap_landed

    Acceptance: Given the 2026-08-19 in-flight write list, emits LANDED or NOT per row matching the hand adjudication with zero false LANDED -- wrong only toward NOT

    Authored effort: 0.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.

  5. DM5 — Owner-scan on BEHIND

    Prerequisites: None declared; this does not establish execution eligibility.

    Contract: ps_owner_scan

    Acceptance: Every BEHIND worklist row carries an owner signal before any promote list publishes; a replay fixture of the nx_oo_extract_gate case is detected

    Authored effort: 0.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.

  6. DM6 — DORA on ship receipts

    Prerequisites: None declared; this does not establish execution eligibility.

    Contract: d_ship_join

    Acceptance: Deploy-frequency and lead-time computed from organ_ship.jrnl match a hand count over one week of journal

    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.

  7. DM7 — Adoption-delta emitter

    Prerequisites: DM5 (acceptance unverified)

    Contract: dc_adopt_delta

    Acceptance: Reads the daily artifactdrift.log and nx_catalog output and emits the per-class adoption delta, COMPOSING census outputs already written to disk rather than running a new census. Extends nx_deltaclass_lib, whose ledger reader already separates DELIVERED from SCOPE-MOVED from THRASH, so this is a second reader of an old log and adds no new collector and no new load [@devlake-dora]. ACCEPT: two consecutive beats emit deltas whose arithmetic reconciles against the underlying logs, and any row whose reference is REF-FOSSIL is excluded from the promotable delta rather than counted in it

    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.

  8. DM8 — Documentation-adoption stage

    Prerequisites: DM5 (acceptance unverified)

    Contract: os_doc_stage

    Acceptance: A shipped symbol must appear in a compare matrix, plan or watch row, or carry a memory pointer. REPORT-ONLY first: a pre-flight that can refuse will be disabled, while one that only informs survives [@claude-code-sessions]. WATCH CONTRACT ONLY -- nx_organ_ship is another lane source and this rung licenses no edit to it. ACCEPT: the stage reports DOCUMENTED or UNDOCUMENTED per ship with ZERO false DOCUMENTED, measured against the symbols a session actually shipped

    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.

  9. DM9 — Three-party acceptance ledger

    Prerequisites: None declared; this does not establish execution eligibility.

    Contract: acm_emit

    Acceptance: COMPLETE on /compare is derived, never declared: nx_accept emit regenerates runtime/nx_accept_decl.nx from knowledge/store/accept- (the operator) plus referee- (the cjc_panel percept lens, RUN on a full-resolution capture, never typed) plus attest- (the shipping seat), one ga_accept_SUBJECT declaration per subject that carries all three signatures, sorted, no timestamp, byte-identical while the planes are unchanged; every ACCEPTANCE watch row names that file and flips only through it, and a NOT-AGREED always names the missing party (OPERATOR-MISSING or OPERATOR-REJECT, REFEREE-MISSING or REFEREE-BELOW-BAND or REFEREE-TIER-UNADMITTED, SEAT-MISSING). ACCEPT: nx_accept_gate GREEN over /tmp fixture planes (accept-after-reject restores, reject-after-accept revokes, GOOD below the floor is not agreed, a non-operator ACCEPT does not sign, emit idempotent and exactly the agreed set, a hand-added declaration convicted, no verb writes accept-), bite-proven in subject mode, and the live emit UNCHANGED on its second run

    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.

  10. DM10 — Shell-gap census as a verb on the capture beat

    Prerequisites: DM1 (acceptance unverified)

    Contract: ch_shellgap

    Acceptance: nx_claude_harvest gains a shellgap verb that classifies every Bash and PowerShell frame by the sovereign capability it stands in for (MCP-RAW-LANE with the tool name, SSH with the remote verb, PYTHON with the script, WEB with the host, LAPTOP-ORGAN with the organ, LOCAL-FILE-OPS) and publishes the partition with a weekly outside_permil beside ch_gauge_json, so the worklist is a beat not a hand run. MEASURED 2026-09-02 by a declared break-glass scan (knowledge/status/shellgap_census.txt): 240588 frames, MCP-RAW-LANE 15647 of which 14620 in MCP-live sessions = a cap gap closed the same day by a seat-wide 30-day cap; SSH 5202 led by builds over ssh 466 and scp 268; PYTHON 5947; WEB 11044. ACCEPT: the verb reproduces that census's partition on the same corpus with sum equal to frames, and a planted frame lands in exactly one class

    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.

  11. DM11 — A citation lands as one publish

    Prerequisites: DM10 (acceptance unverified)

    Contract: cc_publish

    Acceptance: SOURCE-LANDED 2026-09-02: nx_compare_cite writes the ref row (pin computed from the mirror) and the inline mark on exactly one matched row under one compare-and-swap publish each, refs first, idempotent. Done when nx_compare_cite_gate proves the receipt, the computed pin, the mark placement, idempotence, and the four refusals (absent mirror, row not found, ambiguous label, pipe in prose) leave both files byte-identical

    Authored effort: 0.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.

  12. DM12 — The proof runs the artifact the bank vouches for

    Prerequisites: DM8 (acceptance unverified)

    Contract: osl_pick_banked

    Acceptance: GATE-VINTAGE and PROVE must name the SAME file: nx_provcheck reads the sidecar of the LAST BUILD (root B, buildroot/_build) while the resolver prefers the PROMOTED binary (root A) for every gate the loop did not just build, so a CURRENT bank was vouching for one artifact while PROVE ran another. Done when: on a CURRENT bank the loop runs the banked root-B artifact whenever root A differs (BANKED-BUILD-USED, journalled), reports UNPROVEN when the bank matches nothing on disk (BANK-UNMATCHED), and the import scan never forces a rebuild past a CURRENT bank; nx_organ_ship_gate proves the pure decision (T46-T50, two neg-controls) and a CONTAINS-on-CURRENT no-rebuild tooth

    Authored effort: 0.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.

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 devmgmt 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.
DM1 Session-to-NAS capture beat · cell LANDED · gate NO-GATE-DECLARED
Contractch_beat · executor Organ · 1 u · stands on nothing
Definition of doneA clock row delta-harvests every laptop transcript (ch_delta) and lands frames in a NAS journal; the gauge runs NAS-side over the captured frames. The parser, delta and idempotent ingest already exist -- this rung is composition plus cadence, not a new parser
Matrix cellDEV: session-to-NAS capture beat · runtime/_hdl_build/nx_claude_harvest.nx · LANDED decl
GateNO-GATE-DECLARED — knowledge/organ_gate.conf carries no row for nx_claude_harvest; declare nx_claude_harvest TAB <gate> and the ship loop proves it and the verdict lands here.
Work logno log row names this rung yet
DM2 Crash-resume map · cell LANDED · gate NO-GATE-DECLARED
Contractst_resume_map · executor Organ · 1 u · stands on DM1
Definition of doneOne call after a crash emits a per-seat lane, last-action, in-flight and resume-point map, validated against the hand-mined 2026-08-19 map (7 seats, both crashes)
Matrix cellDEV: per-seat crash-resume map from transcript tails · runtime/_hdl_build/nx_seat.nx · LANDED decl
GateNO-GATE-DECLARED — knowledge/organ_gate.conf carries no row for nx_seat; declare nx_seat TAB <gate> and the ship loop proves it and the verdict lands here.
Work logno log row names this rung yet
DM3 Lost-set miner · cell LANDED · gate UNRECORDED
Contractrm_lostset · executor Organ · 1 u · stands on DM1
Definition of doneRe-derives the 18-row 2026-08-19 lost set (knowledge/status/toolrows_lostset_20260819.txt) from the captured record with zero hand-mining, exec evidence reconciled against the registry
Matrix cellDEV: exec-proven lost-set miner · runtime/_hdl_build/nx_registrymine.nx · LANDED decl
Gatenx_lostset_gate · UNRECORDED — no recorded verdict for this gate (it is declared for the organ but the evidence referee's last run did not record it: it is not on this board's gates map, or the referee has not run since the per-gate record shipped)
Work logno log row names this rung yet
DM4 Crash-write adjudicator · cell LANDED · gate NO-GATE-DECLARED
Contractap_landed · executor Organ · 0.5 u · stands on nothing
Definition of doneGiven the 2026-08-19 in-flight write list, emits LANDED or NOT per row matching the hand adjudication with zero false LANDED -- wrong only toward NOT
Matrix cellDEV: crash-write adjudicator · runtime/_hdl_build/nx_atomic_publish.nx · LANDED decl
GateNO-GATE-DECLARED — knowledge/organ_gate.conf carries no row for nx_atomic_publish; declare nx_atomic_publish TAB <gate> and the ship loop proves it and the verdict lands here.
Work logno log row names this rung yet
DM5 Owner-scan on BEHIND · cell LANDED · gate NO-GATE-DECLARED
Contractps_owner_scan · executor Organ · 0.5 u · stands on nothing
Definition of doneEvery BEHIND worklist row carries an owner signal before any promote list publishes; a replay fixture of the nx_oo_extract_gate case is detected
Matrix cellDEV: concurrent-ownership detector on BEHIND rows · runtime/nx_artifactdrift.nx · LANDED decl
GateNO-GATE-DECLARED — knowledge/organ_gate.conf carries no row for nx_artifactdrift; declare nx_artifactdrift TAB <gate> and the ship loop proves it and the verdict lands here.
Work logno log row names this rung yet
DM6 DORA on ship receipts · cell LANDED · gate NO-GATE-DECLARED
Contractd_ship_join · executor Organ · 1 u · stands on nothing
Definition of doneDeploy-frequency and lead-time computed from organ_ship.jrnl match a hand count over one week of journal
Matrix cellDEV: DORA fed by ship receipts · runtime/_hdl_build/nx_dora.nx · LANDED decl
GateNO-GATE-DECLARED — knowledge/organ_gate.conf carries no row for nx_dora; declare nx_dora TAB <gate> and the ship loop proves it and the verdict lands here.
Work logno log row names this rung yet
DM7 Adoption-delta emitter · cell LANDED · gate NO-GATE-DECLARED
Contractdc_adopt_delta · executor Organ · 1 u · stands on DM5
Definition of doneReads the daily artifactdrift.log and nx_catalog output and emits the per-class adoption delta, COMPOSING census outputs already written to disk rather than running a new census. Extends nx_deltaclass_lib, whose ledger reader already separates DELIVERED from SCOPE-MOVED from THRASH, so this is a second reader of an old log and adds no new collector and no new load [devlake-dora]. ACCEPT: two consecutive beats emit deltas whose arithmetic reconciles against the underlying logs, and any row whose reference is REF-FOSSIL is excluded from the promotable delta rather than counted in it
Matrix cellADOPT: the adoption delta as a per-class trend, never a level · runtime/_hdl_build/nx_deltaclass_lib.nx · LANDED decl
GateNO-GATE-DECLARED — knowledge/organ_gate.conf carries no row for nx_deltaclass_lib; declare nx_deltaclass_lib TAB <gate> and the ship loop proves it and the verdict lands here.
Work logno log row names this rung yet
DM8 Documentation-adoption stage · cell LANDED · gate UNRECORDED
Contractos_doc_stage · executor Organ · 1 u · stands on DM5
Definition of doneA shipped symbol must appear in a compare matrix, plan or watch row, or carry a memory pointer. REPORT-ONLY first: a pre-flight that can refuse will be disabled, while one that only informs survives [claude-code-sessions]. WATCH CONTRACT ONLY -- nx_organ_ship is another lane source and this rung licenses no edit to it. ACCEPT: the stage reports DOCUMENTED or UNDOCUMENTED per ship with ZERO false DOCUMENTED, measured against the symbols a session actually shipped
Matrix cellADOPT: documentation as a shipping stage, reported per ship · runtime/nx_organ_ship.nx · LANDED decl
Gatenx_organ_ship_gate · UNRECORDED — no recorded verdict for this gate (it is declared for the organ but the evidence referee's last run did not record it: it is not on this board's gates map, or the referee has not run since the per-gate record shipped)
nx_organ_ship_behavior_gate · UNRECORDED — no recorded verdict for this gate (it is declared for the organ but the evidence referee's last run did not record it: it is not on this board's gates map, or the referee has not run since the per-gate record shipped)
Work logno log row names this rung yet
DM9 Three-party acceptance ledger · cell PRESENT · gate UNRECORDED
Contractacm_emit · executor Organ · 1 u · stands on nothing
Definition of doneCOMPLETE on /compare is derived, never declared: nx_accept emit regenerates runtime/nx_accept_decl.nx from knowledge/store/accept- (the operator) plus referee- (the cjc_panel percept lens, RUN on a full-resolution capture, never typed) plus attest- (the shipping seat), one ga_accept_SUBJECT declaration per subject that carries all three signatures, sorted, no timestamp, byte-identical while the planes are unchanged; every ACCEPTANCE watch row names that file and flips only through it, and a NOT-AGREED always names the missing party (OPERATOR-MISSING or OPERATOR-REJECT, REFEREE-MISSING or REFEREE-BELOW-BAND or REFEREE-TIER-UNADMITTED, SEAT-MISSING). ACCEPT: nx_accept_gate GREEN over /tmp fixture planes (accept-after-reject restores, reject-after-accept revokes, GOOD below the floor is not agreed, a non-operator ACCEPT does not sign, emit idempotent and exactly the agreed set, a hand-added declaration convicted, no verb writes accept-), bite-proven in subject mode, and the live emit UNCHANGED on its second run
Matrix cellADOPT: COMPLETE on /compare is three-party agreement, derived from planes and never declared · runtime/nx_accept.nx · PRESENT decl
Gatenx_accept_gate · UNRECORDED — no recorded verdict for this gate (it is declared for the organ but the evidence referee's last run did not record it: it is not on this board's gates map, or the referee has not run since the per-gate record shipped)
Work logno log row names this rung yet
DM10 Shell-gap census as a verb on the capture beat · cell WATCHING · gate NO-GATE-DECLARED
Contractch_shellgap · executor Organ · 1 u · stands on DM1
Definition of donenx_claude_harvest gains a shellgap verb that classifies every Bash and PowerShell frame by the sovereign capability it stands in for (MCP-RAW-LANE with the tool name, SSH with the remote verb, PYTHON with the script, WEB with the host, LAPTOP-ORGAN with the organ, LOCAL-FILE-OPS) and publishes the partition with a weekly outside_permil beside ch_gauge_json, so the worklist is a beat not a hand run. MEASURED 2026-09-02 by a declared break-glass scan (knowledge/status/shellgap_census.txt): 240588 frames, MCP-RAW-LANE 15647 of which 14620 in MCP-live sessions = a cap gap closed the same day by a seat-wide 30-day cap; SSH 5202 led by builds over ssh 466 and scp 268; PYTHON 5947; WEB 11044. ACCEPT: the verb reproduces that census's partition on the same corpus with sum equal to frames, and a planted frame lands in exactly one class
Matrix cellDEV: outside-tool frames classified by CAUSE, not merely counted · runtime/_hdl_build/nx_claude_harvest.nx · WATCHING decl
GateNO-GATE-DECLARED — knowledge/organ_gate.conf carries no row for nx_claude_harvest; declare nx_claude_harvest TAB <gate> and the ship loop proves it and the verdict lands here.
Work log2026-09-03 measure THE ACCEPTANCE QUEUE WAS COMPLETE AND UNPUBLISHED, and the operator named it: "for human acceptance you need to publish a queue and evidence to review like how we have rigview but you arent anywhere". Measured 2026-09-03: nx_accept list ALREADY computes, per subject, which of the three parties is missing, and knowledge/store/accept- ALREADY holds the operator's verdicts and words. Neither has ever been rendered anywhere -- the queue existed only if you ran a CLI verb. Live ledger: subjects=5 agreed=0 not_agreed=5 planes=3/3, and the split matters -- only SKIN is missing=OPERATOR-UNJUDGED and therefore actually waiting on the operator; face, garments, hair and locomotion are the operator's own REJECTs waiting on SEATS to rework. FACE IS THE DOCTRINE WORKING, NOT A DEFECT: referee=OK with percept=214 against floor=151 while the operator REJECTed -- the machine lens cleared its bar and the human did not, which is exactly why three signatures exist. ★★★★★★A DECISION THAT REQUIRES A HUMAN AND IS NOT PUT IN FRONT OF THEM IS NOT A PENDING DECISION, IT IS A STALLED ONE -- and from the inside it is indistinguishable from the human being slow
2026-09-03 land nx_acceptview SOURCE-LANDED at 17428 B: composes nx_accept list (verdict and missing-party from the ONE classifier, nx_accept_lib) plus the accept- plane through nx_store_put's own loader, and computes NO verdict of its own -- a second opinion rendered beside the first is a duplicate ruler wearing a stylesheet. Publishes sites/nishifamily/compare/acceptance/index.html, sorted so subjects awaiting the OPERATOR come first, showing the referee's percept against its own floor and the operator's words VERBATIM through an escaper (a rejection note is free text a human typed and an angle bracket in one must never become markup on the page they decide from). Also truncate-writes knowledge/status/accept_queue.status with awaiting_operator and awaiting_seat_or_referee, verdict LAST. It REFUSES to publish an empty queue: an empty acceptance page would read as nothing awaiting review, which is the most dangerous false statement that page could make. Precedent for a page organ beside the matrix emitter is established -- nx_maturity_board, nx_rulers_page, nx_pm_page all do this
2026-09-03 queue OWED: the nx_acceptview build was refused four times by I/O admission and is ENQUEUED (rc=0); once the binary exists, declare its hourly clock row beside acceptemit and verify the page renders. NOTE THE GUARD THAT FIRED: nx_clockjob REFUSED the row while the elf was absent -- "a row whose organ does not exist is a beat that is dead the moment it is written, and it dies SILENTLY" -- so the beat is declared AFTER the binary, never before. Owed after that: a gate over the escaper and the empty-queue refusal, and a link from the devmgmt page to /compare/acceptance
DM11 A citation lands as one publish · cell PRESENT · gate NO-GATE-DECLARED
Contractcc_publish · executor Organ · 0.5 u · stands on DM10
Definition of doneSOURCE-LANDED 2026-09-02: nx_compare_cite writes the ref row (pin computed from the mirror) and the inline mark on exactly one matched row under one compare-and-swap publish each, refs first, idempotent. Done when nx_compare_cite_gate proves the receipt, the computed pin, the mark placement, idempotence, and the four refusals (absent mirror, row not found, ambiguous label, pipe in prose) leave both files byte-identical
Matrix cellDEV: a citation lands as ONE publish -- the ref row and its inline mark together, or neither · runtime/nx_compare_cite.nx · PRESENT decl
GateNO-GATE-DECLARED — knowledge/organ_gate.conf carries no row for nx_compare_cite; declare nx_compare_cite TAB <gate> and the ship loop proves it and the verdict lands here.
Work logno log row names this rung yet
DM12 The proof runs the artifact the bank vouches for · cell NO-MATRIX-ROW · gate NO-MATRIX-ROW
Contractosl_pick_banked · executor Organ · 0.5 u · stands on DM8
Definition of doneGATE-VINTAGE and PROVE must name the SAME file: nx_provcheck reads the sidecar of the LAST BUILD (root B, buildroot/_build) while the resolver prefers the PROMOTED binary (root A) for every gate the loop did not just build, so a CURRENT bank was vouching for one artifact while PROVE ran another. Done when: on a CURRENT bank the loop runs the banked root-B artifact whenever root A differs (BANKED-BUILD-USED, journalled), reports UNPROVEN when the bank matches nothing on disk (BANK-UNMATCHED), and the import scan never forces a rebuild past a CURRENT bank; nx_organ_ship_gate proves the pure decision (T46-T50, two neg-controls) and a CONTAINS-on-CURRENT no-rebuild tooth
Matrix cellNO-MATRIX-ROW — no matrix row carries osl_pick_banked; 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.
Gatethe gate join needs a matrix row: no organ is named for this rung
Work log2026-09-05 measure MEASURED 2026-09-05 on nx_janitor_caps_gate: BANK CURRENT (closure cab9f3fc), PROVE ran ./nx_janitor_caps_gate.elf = 20,695 B (the pre-migration gate, hand-rolled dialect) while buildroot/_build/nx_janitor_caps_gate.sov.elf = 30,649 B was the artifact the bank described; the receipt read vintage=FRESH-closure-bank-CURRENT about a binary the bank had never seen. Same shape one hour later on the loop's own gate: bank CURRENT, import scan demanded a rebuild anyway, admission refused it, PROVE ran the promoted 43-tooth gate while the banked 50-tooth build sat in root B, labelled STALE-gate-rebuild-REFUSED.
2026-09-05 land nx_organ_ship 43ae1d12 PROMOTED (self-ship, allow_loss=1 for the reworded NO REBUILD sentence, offc twin fresh): osl_pick_banked(resolved_root, sha_a, sha_b, b_exists) in nx_organ_ship_lib (KEEP / SWITCH_B / UNPROVEN) + os_gate_freshen switching gpath to root B on a differing digest (BANKED-BUILD-USED) or returning UNKNOWN when the bank matches nothing (BANK-UNMATCHED); nx_organ_ship_gate T46-T50 GREEN (50/50 on the rebuilt gate). OPEN in this rung: a CURRENT bank must beat the CONTAINS import scan so no compile is spent and no refusal downgrades a proven artifact to STALE.
2026-09-05 land FIX TWO LIVE: nx_organ_ship c862f05f PROMOTED (allow_loss=1 for the vanished symbol string osl_should_rebuild_prov, which the program no longer references), gate REBUILT 56/56 GREEN with T51-T56: osl_should_rebuild_pick(gate, target, clo, prov, pick) lets a CURRENT bank veto the import scan's rebuild ONLY when the banked artifact is on disk and is the one PROVE runs (KEEP or SWITCH_B); an UNPROVEN pick (banked artifact gone) leaves the incumbent rebuild standing (neg-control T53); os_gate_freshen computes the pick BEFORE the decision. T39 (a bank alone never vetoes) deliberately kept true of osl_should_rebuild_prov. The rung's own receipt was the measurement: the loop that shipped fix two was the fix-one binary, so it still rebuilt past a CURRENT bank once more; the next ship through c862f05f runs the banked artifact without a compile.
2026-09-06 land nx_sov_build_run 981d60e0 (146592 B, TOOLCHAIN-PROMOTED canary GREEN into buildroot/_offc AND promoted to the serving root, contentdiff strict superset): the build FLAVOUR now follows the incumbent. With neither --debug nor the new --release given the runner reads the serving-root twin's bytes (sbr_incumbent_flavour: the DWARF line-table section name present = debug; needle assembled from two halves so a self-rebuild cannot read its own literal) and announces FLAVOUR debug
2026-09-06 lesson a per-call build flavour that no target declares is a silent CAPLOSS generator: nx_wgsl rebuilt without --debug against a live debug binary read lost_from_live=823 (422 permil) with lost_other=0, and the runner's own first rebuild reproduced it (147 metadata-only losses, release 127373 B vs live debug 144136 B). A guard that fires on every flavour swap is a guard seats learn to pass allow_capability_loss through, which disarms it for the real regression; derive the flavour from the artifact, never make the seat remember a flag. The flavour is one more entry in the CQ13 census class (a build-shaping choice with no declared owner)

dossiers=12 cells_joined=11 no_matrix_row=1 (sum 12) gates_recorded=0 gates_unrecorded=3 no_gate_declared=8 (sum 11 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. 28 feature rows mapped of 28 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/devmgmt.cdmap (cut|x|y, cube|x|y|z); absent = the HBR defaults
Position map, two-dimensional cutOne bubble per player. Bubble area is breadth, the ring colour is momentum, the dashed lines are the category means, and both axes are fitted to the field of play with their tick numerals shown. Every value is repeated in the table that follows. 0 200 400 600 800 1000 420 440 460 480 500 520 centrality (permil, fitted 0–1000) distinctiveness (permil, fitted 420–520) mean 466 mean 459 Unconventional Aspirational Peripheral Mainstream Nishi, centrality 964, distinctiveness 493, breadth 642, depth 666, momentum 0 git, centrality 105, distinctiveness 458, breadth 59, depth 833, momentum 0 Jujutsu, centrality 350, distinctiveness 440, breadth 190, depth 761, momentum 0 Devin, centrality 385, distinctiveness 458, breadth 214, depth 750, momentum 0 Faros AI, centrality 526, distinctiveness 448, breadth 309, depth 666, momentum 0 Nishi git Jujutsu Devin Faros AI

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 420–520 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 693 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)
Position map, three-dimensional cubeThe same players in an isometric cube. Each axis is fitted to its own field of play and carries numerals on the floor grid and the vertical axis; each bubble drops a dotted line to its floor shadow so height reads as height. Values are in the table that follows. 0 200 400 600 800 1000 420 440 460 480 500 520 0 200 400 600 800 centrality distinctiveness breadth git: centrality 105, distinctiveness 458, breadth 59 Jujutsu: centrality 350, distinctiveness 440, breadth 190 Devin: centrality 385, distinctiveness 458, breadth 214 Faros AI: centrality 526, distinctiveness 448, breadth 309 Nishi: centrality 964, distinctiveness 493, breadth 642 Nishi git Jujutsu Devin Faros AI
axes fitted: centrality 0–1000 · distinctiveness 420–520 · breadth 0–800 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 2 (a fact of the data: two players that close are that close) · data spread 167 permil of the plot
Position map, small multiplesEvery pair of registered axes as one small cut. Each panel fits both axes to the field of play, the dashed lines are the category means, bubble area is breadth and the ring colour is momentum; the legend below names the colours. 0 1000 420 520 distinctiveness vs centrality Nishi: centrality 964, distinctiveness 493 git: centrality 105, distinctiveness 458 Jujutsu: centrality 350, distinctiveness 440 Devin: centrality 385, distinctiveness 458 Faros AI: centrality 526, distinctiveness 448 0 1000 0 800 breadth vs centrality Nishi: centrality 964, breadth 642 git: centrality 105, breadth 59 Jujutsu: centrality 350, breadth 190 Devin: centrality 385, breadth 214 Faros AI: centrality 526, breadth 309 0 1000 600 900 depth vs centrality Nishi: centrality 964, depth 666 git: centrality 105, depth 833 Jujutsu: centrality 350, depth 761 Devin: centrality 385, depth 750 Faros AI: centrality 526, depth 666 0 1000 480 520 momentum vs centrality Nishi: centrality 964, momentum 500 git: centrality 105, momentum 500 Jujutsu: centrality 350, momentum 500 Devin: centrality 385, momentum 500 Faros AI: centrality 526, momentum 500 420 520 0 800 breadth vs distinctiveness Nishi: distinctiveness 493, breadth 642 git: distinctiveness 458, breadth 59 Jujutsu: distinctiveness 440, breadth 190 Devin: distinctiveness 458, breadth 214 Faros AI: distinctiveness 448, breadth 309 420 520 600 900 depth vs distinctiveness Nishi: distinctiveness 493, depth 666 git: distinctiveness 458, depth 833 Jujutsu: distinctiveness 440, depth 761 Devin: distinctiveness 458, depth 750 Faros AI: distinctiveness 448, depth 666 420 520 480 520 momentum vs distinctiveness Nishi: distinctiveness 493, momentum 500 git: distinctiveness 458, momentum 500 Jujutsu: distinctiveness 440, momentum 500 Devin: distinctiveness 458, momentum 500 Faros AI: distinctiveness 448, momentum 500 0 800 600 900 depth vs breadth Nishi: breadth 642, depth 666 git: breadth 59, depth 833 Jujutsu: breadth 190, depth 761 Devin: breadth 214, depth 750 Faros AI: breadth 309, depth 666 0 800 480 520 momentum vs breadth Nishi: breadth 642, momentum 500 git: breadth 59, momentum 500 Jujutsu: breadth 190, momentum 500 Devin: breadth 214, momentum 500 Faros AI: breadth 309, momentum 500 600 900 480 520 momentum vs depth Nishi: depth 666, momentum 500 git: depth 833, momentum 500 Jujutsu: depth 761, momentum 500 Devin: depth 750, momentum 500 Faros AI: depth 666, momentum 500
Nishi git Jujutsu Devin Faros AI
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 8 (a fact of the data: two players that close are that close) · data spread 533 permil of the plot
PlayerQuadrantcentralitydistinctivenessbreadthdepthmomentumRows heldDays on spineFirst seen
NishiAspirational9644936426660 since 2026-09-2327102026-09-15
gitPeripheral105458598330 since 2026-09-232102026-09-15
JujutsuPeripheral3504401907610 since 2026-09-237102026-09-15
DevinPeripheral3854582147500 since 2026-09-238102026-09-15
Faros AIMainstream5264483096660 since 2026-09-2313102026-09-15
DayMatrix rows reviewedPlayers recorded
2026-09-15285
2026-09-16285
2026-09-17285
2026-09-18285
2026-09-19285
2026-09-20285
2026-09-21285
2026-09-22285
2026-09-23285
2026-10-08285

players 5|matrix rows 28|feature mass 57|centrality mean 466|distinctiveness mean 459|axes 5|spine days 10 (shown 10)|rows written today 0|readability defects 2D 0 cube 0|spine knowledge/status/cdmap/devmgmt.spine

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 112, unassessed 0. Authored assessments are not verified outcomes.

CapabilityNishigitJujutsuDevinFaros AI
DEV
full-fidelity session record harvested to sovereign framesMeasured: ch_frames exists in runtime/_hdl_build/nx_claude_harvest.nx, verified at emit. Parses the Claude Code transcript JSONL (measured 2026-08-19: 869 files, 2.39 GB, laptop-local -- the honest limitation) into actlog frames; ch_delta is HWM-incremental and ch_ingest is marker-idempotent, portable by design. A git commit records exactly a tree, parents, identity and a message [git-object-model]; the transcript contract is declared internal and version-unstable, so the sovereign frame is the durable form [claude-code-sessions]. Devin keeps a full server-side activity record; Faros ingests assistant telemetry counters, never sessions. 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); only referenced by nx_claude_harvest_gate -- a mention, not a run.
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); only referenced by nx_claude_harvest_gate -- a mention, not a run
Pros Implementing source symbol found; runtime acceptance separate; ahead of gitCons behind Devin (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); only referenced by nx_claude_harvest_gate -- a mention, not a run
●○●◉●
outside-tool frames classified by CAUSE, not merely countedDARK — runtime/_hdl_build/nx_claude_harvest.nx EXISTS but does not declare ch_shellgap: 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. MEASURED 2026-09-02 over the WHOLE laptop corpus, no sampling: 2336 transcripts, 240588 tool_use frames (partition sums), sovereign MCP 629 permil, shell 53545 frames = 261 permil of shell-plus-MCP, outside_permil by ISO week 749/466/115/332/280/202 (W31..W36). The gauge row above says HOW MUCH rides outside; this contract says WHY, per frame: MCP-RAW-LANE 15647 (of which 14620 in sessions that had a LIVE MCP client -- a CAP gap, not transport; tools nx_fs 1121, nx_mgmt 1051, nx_fs_write 406, nx_shelltool 349, nx_debt 271), SSH 5202 (nx_sov_build_run.elf over ssh 466, scp 268, cp/rm/kill/nohup/ps host actions with no API verb), PYTHON 5947 (nxq/nxcall/nx_upload wire glue, strip/h2t extraction, marionette capture), WEB 11044 (WebFetch arxiv 663, github 569, nishifamily.com 126 -- our own site through a third-party summariser), LAPTOP-ORGAN 2363 (nx_sov_build_run 1313 local builds, the memory plane), LOCAL-FILE-OPS 15807 (laptop files; harness-local). Durable receipt: knowledge/status/shellgap_census.txt (NX-DERIVED), produced this once by a declared break-glass scan; the contract is the same census as a verb on this organ, on the capture beat, keyed on the command text the frames do not yet carry. Devin's activity record and Faros telemetry count tool calls but neither classifies a shell command by the sovereign capability it stands in for. rival marks uncited — the Yes, Best or Part codes on this row are an observation read with no reference mark behind them
dossierwatching ch_shellgap
Pros none measured yetCons behind Devin, Faros AI; open contract; expected source declaration not established
○○○●●
nishi-vs-outside tooling gaugeMeasured: ch_gauge_json exists in runtime/_hdl_build/nx_claude_harvest.nx, verified at emit. outside_permil over harvested frames measures what fraction of real dev actions still ride non-sovereign tools -- dev-loop sovereignty as a number. OTel GenAI semconv standardizes the naming of agent and tool-call telemetry but ships no storage, replay or resume semantics [otel-genai-semconv]; Faros computes tool-adoption mix from telemetry, the nearest partial. 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); only referenced by nx_claude_harvest_gate -- a mention, not a run.
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); only referenced by nx_claude_harvest_gate -- a mention, not a run
Pros Implementing source symbol found; runtime acceptance separate; ahead of git, Jujutsu, DevinCons 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); only referenced by nx_claude_harvest_gate -- a mention, not a run
●○○○●
empirical workflow mining over the action journalMeasured: al_mine_json exists in runtime/_hdl_build/nx_actlog.nx, verified at emit. Recurring tool:verb bigrams and trigrams with support at or above minsup are the estate's de-facto workflows, MINED not declared; al_harden_json files hardening candidates and al_append is the frame writer. CodeSight process-mines GitHub PR-to-deployment exhaust -- the delivery workflow's shadow, never how the code came to exist [codesight-procmine]; Devin's session search is retrieval over the record, not pattern mining. Adoption: RUN-BY:clock — fully adopted (top of its ladder).
Pros Implementing source symbol found; runtime acceptance separate; ahead of git, Jujutsu, Faros AI; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)
●○○●○
trajectory anti-pattern scanningMeasured: tj_core exists in runtime/_hdl_build/nx_trajscan.nx, verified at emit. Deterministic judge-free detectors (edit-without-verify, search loops, echo groups) over actlog frames. The field basis is research literature, not shipped product; no tool in the researched set scans agent trajectories for process defects. 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 git, Jujutsu, Devin, Faros AICons 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)
●○○○○
workstream lifecycle intelligenceMeasured: wm_mine_json exists in runtime/_hdl_build/nx_ws_miner.nx, verified at emit. Per-lane kickoffs, beats and dones with DONE ACTIVE STALE ABANDONED states and per-actor engagement from the ws_sync journal; nx_ws_sync resume lists in-flight lanes from the same record. Devin tracks session state and PR takeover; Faros-class platforms infer lifecycle from repo and issue exhaust. 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 git, JujutsuCons 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)
●○○●●
DORA delivery metrics without git-pollMeasured: d_band_deploy exists in runtime/_hdl_build/nx_dora.nx, verified at emit. Derives the DORA keys from sovereign event planes (ws_sync journal plus the debt plane) where the field polls git, Jira and CI; nx_dora_gate stands beside it. DevLake computes DORA from exactly pull requests, deployments and incidents, the clock starting at the first commit [devlake-dora]; the DORA research itself is survey-based and structurally cannot see a session [dora-2025]. 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); only referenced by nx_shipjoin_gate -- a mention, not a run.
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); only referenced by nx_shipjoin_gate -- a mention, not a run
Pros Implementing source symbol found; runtime acceptance separate; ahead of git, Jujutsu, DevinCons 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); only referenced by nx_shipjoin_gate -- a mention, not a run
●○○○●
gate-outcome history mining -- flake and erosionMeasured: hm_mine_json exists in runtime/_hdl_build/nx_harnessmine.nx, verified at emit. Mines the per-verdict frames nx_gate_verdict self-records; before it 953-plus gates ran with ZERO recorded outcomes (nx_minecov MC09), flake structurally invisible. The field ingests CI outcomes as delivery exhaust; none mines check-verdict history for flake and erosion. 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 git, Jujutsu, DevinCons 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)
●○○○●
sovereign VCS push, zero-gitMeasured: sgp_walk exists in runtime/_hdl_build/nx_sovgit_push.nx, verified at emit. Tree walk to sha256 objects to packfile to receive-pack wire, no /usr/bin/git anywhere -- the substrate spoken natively [git-object-model]. git and jj are the incumbents on this row and score accordingly. CAUTION: the served binary is drift-census AHEAD class -- a promote from this campaign destroys capability. 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 Devin, Faros AICons behind git (leads), Jujutsu (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)
●◉◉○○
proof-carrying change -- the capability-loss rulerMeasured: cd_show_lost exists in runtime/nx_contentdiff.nx, verified at emit. GREEN only at zero lost runs, every LOST named; the /api/promote guard shares the arithmetic (cdl_lost). The VCS frontier's mutation histories record graph surgery, never a measurement bound to a state; field CI diffs text. Nothing researched refuses a deploy on measured capability loss. Adoption: RUN-BY:fork:nx_rebuild_drain — fully adopted (top of its ladder).
Pros Implementing source symbol found; runtime acceptance separate; ahead of git, Jujutsu, Devin, Faros AI; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)
●○○○○
gates proven non-vacuous by mutationMeasured: gb_try exists in runtime/_hdl_build/nx_gate_bite.nx, verified at emit. Plants byte mutations and asserts the gate goes RED; taxonomy BITES, INCONCLUSIVE, UNCONTROLLED. Fleet measured 2026-08-15: 2,317 gate sources, 135 deployed, 30 invoked, 0 invocation gaps. No researched tool proves its own checks can fail. Adoption: RUN-BY:actlog — fully adopted (top of its ladder).
Pros Implementing source symbol found; runtime acceptance separate; ahead of git, Jujutsu, Devin, Faros AI; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)
●○○○○
served-vs-built drift census by remedyMeasured: ps_judge exists in runtime/nx_artifactdrift.nx, verified at emit. BEHIND, AHEAD and RESIZED-EQUAL partitions reconciled plus the INERT exec-bit axis (ps_execbit); per-row lost-run worklists and a daily append to knowledge/status/artifactdrift.log, so the trend exists and not just the level. The field's nearest concept is deploy tracking from CI exhaust; none compares served bytes against a rebuild of source. Adoption: RUN-BY:clock — fully adopted (top of its ladder).
Pros Implementing source symbol found; runtime acceptance separate; ahead of git, Jujutsu, Devin, Faros AI; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)
●○○○○
one-call ship loop with a durable journalMeasured: os_jrnl exists in runtime/nx_organ_ship.nx, verified at emit. build, gate, contentdiff, behaveprobe, promote, offc-twin, register and verify as one organ; every stage appends knowledge/status/organ_ship.jrnl and the trace survived four client deaths. Copilot's coding agent links each commit to its session log, a read-only audit surface with no export and no resume [copilot-session-logs]; Devin lands PRs end-to-end without a verifiable stage journal. Adoption: RUN-BY:clock — fully adopted (top of its ladder).
Pros Implementing source symbol found; runtime acceptance separate; ahead of git, Jujutsu, Faros AI; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)
●○○●○
multi-seat compare-and-swap on the shared treeMeasured: fsw_expect_val exists in runtime/nx_fsops_write.nx, verified at emit. Content CAS whose refusal hands the caller the expect token (tools-api name nx_fs_write); nx_atomic_publish is the whole-file all-or-nothing lane, grounded by the 2026-08-15 concurrent-writer clobber measurement. jj proves lock-free concurrent repo ops with op-log merge [jj-oplog]; Amp threads are durable shared objects with one writer each [amp-threads]; Devin sidesteps coordination by VM isolation. Nobody researched coordinates concurrent agent writes to one shared working tree. Adoption: REGISTERED-UNAUTHORISED — PARTIAL: registered, no cap ever minted; no execution surface runs it either (clock, cron, daemon, roster, actlog and surfaced forks checked); only referenced by nx_fsops_write_gate -- a mention, not a run.
not adopted: registered, no cap ever minted; no execution surface runs it either (clock, cron, daemon, roster, actlog and surfaced forks checked); only referenced by nx_fsops_write_gate -- a mention, not a run
Pros Implementing source symbol found; runtime acceptance separate; ahead of git, Faros AICons behind Jujutsu (leads); not adopted yet: registered, no cap ever minted; no execution surface runs it either (clock, cron, daemon, roster, actlog and surfaced forks checked); only referenced by nx_fsops_write_gate -- a mention, not a run
●○◉●○
seat token-engine boot and meteringMeasured: st_boot exists in runtime/_hdl_build/nx_seat.nx, verified at emit. One-call boot digest at or under 4096 B versus a 40K-token memory-file boot (12-session baseline: cache_read 920.8M vs output 6.1M tokens); st_meter_append is the per-session dev-cost ledger. DX meters utilization, impact and cost from tool telemetry and surveys, outside-in [dx-ai-framework]; the seat meters itself from inside the session. Adoption: RUN-BY:actlog — fully adopted (top of its ladder).
Pros Implementing source symbol found; runtime acceptance separate; ahead of git, Jujutsu, Devin; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)
●○○○●
per-seat crash-resume map from transcript tailsMeasured: st_resume_map exists in runtime/_hdl_build/nx_seat.nx, verified at emit. Hand-done TWICE on 2026-08-19 (7 seats died near 11:26 and again near 21:09; the coordinator mined transcript tails, scratchpads and output tails for exact per-seat resume points). Langfuse session replay is viewing the record, not resuming the agent [langfuse-sessions]; Devin's session search is post-hoc analytics with no path back to a resumable state; jj op restore rewinds repo state only. Incumbent floor: nx_ws_sync resume reads the journal but cannot see last-action or in-flight writes; compose ch_frames over the tail. Adoption: RUN-BY:actlog — fully adopted (top of its ladder).
dossier
Pros Implementing source symbol found; runtime acceptance separate; ahead of git, Faros AI; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)
●○●●○
session-to-NAS capture beatMeasured: ch_beat exists in runtime/_hdl_build/nx_claude_harvest.nx, verified at emit. Parser, delta (ch_delta high-water mark) and idempotent ingest already exist and are portable; what is missing is cadence plus a NAS landing, so 869 files and 2.39 GB of dev record are unmineable from the estate. Checkpoints live tool-locally outside repo history, two unjoined histories by platform default [claude-code-checkpoints]; Devin's sessions land server-side and searchable by activity class, the strongest field capture [devin-session-search]. Done-rule: a clock row delta-harvests every transcript and frames land in a NAS journal. 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); only referenced by nx_claude_harvest_gate -- a mention, not a run.
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); only referenced by nx_claude_harvest_gate -- a mention, not a run
Pros Implementing source symbol found; runtime acceptance separate; ahead of git, JujutsuCons behind Devin (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); only referenced by nx_claude_harvest_gate -- a mention, not a run
●○○◉●
exec-proven lost-set minerMeasured: rm_lostset exists in runtime/_hdl_build/nx_registrymine.nx, verified at emit. On 2026-08-19 an agent hand-mined 836,673 transcript lines and 32,122 MCP calls to find 18 exec-proven tools with no registry row (knowledge/status/toolrows_lostset_20260819.txt, debt 1787175603); the shape belongs in the registry miner as a standing verb. Faros reconciles AI-tool adoption from telemetry and repo exhaust, never exec-proven from the session record [faros-ai-impact]. 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); only referenced by nx_lostset_gate -- a mention, not a run.
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); only referenced by nx_lostset_gate -- a mention, not a run
Pros Implementing source symbol found; runtime acceptance separate; ahead of git, Jujutsu, DevinCons 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); only referenced by nx_lostset_gate -- a mention, not a run
●○○○●
concurrent-ownership detector on BEHIND rowsMeasured: ps_owner_scan exists in runtime/nx_artifactdrift.nx, verified at emit. BEHIND is necessary-not-sufficient for promote: a BEHIND row can be another seat's in-flight work (caught live on nx_oo_extract_gate; nx_treediverge.nx carries two scratch files beside it now, nx_artifactdrift.nx nineteen). GitButler hands agents a CLI for commits yet documents no record of which agent made which change [gitbutler-vbranches]; git names an author only once a commit exists, jj stamps username and hostname per operation. Done-rule: every BEHIND row carries an owner signal before any promote list publishes. Adoption: RUN-BY:clock — fully adopted (top of its ladder).
dossier
Pros Implementing source symbol found; runtime acceptance separate; ahead of Devin, Faros AI; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)
●●●○○
a citation lands as ONE publish -- the ref row and its inline mark together, or neitherMeasured: cc_publish exists in runtime/nx_compare_cite.nx, verified at emit. SOURCE-LANDED 2026-09-02 (operator: these should be capabilities the estate has, not a seat's hand edits). A /compare citation is two writes in two files, and nx_compare_refs_gate refuses the board when either half is missing (UNCITED without the mark, UNRESOLVED-MARK without the row); measured the day it was written, fifteen refs landed as one edit and five marks then took five sequential compare-and-swap edits, each a transport round-trip that can half-land. The estate held a citations GATE, a format PRECHECK and a VERIFIER and no WRITER. nx_compare_cite computes the pin FROM the mirror (an unfetched reference cannot be cited -- the fabrication class refused by construction), matches EXACTLY ONE matrix row by label prefix (0 or 2+ refuse with the count), refuses a pipe in any prose field, resolves both files in the referee's PUBLISHED tree order (nx_comparetree_lib), and publishes each file whole under nx_atomic_publish's compare-and-swap with the sha256 this run read -- composed by fork, never re-implemented -- refs first, mark second, idempotent on re-run (ALREADY-CITED). Build queued behind admission the day it landed; the gate is the next row's subject. git and jj version files and know nothing of a citation as a unit; Devin and Faros do not write research registers. Adoption: REGISTERED-UNAUTHORISED — PARTIAL: registered, no cap ever minted; no execution surface runs it either (clock, cron, daemon, roster, actlog and surfaced forks checked).
dossiernot adopted: registered, no cap ever minted; 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 git, Jujutsu, Devin, Faros AICons not adopted yet: registered, no cap ever minted; no execution surface runs it either (clock, cron, daemon, roster, actlog and surfaced forks checked)
●○○○○
which surface launches this organ, asked as a question the census answersMeasured: es_who exists in runtime/nx_execsurface.nx, verified at emit. SOURCE-LANDED 2026-09-02 (operator: capabilities, not hand greps). nx_execsurface has censused every promoted organ's execution surfaces daily since 08-23 (clock, cron, daemons.reg, gate roster, MCP actlog, source forks to a fixed point) into execsurface.tsv -- and the day the question mattered (what relaunches nx_daemon_supervisor?) a seat grepped four surfaces by hand instead of reading the row, which says 0 0 0 - 0 0 -: NOTHING in the estate launches the fleet supervisor. A CENSUS NOBODY CAN ASK A QUESTION OF IS A FILE, NOT A CAPABILITY. The who verb reads the last census only (safe under any load), decodes the row into launched-by and first_surface, prints the stamp and its age with census_stale= at two missed beats, and exits ON-SURFACE, NO-SURFACE, NOT-IN-CENSUS or UNOBSERVABLE so a script can branch on it. Faros answers who USED a tool from telemetry; git, jj and Devin do not model execution surfaces at all. 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:clock — fully adopted (top of its ladder).
Pros Implementing source symbol found; runtime acceptance separate; ahead of git, Jujutsu, Devin; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)
●○○○●
crash-write adjudicatorMeasured: ap_landed exists in runtime/_hdl_build/nx_atomic_publish.nx, verified at emit. At both 2026-08-19 crashes the in-flight async writes split roughly half landed and half not; six lanes were adjudicated by hand from artifacts. The jj op log records every repo mutation with a full view snapshot, the strongest landed-or-not substrate for repo state; Cursor checkpoints snapshot files with crash persistence undocumented [cursor-checkpoints]. Done-rule: given expected writes, read back size and hash, emit LANDED or NOT per row, wrong only toward NOT. 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); only referenced by nx_atomic_publish_gate -- a mention, not a run.
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); only referenced by nx_atomic_publish_gate -- a mention, not a run
Pros Implementing source symbol found; runtime acceptance separate; ahead of git, Devin, Faros AICons 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); only referenced by nx_atomic_publish_gate -- a mention, not a run
●○●○○
DORA fed by ship receiptsMeasured: d_ship_join exists in runtime/_hdl_build/nx_dora.nx, verified at emit. nx_dora's constants name only the ws_sync journal and the debt plane while organ_ship.jrnl carries the actual promote and verify events; the join turns deploy-frequency and lead-time from workstream proxy into the real ship record. The field's delivery clock starts at the first commit and consumes only PR, deploy and incident exhaust; even the strongest measurement frameworks concede agentic measurement must still evolve. 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); only referenced by nx_shipjoin_gate -- a mention, not a run.
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); only referenced by nx_shipjoin_gate -- a mention, not a run
Pros Implementing source symbol found; runtime acceptance separate; ahead of git, Jujutsu, DevinCons 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); only referenced by nx_shipjoin_gate -- a mention, not a run
●○○○●
ADOPT
the whole adoption chain judged end to end with a weakest-link verdictMeasured: cat_one exists in runtime/nx_catalog.nx, verified at emit. SOURCE then BUILT then STAGED then PROMOTED then REGISTERED then AUTHORISED then INVOKED, one call per name, and the published answer is the WEAKEST link rather than a headline -- so BUILT-UNPROMOTED, PROMOTED-UNREGISTERED and REGISTERED-DARK are three answers with three different remedies instead of one word. This is the adoption axis for a single CAPABILITY; growth.matrix gs_axis_adoption measures the estate-wide STOCK from source-level callers, and the two are deliberately kept apart rather than merged into a duplicate ruler. Faros computes adoption and acceptance rates from assistant telemetry and repo exhaust, which measures whether humans use a TOOL, never whether a capability this process built ever became callable [faros-ai-impact]. Copilot links each commit to its session log for audit, a read-only surface that says nothing about deployment state [copilot-session-logs]. Adoption: LIVE — fully adopted (top of its ladder).
Pros Implementing source symbol found; runtime acceptance separate; ahead of git, Jujutsu, Devin; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)
●○○○●
an unpromoted build is DECLARED by its owner, never inferred by a readerMeasured: ps_decl_has exists in runtime/nx_artifactdrift.nx, verified at emit. The standing law is that any build you do not promote must be said out loud with a reason. This gives that statement a place to live and a reader that acts on it, so a claimed target reads DECLARED on the promote worklist and an unclaimed one cannot hide among the claimed. Rows are anchored on field 0, so a target name appearing inside another row prose can never claim it -- a whole-buffer search would have reported rows as owned that nobody owned. jj stamps username and hostname on every operation, the closest field equivalent, but it records who DID something rather than who is HOLDING something right now [jj-oplog]. GitButler hands agents a CLI for commits and history surgery and documents no record of which agent made which change [gitbutler-vbranches]. Adoption: RUN-BY:clock — fully adopted (top of its ladder).
Pros Implementing source symbol found; runtime acceptance separate; ahead of git, Devin, Faros AI; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)
●○●○○
the adoption delta as a per-class trend, never a levelMeasured: dc_adopt_delta exists in runtime/_hdl_build/nx_deltaclass_lib.nx, verified at emit. A level says 147 binaries are behind; only a delta says whether the promotable backlog is shrinking or merely changing hands. The incumbent to extend is the ledger reader that already separates DELIVERED from SCOPE-MOVED from THRASH, and both inputs are census outputs already on disk -- artifactdrift.log once per beat and nx_catalog once per name -- so this rung COMPOSES and never sweeps. DevLake computes delivery rates from exactly pull requests, deployments and incidents with the clock starting at the first commit, so a capability built and never deployed is invisible to it by construction [devlake-dora]. DX meters utilization, impact and cost from tool telemetry and surveys and its own authors concede agentic measurement must still evolve [dx-ai-framework]. Done-rule: two consecutive beats emit deltas whose arithmetic reconciles against the underlying logs. Adoption: LIB-WIRED importers=2 nonval=1 — fully adopted (top of its ladder).
dossier
Pros Implementing source symbol found; runtime acceptance separate; ahead of git, Jujutsu, Devin; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)
●○○○●
documentation as a shipping stage, reported per shipMeasured: os_doc_stage exists in runtime/nx_organ_ship.nx, verified at emit. A capability that is built, promoted, registered and undocumented is one nobody will find, and the operator named documenting alongside deploying and wiring as one failure rather than three. The stage asks one mechanical question at ship time -- does this symbol appear in a compare matrix, plan or watch row, or carry a memory pointer -- and REPORTS rather than refuses, because a pre-flight that can refuse gets disabled while one that only informs survives. Claude Code sessions persist locally with the full tool history restored on resume and no link to any capability register [claude-code-sessions]. Amp threads are durable shared objects searchable by label, file, repo and author, which shares the CONVERSATION rather than registering the capability it produced [amp-threads]. Done-rule: DOCUMENTED or UNDOCUMENTED per ship with zero false DOCUMENTED. Adoption: RUN-BY:clock — fully adopted (top of its ladder).
dossier
Pros Implementing source symbol found; runtime acceptance separate; ahead of git, Jujutsu, Devin, Faros AI; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)
●○○○○
COMPLETE on /compare is three-party agreement, derived from planes and never declaredMeasured: acm_emit exists in runtime/nx_accept.nx, verified at emit. Operator standing order 2026-08-30: doing it poorly is not a complete; it is not complete till the operator, the seat and the nishi referees agree. Three sovereign planes, one classifier (nx_accept_lib): knowledge/store/accept- holds the OPERATOR verdict rows (id, subject words, ACCEPT or REJECT or UNJUDGED, date, actor operator, words, targets); knowledge/store/referee- holds the REFEREE rows written only by nx_accept referee SUBJECT PNG TIER SEAT, which runs the cjc_panel percept lens on the capture and records the percept against the panel's admitted per-tier floor (a tier the receipt has not admitted is REFUSED, a lens that cannot see writes no row); knowledge/store/attest- holds the SEAT rows written by nx_accept attest SUBJECT SEAT WORDS ARTIFACT with the stamp derived as the artifact's sha256. nx_accept emit (clock row acceptemit, hourly, ahead of the six-hourly compare beat) regenerates runtime/nx_accept_decl.nx with one ga_accept_SUBJECT declaration per subject that carries all three, so an ACCEPTANCE watch row lands only on agreement, and nx_accept status SUBJECT names the missing party. OPERATOR RECIPE, one call, the only write the operator makes: nx_store_put knowledge/store/accept- put operator ID SUBJECT-WORDS ACCEPT DATE operator WORDS ga_accept_SUBJECT -- the targets field MUST carry the token ga_accept_SUBJECT (bare or domain-qualified, mechanical symbols may follow after commas) or the row governs nothing and is printed UNMAPPED with that remedy; a later REJECT row revokes an earlier ACCEPT because row order is write order. Gate nx_accept_gate GREEN and bite-proven in subject mode on 2026-08-31; the mechanism's own acceptance needs a non-visual referee class (its gate) that the percept-only referee plane cannot yet express, stated rather than faked with a cell that could never flip. The field has no counterpart: git, jj, Devin and Faros record who did what and never whether three named parties agreed a thing is complete. Adoption: RUN-BY:clock — fully adopted (top of its ladder).
dossier
Pros Implementing source symbol found; runtime acceptance separate; ahead of git, Jujutsu, Devin, Faros AI; 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
ClassCountNote
rows with rival marks21rows carrying a Yes, Best or Part in a rival column
cited16a reference mark resolves to a pinned mirror
uncited5an observation read, badged until a reference lands
rows, summed21RECONCILED: 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

RiskLikelihood x impactMitigation
The capture beat hammers the NAS with a 2.39 GB backfillpossible x mediumch_delta is HWM-incremental so the beat lands deltas only; the first backfill runs as a named one-off job under the io-admission ruler, never on the beat.
A resume map read as authority replays a stale planpossible x mediumDM2 emits evidence rows (lane, last artifact, in-flight writes, timestamps); the relaunching coordinator judges -- the map never auto-relaunches a seat.
A watch contract flips on symbol existence, so a stub reads greenpossible x highThe done-rule proven against the 2026-08-19 hand-mined ground truth is the bar; the flip is the receipt, never the proof.

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.
WhenRungKindEntry
2026-09-03DM10measureTHE ACCEPTANCE QUEUE WAS COMPLETE AND UNPUBLISHED, and the operator named it: "for human acceptance you need to publish a queue and evidence to review like how we have rigview but you arent anywhere". Measured 2026-09-03: nx_accept list ALREADY computes, per subject, which of the three parties is missing, and knowledge/store/accept- ALREADY holds the operator's verdicts and words. Neither has ever been rendered anywhere -- the queue existed only if you ran a CLI verb. Live ledger: subjects=5 agreed=0 not_agreed=5 planes=3/3, and the split matters -- only SKIN is missing=OPERATOR-UNJUDGED and therefore actually waiting on the operator; face, garments, hair and locomotion are the operator's own REJECTs waiting on SEATS to rework. FACE IS THE DOCTRINE WORKING, NOT A DEFECT: referee=OK with percept=214 against floor=151 while the operator REJECTed -- the machine lens cleared its bar and the human did not, which is exactly why three signatures exist. ★★★★★★A DECISION THAT REQUIRES A HUMAN AND IS NOT PUT IN FRONT OF THEM IS NOT A PENDING DECISION, IT IS A STALLED ONE -- and from the inside it is indistinguishable from the human being slow
2026-09-03DM10landnx_acceptview SOURCE-LANDED at 17428 B: composes nx_accept list (verdict and missing-party from the ONE classifier, nx_accept_lib) plus the accept- plane through nx_store_put's own loader, and computes NO verdict of its own -- a second opinion rendered beside the first is a duplicate ruler wearing a stylesheet. Publishes sites/nishifamily/compare/acceptance/index.html, sorted so subjects awaiting the OPERATOR come first, showing the referee's percept against its own floor and the operator's words VERBATIM through an escaper (a rejection note is free text a human typed and an angle bracket in one must never become markup on the page they decide from). Also truncate-writes knowledge/status/accept_queue.status with awaiting_operator and awaiting_seat_or_referee, verdict LAST. It REFUSES to publish an empty queue: an empty acceptance page would read as nothing awaiting review, which is the most dangerous false statement that page could make. Precedent for a page organ beside the matrix emitter is established -- nx_maturity_board, nx_rulers_page, nx_pm_page all do this
2026-09-03DM10queueOWED: the nx_acceptview build was refused four times by I/O admission and is ENQUEUED (rc=0); once the binary exists, declare its hourly clock row beside acceptemit and verify the page renders. NOTE THE GUARD THAT FIRED: nx_clockjob REFUSED the row while the elf was absent -- "a row whose organ does not exist is a beat that is dead the moment it is written, and it dies SILENTLY" -- so the beat is declared AFTER the binary, never before. Owed after that: a gate over the escaper and the empty-queue refusal, and a link from the devmgmt page to /compare/acceptance
2026-09-05DM12measureMEASURED 2026-09-05 on nx_janitor_caps_gate: BANK CURRENT (closure cab9f3fc), PROVE ran ./nx_janitor_caps_gate.elf = 20,695 B (the pre-migration gate, hand-rolled dialect) while buildroot/_build/nx_janitor_caps_gate.sov.elf = 30,649 B was the artifact the bank described; the receipt read vintage=FRESH-closure-bank-CURRENT about a binary the bank had never seen. Same shape one hour later on the loop's own gate: bank CURRENT, import scan demanded a rebuild anyway, admission refused it, PROVE ran the promoted 43-tooth gate while the banked 50-tooth build sat in root B, labelled STALE-gate-rebuild-REFUSED.
2026-09-05DM12landnx_organ_ship 43ae1d12 PROMOTED (self-ship, allow_loss=1 for the reworded NO REBUILD sentence, offc twin fresh): osl_pick_banked(resolved_root, sha_a, sha_b, b_exists) in nx_organ_ship_lib (KEEP / SWITCH_B / UNPROVEN) + os_gate_freshen switching gpath to root B on a differing digest (BANKED-BUILD-USED) or returning UNKNOWN when the bank matches nothing (BANK-UNMATCHED); nx_organ_ship_gate T46-T50 GREEN (50/50 on the rebuilt gate). OPEN in this rung: a CURRENT bank must beat the CONTAINS import scan so no compile is spent and no refusal downgrades a proven artifact to STALE.
2026-09-05DM12landFIX TWO LIVE: nx_organ_ship c862f05f PROMOTED (allow_loss=1 for the vanished symbol string osl_should_rebuild_prov, which the program no longer references), gate REBUILT 56/56 GREEN with T51-T56: osl_should_rebuild_pick(gate, target, clo, prov, pick) lets a CURRENT bank veto the import scan's rebuild ONLY when the banked artifact is on disk and is the one PROVE runs (KEEP or SWITCH_B); an UNPROVEN pick (banked artifact gone) leaves the incumbent rebuild standing (neg-control T53); os_gate_freshen computes the pick BEFORE the decision. T39 (a bank alone never vetoes) deliberately kept true of osl_should_rebuild_prov. The rung's own receipt was the measurement: the loop that shipped fix two was the fix-one binary, so it still rebuilt past a CURRENT bank once more; the next ship through c862f05f runs the banked artifact without a compile.
2026-09-06DM12landnx_sov_build_run 981d60e0 (146592 B, TOOLCHAIN-PROMOTED canary GREEN into buildroot/_offc AND promoted to the serving root, contentdiff strict superset): the build FLAVOUR now follows the incumbent. With neither --debug nor the new --release given the runner reads the serving-root twin's bytes (sbr_incumbent_flavour: the DWARF line-table section name present = debug; needle assembled from two halves so a self-rebuild cannot read its own literal) and announces FLAVOUR debug
2026-09-06DM12lessona per-call build flavour that no target declares is a silent CAPLOSS generator: nx_wgsl rebuilt without --debug against a live debug binary read lost_from_live=823 (422 permil) with lost_other=0, and the runner's own first rebuild reproduced it (147 metadata-only losses, release 127373 B vs live debug 144136 B). A guard that fires on every flavour swap is a guard seats learn to pass allow_capability_loss through, which disarms it for the real regression; derive the flavour from the artifact, never make the seat remember a flag. The flavour is one more entry in the CQ13 census class (a build-shaping choice with no declared owner)
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. The coverage above records source-symbol presence. Stronger comparisons are authored claims, not measured runtime superiority or accepted outcomes. A watch contract names an expected source symbol; finding it changes source discovery only. Qualification, deployment and runtime acceptance require their own evidence.

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

Every compare carries this layer. Declare knowledge/compare/devmgmt.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 devmgmt, 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 devmgmt.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
ClassCountNote
seeds3
scanned3
fetched3
reused0
failed0
named3
candidates3
mentions3
capped0
RankRivalSeedsMentionsFirst seedKindLink
1git11col0-gitnamedhttps://git-scm.com/book/en/v2/Git-Internals-Git-Objects
2Devin11col2-devinnamedhttps://docs.devin.ai/release-notes
3Faros AI11col3-farosnamedhttps://www.faros.ai/ai-impact

field candidates 3|shown 3 of 3|matrix columns in the field 3 of 4|discovered rivals with no column 0|malformed rows 0 (counted, never rendered)|read-capped 0

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 28 capabilities: 16 exclusive to it and 12 shared with other boards. Shared rows on this page: 12 = home here 3 + home elsewhere 1 + ambiguous 0 + undecided 8 + refused 0 (partition 12); undecided = unmapped 0 + unproven 8 + unevidenced 0; homonyms 0; since the previous census: new 0, resolved 0. Census FRESH age_s=6731.

CapabilityOrganBoards grading itHomeRuleEvidenceStanding on this board
d_band_deploynx_dora.nxswarm, devmgmt, codeeffectiveness—noneunprovenundecided
ch_framesnx_claude_harvest.nxdevmgmt, codeeffectiveness—noneunprovenundecided
ch_gauge_jsonnx_claude_harvest.nxdevmgmt, engineshift—noneunprovenundecided
al_mine_jsonnx_actlog.nxdevmgmt, codeeffectiveness—noneunprovenundecided
cd_show_lostnx_contentdiff.nxdevmgmt, codequality, autodev, capregistry, codeeffectiveness—noneunprovenundecided
gb_trynx_gate_bite.nxdevmgmt+, codequality, autodev*, codeeffectivenessautodevrungplanhome elsewhere
adopt: @xrow autodev|gb_try|home by rung (fleet duplicate census)
ps_judgenx_artifactdrift.nxdevmgmt, capregistry, codeeffectiveness—noneunprovenundecided
os_jrnlnx_organ_ship.nxdevmgmt+, autodevdevmgmtgatesgateshome here
st_bootnx_seat.nxdevmgmt, engineshift, codeeffectiveness—noneunprovenundecided
st_resume_mapnx_seat.nxdevmgmt*, engineshiftdevmgmtrungplanhome here
ap_landednx_atomic_publish.nxdevmgmt*, sharehubdevmgmtrungplanhome here
cat_onenx_catalog.nxdevmgmt, capregistry—noneunprovenundecided

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 1395836 s), sources read 4 of 7 declared — a BLIND census is a FLOOR: unread sources can only add rows.

kindnameboardsourceevidence

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.
  1. [git-object-model] Pro Git, Git Internals - Git Objects (official git-scm.com book): a commit records exactly a tree hash, parent hashes, author and committer identity with timestamps, and a free-text message -- nothing else; the development process collapses to snapshots plus prose. publisher · read in our library knowledge/fetched/cmp_devmgmt_git-object-model.html · pin h74c89abda3e3d044d865707d89d8b33714b34c74a3032937db53a54ba38f35f3 · accessed 2026-08-19 · vendor-docGrounds: DEV: full-fidelity session record harvested to sovereign frames
  2. [jj-oplog] Jujutsu official docs, Operation log: every repo-mutating operation is recorded with a full view snapshot (refs, heads, per-workspace working-copy commits) plus username, hostname and time, enabling undo, op revert, op restore and lock-free concurrent operations -- who-ran-what-when on the repo only, no reason and no measurement attached to any state. publisher · read in our library knowledge/fetched/cmp_devmgmt_jj-oplog.html · pin h9c337e3458805334a24ca402cce2b8fcacf2a85f26b76f38981c2657a3d5b19b · accessed 2026-08-19 · vendor-docGrounds: DEV: multi-seat compare-and-swap on the shared tree
  3. [faros-ai-impact] Faros AI, AI Coding Assistant Impact and Productivity Metrics product page: ingests AI-assistant telemetry (Copilot, Claude, Cursor, Windsurf, Devin, Amazon Q) plus repos, Jira, CI and surveys; computes adoption, acceptance rates and percent-AI-generated by repository -- attribution stops at assistant telemetry and repo granularity, never the in-session process. publisher · read in our library knowledge/fetched/cmp_devmgmt_faros-ai-impact.html · pin h674d36e02fea9b26fffa4fda443203f5efc5a11a19f7f8aabe42c78878c49b00 · accessed 2026-08-19 · vendor-docGrounds: DEV: exec-proven lost-set miner
  4. [claude-code-sessions] Anthropic, Manage sessions (Claude Code docs): sessions persist as local JSONL transcripts with the full history including tool calls restored on resume, plus branching and scripted access; the entry format is declared internal and version-unstable, and two terminals on one session interleave into one transcript -- no multi-seat write coordination, no cross-seat crash recovery. publisher · read in our library knowledge/fetched/cmp_devmgmt_claude-code-sessions.html · pin hc466e842c9a0c734163e77dc0019d9575cffb7163b337f844b14369066f1f5e3 · accessed 2026-08-19 · vendor-docGrounds: DEV: per-seat crash-resume map from transcript tails
  5. [claude-code-checkpoints] Anthropic, Enabling Claude Code to work more autonomously (2025-09-29): checkpoints auto-save code state before each agent edit and can rewind code, conversation or both -- the first mainstream versioning of the intent trace; they exclude user edits and bash commands, live tool-locally outside repo history, and Anthropic directs users to run real VCS alongside. publisher · read in our library knowledge/fetched/cmp_devmgmt_claude-code-checkpoints.html · pin hfe0d69c45f12bfe98df5a8389f37ef21a0cdb83f858e92fbd23108a678e8a0be · accessed 2026-08-19 · vendor-docGrounds: DEV: session-to-NAS capture beat
  6. [cursor-checkpoints] Cursor docs, Checkpoints: the agent automatically creates checkpoints before significant changes, capturing the state of all modified files, restorable from the chat timeline, stored locally and separate from git; persistence across restart or crash is undocumented, and there is no query, export or mining surface. publisher · read in our library knowledge/fetched/cmp_devmgmt_cursor-checkpoints.html · pin h3c18bc24b644b21c61a62690a7bcd1e363a25ec8049935e49b15f0f6c7dfaa4d · accessed 2026-08-19 · vendor-docGrounds: DEV: crash-write adjudicator
  7. [copilot-session-logs] GitHub docs, Tracking GitHub Copilot sessions: session logs expose the coding agent's internal reasoning and the tools it used, and each commit message links to its session logs for audit -- a read-only surface with no documented resume of a crashed session, no API export and unstated retention. publisher · read in our library knowledge/fetched/cmp_devmgmt_copilot-session-logs.html · pin h26d8e81eaecd19d99676f1067b9b9a86a37e63a26b35ac5b49643724955e95f0 · accessed 2026-08-19 · vendor-docGrounds: DEV: one-call ship loop with a durable journal
  8. [amp-threads] Sourcegraph, Amp Owner's Manual: threads are durable server-side objects shared with workspace members by default, searchable by label, file, repo, author and date, with remote control across devices -- whole-conversation sharing for humans, one writer per thread, no mechanical reconstruction of interrupted work state and no coordination protocol between concurrent writers. publisher · read in our library knowledge/fetched/cmp_devmgmt_amp-threads.html · pin h946c2b24ccca92a4be495ff4d329799f7e07e6a7479808875684d62a61e9182b · accessed 2026-08-19 · vendor-docGrounds: DEV: multi-seat compare-and-swap on the shared tree
  9. [langfuse-sessions] Langfuse docs, Sessions: a propagated sessionId groups observations and traces into a session with replay of the entire interaction plus session-level scores via UI, SDK and API -- replay is viewing the record, not resuming the agent; it observes an instrumented app and cannot restore or coordinate agent working state. publisher · read in our library knowledge/fetched/cmp_devmgmt_langfuse-sessions.html · pin he830faa9f9b0efaa150d3ee6fe507129e47586fb6711d3d5302fd11e38efd994 · accessed 2026-08-19 · vendor-docGrounds: DEV: per-seat crash-resume map from transcript tails
  10. [otel-genai-semconv] OpenTelemetry, semantic-conventions-genai repository: vendor-neutral semantic conventions for GenAI spans, metrics and events covering GenAI clients, MCP and provider-specific conventions; in development with no declared stability -- standardizes telemetry shape only, with no storage, replay, resume or recovery semantics. publisher · read in our library knowledge/fetched/cmp_devmgmt_otel-genai-semconv.html · pin h101ed9c8ca53eb9cdde8d2f002b400266c45ec0e0a17c97a74c93473d16e2571 · accessed 2026-08-19 · published-standardGrounds: DEV: nishi-vs-outside tooling gauge
  11. [dora-2025] DORA (Google Cloud research program), State of AI-assisted Software Development 2025: AI is an amplifier magnifying existing organizational strengths and weaknesses, returns come from the underlying organizational system; survey-based respondent self-report -- it measures perceptions and reported outcomes and structurally cannot see any actual development session. publisher · read in our library knowledge/fetched/cmp_devmgmt_dora-2025.html · pin h6bb53c243fc615849727e65b6a9aa33dbd6b0d5c4e63af5ce68137db0924b4d9 · accessed 2026-08-19 · published-paperGrounds: DEV: DORA delivery metrics without git-poll
  12. [devlake-dora] Apache DevLake documentation, DORA metrics implementation: computes DORA from exactly three entities -- pull requests, deployments, incidents -- sourced from CI systems, issue trackers and repos, webhooks for the rest; lead time is measured commit-to-production, so everything before the first commit (IDE work, agent sessions, abandoned attempts) is invisible by construction. publisher · read in our library knowledge/fetched/cmp_devmgmt_devlake-dora.html · pin h253628287ee222cbc38c1216811d5cb00ac514bbf7ec7796c7effc79c925ea47 · accessed 2026-08-19 · vendor-docGrounds: DEV: DORA delivery metrics without git-poll
  13. [dx-ai-framework] DX Research, Measuring AI code assistants and agents (AI Measurement Framework): three dimensions -- utilization, impact (AI-driven time savings plus Core 4), cost -- from AI-tool telemetry, git data and surveys; agents are treated as team extensions with contribution measured by emitted PRs, and the authors concede agentic measurement must still evolve. publisher · read in our library knowledge/fetched/cmp_devmgmt_dx-ai-framework.html · pin h778e2f333c133d411f930c36a9248dd4329f3118cf8de40acafa12c50701baa7 · accessed 2026-08-19 · vendor-docGrounds: DEV: seat token-engine boot and metering
  14. [codesight-procmine] Dorado, Folgueira, Martin et al., CodeSight: process mining for software development workflows, arXiv 2510.25935 (Oct 2025): captures GitHub PR-to-deployment events as process-mining logs, mines workflow variants and trains an LSTM to predict remaining PR resolution time -- the event log begins at GitHub exhaust, so it mines the delivery workflow's shadow; how the code came to exist is outside the log. publisher · read in our library knowledge/fetched/cmp_devmgmt_codesight-procmine.html · pin hcab78693a99affba3d3555d9b98cd4237b81cf6cd9f026858adf390b27011bca · accessed 2026-08-19 · published-paperGrounds: DEV: empirical workflow mining over the action journal
  15. [gitbutler-vbranches] GitButler docs, Virtual Branches: multiple branches applied to one working directory simultaneously with per-lane staging and hunk-level assignment of uncommitted changes, plus an oplog restoring prior workspace layouts; the agents doc gives agents a CLI for commits and history surgery but documents no session tracking and no record of which agent made which change. publisher · read in our library knowledge/fetched/cmp_devmgmt_gitbutler-vbranches.html · pin h805c988d5cf89d5316e28e7006caef196620e09483c2daf4b204fdaa4ce8a2fc · accessed 2026-08-19 · vendor-docGrounds: DEV: concurrent-ownership detector on BEHIND rows

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