NPS-Release

English 中文版

NPS Roadmap

Version: 0.4
Date: 2026-04-30
Owner: LabAcacia / INNO LOTUS PTY LTD

Cadence

Each phase breaks into three segments:

① Spec Sprint   (2 weeks)   — freeze every spec for this phase
② Impl Sprint   (6–8 weeks) — implementation, testing, documentation
③ Review Gate   (1 week)    — community / internal review before advancing

Version convention

Version tag Meaning
v0.x-draft internal draft; breaking changes allowed
v0.x-alpha public preview; API unstable
v0.x-beta feature-complete; external testing welcome
v1.0 spec frozen; production-ready

Phase 0 — Spec Unification (2026 Q2) — ✅ done

Goal: establish the full NPS spec skeleton, unify the frame namespace and naming, produce a v0.2-draft for community comment.

Phase 1 — Core Implementation (2026 Q3) — ✅ shipped

Goal: NCP + NWP + NIP + NDP + NOP production-ready across six reference SDKs; NIP CA Server OSS in all six.

SDKs

Language Package Status
.NET LabAcacia.NPS.Core + .NWP + .NWP.Anchor + .NWP.Bridge + .NIP + .NDP + .NOP ✅ v1.0.0-alpha.11 (655 tests)
Python nps-lib (PyPI) ✅ v1.0.0-alpha.11 (211+ tests, ≥97% coverage)
TypeScript @labacacia/nps-sdk (npm) ⚠️ source/tag v1.0.0-alpha.11; npm 1.0.0-alpha.11 deprecated, alpha tag temporarily on 1.0.0-alpha.11
Java com.labacacia.nps:nps-java (Maven Central) ✅ v1.0.0-alpha.11 (112+ tests)
Rust nps-sdk + 6 sibling crates (crates.io) ✅ v1.0.0-alpha.11 (109 tests)
Go github.com/labacacia/NPS-sdk-go ✅ v1.0.0-alpha.11 (96 tests)

NIP CA Server (six-language reference deployment)

Language Stack Status
C# / .NET ASP.NET Core + SQLite + Docker ✅ v0.1
Python FastAPI + SQLite + Docker ✅ v0.1
TypeScript Fastify + SQLite + Docker ✅ v0.1
Java Spring Boot 3.4 + SQLite ✅ v0.1
Rust Axum + SQLite + Docker ✅ v0.1
Go net/http stdlib + SQLite ✅ v0.1

.NET server runtime (reference)

RFCs and CRs shipped in Phase 1

Daemons

Daemon Status at alpha.6
npsd ✅ L1 + sub-NID issuance + per-NID inbox queue (17 integration tests)
nps-registry ✅ SQLite-backed real registry (SqliteNdpRegistry, 10 tests)
nps-ledger ✅ Phase 3: SQLite + Merkle + STH + inclusion proofs + STH gossip (33 tests)
nps-runner Phase 1 skeleton (L3 runtime deferred)
nps-gateway Phase 1 skeleton (Internet ingress deferred)
nps-cloud-ca Stubbed (2027 Q1+)

nps-gateway is a process-level daemon name for Internet ingress. It does not reintroduce the retired NWP Gateway Node role; logical node roles remain Anchor Node and Bridge Node.

Completion bar

Phase 2 — Ecosystem Expansion (2026 Q4) — 🚧 in progress

Goal: adapters to existing ecosystems (MCP, A2A, gRPC), richer SDK examples, Tier-2 MsgPack production hardening.

alpha.5 Release — 2026-05-01 ✅

Completed in alpha.5

Item Notes
NPS-RFC-0004 Phase 3 — STH gossip for nps-ledger GossipState + GossipService + GET /v1/log/gossip/sth; 13 new tests
AaaS-Profile L2-09 — default reputation_policy SHOULD requirement; minimum recommended policy defined
NWP-RESERVED-TYPE-UNSUPPORTED in AnchorNodeMiddleware HTTP 501; NPS-SERVER-UNSUPPORTED status code added
topology:read capability gate on AnchorNodeMiddleware AnchorNodeOptions.RequireTopologyCapability; X-NWP-Capabilities header
cgn_est per-event on TopologyEventEnvelope UTF-8/4 estimate per §7.2 (SHOULD)
AssuranceLevel from_wire("") fix Python, TS, Java SDKs; "" → Anonymous
Spec / doc CN sync error-codes.cn.md, RFC-0004.cn.md, status-codes.cn.md all up-to-date

Deferred to alpha.6

