NCP v0.1 draft

THE NERVOUS SYSTEM
FOR PASSIVE AI.

Powering the next generation of seamless, context-aware artificial intelligence. Nerve is the foundational infrastructure for autonomous data synthesis.

MCP standardizes what agents can use. NCP standardizes what wakes them up.

View ProtocolView ExamplesAgent Guide
Scroll to traverse

PASSIVE VS. ACTIVE AI.

Existing assistant workflows are mostly active: a user asks, then AI answers. Passive AI needs a different loop: a system senses, evaluates, routes, wakes an agent, then acts or notifies within a policy boundary.

THE NCP ROLE

NCP does not replace MCP. It standardizes the trigger envelope that tells a passive runtime why an event matters, who owns it, how urgent it is, what context is referenced, and what actions are allowed.

Active AI

Manual prompt

Remind me if the time change is going to affect anything this week.

User has to ask first
Passive AI

NCP trigger

Upcoming time change may affect wake times, school dropoff, recurring meetings, and automated routines.

System wakes the right agent
Signal path
  1. 01 // calendar
  2. 02 // calendar.time_change
  3. 03 // score relevance
  4. 04 // route to family_logistics_agent
  5. 05 // daily_digest
{
  "ncp_version": "0.1",
  "type": "trigger",
  "source": {
    "system": "calendar",
    "event_type": "calendar.time_change"
  },
  "domain": "calendar",
  "subject": "Daylight saving schedule shift",
  "summary": "Upcoming time change may affect wake times, school dropoff, recurring meetings, and automated routines.",
  "severity": "medium",
  "sensitivity": "family",
  "recommended_route": {
    "agent": "family_logistics_agent"
  },
  "delivery_policy": {
    "urgency": "daily_digest"
  }
}
Active architecture

THE NERVE
ROUTING LOOP

NerveEndings gather signals from the world, NerveSynapse receives external events, NerveBridge converts legacy alerts into NCP triggers, and NerveOS System decides whether to wake an agent, route to a digest, notify, act, or suppress.

NerveEndings

apps
alerts
wearables
calendar
sensors
NCP

NerveOS System

policy + relevance + route selection

score relevance
apply policy
respect sensitivity
route intent

Reflex outputs

wake agent
digest
notify
act
suppress
01 sense system and human state
02 normalize into NCP triggers
03 route by policy, urgency, and context
Reflex layer

WAKE
EQUIP
ACT

The NerveOS System wakes agents, routes context, and enforces policy as the agentic market evolves around it.

NCP wakes. MCP equips. NerveOS decides.

01

NCP standard

NCP trigger

standard event shape NerveOS receives

02

inside NerveOS

Reflex Engine

score urgency, relevance, sensitivity, policy

03

agent market

Specialist agent

security_agent, finance_agent, family_logistics_agent

04

MCP tool layer

MCP tools

GitHub, calendar, billing, docs, local systems

05

inside NerveOS

Approval gate

NerveOS enforces what can happen next

NCP standardinside NerveOS Systemspecialist agent marketexternal MCP tools
Agent wake packet
{
  "trigger": "security.secret_exposed",
  "wake": "security_agent",
  "context_refs": ["mcp://github/security-alerts/123"],
  "allowed_without_approval": ["summarize_alert", "draft_rotation_steps"],
  "requires_approval": ["revoke_key", "rotate_secret"]
}
↳draft response
↳notify user
↳execute approved action
↳write audit log

NERVE
SYSTEM

Protocol, runtime, synapse gateway, adapters, NerveSignals, and policy layer.

01 // PROTOCOL

NCP

Nerve Context Protocol

An open JSON trigger format for alerts, notifications, events, workflows, signals, and system changes.

  • source
  • severity
  • confidence
  • context_refs
02 // RUNTIME

NerveOS

NerveOS System

The runtime layer that evaluates NCP triggers, applies policy, routes work, suppresses noise, and wakes agents when needed.

  • policy
  • routing
  • relevance
03 // INTAKE

NerveSynapse

Signal intake gateway

Secure endpoint where external systems hand raw alerts or NCP-native triggers to a user's NerveOS System.

  • verify source
  • normalize event
  • route workspace
04 // ADAPTER

NerveBridge

Legacy alert conversion

Conversion layer inside NerveSynapse that maps legacy alert formats into validated NCP triggers.

  • firebase alerts
  • github alerts
  • billing events
05 // GENERATOR

NerveEndings

Generate signal adapters

Developer tool for generating app-specific NCP signal adapters, schemas, fixtures, and NerveBridge mappings from existing apps, APIs, logs, and webhooks.

  • adapter generation
  • schema fixtures
  • route hints
Factual trigger examples

REAL NCP SIGNAL AREAS

API

API spend spike

Route usage anomalies to a cost agent with evidence, projected cost, approval boundaries, and same-hour delivery.

  • api.usage.spike
  • financial
  • cost_guardian
SEC

Compromised key

Keep secrets behind context references while interrupting the right security workflow immediately.

  • security.secret_exposed
  • secret
  • security_agent
OPS

Family or field logistics

Turn schedule conflicts and readiness windows into structured triggers with owners, urgency, and permitted actions.

  • calendar.conflict
  • family/private
  • route-aware

STANDARDIZE
WHAT WAKES AI.

NCP is deployment-agnostic: local-first NerveOS System, private cloud NerveOS System, hosted NerveOS System, or a hybrid relay model. Sensitive payloads should stay behind context references instead of being copied into events.

NCP v0.1
Zod validator

NerveBridge supports

api_usage_spike // github_secret_alert // bill_due // calendar_conflict // weather_window

ncp-trigger.json
{
  "ncp_version": "0.1",
  "type": "trigger",
  "source": {
    "system": "github",
    "event_type": "security.secret_scanning_alert"
  },
  "severity": "critical",
  "sensitivity": "secret",
  "context_refs": [
    {
      "type": "mcp",
      "ref": "mcp://github/security-alerts/123",
      "sensitivity": "secret"
    }
  ],
  "recommended_route": {
    "agent": "security_agent"
  },
  "delivery_policy": {
    "urgency": "interrupt_now"
  }
}