Nishi Family › Compare › Project Management and Team Coordination

Nishi Compare · capabilities, evidence and delivery

Project Management and Team Coordination

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

Nishi vs Microsoft Project and Leantime and Asana and OpenProject

Overview

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

Where we are. Measured 2026-08-19. The engine is deep where MS Project is deep -- critical path, EVM, leveling, baselines, risk, time tracking, templates, a contractor portal -- and exceeds on sovereignty, a concurrent-durable additive store measured against git, liveness heartbeats and autonomous dispatch. The 13 absent rows are the everyday PM surface the majors ship: dependency types, recurrence, fields, tags, attachments, approvals, import, dashboards, skills, RCPSP, collaboration, mobile and AI planning.

Where we need to go. Finish the schedule algebra first (it is the dependency of import and RCPSP), then the task surface, then reporting, then the resourcing frontier and reach -- composing the office CRDT, the workflow approvals and the versioned doc store rather than building seconds.

The unit. 1 u = one measured session-leg. Calibration from landed rungs: the mangagen panel compositor went from existing substrate to shipped and live-verified in ONE leg (2026-08-13); the citations rung went from 3 to 55 domains in one leg across seven seats (2026-08-18); a greenfield engine with a bite-proven gate has measured 2 to 4 legs. Estimates recalibrate as rungs land and PR7 actuals write back.

Cost to schedule algebra: 2.5 u. Through M0.

Cost to production parity: 10 u. Through M2: task richness, import and dashboards.

Cost to the frontier: 21.5 u. Everything below. RCPSP and the mobile shell are the long poles.

Risk evidence owner: runtime/nx_project.nx PROJECT-RISK. Reuse existing task register and WCONF. Fields: tid,due,days_left,chain_min,days_needed,slack,level; levels derive from recorded schedule data. Missing WCONF stays UNRATED, never zero risk. Generic probability, impact and mitigation are NOT implemented by this schedule-risk owner.

Risk to PM join contract: NEEDS_BINDING. Join project_id/task_id to RACI activity and exactly one accountable owner using nx_raci_sov; preserve risk source SHA, observed_at, evidence age, deciding gate, reason and next_action. Missing owner or stale evidence yields NEEDS_EVIDENCE, not a fabricated assignment. Existing nx_pm_cockpit investment-json resolves activity ownership only; risk ownership remains UNBOUND until this join is implemented and tested.

Risk and investment inputs: BACKLOG_ONLY. Compose existing nx_pm_cockpit, nx_eff_board and nx_workmix; preserve expected value, effort, elapsed, rework, resource cost, opportunity cost, confidence, horizon and measured outcome with units and UNKNOWN states. Rank inputs remain deficit, cost-of-delay, enablement, dependency momentum, estimate, sponsorship and sovereignty ledger. Risk is evidence for an authorized decision, not an invented multiplier. Workmix deci-u is not seconds and rank ordinal is not money; realized ROI remains null without accepted outcome evidence.

Release evidence contract: NEEDS_EVIDENCE. Carry affected artifact SHA, release cycle and predecessor, native gate job/exit, evidence scope and served review state. Component success never proves served or product acceptance. Controlled Alpha may expose RED with provenance, reproduction, owner and next action; Beta requires integrated evidence; Production requires served experience and rights acceptance. Feedback creates a new versioned cycle.

PM risk integration acceptance: OPEN. Existing projectmgmt and pmdash PR5/PR7/PR8/PR9 remain owners. Qualify actual risk extraction, task-to-RACI identity, missing-owner and stale-evidence refusals, additive replay, investment unit preservation and no promotion from component-only evidence. Beach remains the active pilot; captured feedback is BACKLOG_ONLY and does not authorize reranking. Run nx_compare_rank projectmgmt --artifact-only for contract checks.

Measured PM effectiveness and higher-value human work: PLANNED via pmdash:PR21. Operator 2026-09-30: existing scheduling, skills matching, approvals and LLM planning participate in the same estate-wide RACI/evidence contract. Compare human PM, Nishi PM and partnership through the shared pmdash:PR21 and codeeffectiveness:CE12 outcome instruments, not a second project-management ruler. Retain quality, time, organizational value, resource constraints and uncertainty; any human-talent shift is an accountable recommendation supported by outcomes.

Latest recorded release

No valid dated release entry is recorded for this domain.

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

33 of 46 capability source symbols found|5 of them authored stronger-claims|13 open|coverage 717/1000|adoption 28 full / 5 partial

Evidence profile — what the gaps on this board actually are

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

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

partition: grounded + unsupported = 33 vs present 33 · named + unnamed + withheld = 13 vs open 13 · both reconcile

liar-kill conj=GPQN · all four conjuncts held

graded document: BUILDROOT tree, 8419 bytes · gates map: PRIMARY · stamped 0d 13h ago · source ../knowledge/status/evstamp_projectmgmt.verdict

Gap class	What it is, and the work it names
NONE	No gap class fires on this board: every published claim is grounded, the declared gates ran and were green, no watch contract is unnamed or already landed, and the stamp is inside its TTL. That is a statement about evidence, not about depth, scale or polish.

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 projectmgmt 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: STALE_OR_INVALID_BINDING. Recorded priorities require current acceptance evidence and resource checks before execution.

Recorded ranking withheld

Retained ranking is not bound to the current plan and matrix: STALE_OR_INVALID_BINDING. Historical data remains retained. Refresh the ranking after resolving the input differences. Latest execution outcome is unverified.

Declared roadmap — contract, acceptance, executor, effort

Rung	Closes with	Definition of done (pre-declared)	Executor	Est.
Dependency algebra: FS SS FF plus lead and lag (R0)	pd_schedule	The scheduler honours all four dependency types with lead and lag on the critical-path DP; a banked MS Project sample schedules to the same dates; cycle detection stays loud	Organ	1.5 u
Recurring tasks (R1)	pr_expand	Native task recurrence as a rule row expanded into dated task records on load (the calendar RRULE parser is composed, never copied); the next occurrence is never double-created	Organ	1 u
Custom fields (R2)	pf_set	User-defined typed attributes per task stored as additive records and rendered on the portal; a field schema is data	Organ	1 u
Tags and saved filters (R3) after R2	pt_filter	Tags as additive records; saved views as named filter rows; the portal lists by tag and view	Organ	1 u
Attachments on tasks (R4)	pat_put	A task carries content-addressed attachments through the versioned doc store already shipped; download is ReBAC-gated like sharing	Organ	1 u
Approval and sign-off gates (R5)	pap_gate	Stage gates as DENY-WINS approvals composed from the workflow domain; a task cannot move past a gate without the accountable role's recorded approval	Organ	1 u
CSV and MS Project import (R6) after R0	pim_load	A CSV and an MS Project XML plan import into dated task files; the imported plan schedules identically to its source on the sample	Organ	1.5 u
Custom dashboards and report builder (R7) after R2,R3	pds_emit	Report definitions as data rows (which records, which grouping, which chart) rendered on the portal; burndown, velocity and cumulative flow are the first three reports	Organ	2 u
Multi-skill resource matching (R8)	psk_match	Assignment by declared skills and availability, not capacity alone; the leveling loop consumes the match	Organ	1.5 u
Resource-constrained multi-mode scheduling (R9) after R0,R8	prc_solve	An RCPSP solver over modes and resource limits with a PSPLIB instance as the oracle; makespan within a PRE-DECLARED permille of the published best-known	Organ	3 u
Real-time collaborative editing (R10)	pco_sync	Task text and plan rows synced live through the RGA CRDT and sync daemon already proven in the office domain; two concurrent clients converge	Organ	2 u
Mobile shell (R11)	pmo_shell	A sovereign mobile shell (the browser-WASM worker and NXE germination precedent) for the portal with offline view of assigned tasks; graded by the UI judge	Organ	3 u
LLM planning assistant (R12) after R0	pai_plan	Natural-language plan generation into task files on the sovereign seat; every generated dependency is schedule-checked before it is written; quality graded by the referee	Local model	2 u

Milestones

Milestone	Rungs	Cumulative
M0 · Schedule algebra	R0,R1	2.5 u
M1 · Task richness	R2,R3,R4,R5	6.5 u
M2 · Reporting and import	R6,R7	10 u
M3 · Resourcing frontier	R8,R9	14.5 u
M4 · Collaboration and reach	R10,R11,R12	21.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
Class	Count	Note
bars	0	sotabar rows on the plan
fresh	0	the bar month is the current month
attested	0	an older bar with a this-month barscan reporting no newer entry
stale	0	a this-month scan saw a newer month the bar ignores
unattested	0	nobody looked this month
malformed	0	a sotabar row missing a field
duplicate	0	bar ids an earlier row already carries
bars, summed	0	RECONCILED: the parts sum to the total 0
current month	2026-10	the month every bar is judged against

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

