Debate code findings to consensus
lens-debateworkflowsetup L3★0
srid/smriti ↗What it does
Debate code changes across two structural lenses to consensus
Best for
Code reviews where structural fit matters more than style, paired with expedited fix application.
Inputs
- · git diff (committed+staged)
- · repo path
- · optional author rationale
Outputs
- · lenses' findings (struct)
- · debate transcript
- · agreed fixes (per-commit)
Requires
- · agent() (Workflow runtime)
- · parallel()
- · git diff
Preconditions
Workflow runtime; git repo with staged changes; model inference access
Failure modes
- · Lenses deadlock on boundary definitions (mitigated by 12-round cap)
- · Electricity probe fails to ground abstraction boundary
- · Consensus gap on severity/urgency interpretation
Trust signals
- · Two independent lenses (lowy + hickey)
- · Debate rounds with explicit consensus gate
- · Electricity probe grounds abstractions in code structure
- · Each fix applied as separate commit (atomic + reviewable)