code wiki / crew
topic: crew
11 modules sharing the crew name family (derived from the tree's prefix discipline).
| module | description | lines | funcs |
|---|---|---|---|
| nx_crew_capability_gate.nx | does each RACI role OWN its accountable capability, and is it an MCP API? (operator 2026-07-10: | 143 | 11 |
| nx_crew_council.nx | the crew's 3 -> 2 -> 1 checks-and-balances council | 51 | 4 |
| nx_crew_council_test.nx | proves the crew council's 3 -> 2 -> 1 decision logic | 57 | 1 |
| nx_crew_live_verify.nx | SOVEREIGN live verification of the nishi_crew MCP plane over the PUBLIC EDGE, every rung | 260 | 14 |
| nx_crew_page.nx | GENERATOR (not hand-authored HTML, per build-generators-not-artifacts) for the CREW CAPABILITY | 137 | 9 |
| nx_crew_roster_gate.nx | THE CREW-COMPLETENESS GUARD (operator 2026-07-10: "are you sure you have them all"). | 120 | 13 |
| nx_crew_scribe.nx | how the areas COMMUNICATE + a team member DOCUMENTS it. Every handoff | 81 | 7 |
| nx_crew_scribe_test.nx | show the areas handing DELIVERABLES to each other, each documented | 18 | 1 |
| nx_crew_selfheal.nx | the SAFE-ACT loop: the crew doesn't just SEE a problem, | 109 | 6 |
| nx_crew_serve.nx | the ONE consolidated crew-capabilities MCP backend (operator 2026-07-10: "each role owns its raci | 237 | 16 |
| nx_crew_tool_register.nx | register the nishi_crew capability-directory API into the sovereign tool registry | 46 | 4 |