Inspect a rung and its prerequisites

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

Plan SHA-256 ea86791464f6632a3a8deacfdd8fcae160d22f765e6b88381212fd7f5f3da55f. 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 13 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.

R0 — Dependency algebra: FS SS FF plus lead and lag
Prerequisites: None declared; this does not establish execution eligibility.
Contract: pd_schedule
Acceptance: The scheduler honours all four dependency types with lead and lag on the critical-path DP; a banked MS Project sample schedules to the same dates; cycle detection stays loud
Authored effort: 1.5. Executor kind: Organ. Responsible, accountable and verifier not established. Inspect retained worklog.
Runtime observation: UNKNOWN; outcome UNKNOWN; observed epoch -1. Declared owner: . Receipt , SHA-256 . Identity-bound observation is not accepted completion. Qualification and deployment remain unverified by this projection.
R1 — Recurring tasks
Prerequisites: None declared; this does not establish execution eligibility.
Contract: pr_expand
Acceptance: Native task recurrence as a rule row expanded into dated task records on load (the calendar RRULE parser is composed, never copied); the next occurrence is never double-created
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.
R2 — Custom fields
Prerequisites: None declared; this does not establish execution eligibility.
Contract: pf_set
Acceptance: User-defined typed attributes per task stored as additive records and rendered on the portal; a field schema is data
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.
R3 — Tags and saved filters
Prerequisites: R2 (acceptance unverified)
Contract: pt_filter
Acceptance: Tags as additive records; saved views as named filter rows; the portal lists by tag and view
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.
R4 — Attachments on tasks
Prerequisites: None declared; this does not establish execution eligibility.
Contract: pat_put
Acceptance: A task carries content-addressed attachments through the versioned doc store already shipped; download is ReBAC-gated like sharing
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.
R5 — Approval and sign-off gates
Prerequisites: None declared; this does not establish execution eligibility.
Contract: pap_gate
Acceptance: Stage gates as DENY-WINS approvals composed from the workflow domain; a task cannot move past a gate without the accountable role's recorded approval
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.
R6 — CSV and MS Project import
Prerequisites: R0 (acceptance unverified)
Contract: pim_load
Acceptance: A CSV and an MS Project XML plan import into dated task files; the imported plan schedules identically to its source on the sample
Authored effort: 1.5. Executor kind: Organ. Responsible, accountable and verifier not established. Inspect retained worklog.
Runtime observation: UNKNOWN; outcome UNKNOWN; observed epoch -1. Declared owner: . Receipt , SHA-256 . Identity-bound observation is not accepted completion. Qualification and deployment remain unverified by this projection.
R7 — Custom dashboards and report builder
Prerequisites: R2 (acceptance unverified), R3 (acceptance unverified)
Contract: pds_emit
Acceptance: Report definitions as data rows (which records, which grouping, which chart) rendered on the portal; burndown, velocity and cumulative flow are the first three reports
Authored effort: 2. Executor kind: Organ. Responsible, accountable and verifier not established. Inspect retained worklog.
Runtime observation: UNKNOWN; outcome UNKNOWN; observed epoch -1. Declared owner: . Receipt , SHA-256 . Identity-bound observation is not accepted completion. Qualification and deployment remain unverified by this projection.
R8 — Multi-skill resource matching
Prerequisites: None declared; this does not establish execution eligibility.
Contract: psk_match
Acceptance: Assignment by declared skills and availability, not capacity alone; the leveling loop consumes the match
Authored effort: 1.5. Executor kind: Organ. Responsible, accountable and verifier not established. Inspect retained worklog.
Runtime observation: UNKNOWN; outcome UNKNOWN; observed epoch -1. Declared owner: . Receipt , SHA-256 . Identity-bound observation is not accepted completion. Qualification and deployment remain unverified by this projection.
R9 — Resource-constrained multi-mode scheduling
Prerequisites: R0 (acceptance unverified), R8 (acceptance unverified)
Contract: prc_solve
Acceptance: An RCPSP solver over modes and resource limits with a PSPLIB instance as the oracle; makespan within a PRE-DECLARED permille of the published best-known
Authored effort: 3. Executor kind: Organ. Responsible, accountable and verifier not established. Inspect retained worklog.
Runtime observation: UNKNOWN; outcome UNKNOWN; observed epoch -1. Declared owner: . Receipt , SHA-256 . Identity-bound observation is not accepted completion. Qualification and deployment remain unverified by this projection.
R10 — Real-time collaborative editing
Prerequisites: None declared; this does not establish execution eligibility.
Contract: pco_sync
Acceptance: Task text and plan rows synced live through the RGA CRDT and sync daemon already proven in the office domain; two concurrent clients converge
Authored effort: 2. Executor kind: Organ. Responsible, accountable and verifier not established. Inspect retained worklog.
Runtime observation: UNKNOWN; outcome UNKNOWN; observed epoch -1. Declared owner: . Receipt , SHA-256 . Identity-bound observation is not accepted completion. Qualification and deployment remain unverified by this projection.
R11 — Mobile shell
Prerequisites: None declared; this does not establish execution eligibility.
Contract: pmo_shell
Acceptance: A sovereign mobile shell (the browser-WASM worker and NXE germination precedent) for the portal with offline view of assigned tasks; graded by the UI judge
Authored effort: 3. Executor kind: Organ. Responsible, accountable and verifier not established. Inspect retained worklog.
Runtime observation: UNKNOWN; outcome UNKNOWN; observed epoch -1. Declared owner: . Receipt , SHA-256 . Identity-bound observation is not accepted completion. Qualification and deployment remain unverified by this projection.
R12 — LLM planning assistant
Prerequisites: R0 (acceptance unverified)
Contract: pai_plan
Acceptance: Natural-language plan generation into task files on the sovereign seat; every generated dependency is schedule-checked before it is written; quality graded by the referee
Authored effort: 2. Executor kind: Local model. 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 projectmgmt 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.

R0 Dependency algebra: FS SS FF plus lead and lag · cell WATCHING · gate NO-GATE-DECLARED

Contract	`pd_schedule` · executor Organ · 1.5 u · stands on nothing
Definition of done	The scheduler honours all four dependency types with lead and lag on the critical-path DP; a banked MS Project sample schedules to the same dates; cycle detection stays loud
Matrix cell	Lead / lag + dependency types (FS/SS/FF) · `runtime/nx_project_deptype.nx` · WATCHING decl
Gate	NO-GATE-DECLARED — `knowledge/organ_gate.conf` carries no row for `nx_project_deptype`; declare `nx_project_deptype TAB <gate>` and the ship loop proves it and the verdict lands here.
Work log	2026-09-12 requirement OPERATOR ECONOMIC VALUE 2026-09-12: measure capability growth in dollars, elapsed and active time, opportunity cost and realized user value, alongside depth/breadth and current frontier qualification. Extend existing pm_roi.data and projectmgmt/finance owners; do not create a second value ledger. Separate cash marginal expense, allocated subscription/hardware/energy/storage, human effort and agent cached/uncached input/output plus tool/review/rejected-work overhead. Avoided spend is realized only when a genuinely needed equivalent purchase is displaced; capability presence or competitor list price is not savings. Value must be net of operation/maintenance and quality differences. Forecasts carry horizon, assumption owner, ranges and dated baselines; payback/ROI use the same horizon and net-benefit denominator; zero or unknown investment does not produce infinite ROI. Opportunity cost names the best feasible alternative foregone under current dependencies and resources, and is shown separately to avoid double counting labor or benefits. Shared capability costs allocated once, reuse recorded per accepted workflow, portfolio totals deduplicated. Existing pm_roi.data estimates remain historical UNREVALIDATED: static SaaS labels, assumed40W NAS and extrapolated manual hours do not prove realized savings. No new dollar value or positive ROI claimed today. 2026-09-12 requirement One-call domain pilot must connect existing nx_plan_run data workflows, nx_product_decompose, nx_capsearch, nx_compare_rank, nishi_crew and scoped Compare publisher through verified bindings. Existing decompose substring matching is a gap, not a semantic requirement oracle. Track source/owner coverage, prerequisite depth, representative tested breadth, matched competitor baselines, uncertainty and economic actuals per accepted outcome. Elder AI/Media Manager/Companion recovery uses existing gen/media/companionchat boards; same workflow must also qualify a new-domain target. No new orchestrator or autonomous completion claim.

R1 Recurring tasks · cell WATCHING · gate NO-GATE-DECLARED

