2 Commits

Include renames

Author	SHA1	Message	Date
Pouya LajevardiandClaude Opus 5	610edc24fd	feat: Q.Arb is held; strike C.Med-Arb entirely; dissolve the paired disclosure ... Pouya's ruling, 2026-08-29. Treated as D3-class and swept accordingly. §4 Q.Arb becomes a HELD designation. Obtained July 2026 — recorded in the register, deliberately not published. Public copy carries "Q.Arb (ADRIC / ADRIO)" beside Q.Med and nothing more. Every stage form is struck: "commenced", "in progress", "pathway", "not yet". C.Med-Arb as a stated goal is struck. This DEVIATES FROM THE STRATEGY BRIEF, which made it "the explicit long-term professional narrative"; the brief is not in this repository, so the deviation is recorded in four places so nobody reinstates it from a document no reader can open. The designation stays in §11 as a definition — what is struck is its status as a goal of his. The paired-disclosure condition dissolves. It existed only because Q.Arb was in progress; there is no stage left to disclose, and a condition with no subject cannot be half-kept. Pages /about/'s credentialing arc is DELETED, not rewritten — two held designations are not a journey. /arbitration/ loses its stage section and its "Available now, and open about the stage" h1. /med-arb/'s endpoint section is rewritten. Deleting CREDENTIALS.goal/goalName rather than emptying them turned every consumer into a build error, which is how the last two surfaced. hasCredential now maps CREDENTIALS.designations instead of indexing [0]; _DesignationRowParity pins the visible credential row to the same constant. check:claims q-arb-as-a-stage (inverted from the predecessor, which barred Q.Arb reading as HELD) and c-med-arb-struck. Each page is now scanned twice — as published, and with inline tags collapsed — because [^<] cannot cross <strong>, which this site sets in prose. Two open questions for Pouya, neither blocking: Q55 — the acquisition date. §4 says obtained July 2026; the Change Log of 2026-08-26 records "commenced August 2026", both stamped [verified — Pouya]. They cannot both be true. Nothing published turns on it. Q56 — is the mediation offering scoped commercial? §4 leaves it unscoped; four surfaces say "commercial mediation"; /practice/insurance/ offers mediation in insured-versus-insurer SABS matters. Two review rounds, all findings applied or declined with a stated reason. Round 2 found ten lines in docs/03 still instructing the struck form — the 2026-08-29 sweep missed them because `git grep 'Q.Arb'` is line-anchored and the block never names it. Sweep the vocabulary, not only the subject. Gates, exit statuses read directly, never through a pipe: npm run check exit=0 (0 errors, 0 warnings, 0 hints) npm run lint exit=0 npm run build exit=0 (12 pages) npm run check:claims exit=0 (11 patterns, 26 approved strings) npm audit exit=0 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Md3GndFqWPzK78xAoebsg5	2026-08-30 10:37:19 -04:00
Pouya LajevardiandClaude Opus 5	79b19a7bd0	feat: build step 5 — /practice/ and six area pages; check:claims gates §4 in dist ... Step 5 ships /practice/ and the six practice-area pages (construction, technology, energy, insurance, shareholder, cross-border) from one route, and adds the mechanical §4 gate Pouya ruled for. check:claims — §4 Forbidden becomes a build error scripts/check-claims.mjs greps dist/**/*.html for 10 patterns, each carrying the incident that put it there. It strips <style> and non-JSON-LD <script> first (a bare sweep for "leading" returned 26 hits, 25 of them var(--leading-body)), self-tests every pattern against fixtures before sweeping, and refuses a missing, empty or stale dist/. Wired into /build Phase 5 and both deploy paths. Q54 — six conduct undertakings publish, and §4 gains a third class Conduct undertakings sit apart from credentials and offerings: the gate is that Pouya said it in terms. The strings live in CONDUCT_UNDERTAKINGS so a softening is one visible diff. (e) and (f) replace the third-person sentences already on /arbitration/ rather than joining them. Q49, Q50 recorded as rulings. §7 records the SES us-east-1 stray identity's deletion. R11 holds typescript at its current major, with the peer-range reason recorded. Three facts corrected, two of them already shipped - The LAT gloss said mediation "before filing and continuing after filing"; the Tribunal names mediation for "Before you apply" only and its second sentence is about negotiation. An ellipsis in docs/01 had deleted it. - "Connection allocation" is not an Ontario term. - "The 2026 privacy statute" does not exist — Bill C-27 died without royal assent. Struck from docs/03 rather than corrected in place. ADR Chambers struck from /arbitration/ and from docs/01 item 3 (Pouya, 2026-08-30): the source establishes what the firm publishes, not that an outside neutral can be appointed under its rules. claims-auditor gains a second lens — for every quoted source, whether the sentence beneath stays inside what the quotation establishes. Four shipped defects had that shape and none of them is greppable. CLAUDE.md gains a convention: never truncate the output of a check you intend to believe. `npm run check | tail -3` returns warnings, hints and a blank line and drops the errors line; it was reported as passing four times while astro check was exiting 1 with 10 type errors. Gates, exit status read directly, not through a pipe: npm run check exit=0 npm run lint exit=0 npm run build exit=0 npm run check:claims exit=0 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Md3GndFqWPzK78xAoebsg5	2026-08-30 09:35:26 -04:00