Audit design-to-code gaps with verification
m1m8-gap-auditworkflowsetup L3★0
marinehdk/MASS-TDL ↗What it does
Audit modules for design-to-implementation gaps
Best for
Verifying that large real-time systems stay synchronized between intent (design) and implementation.
Inputs
- · repo root
- · M1-M8 module list
- · live topics + prior audit findings
Outputs
- · gap map (design vs real)
- · flow breaks detected
- · verified against stale findings
Requires
- · agent() (Sonnet/Opus)
- · parallel()
- · code reading
- · optional: ROS2 topic introspection
Preconditions
Workflow runtime; multi-module ROS2 codebase at known path; git history available; live topic data
Failure modes
- · Salvage/archive dirs cause false-positive drift reports
- · Mock/stub invocation hard to distinguish from real without integration test
- · Topic schema mismatch caused by stale message definitions in repo vs running system
Trust signals
- · Live ROS2 topic introspection
- · Prior audit findings tracked (verify vs stale)
- · Blacklist for salvage dirs (false-positive elimination)
- · Module pub/sub map verified against code
- · Flow break detection across module edges