StoryDeck · StoryReel · commerce · data workflows · build with a coding agent ↗
Build software you can investigate.
Connect a result to the recorded steps, inputs and decisions behind it. Give people and coding agents evidence to inspect, with a clear answer when something was not captured.
Capture the connections. Keep the gaps visible.
Build · record · inspect · verify
Build with a coding agent. Debug from the record.
Use FootPrint in an ordinary application. Your coding agent can inspect its recorded run without putting an AI model inside the application.
Build
Use named stages, tracked state and explicit decisions.
Record
Run with the required recorders enabled.
Inspect
Follow the wrong result through its recorded dependencies.
Verify
Test the repair and record another run.
Share the relevant trace slice. Missing evidence stays unknown; token use and development speed depend on your workflow and tooling.
01 · the ecosystem map
hover a node — the map is a trace explorer
The ecosystem · choose the layer you need
Start with execution and record tools, add the application capabilities you need, and inspect the captured evidence through a viewer. Each library has its own capture limits.
The map shows selected core relationships. The cards below include the record tools, application libraries and viewers.
Flow, Why and Story — different views over supported execution evidence
Loading the ecosystem…