📖About

Ninad opened a track page and found it empty. The records hold a 219-character account of what that line of work IS; the page showed four words. The fence drops a whole SENTENCE when it finds money, which is right when the sentence exists to state a figure and wrong when the confidential part is a trailing CLAUSE on an otherwise good description - 'executes it directly as a bypass on the Claude Max subscription' loses the whole account of the lane to protect six words at the end. The three most important tracks in the estate were reduced to 'Owned by Albus.', 'Owned by Orion.' and 'Owned by Merlin.', and the same will have happened to any prose anywhere that mentions how something is funded. Separate the two cases: a sentence carrying an AMOUNT is still dropped whole, because the figure is the point of it; a sentence that merely names a budget ARRANGEMENT loses only that clause and keeps the rest. And where redaction genuinely empties a field, the page must SAY the subject is confidential rather than show a stub, because a stub reads as a broken page and protects nothing extra.

⚖️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)
• [delivery-check] 6 must-have criteria remain pending at bypass_end — delivery FAILED live re-performance; UAT must grade on live evidence, not checklist silence (CAROL-INI-3020): test test_ini3614.py: FAIL (no tests ran in 0.56s) (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

• A sentence naming a budget arrangement keeps everything except the clause that names it (must_have)
• A sentence carrying a money amount is still dropped whole, and no figure survives anywhere (must_have)
• The three execution-lane tracks each describe their line of work again, in the records' own words minus the money (must_have)
• Where redaction empties a field entirely the page says the subject is confidential, rather than showing a fragment (must_have)
• Measured across every live page: no page lost more than a stated fraction of its description to the fence (must_have)
• The whole-estate leak sweep still passes - fixing the over-reach reintroduces nothing (must_have)