The systems library
Systems, under
examination.
Enter through a question. Follow a mechanism. Read the evidence with its limits still attached.
A selected index of engineering and research. Jay’s personal notebook is the place for perspective, artwork and current thinking.
Investigation and evidence
Ask what a boundary enforces, then inspect what actually happened.
-
Black Lantern
What actually enforces an agent’s boundaries?
Harness-bound identity and final-action authorization are checked against observed synthetic resource effects.
Executed synthetic tests in the published record. No production containment guarantee.
Read the coverage counterexample -
CipherLoop → TraceForge
Can another process check the saved record?
An investigation workflow writes observations and failures; a separate reader checks the two-file artifact contract.
Experimental workflow; offline scripted tools. Integrity does not establish task success.
Read the evidence handoff
Decisions and authority
Separate the proposal, the permission and the eventual outcome.
-
SHAD0W
When is an action eligible to happen?
A chronological timeline, explicit lifecycle state and independent paper-risk admission separate signal availability from simulated execution.
Source and tests inspected. No profitability or live-capital execution established.
Read the chronology study -
AetherForge
When is switching worth admitting?
An admission gate compares configured switching costs with staying, then accounts for thermal and queue constraints.
Four controlled mock probes; no hardware performance result.
Try the recorded admission cases
Coordination and infrastructure
Coordinate intelligence while keeping consequential authority inspectable.
-
Unhinged Agent
What survives a cancelled handoff?
Agent-service coordination and an ESPHome bridge explore cancellation and shared-service boundaries.
Controlled bridge stress tests; no hardware-in-the-loop validation.
Inspect the applied record
Applied field systems
Software for practical work, with the same attention to state and handoffs.
-
Truck-Ready HVAC
How does a field record become an operational workflow?
A historical operational backend with scoped tenancy and core tests. The preserved record keeps its implementation and limitations visible.
Historical verification. Current end-to-end workflows remain unverified.
Read the field-system record
Research and open questions
Follow the ideas across projects without mistaking a shared question for an integration.
-
Machine-Native Systems
Where should meaning meet deterministic authority?
A research argument about semantic boundaries, execution state and independently readable evidence.
Engineering direction, with inconclusive and not-run experiments stated explicitly.
Read the research argument -
TEMPER
When should a learned decision abstain?
Selective-prediction metrics and specialist-cascade research. The homepage instrument exposes a small fixed risk/coverage example.
No established cost or reliability advantage; the broader thesis remains a hypothesis.
Inspect the research scope
Historical work
Earlier experiments remain available with their original maturity and evidence boundaries.
-
Methods & prototypes
Which questions are still unresolved?
Evidence Strategy Skills, Fracture and Sightglass explore evaluation practice, failure recovery and inspection interfaces.
Methodology and experimental prototypes; incomplete runtime and approval boundaries remain documented.
Open the complete project registry