Nishi FamilyCompare › Project Management and Team Coordination

Nishi vs the Field

Project Management and Team Coordination — mechanically measured, liar-killed, sovereign.

Nishi vs Microsoft Project and Leantime and Asana and OpenProject

How this is scored. Every Nishi cell is measured: the generator reads the real organ source on disk and requires the implementing symbol to exist (no self-grading). Competitor cells record documented capability presence. Best=leads this axis, Yes=present, Part=partial, No=absent. This is capability presence, not depth or scale: the majors lead on index size and neural ranking. Nishi's genuine exceeds are the sovereignty / neutrality / determinism axes.

Feature matrix

CapabilityNishiMicrosoft ProjectLeantimeAsanaOpenProjectNotes
Task management + status workflowYesYesYesYesYesREADY/BLOCKED/DONE derived from dependency state with loud cycle detection
Dependency scheduling + critical pathYesBestPartPartPartTopo-DP longest-effort chain; MS Project is the schedule-engine gold standard
Kanban / priority boardYesPartYesYesYesEisenhower urgency x importance bands, data-driven
Milestones + progress percentYesYesYesYesYesMilestone pct from task completion
Calendar time-blocking of ready tasksYesPartNoNoNoFirst-fit by priority into REAL calendar free windows
Group find-a-time + scheduling pollsYesNoNoNoNoFree/busy intersection across member calendars plus vote tally
Portfolio multi-project registry + live boardYesPartPartPartYes1265-stream WMS registry with live HTML board; rivals tier-gate portfolio
Calendar interop RFC5545 export + importYesYesYesYesYesRound-trip .ics incl YEARLY recurrence
Reminders + once-only notification ledgerYesYesYesYesYesLead-day matching, sent-once ledger, on-site feed + email digest
Versioned document managementYesPartPartPartYesAdditive CID versions, old bytes never destroyed
Coordination-to-document generationYesNoNoNoNoPlan/venue fields emit a real .docx, filed versioned
Team + contractor relationship graphYesPartYesPartPartOne multi-tenant graph for staff and contractors; Leantime has first-class clients
Bulk personalized multi-channel commsYesNoNoNoNoSegment to personalized email/letter/card merge
RACI accountable-owner routingYesPartNoPartPartEvery activity routes to its RACI-accountable role by construction
API + MCP agent toolsYesYesPartYesYes11 coordination tools fork-exec over /mcp; Asana ships MCP too
Gantt / timeline schedule viewYesBestYesYesYesLatest-safe effort windows vs due on the portal page; MS Project gantt deepest
Time tracking / timesheetsYesYesBestPartYesAdditive LOG records + per-person timesheet; Leantime timesheet-first still deepest
Budget / cost / earned valueYesBestPartPartYesInteger EV/CPI permil from BUDGET/COST records; MS Project EVM deepest
Risk register + delay predictionYesPartNoNoPartOverdue + slack vs critical-chain, WCONF work-day as data; rivals track status not risk
Resource workload allocation + levelingYesBestNoPartPartClosed-loop: suggest AND apply as durable ASSIGN records; MS Project auto-leveling deepest
Project templates / blueprintsYesYesPartYesYesBlueprint rows + a start date emit a dated task file the planner loads
Task comments / discussion threadsYesPartYesBestYesAdditive NOTE records, task-visibility-scoped on the portal; Asana threads deepest
Contractor portal with scoped accessYesPartYesYesYesLIVE: OPAQUE login, per-person picker, cross-project 403, supervised self-healing daemon
Sovereign own-stack zero per-seat costBestNoPartNoPartOwn language compiler TLS store on your hardware; PHP/Ruby self-hosts still ride third-party stacks
Concurrent-durable additive store measured vs gitBestPartPartYesYes144/144 concurrent writes zero lost vs live git 104 refused; reflog crash-repair gated
Work liveness heartbeats ALIVE/STALLEDBestNoNoPartNoLiveness recomputed from real beats vs the clock, not self-reported status
Autonomous dispatch runs + completes workBestNoNoPartPartMachine leases a stream, runs its gate, marks DONE only on GREEN; rival rules move tasks but do not run work
Effective-owner reassignment (latest-wins history)YesYesNoYesYesASSIGN records override task owner, latest date wins, history preserved; rivals reassign destructively
Critical-chain slack + delay forecastYesBestNoNoNoOpen critical-chain minutes to finish, converted to slack days vs due; MS Project chain engine deepest
Scheduling poll vote tallyYesNoNoPartNoLatest-vote-per-member wins with lexicographic tie-break; Doodle-style, in-stack
Path-guarded store security (deny-by-default)BestYesYesYesYesStore writes confined to a namespace and dot-dot refused by construction; rivals trust the app layer
Recurring tasks (native repeat)NoYesYesYesYesNative task recurrence; ours is calendar-event recurrence only
Custom fields per taskNoYesYesBestYesUser-defined task attributes; Asana custom fields deepest
Task tags / labels / saved filtersNoYesYesBestYesTagging plus saved views; a core Asana and Leantime feature we lack
Saved baseline + schedule varianceYesBestNoYesYesSnapshot BASE records then due-slip + effort-delta variance per task; MS Project baselines still deepest
Lead / lag + dependency types (FS/SS/FF)NoBestNoYesYesOnly finish-to-start today; MS Project has the full dependency algebra
Multi-mode resource-constrained schedulingNoBestNoNoYesThe RCPSP frontier, the top 2025/26 research axis; MS Project leveling closest
Multi-skill resource matchingNoYesNoYesYesAssign by skill and availability; we match capacity only
Burndown / velocity / cumulative-flow chartsYesYesPartYesPartRemaining-effort-over-time series from DONE + effort records; visual chart rendering is the next rung
Custom dashboards / report builderNoBestYesYesYesConfigurable reporting; every incumbent has one
Approval / sign-off workflowNoYesYesBestYesFormal approvals and stage gates; Asana rules and MS Project gates
File attachments on tasksNoYesYesYesYesAttach files to a task; our doc store is project-level, not task-attached
Native mobile appNoYesYesYesPartResponsive web only; the majors ship native iOS and Android apps
CSV / MS Project importNoBestYesYesPartImport an existing plan; we author fresh only
LLM / AI planning assistantNoPartNoPartNoNatural-language plan generation; gated on the sovereign LLM engine
Real-time collaborative editingNoYesYesBestYesSimultaneous multi-user edit; a core cloud-PM feature we lack
coverage 717/1000EXCEEDS 5PRESENT 28ABSENT 13
Evidence for every claim. This is not an opinion matrix: each capability we mark present is grounded in real source and proven by a live-forked gate. See the autonomously-generated evidence page → (per-axis source lines + executed self-test verdicts) or the machine-readable evidence.json.
Honest verdict. Nishi has broad, sovereign search-engine presence — a real organ behind every core ranking and crawl axis, built bits-up in one language. It is not yet a scale or neural-ranking rival: the majors lead on index size (billions to trillions vs a Common-Crawl-seeded slice) and trained rerankers. Nishi's genuine exceeds are structural — owning the whole stack, neutrality by construction, and a zero-JS integer-deterministic result page. The climb is a bigger index and a trained reranker.

Generated by nx_swcompare_matrix (sovereign NishiLang organ) from knowledge/compare/projectmgmt.matrix — every Nishi cell verified against real organ source on disk. Zero JS, zero trackers.