You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
solution-architect PR advisories are invisible to dev-lead and the approval gate (same persona-marker exemption as qa-lead) #2203
The Solution Architect persona's PR advisory has the same fate as qa-lead's: dev-lead never responds and the approval gate never requires a response.
Unlabelled on purpose. This needs the same policy ruling as the qa-lead companion issue.
Mechanism
Reach. It is served only via @mention (personas/solution-architect/persona.yml:63-75, interaction.yml:8-12).
How it posts. It posts as don-petry through the same persona runner (persona.yml:100-103), so the body carries <!-- persona:solution-architect -->.
Same three skips as qa-lead:
gate exemption, maintainer-comment-gate.sh:74;
prompt skip, fix-reviews.md:161;
no dev-lead intent, dev-lead-intent.sh:635-640.
Escalation.prompts/solution-architect/advisory.md:111: "you cannot block, only say so". Nothing reads its escalation.
Contract. Its contract emits only comment:advisory-response. Nothing obliges dev-lead to answer.
Impact is lower than qa-lead's because a human must summon it. That also means the human asked for the input and expects it acted on, which makes silently ignoring it worse.
Proposed acceptance criteria (pending the policy ruling)
Apply the same fix as qa-lead: split the recursion guard from the disposition exemption, and have dev-lead disposition each finding.
Architecture escalations hold the PR until a maintainer or a fixed disposition clears them.
Record the obligation in interaction-contracts/dev-lead.yml.
Prefer one shared mechanism for all advisory personas (qa-lead, solution-architect, security-lead, sre-lead, devops-lead) rather than per-persona special cases.
Related
qa-lead companion issue, filed alongside this one.
Thanks for the detailed write-up and for tracing the exact skip points (gate exemption, prompt skip, and missing dev-lead intent). To confirm the scope before work starts: for architecture escalations from solution-architect, should an unresolved one hold the PR until a maintainer or a fixed disposition clears it, or should it only require that dev-lead record a disposition without blocking merge? Given #1787 (over-escalation), the answer determines whether calibration has to land before enforcement.
Activity
don-petry commentedon Oct 10, 2026
Companion issue for qa-lead: #2202. One shared fix for both is preferred.
Generated by Claude Code
github-actions commentedon Oct 10, 2026
Thanks for the detailed write-up and for tracing the exact skip points (gate exemption, prompt skip, and missing dev-lead intent). To confirm the scope before work starts: for architecture escalations from solution-architect, should an unresolved one hold the PR until a maintainer or a
fixeddisposition clears it, or should it only require that dev-lead record a disposition without blocking merge? Given #1787 (over-escalation), the answer determines whether calibration has to land before enforcement.