memdancePinnedOur Ambition: Rethinking Chip Design Cycle with AI
Building AI-first hardware engineering infrastructure for more rigorous decisions, connected evidence, and earlier investigation of costly mistakes.
THE MEMDANCE JOURNAL
Engineering evidence
Connecting observed results to the decisions they support.
Pause. Power Off. Resume the Same Experiment.
A checkpointed Dancer run on Orchestra: resume execution after power-off and verify the completed result.
One SoC, Multiple Engines, Matching Results
Taking a multicore workload through Dancer and checking its result and waveform streams across execution environments.
Evidence Built Into the Engineering Loop
How observed concurrency, event history, and meaningful execution checks turn results into better engineering decisions.
When the Right Fix Is No Fix
A blinded debugging pilot: repair a hidden defect, reject a bad expectation, and leave an unsupported physical claim unresolved.
The Clocks Looked Identical. They Belonged to Different Domains.
Identical clock schedules, an invalid connection, and a constrained correction that preserves the valid neighbor.
The Formula Was the Same. The Numeric Semantics Were Not.
A low-precision dot product, four candidate repairs, and a signed-zero error in the reference oracle.
The Response Was Correct. The Transaction Was Wrong.
Tag reuse, reset, and transaction ownership: a controlled experiment in preserved history and bounded verification evidence.
Tracing a Hardware Failure to Evidence
An independent model, a controlled correction, and a result with clear boundaries.