Architecture

Four machines that do not trust each other.

Separation is the design. The node that decides is not the node that executes, and the node the public can reach holds nothing it was not explicitly handed.

Control plane

control

Apple M4 Pro · 24 GB

Orchestration, CI, gate enforcement, human approval rail.

GPU executor

executor

NVIDIA RTX 5070 Ti · 16 GB

Intended inference and bounded-execution host; runtime unavailable.

Offload VM

offload

GCP Compute Engine

Long-running batch work and scheduled collectors.

Public edge

edge

Cloud Run · us-central1

This site, the public telemetry API, and privacy-bounded capital summaries.

Request path

Intent travels one direction. Authority never does.

Control plane: Orchestration, CI, and gate enforcement run on the Mac. It is the only machine permitted to approve an outward action, and it holds no execution keys.
Execution: A Windows GPU node is the intended host for inference and bounded execution. Robinhood Agentic MCP and provisioned wallets are candidate rails, not evidence that credentials, runtime installation, reconciliation, or order placement exist.
Orchestration: Grok Super Heavy is the primary plant planner (high effort); local Nemotron is the offline fallback. Orchestrators propose and schedule — they never hold keys or place.
Telemetry: Collectors on both machines emit HMAC-signed semantic snapshots. The edge validates the signature, rejects replays, and persists to Firestore.
Public edge: Cloud Run serves this site, the architecture telemetry API, and separate privacy-bounded capital summaries. It is the only internet-reachable surface, and it can read nothing it was not pushed.

The stack

Boring technology, deliberately.

FastAPI and Python on the backend. React on the operator dashboard, statically exported Next.js for this site. Firestore for telemetry, Cloud Run for the edge, Tailscale for the mesh between machines.

None of that is interesting, which is the point. The novelty budget is spent on the safety model and the test suite, not on the framework list.

Single containerOne deploy pathNo runtime secrets in image

deploy path

# one image, one service, one domain. $./deploy.shstep 0: verify source ................. okstep 1: docker build  ................. okstep 2: docker push   ................. okstep 3: run deploy    ................. ok service   sapphire-alpha-dashboardregion    us-central1image     immutable build ID # secrets resolve at runtime, never baked in.

Scale

Surface area, counted.

Test modules

484

Files under tests/ holding the executable specification.

Solidity contracts

On-chain surface. Small on purpose — most logic stays off-chain.

Python modules

1,384

Total tracked Python files, tests included.

A note on the Solidity count. Five contracts is a small on-chain surface, and that is intentional: every line deployed to a chain is a line that cannot be patched. Logic lives off-chain where it can be tested, reverted, and re-deployed in minutes. The chain settles; it does not decide.