📖About

The Requests Inbox shows every web request as Web visitor. Root cause: Carol request classifier hardcodes user_name=Web visitor when capturing web conversations, ignoring the conversation sender_key (web:) and the Google-verified name already stored in the registry users table. Fix: resolve the visitor real name + email from sender_key -> users table; fall back to email local-part, then Web visitor only if truly anonymous. Backfill existing rows that have an email.

⚖️Decisions

• Elrond's bypass methodology checklist (a reminder, not a gate -- you've got this): 0. File it requested_mode='bypass' (planner-vs-bypass is a deliberate choice). bypass_start REFUSES a non-bypass initiative (CAROL-INI-1846), and the dispatcher only skips the bypass lane when the mode says bypass -- a 'planner' mistag lets Merlin's pipeline grab the placeholder step and block your finished work. 1. Filed as planned status -- let the bypass claim/activate it; never file active. 2. Open the bypass (bypass_start) with your droid id + the remediation answer (remediates_initiative_id=NNN, or remediates_nothing=True). 3. Work the blocks for your work-type: template -> design -> code -> test -> review. Do the real work; record decisions on the initiative as you make them. 4. Reality is recorded for you at close -- code (files changed), each decision, and the twin-review verdict become real activities tied to this initiative and show in the Activity Tracker like a planner run (CAROL-INI-1840). No dummy rows. 5. Keep the initiative status moving; it parks in 'reviewing' and is tagged uat-pending for you at close (CAROL-INI-1836), so the stuck-watchdog leaves it alone until UAT. 6. Close runs the gates (design/architecture compliance + caller-audit). If a gate flags something pre-existing or unrelated to your change, waive it with a clear written rationale -- audit, don't skip. 7. Bypass skips the planner's auto-orchestration, NOT the standards. Same template checklist, same review, same observability as a planner run. (elrond)
• [status-router] planned -> executing | event=bypass_executing | bypass transition (or-bx-01)
• [status-router] executing -> reviewing | event=bypass_reviewing | bypass transition (or-bx-01)
• Elrond re-scoped success criterion 1 (replace) on Albus's prescription — Policy P.01.02.04.16 (Elrond edits the initiative definition ONLY on Albus's prescription). Albus diagnosis: The original criterion 'capture the web visitor real name (not Web visitor)' is ambiguous about the mechanism (no owner for the code change) and unbounded (no definition of 'capture'). Replacing it with a specific, bounded patch target plus a design-review gate makes the initiative achievable by the existing agent pipeline (Archon designs, Forge implements, Argus tests, Albus verifies). (elrond)
• Elrond re-scoped success criterion 1 (replace) on Albus's prescription — Policy P.01.02.04.16 (Elrond edits the initiative definition ONLY on Albus's prescription). Albus diagnosis: The original criterion 'capture the web visitor real name (not Web visitor)' is ambiguous about the mechanism (no owner for the code change) and unbounded (no definition of 'capture'). Replacing it with a specific, bounded patch target plus a design-review gate makes the initiative achievable by the existing agent pipeline (Archon designs, Forge implements, Argus tests, Albus verifies). (elrond)
• Elrond re-scoped success criterion 1 (replace) on Albus's prescription — Policy P.01.02.04.16 (Elrond edits the initiative definition ONLY on Albus's prescription). Albus diagnosis: The original criterion 'capture the web visitor real name' is technically impossible without redesigning the Carol classifier because the classifier hardcodes 'Web visitor' at ingestion time — before the inbox step runs. Any step that only touches the inbox display can never satisfy this criterion since the real name is already lost. The corrected criterion makes the true architectural dependency (elrond)
• Elrond re-scoped success criterion 1 (replace) on Albus's prescription — Policy P.01.02.04.16 (Elrond edits the initiative definition ONLY on Albus's prescription). Albus diagnosis: The original criterion 'capture the web visitor real name' is technically impossible without redesigning the Carol classifier because the classifier hardcodes 'Web visitor' at ingestion time — before the inbox step runs. Any step that only touches the inbox display can never satisfy this criterion since the real name is already lost. The corrected criterion makes the true architectural dependency (elrond)
• [status-router] reviewing -> closed | event=operator_signoff | Auto-accepted (CAROL-INI-1859): Orion-initiated, >2 days in reviewing with no objection. (el-srac-01)

✅Success criteria

• Web requests capture the visitor Google-verified name when available (must_have)
• Falls back to email local-part, then Web visitor only if truly anonymous (must_have)
• Existing rows with an email are backfilled with a real name (must_have)