Item Notes
NPS-CR-0002 Phase 2 — server-side Anchor middleware push of topology updates .NET reference push/notify now lands through AnchorNodeMiddleware + IAnchorTopologyService; non-.NET ports remain below
Non-.NET port of NPS-CR-0002 AnchorNodeClient topology client .NET reference done; Python/TS/Go/Java/Rust need port
Non-.NET port of NPS-RFC-0004 reputation helpers (ReputationLogClient) .NET reference done; port all six SDKs
Non-.NET port of NPS-RFC-0003 assurance-level enforcement helpers Wired in .NET; other SDKs have enum only, no enforcement helpers
NPS-RFC-0002 promotion Draft → Proposed/Accepted Closed by NPS-CR-0004 (2026-05-08): IANA PEN 65715 assigned; OID arc 1.3.6.1.4.1.65715 replaces provisional 1.3.6.1.4.1.99999; RFC-0002 promoted Draft → Proposed (wire-in lands in alpha.6)

alpha.6 Task Queue

Tasks queued for v1.0.0-alpha.11:

In-flight RFCs / CRs

Item Notes
NPS-CR-0002 Phase 2 — server-side Anchor middleware push of topology updates .NET reference complete; alpha.6 closes the node_kind compatibility window and requires topology.filter.node_roles
NPS-RFC-0002 promotion Draft → Proposed/Accepted Closed by NPS-CR-0004 (2026-05-08): IANA PEN 65715 assigned; OID arc 1.3.6.1.4.1.65715 replaces provisional 1.3.6.1.4.1.99999; RFC-0002 promoted Draft → Proposed (wire-in lands in alpha.6)

SDK parity gaps

Item Notes
Non-.NET port of NPS-CR-0002 AnchorNodeClient topology client .NET reference done; Python/TS/Go/Java/Rust need port
Non-.NET port of NPS-RFC-0004 reputation helpers (ReputationLogClient) .NET reference done; port all six SDKs
Non-.NET port of NPS-RFC-0003 assurance-level enforcement helpers Wired in .NET; other SDKs have enum only, no enforcement helpers

Protocol / spec items

Item Notes
NDP.ResolveFrame DNS TXT resolution (nwp:// → physical endpoint) ✅ Implemented in all six SDKs — resolve_via_dns / resolveWithDns / ResolveViaDns; injectable DnsTxtLookup
nps-gateway process-level L2 Internet ingress (:8080→:443 termination, NCP over TLS) Skeleton only at alpha.4; L2 conformance deferred
nps-runner L3 FaaS task runtime Skeleton only; full impl Phase 3 scope

Tooling

Item Notes
NPS Studio — visual debugger for NPS frame streams Phase 2 target; not yet started
NPS Probe — Agent Coder conformance CLI Phase 2 target; not yet started

Phase 3 — Ecosystem Validation (2027 Q1–Q2)

Goal: real-world PoCs, NPS Cloud CA v1.0 live, lay the groundwork for de-facto standard status.

Phase 4 — Standardization (2027 Q3 onward)

Goal: push NPS toward formal W3C / IETF standardization; freeze NPS 1.0.

Milestone Dependency Graph

Phase 0                Phase 1                  Phase 2             Phase 3
──────                 ────────                 ────────            ────────
[spec skeleton]
    │
    ├──→ [NPS.Core] ──→ [NWP Memory/Action] ──→ [Complex Node]
    │         │                  │              [mcp-ingress] ──→ [framework integrations]
    │    [NIP CA OSS] ──────────────────────→  [a2a-ingress]
    │         │                               [grpc-ingress]
    └──→ [six SDKs] ─────────────────────────→ [SDK parity]
                                               [NDP DNS TXT]
                                               [NOP orchestr] [Cloud CA]──→ [PoC]

Risk Register

ID Risk Probability Impact Mitigation
R01 Spec changes force implementation rework High High Phase 0 freezes spec before implementation; changes go through RFC
R02 MCP ecosystem evolves quickly, breaks the ingress adapter Medium Medium Version mcp-ingress independently
R03 Token savings fall short (<30%) Medium High Benchmark from Phase 1 (actual: 45 %); AnchorFrame hit rate is the lever
R04 NIP CA private-key incident Low Critical Reserve HSM interface; enforce annual key rotation
R05 Competitor reaches similar positioning first Medium Medium NPS differentiates on Token Economy; accelerate OSS release
R06 Phase 3 PoC partner resources fall through Medium Medium Backup: internal demo datasets in lieu of real partners
R07 W3C/IETF cycle too long High Low Pursue de-facto-standard path (GitHub adoption) before formal RFC
R08 IANA PEN assignment delayed Medium Low RFC-0002 ships with provisional OID; IANA PEN is non-blocking for alpha releases

Copyright: LabAcacia / INNO LOTUS PTY LTD · Apache 2.0

This site is open source. Improve this page.