OpenVault

How work happens here

This repo runs on the Netie operating system. Three agents, one loop, everything in git.

  you write the PRD  ->  prd-agent slices it into epics
                              |
                         epic-agent turns one epic into tickets
                              |
                       ticket-runner executes them
                              |
                   epic-agent re-checks: is the epic actually done?
                              |
                   all epics done  ->  back to you for feedback

Getting started in a new session - just say what you want. The agent reads CLAUDE.md, which tells it where everything lives. You do not need to re-explain the project.

Reporting a bug or asking for a feature - say it anywhere, in any repo. It gets routed to the PRD Agent, which files it against the right epic and records it in the feedback ledger. That ledger is why something you mentioned three weeks ago still lands in the right place.

Where things live

You want	Look at
what we are building and why	D:\Netie\Software Blueprint\OpenVault\
the live task list	GitHub Issues on this repo
what is true right now	STATUS.md
why the code is shaped this way	docs/decisions/
what we deliberately are not doing	PARKING_LOT.md
the rules every repo follows	D:\Netie\NETIE.md

Skills and prompts - reusable agent prompts live in D:\Netie\Internal\Prompts\. Distilled lessons and invariants live in D:\Netie-KB - search before non-trivial work with python D:\Netie-KB\scripts\kb.py search "<keywords>".

To set this up in another repo: python D:\Netie\scripts\netie_init.py <path>

One local control plane: see bottleneck → acknowledge model slots → hold keys → ship → mesh into Cortex → gated fix.

Product roles: OpenVault = keys + gate + connect + deploy/host. Cortex = brains. AirGPT = shell. FreeIDE = coding. See PRODUCT_ROLES.md — do not grow a second key vault or a third orchestrator.

Libraries for measurement stay at the repo root; the operator console lives in OpenMW.

---

Product flow

1. See — NVMe → PCIe → DRAM → VRAM → GPU path with red hotspots (/api/observe/path, Bottleneck tab)
2. Slots — every local + Cortex model acknowledged (/api/slots)
3. Keys — encrypted vault + fallback proxy
4. Ship — FreeBuild / deploy gates / email DNS checks
5. Mesh — OpenVault :5000 ↔ Cortex :8000 ↔ FreeIDE :8765 ↔ Rust :5055
6. Fix — GPU/CPU/fan control with dry_run default (/api/control/*)

---

Layout

Full tier map (incl. cloud/ route/ routers/ sentinel/): docs/ACTIVE.md.

Path	What
nvme_sentinel/	NVMe HAL, SMART, BenchRunReport (library)
Profiler/	PathTrace + capability probe (library)
OpenMW/openmw/openvault/	App tiers: health/ observe/ vault/ ship/ mesh/ control/ + more, see docs/ACTIVE.md
OpenMW/	Custody API on :5000 (redirects / → app)
apps/web/	OpenVault UI on :3010
docs/reference/	Setup, design decisions, architecture diagram, NVMe protocol spec
docs/decisions/	Decision records (DR-####-kebab-title.md)
scripts/windows/	Start-OpenVaultDemo.ps1, Start-NetieStack.ps1, Start-LocalMesh.ps1
docs/ONE_SEAT_DEMO.md	Buyer one-seat path (mocks/simulate; HT1–HT5 human-only)
openvault.local.example.json	Copy to openvault.local.json

Peer (not in this repo): Cortex at D:\Cortex → http://127.0.0.1:8000 (URL wiring only).

Three separate uv sync roots today: repo root (sentinel), OpenMW/, Profiler/.

---

nvme-sentinel quickstart

uv sync
uv run nvme-sentinel demo

uv run mypy nvme_sentinel
uv run pytest tests/unit tests/integration -q

---

Local mesh

FreeIDE :8765  ──handshake──►  OpenVault :5000  ◄──engines──  Cortex :8000
                                  │
                                  └── passkeys ──► Rust :5055

1. Start Cortex on :8000 yourself (e.g. from D:\Cortex).
2. powershell -ExecutionPolicy Bypass -File scripts\windows\Start-LocalMesh.ps1 (optional -WithRustAuth).
3. Open http://127.0.0.1:3010/peers and approve peers.
4. Connect pack: .openvault/connect_pack.json.

cd OpenMW && uv sync
uv run openmw console --cortex-url http://127.0.0.1:8000 --openide-url http://127.0.0.1:8765

---

Documentation

• Law: CLAUDE.md · Map: docs/ACTIVE.md
• Current state: STATUS.md · History: CHANGELOG.md
• Deferred backlog: PARKING_LOT.md
• Decision records: docs/decisions/
• Setup: docs/setup.md
• Design: docs/design-decisions.md
• Architecture: docs/architecture.puml
• NVMe protocol spec (nvme-sentinel source of truth): docs/reference/nvme-sentinel-spec.md
• Subprojects: OpenMW/README.md, Profiler/README.md

---

License

MIT