governed scope · the power to build
The power to build in your own network — bounded by exactly what you allow.
Tap your running systems, question the facts, move them within your network and beyond. A governed workspace, not a dashboard.
The unit
Three things arrive together — and none of them is the hardware. A scoped builder, a private overlay that binds it to your node, and a governed door onto your systems. One unit, not three vendors to wrangle.
The builder: a workspace fully scoped and locked down, ready for your Claude Code. Your own intelligence, free to build anything within the grant — and nothing outside it.
A private, identity-based overlay binds the builder to the node — and locks everything else out. Low-overhead, and it survives flaky, distributed links; not a flat network you hope stays safe.
On the node, a governed door onto everything behind it — the power to tap running systems and move the facts out where you need them. Scoped, time-bound, revocable, audited. Raw stays put; facts flow.
How it works
A dock gives a vessel power, data, and controlled access to shore. A node is the same thing for a sensor, a camera, a PLC — or, one day, a humanoid. Power and link go in; governed facts come out.
edge compute at the seam
Now → Next
The node you deploy today on PoE is the same unit that docks an autonomous machine tomorrow — same power-plus-connectivity-plus-door. The capture device swaps; the governed memory stays constant.
What you get
Raw stays on the node. What leaves is the answer to a question you asked — cheap to keep, compounding in value.
Access is a grant on a door — verbs, scope, expiry. Expand it by editing a grant; cut it the same way.
Power, connectivity and governance arrive together, installed like structured cabling. One thing to own.
Behind it
This is a working project, not a slide. The nodes, the overlay, the door and the question path run in my own lab today — and the roadmap is a certification path, not a funding round.
Build a node
The service is governance. The hardware is only where it starts — what compounds is the facts and the network knowledge, held and managed for you through the builder.
A governed workspace running your intelligence — your own Claude subscription — bounded by a grant we control. Through it you tap systems, question the facts, and manage what's known. Scoped, revocable, audited.
Generic hardware is the starting point, not the point. Pick a body for the job — the same builder operates all of them; only the reach and capacity change.
| Tier | Body · reach |
|---|---|
| Basic leaf | Pi Zero 2W / Pi 4 · 1 PoE · one sensor or camera |
| Standard leaf | Pi 5 · 1 PoE · multiple sensors + light local processing |
| Gateway | dual-NIC, inline · taps & governs a downstream private network |
| High-spec | N100 / multi-NIC · many simultaneous taps · can host the builder on-node |
Tell me what you need to see — I’ll build the node, power it, connect it, and hand you the door.
Start a build