Silicon observability
Debug and state-capture primitives for complex AI/HPC hardware systems: scan paths, JTAG-style control, functional state capture, and repeatable root-cause workflows.
The Observability Stack
Research notes on silicon debug, AI infrastructure, autonomous agents, and complex compute systems.
Complex systems do not become trustworthy just because they perform well. They become trustworthy when their behavior can be inspected, replayed, and debugged.
The Observability Stack is my public research surface for exploring how complex compute systems become inspectable: from scan-based silicon state capture to AI infrastructure economics, autonomous agent evals, and quantum-classical control systems.
Why this exists
This publication exists for one question: as compute systems become more capable, distributed, and autonomous, what instrumentation do we need to understand them when they fail?
In silicon, observability means state capture, scan paths, controlled debug flows, and root-cause workflows. In AI agents, it may mean goal traces, tool-call traces, uncertainty traces, replayable execution, and escalation checkpoints. In quantum-classical systems, it may mean low-latency measurement, feedback, and control. Different systems, same pressure: hidden behavior must become inspectable.
Core pillars
Debug and state-capture primitives for complex AI/HPC hardware systems: scan paths, JTAG-style control, functional state capture, and repeatable root-cause workflows.
Frameworks for reasoning about useful AI output under real constraints: latency, reliability, quality, safety, and cost.
Research notes and eval ideas for making tool-using AI agents inspectable, replayable, and debuggable.
Notes on the classical control, calibration, and observability layers that may make future quantum systems operationally useful.
Featured artifacts
A framework for reasoning about useful AI output under constraints like latency, reliability, safety, and quality.
What AI safety can learn from silicon bring-up: state capture, replay, traces, and root-cause workflows.
As AI agents move from answering to acting, safety will depend on whether we can trace, replay, and debug their behavior.
Interactive visual model for scan-chain movement, state capture, and debug intuition.
Frameworks
A layered model for tracing agent behavior from instruction to goal interpretation, planning, tool use, uncertainty, escalation, outcome, and replay.
Five levels of agent observability, from final-output-only systems to replayable execution with failure taxonomy and eval integration.
A conceptual bridge between state capture, scan/debug paths, signal traces, and agent traces, tool logs, uncertainty, and escalation.
Publication roadmap
Discussion / citation layer
Each major piece includes a thesis, citation block, and related artifacts. If you build on a framework, cite the page or link back to the canonical article. For serious feedback or collaboration, email me.