Growth and Executive Intelligence

Nishi vs the field — every Nishi cell is measured against real organ source at emit time; each gap names the watch contract that will close it.

The wedding cake -- executive, managerial, operational -- measured over time from the sovereign planes, never asserted. Capability growth AND the West Industrial firm on one surface, with a daily/weekly/monthly derivative rather than a snapshot. Every gap row WATCHES its future organ:symbol and flips live when the workstream ships it.

Layer 1 · Executive

Where we are. The wedding cake is live and self-measured: a three-tier exec/managerial/operational board derived from the sovereign planes, a dated growth series with daily, weekly and monthly deltas that ABSTAIN without a baseline (exceed), a one-sample series that refuses to trend (exceed), incidents as counts, retro-computed history mined from 1,863 anchored frames with a reconciling partition (exceed), a silent coordination plane that cannot read as zero work (exceed), the honest ROI ledger (exceed), money on the dated series with cost and value side by side (exceed), written laws mechanically detected and owner-joined (exceed), the MCP adoption gap as a tracked number, adoption as a first-class axis, per-lane RACI debt, the corridor-costing engine LIVE with 17 corridors, the inventory substrate wired with 9 importers, and R and D tracked as 706 frontier rungs. The West Industrial business half is PART LIVE: entity register, P and L and the external ingest lane are genuine gaps, and until the ingest lane lands every WI figure is honestly UNMEASURED.

Where we need to go. A growth surface an executive sponsor reads daily, weekly and monthly where the BUSINESS half is as measured as the capability half: external sources ingested, the firm's entities and products registered, revenue and margin per serviced business on the same dated series as capability growth -- and a catalogue that stops telling people to build libraries.

The unit. 1 u = one measured session-leg (estate calibration: graphics R21 in one leg 2026-08-15). Local evidence: gs_beat, gs_mine and gs_axis_finance each landed gated in one leg on 2026-08-15; estimates are relative to those.

Where we are: 5 open rungs. Capability half measured and exceeding; business half part live with three named ingest-dependent gaps. Counts measured at emit below this line.

Cost to honest catalogue verdicts: 0.5 u. GW1 cl_is_lib -- LANDED AND LIVE, verified 2026-08-25 against the PROMOTED nx_catalog (nx_catalog_lib, nx_fixq30_lib and nx_market_ladder_lib all return KIND LIB plus the importer-count guidance). The 2026-08-16 awaiting-promote claim was STALE; the rung read OPEN only because the CE2 extraction of 2026-08-23 moved the predicate into nx_catalog_lib.nx and renamed it from cat_is_lib to cl_is_lib, which is ABSENT-PROVEN corpus_complete=1 under the old name.

Cost to a tracked tool count: 0.5 u. GW2 gs_axis_tools carrying the nx_capsearch considered count as a series axis.

Cost to a measured business half: 6 u. GW3 the external ingest lane FIRST (every WI figure depends on it), then GW4 the entity and product register, then GW5 P and L per serviced business on the dated series.

Research bar. Jellyfish, LinearB, Swarmia is measured on engineering-intelligence boards, adoption as the leading metric. Theirs: the capability-half bar. Ours: already matched on the series axes; GW2 widens it.

Research bar. NetSuite and Odoo is measured on entity register, inventory, P and L per business unit. Theirs: the business-half bar. Ours: GW3 GW4 GW5 measured on this page.

16 of 23 capabilities measured|7 of them measured exceeds|7 open|coverage 695/1000|adoption 13 full / 3 partial

Layer 2 · Roadmap

Do this next — computed by the ranker, never chosen by a seat

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: the cheapest closures on this board, listed before any new work. Stamp: # asof=1787883530 domain=growth target_version=0.1 rungs=10 done=6 open=4 finish=0 ranker=nx_dr_ocm