Contract	`pr_expand` · executor Organ · 1 u · stands on nothing
Definition of done	Native task recurrence as a rule row expanded into dated task records on load (the calendar RRULE parser is composed, never copied); the next occurrence is never double-created
Matrix cell	Recurring tasks (native repeat) · `runtime/nx_project_recur.nx` · WATCHING decl
Gate	NO-GATE-DECLARED — `knowledge/organ_gate.conf` carries no row for `nx_project_recur`; declare `nx_project_recur TAB <gate>` and the ship loop proves it and the verdict lands here.
Work log	no log row names this rung yet

R2 Custom fields · cell WATCHING · gate NO-GATE-DECLARED

Contract	`pf_set` · executor Organ · 1 u · stands on nothing
Definition of done	User-defined typed attributes per task stored as additive records and rendered on the portal; a field schema is data
Matrix cell	Custom fields per task · `runtime/nx_project_fields.nx` · WATCHING decl
Gate	NO-GATE-DECLARED — `knowledge/organ_gate.conf` carries no row for `nx_project_fields`; declare `nx_project_fields TAB <gate>` and the ship loop proves it and the verdict lands here.
Work log	no log row names this rung yet

R3 Tags and saved filters · cell WATCHING · gate NO-GATE-DECLARED

Contract	`pt_filter` · executor Organ · 1 u · stands on R2
Definition of done	Tags as additive records; saved views as named filter rows; the portal lists by tag and view
Matrix cell	Task tags / labels / saved filters · `runtime/nx_project_tags.nx` · WATCHING decl
Gate	NO-GATE-DECLARED — `knowledge/organ_gate.conf` carries no row for `nx_project_tags`; declare `nx_project_tags TAB <gate>` and the ship loop proves it and the verdict lands here.
Work log	no log row names this rung yet

R4 Attachments on tasks · cell WATCHING · gate NO-GATE-DECLARED

Contract	`pat_put` · executor Organ · 1 u · stands on nothing
Definition of done	A task carries content-addressed attachments through the versioned doc store already shipped; download is ReBAC-gated like sharing
Matrix cell	File attachments on tasks · `runtime/nx_project_attach.nx` · WATCHING decl
Gate	NO-GATE-DECLARED — `knowledge/organ_gate.conf` carries no row for `nx_project_attach`; declare `nx_project_attach TAB <gate>` and the ship loop proves it and the verdict lands here.
Work log	no log row names this rung yet

R5 Approval and sign-off gates · cell WATCHING · gate NO-GATE-DECLARED

Contract	`pap_gate` · executor Organ · 1 u · stands on nothing
Definition of done	Stage gates as DENY-WINS approvals composed from the workflow domain; a task cannot move past a gate without the accountable role's recorded approval
Matrix cell	Approval / sign-off workflow · `runtime/nx_project_approve.nx` · WATCHING decl
Gate	NO-GATE-DECLARED — `knowledge/organ_gate.conf` carries no row for `nx_project_approve`; declare `nx_project_approve TAB <gate>` and the ship loop proves it and the verdict lands here.
Work log	no log row names this rung yet

R6 CSV and MS Project import · cell WATCHING · gate NO-GATE-DECLARED

Contract	`pim_load` · executor Organ · 1.5 u · stands on R0
Definition of done	A CSV and an MS Project XML plan import into dated task files; the imported plan schedules identically to its source on the sample
Matrix cell	CSV / MS Project import · `runtime/nx_project_import.nx` · WATCHING decl
Gate	NO-GATE-DECLARED — `knowledge/organ_gate.conf` carries no row for `nx_project_import`; declare `nx_project_import TAB <gate>` and the ship loop proves it and the verdict lands here.
Work log	no log row names this rung yet

R7 Custom dashboards and report builder · cell WATCHING · gate NO-GATE-DECLARED

Contract	`pds_emit` · executor Organ · 2 u · stands on R2, R3
Definition of done	Report definitions as data rows (which records, which grouping, which chart) rendered on the portal; burndown, velocity and cumulative flow are the first three reports
Matrix cell	Custom dashboards / report builder · `runtime/nx_project_dash.nx` · WATCHING decl
Gate	NO-GATE-DECLARED — `knowledge/organ_gate.conf` carries no row for `nx_project_dash`; declare `nx_project_dash TAB <gate>` and the ship loop proves it and the verdict lands here.
Work log	no log row names this rung yet

R8 Multi-skill resource matching · cell WATCHING · gate NO-GATE-DECLARED

Contract	`psk_match` · executor Organ · 1.5 u · stands on nothing
Definition of done	Assignment by declared skills and availability, not capacity alone; the leveling loop consumes the match
Matrix cell	Multi-skill resource matching · `runtime/nx_project_skills.nx` · WATCHING decl
Gate	NO-GATE-DECLARED — `knowledge/organ_gate.conf` carries no row for `nx_project_skills`; declare `nx_project_skills TAB <gate>` and the ship loop proves it and the verdict lands here.
Work log	no log row names this rung yet

R9 Resource-constrained multi-mode scheduling · cell WATCHING · gate NO-GATE-DECLARED

Contract	`prc_solve` · executor Organ · 3 u · stands on R0, R8
Definition of done	An RCPSP solver over modes and resource limits with a PSPLIB instance as the oracle; makespan within a PRE-DECLARED permille of the published best-known
Matrix cell	Multi-mode resource-constrained scheduling · `runtime/nx_project_rcpsp.nx` · WATCHING decl
Gate	NO-GATE-DECLARED — `knowledge/organ_gate.conf` carries no row for `nx_project_rcpsp`; declare `nx_project_rcpsp TAB <gate>` and the ship loop proves it and the verdict lands here.
Work log	no log row names this rung yet

R10 Real-time collaborative editing · cell WATCHING · gate NO-GATE-DECLARED

Contract	`pco_sync` · executor Organ · 2 u · stands on nothing
Definition of done	Task text and plan rows synced live through the RGA CRDT and sync daemon already proven in the office domain; two concurrent clients converge
Matrix cell	Real-time collaborative editing · `runtime/nx_project_collab.nx` · WATCHING decl
Gate	NO-GATE-DECLARED — `knowledge/organ_gate.conf` carries no row for `nx_project_collab`; declare `nx_project_collab TAB <gate>` and the ship loop proves it and the verdict lands here.
Work log	no log row names this rung yet

R11 Mobile shell · cell WATCHING · gate NO-GATE-DECLARED

Contract	`pmo_shell` · executor Organ · 3 u · stands on nothing
Definition of done	A sovereign mobile shell (the browser-WASM worker and NXE germination precedent) for the portal with offline view of assigned tasks; graded by the UI judge
Matrix cell	Native mobile app · `runtime/nx_project_mobile.nx` · WATCHING decl
Gate	NO-GATE-DECLARED — `knowledge/organ_gate.conf` carries no row for `nx_project_mobile`; declare `nx_project_mobile TAB <gate>` and the ship loop proves it and the verdict lands here.
Work log	no log row names this rung yet

R12 LLM planning assistant · cell WATCHING · gate NO-GATE-DECLARED

Contract	`pai_plan` · executor Local model · 2 u · stands on R0
Definition of done	Natural-language plan generation into task files on the sovereign seat; every generated dependency is schedule-checked before it is written; quality graded by the referee
Matrix cell	LLM / AI planning assistant · `runtime/nx_project_ai.nx` · WATCHING decl
Gate	NO-GATE-DECLARED — `knowledge/organ_gate.conf` carries no row for `nx_project_ai`; declare `nx_project_ai TAB <gate>` and the ship loop proves it and the verdict lands here.
Work log	2026-09-30 queue Estate-wide direction retained 2026-09-30; future PM effectiveness study depends on bottom-up callable, composable and dependable workflows and efficiency baselines.

