Repository navigation
Measure Gate A on chg-loop tickets apart from human intake (US-47.11) - #1009
Merged
Merged
Conversation
Gate A's replay report gains two strata that partition all: chg_loop (tickets labelled chg-loop, which chg files with evidence) and human (every other ticket). intake and all are unchanged; the gate is not relaxed. A new dated artifact pair records the split on home_care_billing (chg_loop is empty: chg has filed nothing yet). docs/agent-delivery-loop.md states that a repository absent from DELIVERY_GATES_CONFIG escalates every change, that claude-config and chg are absent today, and the human_paths floor each must carry once it gets an entry. The globs live in the operator KB because both repositories are private. A test pins the unknown-repo escalation for both. Part of #986 (items 2 and 4).
Owner
Author
|
Review round 1 (code) counted at |
- The summary test anchors each stratum line to its start, so a missing main-strata line can no longer pass on the indented sensitivity line. - The unknown-repo pin asserts the configured repo screens clear at triage too, so the escalation is shown to come from the missing entry. - One intake_replays/1 feeds both the intake stratum and intake_is_feature_share. - Ticket and GateAReplay moduledocs say four strata; the Gate B doc names claude-config's git hooks.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
US-47.11, part of #986 (items 2 and 4).
Gate A: chg-loop tickets measured apart from human intake
Measurement.Ticketgainschg_loop?, true exactly when the labels includechg-loop; the title plays no part.Report.gate_a_strata/1builds every stratum once, and both the main report and the sensitivity run use it. It now returns:intakeandall, unchanged;chg_loop, the chg-loop tickets;human, every other ticket.chg_loopandhumanpartitionall.chg_loopflag.docs/measurements/gate_a_2026-10-19.{json,md}, made bymix loopctl.gates.measure_afrom home_care_billing's 536 issues. It is redacted the same way as the 2026-09-14 pair, which stays as it was.chg_loopis empty: chg has filed no chg-loop issue yet on home_care_billing, claude-config or chg.Gate B: self-modification
DELIVERY_GATES_CONFIGescalates every change with{:unknown_repo, repo}. A new test pins this for both repos, at the merge gate and at the triage screen.docs/agent-delivery-loop.mdstates the rule: when either repo gets an entry, itshuman_pathsmust carry its self-modification code.4a86157b, not in this public doc, because both repos are private. Every glob was checked againstgit ls-files.Item 1 (operational, done outside this PR)
claude-config and chg are enrolled as intake sources, each with its own work project and target epic, and an Issues-only webhook. Both pings returned 200.
repo_url, deliberately: the existing KB scopes already carry it, and a second project on the same URL makesresolve_projectambiguous.required_checksis empty on both. That matches the loopctl source.Tests
intakeandallunchanged.chg_loophas a nil rate.intake?fails 4 tests, hard-coding the flag fails 5, and letting chg through Gate B fails the pin.Defaults Mark may want to overrule
4a86157binto the doc.required_checksis empty on both new intake sources, so story verification recordsno_required_checksthere. To opt in, set it withintake_source_update, using job names from a PUSH run.