#	Stage	Rung	Priority	Derivation
#1	0.1	Tool count as a series axis (GW2) gs_axis_tools	400	v=1 m=2 c=5
#2	later	External source ingest lane (GW3) wi_ingest	3666	v=11 m=2 c=6
#3	later	Entity and product register (GW4) wi_entity_plane	1600	v=8 m=1 c=5
#4	later	P and L per serviced business (GW5) wi_pl_plane	625	v=5 m=1 c=8

Critical path — contract, done-rule, executor, cost

Rung	Closes with	Definition of done (pre-declared)	Executor	Est.
Dated growth series (GS0)	gs_beat	Daily weekly monthly deltas with per-window observability -- LANDED 27/27	Organ	0 u
Retro-computed history (GS1) after GS0	gs_mine	1,863 anchored frames, partition reconciles -- LANDED	Organ	0 u
Money on the series (GS2) after GS0	gs_axis_finance	Cost and value side by side, the time-base mismatch named -- LANDED	Organ	0 u
Adoption axis (GS3) after GS0	gs_axis_adoption	506 permil over 38,953 defs from nx_adopt -- LANDED	Organ	0 u
Corridor costing (GS4)	lc_calc	17 live corridors, selftest 15/15 both ways -- LANDED	Organ	0 u
Catalogue LIB verdict (GW1)	cl_is_lib	nx_catalog reports a main()-less source as LIB with importer count instead of SOURCE-ONLY Build it; gate proves nx_inventory reads LIB importers=9 and a program still reads by binary presence	Organ	0.5 u
Tool count as a series axis (GW2) after GS0	gs_axis_tools	The nx_capsearch considered count carried per beat, abstaining when the search is unobservable rather than writing a permanent minus-one; gate proves a beat with the count present writes it and a beat without it writes nothing	Organ	0.5 u
External source ingest lane (GW3) after GS0	wi_ingest	A declared set of external sources (operator-named) pulled on the beat into a sovereign plane with provenance per row and a receipts partition that SUMS; gate proves one source round-trips with its as-of and a source that fails reads UNOBSERVED in the tier, never zero	Organ	2 u
Entity and product register (GW4) after GW3	wi_entity_plane	The family firm's first-party and client businesses with their digital and physical products as a plane (NOT the media entity dossier -- that organ's name invited this row and its content refuted it); gate proves a registered business resolves to its products and an unregistered id is refused	Organ	1.5 u
P and L per serviced business (GW5) after GW4	wi_pl_plane	Revenue and margin per business from GW3's ingested rows on the same dated series as the capability axes, through the finance stack's derived statements; gate proves a fixture month's P and L equals the ledger's income statement for that business and an unmeasured month reads UNMEASURED	Organ	2.5 u

Milestones

Milestone	Rungs	Cumulative
M1 · Honest catalogue and tool axis	GW1,GW2	1 u
M2 · Business data in	GW3	3 u
M3 · Business half measured	GW4,GW5	7 u

Layer 3 · Engineering

How this is scored. Every Nishi mark is measured: the generator reads the real organ source on disk and requires the implementing symbol to exist (no self-grading). A watching tag names the organ and symbol contracted to close a gap — the mark flips itself on the next compare beat when that workstream ships, and the comparewatch- plane row flips with it. The flip is necessary, not sufficient: it proves the symbol exists, never that the capability is good. The bar is the rung's pre-declared done-rule, proven by its gate — a symbol shipped without the behaviour behind it is a defect, and the flip is exactly what makes that defect visible instead of quiet. Competitor marks record documented capability presence — presence, not depth or scale. Adoption is measured too: every measured row carries where its organ stands on the estate's ladder (source → built → promoted → registered → invoked; libraries by importer reach minus validation importers; gates by the execution surfaces that run them). A row is fully adopted only at the top of its ladder; anything short is tagged partial with the exact remedy, so a build nobody promoted can no longer read as shipped. Census stamps: importers asof 1787849099, gate census asof 1787855507 (unix seconds; -1 = census absent).

Capability matrix — measured against source

