📖About

Follow-on to make the web chat person-folder-native and switch off the redundant cross-channel mirror copy. Persist shared memory to the canonical person folder resolved via the person model, then disable mirroring. Fail-safe fallback to the given folder. Orion bypass.

⚖️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 -> discarded | event=filing_validity_reject | CAROL-INI-2704 filing-time validity: invalid_problem — The droid 'mirror' that cross-channel mirroring depends on is already retired, so the premise of disabling a non-existent component makes the filing invalid. (el-ci-01)
• [INI-3011 FAMILY DEATH, OBJECTIVE UNMET] event=filing_validity_reject took the last live member of family CAROL-INI-3150 terminal while the Outcome Oracle reads the objective UNMET (criterion not met: The web chat writes a user's shared memory directly to that person's ONE folder ; criterion not met: Cross-channel mirroring is switched OFF and a linked web user's message still re). This needs a human or RSI decision — refile or explicitly discard the objective. (status-router)
• Filing rejected by Elrond's validity check (invalid_problem): The droid 'mirror' that cross-channel mirroring depends on is already retired, so the premise of disabling a non-existent component makes the filing invalid. | Current state: The droid 'mirror' (Mirror) is retired, meaning the cross-channel mirroring system no longer exists. The web chat may already be writing to the canonical person folder without a mirror copy, or the mirroring is no longer active. There is no mirror to turn off. (CAROL-INI-2704) (elrond)
• [status-router] discarded -> executing | event=operator_reopen | Operator revive: mirroring-retirement follow-on, filing gate false-discarded it (orion)
• [status-router] executing -> reviewing | event=bypass_reviewing | bypass transition (or-bx-01)
• [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

• The web chat writes a user's shared memory directly to that person's ONE folder (the canonical/WhatsApp folder for a linked person), so web and WhatsApp share memory without a mirror copy. (must_have)
• Cross-channel mirroring is switched OFF and a linked web user's message still reaches the person's WhatsApp folder; an unlinked user's memory stays in their own folder (no regression). (must_have)