Bind repo objective and approval boundary
passedSimulate a governed AI coding-agent run before trusting live execution.
This static run path helps a team evaluate fit before live access: bind a requirement, map the software workflow, attach verification records, and define the evidence boundary for human approval.
SDLC WorkGraph plan
Fix failing web build after dependency update
6 steps · 6 lanes · safe-stop: Discard generated handoff or patch draft
- Bind repo objective and approval boundary
- Inspect public repo metadata and failure context read-only
- Draft bounded patch or explicit blocker route
- Run available lint/typecheck/test/build verification receipts
- Capture risks, safe-stop path, and human approval request
- Emit Evidence Report handoff
Inspect public repo metadata and failure context read-only
passedDraft bounded patch or explicit blocker route
passedRun available lint/typecheck/test/build verification receipts
passedCapture risks, safe-stop path, and human approval request
waiting for humanEmit Evidence Report handoff
waiting for humanCode/style sanity
repo CI conventionsContract correctness
TypeScript/Python schema gatesBehavior regression proof
GitClaw/GitWork test disciplineDeploy readiness
Vercel/App Router gatesGovernance and approval boundary
GitClaw WorkGraph policyRisk screening
DeepBrainz guardrail taxonomyQuality signal beyond tests
DeepBrainz eval vendors: lm-evaluation-harness, lighteval, simple-evals, verifiers, frontier-evalsApproval authority
Human governance gateEdit inputs, then draft an Evidence Report · sample review JSON