@neuroverseos/governance 0.7.0 → 0.8.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -3,12 +3,103 @@
3
3
  [![npm version](https://img.shields.io/npm/v/@neuroverseos/governance)](https://www.npmjs.com/package/@neuroverseos/governance)
4
4
  [![license](https://img.shields.io/npm/l/@neuroverseos/governance)](LICENSE.md)
5
5
 
6
- **Control what AI can doand how it behaves across every app.**
6
+ **Behavioral governance for AI systems.** Give meaning to behavior meaning relative to the behavioral models that have been declared and governed.
7
7
 
8
- NeuroVerse is the governance layer for AI-powered devices. It gives users, developers, and organizations a single system to define permissions, behavioral personality, and role-based accessfor smart glasses, phones, agents, or any AI-enabled product.
8
+ Human intelligence and artificial intelligence are two different kinds of intelligence working together. All organizations, all systems, gather people around declared shared intent. NeuroverseOS tools help define those intentions into behaviors and those behaviors become a constitution carried out at runtime.
9
9
 
10
- **Built for multi-agent systems:** when many agents are active, they all evaluate against the same deterministic governance model.
11
- **Built for handoff:** governance is portable as world/plan artifacts, so teams can update policy quickly and hand it across agents, apps, and operators without rewriting core logic.
10
+ NeuroverseOS is the universe where human and AI meet to work together, defined by the behaviors the organization has agreed upon. **Radiant** is the behavioral intelligence layer built on top: it reads what happened, compares it against what was declared, and tells you where the work aligns and where it drifts.
11
+
12
+ Together they put you in a cocoon of behavior — not a cage, a cocoon. Something that holds your shape while you're becoming what you said you'd become.
13
+
14
+ ## Two products, one package
15
+
16
+ | Layer | What it does | Who uses it |
17
+ |---|---|---|
18
+ | **NeuroverseOS** | Governance engine — worldmodel compiler, guard engine, lens system, plan enforcement | Developers building governed AI apps |
19
+ | **Radiant** | Behavioral intelligence — reads activity, gives it meaning through the worldmodel, measures human-AI alignment | Teams and organizations (starting with Auki/ExoCortex) |
20
+
21
+ Both ship in `@neuroverseos/governance`. Install once, use either or both.
22
+
23
+ ## Radiant — behavioral intelligence for collaboration
24
+
25
+ Radiant gives meaning to behavior. It reads activity across every tool your team uses, classifies each event by who did it (human, AI, or both together), extracts behavioral signals, identifies patterns through AI interpretation governed by the worldmodel, and produces a structured read.
26
+
27
+ ### Five data sources, one pipeline
28
+
29
+ | Source | What it reads | What it reveals |
30
+ |---|---|---|
31
+ | **GitHub** | Commits, PRs, reviews, comments | What was SHIPPED — architecture decisions, code quality, collaboration patterns |
32
+ | **ExoCortex** | attention.md, goals.md, sprint.md | What was STATED — the gap between intent and action is drift |
33
+ | **Discord** | Channel messages, threads, help requests | How the team COMMUNICATES — response times, newcomer welcome, unresolved debates |
34
+ | **Slack** | Workspace messages, partner channels | How the team COORDINATES externally — client engagement, coalition alignment |
35
+ | **Notion** | Page creation, updates, staleness | How the team DOCUMENTS — knowledge crystallization, doc gaps, decision records |
36
+
37
+ All five produce `Event[]` → same pipeline → one read. One command, all sources:
38
+
39
+ ```bash
40
+ npx @neuroverseos/governance radiant emergent aukilabs/ \
41
+ --lens auki-builder --worlds ./worlds/ --view team
42
+ ```
43
+
44
+ ### Three views for different scopes
45
+
46
+ ```bash
47
+ --view community # public repos + public channels. Anyone can reproduce.
48
+ --view team # + private repos + team channels. Team exocortex.
49
+ --view full # + cross-exocortex comparison. Leader's view.
50
+ ```
51
+
52
+ ### Org-level reads
53
+
54
+ Point at an entire GitHub org, not just one repo:
55
+
56
+ ```bash
57
+ radiant emergent aukilabs/ # entire org
58
+ radiant emergent aukilabs/exocortex # single repo
59
+ ```
60
+
61
+ ### Output structure
62
+
63
+ ```
64
+ EMERGENT — what patterns are visible in the team's work
65
+ MEANING — what it means against the worldmodel (plain English, no jargon)
66
+ MOVE — what to do about it (or "nothing's broken, keep shipping")
67
+ ALIGNMENT — L/C/N/R scores (human, AI, collaboration, composite)
68
+ GOVERNANCE — audit trail: which events triggered governance, on which side
69
+ DEPTH — what Radiant can see now vs what unlocks with more reads
70
+ ```
71
+
72
+ ### Three alignment scores nobody else measures
73
+
74
+ - **L (Human work)** — is the human's activity aligned with the declared model? Not productivity — alignment.
75
+ - **C (AI work)** — is the AI's output governed by the worldmodel? Right vocabulary? Invariants respected?
76
+ - **N (Human–AI collaboration)** — when human and AI work together, is shared meaning preserved? This score only exists because the worldmodel provides a shared frame to measure against.
77
+
78
+ ### Memory + evolution
79
+
80
+ Radiant writes each read to the ExoCortex as a dated Memory Palace file. Next run reads prior history, detects pattern persistence, and proposes worldmodel evolution — what to ADD (recurring candidate patterns) and what to REMOVE (invariants that haven't fired). A lean worldmodel with 5 sharp invariants is stronger than a bloated one with 20.
81
+
82
+ ### MCP server
83
+
84
+ Configure Claude Code to call Radiant in conversation — no terminal needed:
85
+
86
+ ```json
87
+ {
88
+ "mcpServers": {
89
+ "radiant": {
90
+ "command": "npx",
91
+ "args": ["@neuroverseos/governance", "radiant", "mcp",
92
+ "--worlds", "./worlds/", "--lens", "auki-builder"]
93
+ }
94
+ }
95
+ }
96
+ ```
97
+
98
+ Ask Claude: *"What's emerging in aukilabs/exocortex this week?"* — Claude calls `radiant_emergent` behind the scenes and responds conversationally.
99
+
100
+ For the full Radiant documentation, see [`src/radiant/examples/auki/README.md`](src/radiant/examples/auki/README.md).
101
+
102
+ ## Governance engine — deterministic rules for AI
12
103
 
13
104
  ```
14
105
  What AI can do → Rules (permissions)