SILVER/NODEDC_1C
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Привязать detector gate к accepted agent loop

Browse Source
This commit is contained in:
dctouch
2026-06-03 11:33:42 +03:00
parent 50d4daf64e
commit c8a58f6163
5 changed files with 167 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/orchestration/domain_scenario_loop_repo_adapter.md
+2
View File
@@ -195,6 +195,8 @@ When the coder result is `patched`, the next `ingest-gui-run` is treated as post
The stage closing gate enforces that rule even when the inner pack loop reports `accepted`: `loop_accepted_gate` preserves the raw loop verdict, but stage-level `accepted_gate` stays `false` with `stage_closing_gate.status = blocked_pending_repair_validation` until the latest patched repair has a matching successful validation run.
Inside the autonomous domain pack loop, acceptance is detector-aware as well: `accepted_gate` requires analyst acceptance, deterministic gate success, and a clean detector-results gate. If `detector_results.json` reports `fail` or `review`, the loop must not close as accepted; it should surface the failed/review detector names in `business_audit.json`, `loop_state.json`, and the Lead Codex handoff so the next repair pass starts from the concrete user-facing signal instead of a hidden green status.
## Placeholder contract
Scenario questions can reference earlier step outputs with placeholders such as: