THE QUESTION
Can we rehearse a decision before trusting it?
Make the software’s behavior visible: evidence, dependencies, retries, costs and the decision a person actually approved.
Investigate a documentWorking local workflow · source, correction and approvalThis is where the laboratory meets my daily work: making complicated systems easier to understand and change responsibly.
On the workbench
7 instruments- FondeoCorrect a document field and approve the exact reviewed revision.
- Wind TunnelLose a reply, retry a request, and inspect duplicate behavior.
- Follow the ThreadTrace a field back to its source and acceptance rule.
- CausalityChange traffic and find a simulated bottleneck.
- FoundryCompare hypothetical model-routing tradeoffs.
- ContinuumSave an investigation another engineer can reproduce.
- Early notebooksInspect the earlier programs and what I corrected.
NEXT CAPABILITY / RESEARCHED, NOT BUILT
Turn real traces and declared system constraints into diagrams that stay readable while you change them. Keep AI proposals separate from the checks that accept them.
The real projects behind the direction
Constraint-based technical diagrams and interactive optimization.
A diagram optimizer, not a physical solver or proof that an architecture is correct. Researched, not integrated yet.
Recorded operation timing and parent relationships for inspectable software.
WEAVE already reads bounded local OTLP files. Recorded duration alone does not establish causality.
How the art carries information
Time runs in one direction. Branches show alternatives, edges show dependencies, and a changed state gets a brief localized signal.