dossiers=13 cells_joined=13 no_matrix_row=0 (sum 13) gates_recorded=0 gates_unrecorded=0 no_gate_declared=13 (sum 13 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. 46 feature rows mapped of 46 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/projectmgmt.cdmap (cut|x|y, cube|x|y|z); absent = the HBR defaults

bubble area = breadth · ring = momentum (green rising, red falling, grey until day two) · dashed = category means · axes fitted to the field of play: centrality 700–950, distinctiveness 50–350 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 744 permil of the plot · quadrant words unseated 0
text contrast, measured with wcag2-ratio (floors from contrast.conf), light theme: labels 16.24 (floor 4.50) · notes 16.24 (floor 4.50) · quadrant words 5.89 (floor 4.50) · tick numerals 5.89 (floor 4.50) · axis titles 5.59 (floor 4.50) · dark theme: labels 13.78 (floor 4.50) · quadrant words 5.55 (floor 4.50) · axis titles 5.97 (floor 4.50) · dark classes under their floor 0 (one figure serves both themes: a dark shortfall is a token to fix, never a class to hide) · classes refused under their floor 0 (a refused class is not drawn; the scale classes are measured, never hidden) · export: SVG PNG (receipt, rendered by the estate's own rasteriser from this page)

axes fitted: centrality 700–950 · distinctiveness 50–350 · breadth 300–600 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 1 · unresolved labels 0 · mark overlaps 0 (a fact of the data: two players that close are that close) · data spread 388 permil of the plot

Nishi Microsoft Project Leantime Asana OpenProject
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 6 (a fact of the data: two players that close are that close) · data spread 568 permil of the plot

Player	Quadrant	centrality	distinctiveness	breadth	depth	momentum	Rows held	Days on spine	First seen
Nishi	Unconventional	740	318	514	717	0 since 2026-09-30	33	11	2026-09-15
Microsoft Project	Aspirational	926	228	557	658	0 since 2026-09-30	39	11	2026-09-15
Leantime	Peripheral	757	94	362	574	0 since 2026-09-30	29	11	2026-09-15
Asana	Mainstream	915	162	500	605	0 since 2026-09-30	38	11	2026-09-15
OpenProject	Mainstream	926	127	478	578	0 since 2026-09-30	38	11	2026-09-15

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

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

Capability matrix — measured against source

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

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

Capability	Nishi	Microsoft Project	Leantime	Asana	OpenProject
Task management + status workflow Measured: `TASK` exists in `runtime/_hdl_build/nx_vizsla_plan.nx`, verified at emit. READY/BLOCKED/DONE derived from dependency state with loud cycle detection rival marks uncited — the Yes, Best or Part codes on this row are an observation read with no reference mark behind them Adoption: `RUN-BY:fork:nx_vizsla_coord_gate` — fully adopted (top of its ladder). Pros Implementing source symbol found; runtime acceptance separate; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)	●	●	●	●	●
Dependency scheduling + critical path Measured: `CRITICAL` exists in `runtime/_hdl_build/nx_vizsla_plan.nx`, verified at emit. Topo-DP longest-effort chain [kelley-walker1959]; MS Project is the schedule-engine gold standard [msproject] Adoption: `RUN-BY:fork:nx_vizsla_coord_gate` — fully adopted (top of its ladder). Pros Implementing source symbol found; runtime acceptance separate; ahead of Leantime, Asana, OpenProject; fully adopted on the estate ladderCons behind Microsoft Project (leads)	●	◉	◐	◐	◐
Kanban / priority board Measured: `vp_cmd_board` exists in `runtime/_hdl_build/nx_vizsla_plan.nx`, verified at emit. Eisenhower urgency x importance bands, data-driven rival marks uncited — the Yes, Best or Part codes on this row are an observation read with no reference mark behind them Adoption: `RUN-BY:fork:nx_vizsla_coord_gate` — fully adopted (top of its ladder). Pros Implementing source symbol found; runtime acceptance separate; ahead of Microsoft Project; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)	●	◐	●	●	●
Milestones + progress percent Measured: `MILE` exists in `runtime/_hdl_build/nx_vizsla_plan.nx`, verified at emit. Milestone pct from task completion rival marks uncited — the Yes, Best or Part codes on this row are an observation read with no reference mark behind them Adoption: `RUN-BY:fork:nx_vizsla_coord_gate` — fully adopted (top of its ladder). Pros Implementing source symbol found; runtime acceptance separate; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)	●	●	●	●	●
Calendar time-blocking of ready tasks Measured: `vp_cmd_timeblock` exists in `runtime/_hdl_build/nx_vizsla_plan.nx`, verified at emit. First-fit by priority into REAL calendar free windows rival marks uncited — the Yes, Best or Part codes on this row are an observation read with no reference mark behind them Adoption: `RUN-BY:fork:nx_vizsla_coord_gate` — fully adopted (top of its ladder). Pros Implementing source symbol found; runtime acceptance separate; ahead of Microsoft Project, Leantime, Asana, OpenProject; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)	●	◐	○	○	○
Group find-a-time + scheduling polls Measured: `vg_cmd_findtime` exists in `runtime/_hdl_build/nx_vizsla_group.nx`, verified at emit. Free/busy intersection across member calendars plus vote tally Adoption: `PRODUCER-ALIAS` — fully adopted (top of its ladder). Pros Implementing source symbol found; runtime acceptance separate; ahead of Microsoft Project, Leantime, Asana, OpenProject; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)	●	○	○	○	○
Portfolio multi-project registry + live board Measured: `ws_put` exists in `runtime/_hdl_build/nx_workstream_store.nx`, verified at emit. 1265-stream WMS registry with live HTML board; rivals tier-gate portfolio rival marks uncited — the Yes, Best or Part codes on this row are an observation read with no reference mark behind them Adoption: `LIB-WIRED importers=36 nonval=23` — fully adopted (top of its ladder). Pros Implementing source symbol found; runtime acceptance separate; ahead of Microsoft Project, Leantime, Asana; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)	●	◐	◐	◐	●
Calendar interop RFC5545 export + import Measured: `RRULE` exists in `runtime/_hdl_build/nx_vizsla_ics.nx`, verified at emit. Round-trip .ics incl YEARLY recurrence [rfc5545] Adoption: `PRODUCER-ALIAS` — fully adopted (top of its ladder). Pros Implementing source symbol found; runtime acceptance separate; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)	●	●	●	●	●
Reminders + once-only notification ledger Measured: `VIZSLA-REM-DUE` exists in `runtime/_hdl_build/nx_vizsla_remind.nx`, verified at emit. Lead-day matching, sent-once ledger, on-site feed + email digest rival marks uncited — the Yes, Best or Part codes on this row are an observation read with no reference mark behind them Adoption: `PRODUCER-ALIAS` — fully adopted (top of its ladder). Pros Implementing source symbol found; runtime acceptance separate; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)	●	●	●	●	●
Versioned document management Measured: `vd_cmd_history` exists in `runtime/_hdl_build/nx_vizsla_doc.nx`, verified at emit. Additive CID versions, old bytes never destroyed rival marks uncited — the Yes, Best or Part codes on this row are an observation read with no reference mark behind them Adoption: `PRODUCER-ALIAS` — fully adopted (top of its ladder). Pros Implementing source symbol found; runtime acceptance separate; ahead of Microsoft Project, Leantime, Asana; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)	●	◐	◐	◐	●
Coordination-to-document generation Measured: `dg_store_doc` exists in `runtime/_hdl_build/nx_vizsla_docgen.nx`, verified at emit. Plan/venue fields emit a real .docx, filed versioned Adoption: `PRODUCER-ALIAS` — fully adopted (top of its ladder). Pros Implementing source symbol found; runtime acceptance separate; ahead of Microsoft Project, Leantime, Asana, OpenProject; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)	●	○	○	○	○
Team + contractor relationship graph Measured: `re_edge_ok` exists in `runtime/nx_relate.nx`, verified at emit. One multi-tenant graph for staff and contractors; Leantime has first-class clients rival marks uncited — the Yes, Best or Part codes on this row are an observation read with no reference mark behind them Adoption: `SOURCE-ONLY` — PARTIAL: source exists, never compiled: /api/build it. not adopted: source exists, never compiled: /api/build it Pros Implementing source symbol found; runtime acceptance separate; ahead of Microsoft Project, Asana, OpenProjectCons not adopted yet: source exists, never compiled: /api/build it	●	◐	●	◐	◐
Bulk personalized multi-channel comms Measured: `MERGE` exists in `runtime/nx_send_merge.nx`, verified at emit. Segment to personalized email/letter/card merge Adoption: `SOURCE-ONLY` — PARTIAL: source exists, never compiled: /api/build it. not adopted: source exists, never compiled: /api/build it Pros Implementing source symbol found; runtime acceptance separate; ahead of Microsoft Project, Leantime, Asana, OpenProjectCons not adopted yet: source exists, never compiled: /api/build it	●	○	○	○	○
RACI accountable-owner routing Measured: `pm_route` exists in `runtime/_hdl_build/nx_pm.nx`, verified at emit. Every activity routes to its RACI-accountable role by construction rival marks uncited — the Yes, Best or Part codes on this row are an observation read with no reference mark behind them Adoption: `LIVE` — fully adopted (top of its ladder). Pros Implementing source symbol found; runtime acceptance separate; ahead of Microsoft Project, Leantime, Asana, OpenProject; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)	●	◐	○	◐	◐
API + MCP agent tools Measured: `vt_reg1` exists in `runtime/nx_vizsla_tool_register.nx`, verified at emit. 11 coordination tools fork-exec over /mcp; Asana ships MCP too [asana-mcp] Adoption: `PROMOTED-UNREGISTERED` — PARTIAL: a real binary nobody can call over MCP: /api/tools/register it; no execution surface runs it either (clock, cron, daemon, roster, actlog and surfaced forks checked). not adopted: a real binary nobody can call over MCP: /api/tools/register it; 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 LeantimeCons not adopted yet: a real binary nobody can call over MCP: /api/tools/register it; no execution surface runs it either (clock, cron, daemon, roster, actlog and surfaced forks checked)	●	●	◐	●	●
Gantt / timeline schedule view Measured: `pj_html_build` exists in `runtime/nx_project.nx`, verified at emit. Latest-safe effort windows vs due on the portal page; MS Project gantt deepest rival marks uncited — the Yes, Best or Part codes on this row are an observation read with no reference mark behind them Adoption: `PRODUCER-ALIAS` — fully adopted (top of its ladder). Pros Implementing source symbol found; runtime acceptance separate; fully adopted on the estate ladderCons behind Microsoft Project (leads)	●	◉	●	●	●
Time tracking / timesheets Measured: `PROJECT-TIME` exists in `runtime/nx_project.nx`, verified at emit. Additive LOG records + per-person timesheet; Leantime timesheet-first still deepest [leantime] Adoption: `PRODUCER-ALIAS` — fully adopted (top of its ladder). Pros Implementing source symbol found; runtime acceptance separate; ahead of Asana; fully adopted on the estate ladderCons behind Leantime (leads)	●	●	◉	◐	●
Budget / cost / earned value Measured: `PROJECT-EVM` exists in `runtime/nx_project.nx`, verified at emit. Integer EV/CPI permil from BUDGET/COST records; MS Project EVM deepest rival marks uncited — the Yes, Best or Part codes on this row are an observation read with no reference mark behind them Adoption: `PRODUCER-ALIAS` — fully adopted (top of its ladder). Pros Implementing source symbol found; runtime acceptance separate; ahead of Leantime, Asana; fully adopted on the estate ladderCons behind Microsoft Project (leads)	●	◉	◐	◐	●
Risk register + delay prediction Measured: `PROJECT-RISK` exists in `runtime/nx_project.nx`, verified at emit. Overdue + slack vs critical-chain, WCONF work-day as data; rivals track status not risk rival marks uncited — the Yes, Best or Part codes on this row are an observation read with no reference mark behind them Adoption: `PRODUCER-ALIAS` — fully adopted (top of its ladder). Pros Implementing source symbol found; runtime acceptance separate; ahead of Microsoft Project, Leantime, Asana, OpenProject; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)	●	◐	○	○	◐
Resource workload allocation + leveling Measured: `PROJECT-LEVEL` exists in `runtime/nx_project.nx`, verified at emit. Closed-loop: suggest AND apply as durable ASSIGN records; MS Project auto-leveling deepest rival marks uncited — the Yes, Best or Part codes on this row are an observation read with no reference mark behind them Adoption: `PRODUCER-ALIAS` — fully adopted (top of its ladder). Pros Implementing source symbol found; runtime acceptance separate; ahead of Leantime, Asana, OpenProject; fully adopted on the estate ladderCons behind Microsoft Project (leads)	●	◉	○	◐	◐
Project templates / blueprints Measured: `TPLTASK` exists in `runtime/nx_project.nx`, verified at emit. Blueprint rows + a start date emit a dated task file the planner loads rival marks uncited — the Yes, Best or Part codes on this row are an observation read with no reference mark behind them Adoption: `PRODUCER-ALIAS` — fully adopted (top of its ladder). Pros Implementing source symbol found; runtime acceptance separate; ahead of Leantime; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)	●	●	◐	●	●
Task comments / discussion threads Measured: `PROJECT-NOTE` exists in `runtime/nx_project.nx`, verified at emit. Additive NOTE records, task-visibility-scoped on the portal; Asana threads deepest rival marks uncited — the Yes, Best or Part codes on this row are an observation read with no reference mark behind them Adoption: `PRODUCER-ALIAS` — fully adopted (top of its ladder). Pros Implementing source symbol found; runtime acceptance separate; ahead of Microsoft Project; fully adopted on the estate ladderCons behind Asana (leads)	●	◐	●	◉	●
Contractor portal with scoped access Measured: `PSV_BOOTSTRAP` exists in `runtime/_hdl_build/nx_project_serve.nx`, verified at emit. LIVE: OPAQUE login, per-person picker, cross-project 403, supervised self-healing daemon 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:daemon` — fully adopted (top of its ladder). Pros Implementing source symbol found; runtime acceptance separate; ahead of Microsoft Project; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)	●	◐	●	●	●
Sovereign own-stack zero per-seat cost Source present; authored stronger claim: `ws_put_locked` in `runtime/_hdl_build/nx_ws_cas.nx`, verified at emit. Own language compiler TLS store on your hardware; PHP/Ruby self-hosts still ride third-party stacks [openproject] Adoption: `LIB-WIRED importers=10 nonval=5` — fully adopted (top of its ladder). Pros Source symbol found; stronger capability claim is authored; ahead of Microsoft Project, Leantime, Asana, OpenProject; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)	◉	○	◐	○	◐
Concurrent-durable additive store measured vs git Source present; authored stronger claim: `WMS` in `runtime/_hdl_build/nx_ws_exceed_git_live_gate.nx`, verified at emit. 144/144 concurrent writes zero lost vs live git 104 refused; reflog crash-repair gated rival marks uncited — the Yes, Best or Part codes on this row are an observation read with no reference mark behind them Adoption: `GATE:BUILT-UNPROMOTED trial=-` — PARTIAL: compiled, never promoted to the serving root: /api/promote it, then roster it. not adopted: compiled, never promoted to the serving root: /api/promote it, then roster it Pros Source symbol found; stronger capability claim is authored; ahead of Microsoft Project, Leantime, Asana, OpenProjectCons not adopted yet: compiled, never promoted to the serving root: /api/promote it, then roster it	◉	◐	◐	●	●
Work liveness heartbeats ALIVE/STALLED Source present; authored stronger claim: `hbm_scan_registry` in `runtime/_hdl_build/nx_heartbeat_str.nx`, verified at emit. Liveness recomputed from real beats vs the clock, not self-reported status rival marks uncited — the Yes, Best or Part codes on this row are an observation read with no reference mark behind them Adoption: `LIB-WIRED importers=11 nonval=6` — fully adopted (top of its ladder). Pros Source symbol found; stronger capability claim is authored; ahead of Microsoft Project, Leantime, Asana, OpenProject; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)	◉	○	○	◐	○
Autonomous dispatch runs + completes work Source present; authored stronger claim: `dl_try_lease` in `runtime/_hdl_build/nx_dispatch_lease.nx`, verified at emit. Machine leases a stream, runs its gate, marks DONE only on GREEN; rival rules move tasks but do not run work rival marks uncited — the Yes, Best or Part codes on this row are an observation read with no reference mark behind them Adoption: `SOURCE-ONLY` — PARTIAL: source exists, never compiled: /api/build it. not adopted: source exists, never compiled: /api/build it Pros Source symbol found; stronger capability claim is authored; ahead of Microsoft Project, Leantime, Asana, OpenProjectCons not adopted yet: source exists, never compiled: /api/build it	◉	○	○	◐	◐
Effective-owner reassignment (latest-wins history) Measured: `ASSIGN` exists in `runtime/nx_project.nx`, verified at emit. ASSIGN records override task owner, latest date wins, history preserved; rivals reassign destructively rival marks uncited — the Yes, Best or Part codes on this row are an observation read with no reference mark behind them Adoption: `PRODUCER-ALIAS` — fully adopted (top of its ladder). Pros Implementing source symbol found; runtime acceptance separate; ahead of Leantime; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)	●	●	○	●	●
Critical-chain slack + delay forecast Measured: `pj_chain_min` exists in `runtime/nx_project.nx`, verified at emit. Open critical-chain minutes to finish, converted to slack days vs due; MS Project chain engine deepest rival marks uncited — the Yes, Best or Part codes on this row are an observation read with no reference mark behind them Adoption: `PRODUCER-ALIAS` — fully adopted (top of its ladder). Pros Implementing source symbol found; runtime acceptance separate; ahead of Leantime, Asana, OpenProject; fully adopted on the estate ladderCons behind Microsoft Project (leads)	●	◉	○	○	○
Scheduling poll vote tally Measured: `vg_cmd_tally` exists in `runtime/_hdl_build/nx_vizsla_group.nx`, verified at emit. Latest-vote-per-member wins with lexicographic tie-break; Doodle-style, in-stack rival marks uncited — the Yes, Best or Part codes on this row are an observation read with no reference mark behind them Adoption: `PRODUCER-ALIAS` — fully adopted (top of its ladder). Pros Implementing source symbol found; runtime acceptance separate; ahead of Microsoft Project, Leantime, Asana, OpenProject; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)	●	○	○	◐	○
Path-guarded store security (deny-by-default) Source present; authored stronger claim: `pj_pathok` in `runtime/nx_project.nx`, verified at emit. Store writes confined to a namespace and dot-dot refused by construction; rivals trust the app layer rival marks uncited — the Yes, Best or Part codes on this row are an observation read with no reference mark behind them Adoption: `PRODUCER-ALIAS` — fully adopted (top of its ladder). Pros Source symbol found; stronger capability claim is authored; ahead of Microsoft Project, Leantime, Asana, OpenProject; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)	◉	●	●	●	●
Recurring tasks (native repeat) Open — watching `runtime/nx_project_recur.nx` : `pr_expand`, re-measured on every compare beat. Ship that symbol and this mark flips itself; the `comparewatch-` plane row flips with it. Native task recurrence; ours is calendar-event recurrence only rival marks uncited — the Yes, Best or Part codes on this row are an observation read with no reference mark behind them dossierwatching pr_expand Pros none measured yetCons behind Microsoft Project, Leantime, Asana, OpenProject; open contract; expected source declaration not established	○	●	●	●	●
Custom fields per task Open — watching `runtime/nx_project_fields.nx` : `pf_set`, re-measured on every compare beat. Ship that symbol and this mark flips itself; the `comparewatch-` plane row flips with it. User-defined task attributes; Asana custom fields deepest [asana-api] dossierwatching pf_set Pros none measured yetCons behind Microsoft Project, Leantime, Asana (leads), OpenProject; open contract; expected source declaration not established	○	●	●	◉	●
Task tags / labels / saved filters Open — watching `runtime/nx_project_tags.nx` : `pt_filter`, re-measured on every compare beat. Ship that symbol and this mark flips itself; the `comparewatch-` plane row flips with it. Tagging plus saved views; a core Asana and Leantime feature we lack rival marks uncited — the Yes, Best or Part codes on this row are an observation read with no reference mark behind them dossierwatching pt_filter Pros none measured yetCons behind Microsoft Project, Leantime, Asana (leads), OpenProject; open contract; expected source declaration not established	○	●	●	◉	●
Saved baseline + schedule variance Measured: `PROJECT-BASELINE` exists in `runtime/nx_project.nx`, verified at emit. Snapshot BASE records then due-slip + effort-delta variance per task; MS Project baselines still deepest rival marks uncited — the Yes, Best or Part codes on this row are an observation read with no reference mark behind them Adoption: `PRODUCER-ALIAS` — fully adopted (top of its ladder). Pros Implementing source symbol found; runtime acceptance separate; ahead of Leantime; fully adopted on the estate ladderCons behind Microsoft Project (leads)	●	◉	○	●	●
Lead / lag + dependency types (FS/SS/FF) Open — watching `runtime/nx_project_deptype.nx` : `pd_schedule`, re-measured on every compare beat. Ship that symbol and this mark flips itself; the `comparewatch-` plane row flips with it. Only finish-to-start today; MS Project has the full dependency algebra rival marks uncited — the Yes, Best or Part codes on this row are an observation read with no reference mark behind them dossierwatching pd_schedule Pros none measured yetCons behind Microsoft Project (leads), Asana, OpenProject; open contract; expected source declaration not established	○	◉	○	●	●
Multi-mode resource-constrained scheduling Open — watching `runtime/nx_project_rcpsp.nx` : `prc_solve`, re-measured on every compare beat. Ship that symbol and this mark flips itself; the `comparewatch-` plane row flips with it. The RCPSP frontier, the top 2025/26 research axis [psplib]; MS Project leveling closest dossierwatching prc_solve Pros none measured yetCons behind Microsoft Project (leads), OpenProject; open contract; expected source declaration not established	○	◉	○	○	●
Multi-skill resource matching Open — watching `runtime/nx_project_skills.nx` : `psk_match`, re-measured on every compare beat. Ship that symbol and this mark flips itself; the `comparewatch-` plane row flips with it. Assign by skill and availability; we match capacity only rival marks uncited — the Yes, Best or Part codes on this row are an observation read with no reference mark behind them dossierwatching psk_match Pros none measured yetCons behind Microsoft Project, Asana, OpenProject; open contract; expected source declaration not established	○	●	○	●	●
Burndown / velocity / cumulative-flow charts Measured: `PROJECT-BURN` exists in `runtime/nx_project.nx`, verified at emit. Remaining-effort-over-time series from DONE + effort records; visual chart rendering is the next rung rival marks uncited — the Yes, Best or Part codes on this row are an observation read with no reference mark behind them Adoption: `PRODUCER-ALIAS` — fully adopted (top of its ladder). Pros Implementing source symbol found; runtime acceptance separate; ahead of Leantime, OpenProject; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)	●	●	◐	●	◐
Custom dashboards / report builder Open — watching `runtime/nx_project_dash.nx` : `pds_emit`, re-measured on every compare beat. Ship that symbol and this mark flips itself; the `comparewatch-` plane row flips with it. Configurable reporting; every incumbent has one rival marks uncited — the Yes, Best or Part codes on this row are an observation read with no reference mark behind them dossierwatching pds_emit Pros none measured yetCons behind Microsoft Project (leads), Leantime, Asana, OpenProject; open contract; expected source declaration not established	○	◉	●	●	●
Approval / sign-off workflow Open — watching `runtime/nx_project_approve.nx` : `pap_gate`, re-measured on every compare beat. Ship that symbol and this mark flips itself; the `comparewatch-` plane row flips with it. Formal approvals and stage gates; Asana rules and MS Project gates rival marks uncited — the Yes, Best or Part codes on this row are an observation read with no reference mark behind them dossierwatching pap_gate Pros none measured yetCons behind Microsoft Project, Leantime, Asana (leads), OpenProject; open contract; expected source declaration not established	○	●	●	◉	●
File attachments on tasks Open — watching `runtime/nx_project_attach.nx` : `pat_put`, re-measured on every compare beat. Ship that symbol and this mark flips itself; the `comparewatch-` plane row flips with it. Attach files to a task; our doc store is project-level, not task-attached rival marks uncited — the Yes, Best or Part codes on this row are an observation read with no reference mark behind them dossierwatching pat_put Pros none measured yetCons behind Microsoft Project, Leantime, Asana, OpenProject; open contract; expected source declaration not established	○	●	●	●	●
Native mobile app Open — watching `runtime/nx_project_mobile.nx` : `pmo_shell`, re-measured on every compare beat. Ship that symbol and this mark flips itself; the `comparewatch-` plane row flips with it. Responsive web only; the majors ship native iOS and Android apps rival marks uncited — the Yes, Best or Part codes on this row are an observation read with no reference mark behind them dossierwatching pmo_shell Pros none measured yetCons behind Microsoft Project, Leantime, Asana, OpenProject; open contract; expected source declaration not established	○	●	●	●	◐
CSV / MS Project import Open — watching `runtime/nx_project_import.nx` : `pim_load`, re-measured on every compare beat. Ship that symbol and this mark flips itself; the `comparewatch-` plane row flips with it. Import an existing plan; we author fresh only rival marks uncited — the Yes, Best or Part codes on this row are an observation read with no reference mark behind them dossierwatching pim_load Pros none measured yetCons behind Microsoft Project (leads), Leantime, Asana, OpenProject; open contract; expected source declaration not established	○	◉	●	●	◐
LLM / AI planning assistant Open — watching `runtime/nx_project_ai.nx` : `pai_plan`, re-measured on every compare beat. Ship that symbol and this mark flips itself; the `comparewatch-` plane row flips with it. Natural-language plan generation; gated on the sovereign LLM engine rival marks uncited — the Yes, Best or Part codes on this row are an observation read with no reference mark behind them dossierwatching pai_plan Pros none measured yetCons behind Microsoft Project, Asana; open contract; expected source declaration not established	○	◐	○	◐	○
Real-time collaborative editing Open — watching `runtime/nx_project_collab.nx` : `pco_sync`, re-measured on every compare beat. Ship that symbol and this mark flips itself; the `comparewatch-` plane row flips with it. Simultaneous multi-user edit; a core cloud-PM feature we lack rival marks uncited — the Yes, Best or Part codes on this row are an observation read with no reference mark behind them dossierwatching pco_sync Pros none measured yetCons behind Microsoft Project, Leantime, Asana (leads), OpenProject; open contract; expected source declaration not established	○	●	●	◉	●

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

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

Delivery and evidence

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

Release history and work log

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

When	Rung	Kind	Entry
2026-09-12	R0	requirement	OPERATOR ECONOMIC VALUE 2026-09-12: measure capability growth in dollars, elapsed and active time, opportunity cost and realized user value, alongside depth/breadth and current frontier qualification. Extend existing pm_roi.data and projectmgmt/finance owners; do not create a second value ledger. Separate cash marginal expense, allocated subscription/hardware/energy/storage, human effort and agent cached/uncached input/output plus tool/review/rejected-work overhead. Avoided spend is realized only when a genuinely needed equivalent purchase is displaced; capability presence or competitor list price is not savings. Value must be net of operation/maintenance and quality differences. Forecasts carry horizon, assumption owner, ranges and dated baselines; payback/ROI use the same horizon and net-benefit denominator; zero or unknown investment does not produce infinite ROI. Opportunity cost names the best feasible alternative foregone under current dependencies and resources, and is shown separately to avoid double counting labor or benefits. Shared capability costs allocated once, reuse recorded per accepted workflow, portfolio totals deduplicated. Existing pm_roi.data estimates remain historical UNREVALIDATED: static SaaS labels, assumed40W NAS and extrapolated manual hours do not prove realized savings. No new dollar value or positive ROI claimed today.
2026-09-12	R0	requirement	One-call domain pilot must connect existing nx_plan_run data workflows, nx_product_decompose, nx_capsearch, nx_compare_rank, nishi_crew and scoped Compare publisher through verified bindings. Existing decompose substring matching is a gap, not a semantic requirement oracle. Track source/owner coverage, prerequisite depth, representative tested breadth, matched competitor baselines, uncertainty and economic actuals per accepted outcome. Elder AI/Media Manager/Companion recovery uses existing gen/media/companionchat boards; same workflow must also qualify a new-domain target. No new orchestrator or autonomous completion claim.
2026-09-21	RISK	evidence	2026-09-21 t398 private qualification GREEN 74/74; receipt buildroot/knowledge/gates/pm-compare-rank-risk-t398-review.json sha256=2afe283665f30ed0b376577a3536eb46506bf19eff730a0c9191f4933f31c3c8; shared rank writer estate-path repair verified; all13 rank rows unchanged and evidence influence NONE. Status remains OPEN pending trusted deployment-owned startup binding, approved public classification and guarded source adoption; no public Compare or production authorization.
2026-09-21	RESOURCE	requirement	2026-09-21 native health remains DEGRADED (mem_avail_permil=345, swap_used_permil=1000, services=16 UP). Existing nx_resmon reports RED while nx_build_admit returns GRANT. Additive estate work item: compose a fresh, provenance-bound resmon current-state artifact into nx_build_admit and qualify GRANT/RED/stale differential behavior without changing existing queue owners or thresholds until measured evidence supports it. No Beach heavy dispatch while unresolved.
2026-09-21	RESOURCE	evidence	2026-09-21 nx_resmon trend native run: rows=12, log_bytes=2155047, tail_trunc=1, worst=nx_email_portal, newest_kb=2871456, grew_in=3/11, delta_kb=2748, name_changed=1, verdict=UNOBSERVABLE. Trend cannot qualify duration when worst process changes; retain as unobservable and do not infer recovery. Recovery contract must carry freshness and attribution instead of guessing from one process.
2026-09-21	RACI	evidence	2026-09-21 canonical RACI dynamic validator guarded ship and live native verification complete: gate1789999602 GREEN35/35; ship1789999649 fresh gate35/35 contentGREEN behaviorIDENTICAL; live1789999684 sovereign226rows57activities; receipt buildroot/knowledge/gates/raci-integrity-t399-ship-review.json SHA575f0cc119212fcb138e1a5fd9519bd75e7209a1494316d5ec27b13ad37f7816. Studio/capacity15 native proposal records remain BACKLOG_ONLY not dispatched; no authority reassignment, rank delta, Beach or public UI change. PM coordinates; craft/technical/operations/repair/verification/admission/release owners remain separate.
2026-09-21	RELEASE	followup	2026-09-21 stale-gate rebuild-refusal evidence retained as INTERNAL OBSERVED_UNVERIFIED BACKLOG_ONLY: buildroot/knowledge/gates/pm-ship-stale-gate-t399.json SHAa2f812f25e3f3ad76e76146418f95404ccd57febabfdb44a5f2f78f8990f9517. Repair doctor; independent verification engineer; admission warden; release publisher; coordination pm. Next: shared ship owner refuses stale fallback after gate rebuild failure and binds fresh gate closure/binary/output. Not dispatched; no automatic repair or promotion claimed.
2026-09-21	RESOURCE	requirement	2026-09-21 operator extends resource stewardship to field sensors, local hosts, rented compute, swarm workers and supercomputers. Architect owns common contracts; each resource operator owns capacity, lifecycle and hardware/provider-specific policy; engineer verifies; PM coordinates ranked investment. Capture observed vs unavailable CPU/GPU/memory/VRAM/IO/network/energy/temperature/wear/provider-quota metrics with owner, units, provenance and freshness. Rank accepted outcomes against energy, latency, cost, retries, context and tokens; reclaim request resources and idle work. Admission must use actual demand, operating envelopes and pressure evidence, not a universal fixed ceiling or swap-occupancy-only diagnosis. Preserve high-capability quality preferences and explicit energy-saving choices. Primary oracle https://docs.kernel.org/accounting/psi.html distinguishes productive utilization from stalls; https://docs.kernel.org/admin-guide/cgroup-v2.html supplies resource-controller reference behavior, not a claim of NAS support or a new runtime dependency. This is a retained cross-estate requirement; current implementation remains NAS request lifetime, attribution and release-proof repair, not dispatched control on every device.
2026-09-21	RESOURCE	evidence	2026-09-21 nx_resmon guarded ship1790013498 and real default run1790013551 verified:current19/19; live/offc68760B SHA5cb1603f75ec8b540309be2b3d8ef89442c2364288cfafd55b2415c85eb4ed4d; real journal includes process swap attribution and epoch. DEGRADED remains; pressureRED/2 is measurement, not execution failure. /proc/swaps differentiates21GiB-class zram from2GiB disk swap; PSI unavailable;126.98s sample pswpin+7 pswpout+4. Hardware wear cannot be inferred from full logical swap. Shared publisher stale-refresh repair also live71/71 with installed-owner isolated control flow18/18 job1790013676. Email request lifetime repair remains candidate source work. Resource-wide requirement is retained, not implemented on every device. Existing receipt buildroot/knowledge/gates/nas-resmon-adoption-review-20260921.md; current hardware telemetry oracle DMTF Redfish2026.2 released14Sep2026 https://www.dmtf.org/standards/redfish plus Slurm power lifecycle oracle https://slurm.schedmd.com/power_save.html; benchmarks only, no added runtime dependency. Prior append1790013683 refused before execution; native no-marker and tail confirmed absence before retry.
2026-09-21	RELEASE	evidence	2026-09-21 stale-required-gate release blocker repaired through nx_organ_ship owner: component71/71 job1790000935; guarded ship1790013309 exact reviewed diagnostic-loss approval; installed-owner isolated refusal18/18 job1790013676. Live/offc178136B SHAeea91757617a8859b65a38590e2e323223e52d2f26a320bd8f739f85df61647d. Actual installed owner refuses23 before stale execution/adoption/promotion and retains candidate. Native API/provenance fixtures isolated with no network; usage-only behavior comparison remains WEAK. Receipt buildroot/knowledge/gates/ship-required-refresh-t400-final.json SHA1efdda87156b18f179b803bd72f721590e3750b2c616d2d93ba7df851912c488. Publisher release; doctor repair; engineer verification; PM coordination. No Beach or rank change.
2026-09-21	RESOURCE	debt	2026-09-21 readback confirms host still DEGRADED with16services up, memavailable421permil and logical swap1000permil. Timestamped process-swap monitoring now live; this alone is not stable-resource proof. Review of canonical nx_http_server and nx_http_io shows no per-request allocation in accept/read/parse, but existing Content-Length parser matches only part of the field name and has unchecked decimal accumulation; read_request assumes headers fit the first read. Retain for existing HTTP/parser owner with fragmented-header, exact-header-name, overflow and timeout reproductions; no speculative shared-parser rewrite during email request-lifetime delivery. Email actual-router qualification1790013983 stopped at undefined gate-only sys_fcntl before binary production; worker correcting verified syscall naming. No candidate deployment yet.
2026-09-21	RESOURCE	qualification	2026-09-21 email candidate lifecycle passed272 repetitions across17 actual routes with parent mappings8to8 and virtualpages1161to1161; failed allocation, worker signal death, exact-child reaping, inherited descriptors, blocked-alarm recovery and parent-mask restoration passed. Legacy fixture gate1790014916 passed12/12 real registration/login, delivery, isolation, escaping, queue and softdelete behaviors. Actual daemon HTTP proof remains pending1790015005; no deployment claim. An isolated native probe1790014826 confirmed an optimizer defect: tailcalling with a local-address argument retires its frame before the callee reads it. Safe helper retains ownership, while compiler owner nx_opt is assigned a permanent eligibility repair; x86 signal facade has explicit platform scope, not a portable-hardware claim. Added worker startup1790014852 failed MCP initialization503/read-after-accept; no new worker ran. Existing MCP health1790014914 works (16services up, memory417permil, swap1000permil); neither error nor recovery proves a NAS cause.
2026-09-21	RESOURCE	risk	2026-09-21 independent source/live audit: resgov state keyed12298:0 despite actual nx_motion_serve PID12298 starttime343224463; existing parser stops after first token. Aggregate nomination watches only largest nonexempt process, so nonrecyclable largest blocks eligible email. Action receipts do not consistently check signal/renice/restart/unlink results; destructive per-process decisions lack aggregate path's recycle requirement. Existing resmon trend persists observed=0 verdict=GREEN for UNOBSERVABLE; trend consumer ignores observed. Monitor pressure remains correctlyRED. Existing sizeguard only reports oversize, no archival performed. Next owners: resource governor identity+action-result/recycle safety; resource monitor truthful unknown propagation; archival owner verified retention. No new automatic restarts or thresholds authorized by this audit; preserve evidence and qualify changes through existing owners.
2026-09-21	RESOURCE_PORTABILITY	operator_requirement	Scope includes field sensors through supercomputers and swarm. Public Nishi resource/process APIs must retain stable contracts with capability-probed platform backends; Linux procfs and Linux-x64 signal calls are proven backend implementations only, not Nishi OS portability. Unsupported observations remain unknown. Email canonical gate 1790015791 GREEN12/12 and exact staged executable HTTP gate1790015817 GREEN144 requests stable mappings/pages; guarded ship1790015489 refused3 printable runs pending exact loss review; no daemon restart yet.
2026-09-30	R12	queue	Estate-wide direction retained 2026-09-30; future PM effectiveness study depends on bottom-up callable, composable and dependable workflows and efficiency baselines.

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

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

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

Rank	Rival	Seeds	Mentions	First seed	Kind	Link
1	Microsoft Project	1	1	col0-microsoft	named	https://support.microsoft.com/en-us/project
2	Leantime	1	1	col1-leantime	named	https://github.com/Leantime/leantime
3	Asana	1	1	col2-asana	named	https://developers.asana.com/docs/overview
4	OpenProject	1	1	col3-openproject	named	https://www.openproject.org/docs/

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

Capability	Organ	Boards grading it	Home	Rule	Evidence	Standing on this board
VIZSLA-REM-DUE	`nx_vizsla_remind.nx`	automation, projectmgmt	—	none	unproven	undecided
dg_store_doc	`nx_vizsla_docgen.nx`	automation, projectmgmt	—	none	unproven	undecided
hbm_scan_registry	`nx_heartbeat_str.nx`	automation, projectmgmt	—	none	unproven	undecided
ws_put_locked	`nx_ws_cas.nx`	automation, projectmgmt	—	none	unproven	undecided

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

kind	name	board	source	evidence

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

References

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

[msproject] Microsoft. Microsoft Project help and learning (support.microsoft.com): critical path, resource leveling, baselines, earned value and Gantt scheduling for Project desktop and Project for the web. Accessed 2026-08-18. publisher · read in our library knowledge/fetched/cmp_projectmgmt_msproject.html · pin hab62522275c5f0d691dc7343e4c151aa4bac21491c3237cefeaaf77438dda9fd · accessed 2026-08-18 · vendor-docGrounds: The Microsoft Project column Best codes on 'Dependency scheduling + critical path', 'Gantt / timeline schedule view', 'Budget / cost / earned value', 'Resource workload allocation + leveling', 'Saved baseline + schedule variance', 'Lead / lag + dependency types (FS/SS/FF)' and 'Critical-chain slack + delay forecast' -- the schedule-engine gold standard the notes name; closed SaaS, so no version bar is claimed.
[leantime] Leantime. Leantime open-source project management (GitHub repository, releases feed used for the v3.9.8 bar as-of 2026-08-04). Accessed 2026-08-18. publisher · read in our library knowledge/fetched/cmp_projectmgmt_leantime.html · pin hde938738e66f856137729c4c7bef342cc7ed4452599e61b5731be49d50c85bb6 · accessed 2026-08-18 · vendor-docGrounds: The Leantime column: Best on 'Time tracking / timesheets' (timesheet-first, per the note) and first-class clients on 'Team + contractor relationship graph'; the matrix header reads its version bar from this repository's releases feed, which is why the bar carries an as-of date.
[asana-api] Asana. Asana Developers -- API overview (developers.asana.com), accessed 2026-08-18. publisher · read in our library knowledge/fetched/cmp_projectmgmt_asana-api.html · pin hd7f2402be98b4755ac6bb95aa242604173b60c4bbceb08907dfd769b2652ed57 · accessed 2026-08-18 · vendor-docGrounds: The Asana column: Best on 'Custom fields per task', 'Task tags / labels / saved filters', 'Task comments / discussion threads', 'Approval / sign-off workflow' and 'Real-time collaborative editing' -- the work-graph API is the documented surface those codes rest on; closed SaaS, no version bar.
[asana-mcp] Asana. Using Asana's MCP Server -- a Model Context Protocol server exposing the Asana Work Graph to AI assistants (developers.asana.com), accessed 2026-08-18. publisher · read in our library knowledge/fetched/cmp_projectmgmt_asana-mcp.html · pin hf17c57bed8752c57a6f0369fff73a5f9fe9ea62e519e2b7cb87dfe9f9b69a65a · accessed 2026-08-18 · vendor-docGrounds: The 'API + MCP agent tools' row: its note says Asana ships MCP too, and this is the page that says so -- our 11 coordination tools fork-exec over /mcp on the same protocol.
[openproject] OpenProject. OpenProject documentation (user guide, admin guide, API; the v17.6.0 bar was read from the opf/openproject releases feed as-of 2026-08-04). Accessed 2026-08-18. publisher · read in our library knowledge/fetched/cmp_projectmgmt_openproject.html · pin h6be6da7b0d71af099986bfc8f39e63c39066cb356714a2e130527978f1e9f7b9 · accessed 2026-08-18 · vendor-docGrounds: The OpenProject column: Yes on the task, Gantt, time-tracking, cost and portfolio rows and Part on 'Dependency scheduling + critical path' and 'Multi-mode resource-constrained scheduling' -- the open-source self-hosted comparator, still riding a third-party Ruby stack per the 'Sovereign own-stack zero per-seat cost' row.
[rfc5545] Desruisseaux, B. (ed.). RFC 5545: Internet Calendaring and Scheduling Core Object Specification (iCalendar). IETF, September 2009 -- VEVENT, RRULE recurrence, VALARM. publisher · read in our library knowledge/fetched/cmp_projectmgmt_rfc5545.html · pin h282ac461d0bcb1361f7bf9253b0ed49de451404275ff09509a90e633cc59b3ed · accessed 2026-08-18 · published-standardGrounds: The 'Calendar interop RFC5545 export + import' row: the .ics round-trip including YEARLY RRULE recurrence that nx_vizsla_ics implements is this specification, and the 'Calendar time-blocking of ready tasks' free-window math reads the same VEVENTs.
[kelley-walker1959] Kelley, J. E. and Walker, M. R. Critical-path planning and scheduling. Papers presented at the December 1-3, 1959 Eastern Joint IRE-AIEE-ACM Computer Conference, ACM, 1959. DOI 10.1145/1460299.1460318. publisher · read in our library knowledge/fetched/cmp_projectmgmt_kelley-walker1959.html · pin h0b7e1e7e71fc9f003ad3e1b9c22aaf2e083c77fccced3b3038f86f5e1fe91131 · accessed 2026-08-18 · published-paperGrounds: The 'Dependency scheduling + critical path' and 'Critical-chain slack + delay forecast' rows: the longest-path-through-precedence method that the topo-DP longest-effort chain implements is this paper's critical-path method (CPM), the origin of the schedule engine MS Project is graded Best on.
[psplib] Kolisch, R. and Sprecher, A. PSPLIB -- Project Scheduling Problem Library: benchmark instances for single-mode, multi-mode and resource-investment project scheduling (RCPSP), TUM operations-management site; the library was introduced in European Journal of Operational Research 96(1), 1997. publisher · read in our library knowledge/fetched/cmp_projectmgmt_psplib.html · pin had4344598523d45ead3bc6a0affafe50dbc7c23b6acb53e6f4f20c30971f7ee0 · accessed 2026-08-18 · datasetGrounds: The 'Multi-mode resource-constrained scheduling' gap row: the RCPSP frontier the note calls the top 2025/26 research axis is benchmarked on these instances, which is the ruler any nx_project_rcpsp rung would have to score against before claiming the cell.

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