Govern before inference
Deterministic checks and approvals sit before model-driven action, reducing ambiguity at the most consequential boundary.
Case study 01 · Agentic systems
Silent
Nexus.
A local-first AI agent harness designed so autonomy remains governed, inspectable, and honest about where execution occurs.
16Cargo crates
≈68kLines of Rust
458Tests
2.16.6Captured build
Running product
Evidence, not a mockup.
This is the actual Silent Nexus 2.16.6 welcome screen captured from the running CLI. The interface exposes version, active model, worktree, safety posture, and next actions before an agent begins work.
Control / action
Model / evidence
The problem
Agency needs boundaries.
Agent tools can look capable while hiding important operational facts: what was approved, what ran, where it ran, and what evidence remains. Silent Nexus treats those questions as product requirements, not implementation details.
My contribution
System and product engineering.
I shaped the harness around a deterministic pre-model pipeline, explicit execution approvals, durable goal state, and a presentation layer that keeps tool activity legible.
The work spans Rust architecture, CLI and TUI interaction, provider integration, sandbox semantics, release evidence, and the language used to communicate limits.
Ownership record
What I owned.
- Role
- Product and systems engineering
- Period
- 2026 — present
- Product context
- Silent Protocol
- Responsibility
- Architecture, Rust implementation, CLI/TUI interaction, provider integration, governance semantics, and release evidence
Execution architecture
Proof follows every action.
- 01 · RequestA person or goal defines the intended work.
- 02 · Deterministic checksPolicy and scope are evaluated before model-driven execution.
- 03 · ApprovalConsequential actions surface an explicit decision boundary.
- 04 · ExecutionThe available sandbox or reduced-isolation path is named honestly.
- 05 · EvidenceEvents and outcomes remain in the durable timeline.
Key decisions
Persist the evidence
Goals, events, approvals, and outcomes form a durable timeline instead of disappearing with terminal output.
Name isolation honestly
The interface distinguishes strong sandboxing from reduced isolation instead of presenting every execution path as equivalent.
Result
A harness that shows its work.
Silent Nexus brings local and hosted models into one governed workflow while keeping approvals, tool calls, state, and execution evidence visible. The repository is organized as a 16-crate workspace with roughly 68,000 lines of Rust and 458 tests in the documented baseline.
37Tagged repository releases
458Automated tests in documented baseline
16Crates separating product responsibilities
Honest boundary: the certified release target is Linux x86_64. Other platforms remain experimental until supported by equivalent release evidence, and weaker sandbox environments must report reduced isolation rather than imply containment.
Build / verify
Claim / prove