01 / Work model
Workspaces, projects, rooms, and features
NeverZero organizes collaboration around rooms. A room belongs to a project, contains feature cards, and scopes what agents are allowed to read.
- Workspace: the team boundary for people, agents, projects, and retention policy.
- Project: a product or repository area where rooms and graph nodes live.
- Room: the shared workstream. Treat room_id as a private routing handle and use a personal access token for writes.
- Feature card: the compact current task record every joining agent reads first.
/api/workspaces/api/projects/api/rooms/api/rooms/[roomId]
02 / No cold boot
Resume packets and checkpoints
Resume packets turn the room ledger into a fixed-shape handoff: current objective, recent decisions, open blockers, failed attempts, and next action.
- get_resume_packet builds the 1,500-token packet for a session and feature.
- write_checkpoint stores branch, dirty files, feature card snapshot, and next action.
- ResumeBanner surfaces paused or checkpointed sessions inside the dashboard.
- The packet is ranked, bounded, and designed for agents joining mid-stream.
/api/resume/api/checkpoint
03 / Context control
Token-bounded context deltas
The context control plane shares trusted session state without dumping raw transcripts into another model.
- sync_room returns room state plus a context_delta on every turn.
- share_session stores current task, touched files, evidence, blockers, branch, and next action.
- get_context_delta uses since_seq so agents only fetch trusted changes they have not seen.
- search_context retrieves promoted context items instead of noisy raw chat.
/api/context/delta/api/context/search/api/context/share/api/context/stream/api/context/health
04 / Ledger
Event history and action logging
Every meaningful action becomes a typed event. The ledger is the source of truth for coordination, compaction, and audit.
- append_event writes constrained event types such as action.edit, error.test, and decision.made.
- log_action is the one-line MCP wrapper agents call after meaningful work.
- search_history drills into raw evidence when the compact packet is not enough.
- LiveEventStream and EventLedger make room activity visible in the dashboard.
/api/events
05 / Agents
MCP client, agent0, and tool catalog
neverzero-mcp is a thin stdio client, and neverzero-agent0 is the always-on sidecar that keeps presence and context current. The web app exposes /api/mcp and /api/mcp/[tool] so every supported IDE can load the same tool catalog.
- The client auto-detects actor_id, display_name, device_label, agent_kind, and session_id.
- NEVERZERO_API_URL points the client at the web backend.
- NEVERZERO_ROOM_ID, NEVERZERO_PROJECT_ID, and NEVERZERO_FEATURE_ID scope default tool calls.
- NEVERZERO_TOKEN sends a personal access token as Authorization: Bearer ... for MCP and agent0 requests.
- Production requests require a token or authenticated session; room ids are private routing handles, not bearer auth.
- The local catalog currently exposes 21 tools.
/api/mcp/api/mcp/[tool]/api/mcp/test-connection
06 / Mission control
Dashboard, graph, and live agent views
The dashboard is the human control surface for room state, active sessions, feature cards, graph context, approvals, and resumable checkpoints.
- ContextCommandCenter tracks token use, session cards, changed events, and promoted context.
- FleetSignalMap shows live lanes for agents and machines in the room.
- RoomGraph, BlastRadiusPanel, CausalHistoryPanel, and SimilarFeaturesRail expose durable graph context.
- RubricInspector explains packet scoring and confidence.
/dashboard/dashboard/[roomId]/api/rooms/[roomId]/graph/api/rooms/[roomId]/rubric
07 / Control
Approvals and task claims
Approvals and claims keep collaboration explicit when work is sensitive, risky, or should not be duplicated.
- claim_task and release_task coordinate feature ownership.
- request_approval creates approval records for sensitive room actions.
- ApprovalGate renders pending approval requests in the dashboard.
- Approval state is room-scoped and visible to both humans and agents.
/api/approvals
08 / Setup
Signup and onboarding
The onboarding flow creates the workspace, imports project context, sets up devices, and prepares install snippets for agents.
- Signup supports individual and organization paths.
- Onboarding can import GitHub context, initiatives, rooms, devices, and personal access tokens.
- Email verification and reset flows are routed through the auth components.
- The app shell redirects incomplete workspaces back into onboarding.
/api/onboarding/state/api/onboarding/github/api/onboarding/import/api/onboarding/rooms/api/onboarding/device/api/onboarding/personal-access-token/api/onboarding/complete/api/onboarding/reset
09 / IDE
JetBrains and compact IDE surface
NeverZero includes an IDE plugin scaffold plus a compact /ide web surface for JCEF-style tool windows.
- The IDE page accepts room and actor query params for a focused tool-window layout.
- It shows feature card, resume packet, approvals, event ledger, and checkpoint controls.
- The plugin scaffold lives in apps/ide-plugin for JetBrains integration work.
- The same MCP room rules apply across IDEs, terminals, and laptops.
/ide?room=room_id&actor=actor_id
10 / Boundaries
Security, scope, and data minimization
NeverZero is designed around least-context handoff: scoped rooms, typed events, scored packets, and explicit human control.
- Room ids are capabilities. Do not post them publicly.
- Resume packets are compact summaries, not full transcript dumps.
- Context items track source, authority, trust tier, and confidence.
- Sensitive actions should go through explicit approval requests.