◉ leads / measured exceed● present◐ partial○ absent · click any capability for its evidence

Capability	Nishi	Jellyfish	LinearB	Swarmia	NetSuite	Odoo
EXEC
three-tier exec/managerial/operational board Measured: `PB_CAP` exists in `runtime/_hdl_build/nx_pm_board.nx`, verified at emit. Built to the operator 2026-07-18 spec; derives every tier from the sovereign frontier, debt, work, raci and roi planes. Rivals ship exec dashboards too [dora] -- the sovereign difference is that no figure on this one is typed by a human Adoption: `REGISTERED-DARK` — PARTIAL: callable, authorised, no MCP invocation on record (a direct fork logs the runner, so this is not proof it never ran); no execution surface runs it either (clock, cron, daemon, roster, actlog and surfaced forks checked). adoption REGISTERED-DARK	●	●	●	●	●	●
dated growth series (the derivative, not the level) Measured exceed: `gs_beat` in `runtime/_hdl_build/nx_growth_series.nx`, verified at emit. SHIPPED 2026-08-15, selftest 27/27, first live row appended the same day. Nothing in the estate rolled any metric into daily/weekly/monthly deltas before this. CORRECTED TWICE THE SAME DAY, and the second correction retracts the first: nx_store_put load is a ROW-plane verb and the control settled it in one call -- the same verb on knowledge/store/roi- returns every row, which exonerates sts_load_fit, sts_load, ss_open and ss_open2 at once. ecomat simply is not a row plane. The real defect was the SENTENCE -- it said EMPTY when it meant NOT MY FORMAT, a false diagnosis wearing an authoritative name Adoption: `RUN-BY:clock` — fully adopted (top of its ladder).	◉	●	●	●	●	●
daily/weekly/monthly deltas with per-window observability Measured exceed: `gs_report` in `runtime/_hdl_build/nx_growth_series.nx`, verified at emit. Emits a GROWTH-DELTA block per window carrying its own observed flag. An axis with no baseline inside the window ABSTAINS rather than reporting zero change Adoption: `RUN-BY:clock` — fully adopted (top of its ladder).	◉	●	●	●	●	●
a one-sample series REFUSES to report a trend Measured exceed: `gs_observed` in `runtime/_hdl_build/nx_growth_series.nx`, verified at emit. Caught by this organ's own first live run, which compared a single row against itself and printed observed=1 with a delta of zero. Extracted to one predicate with three teeth. No rival surface refuses to trend a single data point; the common behaviour is to interpolate it Adoption: `RUN-BY:clock` — fully adopted (top of its ladder).	◉	○	○	○	○	○
incident posture as a COUNT, not 936 raw ids Measured: `gs_json_count` exists in `runtime/_hdl_build/nx_growth_series.nx`, verified at emit. nx_pm_board emits every sev>=7 incident id inline -- 936 of them on 2026-08-15. An executive tier that hands a sponsor 936 ids has reported nothing. The ids stay available to the operational tier. THAT INLINE LIST WAS ALSO THE ZERO-BYTE BUG: it was accumulated into a fixed 4096-byte page with no bounds check, 938 ids x 13 bytes = a 3x overflow, root-caused and fixed 2026-08-16 (debt 1786921263) Adoption: `RUN-BY:clock` — fully adopted (top of its ladder).	●	●	●	●	●	●
retro-computed history from already-dated sources Measured exceed: `gs_mine` in `runtime/_hdl_build/nx_growth_series.nx`, verified at emit. SHIPPED 2026-08-15, so the first weekly did not have to wait seven days. Full-population mine of ws_sync.jrnl: 1433348 bytes, 1863 anchored frames, 27-day span, coverage_complete=1, and the partition kickoff 556 + beat 432 + done 724 + reaped 57 + other 94 = 1863 RECONCILES against the frame count Adoption: `RUN-BY:clock` — fully adopted (top of its ladder).	◉	●	●	●	●	●
a silent coordination plane cannot read as zero work Measured exceed: `gs_mine_scan` in `runtime/_hdl_build/nx_growth_series.nx`, verified at emit. MEASURED 2026-08-15 and the reason the workstream story did not match the investment: ws_sync.jrnl's newest frame is 3.3 days old, and DONE frames fell from 149 on the peak day to 3 across the last seven. That is a SELF-REPORTED plane going quiet, not the estate stopping. Every window therefore publishes days_covered_by_journal, so a gap in reporting can never be rendered as a measured zero Adoption: `RUN-BY:clock` — fully adopted (top of its ladder).	◉	○	○	○	○	○
OPS
honest ROI ledger, every row tagged MEASURED or ESTIMATE Open — no implementing organ is measured for this axis yet. pm_roi.data carries money, energy and time with a named assumption per row and a conservative floor; SET-ME rows surface as needs_decision rather than being invented. The rival norm is a confident single number with no basis attached	○	◐	◐	◐	●	●
cost flow reconciled against value stock Open — no implementing organ is measured for this axis yet. roi-effcost measured 57744 USD of 7-day model spend against a 69-138k labor-equivalent stock, and NAMES the time-base mismatch as the open reconciliation instead of netting the two into a flattering number	○	●	●	●	●	●
EXEC
money on the dated series, cost and value side by side Measured exceed: `gs_axis_finance` in `runtime/_hdl_build/nx_growth_series.nx`, verified at emit. SHIPPED 2026-08-15. Four finance axes ride the same 6h beat as the capability axes, composed from nx_eff_board -- no figure here is authored. LIVE ROW: cost_per_action_cents=214, cache_hit_pct=96, monthly_cost_cents=24747471, monthly_value_cents=21800. CARRYING BOTH IS THE POINT: 247475 USD per month of cost beside 218 USD per month of recorded value is not a loss, it is an UNMEASURABLE return, because a labor-equivalent value STOCK is never amortized against a monthly cost FLOW -- a time-base mismatch nx_eff_board names itself and nothing has reconciled. Publishing one without the other would be the made-up number Adoption: `RUN-BY:clock` — fully adopted (top of its ladder).	◉	●	●	●	○	○
MGMT
written laws mechanically detected, every one owner-joined Measured exceed: `gs_axis_laws` in `runtime/_hdl_build/nx_growth_series.nx`, verified at emit. SHIPPED 2026-08-15, composing nx_law_warden, which was on NO BEAT. LIVE: laws_breached=9 of 11, breach_weight_permil=807, enforced_permil=1000, laws_unowned=0. Rivals score services against templates; nothing in the field detects breaches of a house constitution and routes each to an accountable role. Trended rather than judged, because ADDING a law RAISES the breach count -- that is the surface widening, not the estate degrading, and only laws_total separates the two Adoption: `RUN-BY:clock` — fully adopted (top of its ladder).	◉	○	○	○	○	○
the MCP adoption gap as a tracked number Measured: `gs_axis_laws` exists in `runtime/_hdl_build/nx_growth_series.nx`, verified at emit. L003 measured live: 977 of 1926 shipped .elf organs are absent from the tool allowlist -- a capability that exists and that nobody can call. That is 507 permil, and nx_adopt independently reports 506 permil adoption from a completely different method (source-level external callers over 38953 defs). TWO INSTRUMENTS THAT AGREE ON A NUMBER NEITHER COULD PRODUCE ALONE. Owner role: librarian Adoption: `RUN-BY:clock` — fully adopted (top of its ladder).	●	●	●	●	○	○
OPS
the efficiency lever is named by the data, not by taste Open — no implementing organ is measured for this axis yet. Cache read plus write are 7757723 + 3845175 of 5774410 window cents at a 96 percent hit ratio, so context and cache management is the lever and output brevity is not. The board says so from its own token classes rather than from an opinion	○	●	●	●	○	○
MGMT
per-lane RACI open debt and open work Measured: `PB_MAXCOL` exists in `runtime/_hdl_build/nx_pm_board.nx`, verified at emit. 24 lanes derived from the raci- plane, each with an accountable owner Adoption: `REGISTERED-DARK` — PARTIAL: callable, authorised, no MCP invocation on record (a direct fork logs the runner, so this is not proof it never ran); no execution surface runs it either (clock, cron, daemon, roster, actlog and surfaced forks checked). adoption REGISTERED-DARK	●	●	●	●	●	●
EXEC
registered-tool and capability count as a series axis Open — watching `runtime/_hdl_build/nx_growth_series.nx` : `gs_axis_tools`, re-measured on every compare beat. Ship that symbol and this mark flips itself; the `comparewatch-` plane row flips with it. WATCH gs_axis_tools: carry the nx_capsearch considered count (1082 on 2026-08-15, 937-946 on 2026-08-07) as a tracked axis. Deliberately NOT shipped as an always-minus-one column, because a field that is permanently absent reads as evidence watching gs_axis_tools	○	○	○	○	○	○
OPS
adoption as a first-class tracked axis Measured: `gs_axis_adoption` exists in `runtime/_hdl_build/nx_growth_series.nx`, verified at emit. SHIPPED 2026-08-15 and deliberately NOT claimed as an exceed -- Jellyfish [jellyfish], LinearB [linearb] and Swarmia [swarmia] lead this axis and we have merely reached it. Added on EXTERNAL ground truth rather than taste [space2021]: the 2026 platform-engineering consensus makes adoption THE leading metric, with roughly 70pc of platform initiatives failing to reach meaningful adoption. MEASURED HERE by composing the estate's own nx_adopt census: ADOPTION_PERMIL=506 over defs=38953, DARK_total=19224 with zero external callers, PROVEN_UNWIRED=5114 gate-proven capabilities with zero production callers -- built and gated and never called, which scores as done and behaves as absent. nx_adopt was ITSELF REGISTERED-DARK when this axis was wired: the organ that measures adoption had never been adopted Adoption: `RUN-BY:clock` — fully adopted (top of its ladder).	●	●	●	●	○	○
WI
entity and product register (digital and physical) Open — watching `_ABSENT_` : `wi_entity_plane`, re-measured on every compare beat. Ship that symbol and this mark flips itself; the `comparewatch-` plane row flips with it. WATCH wi_entity_plane: the family firm servicing first-party AND client businesses, digital and physical product. STILL A GENUINE GAP, and worth saying why: nx_entity_dossier is LIVE and its name invites exactly this row, but reading it shows a media/content entity landing page served off the docportal search daemon -- not a business register. INFERRING A SUBJECT FROM AN ORGAN'S NAME IS HOW A GAP GETS CLOSED ON PAPER AND NOWHERE ELSE. NetSuite [netsuite-docs] and Odoo [odoo-docs] are the honest bar here, not the engineering-intelligence columns watching wi_entity_plane	○	●	○	○	◉	◉
import and export corridor costing Measured: `lc_calc` exists in `runtime/_hdl_build/nx_landed_cost.nx`, verified at emit. CORRECTED 2026-08-16 -- this row said UNMEASURED and that was WRONG. nx_landed_cost is LIVE and INVOKED, selftest 15/15 GREEN integer-exact with every tooth proven BOTH WAYS (col2/col1 switch, per-corridor preference eligibility, sanctions-bypass regression, domestic origin, country-scoped 301). It computes duty plus MPF at 0.3464pc floored 33.58 and capped 651.50 [cbp-fees-fy2026], HMF 0.125pc ocean-only, Section 232 and 301. AND THE DATA EXISTS: knowledge/store/corridor- carries 17 live corridors read in full -- vn by ru uz kz kg ge am md ke gh et eu cn mx ca us -- each with tariff column, sanctions status, preference regime and a diligence note (Belarus finance-open freight-walled; AGOA window lapsing; USMCA duty-free only if rules of origin are met; us present as a RANKABLE domestic option rather than an unmodeled blank) Adoption: `LIVE` — fully adopted (top of its ladder).	●	○	○	○	◉	◉
inventory and bill-of-materials substrate Measured: `iv_add` exists in `runtime/_hdl_build/nx_inventory.nx`, verified at emit. CORRECTED TWICE, and the second correction retracts the first. I published that nx_inventory DOES NOT BUILD and called it breakage. FALSE: the answer is the first word of the file, nx_inventory.nx -- LIB. It has no main() among its 29 declarations, so A LIB HAS NO BINARY BY DESIGN and two failed /api/build attempts were me asking a library to be a program. It is WIRED, not dark: 9 importers, four of them gates -- nx_household, nx_household_gate, nx_pantry_meal_gate, nx_reorder_gate, nx_shopping, nx_meal_plan, nx_pantry, nx_estate, nx_estate_gate. THE REAL STATE IS ADOPTION, NOT ABSENCE: three consumer gates are BUILT and PROMOTED (reorder 295760 B, household 308404 B, estate 264052 B) and five consumer programs are SOURCE-ONLY. nx_reorder_gate and nx_household_gate were PROMOTED-UNREGISTERED, real binaries nobody could call, and were REGISTERED 2026-08-16 -- whereupon BOTH hung after their banner, which is why the adoption metric should count INVOKED-AND-COMPLETED rather than registered (debt 1786918553) Adoption: `LIB-WIRED importers=9 nonval=5` — fully adopted (top of its ladder).	●	○	○	○	◉	◉
a catalogue verdict that tells you to build a library Measured: `cl_is_lib` exists in `runtime/nx_catalog_lib.nx`, verified at emit. WATCH cat_is_lib (organ path CORRECTED 2026-08-16 -- it named nx_inventory, the SUBJECT, while the symbol lives in nx_catalog, the JUDGE, so this contract could never have flipped; A WATCH THAT POINTS AT THE WRONG ORGAN IS A CONTRACT NOBODY CAN FULFIL AND IT READS AS UNBUILT FOREVER). LANDED AND LIVE, VERIFIED 2026-08-25: the PROMOTED nx_catalog was run on three main()-less libs (nx_catalog_lib, nx_fixq30_lib, nx_market_ladder_lib) and all three returned KIND LIB plus VERDICT LIB naming IMPORTER COUNT as the adoption question, so the 2026-08-16 AWAITING PROMOTE claim is STALE and is corrected here. THE ROW COULD NOT FLIP BECAUSE THE CE2 EXTRACTION OF 2026-08-23 MOVED THE PREDICATE INTO nx_catalog_lib.nx AND RENAMED IT cl_is_lib; cat_is_lib is ABSENT-PROVEN over buildroot/runtime with corpus_complete=1. A WATCH ROW GOES STALE BY REFACTOR, AND THIS IS THE SECOND TIME THIS SAME ROW WAS UNFULFILLABLE -- first by organ path in 2026-08-16, now by symbol name. Historic: nx_catalog reported a main()-less LIB as SOURCE-ONLY (S2) with the instruction Build it. That is a FALSE INSTRUCTION WITH AN AUTHORITATIVE NAME -- it sent me to run two builds and then publish a breakage claim about a library that was working correctly. The estate already banks the law it violates: before reporting something MISSING, check whether it was ever supposed to exist, a lib has no binary by design. The fix is one predicate -- absence of main() -> verdict LIB, and for a lib the adoption question is IMPORTER COUNT, not binary presence Adoption: `LIB-WIRED importers=5 nonval=5` — fully adopted (top of its ladder).	●	○	○	○	○	○
client and first-party business P and L Open — watching `_ABSENT_` : `wi_pl_plane`, re-measured on every compare beat. Ship that symbol and this mark flips itself; the `comparewatch-` plane row flips with it. WATCH wi_pl_plane: revenue and margin per serviced business. UNMEASURED until an ingest lane exists. A fabricated constant here would be worse than a blank, because it would wear the shape of a measurement watching wi_pl_plane	○	○	○	○	◉	◉
external source ingest lane Open — watching `_ABSENT_` : `wi_ingest`, re-measured on every compare beat. Ship that symbol and this mark flips itself; the `comparewatch-` plane row flips with it. WATCH wi_ingest: the operator named external sources as the real data home for the business half. Until this lands every WI row above is honestly UNMEASURED and the executive tier must say so rather than render zeros watching wi_ingest	○	●	●	●	◉	◉
research and innovation pipeline as tracked work Measured: `PB_OUT` exists in `runtime/_hdl_build/nx_pm_board.nx`, verified at emit. The frontier plane already tracks R and D as 706 rungs with owners and a critical path; the West Industrial half inherits that tracker rather than starting a second one Adoption: `REGISTERED-DARK` — PARTIAL: callable, authorised, no MCP invocation on record (a direct fork logs the runner, so this is not proof it never ran); no execution surface runs it either (clock, cron, daemon, roster, actlog and surfaced forks checked). adoption REGISTERED-DARK	●	●	●	●	●	●

