Developer Guide

Content layout

docs/
├── index.md
├── rfc/
│   ├── index.md
│   ├── RFC-NVS-GOV-0001.md
│   ├── RFC-NVS-0199.md
│   └── …
├── architecture/
├── products/
├── governance/
├── developer/
└── compliance/

RFC contribution workflow

1. Open a PR against GemminAI/sensos-docs.
2. Add or update Markdown under docs/rfc/ with required frontmatter.
3. Follow the five-stage change control in RFC-NVS-GOV-0001.
4. Do not manually edit /compliance/index.json — CI generates it.

Required RFC frontmatter

---
title: Example Title
status: Proposed
category: Runtime protocol
version: "1.0.0"
updated: 2026-07-26
repository: GemminAI/nvs-runtime
supersedes: []
superseded_by: []
related:
  - RFC-NVS-0199
---

Machine interfaces

• GET /api/v1/rfc.json — RFC index JSON
• GET /api/v1/products.json — product identity map
• GET /api/v1/rfc/{id}.json — RFC metadata + markdown
• GET /compliance/index.json — compliance index

GraphProvider & Graphify (optional)

The Graph section is a semantic navigation layer backed by GraphProvider (current: GraphifyProvider). Artifacts under public/graph/ are optional and must never block documentation builds.

pip install graphifyy
graphify .
mkdir -p public/graph
cp graphify-out/graph.html graphify-out/graph.json graphify-out/GRAPH_REPORT.md public/graph/

Internal API surface for future agents/MCP: getNode, getNeighbors, search, getPath, getMetadata.

Full instructions: docs/graph/README.md.