Risk register

Risk	Likelihood x impact	Mitigation
A WI figure rendered before the ingest lane exists is a fabricated constant wearing the shape of a measurement	certain x high	GW4 and GW5 depend on GW3 by declaration; the tier renders UNMEASURED until then.
An organ whose name matches the row gets wired as the capability	possible x high	Every WI rung's done-rule reads the subject's content, never its name (the entity-dossier lesson is in the matrix).

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 is capability presence measured against source — not depth, scale, or polish, where mature rivals may lead. Exceeds are claimed only where a mechanism backs them. Every open gap is a watch contract: it names the organ and symbol that closes it, and this page flips the cell itself when that workstream ships.

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

Every compare carries this layer. Declare knowledge/compare/growth.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 growth, 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).

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.

[jellyfish] Jellyfish. Jellyfish -- engineering management platform: DORA and SPACE-style delivery metrics, allocation and investment reporting (product surface), accessed 2026-08-18. publisher · read in our library knowledge/fetched/cmp_growth_jellyfish.html · pin h44a46277adf793652d2c83a0f8a69438a495a0d10ad5f00cfd0a29d7782979cd · accessed 2026-08-18 · vendor-docGrounds: The Jellyfish column: Yes across the EXEC board, growth-series and 'OPS: adoption as a first-class tracked axis' rows -- one of the three engineering-intelligence products the header names as the bar we merely reach on adoption.
[linearb] LinearB. LinearB -- software engineering intelligence: DORA metrics, cycle-time and PR-flow analytics, workflow automation (product surface), accessed 2026-08-18. publisher · read in our library knowledge/fetched/cmp_growth_linearb.html · pin h756712b7be6a2a7e141e93fadeec7fe55e4923d974f59be664d2655c716034e7 · accessed 2026-08-18 · vendor-docGrounds: The LinearB column: Yes on the executive-tier and adoption rows and 0 on the West Industrial rows -- engineering-intelligence tooling, not business-ops, exactly as the header partitions the columns.
[swarmia] Swarmia. Swarmia -- engineering effectiveness platform: DORA metrics, working agreements, investment balance and developer-experience surveys (product surface), accessed 2026-08-18. publisher · read in our library knowledge/fetched/cmp_growth_swarmia.html · pin h0a6a665525d56f707d312c63ea5345cf1df0289beded730fa85b151707bc105b · accessed 2026-08-18 · vendor-docGrounds: The Swarmia column: the third engineering-intelligence bar; Yes on the EXEC and adoption rows, 0 on 'EXEC: a one-sample series REFUSES to report a trend' -- the note observes no rival surface refuses to trend a single point.
[netsuite-docs] Oracle. NetSuite documentation -- Get Started (Oracle Help Center): the cloud ERP for financials, inventory, order management and reporting, accessed 2026-08-18. The netsuite.com product page answers 403 to the sovereign fetcher, so the Help Center is the mirrored primary. publisher · read in our library knowledge/fetched/cmp_growth_netsuite-docs.html · pin h8d8fc8f0b20e6175a11f7846493b84156ef43394ad98bf39a12a4c23a6c9ebb7 · accessed 2026-08-18 · vendor-docGrounds: The NetSuite column: Best on 'WI: entity and product register', 'WI: import and export corridor costing', 'WI: inventory and bill-of-materials substrate' and 'WI: client and first-party business P and L' -- the business-ops/ERP bar the header says the West Industrial half must be measured against.
[odoo-docs] Odoo S.A. Odoo documentation -- user, developer and administration docs for the open-source ERP (accounting, inventory, MRP, CRM), accessed 2026-08-18. publisher · read in our library knowledge/fetched/cmp_growth_odoo-docs.html · pin h88df823b3f978ad33b9147136a9349b26b70946d7e00c8c1b3dae15a7d103f5a · accessed 2026-08-18 · vendor-docGrounds: The Odoo column: Best on the same WI rows as NetSuite (entity register, corridor costing, inventory/BOM, P and L) -- the open-source ERP comparator for the family-firm half of the page.
[dora] DORA (DevOps Research and Assessment). dora.dev -- the four key software-delivery metrics (lead time, deployment frequency, change fail rate, time to restore) and the annual State of DevOps research program, accessed 2026-08-18. publisher · read in our library knowledge/fetched/cmp_growth_dora.html · pin hd23da56ac392b5f718a6fa6aea341e58b324a770746116b28e626fab5394dc79 · accessed 2026-08-18 · published-paperGrounds: The engineering-intelligence axis the Jellyfish, LinearB and Swarmia columns are graded on: their exec dashboards report DORA metrics, which is the yardstick behind the 'EXEC: three-tier exec/managerial/operational board' and 'EXEC: dated growth series' comparisons.
[space2021] Forsgren, Storey, Maddila, Zimmermann, Houck, Butler. The SPACE of Developer Productivity: There's more to it than you think. ACM Queue 19(1), 2021. publisher · read in our library knowledge/fetched/cmp_growth_space2021.html · pin hcb70ed85b0c9bf4dd8e477804fa4b7a0b1432350355fa61c491d6776e945070e · accessed 2026-08-18 · published-paperGrounds: The 'OPS: adoption as a first-class tracked axis' and 'MGMT: the MCP adoption gap as a tracked number' rows: SPACE is the published framework that says a single productivity number is a mistake, which is why this page trends adoption, laws and finance side by side rather than one score.
[cbp-fees-fy2026] U.S. Customs and Border Protection. Customs User Fees To Be Adjusted for Inflation in Fiscal Year 2026 (CBP Dec. 25-10), Federal Register, 2025-07-23 (FR Doc. 2025-13869): merchandise processing fee minimum 33.58 USD and maximum 651.50 USD at the 0.3464 percent ad valorem rate, effective 2025-10-01. publisher · read in our library knowledge/fetched/cmp_growth_cbp-fees-fy2026.html · pin h216b5ef6c27fa07a0fef87bb4a80bd55727122ba7cbd63ec9322533bd2a32abd · accessed 2026-08-18 · published-standardGrounds: The 'WI: import and export corridor costing' row: the MPF at 0.3464 percent floored 33.58 and capped 651.50 that nx_landed_cost computes integer-exact are this notice's FY2026 figures, so the row's constants are traceable to the regulator rather than typed.

generated by nx_swcompare_matrix (sovereign NishiLang organ) from knowledge/compare/growth.matrix · every Nishi cell verified against organ source at emit time · watch cells re-measured on every compare beat · zero JS, zero trackers