Pouya LajevardiandClaude Opus 5
6cfe69033f
Build and deploy / build-and-deploy (push) Failing after 4s
Four rulings from Pouya, plus what implementing them turned up. Q58 — RULED, and he attributed the ambiguity to his own document: "3.5 was meant as the TOTAL time committed, of which 2 is preparation — leaving 1.5 hours in the room. Your arithmetic caught it: if prep sat inside, 3.5 and 7 wouldn't be exactly 2x, because preparation doesn't scale with session length." The card now reads: half day up to 3 hours of session, fee includes up to 2 hours of preparation, $2,000; full day up to 6 hours, up to 3 hours of preparation, $4,000. docs/07's own research table corroborates 3 and 6 — Patey and Zuber both publish those hours, and ADR Chambers' roster rate counts preparation separately from "up to three hours of mediation". One provenance note under R14: he recalled "all or part of 3 hours" as their wording; the committed extract carries the hours but not the phrase, so docs/07 cites the hours and attributes the phrase to nobody. Two things fell out of the ruling that the instruction did not name, and both were defects. docs/07 §All parameters confirmed was itself prescribing the flat "including 2 hours of preparation" — the sentence /for-parties/ was built against, so the spec was generating the defect. And the cap had to reach the copy: "including up to 2 hours". FEES.mediation.*.hours is corrected 3.5 -> 3 and 7 -> 6; it had no consumer in src/ while the question was open, which is the only reason no page was ever wrong. /fees/ is unblocked for step 9 on the question Q58 asked. Q57 — CLOSED with no seventh undertaking. "A reader assumes the outcome, and the obvious undertaking adds nothing a reader doesn't already infer." The TODO(pouya) is replaced by the ruling where the question was; src/ now carries zero live TODO(pouya) markers. §4's mediation row lists all six published areas. Q56's ruling had named five, which was four areas plus the word "commercial" — a scope descriptor, not a seventh area. The hedge is struck on his instruction; the clause saying the six are not the authorised subject-matter list is restored, because his ruling supplied a correct value and did not close Q35(c)'s class. Split-stamped. docs/03's compliance checklist now names what to look for on a page and which §4 row decides it, never the bar's own wording. 12 items before, 12 after — a structural fix, not a coverage change. Thirteen review findings across two rounds, all applied, none declined. Three were mine to own. The capped-form rule was written and then applied to one surface: /mediation/ shipped an uncapped form in words no barred-string grep could reach, site.ts quoted a docs/07 sentence Q58 had just deleted, and §9's Q15/Q16/Q17 row prescribed the flat form — which is what a later implementer building /fees/ reads. A derived fee term was asserted as applied fact in the document that is the authority on money: "overtime begins after 3 h and 6 h" is in no ruling. Struck, and opened as Q59. And round 2 caught the arithmetic in round 1's own fix. The full-day route is flat $4,000 until hour 6, so generalising it as 500n+1000 for all n>=3 was valid only from 6 h, and "cheaper by $500 at every length" was wrong across the whole 3-6 h band. The real spread is $2,000 at three hours narrowing to $500 from six on — up to four times larger, and largest exactly where a half-day booking overruns. Written into docs/07 §Recorded dissent and §12's R5 row, which is where the 12-month fee review will read it. Round 1's fix for the missing consequence also published the overtime rate on a page that now states an unambiguous cap, defining the trigger by adjacency with no other quantity for it to attach to; the rate came off the page. R11 at the step 6 -> 7 boundary: 13 of 14 pins current. §7's TypeScript hold named one gate and there are two — typescript-eslint requires <6.1.0, tighter than @astrojs/check, so the recorded removal trigger was unreachable. Both are now named. Verified: check 0 errors, lint 0, build 0 (14 pages), check:claims 0, npm audit 0, minifier tripwire clean, zero JS shipped, all copy present with JavaScript disabled. Lighthouse not run — tool unavailable until step 7. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Md3GndFqWPzK78xAoebsg5
6979 lines
536 KiB
Markdown
6979 lines
536 KiB
Markdown
# Agent Working File
|
||
|
||
This file is a **living document** and a **full history tree** for this project —
|
||
not a snapshot. Any agent or person working here (Claude in chat, Claude Code,
|
||
Claude Cowork, or a human) maintains it by the rules below. Everything else in
|
||
this file varies by project; these rules do not.
|
||
|
||
## How to maintain this file
|
||
|
||
1. **Document everything.** On every change, record what was discussed, decided,
|
||
changed, or planned — decisions and plans included, not just executed work.
|
||
|
||
2. **Never overwrite or delete history.** When something changes, update the
|
||
relevant Current Truth section in place **and** append a dated Change Log
|
||
entry capturing old → new and why.
|
||
|
||
3. **Two parts, kept separate:** *Current Truth* is updated in place and always
|
||
reflects the present state; the *Change Log* is append-only, newest entry
|
||
first, and is never edited retroactively.
|
||
|
||
4. **Stamp facts** as `[verified YYYY-MM-DD]` or `[assumed]`. When you re-check a
|
||
fact, re-stamp it with today's date; a stale date means it needs re-verifying.
|
||
|
||
5. **Never prune the Change Log.** If the file gets unwieldy, ask before
|
||
archiving old entries to `AGENTS-history.md`. History is not destroyed.
|
||
|
||
---
|
||
|
||
# Current Truth
|
||
|
||
## 1. What this project is
|
||
|
||
A ground-up rebuild of **adr.smlcompany.ca**, the personal-brand website of the
|
||
alternative dispute resolution practice of **Pouya Lajevardi**. `[verified 2026-08-25]`
|
||
|
||
The brand's centre of gravity is the **practitioner**, not the firm and not
|
||
SML Company Ltd. Legal background, firm affiliation, and the operating company
|
||
are credibility signals referenced in support; they are not the subject.
|
||
`[verified 2026-08-25 — source: PL_ADR_Personal_Branding_Strategy_Brief.docx]`
|
||
|
||
**Positioning in one sentence:** a credentialed neutral who is also close to
|
||
live litigation and a practising machine-learning / infrastructure engineer — a
|
||
combination that is close to absent from Canadian ADR rosters, and which is the
|
||
practice's economic moat. `[verified 2026-08-25 — source: strategy brief §I, §V]`
|
||
*(Wording corrected 2026-08-26: "a working litigator" asserted conduct of
|
||
litigation, which §4 bars — see entry (q).)*
|
||
|
||
**Time horizon:** the strategy brief plans a 24-month compounding arc. The site
|
||
is built to be added to continuously, not shipped once. `[verified 2026-08-25]`
|
||
|
||
## 2. State of the thing being replaced
|
||
|
||
The site live at `adr.smlcompany.ca` as of this entry: `[verified 2026-08-25]`
|
||
|
||
> ⚠️ **Several of these measurements are contested — see Q34 (opened
|
||
> 2026-08-26).** A re-fetch of the deployed URL that day reproduced some of the
|
||
> list exactly and could not reproduce others *from the served HTML*, because
|
||
> the served document turns out to be a bundler harness whose application lives
|
||
> in nine UUID-named script files that were not fetched. **Do not cite any
|
||
> figure below as established, and do not put one in public copy, until Q34
|
||
> closes.** The items marked ⚠️ are the specific ones in doubt. This caveat sits
|
||
> here rather than only in §9 because a reader who arrives at a `[verified]`
|
||
> stamp will otherwise never learn it is under review.
|
||
|
||
- It is a **single 2.2 MB HTML file** containing an entire React application,
|
||
compiled **in the browser at runtime** by Babel Standalone loaded from unpkg.
|
||
*Confirmed on re-fetch 2026-08-26: the response is **2,206,032 bytes**, of
|
||
which **2,210,921** are inline `<script>`.*
|
||
- ⚠️ React and ReactDOM are loaded as **development** builds from a public CDN.
|
||
*Not reproducible 2026-08-26: the served file contains no reference to
|
||
`unpkg` or to a React development build. They may be inside the unfetched
|
||
bundles. Q34.*
|
||
- **Crawlers see almost nothing.** A server-side fetch of the URL returns only
|
||
`SML Company`, `DISPUTE RESOLUTION`, and the loading string `Unpacking...`.
|
||
Every word of real content is assembled client-side after three CDN round
|
||
trips. `[verified 2026-08-25 — direct fetch]`
|
||
- The deployed `<head>` has **no `<meta name="viewport">`**, no meta
|
||
description, no Open Graph or Twitter card tags, no canonical URL, and no
|
||
favicon. `[verified 2026-08-25]` — *still true of the head a crawler parses.
|
||
Note for accuracy: the harness carries a second, JSON-escaped `<head>` inside
|
||
a `<script type="__bundler/template">` which does contain a viewport tag. It
|
||
is assembled by JavaScript, so it reaches a browser and not a crawler, which
|
||
is the distinction that matters here.*
|
||
- `robots.txt` returns **403**. There is no sitemap. `[verified 2026-08-25]`
|
||
- ⚠️ The two logo PNGs are ~1 MB combined and are **base64-inlined** into the
|
||
HTML, so they cannot be cached separately from the page. `[verified
|
||
2026-08-25]` — **but a 2026-08-26 fetch found zero `base64,` occurrences
|
||
anywhere in the served document.** Q34. This figure is cited as the *reason*
|
||
for a standing convention in `CLAUDE.md` and `docs/02`, both of which now
|
||
carry the caveat. A related number, "470 KB PNG", appeared in `docs/02` with
|
||
no source anywhere in this repo and has been removed.
|
||
- `<title>` is still `SML Company · Dispute Resolution` — the pre-rebrand
|
||
placeholder title. `[verified 2026-08-25]`
|
||
- There is **no version control, no build step, and no test suite**. The
|
||
publishing mechanism is a Python script (`rebuild-standalone.py`) that inlines
|
||
the JSX components into the single file. `[verified 2026-08-25]`
|
||
- The May 2026 content brief was **partially applied** — the JSX components
|
||
under `components-standalone/` contain the corrected Pouya-branded copy, but
|
||
the document `<head>` and some structural defaults still carry placeholder
|
||
content. `[verified 2026-08-25]`
|
||
|
||
**Consequence, stated plainly:** for a site whose entire purpose is to be found
|
||
by counsel, general counsel, and appointing bodies searching for a neutral, the
|
||
current architecture is close to a worst case. This rebuild is justified on
|
||
architecture alone, independent of any content or design opinion.
|
||
`[verified 2026-08-25]`
|
||
|
||
## 3. Locked decisions
|
||
|
||
Decided with Pouya on 2026-08-25. Each of these is settled; do not re-open one
|
||
without an explicit instruction and a Change Log entry. `[verified 2026-08-25]`
|
||
|
||
| # | Decision | Chosen | Rejected alternatives |
|
||
|---|---|---|---|
|
||
| D1 | Framework | **Astro, static output, v7.x.** *Amended 2026-08-26:* the major is now pinned deliberately rather than inherited. The original `^5.0.0` pin was **recalled, not checked, and was two majors stale the day it was written**. Upgrading costs three config files now and compounds with every page; the v5 advisories were **high-severity XSS in the framework rendering a public site**, and "we don't use those authoring patterns" is a claim about all future code, not just today's. Starting two majors behind means being three behind at launch | Next.js; patching the single-file build; hand-written HTML; staying on v5 |
|
||
| D2 | Content scope | **Full re-architecture** — new IA, new pages, all copy rewritten | Copy rewrite on existing structure; audit only; technical layer only |
|
||
| D3 | Hosting & CI/CD | **Git repo + Gitea Actions → existing S3 + CloudFront.** *Amended 2026-08-26:* self-hosted **Gitea**, repo `adr-sml`. Gitea Actions uses GitHub Actions syntax, so the workflow ports nearly as is — but Gitea is not an AWS OIDC provider, so deploys authenticate with a **scoped IAM user**, rotated quarterly | GitHub Actions + OIDC; Terraform/CDK IaC; Amplify; manual deploys |
|
||
| D4 | Languages | **English only** | Full EN/FA bilingual; EN + one Farsi page; EN with FA scaffolding |
|
||
| D5 | Page structure | **Full multi-page**, ~20 URLs | Lean six-page; rich home + a few deep pages |
|
||
| D6 | Primary audience | **All four tiers**, served by different surfaces (see §5) | Single-audience focus |
|
||
| D7 | Visual design | **Keep palette and infinity mark; modernize the execution** | Faithful port; strip motion only; fresh design direction |
|
||
| D8 | Fees | **Full rate card published on a `/fees/` page** | Ranges only; on request; gated PDF |
|
||
| D9 | Insights | **Build it and launch with 3–5 drafted pieces**, every word reviewed by Pouya before publication | Launch empty; no Insights section |
|
||
| D10 | Intake | **Rebuilt intake form + calendar booking** for the confidential intake call | Structured questionnaire; form only; email/phone only |
|
||
| D11 | Rollout | **Build everything, one clean cutover.** The current site stays live untouched until replaced | Patch live site first; staging subdomain; take site down |
|
||
| D12 | Agent working file | **This file**, maintained under the constitution above | Ad hoc notes |
|
||
| D13 | Licensure claims | **The site asserts the JD only.** No claim of licensure, call to the bar, or entitlement to practise law. The approved phrasing for the boutique role is **"active litigation exposure"** or **"involvement in litigation and ADR matters"** — never "practice" **in that context**. "Practice" describing Pouya's own ADR practice — "the dispute resolution practice of Pouya Lajevardi" — is correct and stays. Pouya's direction, 2026-08-26. **Explicitly interim — see Standing Reminders §12** | Stating LSO licence status; the word "practice" |
|
||
| D14 | Fee structure | **Single published rate card, all mediation matters at one rate.** Confirmed by Pouya 2026-08-26; figures in `docs/07-fees.md`. No tribunal-secretary line | Two-tier card (recommended by Claude, declined); ranges; fees on request |
|
||
| D15 | Analytics | **Plausible.** Privacy-first and cookieless: no cookie banner, nothing to consent to, one line in the privacy policy. *Amended 2026-08-26 (Q31):* the original read "Plausible **or** Fathom", i.e. undecided, and a guessed `'plausible'` had already leaked into `src/data/site.ts` from it. **Decided, not defaulted** — Pouya checked rather than assumed and found his own assumption wrong: Fathom is Canadian-owned, which is the intuitive answer here, but it stores non-EU traffic on **US servers** and isolates in the EU only for EU visitors. Plausible keeps all data in the EU. For a practice whose privacy posture is part of the offer, EU-only beats US-hosted, and ownership is not the axis that matters | GA4; no analytics at all; **Fathom** — rejected on data residency, not on quality |
|
||
| D18 | Intake email | **Two emails per submission** — notification to `info@smlcompany.ca`, and a **confirmation receipt to the inquirer**. Pouya, 2026-08-26. The receipt is what requires SES production access (Q19) | Notification only; no email; no form at all |
|
||
| D17 | Working method | **Pouya architects; Claude Code implements and then adversarially reviews its own work.** Six-phase loop encoded in `.claude/commands/build.md`; two independent review agents in `.claude/agents/`; extended thinking on by default. Standing agreement — not restated per prompt. ***Amended 2026-08-30 — see D20:*** *the per-step review is `adversarial-reviewer` **alone**. `claims-auditor` no longer runs per step; it runs **once, at cutover, over the whole finished site**. "Two independent review agents" now describes the project, not the step* | Implement-and-report; single generic reviewer; review only on request |
|
||
| D19 | Bounding the review loop | **Review scope is `dist/`, `src/`, the specs that direct copy (`docs/01`, `03`, `04`, `07`), and `AGENTS.md` §3, §4, §7, §9, §12. TWO ROUNDS IS THE CAP. Findings are blocking or should-fix, with a "consider" only where acting on it changes what ships. A non-gating observation is a Change Log note, not a numbered question. Comments record decisions, not history.** Pouya's ruling, 2026-08-28, on his own measurement: 48 findings across two rounds with most of round two being defects in round one's fixes; 342 lines added to `src/` for 8 functional; four findings that were stale statements inside comments written that same session; and a Change Log sweep that could not reproduce because writing it changed the file it counted. His words: *"Every one is a real defect — but they are defects in the record about the record, and that is infinite regress. My fault for never bounding scope."* **Out of scope: the Change Log, the agents' own briefs, `AGENTS.md` prose outside those five sections, and the historical accuracy of code comments.** A false statement in a Change Log entry is corrected when noticed; it does not get a review pass, because no visitor reads it. Swept into `.claude/agents/adversarial-reviewer.md`, `.claude/agents/claims-auditor.md`, `/build` Phases 2–4, `/wrap` and `CLAUDE.md`. ***Amended 2026-08-30 — see D20:*** *the two-round cap governs the **per-step code review**, which is now `adversarial-reviewer` alone. It does **not** govern the single cutover claims pass — that one runs until its findings are resolved, because there is no second pass behind it. A cap on rounds is not a licence to publish an unresolved claims finding* | Unbounded scope; a third round; reporting every "consider"; a numbered question per observation |
|
||
| D20 | Where the claims pass runs | **`claims-auditor` runs ONCE, at cutover, over the whole finished site — not per build step.** Per step: **`adversarial-reviewer` alone** — correctness, accessibility, crawlability, performance, security, simplicity — two rounds max, per D19. `npm run check:claims` is **unchanged**: it runs on every build and on both deploy paths. It is the mechanical floor and it stays. **Pouya reads the copy as it is built; that is the human pass.** *Recorded in full, because "we stopped running the compliance check" must read as a calibration decision and not as erosion.* **Why.** Nothing has shipped and there is no public site, so every claims finding to date has been about a page no visitor can reach — the entire risk is deferred to cutover, and auditing nine build steps and then re-auditing the fixes is auditing a draft nobody can read. A single pass over twenty finished pages will also catch **more** than nine passes over drafts, because it sees the site as a reader does: the `/med-arb/` ADRIC gloss is the proof — no individual claim was false, the defect was **adjacency**, and adjacency defects do not exist until the pages sit next to each other. The code reviewer stays per step because **what it catches compounds** — an accessibility or crawlability defect propagates into every page built on it. A claims defect does not compound; it sits there until someone reads it. **What this costs, recorded honestly so a later reader can weigh it.** `claims-auditor` has caught, among others: the struck false universal reaching a public page in the first person; a `<title>` reading *"Sole Arbitrator"*; *"Every award I issue"* on a practice with no completed arbitration; four breaches of the Q54 gate on the day it was written; the memberships currency warranty; and a §4 Verified row authorising exactly what D16 forbids. Those are real, and several are the class of thing that reads badly on the site of a person who holds a JD. Deferring the check to cutover accepts that such a defect may live in an unpublished draft for weeks. **It must not survive cutover** — `docs/06`'s checklist carries two blocking items for it, near the top, and nothing publishes until both are clean. Pouya's ruling, 2026-08-30. Swept to `CLAUDE.md`, `/build` Phase 3, `/review`, `.claude/agents/claims-auditor.md`, `docs/06` and `docs/08` | Per-step claims audit (the status quo — its cost is recorded above, not dismissed); dropping the claims pass entirely; relying on `check:claims` alone |
|
||
| D16 | Naming the boutique | **Never named.** Referred to throughout as *a Toronto litigation and ADR boutique*. Pouya's decision, 2026-08-26 | Naming the firm |
|
||
|
||
## 4. Credential and claim register
|
||
|
||
**This is the most important section in this file.** The previous version of this
|
||
site carried a fictitious founder, invented matter values, fabricated office
|
||
locations, and a testimonial attributed to a person who does not exist. Whatever
|
||
regulatory regime does or does not apply, publishing false credentials on a
|
||
professional's marketing site is the thing this register exists to prevent. That
|
||
reason is sufficient on its own, and it does not rest on a fact this file has
|
||
never established.
|
||
|
||
**Note on this paragraph's own history, kept as a caution.** It previously read
|
||
"Pouya is a licensed legal professional", then "a legal professional", then
|
||
asserted that LSO marketing rules apply — three progressively weaker forms of the
|
||
same unverified claim, each surviving a sweep meant to remove it. The register
|
||
was asserting what it could not vouch for, in the section written to stop exactly
|
||
that.
|
||
|
||
### Governing rule
|
||
|
||
> **No claim reaches a public page unless it appears in the Verified column
|
||
> below.** If a page needs a fact that is not here, stop and ask Pouya. Do not
|
||
> infer it, do not soften it into something defensible, and do not carry it over
|
||
> from the old site.
|
||
|
||
### Verified — may be published
|
||
|
||
Sourced from Pouya's own strategy brief of 2026-05-26. Self-reported by the
|
||
subject, which makes them reliable as to substance, but **currency is not
|
||
confirmed** — several are on a moving credentialing track and may have advanced
|
||
since May.
|
||
|
||
| Claim | Status |
|
||
|---|---|
|
||
| Pouya Lajevardi, JD, Bond University | `[verified 2026-08-25 — strategy brief §I]` |
|
||
| **Licence status — NOT ESTABLISHED** | `[unestablished 2026-08-26]`. This record does not know whether Pouya is licensed. He instructed that licensure be left out of the site (D13) — an instruction about the site, **not a statement of fact either way.** Do not assert it, do not deny it, do not infer it from anything else here, and do not treat any regulatory regime as established. R1 tracks the reopening |
|
||
| ~~Lawyer; Law Society of Ontario member~~ | **DO NOT PUBLISH.** Pouya directed on 2026-08-26 that licensure is left out of the site entirely; the JD is asserted, nothing further. See D13 and the Forbidden table below `[verified 2026-08-26]` |
|
||
| Director of Firm Operations, Toronto litigation and ADR boutique | `[verified 2026-08-25 — strategy brief §I]` |
|
||
| Active litigation **exposure**: personal injury, construction, regulatory (POA), insurance (SABS) | `[verified 2026-08-26]`. **Wording corrected** — this row previously read "practice", the exact word D13 bars in exactly the context it bars it. The register was quoting the strategy brief verbatim and contradicting its own rule. The underlying fact is unchanged |
|
||
| Q.Med designation through ADRIC / ADRIO | `[verified 2026-08-25 — strategy brief §I]` |
|
||
| Has completed multiple sole mediations | `[verified 2026-08-25 — strategy brief §I]` — count deliberately not published, see below |
|
||
| **Practised role — "Mediator"** | `[verified 2026-08-28 — Pouya, Q49]`. **The row `Person.jobTitle` stands on, and the ruling grants exactly one.** Pouya: *"one row: 'Mediator', supported by Q.Med plus completed sole mediations."* Both supports are rows immediately above. **"Arbitrator" as a practised role is still NOT a row** — §4 Offerings verifies that appointments are *accepted* and records no completed arbitration, which is why `claims-auditor` struck *"Mediator and Commercial Arbitrator"* from the same node's `description` on 2026-08-27. The arbitration **offering** is unaffected: `description` and `serviceType` both carry it. **Q49(b) is declined by the same ruling** — one row was granted and the corporate relation *"the entity the practice operates through"* was not it, so `worksFor` stays out of the graph. The row that does exist is *"Operator of SML Company Ltd. **alongside** the practice"*, a different structural relation |
|
||
| **Q.Arb — HELD** | **The stamp is SPLIT, deliberately, and Pouya ratified the split on 2026-08-30.** Status: `[verified 2026-08-29 — Pouya]` — he holds it. Date: **Obtained July 2026** `[Pouya's stated basis 2026-08-29]` — the register vouches only for what he stated, never for the date itself, because it holds contrary evidence (below). **THE DATE IS RECORDED HERE AND NOT PUBLISHED.** His instruction: public copy carries **`Q.Arb (ADRIC / ADRIO)`** beside Q.Med and **nothing more** — no date, no acquisition story. ⚠️ **EVERY STAGE FORM IS STRUCK: "commenced", "in progress", "pathway", "not yet", and the "once/when I hold it" constructions.** This row read *"credentialing pathway — commenced August 2026"* `[verified 2026-08-26 — Pouya]` from 2026-08-26 until 2026-08-29, and every one of those words is now false in the **opposite** direction from the one this register normally guards — the site would be **understating** a held credential. Both directions are misdescription. ⚠️ **THE TWO DATES CANNOT BOTH BE TRUE, AND THIS ROW DOES NOT RECONCILE THEM — Q55, CLOSED UNRESOLVED 2026-08-30.** The Change Log of **2026-08-26 (a)** records *"Q.Arb dated. Old → new: `[assumed]`, stage unknown → **commenced August 2026** `[verified 2026-08-26]`"* — Pouya's own report, three days before this one. **A designation cannot have been obtained in July from a pathway that commenced in August.** One of the two self-reports is wrong and the register cannot say which. **NOTHING PUBLISHED TURNS ON IT:** the site says *held*, which is his ruling either way, and the date is not published — so this does not block. It is flagged because §4's whole function is that a stamped claim is checkable, and this one is contradicted on the face of the record. Found by `claims-auditor` 2026-08-30 and **closed the same day without being resolved — Pouya's ruling, and the distinction is the point.** *"The date is not published and nothing depends on it. A register that says 'two inconsistent reports of an unpublished fact, neither relied on' is complete."* So: the 2026-08-26 (a) Change Log report of *commenced August 2026* stands **UNRECONCILED**, permanently and on purpose. **Do not reconcile it by inference, do not re-stamp it, and do not put it back to Pouya** — it was closed by the architect, not left open. What makes the closure safe is the split stamp above: nothing in this register or on the site rests on the date. **The Forbidden row against "held, imminent, nearly complete" is struck with it** |
|
||
| ~~C.Med-Arb stated as long-term designation goal~~ | **STRUCK 2026-08-29 — Pouya. `C.MED-ARB IS OUT ENTIRELY`, and it must not be reinstated from the strategy brief**, which made it *"the explicit long-term professional narrative"*. **This is a deliberate deviation from the brief and it is recorded as one** — see the Change Log entry of 2026-08-30 (ad). His reasoning: *"Pouya holds Q.Med and Q.Arb, which is what med-arb requires. The page says he conducts med-arb and stops."* **The designation is still real and stays in §11 as a DEFINITION** — what is struck is its status as a published goal *of his*. Superseded `[verified 2026-08-25 — strategy brief §I, §IV]` |
|
||
| Kompass Arbitration Certificate Program — completed | `[verified 2026-08-25 — strategy brief §I]` |
|
||
| Stitt Feld Handy negotiation and ADR workshop sequence — completed | `[verified 2026-08-25 — strategy brief §I]` |
|
||
| Practising machine-learning and DevOps / infrastructure engineer | `[verified 2026-08-25 — strategy brief §I, §V]` |
|
||
| Bilingual English and Farsi | `[verified 2026-08-25 — strategy brief §I]` |
|
||
| Iranian-Canadian; cross-cultural fluency with diaspora business communities | `[verified 2026-08-25 — strategy brief §I]` |
|
||
| Operator of SML Company Ltd. alongside the practice | `[verified 2026-08-25 — strategy brief §I]` |
|
||
| **SML Company Ltd — incorporated FEDERALLY, under the CBCA** | `[verified 2026-08-26 — Pouya, Q30]`. Two facts were being conflated and one of them was wrong: **jurisdiction of incorporation is federal (Canada)**; **place of business is Toronto, Ontario**. `src/data/site.ts` carried `'SML Company Ltd. · Ontario, Canada'`, which reads as a jurisdiction of incorporation and named the wrong one. **No corporation number** — none is held and the line does not need one. **Caution, and it is the point of this row:** "federally incorporated" says nothing about professional licensure, and nothing about where the practice may operate. It must not be read together with the **Licence status — NOT ESTABLISHED** row into an implication that neither row makes. **Not published:** on Pouya's direction the footer reads `© <year> SML Company Ltd` and nothing further — the fact is verified and available, it is simply not on a page |
|
||
| Memberships: **ADRIC**, **ADRIO**, **OBA — Construction & Infrastructure, ADR, and Civil Litigation sections**, and the **Canadian Tax Foundation** | **`[verified 2026-08-28 — Pouya]` — RE-CONFIRMED, R10 DISCHARGED, AND NOW PUBLISHED ON `/about/`.** Q44 closed: *"All four are current as of today."* **Note on the stamp date, because it is a currency stamp and the date is the whole content:** Pouya's ruling said *"Stamp `[verified 2026-08-26 — Pouya]`"*, which is the date of the **original** confirmation. The stamp here reads **2026-08-28**, the date he actually re-confirmed — a stamp records when the assertion was made, and back-dating a re-confirmation by two days would understate the only thing the stamp is for. Flagged to him; one edit to change if he meant otherwise. **NO CURRENCY WARRANTY MAY BE PUBLISHED.** His words: *"List the memberships; promise nothing about their future state."* The struck sentence (*"Memberships are renewed annually and are listed as current"*) stays struck and nothing replaces it. **Renewal periods: the OBA sections and the CTF renew yearly. This record says NOTHING about ADRIC's or ADRIO's period** — an earlier form asserted "all four renew yearly" and that widened form propagated to four files. **He declined renewal-date tracking**, so R10 no longer fires on a date; it fires on an **event** — re-confirm before any cutover or major republish. **`memberOf` IS NOW EMITTED** on `/about/`'s Person node — Q53, ruled 2026-08-28; the withholding is dropped and this sentence said the opposite until the sweep that should have caught it was run. So the graph and the visible list assert the same four lines, and R10's event trigger covers both. `/`'s Person node omits it, because `/` shows no memberships. **CTF is a membership, not a practice area** — it is the one credential none of the six areas touch, and `docs/01-architecture.md` records why there is no seventh page at launch and when to revisit (R3) **Q51 CLOSED 2026-08-28 — the OBA sections STAY, and the distinction is structural.** Pouya: *"the Law Society is the regulator, so membership IS licensure; the OBA is a voluntary association."* That is why the `~~LSO~~` row below excludes one and this row publishes the other, and it holds **independently of eligibility details** — which is what made the question unanswerable inside this repo. Recorded so it is not re-litigated: a voluntary professional association admits members it does not license, so listing it carries no licensure implication; a regulator's membership roll *is* the licence. |
|
||
| ~~OCNI~~ | **Not current. Do not publish** `[verified 2026-08-26 — Pouya]` |
|
||
| ~~LSO~~ | **Do not publish.** Listing the Law Society among memberships implies licensure, which D13 bars. Excluded deliberately, not by oversight `[verified 2026-08-26]` |
|
||
| Toronto, Ontario; by appointment | `[verified 2026-08-26]` |
|
||
| Contact: `info@smlcompany.ca`; no public phone number; consultations by scheduled call | `[verified 2026-08-26 — Pouya]` |
|
||
| **Response time: inquiries answered within two business days** | `[verified 2026-08-26 — Pouya]`. A public commitment — it must read identically on `/contact/`, in the inquirer confirmation email, and in any bio |
|
||
| LinkedIn: `https://www.linkedin.com/in/pouyalajevardi/` | `[verified 2026-08-26 — Pouya]` |
|
||
| ~~The boutique may be named on the site~~ | **STRUCK 2026-08-26 (Q25).** Superseded by **D16 — never named.** Pouya said it *could* be named, then reversed; the permission survived the reversal and sat in the Verified table authorising exactly what D16 bars. Refer to it only as *a Toronto litigation and ADR boutique* |
|
||
|
||
### Offerings — what the practice offers, as distinct from what Pouya holds
|
||
|
||
**Added 2026-08-26 on Pouya's ruling (Q33, Q36).** Everything above this point
|
||
answers one question: *is this claim about Pouya true?* That is a question about
|
||
**credentials**. It turns out the register also has to answer a second, different
|
||
question: *does the practice offer this?* — and applying the credential test to
|
||
an offering produced a wrong answer twice in one session.
|
||
|
||
**What went wrong, because it explains the rule — stated correctly on the second
|
||
attempt.** `co-arbitration available now` was flagged across three specs on the
|
||
reasoning that §4 **then recorded** the Q.Arb pathway as merely *commenced* and
|
||
therefore could not support an arbitration offering. *(Past tense throughout this
|
||
paragraph: Q.Arb has been HELD in §4 since 2026-08-29. The error described here
|
||
is a 2026-08-26 one, and it did not depend on the credential's state.)* **That** reasoning was wrong at the
|
||
root: it silently treated a **designation** as though it were a **licence**.
|
||
|
||
*The masthead objection was a different one, and this paragraph originally
|
||
misdescribed it.* Q33-orig did not say Pouya was not entitled to arbitrate. It
|
||
said the line had been **promoted to a masthead under his name on every page,
|
||
where nothing qualifies it and it reads as a designation strip** — an objection
|
||
about **placement and implication**, not entitlement. Answering the entitlement
|
||
objection does not answer the placement one, and the first version of this
|
||
section quietly substituted the easier question. `claims-auditor` caught the
|
||
substitution. The placement objection is answered by the paired-disclosure
|
||
condition below, which is a **condition**, not a formality.
|
||
|
||
**Pouya's ruling, and the reasoning to keep.** His stated basis: ADRIC and ADRIO
|
||
designations — Q.Med, Q.Arb, C.Med-Arb — are **voluntary credentials, not
|
||
licences**, and **commercial arbitral appointment in Ontario is not gated behind
|
||
a designation** — scoped and sourced as the box below now sets out, after the
|
||
unscoped version of that sentence turned out to be false. So the constraint on offering arbitration was never *may he
|
||
act* — only *will parties appoint someone at this stage of the arc*, which is
|
||
**positional** and his to answer. He answers it: **he accepts arbitration
|
||
appointments now**, and that — his acceptance — is what the rows below record.
|
||
|
||
> ⚠️ **The legal proposition underneath is the architect's, not this register's,
|
||
> and it is deliberately NOT stamped `[verified]`.** `[verified — Pouya]` means
|
||
> *the subject reported it*, which can establish what he offers and cannot
|
||
> establish a proposition of Ontario law. That much is unchanged.
|
||
>
|
||
> **What HAS changed: there is now a source in the repo** —
|
||
> `docs/reference/ontario-family-arbitration-training.md`, the extract Pouya's
|
||
> Q39 ruling named, retrieved 2026-08-27 with its provenance and the method that
|
||
> produced it. R14 is satisfied for the half of the proposition it covers, and
|
||
> **it does not cover both halves.** Read the next paragraph before relying on
|
||
> either.
|
||
>
|
||
> **THE UNIVERSAL IS STRUCK, AND IT WAS FALSE.** This paragraph carried
|
||
> *"Anyone may be appointed an arbitrator in Ontario. Nothing in law gates the
|
||
> role behind a designation."* `claims-auditor` produced a counter-example from
|
||
> inside this repo — the site ships a **Shareholder & Family Business** practice
|
||
> area, and family arbitration looked like a place where qualification *is*
|
||
> prescribed — and **Pouya checked it and confirmed the counter-example.** His
|
||
> words, 2026-08-27: *"My assertion was FALSE as a universal."* Family
|
||
> arbitrators in Ontario must complete training approved by the Attorney
|
||
> General: **14 hours** on screening for domestic violence and power imbalances,
|
||
> **30 hours** of Ontario family law for arbitrators outside the Ontario or
|
||
> another Canadian bar, and **10 hours ongoing per two-year period**, five of
|
||
> them on domestic violence or power imbalance. Sourced, per the extract above.
|
||
>
|
||
> ⚠️ **"PRESCRIBED" WAS THE WRONG WORD FOR THE HOURS, AND IT IS CORRECTED HERE
|
||
> RATHER THAN SWEPT. Re-checked independently 2026-08-29** —
|
||
> `docs/reference/ontario-shareholder-remedies.md` carries the re-check.
|
||
> **No hour figure appears anywhere in O. Reg. 134/07, in any version.** Section
|
||
> 3 requires only that an arbitrator *"shall have received the training approved
|
||
> by the Attorney General"*, as set out on a Government of Ontario website — so
|
||
> the **requirement** is prescribed by regulation and the **content** is
|
||
> delegated to a web page. The hours are real and are confirmed word for word on
|
||
> that page; they are simply not in the instrument. Two things the original
|
||
> extract did not record: the training must have been done **within five years**
|
||
> of an arbitration unless the arbitrator averaged at least two family
|
||
> arbitrations a year across those five, and the government states that **awards
|
||
> by family arbitrators who have not completed the training are not enforceable
|
||
> by the courts.**
|
||
>
|
||
> **The shorthand *"carries prescribed training"* is left standing in the
|
||
> NOT-NEGOTIABLE bullet below, in `docs/01`, in `schema.ts` and in
|
||
> `SiteHeader.astro` — deliberately.** A regulation that imposes a training
|
||
> requirement by reference does prescribe one, and rewriting four files to
|
||
> sharpen a phrase that gates nothing is the record-about-the-record work D19
|
||
> exists to stop. The precision matters here, where the reasoning is relied on.
|
||
> **Nothing on the site says any of this:** family arbitration is not offered,
|
||
> and `/arbitration/` says only that.
|
||
>
|
||
> **The scoped replacement, and exactly whose it is.** *Commercial arbitration
|
||
> in Ontario requires no licence and no designation.* That is **Pouya's stated
|
||
> position** — `[Pouya's stated basis 2026-08-27]`, deliberately **not**
|
||
> `[verified]`. The extract establishes the **family** gate directly; it
|
||
> establishes the **commercial** half only by *absence*, because a government
|
||
> page about family arbitrators is not authority for what a commercial
|
||
> arbitrator needs. It neither mentions nor excludes commercial arbitration.
|
||
> **Do not cite it as if it did**, and do not let the scoped form drift back
|
||
> toward a universal because it now has a footnote attached.
|
||
>
|
||
> **The reason nothing on the site turns on any of this** is the scope exclusion
|
||
> two paragraphs down, not the reasoning above: family arbitration is not
|
||
> offered.
|
||
|
||
### The offering test
|
||
|
||
> **For an offering, ask about COMPETENCE. For a credential, ask about
|
||
> PERMISSION.** A credential claim needs a row in the Verified table because it
|
||
> asserts a fact about Pouya that is either true or false. An offering needs
|
||
> **three** things, and they are answered by different people:
|
||
>
|
||
> 0. **Is this a role in which the practice is PARTISAN between the parties to a
|
||
> dispute?** — ***his call, and only his.*** It is a question about **role
|
||
> design**: what the practice holds itself out as doing, which is his to
|
||
> define. Not the register's, not an implementer's, not a reviewer's.
|
||
> **If the answer is yes, the offering is refused before the test starts**,
|
||
> and neither question below is reached. Numbered **0** because it runs first
|
||
> and disposes of the candidate on its own.
|
||
>
|
||
> *The owner was left unstated when this gate was numbered on 2026-08-28,
|
||
> while gates 1 and 2 both name one and the ENE row supplied one anyway
|
||
> ("it is his to answer"). `adversarial-reviewer`: the intro promises
|
||
> "answered by different people", and this section's whole failure history is
|
||
> gate 1 being closed by the wrong party — twice, both times caught by audit.
|
||
> An unowned gate recreates that opening.*
|
||
>
|
||
> It is the gate that disposed of **settlement counsel** — and the catch was
|
||
> **Pouya's**, not this register's. §4's own row records it: *"Pouya removed it
|
||
> as his own error in `docs/01`."* An earlier version of this bullet called it
|
||
> "this register's highest-value catch"; the register's credit is for keeping
|
||
> the worked example, not for making the catch.
|
||
> 1. **Is the activity gated?** — *a question for THIS REGISTER, not for the
|
||
> subject.* It needs a source that a reviewer can check, and it is answered
|
||
> per activity and per jurisdiction, never as a class. Until it is answered,
|
||
> the offering does not ship.
|
||
> 2. **Is he competent to do it?** — *his call, and only his.* Not the
|
||
> register's, not an implementer's, not a reviewer's.
|
||
>
|
||
> ⚠️ **GATE 0 WAS UNNUMBERED PROSE UNTIL 2026-08-28, AND IT LIVED ONLY IN THE
|
||
> WORKED EXAMPLE.** The rows in the Offerings table cited "gates 2 and 3" and
|
||
> quoted Pouya's ruling about *"all three gates"* while the section titled *The
|
||
> offering test* enumerated two — so an implementer at step 5 reading the
|
||
> definition would not find a third gate at all, and the partisan check was
|
||
> invisible from the place it is defined. Found by `adversarial-reviewer`.
|
||
> **The rows' "gate 3" is this gate 0.** Numbering it 0 rather than 3 records
|
||
> that it runs before the others rather than after them.
|
||
>
|
||
> **Question 1 is not his to answer**, and an earlier draft of this test said it
|
||
> was: it ended "That is his call, not the register's, and not an implementer's"
|
||
> attached to the *whole* preceding question, gating included. That hands a
|
||
> future writer the sentence *"he says this one is ungated, and §4 says that is
|
||
> his call"* — which is the walk-through the boundary below exists to prevent.
|
||
> Split, on `claims-auditor`'s finding, 2026-08-26.
|
||
|
||
### What counts as an offering, and the rule for publishing one
|
||
|
||
> **An offering may not be published until it has a row in "Offered now" below.**
|
||
> Same force as the governing rule for the Verified table. The register created
|
||
> this category; it has to gate it too, or it is a category that authorises
|
||
> everything by saying nothing.
|
||
|
||
**Scope: an offering is a PROCESS the practice conducts** — mediation,
|
||
arbitration, med-arb, early neutral evaluation, dispute-system design,
|
||
pre-dispute technical advisory. Each needs its own row.
|
||
|
||
*`settlement counsel` was in this enumeration until 2026-08-27 and is removed
|
||
from it, not merely left unrowed: it is **not a process this practice conducts**
|
||
at all. See the struck row in the Offerings table — Q42.*
|
||
|
||
**A subject-matter area is NOT an offering.** *Construction*, *technology*,
|
||
*energy*, *insurance*, *shareholder*, *cross-cultural* are the contexts in which
|
||
the processes are conducted, not additional things offered. They are governed by
|
||
`docs/03`'s framing rule instead — *"Frame as positioning, not as history"* — and
|
||
the open half of **Q35** asks whether a one-word nav label can carry even that.
|
||
Do not read this scope note as clearing them; it says only which rule applies.
|
||
|
||
*Added 2026-08-26 on `claims-auditor`'s finding that the section had created a
|
||
category without defining either its extent or its gate — so `Med-Arb` was
|
||
sitting in the site-wide footer as an offering with no row, three sentences
|
||
below a paragraph saying not to infer exactly that. It has been removed from the
|
||
footer pending Q35(a).*
|
||
|
||
**THE BOUNDARY, AND IT IS NOT NEGOTIABLE.** This test applies **only where no
|
||
licence gates the activity.** It is not a general licence-free zone, and it must
|
||
never be read as one:
|
||
|
||
- **Mediation, and COMMERCIAL arbitration, are ungated.** No designation is
|
||
required to be appointed. The offering test governs, and Pouya has answered it.
|
||
*Scoped 2026-08-27 (Q39).* This bullet read "Mediation and arbitration are
|
||
ungated" — an unqualified statement about arbitration as a class, in the
|
||
paragraph headed **NOT NEGOTIABLE**, which is the worst place in this file for
|
||
one. **Family arbitration in Ontario carries prescribed training**
|
||
(`docs/reference/ontario-family-arbitration-training.md`), so the class
|
||
statement was false and the boundary paragraph was the thing breaching its own
|
||
boundary. Family arbitration is separately **not offered** — see the Offerings
|
||
table — so the site never relied on the false half; the record did.
|
||
- **Legal services are gated.** Providing legal services and practising law in
|
||
Ontario are restricted activities. For anything on that side of the line the
|
||
binding question is **permission**, the answer is **not established** (see the
|
||
**Licence status — NOT ESTABLISHED** row above), and **D13 bars the claim
|
||
outright.** "I offer legal representation — that is competence, not
|
||
permission" is exactly the misreading this paragraph exists to foreclose.
|
||
- **The test never converts a credential into an offering.** Offering
|
||
arbitration and holding Q.Arb remain two different statements, and the site
|
||
makes both. *This bullet read "Q.Arb is still commenced August 2026 and must
|
||
still never read as held" until 2026-08-29; the designation is now held and
|
||
the ruling that made the offering publishable never depended on it — the
|
||
reasoning above is unchanged by the change in the credential.*
|
||
|
||
### Offered now — may be published
|
||
|
||
| Offering | Status |
|
||
|---|---|
|
||
| **Mediation** — sole mediator | `[verified 2026-08-26 — Pouya]`. Q.Med held; §4 also verifies multiple completed sole mediations. ⚠️ **UNSCOPED, AND DELIBERATELY SO — Q56, ruled by Pouya 2026-08-30. Do not add "commercial" to this row, and do not scope it on a page.** **He mediates in all six published practice areas** — construction, technology, energy, insurance, shareholder, and cross-cultural. `PRACTICE_AREAS` in `src/data/site.ts` carries the full names and the six pages are built (`src/data/practice-pages.ts`); **every one of the six offers mediation**, and each is named under **Q35(c)'s subject-matter publication gate**. ⚠️ **THE SIX ARE THE VALUE, AND THE HEDGE THAT STOOD HERE FOR ONE DAY IS STRUCK — Pouya, 2026-08-31:** *"The register should match the site; 'illustrative' is a hedge covering a gap that has a correct value. Technology and energy go in."* Q56's ruling had named five — *"commercial, construction, insurance/SABS, shareholder and cross-cultural"* — which is **four of the six areas plus the word *commercial***, a scope descriptor rather than a seventh area. `adversarial-reviewer` found the row two short; it was annotated as illustrative rather than rewritten, because the words were his ruling and only he could supply the missing value. He has, so the enumeration is now the site's own six and a reader comparing register against site finds them equal. ⚠️ **BUT THE SIX ARE THE PUBLISHED AREAS, NOT THE AUTHORISED SUBJECT-MATTER LIST — that clause was struck with the hedge on 2026-08-31 and is restored the same day.** Pouya's ruling replaced *"illustrative"* with a correct value; it did not close the class. **Q35(c)'s gate still governs what may be named** — a practice area may be named where he can competently accept an appointment in that subject matter and the page frames it as positioning without claiming history — and the gate is not spent by having been used six times. Read as a closed list this row would withdraw the register's support from `/practice/cross-cultural/`'s shipped *"commercial mediations and arbitrations"*, which was deliberately left on the recorded ground that the class is open. **The six-area fact is `[verified 2026-08-31 — Pouya]`; the row's opening stamp is 2026-08-26 and said nothing about subject matter** — split, on the device this register ratified for the Q.Arb row. **Why this row and the arbitration row below do not match, so the asymmetry reads as designed rather than as an oversight:** arbitration is scoped commercial because of a **legal gate** — Q39, family arbitration in Ontario requires prescribed training. **Mediation has no such gate.** The site said *"Commercial Mediation"* on four surfaces until 2026-08-30; that was under-describing the offering, and it was corrected rather than ratified |
|
||
| **Arbitration — sole arbitrator** (commercial) | `[verified 2026-08-26 — Pouya, Q33/Q36]`. Offered **now**. Not gated by Q.Arb. **Commercial**, and the scope is now load-bearing rather than provisional: Q39 closed 2026-08-27 and **family arbitration is excluded by Pouya's choice** — see the row below. ⚠️ **THE SCOPE IS A LEGAL GATE, NOT A POSITIONING CHOICE — Q56, 2026-08-30.** Family arbitration in Ontario requires prescribed training, which is why this word is load-bearing here and **must not be copied onto the mediation row above**: mediation has no equivalent gate and is unscoped on purpose |
|
||
| **Arbitration — party-appointed** | `[verified 2026-08-26 — Pouya, Q33/Q36]`. Offered **now** |
|
||
| **Arbitration — co-arbitration** | `[verified 2026-08-26 — Pouya, Q33/Q36]`. Offered **now**. This closes Q36, which had flagged the claim as asserted in three specs and resting on no §4 row — the row is here |
|
||
| **Med-Arb** — mediation-arbitration | `[verified 2026-08-27 — Pouya, Q35]`. Offered **now**. Both halves are live: Q.Med is held, and arbitration appointments are accepted (rows above). Ungated by the same reasoning as arbitration. This closes the "Still unanswered" note that used to sit below this table, and it is why `/med-arb/` may stay in the footer sitemap |
|
||
| ~~**Family arbitration** under the *Family Law Act*~~ | **NOT OFFERED — a scope exclusion, not a gating problem** `[verified 2026-08-27 — Pouya, Q39]`. Pouya has confirmed he does not do family arbitration. It is therefore out of scope by his choice, and the prescribed-training question never arises for this practice. Recorded because the register reasoned from a false universal for one day and must not do so again — see the box above and `docs/reference/ontario-family-arbitration-training.md`. **`Shareholder & Family Business` does not touch this:** it means commercial disputes among family shareholders — shareholder and partnership disputes, co-founder breakdowns, business succession — and its page must say plainly that family law matters are not accepted |
|
||
| **Early neutral evaluation (ENE)** | **PUBLISHABLE** — Pouya's second ruling on **Q46(a)**, 2026-08-28: *"ENE, dispute-system design and pre-dispute advisory pass all three gates. Flip the rows. Step 5 unblocked."* **Gate 0 (partisan?) — passes:** delivered *to the parties* as a neutral, not for one of them. **Gate 2 (competence) — passes:** *"A neutral assessment of merits sits inside a Q.Med's competence"* `[Pouya's stated basis 2026-08-27, Q42]`. **Gate 1 (is the activity gated?) — `[Pouya's stated basis 2026-08-28]`, NOT `[verified]`, and there is still no source in `docs/reference/`.** This register held the row for one day on the ground that gate 1 needs a source a reviewer can check. He has now ruled with that objection in front of him, and **it is his call**: gate 1 is a proposition of Ontario law about his own practice, and §4 bars this file from concluding one in either direction. Same treatment as the commercial-arbitration proposition above — the ruling is **attributed**, not verified, and a later reader should read it as one. **Still the offering nearest the NOT-NEGOTIABLE boundary:** a neutral assessment of the *merits*, delivered to parties, sits closest to *"providing legal services"*, so `/practice/`'s strip must frame it as an assessment delivered to **both** parties and never as advice to one. **What would still upgrade the evidence** (an improvement now, not a gate): the Ontario *Law Society Act* s. 1 definition of "providing legal services" and LSO By-Law 4, committed verbatim to `docs/reference/`, with the application to ENE left to Pouya or to counsel — never drawn by this register or by an implementer. §4's worked-example prose cites this row for it. Priced hourly in `docs/07-fees.md`; the line item may now ship |
|
||
| **Dispute-system design** | **PUBLISHABLE** — same ruling as the ENE row above; read it for how gate 1 was closed and on whose authority. **Gate 0 — passes:** it advises *an organisation* about its future disputes, so there is no party to be partisan between. **Gate 2 — passes:** *"Consulting, no appointment, no neutrality question"* `[Pouya's stated basis 2026-08-27, Q42]` — that sentence answers **neutrality**, which is gate 0, and it is not presented here as answering gating. **Gate 1 — `[Pouya's stated basis 2026-08-28]`.** Weakest gating concern of the three: advisory consulting to an organisation is furthest from the boundary |
|
||
| **Pre-dispute technical advisory** | **PUBLISHABLE** — same ruling as the ENE row above. **Gate 0 — passes:** it precedes any dispute, so there is no party to be partisan between. **Gate 2 — passes**, in three words: *"It is the moat"* `[Pouya's stated basis 2026-08-27, Q42]`. **Gate 1 — `[Pouya's stated basis 2026-08-28]`.** ⚠️ **The caution below is NOT a publication gate and does not lift with the ruling:** advisory work for one organisation is the one item in this table that can create a **conflict against a later appointment in the same matter**. That is practice management — but no copy may imply the offering is free of that tension, and `/practice/`'s strip at step 5 is where the temptation to imply it will arise |
|
||
| ~~**Settlement counsel**~~ | **NOT OFFERED, AND IT IS STRUCK RATHER THAN UNROWED** `[verified 2026-08-27 — Pouya, Q42]`. Pouya removed it as **his own error in `docs/01`**: *"Settlement counsel acts **FOR a party** in negotiation. That is a partisan role, and putting it on a site that (a) sells neutrality and (b) asserts no licensure under D13 is **wrong twice over**: it undercuts the brand's central claim and it edges into acting for a client."* **Note the ordering — the positioning objection comes first.** It would still be wrong on a site with no licensure question at all, which is why this row does not read as a D13 consequence. Struck from `docs/01` §`/practice/`, from `docs/07-fees.md`'s hourly list, and from the §4 scope enumeration above. Never priced, never listed, never restored |
|
||
| ~~Tribunal secretary~~ | **Not offered.** D14 removed the rate and bars offering it |
|
||
|
||
**~~How the arbitration page must read~~ — THE PAIRED-DISCLOSURE CONDITION IS
|
||
DISSOLVED, 2026-08-29, Pouya.** His words: *"It existed only because Q.Arb was in
|
||
progress. There is no stage left to disclose."*
|
||
|
||
> **What it required, so the dissolution is legible.** From 2026-08-26 it bound
|
||
> every surface that offered arbitration to state the **stage** of the Q.Arb
|
||
> pathway in the same breath — `/`, `/arbitration/`, `/about/`, `/med-arb/`, the
|
||
> footer designation strip, and the `Person` and `ProfessionalService` graphs.
|
||
> The reasoning was sound while it held: the objection it answered was
|
||
> **placement** (Q33-orig — arbitration promoted to a masthead under Pouya's
|
||
> name, where nothing qualified it), and naming the stage was what made the
|
||
> offering credible rather than what made it permissible.
|
||
>
|
||
> **Why it does not survive.** The condition's subject was a stage. Q.Arb is
|
||
> **held**, so there is no stage — and a condition with no subject cannot be
|
||
> half-kept. **Do not leave a residue of it**: a page that offers arbitration and
|
||
> then reaches for something qualifying to say is reproducing the condition from
|
||
> memory. `Q.Arb (ADRIC / ADRIO)` beside `Q.Med` is the whole of it.
|
||
>
|
||
> **What is NOT dissolved with it.** The Q39 commercial scoping is untouched —
|
||
> family arbitration remains **not offered**, on Pouya's choice, and that
|
||
> exclusion never depended on the Q.Arb stage. Nor is the offering test, nor D13,
|
||
> nor D16.
|
||
|
||
**How the arbitration page must read, as amended:** it offers all three forms —
|
||
sole, party-appointed, co-arbitration — in **commercial** matters, and it names
|
||
the designations held. There is nothing further to disclose.
|
||
|
||
### Subject-matter areas — the publication gate (Q35, 2026-08-27)
|
||
|
||
**This gate did not exist, and its absence is what let `Med-Arb` sit in the
|
||
site-wide footer as an unrowed offering three sentences below a paragraph
|
||
telling readers not to infer exactly that.** Pouya's words: *"Add the
|
||
publication gate you identified was missing."* Same force as the two gates
|
||
above.
|
||
|
||
> **A practice area may be named — in the nav, in the footer, in a card — where
|
||
> BOTH hold:**
|
||
>
|
||
> 1. **He can competently accept an appointment in that subject matter.** His
|
||
> call, and only his. A subject-matter area is not a gated activity (the
|
||
> processes conducted in it are mediation and arbitration, both ungated), so
|
||
> the offering test's question 1 is already answered for it and question 2 is
|
||
> what remains.
|
||
> 2. **The page frames it as positioning, not as claimed history.** `docs/03`:
|
||
> *"Built to facilitate procurement and subcontract disputes on Ontario's
|
||
> megaproject pipeline"* — not *"extensive experience resolving"*. A page that
|
||
> claims volume it does not have fails this gate even though the label passes
|
||
> condition 1.
|
||
>
|
||
> Condition 1 is about the **label**; condition 2 is about the **page**. A label
|
||
> may ship before its page exists only where the page is already specified to
|
||
> meet condition 2 — which `docs/01` does for all six areas, `/practice/energy/`
|
||
> most explicitly (*"Write it as a genuine position, not a claim of existing
|
||
> volume"*).
|
||
|
||
### The offering test, applied — the Q42 worked example (2026-08-27)
|
||
|
||
**Kept because it is the only place in this file where the test is run on four
|
||
candidates at once and one of them fails.** Pouya's instruction was literally
|
||
*"apply the offering test"*, and the outcome was 3–1.
|
||
|
||
| Candidate | **Gate 0 — partisan between the parties?** *(his)* | Gate 1 — is the activity gated? *(the register's, with a source)* | Gate 2 — competence? *(his)* | Outcome |
|
||
|---|---|---|---|---|
|
||
| Early neutral evaluation | **No** — delivered to the parties as a neutral | **`[Pouya's stated basis 2026-08-28]`** — ruled, no source. Q46(a) closed | *"sits inside a Q.Med's competence"* | **Publishable** |
|
||
| Dispute-system design | **No** — advises an organisation; no party to be partisan between | **`[Pouya's stated basis 2026-08-28]`** — ruled, no source. Q46(a) closed | *"Consulting, no appointment, no neutrality question"* | **Publishable** |
|
||
| Pre-dispute technical advisory | **No** — precedes any dispute | **`[Pouya's stated basis 2026-08-28]`** — ruled, no source. Q46(a) closed | *"It is the moat"* | **Publishable** |
|
||
| **Settlement counsel** | **YES — acts FOR a party. Disposed of here.** | *never reached* | *never reached* | **STRUCK** |
|
||
|
||
*The gate-0 column was added 2026-08-28. Without it the only STRUCK candidate's
|
||
disposition sat inside the Q1 cell ("Never reached — failed gate 0"), so the gate
|
||
that actually disposed of it was recorded under a different gate's heading — and
|
||
a reader running the table column by column ran gates 1 and 2 only. This table is
|
||
the operational artefact; `adversarial-reviewer` found it did not run the test it
|
||
demonstrates.*
|
||
|
||
**THE Q1 COLUMN WAS FILLED IN WITH HIS ANSWERS AND HAS BEEN EMPTIED.** The first
|
||
version of this table read *"No. A non-binding neutral assessment is not a
|
||
restricted activity"* and *"No. Consulting, no appointment, no neutrality
|
||
question"* — the second of which does not even address gating. §4 is explicit:
|
||
*"**Question 1 is not his to answer**… It needs a source that a reviewer can
|
||
check, and it is answered per activity and per jurisdiction, never as a class."*
|
||
No jurisdiction was named for any of the three. `claims-auditor` caught this
|
||
substitution on 2026-08-26 in one place and again on 2026-08-28 in this table —
|
||
**the same defect, in the paragraph added to explain the defect.**
|
||
|
||
**THE COLUMN IS STILL EMPTY OF A SOURCE, AND THE ROWS ARE NEVERTHELESS
|
||
PUBLISHABLE. BOTH HALVES OF THAT ARE DELIBERATE.** Pouya ruled on 2026-08-28
|
||
that all three *"pass all three gates including the new partisan question"*.
|
||
Gates 0 and 2 are his and are answered. **Gate 1 is not usually his** — this
|
||
section says so twice, in bold, because it had twice been closed with his words
|
||
and both closures were caught by an audit rather than by the register.
|
||
|
||
**So the register declined to flip the rows, put that objection in front of him,
|
||
and he ruled a second time with it in view.** At that point the rows flip. Gate
|
||
1 asks a proposition of Ontario law about his own practice; §4 bars this file
|
||
from concluding one in either direction; and a register that holds a row against
|
||
a repeated, informed ruling is substituting its judgement for the architect's,
|
||
which is not what it is for.
|
||
|
||
**What survives, and it is the whole of the protection:** the gate-1 column
|
||
records **`[Pouya's stated basis 2026-08-28]`** and **never `[verified]`**. A
|
||
reviewer reading these rows sees an attributed position, not a sourced fact —
|
||
the same treatment §4 gives the commercial-arbitration proposition. Gate 1 was
|
||
never a veto; it was a requirement to say *whose* answer it is, and it still
|
||
does that.
|
||
|
||
**What would still improve it** is named in the ENE row: the *Law Society Act*
|
||
s. 1 definition of "providing legal services" and LSO By-Law 4, committed
|
||
verbatim, with the application left to Pouya or to counsel. That is now an
|
||
upgrade to the evidence rather than a gate on publication. **Step 5 is
|
||
unblocked.**
|
||
|
||
**The reason settlement counsel fails is the finding.** It did not fail question
|
||
1 and it did not fail question 2. It failed a prior question the test does not
|
||
ask: **is this a neutral's role at all?** Settlement counsel acts *for* a party.
|
||
Run mechanically, the two-question test would have passed it — negotiation on a
|
||
party's behalf is not obviously gated, and Pouya is competent to negotiate — and
|
||
it would have put a partisan role on a site whose central claim is neutrality.
|
||
|
||
So the prior question is: **is this a role in which the practice is partisan
|
||
between the parties to a dispute?** If it is, the answer is no before the test
|
||
starts.
|
||
|
||
**THAT IS THE RULE, AND IT IS STATED THIS WAY BECAUSE THE FIRST VERSION HAD AN
|
||
UNGATED EXCEPTION IN IT.** It read *"the offering test presumes the role is a
|
||
neutral's… The one exception in this table is the pre-dispute technical advisory
|
||
row, which is also not a neutral role."* `claims-auditor`: a rule and its ad-hoc
|
||
exception in the same paragraph, in the section written to prevent *"a category
|
||
that authorises everything by saying nothing"* — and the exception was
|
||
self-contradictory, because the *dispute-system design* row two lines above also
|
||
describes a non-neutral role (*"Consulting, no appointment, no neutrality
|
||
question"*). One of the two statements had to be wrong.
|
||
|
||
Restated as above, there is no exception: dispute-system design and pre-dispute
|
||
technical advisory both pass, because neither involves a party to be partisan
|
||
between — one advises an organisation about its future disputes, the other
|
||
precedes any dispute. Settlement counsel fails, because acting *for* a party in
|
||
a negotiation is partisanship between parties by definition. **The distinction is
|
||
the party, not the label.**
|
||
|
||
**Applied, 2026-08-27 — Q35 CLOSED.** `Energy, Grid & Regulatory`,
|
||
`Shareholder & Family Business`, and the other four labels **pass condition 1**
|
||
on Pouya's answer; condition 2 is each page's job at build step 5. `Med-Arb`
|
||
now has an Offerings row of its own and stays in the footer sitemap. Nothing in
|
||
the nav or footer is unrowed or ungated any more.
|
||
|
||
### Conduct undertakings — commitments made, as distinct from credentials and offerings
|
||
|
||
**Added 2026-08-29 on Pouya's ruling (Q54). A THIRD CLASS, and it is his:**
|
||
|
||
> "Add §4 rows for all six as conduct undertakings — a distinct class from both
|
||
> credentials and offerings. They are not facts about experience; they are
|
||
> commitments Pouya has now made, dated 2026-08-27, and they bind. Note in the
|
||
> row that any later softening is a change to a published commitment, not a
|
||
> copy edit."
|
||
|
||
**Why a third class rather than a row in one of the two above.** The Verified
|
||
table answers *is this claim about Pouya true?* The Offerings table answers *does
|
||
the practice offer this?* Neither question fits a commitment: an undertaking is
|
||
not true or false when it is made, and it is not a process the practice conducts.
|
||
It is a promise, and it becomes checkable only in the conduct that follows it.
|
||
Under **Q43** these are **service commitments** — the same class as Q27's
|
||
two-business-day response time — so the bar is that **he has said them**, not that
|
||
§4 can vouch for them. He has said them.
|
||
|
||
> **THE GATE, and it is one line.** An undertaking may be published only where
|
||
> **Pouya has made it in terms.** Not "would obviously agree to", not "follows
|
||
> from the process" — *said*. The three §4 gates for an offering do not apply and
|
||
> do not substitute: this class is the one where the register holds no view and
|
||
> the architect holds all of it.
|
||
|
||
> ⚠️ **ANY LATER SOFTENING IS A CHANGE TO A PUBLISHED COMMITMENT, NOT A COPY
|
||
> EDIT — Pouya's instruction, and it governs every row below.** This is the
|
||
> class's characteristic failure mode and it is silent: nothing in a build fails
|
||
> when a promise gets a little smaller, and the diff reads like tightening. The
|
||
> six strings live in **`CONDUCT_UNDERTAKINGS` in `src/data/site.ts`** and the
|
||
> pages render them, so the diff that would soften one is visible on one
|
||
> constant rather than distributed through three templates.
|
||
|
||
⚠️ **ON THE STAMP DATE, BECAUSE THE DATE IS THE WHOLE CONTENT OF A STAMP.** The
|
||
ruling says *"dated 2026-08-27"*. The rows below read **`[verified 2026-08-29 —
|
||
Pouya, Q54]`**, which is the date he actually ruled. This is not a quibble and it
|
||
is not the same call as the memberships row's two-day question: **the drafts did
|
||
not exist on 2026-08-27.** Q54 was raised by Claude Code on **2026-08-28** and
|
||
(d) and (e) shipped for one pass that same day before `claims-auditor` removed
|
||
them, so a commitment dated 2026-08-27 would predate the text of the commitment.
|
||
A stamp records when the assertion was made.
|
||
|
||
✅ **RATIFIED 2026-08-30 — 2026-08-29 stands.** Pouya: *"You're right that a
|
||
commitment cannot predate its own text. My 2026-08-27 was the date I ruled, not
|
||
the date the undertakings existed."* The ruling date and the stamp date are
|
||
different facts about a commitment, and the stamp is the second one. **Closed —
|
||
do not re-open it against the quoted ruling above.**
|
||
|
||
| Undertaking | Where it ships | Status |
|
||
|---|---|---|
|
||
| **(a) Med-arb — the switch.** *"The switch is agreed in writing before the mediation phase begins, or I do not take the appointment. I will not convert a mediation into an arbitration on the day because the room has run out of road."* | `/med-arb/` §What I undertake **and `/process/` §If it does not settle** (added 2026-08-30, build step 6 — it is the answer to the question that section exists to answer, and it is rendered from the constant, not retyped) | `[verified 2026-08-29 — Pouya, Q54]` |
|
||
| **(b) Med-arb — caucus material.** *"If a party tells me something in caucus they are not prepared for me to rely on as arbitrator, they say so at the time, and it does not enter the arbitral record."* | `/med-arb/` §What I undertake | `[verified 2026-08-29 — Pouya, Q54]` |
|
||
| **(c) Med-arb — the hard one.** *"If I cannot decide a remaining issue without relying on something said to me in confidence, I say so and step out of the arbitral phase rather than decide on it."* | `/med-arb/` §What I undertake | `[verified 2026-08-29 — Pouya, Q54]`. **SHIPS AS DRAFTED, and this row carries his reasoning because it is the only one that cost anything to make.** *"It is the strongest available answer to the med-arb objection, and cheaper in practice than it sounds — the arbitral phase runs on the evidentiary record, not the caucus, so the case where a neutral genuinely cannot decide without confidential material is uncommon. `/med-arb/` was raising the hardest question about med-arb and answering it only at the level of process design."* Q54 warned that *"a neutral who would not honour it must not publish it"*; he published it. **This is the row where softening would be worst and least visible** — a version that says he "may" step out, or that he "considers" stepping out, is a different commitment wearing the same words |
|
||
| **(d) Mediation — caucus confidentiality.** *"What a party tells me in caucus stays in that caucus until they tell me I may use it, and I do not carry a number across the hall that I was not given to carry."* | `/mediation/` §Confidentiality, **`/process/` §Confidentiality, and `/for-parties/` §Questions** — the last both visibly and inside that page's `FAQPage` node (all added 2026-08-30, build step 6). **Three surfaces.** The row recorded two for one pass; `adversarial-reviewer` found the third, and an incomplete "where it ships" on the one class Pouya flagged as failing *silently* is this column doing the opposite of its job | `[verified 2026-08-29 — Pouya, Q54]`. Shipped for one pass at step 4 and removed by `claims-auditor` — correctly: the gate had been applied to `/med-arb/` in the same change set and not one file over. It is here now because it is answered, not because the gate relaxed |
|
||
| **(e) Arbitration — procedure.** *"I will not run a process whose shape nobody agreed to in advance."* | `/arbitration/` §Rules | `[verified 2026-08-29 — Pouya, Q54]`. Same one-pass history as (d). **It REPLACED a third-person sentence rather than joining it** — the page already ended that paragraph *"What does not is a process whose shape nobody agreed to in advance"*, the observation form of the same proposition, and keeping both would have set the undertaking beside its own paraphrase |
|
||
| **(f) Arbitration — the award date.** *"The date the award is due is fixed in the first procedural order rather than left open."* | `/arbitration/` §Awards | `[verified 2026-08-29 — Pouya, Q54]`. Same replacement as (e), of *"The date an award is due belongs in the first procedural order"*. **The sentence after it is unchanged and is doing different work:** *"No number is published here"* is §4 Forbidden's bar on a time-to-award statistic, which is not what this undertaking is |
|
||
|
||
**What these six buy, stated once so it is not re-argued.** Q54's finding was that
|
||
all three process pages answered the fairness question *at the level of process
|
||
design* — what an agreement has to settle, what a rule set does and does not fix —
|
||
and that this is the half a reader can get from any competent page on med-arb.
|
||
**What none of them carried is what the neutral will do**, which is the half a
|
||
party actually weighs when choosing one. That gap was not an oversight: it was the
|
||
register refusing to invent a commitment. The gap closes because he made them, and
|
||
that is the only way it could have closed.
|
||
|
||
### Forbidden — must not appear on the site
|
||
|
||
**Scope, clarified 2026-08-26.** This table governs **published pages** — anything
|
||
a visitor to `adr.smlcompany.ca` can read, JSON-LD included. It is not a word
|
||
filter over the repository's own documentation.
|
||
|
||
**Internal docs are bound by a related rule:** they must not assert as fact
|
||
anything this register has not verified. Reasoning built on an unverified premise
|
||
propagates into copy. Licensure is the live example — **the Verified table above
|
||
does not establish licence status either way**; its two licensure rows are
|
||
verified *directives not to publish*, not a verified status. So no file in this
|
||
repo may call Pouya "licensed", or soften it to "a legal professional", internal
|
||
or not. State the *reason* for a rule rather than a credential the register
|
||
cannot vouch for.
|
||
|
||
| Never publish | Why |
|
||
|---|---|
|
||
| Any count of matters closed, hours mediated, or years in ADR practice | Practice is new. Small true numbers do not persuade a sophisticated GC and invite scrutiny. Save for one-to-one appointment proposals where context travels with the figure. `[verified 2026-08-25 — content brief, "Rule of thumb on numbers"]` |
|
||
| Settlement rates, resolution percentages, median time to award | No underlying data exists |
|
||
| Aggregate value resolved; any dollar figure attached to past matters | No underlying data exists |
|
||
| Named or describable past matters | Confidentiality, and none are publishable |
|
||
| Testimonials, endorsements, quotes from counterparties | None exist. The prior site's testimonial was fabricated |
|
||
| "Since 2009", "sixteen years", London / New York offices, Co. № 07452218 | Artefacts of the placeholder template. All false |
|
||
| The name "S. M. Lawrence" | Fictitious founder from the template |
|
||
| Guarantees of outcome, or superlatives ("best", "leading", "top-rated") | Unverifiable as written, and they read as insecure to the audience this site is for. Marketing rules for regulated professions also treat them as suspect. *(Reason restated 2026-08-26: this row previously read "LSO marketing rules", which asserts the regulatory status the row above marks NOT ESTABLISHED. It was the last surviving instance, flagged in entries (o) and (q) and answered in Q26 as already fixed — it was not. **Restated by Claude Code; the rule itself is unchanged and the restatement needs Pouya's ratification.**)* |
|
||
| The word **"lawyer"** used of Pouya; "called to the bar"; "licensed"; "my law practice"; "my litigation practice"; any post-nominal implying a licence | D13. The site asserts the JD and nothing further |
|
||
| Any phrasing that *implies* entitlement to practise law without saying so — "acts for clients", "represents parties", "my clients", "legal advice" | Same rule. Implication is the risk, not just the word. Describe the role factually instead: *Director of Firm Operations at a Toronto litigation and ADR boutique*, and the matter types worked on |
|
||
| **Q.Arb described as commenced, in progress, a pathway, or not yet held** | **It is HELD** `[verified 2026-08-29 — Pouya]`. Publish `Q.Arb (ADRIC / ADRIO)`. **The acquisition date is recorded in §4 and is NOT published** — and it is itself contradicted on the record and deliberately left that way (Q55, closed unresolved 2026-08-30). `npm run check:claims` `q-arb-as-a-stage` enforces the stage words and a date near the designation, on `dist/` |
|
||
| ~~Q.Arb described as held, imminent, or "nearly complete"~~ | **STRUCK 2026-08-29 — Q.ARB IS HELD.** This row was correct from 2026-08-26 to 2026-08-29 and is now exactly backwards. **What replaces it is the opposite bar:** Q.Arb described as *commenced*, *in progress*, *a pathway*, or *not yet held* — see the Verified row. The publishable form is `Q.Arb (ADRIC / ADRIO)`; the acquisition date is recorded in §4 and is **not** published |
|
||
|
||
### The substitution principle
|
||
|
||
Wherever the design wants a "how much / how many" statistic, substitute a
|
||
**longer-arc credential** — something already substantial and true at launch that
|
||
does not grow by closing files. The approved stat set is `Q.Med` /
|
||
`JD + ML` / `EN · FA`, with `Q.Arb` as a fourth slot where one exists.
|
||
`[verified 2026-08-25 — content brief]`
|
||
|
||
⚠️ **THE FOURTH SLOT IS UNCHANGED IN PLACEMENT AND CHANGED IN CONTENT (2026-08-29).**
|
||
It carried `Q.Arb — commenced August 2026`, a **stage**; it now carries `Q.Arb`, a
|
||
**designation**, on the same footing as `Q.Med`. The slot was never a disclaimer —
|
||
it existed because the substitution principle wanted a fourth credential — so
|
||
nothing about its placement follows from Q.Arb becoming held.
|
||
|
||
## 5. Audience model
|
||
|
||
All four tiers matter, but they are served by different surfaces rather than by
|
||
diluting every page into a compromise. `[verified 2026-08-25 — decision D6]`
|
||
|
||
| Tier | Reads | Wants | Primary surface |
|
||
|---|---|---|---|
|
||
| In-house / general counsel | Home, practice pages | Credentials, subject-matter fluency, procedure, predictable cost | Home + `/practice/*` |
|
||
| Referring lawyers and litigation boutiques | Practice pages, fees, process | Availability, rules familiarity, rate card, confidence you won't embarrass them | `/fees/`, `/process/`, `/mediation/` |
|
||
| Appointing bodies and ADR institutions | About, credentials | A verifiable credential record and evidence of depth | `/about/` |
|
||
| Self-represented parties and SMEs | Plain-language layer | What mediation actually is, what it costs, what happens | `/for-parties/` |
|
||
|
||
Realistically, **referring counsel are the largest source of early
|
||
appointments**. Where two audiences conflict on a page, resolve toward counsel.
|
||
`[assumed]`
|
||
|
||
## 6. Architecture
|
||
|
||
Full sitemap, URL map, and per-page content outline: **`docs/01-architecture.md`**.
|
||
|
||
Summary: ~20 static pages. Home; About; three process pages (Mediation,
|
||
Arbitration, Med-Arb); six practice-area pages; Process; Fees; For Parties;
|
||
Insights index and articles; Contact; Privacy; Terms.
|
||
|
||
**Deliberate omission:** there is no Indigenous engagement / IBA practice page at
|
||
launch, though the strategy brief rates that niche as strategically the most
|
||
valuable. Publishing a practice page for it before the multi-year relationship
|
||
work described in brief §III.4 has been done would read as overreach to exactly
|
||
the audience it targets. Revisit at month 12–18. `[verified 2026-08-25 — decision recorded here, not yet discussed with Pouya]`
|
||
|
||
## 7. Environment and stack
|
||
|
||
| Thing | Value |
|
||
|---|---|
|
||
| Framework | **Astro 7.2.9**, `output: 'static'` `[verified 2026-08-27 — npm view astro version, D1 as amended]`. `@astrojs/mdx` 7.0.8, `@astrojs/sitemap` 3.7.3, `sharp` 0.35.4 — all three at `latest`. Bumped from 7.2.7 at the step 1 → step 2 phase boundary under R11: 7.2.8 published 2026-08-26 and 7.2.9 on 2026-08-27, i.e. **two patches appeared inside 48 hours**, which is the argument for checking at boundaries rather than on failure. `engines` unchanged at `node >=22.12.0`, `npm >=9.6.5` `[verified 2026-08-27 — npm view astro@7.2.9 engines]` |
|
||
| **TypeScript — HELD at 6.x, and the hold is a peer constraint rather than a preference** | Pinned `^6.0.3`; `npm view typescript version` returns **7.0.2** `[verified 2026-08-31 — R11, step 6 → 7 phase boundary; 13 of 14 pins current, this the only hold]`. **The removal trigger was re-checked rather than recalled:** `npm view @astrojs/check@0.9.10 peerDependencies` still returns `{ typescript: '^5.0.0 || ^6.0.0' }`, so the hold stands. ⚠️ **AND THERE ARE TWO GATES, NOT ONE — corrected 2026-08-31, and this row named only the first for two days.** `npm view typescript-eslint peerDependencies` returns `{ typescript: '>=4.8.4 <6.1.0' }`, which is **tighter**: widening `@astrojs/check` alone would not lift the hold, so the trigger as recorded was unreachable. **A second consequence, live:** the pin is a caret, so if a 6.1.x ever ships, a plain `npm install` moves the tree into a peer-range breach with nothing in the repo saying so. Nothing is breached today — `npm ls typescript` resolves **6.0.3**, which is the highest stable 6.x on the registry. Found by running R11's own check rather than reading the row. **One major behind, which is the exact shape D1 was amended over — so the reason is recorded rather than the hold being silent.** `@astrojs/check@0.9.10` declares `peerDependencies: { typescript: '^5.0.0 \|\| ^6.0.0' }` `[verified 2026-08-29 — npm view @astrojs/check@0.9.10 peerDependencies]`, and `npm run check` is `astro check`, which is the type gate the deploy path runs before it builds. **Removal trigger: `@astrojs/check` AND `typescript-eslint` both widen to include 7** — either alone is not enough. Re-check at every phase boundary under R11 — this is a hold on a dependency's schedule, not on a judgement, so it lifts without a decision |
|
||
| Lint toolchain | ESLint **10.9.1**, `@eslint/js` 10.0.1, `globals` 17.11.0, `eslint-plugin-astro` **3.1.0**, `eslint-plugin-jsx-a11y` 6.10.2, `typescript-eslint` 8.68.0, `typescript` **6.0.3** — **every pin at the registry's `latest` except `typescript`** `[verified 2026-08-30 — npm view, all 14 pins, R11 at the step 5 → 6 boundary; thirteen current, one held]`. `@eslint/js` and `globals` are declared explicitly; before 2026-08-26 `eslint.config.js` imported them and they resolved only by npm hoisting accident. **Accessibility linting is on** — `flat/jsx-a11y-recommended`, 36 rules `[verified 2026-08-26 — 7 rules fired on a deliberately inaccessible .astro file]`. `eslint-plugin-jsx-a11y@6.10.2` declares a stale `eslint ^3..^9` peer range; a one-line `overrides` entry in `package.json` resolves it. ⚠️ **`eslint-plugin-astro@3.1.0` declares `node ^22.22.3 \|\| ^24.16.0 \|\| >=26.3.0`**, which excludes Pouya's Node 25.6.0 — `npm install` prints EBADENGINE there. Dev-time only, and `nvm use` (Node 22 LTS, per `.nvmrc`) clears it. **`typescript` — the hold, and it was too wide by a whole major until 2026-08-27.** `latest` is **7.0.2** and it is unusable here: `typescript-eslint@8.68.0` peers `typescript >=4.8.4 <6.1.0` and `@astrojs/check@0.9.10` peers `^5.0.0 \|\| ^6.0.0`, so taking 7 breaks **both** the linter and `astro check` `[verified 2026-08-27 — npm view <pkg> peerDependencies]`. **But this row previously read "held at 5.x", and 6.0.3 is a stable release both peers accept** — so the pin sat a full major behind for no reason the record could name, in a row whose whole job is to name the reason. Now at **6.0.3**, the newest version compatible with both peers; `npx tsc --version` reports 6.0.3 and the full gate is green `[verified 2026-08-27]`. The 6.x listing is mostly `-dev` and `-beta` tags; **6.0.2 and 6.0.3 are the only stable 6.x releases**, which is why `npm view typescript version` (7.0.2) is not the number to pin against here. Re-check at the next phase boundary: the hold ends when `typescript-eslint` widens its peer range past `<6.1.0` |
|
||
| Lighthouse CI | **Not installed, and that is now stated wherever the check is claimed.** `@lhci/cli` was the sole source of all 10 `npm audit` findings (7 high, via `lighthouse → puppeteer-core → extract-zip`), 0.15.1 is `latest` so there was no clean upgrade, and it cannot run at all — no pages, no `lighthouserc`. Removed 2026-08-26; **`npm audit` now reports 0 vulnerabilities** `[verified 2026-08-26 — npm audit]`. Removing it left a **documented control that no longer exists** — `docs/04`, `CLAUDE.md` and `/build` Phase 5 all required a run that had silently become impossible, which is Q22's defect in a different costume. Fixed 2026-08-26: the unavailability is stated in `docs/04-seo-spec.md` (budget table, the callout under Performance, and the post-launch checklist), `CLAUDE.md` (performance budget and the definition of done), `.claude/commands/build.md` Phase 5, `docs/06-deployment.md` (PR checks and the cutover checklist), and `.claude/agents/adversarial-reviewer.md` §4 — which is also told **not** to raise the absence as a finding. **Re-add at build step 7** with a pin verified that day and a check for a patched release; do not assume 0.15.1 is still the ceiling (R11) |
|
||
| Node | **22 LTS line**, `.nvmrc` holds `22` so it tracks the latest 22.x rather than freezing at a floor. `package.json` declares **`engines.node` = `^22.13.0 || >=24`** (verbatim — it excludes Node 23, an EOL odd line, which a flat `>=22.13.0` would have admitted) and **`engines.npm >=9.6.5`** — the intersection of every dependency's own floor: Astro 7 and `@astrojs/mdx` 7 need `>=22.12.0`, ESLint 10 needs `^20.19.0 \|\| ^22.13.0 \|\| >=24` `[verified 2026-08-26 — npm view astro@7.2.7 engines, npm view eslint@10.9.1 engines]`. **Pouya's machine reports Node v25.6.0** `[verified 2026-08-26 — node -v]`, an odd-numbered non-LTS line; it satisfies the floor, but `nvm use` keeps local and CI on the same runtime |
|
||
| Styling | Plain CSS with custom properties. No Tailwind, no CSS-in-JS `[verified 2026-08-25]` |
|
||
| Known HTML-conformance error | **Astro's `<Picture>` + `densities` emits a duplicate-density `srcset`, and it is upstream of this repo.** The pattern is `url, url 1x, url 2x, url 3x` — the first candidate carries no descriptor and therefore defaults to `1x`, so two candidates claim the same density, which puts the document in error per the HTML spec. **Behaviour is benign** and selection is correct at DPR 1, 2 and 3 `[verified 2026-08-27 — measured in headless Chrome]`. It affects **4 of the 12 `srcset` attributes on `/`** — the `<source>` elements of every `<Picture>` using `densities`, i.e. the three `InfinityMark` instances. The hero portrait uses `widths` + `sizes` and emits clean `w` descriptors. **Consequence for the record: do not claim "HTML validator clean" for any page carrying a mark**, and do not re-open this as a defect in this repo — it is `<Picture>`'s output, not ours. It would go if `InfinityMark` moved to `widths` + `sizes`, which would mean every call site supplying a `sizes` string for a fixed-size decorative image; not worth it for a conformance nit. Recorded on `adversarial-reviewer`'s request, 2026-08-27; first raised as step-1 review finding #8 |
|
||
| Deploy ordering | **`/` must not be deployed before `/about/` exists**, and the reason is machine-readable rather than visible. The home page's `Person` JSON-LD sets `url` and `@id` to `https://adr.smlcompany.ca/about/`, which is a **404 until build step 3**. The `@id` resolves inside the page's own `@graph`, so `provider` is fine; `Person.url` is the exposure, and it is the one part of the page a crawler acts on rather than renders. Every internal link is in the same position, which is inherent to a nineteen-page build order — **but D11 already governs this: "Build everything, one clean cutover", and nothing deploys until step 11.** Recorded because `npm run deploy` is a single command from this machine and the guard is a decision rather than a mechanism. Raised by `adversarial-reviewer`, 2026-08-27 |
|
||
| Client JS | **Zero. Not "minimal" — none.** `dist/index.html` contains **1** `<script>` tag and it is `type="application/ld+json"`; non-JSON-LD scripts **0**, and `dist/_astro/` contains no JS bundle `[verified 2026-08-27 — built, counted, and re-confirmed with script execution disabled at the CDP level: 444 DOM nodes, 6,578 characters of visible text, 5,665 px of content, i.e. the identical page]`. *(This row cited `dist/type-scale/index.html` until 2026-08-27; that page was the step-1 proof sheet and step 2 deleted it, so the row named a file that no longer exists. `/` is now the page to count.)* The reveal was an inline `IntersectionObserver` in `<head>` until 2026-08-26; it was removed because `docs/05-backend-spec.md` specifies `script-src 'self'` with no `unsafe-inline`, so the only script on the site was the one thing the site's own CSP would refuse to run. `animation-timeline: view()` in `global.css` replaces it. **Both scroll-driven animations must use `animation-*` LONGHANDS** — Lightning CSS folds the `animation` shorthand together with `animation-timeline` into an invalid declaration and discards it, which works in `npm run dev` and is dead in `npm run build`. It happened twice in one session: once in the header condense, then again in the fix written for it. `/build` Phase 5 now greps `dist` for it. Islands remain available where a feature genuinely cannot be CSS or progressive HTML — none has been needed |
|
||
| Content | Astro **Content Layer API** collections, MDX for Insights. Config lives at **`src/content.config.ts`**; collections declare a `loader`, not a `type`; `z` imports from `astro/zod`. **Astro 5 introduced** the Content Layer API and this location; **Astro 6 removed** the legacy `src/content/config.ts` fallback — moving the file back now raises `LegacyContentConfigError` `[verified 2026-08-26 — reproduced by moving it back]` |
|
||
| Fonts | Instrument Serif + Geist + Geist Mono, **self-hosted**, `font-display: swap`. **Files present as of 2026-08-26** — six `.woff2` cuts, **123,804 bytes** total, in `public/fonts/` (`du -sh` says 136K; that is disk blocks, not transfer, and this row is read in a performance context); provenance, licences (all SIL OFL 1.1) and the reason they are committed rather than pulled at build are in `docs/reference/fonts-provenance.md`. Before this they were *declared* in `global.css` and **absent from disk**, so every face silently fell back to Georgia and the system sans `[verified 2026-08-26 — built and listed]`. Instrument Serif 400 latin (21,032 B) and Geist latin (29,400 B) are preloaded in `BaseLayout.astro` — about 50 kB at first paint; nothing else is. Every font URL carries **`?v=1`**, because the deploy script serves `/fonts/*` `immutable` for a year: replacing a cut means bumping that query in `global.css` and in the preload together `[verified 2026-08-26 — byte counts]` |
|
||
| AWS account | `327082975128` `[verified 2026-08-26 — inventory]` |
|
||
| Region | **`ca-central-1`** throughout — hosting, Lambda, DynamoDB `[verified 2026-08-26]` |
|
||
| S3 bucket | **`adr-smlcompany-site`** — versioning **Enabled**, so rollback works `[verified 2026-08-26]` |
|
||
| CloudFront | **`E1OK7G98KNKUTA`**, alias `adr.smlcompany.ca`, origin `adr-smlcompany-site.s3.ca-central-1.amazonaws.com`, Deployed `[verified 2026-08-26]` |
|
||
| ACM certificate | `arn:aws:acm:us-east-1:327082975128:certificate/2b6d5bdf-6790-430c-9b82-c00ab66e6d87` — ISSUED `[verified 2026-08-26]` |
|
||
| Intake API | `adr-intake-api`, HTTP API `4tl0m5igkj`, endpoint `https://4tl0m5igkj.execute-api.ca-central-1.amazonaws.com` `[verified 2026-08-26]` |
|
||
| Intake Lambda | `adr-intake-handler`, `nodejs24.x` `[verified 2026-08-26]` |
|
||
| Intake table | `adr-intake-submissions` (DynamoDB, ca-central-1) `[verified 2026-08-26]` |
|
||
| SES identities | Domain `smlcompany.ca` **verified for sending** `[verified 2026-08-26]`; addresses `info@`, `intake@`, `adr@` |
|
||
| SES account | **Production access GRANTED** — out of the sandbox in `ca-central-1`, confirmed by AWS in writing and effective immediately `[verified 2026-08-26 — Q19 closed]`. Mail now reaches unverified recipients, so the inquirer confirmation in D18 works |
|
||
| Mail hosting | **Google Workspace** — MX `1 smtp.google.com`; `google._domainkey` present, so Google DKIM is configured `[verified 2026-08-26 — DNS query]` |
|
||
| **SPF** | **PRESENT.** `v=spf1 include:_spf.google.com include:amazonses.com ~all` on `@`, added by Pouya and independently verified `[verified 2026-08-26 — DNS query, Q20]` |
|
||
| **DMARC** | **PRESENT.** `v=DMARC1; p=none; rua=mailto:info@smlcompany.ca; fo=1` on `_dmarc`, added by Pouya and independently verified `[verified 2026-08-26 — DNS query, Q20]`. Still at `p=none`; tighten to `quarantine` only after reports come back clean |
|
||
| Required DNS (Namecheap) | TXT `@` → `v=spf1 include:_spf.google.com include:amazonses.com ~all` · TXT `_dmarc` → `v=DMARC1; p=none; rua=mailto:info@smlcompany.ca; fo=1` `[assumed]` — start at `p=none`, tighten after monitoring |
|
||
| SES DKIM — **the set that actually resolves** | `f5puwearz5ek47aiuoskk57ya6ir66ju`, `jdue2r22cxrk27laxlgnjcpby2fq4vxu`, `kznn3cklvwh4gs342rtf5euqymlger53` — all three answer NOERROR at `<token>._domainkey.smlcompany.ca` `[verified 2026-08-26 — DNS]` |
|
||
| SES DKIM — **the set that is BROKEN** | `3zsnvsjg3ddi6hjyndjy6jgjoitvhydl`, `jejgp7na3wdpprsanamct4uxxgw2tyqw`, `xpiwyftpodmgpnzfof3ee7t7fzmlmhnh` — listed in the SES console, present in Namecheap, but **NXDOMAIN**. They were entered with the full name in Namecheap's Host field, so the zone doubled the domain: `<token>._domainkey.smlcompany.ca.smlcompany.ca` resolves, the correct name does not `[verified 2026-08-26 — DNS]` |
|
||
| SES identity — **`ca-central-1` (the one that matters)** | `Verified: true`, `DkimStatus: SUCCESS`, tokens `kznn…` / `jdue…` / `f5pu…` — the set that resolves. **Healthy. Change nothing.** **RE-VERIFIED BY DNS 2026-08-29** on the same day the `us-east-1` identity threw its health event, which is the check that made "no impact" a result rather than an assumption: all three live DKIM records answer **NOERROR**, and SPF and DMARC are present `[verified 2026-08-29 — DNS, Pouya]` |
|
||
| SES identity — `us-east-1` | **BEING DELETED — Pouya's instruction 2026-08-29, and the reason is a monitoring principle rather than a cleanup.** It was `Verified: false`, `DkimStatus: PENDING`, tokens `3zsn…` / `jejgp…` / `xpiwy…` — the doubled-domain set — a stray identity in a region this project does not use `[verified 2026-08-26]`. On **2026-08-29** it produced an AWS Health event, `AWS_SES_DKIM_PENDING_TO_FAILED`, which is the **expected** outcome of DKIM CNAMEs that never resolved. **That is its third false-alarm signal:** (1) a pending identity on the console dashboard, (2) a near-miss on requesting production access in the wrong region — the trap the row below records — and (3) this health event. Pouya's reason, kept because it generalises past SES: *"A monitoring surface that reports a failure you do not have trains you to discount the ones you do."* **No impact on mail.** Deletion removes the identity, not the records — the three live DKIM CNAMEs belong to the `ca-central-1` identity and are untouched by it |
|
||
| ⚠️ **SES sandbox is per-region** | Recorded as a standing caution, not an open task — production access **was** granted in `ca-central-1` (Q19). The trap: the AWS console defaults to `us-east-1`, and granting access there leaves `ca-central-1` in the sandbox with the intake email still failing. Applies again to any future SES request `[verified 2026-08-26]` |
|
||
| SES custom MAIL FROM | **Not configured** — SES reports "No MAIL FROM records found". This is why SES's SPF is unaligned and DMARC rests on DKIM. Optional future improvement, not required `[verified 2026-08-26]` |
|
||
| SES monitoring — SNS topic | **`ses-alerts`**, `ca-central-1`. Email subscription to `info@smlcompany.ca` is **PENDING CONFIRMATION, not confirmed** `[verified 2026-08-26]`. **Until the subscription is confirmed the alarms below fire into nothing** — confirm the link in the subscription email |
|
||
| SES monitoring — alarms | **`SES-BounceRate-High`** (bounce rate ≥ `0.03`) and **`SES-ComplaintRate-High`** (complaint rate ≥ `0.001`), both `ca-central-1`, `treat-missing-data: notBreaching` `[verified 2026-08-26]` |
|
||
| SES bounce/complaint handling | **Email feedback forwarding** — SES's default, on unless disabled. **Deliberately not an SNS feedback topic:** at under 100 messages a month there is nothing to consume a programmatic feed. Revisit when code needs to act on a bounce `[verified 2026-08-26]` |
|
||
| **DMARC alignment** | SES satisfies DMARC via **DKIM**, not SPF — without a custom MAIL FROM domain its envelope sender is at `amazonses.com` and is unaligned. The SPF record's real job is authenticating **Google Workspace** mail `[verified 2026-08-26]` |
|
||
| **Do not delete** | Two ACM validation CNAMEs → `jkddzztszm.acm-validations.aws`. They renew the `adr.smlcompany.ca` certificate; deleting them breaks HTTPS silently at the next renewal `[verified 2026-08-26]` |
|
||
| Root domain | `@` carries a Namecheap **URL Redirect Record** to `sml-coming-soon.ca`. TXT records coexist with it — adding SPF does not disturb it `[verified 2026-08-26]` |
|
||
| DNS confirmed | `adr.smlcompany.ca` CNAME → `d26v23dhgsp2ta.cloudfront.net` `[verified 2026-08-26]` |
|
||
| TLS | ACM certificate `[verified 2026-08-25 — AWS-Hosting-Guide.md]` |
|
||
| DNS | **Namecheap**, not Route 53 `[verified 2026-08-25 — AWS-Hosting-Guide.md]` |
|
||
| Intake backend | API Gateway (HTTP API) → Lambda → DynamoDB, notifications via SES `[verified 2026-08-25 — AWS-Hosting-Guide.md]` |
|
||
| Repository | **`adr-sml`**, self-hosted **Gitea**. Local clone at `/Users/pouya/Dev/Websites/adr-sml` `[verified 2026-08-26]` |
|
||
| CI/CD | **Gitea Actions**, `.gitea/workflows/deploy.yml`. Instance **git.larsnolden.com, version 1.27.2** `[verified 2026-08-26 — /api/v1/version]` — well above the ~1.21 floor for the `vars` context. The GitHub OIDC workflow is kept as `docs/reference/github-actions-oidc.yml.example`, outside `.github/workflows/` so Gitea cannot fall back to it. **No OIDC available** — Gitea is not an AWS OIDC provider |
|
||
| **Deploy credential — PROVISIONED** | IAM user **`adr-sml-deploy`**, created **2026-08-26T15:45:18Z**, `arn:aws:iam::327082975128:user/adr-sml-deploy` `[verified 2026-08-28]`. **No managed policies, no group memberships.** One inline policy, `adr-sml-deploy-minimal`: `s3:ListBucket` on the site bucket, `s3:PutObject` + `s3:DeleteObject` on `bucket/*`, `cloudfront:CreateInvalidation` on the distribution this section records. **One active access key, created 2026-08-26, NEVER USED** — `AccessKeyLastUsed` returns `ServiceName: "N/A"` / `Region: "N/A"` with no `LastUsedDate` key at all, because deploys still run locally. **Verified by execution, not by reading** — `iam simulate-principal-policy`, **nine** checks: `allowed` for the four intended actions (`s3:PutObject`, `s3:DeleteObject`, `s3:ListBucket`, `cloudfront:CreateInvalidation`); `implicitDeny` for the five that matter more — `s3:ListBucket` and `s3:GetObject` on the client-database backup bucket, `s3:DeleteBucket` on its own bucket, `s3:PutObject` on `meshkinilaw.ca`, and `iam:CreateUser` on `*`. **The resource side is checked too:** `get-bucket-policy` on the backup bucket exits **254** with `NoSuchBucketPolicy`, so no resource-based grant exists and IAM is the only path in — and the same call against the *site* bucket exits 0 with a real CloudFront OAC policy, which is what makes the first result an absence rather than a broken command. **✅ EVIDENCE IS IN THE REPOSITORY — R14 SATISFIED. `docs/reference/deploy-credential-verification.md`**, eighteen read-only calls, each with the command that produced it, the access key ID redacted; re-run 2026-08-28 rather than transcribed, and `adversarial-reviewer` independently reproduced every value including the `MatchedStatements` positions. Q52 closed. ⚠️ **GITEA ACTIONS SECRETS: `UNSET`** `[verified 2026-08-26]` — no access key has been placed in a repository secret on `git.larsnolden.com`, so the key exists in IAM and **nowhere on the jointly-administered instance**. That is a different fact from the key being unused: a key can sit on shared infrastructure without ever authenticating. **Rotation: §12 R17 carries the date and the procedure** — this row deliberately does not restate it |
|
||
| **How deploys actually happen today** | **Locally, via `npm run deploy`** (`scripts/deploy-local.sh`) — same guard, same three sync passes, same cache headers, same invalidation as the workflow. Gitea Actions needs `[actions] ENABLED` in `app.ini` and a registered `act_runner`, both of which need the instance's second administrator (Q23). At this scale the pipeline changes only **how a deploy is triggered**, not what it does `[verified 2026-08-26]` |
|
||
| **Interim auth — do not repeat in CI** | Pouya has been authenticating as **`user/pouya`**, the broadly-permissioned personal user the Q10 inventory captured. Acceptable for interactive work at a keyboard; **never** as a CI credential — see §10 `[verified 2026-08-26]` |
|
||
| Analytics | **Plausible** — cookieless, no personal data, no consent banner, **all data held in the EU** `[verified 2026-08-26 — D15 as amended, Q31]`. `src/data/site.ts` sets `ANALYTICS.provider`. Not yet installed: no script is on any page, and `/legal/privacy/` (step 10) is where the processor gets named |
|
||
|
||
## 8. Design system
|
||
|
||
Full token set, type scale, motion rules, and contrast results:
|
||
**`docs/02-design-system.md`**.
|
||
|
||
Palette and infinity mark carry over unchanged. Execution is modernized:
|
||
fluid type scale, self-hosted fonts, an 8 px spacing scale, motion gated behind
|
||
`prefers-reduced-motion`, and one hard accessibility constraint discovered by
|
||
measurement:
|
||
|
||
> **Gold `#c9a876` on cream `#faf7f2` measures 2.10:1 contrast.** That fails WCAG
|
||
> AA for body text (4.5:1) and for large text (3:1). Gold is a decorative and
|
||
> on-dark colour only. On maroon it measures 5.84:1 and on ink 8.00:1, both of
|
||
> which pass. `[verified 2026-08-25 — computed]`
|
||
|
||
## 9. Open questions — blocking
|
||
|
||
Nothing below can be invented. Each needs an answer from Pouya.
|
||
|
||
| # | Question | Blocks |
|
||
|---|---|---|
|
||
| **Q59** | **WHERE DOES THE OVERTIME HOUR START?** `docs/07`'s card carries *"Overtime, per hour — $500"* and has never said what it is overtime **to**. Q58's ruling settled the two allowances (up to 3 h / 6 h of session, up to 2 h / 3 h of preparation) and did not reach this, and Q15–Q17's answer records the rate with no trigger either. **The two candidates are the session cap (3 h / 6 h) and the billed envelope (5 h / 9 h), and this repository must not pick one** — it is a fee term, and `CLAUDE.md`'s rule for a fact we do not have is a question, not an inference. A first pass at `docs/07`'s Q58 note asserted the session cap as applied fact; `adversarial-reviewer` struck it in the same change set that wrote it. ⚠️ **AND THE ANSWER EXPOSES SOMETHING IN D14's FIGURES THAT IS WORTH SEEING BEFORE `/fees/` PUBLISHES THEM.** Under the session-cap trigger the half-day route costs `2000 + 500 × max(0, n − 3)` and the full-day route is **flat $4,000 until hour 6** — so **booking a half day and paying overtime is cheaper at EVERY length: by $2,000 at 3 h, $1,500 at 4 h, $1,000 at 5 h, and $500 from 6 h on. The full-day rate is never the cheaper choice.** The cause is the relationship between two of D14's own numbers rather than the trigger — the half-to-full step is $2,000 and three hours of overtime is $1,500 — and the envelope trigger trades bands rather than fixing it (worse at 6 h, closing to zero from 9 h). ⚠️ *This row first stated the spread as a flat $500 and generalised the full-day route as `500n + 1000` for all `n ≥ 3`, which is only valid from hour 6. The real spread is up to FOUR TIMES larger and is largest at 3–5 h, the band a half-day booking actually overruns into — so the wrong figure understated exactly the thing this row exists to escalate. Corrected 2026-08-31; found by `adversarial-reviewer` on round 2 of the change set that wrote it.* The table is in `docs/07` §The confirmed rate card and, for the rate decision, §Recorded dissent. **What is needed:** one line on where the hour starts, and a decision on whether the half/full step is a choice or an oversight (R5's 12-month review is the other place that belongs). Raised by `adversarial-reviewer`, 2026-08-31 | **`/for-parties/` NOW, and the overtime line on `/fees/` at step 9.** That page states an unambiguous session cap, so an overtime RATE printed on it defines the trigger **by adjacency** — there is no other quantity for the charge to attach to, and the answer travels alone into the `FAQPage` node. The rate is therefore off that page until this is answered; it names the charge without its rate or its trigger. `/mediation/` says only that overtime is on the rate card |
|
||
| ~~Q58~~ | **RULED 2026-08-31 — `hours` IS THE SESSION, AND THE AMBIGUITY WAS IN `docs/07` RATHER THAN IN ANY COPY. Pouya owned it in terms:** *"the ambiguity is mine… My `docs/07` wording said "up to 3.5 h, including 2 h preparation", which is genuinely unclear: 3.5 was meant as the TOTAL time committed, of which 2 is preparation — leaving 1.5 hours in the room. Your arithmetic caught it: if prep sat inside, 3.5 and 7 wouldn't be exactly 2×, because preparation doesn't scale with session length. The intended reading is the market's, and my wording obscured it."* **THE CORRECTED CARD, in his words:** *"Half day — up to 3 hours of session. Fee includes up to 2 hours of preparation. $2,000. Full day — up to 6 hours of session. Fee includes up to 3 hours of preparation. $4,000."* His reason for 3 and 6: *"the market convention — Patey and Zuber both publish "all or part of 3 hours" and "all or part of 6 hours", and those were the comparables the rate was set against. Selling 1.5 hours of room time as a half day would be an outlier nobody would recognise."* ⚠️ **ONE PROVENANCE NOTE, and it is R14's rule rather than a doubt about the ruling:** `docs/07`'s committed extract records Patey and Zuber at **3 h** and **6 h** but **does not carry the phrase "all or part of"** — so `docs/07` cites the hours, not the phrase, and the phrase is not attributed to them anywhere in the repository. The hours corroborate the ruling on their own, and ADR Chambers' roster rate in the same table is the clearest corroboration of the *shape*: *"one half hour of preparation time per party **and** up to three hours of mediation"* — preparation counted separately from a three-hour session. **APPLIED:** `docs/07`'s two card rows and its §All parameters confirmed (which prescribed the flat *"including 2 hours"*, the form `/for-parties/` then shipped); `FEES.mediation.*.hours` 3.5 → 3 and 7 → 6 with the semantics in the constant's doc comment; `/for-parties/` now states the session length interpolated from the constant and the preparation allowance **as a cap**. **The preparation allowance is CAPPED and must be published as capped** — *"including **up to** 2 hours"*, never the flat form and never "preparation included". **`/fees/` is UNBLOCKED for build step 9.** **The question as raised is preserved below.** **DOES `hours` IN THE MEDIATION RATE CARD MEAN THE LENGTH OF THE DAY, OR THE BILLED ENVELOPE INCLUDING PREPARATION?** `docs/07-fees.md` reads *"Half day — **up to 3.5 h, including 2 h preparation**"* and *"Full day — up to 7 h, including 3 h preparation"*. Taken at face value, 3.5 is the whole billed envelope and the **time in the room is 1.5 h** for a half day and **4 h** for a full day. **Against that reading:** 3.5 and 7 are exactly 2×, which they would not be if preparation sat inside them (1.5 vs 4 is not 2×). So either the card's wording is wrong in the one document that is the authority on money, or `FEES.mediation.*.hours` in `src/data/site.ts` does not mean what a page would naturally publish it as. **This was one sentence from shipping.** A draft of `/for-parties/` answered *"What happens on the day?"* with *"A half day is about 3.5 hours"* — the envelope presented as the day, to the reader least able to check it. The sentence was removed rather than resolved by inference; the page now says only that you book a half day or a full day. **What is needed:** one line from Pouya saying which the 3.5 and 7 are. Then `docs/07`'s two rows or `site.ts`'s field gains the correction, and the semantics go in the constant's doc comment (a warning is there now). **`/fees/` at build step 9 publishes this table and cannot be built without the answer.** Raised by `adversarial-reviewer`, 2026-08-30 | **Nothing.** No page stated a duration while the question was open — the one draft sentence that did was removed rather than reconciled, which is why the ruling had nothing to correct in public copy |
|
||
| ~~Q57~~ | **CLOSED 2026-08-31 — NO SEVENTH UNDERTAKING, AND THE PAGE IS COMPLETE AS IT STANDS.** Pouya: *"`/process/` stating when conflicts are run and what the check needs is complete. A reader assumes the outcome, and the obvious undertaking ("if a conflict is found I decline") adds nothing a reader doesn't already infer. Your restraint was right — §4's gate held. Record it closed rather than open, so it stops appearing in the live list."* **So this is a closure, not a deferral:** the answer is that the page says nothing further, which was one of the two outcomes the question named. §4 gains no seventh conduct undertaking and `CONDUCT_UNDERTAKINGS` still holds six. **APPLIED:** the `TODO(pouya)` is removed from `src/pages/process.astro` §Conflicts and replaced with the ruling, so a later reader finds the decision where the question was rather than an open marker; the file header's *"see the TODO below"* is corrected to cite this closure. `src/` now carries **zero** live `TODO(pouya)` markers. **The question as raised is preserved below.** **WHAT HAPPENS WHEN A CONFLICTS CHECK TURNS SOMETHING UP?** `/process/` §Conflicts ships saying **when** the check runs (the intake call, before anything is agreed) and **what it needs** (full legal names of the parties, the parent or affiliate actually behind the dispute, counsel on each side). It stops there, and the stop is deliberate: **any sentence naming the outcome is a SEVENTH conduct undertaking**, and §4's gate for that class is one line — *"an undertaking may be published only where Pouya has made it in terms. Not 'would obviously agree to', not 'follows from the process' — said."* *"If a conflict appears I decline the appointment"* is exactly what that gate refuses to let this repository infer, however obvious it looks. **What is needed:** one sentence from Pouya, in his words, or a decision that the page says nothing further. `TODO(pouya)` sits at `src/pages/process.astro` §Conflicts. Raised at build step 6, 2026-08-30 | **Nothing.** The section shipped accurate and unchanged; what closed is whether anything more was owed |
|
||
| ~~Q56~~ | **RULED 2026-08-30 — MEDIATION IS *NOT* SCOPED COMMERCIAL.** Pouya: *"Correct the four 'Commercial Mediation' surfaces to 'Mediation'; leave §4's mediation row unscoped."* **And the asymmetry with arbitration is DESIGNED, not an oversight — the reason is now recorded beside both §4 rows so nobody tidies them into a matching pair.** **Arbitration is scoped commercial because of a LEGAL GATE:** Q39 — family arbitration in Ontario requires prescribed training, and Pouya has excluded it by choice. **Mediation has no such gate**; he mediates commercial, construction, insurance/SABS, shareholder and cross-cultural matters, and the practice pages say so. So the site-wide "commercial" framing was **under-describing a wider offering**, which is why it is corrected rather than ratified as a positioning choice. `/practice/insurance/`'s SABS framing needs no reconciliation: it was never outside the offering. **The question as raised is preserved below.** ⚠️ **IS THE MEDIATION OFFERING SCOPED COMMERCIAL, OR NOT? THE SITE SAID BOTH.** §4 Offerings rows arbitration three times, each **scoped commercial**; the mediation row is `**Mediation** — sole mediator`, **unscoped**. Shipped output scopes it anyway: `/mediation/`'s `<title>` is *"Commercial Mediation"*, its `Service` node is `name: "Commercial mediation"`, and `/` and `/about/` both say *"I mediate commercial disputes"*. Meanwhile **`/practice/insurance/` offers mediation in matters that are not commercial on any ordinary reading** — *"Disputes between an insured person and an insurer under the Statutory Accident Benefits Schedule"*, with *"What I offer is private mediation"*. An individual claimant against their own insurer is not a commercial dispute. **Nothing here is a false claim** — scoping a page to commercial mediation asserts *less* than the unscoped §4 row grants, and narrower than the row is always safe. **The problem is that the two halves cannot both be the whole picture**: either the practice takes non-commercial mediations (and the site-wide "commercial" framing under-describes it, including on the page an appointing body reads), or it does not (and `/practice/insurance/` is offering something outside the offering). **What is needed:** either a §4 Offerings row scoping mediation, with `/practice/insurance/`'s SABS framing reconciled to it — or a decision that mediation is deliberately unscoped, in which case the site-wide "commercial" wording is a positioning choice and should be recorded as one rather than read as a limit. **Pre-existing, not created 2026-08-30** — but this change set newly wrote the claim onto `/med-arb/` and it has been removed again pending this answer. Raised by `adversarial-reviewer`, 2026-08-30 | **Nothing — ruled the same day it was raised.** No page was wrong; the register was silent where the site was specific, and the ruling makes the site match the register rather than the other way round |
|
||
| ~~Q55~~ | **CLOSED 2026-08-30 — NOT RESOLVED, AND THE DIFFERENCE IS THE RULING.** Pouya: *"The date is not published and nothing depends on it. Your split stamp was right: `[verified]` on the status, `[Pouya's stated basis]` on the date, the 2026-08-26 record noted as unreconciled. A register that says 'two inconsistent reports of an unpublished fact, neither relied on' is complete. Do not put it to Pouya."* **So this row is not a question any more and must not be re-raised as one.** §4's Q.Arb row now carries the split stamp explicitly and marks the 2026-08-26 (a) report **unreconciled, permanently**. **Why closing beats answering here:** the register's job is to say what it can vouch for, and it can vouch for exactly this — that he reported a July acquisition, that he had reported an August commencement three days earlier, and that no published claim rests on either. Asking again would buy a third self-report about a fact the site does not state. **The question as raised is preserved below, because the evidence is the record.** ⚠️ **WHEN WAS Q.Arb ACTUALLY OBTAINED? THE REGISTER HOLDS TWO DATES FROM THE SAME SOURCE AND THEY CANNOT BOTH BE TRUE.** (a) **2026-08-26 (a)**, Change Log, `[verified 2026-08-26]`: *"Q.Arb dated. Old → new: `[assumed]`, stage unknown → **commenced August 2026**"*. (b) **2026-08-29**, Pouya's amendment, now the §4 Verified row: *"Obtained July 2026"*. A designation cannot have been obtained in July from a pathway reported as commencing in August, and (a) was reported three days before (b). One self-report is wrong; the register cannot say which, and **inferring it would be exactly the guessed-explanation failure `CLAUDE.md` bars**. **THIS DOES NOT BLOCK, and that is the whole reason it is a question rather than a hold.** The published claim is *held* — **which is faithful to his most recent instruction, and that is a different thing from correct.** §4's premise is that `[verified — Pouya]` establishes *what he reported*, never the fact, and this is the one row where the register holds documented evidence that a self-report about this credential is wrong. The date is deliberately unpublished, so no page turns on the answer. What turns on it is whether §4 can vouch for its own highest-stakes new row. **What is needed:** one line from Pouya giving the correct date, and whether (a) was a misreport, a different milestone, or something else. Then re-stamp the §4 row and correct or annotate (a) — the Change Log is append-only, so (a) gets a pointer, never an edit. Raised by `claims-auditor`, 2026-08-30 | **Nothing — and closed on that basis rather than despite it.** The site states what Pouya most recently instructed, and no page carries the date |
|
||
| ~~Q1~~ | **ANSWERED 2026-08-26.** Licensure is left out entirely; the site asserts the JD only. See D13 | — |
|
||
| ~~Q2~~ | **ANSWERED 2026-08-26, AND SUPERSEDED 2026-08-29.** The answer then was *"Q.Arb commenced August 2026"*. **Q.Arb is now HELD** — see the §4 Verified row. ⚠️ Corrected in place because §9 is Current Truth; the superseded answer is preserved above rather than deleted, and **the conflict between the two dates is open as Q55** | — |
|
||
| ~~Q3~~ | **ANSWERED 2026-08-26.** Email `info@smlcompany.ca`. No public phone — "By scheduled call". Location: Toronto · Ontario · By appointment | — |
|
||
| ~~Q4 / Q14~~ | **ANSWERED 2026-08-26.** Rate card confirmed by Pouya — see D14 and `docs/07-fees.md` | — |
|
||
| ~~Q13~~ | **ANSWERED 2026-08-26.** Self-hosted Gitea with Gitea Actions | — |
|
||
| ~~Q15 / Q16 / Q17~~ | **ANSWERED 2026-08-26.** Non-mediation hourly $500. Prep bundled and **CAPPED**: **up to** 2 h in the half day, **up to** 3 h in the full day, and `docs/07` §All parameters confirmed requires it published **in hours and as a cap**. Overtime $500/h — **the RATE only; where it begins is §9 Q59, open.** ⚠️ *Corrected 2026-08-31 with Q58: this row prescribed the flat form ("2 h in the half day"), which is the form `docs/07` now says must never be published — and §9 is what a later implementer building `/fees/` reads. Found by `adversarial-reviewer` in the change set that wrote the new rule.* | — |
|
||
| ~~Q25~~ | **ANSWERED 2026-08-26. Struck.** The §4 row permitting the boutique to be named is removed; D16 governs alone | — |
|
||
| ~~Q26~~ | **ANSWERED 2026-08-26.** §4 now carries an explicit **Licence status — NOT ESTABLISHED** row, and its opening no longer asserts that LSO rules apply. The register's rationale stands on the fabricated-credentials history alone | — |
|
||
| ~~Q24~~ | **ANSWERED 2026-08-26.** `AWS-Hosting-Guide.md` copied into `docs/reference/` — it is the only record of how the hand-built infrastructure was created. Scanned for credentials before copying: no access keys, no secrets, no account ID | — |
|
||
| ~~Q22~~ | **CLOSED ON EXECUTION 2026-08-28 — it exists, and it was verified by running the checks rather than by reading the policy.** IAM user `adr-sml-deploy` created 2026-08-26T15:45:18Z; one inline least-privilege policy; one active access key, never used. Full inventory and the **nine** `simulate-principal-policy` results are in §7. **Two things make this a closure rather than a status update.** (1) The scoped policy was the control §10 identified as *"the actual control standing between a shared Gitea instance and an AWS account holding another business's client-database backups"* — it now exists **and has been proven negative** against that bucket, not just positive against its own. (2) `get-bucket-policy` on the backup bucket returns `NoSuchBucketPolicy`, closing the gap that policy-reading alone could not: a resource-based grant would have been invisible from the IAM side. **The quarterly rotation obligation in D3 now has a subject and a date** — 2026-11-26, in §12 R17. Deploys still run locally; the key exists but is unused. **The tool output IS committed** — `docs/reference/deploy-credential-verification.md`, Q52 closed 2026-08-28; R14 is satisfied for this row. | — |
|
||
| Q5 | Booking tool — **parked 2026-08-26 at Pouya's request.** Build `/contact/` with the form only and a clean slot for the embed. Now tracked as standing reminder R6 | `/contact/` — non-blocking |
|
||
| ~~Q6~~ | **ANSWERED 2026-08-26.** Supplied and committed: `src/assets/pouya-lajevardi.jpg` (1600×1600 master) and `src/assets/og-portrait.jpg` (1200×630 link-preview crop) | — |
|
||
| ~~Q7~~ | **ANSWERED 2026-08-26.** Pouya reverted to generic. The boutique is **never named**; refer to it as *a Toronto litigation and ADR boutique* throughout | — |
|
||
| ~~Q8~~ | **ANSWERED 2026-08-26.** ADRIC, ADRIO, OBA sections, **and the Canadian Tax Foundation** (CTF added 2026-08-26; this row omitted it until `claims-auditor` found the omission on 2026-08-27 — a second, stale copy of the memberships fact in a place nobody re-reads, which is the failure mode §7's single-source rule exists to stop. §4 is the source; this row is a pointer). Not OCNI. Not LSO (see §4) | — |
|
||
| ~~Q9~~ | **ANSWERED 2026-08-26.** Gitea, repo `adr-sml`, clone at `/Users/pouya/Dev/Websites/adr-sml` | — |
|
||
| ~~Q10~~ | **ANSWERED 2026-08-26.** Full inventory captured; values in §7 | — |
|
||
| ~~Q18~~ | **ANSWERED 2026-08-26.** `smlcompany.ca` is verified for sending — `true`. The `None` in the earlier listing was a query artefact, not a fault | — |
|
||
| ~~Q19~~ | **ANSWERED 2026-08-26. Production access granted** in `ca-central-1`, confirmed by AWS in writing, effective immediately. The per-region trap was real and was avoided — it was requested in `ca-central-1`, not the console's default `us-east-1`. **Nothing now blocks `/contact/`** | — |
|
||
| ~~Q20~~ | **ANSWERED 2026-08-26.** Both records added by Pouya and independently verified: SPF `v=spf1 include:_spf.google.com include:amazonses.com ~all` on `@`, DMARC `v=DMARC1; p=none; rua=mailto:info@smlcompany.ca; fo=1` on `_dmarc`. Both existing `@` TXT records, Google DKIM, MX, and the `adr` CNAME all confirmed intact | — |
|
||
| ~~Q21~~ | **ANSWERED 2026-08-26.** `ca-central-1` is healthy (`SUCCESS`) on the resolving token set. The broken records belong to a stray `us-east-1` identity this project does not use. **Nothing to fix.** The three dead CNAMEs are inert; leaving them is the low-risk choice | — |
|
||
| ~~Q11~~ | **ANSWERED 2026-08-26.** Privacy-first, cookieless — Plausible or Fathom. No GA4, no consent banner | — |
|
||
| ~~Q12~~ | **ANSWERED 2026-08-26.** `https://www.linkedin.com/in/pouyalajevardi/` | — |
|
||
| ~~Q27~~ | **ANSWERED 2026-08-26 — two business days.** A public commitment, so it must read identically everywhere it appears: `src/data/site.ts`, `/contact/`, the inquirer confirmation email, and any bio | — |
|
||
| ~~Q28~~ | **ANSWERED 2026-08-26 — OBA Construction & Infrastructure, ADR, and Civil Litigation** `[verified 2026-08-26 — Pouya]`, **for now**: section membership renews yearly, so this is a fact with a shelf life. Tracked as R10 | — |
|
||
| ~~Q29~~ | **ANSWERED 2026-08-26 by implementation.** Guard widened on both counts: the two secrets are checked (emptiness only, never echoed), and `INTAKE_ENDPOINT` is promoted to job-level `env:` and guarded. Every `vars.*` and `secrets.*` the workflow consumes is now covered except `BOOKING_URL`, empty by decision (R6) | — |
|
||
| ~~Q30~~ | **ANSWERED 2026-08-26 — federally, under the CBCA**, and it does **not** appear in the footer. Recorded in §4 with the caution that it implies nothing about licensure or about where the practice may operate. The footer reads `© <year> SML Company Ltd` and stops there (Pouya's direction, given twice). `src/data/site.ts` un-nulled, `TODO(pouya)` removed. Note the spelling: §4 writes *SML Company Ltd.* with a terminal period; the rendered string has none, because that is how Pouya specified it | — |
|
||
| ~~Q31~~ | **ANSWERED 2026-08-26 — Plausible**, and decided rather than defaulted. Pouya checked and found his own assumption wrong: Fathom is Canadian-owned but stores non-EU traffic on US servers, isolating in the EU only for EU visitors; Plausible holds everything in the EU. D15 amended with that reasoning. The value that was guessed and nulled is now the value that was chosen — which is not the same thing, and the difference is why it was nulled | — |
|
||
| ~~Q35~~ | **ANSWERED 2026-08-27, all four items, and the answer added a gate that was missing.** **(a) Med-Arb** — *"he holds Q.Med and now accepts arbitration appointments, so both halves are live. Keep it in the nav. Removing it unilaterally orphaned the page — restoring it was right."* It now has its own row in **§4 Offered now**, and stays in the footer sitemap (`docs/01` keeps it out of the *primary* nav deliberately; that is unchanged). **(b) `Energy, Grid & Regulatory`, `Shareholder & Family Business` and the other four** — *"subject-matter labels, already governed by `docs/03`'s 'positioning, not history'. They pass test 1; test 2 is the page's job."* **(c) THE GATE.** Pouya: *"Add the publication gate you identified was missing: a practice area may be named where he can competently accept an appointment in that subject matter, and where the page frames it as positioning without claiming history. That hole is why Med-Arb sat in the footer under a paragraph telling readers not to infer it."* Written into **§4 → Subject-matter areas — the publication gate.** Nothing in the nav or footer is now unrowed or ungated. Narrowed framing follows | — |
|
||
| ~~Q35-narrowed~~ | **NARROWED 2026-08-26 — two of the four items are resolved; two are not.** `Arbitration` is answered (Q33) and is now a **§4 Offerings** row. What remains: **(a) Med-Arb** — ungated by the same reasoning, so it is purely a competence call, and Pouya named mediation and the three arbitration forms without naming it. Do not infer it. **(b) `Energy, Grid & Regulatory` and `Shareholder & Family Business`** — subject-matter areas rather than gated activities, so the offering test asks only whether he is competent to mediate or arbitrate in them, which is his answer to give. `docs/03` already fixes how the pages must read once answered — *"Frame as positioning, not as history"* — so this is not a blocker on writing them, only on claiming capability in a one-word nav label before the page exists. Original framing follows | Med-Arb (step 4); the practice pages (step 5) |
|
||
| ~~Q35-orig~~ | **May the header nav and footer sitemap name a service or practice area the register does not establish as a present capability, before the page that qualifies it exists?** This is the architecture-versus-register question that `claims-auditor` has now raised twice, and it is not one an implementer should settle. The nav and footer ship on all nineteen pages and today carry **`Arbitration`**, **`Med-Arb`**, **`Energy, Grid & Regulatory`** and **`Shareholder & Family Business`** — none of which trace to a §4 row. Every one of them is also **locked architecture**: D5 and §6 fix the sitemap, and `docs/01` specifies each page. The specs already anticipate the tension and answer it at page level — `docs/03`: *"Frame as positioning, not as history"*; `docs/01` on energy: *"Write it as a genuine position, not a claim of existing volume"* — so the question is precisely whether a **one-word nav label**, which has no room to frame anything, inherits that licence. Three ways out: accept the labels as taxonomy and rely on the pages to qualify (status quo), rename toward capability-neutral wording, or hold items out of the nav until their page ships. **Claude Code declined to act unilaterally on either audit pass**; recorded so the judgement is visible rather than missed | The header and footer on every page; sharpest at step 5 |
|
||
| ~~Q36~~ | **ANSWERED 2026-08-26 — yes, and so are sole-arbitrator and party-appointed appointments.** Now a row in **§4 Offerings** rather than an unsourced assertion in three specs. `docs/01`, `docs/03` and `docs/07-fees.md` no longer need to cite an open question against it. Original text follows | — |
|
||
| ~~Q36-orig~~ | **Is co-arbitration work available now?** Asserted in three specs — `docs/01` §`/arbitration/`, `docs/03` §Voice as model copy, and `docs/07-fees.md`, which instructs *"The page must say so"* — and **it is in no §4 row.** §4 records the Q.Arb pathway as commenced August 2026 and nothing about what is available in the meantime. The sentence is offered under the heading *"Name the limits"*, so the unverified half travels inside advice about honesty, which is how it survived. All three files now cite this question; none has been deleted, because the *shape* of the sentence is right and only its second clause is unsourced. Raised by `claims-auditor`, 2026-08-26 | `/arbitration/` (step 4) and `/fees/` (step 9) |
|
||
| ~~Q37~~ | **ANSWERED 2026-08-27 — the label changes.** `JD + ML` is now labelled **"Legal training and engineering practice"**, not "Law and engineering". Pouya's reasoning, and it is the finding rather than the fix: *"The parallel was doing the implying — a degree and a practice under one noun. The asymmetry is the honest part."* A degree is not a practice, and a label that renders them as two instances of one thing invites the reader to supply the missing symmetry — which for "Law" is precisely the licensure implication D13 bars. The new label is longer and less tidy, deliberately. `docs/03`'s credential-row table is amended, and the `TODO(pouya)` is gone from `src/data/site.ts`. Original question follows | — |
|
||
| ~~Q37-orig~~ | **Is "Law and engineering" the right label under `JD + ML`?** §4's substitution principle supplies the three credential-row **values** (`Q.Med` / `JD + ML` / `EN · FA`); the labels come from `docs/03` and are not themselves registered. `claims-auditor` reads this one as a D13 implication risk: "engineering" is shorthand for a **verified practising** claim, so the parallel invites "Law" to be read the same way, and D13 bars implication as hard as assertion. Left as written — it is approved copy and changing approved copy is not an implementer's call — with a `TODO(pouya)` on it in `src/data/site.ts`. Nothing renders it yet. Raised by `claims-auditor`, 2026-08-26 | The credential row on `/` (step 2) and `/about/` (step 3) |
|
||
| ~~Q33~~ | **ANSWERED 2026-08-26 — the question rested on a false premise.** It assumed the constraint on describing arbitration was about *entitlement*. ADR designations are voluntary credentials, not licences, and **commercial arbitral appointment in Ontario is not gated behind a designation** — so the constraint was always positional, never legal, and it was Pouya's to answer. *(This row said "anyone may be appointed an arbitrator in Ontario" until 2026-08-27. **Pouya checked it and it is false as a universal** — family arbitration is gated; see Q39. Corrected in place, because §9 is Current Truth. The Change Log entries that quote the original stand unedited, which is where the history lives.)* He accepts arbitration appointments now. `Mediation · Arbitration · Toronto` is **restored to the masthead one-liner**, and ~~`docs/04`'s specified home `<title>` stands as written~~ — **AMENDED 2026-08-28.** The literal is replaced by a composition of `SITE.name` + `SITE.tagline`, so the masthead constants and the title cannot drift; the shipped string is `Pouya Lajevardi · Mediation · Arbitration · Toronto`. Q33's substance is untouched — the unscoped masthead form is still ratified — only the instruction to keep a hand-typed literal is See **§4 Offerings**, added for exactly this class of statement. The original question text follows for the record | — |
|
||
| ~~Q33-orig~~ | **How is arbitration described in site-wide copy before Q.Arb is conferred?** Not a wording question — a positioning one, and it recurs on every page. §4 records the Q.Arb pathway as **commenced August 2026**, "never as held or nearing completion". `SITE.tagline` reads `Mediation · Arbitration · Toronto`, and `docs/01` specifies that exact string as the **Home hero eyebrow** — where the hero copy beneath it can qualify it. Build step 1 promoted it to a masthead line under Pouya's name on every page, where nothing qualifies it and it reads as a designation strip; `claims-auditor` flagged it and **it has been removed from the header**. But the question it exposed is still open and lands at build step 2: does the hero eyebrow keep `Arbitration` as specified, qualify it, or hold it until designation? `/arbitration/` (step 4) is separately specced to state the position plainly, which is the honest model — the issue is the one-line forms that have no room to. **Second pass, same day:** the removal from the header did not sweep the proof sheet, where the same string was **hand-typed** as a type specimen and rendered ten times at up to 96px. Both defects fixed — the specimen is now a neutral pangram — and the lesson is the sweep rule again: a removal is a `grep`, not a memory. The nav item `Arbitration` also survives, deliberately; that is Q35. Raised by `claims-auditor`, 2026-08-26 | The Home hero (step 2); `docs/04`'s specified home `<title>`; any bio or one-line descriptor |
|
||
| **Q34** | **Do §2's measurements of the previous build still hold, and were they measured against the deployed file?** Two of `claims-auditor`'s findings were unverified old-site assertions published in copy, which sent Claude Code to measure the live URL on 2026-08-26. What came back does not straightforwardly match §2. **Reproduced:** the response is a single **2,206,032-byte** file, and `<title>` is still `SML Company · Dispute Resolution`. **Could not be reproduced from the served HTML:** there are **zero** `base64,` occurrences anywhere in it — §2 records "two logo PNGs ~1 MB, base64-inlined" — and no reference to `unpkg` or a React development build. **Why this is a question and not a correction:** the served document is a *bundler harness*. 2,210,921 bytes of it are inline `<script>`, the real `<head>` sits JSON-escaped inside a `<script type="__bundler/template">`, and the application is loaded from **nine UUID-named script files that were not fetched**. The logos and the CDN references may well be in those bundles. So §2 may be right, may be stale, or may have been measured against the local source rather than the deployment — this record cannot tell which. **Why it matters beyond tidiness:** `docs/02` and `CLAUDE.md` both cite the base64-logo figure as the *reason* for a standing convention, and §12 R8 exists because unverified premises propagate. Nobody should quote these numbers in public copy until the question closes. Raised by Claude Code, 2026-08-26 | Nothing structural. It governs whether §2's figures may be cited as fact |
|
||
| ~~Q39~~ | **ANSWERED 2026-08-27 — and the answer is that the register's premise was FALSE.** Pouya checked it rather than defending it. His words: *"My assertion was FALSE as a universal."* **(a) Is it gated? YES.** Family arbitrators in Ontario must complete prescribed training — 14 hours on screening for domestic violence and power imbalances, 30 hours of Ontario family law for arbitrators outside the Ontario or another Canadian bar, and 10 hours ongoing per two-year period. **Sourced, and the source is now in the repo** per R14: `docs/reference/ontario-family-arbitration-training.md`, retrieved 2026-08-27 with provenance. **(b) Does the offering extend to it? NO** — and that is what actually disposes of the question. Pouya does not do family arbitration, so it is a **scope exclusion, not a gating problem**, and the prescribed-training requirement never bears on this practice. `Shareholder & Family Business` means **commercial disputes among family shareholders** — shareholder and partnership disputes, co-founder breakdowns, business succession — and its page must state plainly that family law matters are not accepted. *One sentence, not a section: Pouya's instruction is that it earns its place only by saving a wasted intake call.* **(c) One honest limit on the source.** The extract establishes the family gate directly and the commercial half only by absence — it neither mentions nor excludes commercial arbitration. §4 therefore carries *"commercial arbitration in Ontario requires no licence and no designation"* as **Pouya's stated position, unstamped**, not as a sourced fact. Do not let the footnote promote it. **Also swept:** the false universal survived in three live places outside the paragraph that was corrected — §4's NOT-NEGOTIABLE boundary bullet, §9's Q33 closure row, and a comment in `SiteHeader.astro`. All three fixed; the `grep` and its output are pasted in **Change Log entry (w), §Sweeps**. *(`adversarial-reviewer` flagged this citation while it still pointed at nothing: the entry was written at Phase 6, after review, so for the duration of the review a §9 row asserted in the present tense that evidence "is in the Change Log" before it was. Fair catch. The row now names the entry, and the reviewer independently re-ran the sweep and confirmed it was genuinely complete.)* Original question follows | — |
|
||
| ~~Q39-orig~~ | **Does the arbitration offering extend to FAMILY arbitration, and is that activity gated?** Raised by `claims-auditor` 2026-08-26 as a counter-example from inside this repo, and it is a good one. §4 Offerings rests on the proposition that arbitral appointment in Ontario is not gated behind a designation. The site ships a **`Shareholder & Family Business`** practice area — and **family** arbitration in Ontario is understood to be one of the places where arbitrator qualification *is* prescribed by statute and regulation. If so, the offering test's own boundary applies: where an activity is gated, the question is **permission**, and permission is not established. **This record does not resolve it** — Claude Code will not assert a proposition of Ontario law, and neither may a self-report. What is needed: (a) does the practice-area page contemplate family-law arbitration at all, or only shareholder, partnership and family-*business* disputes, which is a different thing; and (b) if it does, the gating question needs a checkable source in the repo, per R14. **Interim:** §4's arbitration rows are scoped to **commercial** arbitration and the universal has been removed from the reasoning. Nothing ships that turns on it | The `Shareholder & Family Business` page (step 5); `/arbitration/` (step 4) |
|
||
| ~~Q40~~ | **RULED 2026-08-27 — and deliberately BUNDLED rather than shipped as a second interim.** Two kinds of card, not one. Pouya: *"A portrait is the **right** OG image for `/` and `/about/` — a face is the strongest social preview for a personal brand. It is the **wrong** one for nineteen pages, where a typed card carrying the page title would do the work. But do not build the generator now and do not leave 'portrait everywhere' as an untracked interim. **Ship it at step 7 alongside Insights, which needs per-article cards anyway — one build, one dependency, one review.**"* So the portrait is the **decided** card for `/` and `/about/`, not a placeholder; the generated typed card covers every other page and every article, built once at step 7 against a freshly checked pin (R11). Until then all pages share the portrait, and that interim **blocks cutover, not build step 3** — recorded on the cutover checklist in `docs/06` and tracked as **R15** with its removal trigger, on his instruction: *"Record the trigger so it cannot quietly become permanent."* `docs/04` amended. | Nothing until step 7. Then the generator, and cutover |
|
||
| ~~Q41~~ | **ANSWERED 2026-08-27 — all three, and two of the three interim wordings were wrong in a way the interim had not identified.** **(a) Q37's reasoning DOES extend to prose, and prose is held to a HIGHER bar, not a looser one.** Pouya: *"The implication test applies everywhere, not just to labels. Prose has more room, so it is easier to satisfy: **state the asymmetry explicitly** rather than relying on a parallel construction to carry it."* Deleting the parallel — which is all the interim did — was half the fix; a reader can still supply the missing symmetry from silence. Both pages now name both halves, from **one constant** — `ASYMMETRY_LINE` in `src/data/site.ts`, which is where a claim-bearing sentence belongs (`ROLE`'s reasoning: *"these are the two where the wording IS the compliance"*). It was typed into `/` and then into `/about/`, and **the two copies had diverged inside the same session** — a comma on one, full stops on the other — which is why it is a constant and why this row cites it rather than quoting a variant. Calling the legal half **training** is what makes the licence implication impossible rather than merely absent. `docs/01` §`/` item 3 and `docs/03` §Home both carry a warning not to lift their own phrase *"law and engineering"* into copy. **(b) NOT restored, and the editorial reason outranks the compliance one.** Pouya: *"That is an unverifiable empirical claim about other practitioners… **It is also weaker copy: assert his capability, not the field's incapability.**"* His replacement is used verbatim — *"disputes that turn on the contract, the code, and the engineering documents"* — and it replaces the comparative in `docs/03`'s **core positioning statement**, so the approved-copy defence that had protected it is gone. The interim (*"the documents rather than the pleadings"*) is also gone: it said nothing about other neutrals but still worked by contrast. **(c) Verified, and the interim was ambiguous in the one word that mattered.** `docs/reference/lat-case-conference.md` `[verified 2026-08-28]`: LAT **Rule 2.4** makes *"Pre-Hearing Conference"* the Tribunal's own term for a **case conference**; **Rule 14.3** puts a **Member** in the chair and then disqualifies them from the hearing panel; **Rule 14.6** makes attendance mandatory; and the Rules contain **zero** occurrences of `mediat` or `arbitrat` in 66,593 characters. A privately retained neutral cannot be appointed to it. The affirmative basis is on the Tribunal's own AABS page: *"Before you apply to the LAT-AABS, you may want to consider negotiation or mediation services."* The interim read *"private mediation of matters **before** the LAT"* — where `before` reads as *pending at* as readily as *prior to*. **⚠️ (c) IS PARTLY REOPENED AND CORRECTED 2026-08-29 — THE WORDING THAT CLOSED IT WAS WRONG ABOUT THE SOURCE.** This row quoted the Tribunal's passage with an ellipsis — *"…negotiation or mediation services… including before filing at the LAT-AABS, and continuing… after a claim has been filed"* — and **the second ellipsis deleted the word that scopes the clause.** The Tribunal's second sentence reads *"Parties are encouraged to attempt to **negotiate** the claim at all times, including before filing at the LAT-AABS, and continuing **negotiation** discussions after a claim has been filed"* — negotiation, twice. So the after-filing frame belongs to **negotiation**, not to mediation, and "private" is not the Tribunal's word either. **The published blurb rested on the elided half and shipped on three pages** — `/`, `/mediation/` and `/practice/`. Now published: *"private mediation retained by the parties, not the Tribunal's case conference"* — the distinction `docs/01` actually requires, and fully supported. **The defect was in the GLOSS beneath a correctly-quoted source**, which is why two review rounds and a claims audit read the extract and passed it; caught by an independent re-fetch that read the sentence structure. Same shape as Q39. Corrected in `docs/reference/lat-case-conference.md` (correction box), `docs/01`, `src/data/site.ts` and this row. **Nothing in Rule 2.4 / 14.3 / 14.6 or the zero-`mediat` count is affected** — that half of (c) stands. No roster claim, because there is no row for one | — |
|
||
| ~~Q42~~ | **ANSWERED 2026-08-27 — 3 offered, 1 STRUCK, and the one that failed is the finding.** Pouya applied the offering test himself: **early neutral evaluation** (*"A neutral assessment of merits sits inside a Q.Med's competence"*), **dispute-system design** (*"Consulting, no appointment, no neutrality question"*) and **pre-dispute technical advisory** (*"It is the moat"*) each gained a §4 Offerings row and may now ship on `/practice/`. **Settlement counsel is struck**, as his own error in `docs/01`: *"Settlement counsel acts **FOR a party** in negotiation. That is a partisan role, and putting it on a site that (a) sells neutrality and (b) asserts no licensure under D13 is **wrong twice over**: it undercuts the brand's central claim and it edges into acting for a client."* **The positioning objection comes first** — it would be wrong on a site with no licensure question at all, so it is not a D13 consequence. **What it exposed about the test:** settlement counsel fails neither question 1 nor question 2. Run mechanically the test would have PASSED it. It fails a prior question the test does not ask — *is this a neutral's role at all?* — so §4 now records that the offering test **presumes** a neutral role, with the Q42 worked example kept as the 3–1 table. Swept by command: `docs/01` §`/practice/`, `docs/07-fees.md` (three services at the hourly rate, not four), `FEES.hourly`'s comment, and `/`'s areas-more comment. `AGENTS.md` lines 293 and 3298 are the §4 scope enumeration (fixed) and Change Log entry (d) (history, not edited) | — |
|
||
| ~~Q43~~ | **ANSWERED 2026-08-27 — and the ruling reversed the reasoning that had blocked it.** The interim shipped the five timings as bare numbers because `docs/03` §Process required them *"real"* rather than illustrative, which was read as **barring** the word "typical". Pouya: the timings are **service commitments, the same class as Q27's response time** — *"not facts about Pouya, so they need framing, not a Verified row. Present them as the TYPICAL shape of an engagement, explicitly not a guarantee: mediation timing depends on party and counsel availability, which he does not control. **Published as typical, they are honest and useful; published as commitments, the first matter that slips makes the page false.**"* So no §4 row, and **the numbers are unchanged** — softening them was never the fix. What ships is `PROCESS_FRAMING` in `src/data/site.ts`: *"This is the typical shape of an engagement, not a commitment. Timing depends on party and counsel availability, which I do not control."* **Not optional, and placed adjacent to the numbers rather than in a section lede above them** — a reader who scans the strip and skips the lede has read a commitment. `docs/03` §Process amended to record the override; `docs/01` §`/process/` requires the same rendering at step 6 | — |
|
||
| ~~Q44~~ | **ANSWERED 2026-08-28 — all four current; R10 DISCHARGED, and it changes shape rather than closing.** Pouya: *"All four are current as of today."* ADRIC, ADRIO, the three OBA sections, the CTF. §4 re-stamped and `/about/` now renders the Memberships group. **Two consequences came with the answer and both are applied:** (1) **no currency warranty on the page** — the struck sentence stays struck and nothing replaces it, because he **declined renewal-date tracking** and so nothing in this repo could support one; (2) **R10 stays live and now fires on an EVENT, not a date** — re-confirm before any cutover or major republish. His reason, recorded because it is the general lesson: *"§4 already carries OCNI as lapsed and unpublishable, and that was found roughly a year late. A stamp with no trigger behind it goes stale silently, which is exactly how OCNI got onto a list of things to feature."* **Two things this answer did NOT settle**, both flagged to him rather than assumed: the stamp date (he wrote 2026-08-26, the original confirmation; the stamp reads **2026-08-28**, when he re-confirmed — a currency stamp records when the assertion was made), and `memberOf` in the JSON-LD — **which Q53 then ruled should be emitted, 2026-08-28.** `/about/`'s Person node carries the four memberships as `Organization` nodes; this row said "still withheld" until that sweep was actually run. See §4, §12 R10, `src/data/schema.ts` | — |
|
||
| ~~Q45~~ | **DEFERRED 2026-08-28 with a recorded trigger — now §12 R16.** Pouya: *"The one-page PDF bio is a derived artifact — generating it before `/about/` and `/fees/` are final just means generating it twice. Ship it at step 9 alongside `/fees/`, since an appointment proposal needs both. Record the trigger so it doesn't become another quiet interim."* Same disposition and same reasoning as Q40/R15: deferred with a build-step trigger rather than left as an untracked gap. The two decisions the question raised — generated-at-build vs authored once, and whether it carries anything the site does not — are **not** answered by the deferral and travel with R16 to step 9. The reason it is a credential document rather than a marketing one also travels: it circulates **detached from the site**, where no reviewer sees it again and no build can re-check it | Nothing. Tracked as R16, due at build step 9 |
|
||
| ~~Q46(a)~~ | **RULED A SECOND TIME AND CLOSED 2026-08-28 — PUBLISHABLE, and gate 1 is closed by the architect rather than by a source.** Pouya: *"Q46(a) PUBLISHABLE — ENE, dispute-system design and pre-dispute advisory pass all three gates. Flip the rows. Step 5 unblocked."* The three §4 Offerings rows are flipped, the worked-example table's gate-1 column reads `[Pouya's stated basis 2026-08-28]`, and `docs/01` and `docs/07` no longer carry the 🚫 blocks. **What this register held out for, and why it yields:** gate 1 asks *is the activity gated?* and §4's own test says it *"needs a source that a reviewer can check"*; no source for any of the three exists in `docs/reference/`. Pouya ruled once, this file declined to flip the rows and put the objection in front of him, **and he ruled again**. That is the mechanism working as designed rather than failing: gate 1 is a proposition of Ontario law about his own practice, §4 bars this file from concluding one in either direction, and holding a row against a repeated ruling would be this file substituting its judgement for the architect's. **The trade is recorded in the rows themselves** — `[Pouya's stated basis]`, never `[verified]` — so a reviewer sees an attributed position rather than a sourced fact. The framing constraints survive the ruling and are **not** discretionary: ENE is an assessment delivered to both parties, never advice to one; and the conflict caution on pre-dispute advisory is practice management, so no copy may imply the offering is free of it | — |
|
||
| ~~Q46(b)~~ | **(b) RATIFIED AND NOW SOURCED, 2026-08-28. (a) RULED, AND THE RULING DOES NOT CLOSE IT — now tracked as its own live row above.** **(b):** §11 Glossary is the source for **definitional expansions**; §4 remains the only source for claims about Pouya. Pouya: *"The line is the same one the Offerings ruling drew — 'Q.Med stands for Qualified Mediator' is a fact about the designation's name, not about him… You were right that one standard or the other had to apply."* He attached a condition — commit the source — and `docs/reference/adrio-designations.md` satisfies R14: all five expansions in ADRIO's own words, four independent fetches, reproducible sha256. **That fetch immediately earned itself** by catching that §11's `C.Med-Arb` expansion was wrong and had shipped to a public page. **(a):** he ruled that ENE, dispute-system design and pre-dispute technical advisory *"pass all three gates"*. Gates 0 and 2 are his and are answered. **Gate 1 is not his** — §4 says so twice — and it requires **an artefact, not a decision**: a checkable source, per activity and per jurisdiction. None existed and the ruling named none, so the three rows were held and the objection was put back to him as **Q46(a)** — **which he then ruled a second time, and Q46(a) is CLOSED. The rows are PUBLISHABLE and step 5 is unblocked;** gate 1 carries `[Pouya's stated basis 2026-08-28]`, not `[verified]`. Read the Q46(a) row above, not this sentence, for the disposition | Both closed |
|
||
| ~~Q47~~ | **ANSWERED 2026-08-28 — set both. THEN BOTH FIELDS WERE REVERTED THE SAME DAY, AND THE OPEN HALF IS Q49.** ⚠️ **Read this first, because the text below describes an implementation that does not exist.** Measured against `dist` 2026-08-28: the Person node ships `jobTitle: "Mediator"` and **no `worksFor` key at any depth**. `jobTitle`'s ruled value was struck by **both** review agents as the role-shaped claim `claims-auditor` had removed from this same node's `description` the previous day; `worksFor` was struck because §4 rows "**alongside** the practice" where the ruling says "operates **through**", and because `ProfessionalService.provider` is this Person, making the same-entity inference transitive. **Q49** carries both open rows. *This row was written describing the pre-revert state and not updated when the revert happened hours later — verbatim the failure Q44's own history records ("four documents recording a page state that had been reversed and not swept"), reproduced inside the change set that records it. Found by `adversarial-reviewer` on re-review.* **Pouya's ruling, and the reasoning that still stands, follows.** **ANSWERED 2026-08-28 — set both.** Pouya: *"A Person with a jobTitle and no worksFor is incomplete; a worksFor naming the boutique would breach D16. This satisfies both."* The bind is broken by changing what `jobTitle` is **about**: it now describes **this practice** rather than the boutique role, so `worksFor` can name **SML Company Ltd** — verified, federally incorporated, the entity the practice operates through — without going near D16. `ROLE.title` is unchanged and still carries "Director of Firm Operations" in **visible** copy; the graph gets its own constant (`PRACTICE_JOB_TITLE`), which is the separation the ruling actually turns on. **`worksFor` carries the NAME ONLY** — no address, no jurisdiction, no legal form: §4 verifies the federal incorporation and in the same row records it as *not published*, and cautions that it must never be read together with the **Licence status — NOT ESTABLISHED** row into an implication neither makes. A JSON-LD field is exactly where that pairing would travel unedited. **One flagged deviation:** he ruled `"Mediator and Arbitrator"`; it ships as **"Mediator and Commercial Arbitrator"**, because the same message instructs that *"Q39's struck universal must not reappear in any form"* and an unscoped "Arbitrator" is that form. One word to revert, deliberately | — |
|
||
| ~~Q48~~ | **CLOSED 2026-08-28 — not site-relevant, and that is a scope answer rather than an answer to the underlying question.** Pouya: *"ADRIO retention governs whether Pouya keeps a designation, not what the site may say about holding it."* He holds Q.Med today (§4, `[verified 2026-08-28]`), so `hasCredential` and the designation line are correct today, and the retention mechanics are his to manage rather than the register's to publish. **The asymmetry in ADRIO's materials is still real and still recorded** — `docs/reference/adrio-designations.md` Finding 4 — and nothing was inferred from it in either direction. **Consequence applied:** the `memberOf` comment in `src/data/schema.ts` no longer carries Q48 as an argument, because Q53 removed the withholding that argument was attached to | — |
|
||
| ~~Q49~~ | **ANSWERED 2026-08-28 — ONE ROW, and it is the value already shipping.** Pouya: *"one row: 'Mediator', supported by Q.Med plus completed sole mediations."* §4 Verified now carries **Practised role — "Mediator"** with both supports named, so `Person.jobTitle` stands on a row instead of on a derivation. **(a) closed:** the narrow value is ratified; the reverted `"Mediator and Arbitrator"` is not restored, and *"Arbitrator"* as a practised role remains unrowed. **(b) declined by the same ruling** — one row was granted and the corporate relation was not it, so **`worksFor` stays out of the graph**. ✅ **CONFIRMED BY POUYA 2026-08-29, as read.** His words: *"Q49 — CONFIRMED as you read it. One row, 'Mediator'. worksFor stays out."* The register had flagged the decline as a reading rather than a ruling, because Q49 asked for two rows and one was granted; the reading is now the ruling. **`worksFor` is settled out of the graph** — not withheld pending anything, and not a candidate for a later tidy-up | — |
|
||
| ~~Q50~~ | **ANSWERED 2026-08-28 — the masthead string, and one claim now has one form.** Pouya: *"`ProfessionalService.name` takes the ratified masthead string. Q33 reaches it; one claim should not have two forms."* `name` was a hand-typed third variant — *"Pouya Lajevardi — Mediation & Arbitration"*, em dash and ampersand — beside the masthead (*"Mediation · Arbitration · Toronto"*) and `/`'s `<title>`. ⚠️ **IMPLEMENTED AS TWO FIELDS, WHICH DEVIATES FROM THE LITERAL RULING AND NEEDS ONE LINE FROM POUYA.** What ships is `name: "Pouya Lajevardi"` and `slogan: "Mediation · Arbitration · Toronto"` — both read from `SITE.name` and `SITE.tagline`, so the hand-typed variant is gone either way, which is what the ruling was for. **Why not the concatenation:** on a `LocalBusiness`-family type `name` means the business's name, and a name plus a service list plus a city is the name-stuffing pattern a search engine discards a rich result for — on the one project whose entire purpose is crawlability. `areaServed` already carries Toronto and Ontario. schema.org has a field for each half of a masthead, so this is a decomposition rather than a refusal. **The half that is mitigated rather than answered:** `slogan` still carries an unscoped *"Arbitration"*, which was the second objection to the concatenation. Against that — the identical string already ships in `<title>`, `og:title`, `twitter:title` and `/`'s hero eyebrow, all ratified under Q33, so excluding it from one name-like field alone would be incoherent. `serviceType` stays scoped because it **enumerates services**. ✅ **RATIFIED 2026-08-29, AND POUYA REVERSED HIS OWN RULING TO DO IT — RECORD IT AS THE DECISION, NOT AS A DEVIATION.** His words: *"name: 'Pouya Lajevardi' + slogan. My ruling was wrong: on LocalBusiness, `name` means the business's name, and name + service list + city is the name-stuffing pattern that gets rich results discarded — on the one project whose premise is crawlability. areaServed already carries the city. Your reading beat mine; record it as the decision, not as a deviation."* So the two-field mapping is **the ruling**, the concatenation is struck, and nothing here is awaiting a line. The half that remains **mitigated rather than answered** is unchanged and stays stated: `slogan` still carries an unscoped *"Arbitration"*, acceptable only because the identical string already ships in `<title>`, `og:title`, `twitter:title` and `/`'s hero eyebrow under Q33. `serviceType` stays scoped because it enumerates services | — |
|
||
| ~~Q51~~ | **ANSWERED 2026-08-28 — KEEP THE OBA SECTIONS. The distinction is structural, not evidentiary.** Pouya: *"the Law Society is the regulator, so membership IS licensure; the OBA is a voluntary association. Structural distinction, independent of eligibility details."* That last clause is what closes it: the question was raised as unanswerable inside this repo **because OBA eligibility is not established here** — and the ruling makes eligibility irrelevant. A voluntary association admits members it does not license, so listing it carries no licensure implication; a regulator's membership roll *is* the licence. Recorded in §4's memberships row and in `.claude/agents/claims-auditor.md` so it is not re-litigated, and removed from `docs/06`'s cutover checklist. **R1 is unaffected** — same page, same subject, different question, still live | — |
|
||
| ~~Q52~~ | **CLOSED 2026-08-28 — committed, and RE-RUN rather than transcribed.** Pouya: *"YES — commit the simulate results, the inline policy, and the `NoSuchBucketPolicy` response, access key ID redacted."* `docs/reference/deploy-credential-verification.md` — eighteen read-only calls, each with the command that produced it, generated from captured output with the key ID replaced by `AKIA…REDACTED`. **Every value in §7's row reproduced**, including all nine `simulate-principal-policy` decisions (four `allowed`, five `implicitDeny`). **Two things the re-run added that the original verification did not have.** (1) A **contrast call**: `get-bucket-policy` on the *site* bucket returns exit 0 and a real policy, which is what makes exit **254** / `NoSuchBucketPolicy` on the backup bucket a genuine absence rather than a command that failed to start — the rule `CLAUDE.md` records twice, applied to the evidence that closes a High risk. (2) A correction to §7's own wording on the key's `LastUsed` field shape. The **secret** access key was never requested; the API cannot return it | — |
|
||
| ~~Q53~~ | **ANSWERED 2026-08-28 — EMIT IT. The withholding is dropped.** Pouya: *"the memberships are already crawlable in `/about/`'s HTML, so withholding the triple reduces no exposure and only makes the graph less complete than the page."* Option (a) of the three the question offered. `src/data/schema.ts` now emits `memberOf` — the four §4 memberships as `Organization` nodes — **on `/about/` only**, which is where the page shows them, so the graph and the visible page assert the same set. **This ends a judgement that was restated three times and wrong twice:** cacheability proved too much (equally true of `hasCredential`, which ships), volatility did not survive the page already carrying the claim, and the widened *"yearly renewing"* premise it rested on was itself a §4 misstatement found on re-audit | — |
|
||
| ~~Q54~~ | **ANSWERED 2026-08-29 — ALL SIX PUBLISH, INCLUDING (c), AND THE ANSWER CREATED A THIRD CLASS IN §4.** Pouya: *"Publish all six, including (c). (c) ships as drafted."* His reasoning on the expensive one, recorded on his instruction: *"it is the strongest available answer to the med-arb objection, and cheaper in practice than it sounds — the arbitral phase runs on the evidentiary record, not the caucus, so the case where a neutral genuinely cannot decide without confidential material is uncommon. `/med-arb/` was raising the hardest question about med-arb and answering it only at the level of process design."* **§4 now carries `Conduct undertakings` as a class distinct from both credentials and offerings** — his ruling: *"They are not facts about experience; they are commitments Pouya has now made... and they bind."* The gate for the class is one line: he must have said it in terms. The six strings are `CONDUCT_UNDERTAKINGS` in `src/data/site.ts` and the three pages render them, so **a later softening shows up as a diff on one constant** — his instruction that softening is a change to a published commitment, made mechanical rather than left as a note. (a)(b)(c) ship on `/med-arb/` in a new §What I undertake; (d) on `/mediation/` §Confidentiality; (e) and (f) on `/arbitration/`, each **replacing** the third-person sentence that already stated the same proposition as an observation. ⚠️ **The stamp reads 2026-08-29, not the 2026-08-27 he named** — the drafts did not exist on 2026-08-27 (Q54 was raised 2026-08-28), so that date would predate the text. **RATIFIED 2026-08-30: 2026-08-29 stands.** Pouya: *"You're right that a commitment cannot predate its own text. My 2026-08-27 was the date I ruled, not the date the undertakings existed."* | — |
|
||
| **Q38** | **A true vector master for the infinity mark.** The mark is a shaded ribbon — variable-width band, maroon flowing into champagne, twisting in three dimensions and passing over itself at the crossing. That is gradient-mesh artwork, and there is no honest way to express it as the flat vector paths `docs/02` assumes. An SVG **is** held — `src/assets/brand/sml-logo-source.svg` — and **it renders faithfully**: rasterised at 8333 px it reproduces the master exactly, at the same 1.566:1 `[verified 2026-08-26 — rendered and measured]`. *The characterisation has now moved twice and Pouya has settled it.* This row first called the file **"a raster in a vector wrapper"**; a later draft withdrew that as unfair. **The withdrawal went too far, and Pouya's ruling of 2026-08-27 restores the substance:** *"It renders faithfully because it IS the raster. Your first characterisation was accurate and the walk-back went too far."* Both things are true at once and the row must hold both — the file is a faithful rendering **and** it is faithful because seven base64 PNGs are carried inside it, which is why fidelity was never the question. **The Canva SVG does not close this question.** Pouya: *"Keep it committed, keep the AVIF render path. R13 stays open for a true vector master."* What rules it out is **payload and composition**: 257,278 bytes against **3,063 B** for the AVIF a Retina browser takes in the header — **84×** — plus **seven embedded base64 PNGs** and a 1,225-stop gradient mesh, so inlining it would breach `CLAUDE.md`'s rule against base64-inlining images. *Restated 2026-08-27, because the single number stopped covering the case:* build step 2 added a **232 px** call site (the home page's approach section, rendering at 225.5 px) beside the existing 64 px one, and at that size a DPR-2 device takes **14,555 B** and DPR-3 **22,639 B** — a ratio of ~11×, not 84×. `adversarial-reviewer` caught the three copies of the old figure going stale together, which is the SES-DKIM duplication in a new place. Both ladders are in `docs/reference/brand-assets.md`; **quote the size with the call site, never on its own.** Also worth knowing before someone reads it as a regression: the PNG fallback at 232 px runs **38,094 / 91,618 / 150,215 B**. Nothing that negotiates content types takes it — a DPR-3 device with neither AVIF nor WebP does not exist in practice — and the AVIF above is what real clients fetch. Accepted deliberately rather than capped, because capping it would blunt the mark on the high-DPI desktops that are the only place the 696 px variant is used at all. What is wanted is a master that is faithful **and** light. **Pouya is commissioning a proper vector master.** Until it lands, `InfinityMark.astro` renders an optimised raster and that is a **documented, temporary exception to `docs/02`'s inline-SVG rule** (R13 keeps it from becoming permanent). When the master arrives: replace the component's `<Picture>` with inline SVG, regenerate the favicons from it, and delete the exception from `docs/02` and this row. Raised by Claude Code 2026-08-26; scoped by Pouya the same day | Nothing — the mark renders correctly. This is fidelity and payload, not function |
|
||
| ~~Q32~~ | **ANSWERED 2026-08-26 — and the answer was that the reconstruction was WRONG.** Pouya rendered the committed path against the master (`SML Company Just Logo Transparent.png`, 3000×3000) and rejected it on three counts. Two reproduce from the path alone: **(a) TANGENT, NOT CROSSING** — all four cubic branches meet the origin at exactly 90°, so the loops are mutually tangent on a vertical line and at stroke-width 28 render as *two kissing circles*, the one thing an infinity mark must not be `[verified 2026-08-26 — tangent vectors computed per segment, independently reproduced]`. Both lobes are strictly confined to their own half-plane (x is monotone on every segment), so the signed crossing number is **0** — they cannot cross anywhere, not merely at the node. Worse at the size actually shipped: the two strokes stay fused into one mass wherever the centreline separation `y²/192` is under 28, i.e. across **61% of the mark's height** — at 2rem that is a 16.8px blob out of a 27.4px-tall mark. No stroke-width, viewBox or scale change can produce a crossing from this centreline; **(b) WRONG PROPORTION** — the master's ink bounding box is **2668 × 1704 = 1.5657:1** `[verified 2026-08-26 — measured]`, and **(c)** the master is a shaded ribbon where the trace was two flat uniform strokes. ***1.23:1 — RECONCILED, and it was a real measurement, not a slip.*** It is the bounding box of the path's **coordinates** rather than of the **curve**. The control points sit at y = ±160 while the curve only reaches ±120 — the standard 3/4 pull-in of a cubic — so a coordinate-hull box is 400 × 320 = 1.2500, and with stroke-width 28 applied on all four sides it is **428 × 348 = 1.2299**. Pouya's figure to four significant figures, from one method applied consistently `[verified 2026-08-26 — derived]`. **It is a trap rather than a slip:** because x is monotone on every segment, the control points give the *correct* width (±200) and a 33% inflated height, so the obvious sanity check — "does the width look right?" — passes. Any tool that reads a bbox from parsed coordinates lands here; `getBBox()` would have returned 400 × 240. **And the direction is inverted from how it read:** measured from the curve, the traced path is 6.4% *wider and flatter* than the master, not squatter. **Consequence worth keeping:** the declared viewBox 440:280 = 1.5714 is within **0.35%** of the master's 1.566, so re-tuning the layout to the true ratio was ~0.18px of work at the shipped 2rem — and **re-tuning to 1.23 would have actively broken it** — at any given width 1.2299 allocates 1.5657/1.2299 = **27% more height** than the mark occupies, so the header would have been rebuilt around a box a quarter too tall. The ratio was never sufficient grounds on its own; **(a) tangency is, and it is exact.** **The traced path is deleted, not kept as a fallback**, on Pouya's instruction: *a wrong mark that renders is worse than a missing one, because it stops looking wrong.* Now closed by Q38 for the vector master | — |
|
||
| ~~Q32-orig~~ | *(superseded — the original wording of this question is preserved in entry (v))* | `src/components/InfinityMark.astro` is built from geometry lifted verbatim from the deployed site's own loading-thumbnail SVG — the element it labels `smlMark`, fetched from `https://adr.smlcompany.ca/` on 2026-08-26. Path, both stroke widths (28 / 6) and the 0.7 inner opacity are the source's; the only change is folding a `translate(60 0)` into the coordinates. So it is SML's own artwork rather than a redrawing — but a loading placeholder is not necessarily the canonical file, and D7 says the mark carries over *unchanged*. If a master SVG or AI/EPS exists, supply it and the component gets replaced. Raised by Claude Code, 2026-08-26 | Nothing — the mark renders. This is about fidelity, not a blocker |
|
||
| **Q23** | **Is a Gitea `act_runner` registered, and are Actions enabled in `app.ini`?** *The version half is closed:* the instance reports **1.27.2** `[verified 2026-08-26 — /api/v1/version]`, so the `vars` context is supported and the first-step guard is belt-and-braces rather than load-bearing. **What remains is not a fact to look up but a dependency on a person:** git.larsnolden.com is **jointly administered**, and both enabling Actions and registering a runner need the second administrator. Until then `npm run deploy` is the path, and it is documented rather than treated as a workaround | How deploys are triggered — not what they do |
|
||
|
||
## 10. Risks
|
||
|
||
| Risk | Severity | Mitigation |
|
||
|---|---|---|
|
||
| A fabricated or unverifiable claim reaches a public page | **High** — professional-conduct exposure | §4 register; every claim traced to a source before it ships |
|
||
| Copy silently carried over from the placeholder template | High | Nothing is ported verbatim. All copy written fresh against `docs/03-content-spec.md` |
|
||
| Insights section launches and then goes stale | Medium | D9 commits to 3–5 pieces at launch and a monthly cadence. A dead blog is worse than no blog |
|
||
| Personal data in the intake pipeline without a retention policy | Medium — PIPEDA | `docs/05-backend-spec.md` sets retention, and `/legal/privacy/` states it |
|
||
| Cutover breaks the live site (D11 is a single-shot deploy) | Medium | Full pre-cutover checklist in `docs/06-deployment.md`; CloudFront can be rolled back to the prior origin path |
|
||
| Twenty pages of thin copy rank worse than six good ones | Medium | Each page must justify itself with substantive content. Ship fewer pages rather than padded ones |
|
||
| **`user/pouya` is a broadly-permissioned personal IAM user, and it is what has been authenticating to this account.** *Q22 closed 2026-08-28: the scoped deploy user now **exists**, so the mitigation below is available rather than pending — but this risk does not close, because `user/pouya` still exists, is still broadly permissioned, and is still what runs the local deploy path* | **High** → **Medium** for CI; unchanged interactively | Fine at an interactive keyboard; **never** in CI, never in a Gitea secret, never in `scripts/deploy-local.sh`. That script refuses to run if `sts get-caller-identity` returns `user/pouya`. **`adr-sml-deploy` now exists and is verified least-privilege (§7), so there is no longer any reason to reach for `user/pouya` in an automated context** `[verified 2026-08-28 — Q22]` |
|
||
| **The deploy secret will live on jointly-administered infrastructure.** git.larsnolden.com has a second administrator. An instance admin can generally reach repository secrets, or register a runner that receives them — that is inherent to how Actions runners are fed credentials, not a flaw in this setup | **High** | This does not change the plan; it changes **what the scoped IAM policy is for.** The policy is no longer hygiene — it is the actual control standing between a shared Gitea instance and an AWS account holding another business's client-database backups. Four actions, one bucket, one distribution. **Never widen it**, and treat any request to as a security decision, not a convenience one `[verified 2026-08-26]`. **THE CONTROL NOW EXISTS AND HAS BEEN TESTED AGAINST THE THING IT PROTECTS** — `adr-sml-deploy` returns `implicitDeny` for `s3:ListBucket` and `s3:GetObject` on the client-backup bucket under `simulate-principal-policy`, and that bucket has no bucket policy (§7, Q22) `[verified 2026-08-28]`. The severity stays **High** because the exposure is unchanged: a static key on shared infrastructure, and the key is only as narrow as the next person to edit the policy leaves it |
|
||
| **Deploy-credential blast radius.** AWS account `327082975128` is not a single-project account. It also holds `meshkinilaw.ca` and its preview site, `demesne.media`, `orynenergy.ca`, `lajirugs.ca`, and **`mlp-clientdb-prod-backups-327082975128`** (recorded in an earlier entry with the account suffix; the short form `mlp-clientdb-prod-backups` is used elsewhere in the docs) — which **by its name** holds production client-database backups. Only the name was ever observed; the contents were not inspected and the owner is not established | **High** | A static deploy key for a personal website must never be able to reach a client database. The scoped IAM policy in `docs/06-deployment.md` grants four actions on one bucket and one distribution and nothing else — that narrowness is now load-bearing, not hygiene. Never widen it. Never reuse the `user/pouya` credentials in CI `[verified 2026-08-26 — inventory]`. **TESTED 2026-08-28 (Q22), and both halves were tested, which is the part that matters:** `simulate-principal-policy` returns `implicitDeny` for `s3:ListBucket` and `s3:GetObject` on `mlp-clientdb-prod-backups-*`, **and** `get-bucket-policy` on that bucket returns `NoSuchBucketPolicy` — so there is no resource-based grant, IAM is the only path, and this user has none. A policy read alone could not have established the second half `[verified 2026-08-28 — Pouya]` |
|
||
| ~~SES is in the sandbox~~ | ~~High~~ → **RESOLVED 2026-08-26** | Q19 closed: production access granted in `ca-central-1`, confirmed in writing. Residual, tracked in §7: the `ses-alerts` SNS email subscription is **pending confirmation**, so the bounce and complaint alarms currently notify nobody `[verified 2026-08-26]` |
|
||
| ~~No SPF and no DMARC on `smlcompany.ca`~~ | ~~High~~ → **RESOLVED 2026-08-26** | Both records added by Pouya and independently verified (Q20). SPF authenticates Google Workspace mail; SES satisfies DMARC through DKIM alignment on the three resolving CNAMEs. DMARC sits at `p=none` — the residual task is to review reports and tighten to `quarantine`, which is monitoring, not a risk `[verified 2026-08-26 — DNS query]` |
|
||
|
||
## 11. Glossary
|
||
|
||
> ✅ **THIS SECTION IS A PUBLISHABLE SOURCE — for DEFINITIONAL EXPANSIONS ONLY.**
|
||
> Ratified by Pouya 2026-08-28 (Q46(b)): *"§11 Glossary is the source for
|
||
> DEFINITIONAL expansions; §4 remains the only source for claims about Pouya. The
|
||
> line is the same one the Offerings ruling drew — 'Q.Med stands for Qualified
|
||
> Mediator' is a fact about the designation's name, not about him."*
|
||
>
|
||
> So a page may expand an abbreviation on this section's authority. It may **not**
|
||
> say he holds the thing, has commenced it, or is progressing toward it — those
|
||
> are §4 Verified rows, and §4 remains the only gate for them.
|
||
>
|
||
> **The five ADR designations are sourced, not asserted here.**
|
||
> `docs/reference/adrio-designations.md` carries all five in ADRIO's own words
|
||
> with reproducible digests (R14). Pouya attached that fetch to the ratification
|
||
> as a condition, and it caught the error below.
|
||
>
|
||
> ⚠️ **CORRECTION, 2026-08-28 — `C.Med-Arb` WAS WRONG IN THIS TABLE FROM THE
|
||
> FILE'S CREATION.** It read *"Chartered Mediator-Arbitrator"*. ADRIO's term is
|
||
> **"Chartered Med-Arbitrator"**. Pouya raised it himself: *"I took the expansion
|
||
> from the strategy brief and never sourced it… It is the practice's stated
|
||
> long-term designation, so getting its name wrong on a public page is not
|
||
> cosmetic."* It **had** reached a public page — `/about/`'s credential arc, and
|
||
> `dist/about/index.html` — and four adversarial review passes read that string
|
||
> without catching it, because each checked whether it was *sourced*, not whether
|
||
> it was *right*. Swept from four files; the sweep command is in Change Log (y).
|
||
|
||
| Term | Meaning |
|
||
|---|---|
|
||
| ADR | Alternative dispute resolution |
|
||
| ADRIC | ADR Institute of Canada — national credentialing body |
|
||
| ADRIO | ADR Institute of Ontario — provincial affiliate |
|
||
| Q.Med | **Qualified Mediator** — ADRIC / ADRIO designation |
|
||
| Q.Arb | **Qualified Arbitrator** — ADRIC / ADRIO designation |
|
||
| C.Med | **Chartered Mediator** — ADRIC / ADRIO designation |
|
||
| C.Arb | **Chartered Arbitrator** — ADRIC / ADRIO designation |
|
||
| C.Med-Arb | **Chartered Med-Arbitrator** — ADRIC / ADRIO designation. *Do not write "Mediator-Arbitrator", and do not call it "senior" or "the senior hybrid designation": this row said that until 2026-08-28, and it is a ranking claim about a third party's credential structure with no source. ADRIO applies "most senior" to **C.Med**, not to this one — and §4 Forbidden bars superlatives on the site regardless of who said them first.* ⚠️ **THIS ROW IS A DEFINITION AND NOTHING ELSE (2026-08-29).** It used to close *"that it is Pouya's long-term goal is a §4 row"*; that §4 row is struck and C.Med-Arb is off the site entirely. The designation exists; this project makes no claim about it and names it on no page. |
|
||
| CTF | Canadian Tax Foundation |
|
||
| Med-Arb | Hybrid process: mediation that converts to binding arbitration if unresolved |
|
||
| SABS | Statutory Accident Benefits Schedule — Ontario auto insurance benefits |
|
||
| LAT | Licence Appeal Tribunal — hears Ontario SABS disputes |
|
||
| POA | Provincial Offences Act |
|
||
| ENE | Early neutral evaluation |
|
||
| LSO | Law Society of Ontario |
|
||
| OBA | Ontario Bar Association |
|
||
| IESO | Independent Electricity System Operator |
|
||
| OEB | Ontario Energy Board |
|
||
| SMR | Small modular reactor |
|
||
| PIPEDA | Personal Information Protection and Electronic Documents Act |
|
||
|
||
## 12. Standing reminders
|
||
|
||
**Surface these to Pouya at the start of any substantial session.** They are
|
||
open questions he has deliberately parked, not settled matters. The point of
|
||
this section is that a parked decision does not quietly become permanent by
|
||
never being raised again.
|
||
|
||
| # | Reminder | Raised | Why it must keep coming back |
|
||
|---|---|---|---|
|
||
| R1 | **RAISED AGAIN 2026-08-28, and `/about/` is why the stakes moved a second time.** `/about/` is *"the page an appointing body or opposing counsel reads before agreeing to an appointment"* (`docs/01`), it is the site's credential spine, and it now carries the full designation list, the education line, the certifications, the memberships and the boutique role — with **no licence status stated either way**. On `/` that reads as brevity. On a dedicated credentials page a sophisticated reader notices the omission, and D13's framing is doing more work than it was designed for. Q41(a)'s ruling is now load-bearing on the same page: the copy says the legal half is *"training I hold"*, which is honest and is also the closest the site comes to addressing the question. **Nothing here is a request to change D13 — it is the surfacing R1 exists to compel.** Previous text follows. **Licensure — RAISED 2026-08-27 and acknowledged by Pouya; still open, and the stakes are higher than when it was written.** His words: *"The interim licensure framing is now carried by shipped pages rather than specs, which raises the stakes. Keep surfacing it."* So it is surfaced, and it will be surfaced again next session. **The opening sentence below is now false and is kept only because §12 rows are not rewritten silently:** `src/pages/` exists, `/` ships at build step 2, and the framing is on a public page rather than in a document. Original text follows. **Licensure.** No site exists yet — `src/pages/` does not exist. **As specified**, the copy will assert the JD only and describe the boutique role as *active litigation exposure*, never *practice*. Pouya flagged that as an interim position and asked to be reminded to change it. §4 now records licence status as `[unestablished]`, which is the honest state, not a resolution | 2026-08-26 | If he is licensed and in good standing, it is the first credential appointing bodies and opposing counsel look for, and its absence from a detailed credentials page is conspicuous. If licensure is in progress, the copy should be rewritten the moment it completes. Either way this is a **temporary** framing that will otherwise ossify |
|
||
| R2 | **Matter counts stay off the site until they are independently credible.** Revisit once there is a number a sophisticated GC would find persuasive on its own | 2026-08-26 | §4 forbids them now. That rule has an expiry date nobody has set |
|
||
| R3 | **The month 12–18 practice-area review — now two candidates, not one.** *(a)* **Indigenous engagement**, deliberately omitted at launch (§6). *(b)* **Tax-adjacent disputes**, added 2026-08-26 on the Canadian Tax Foundation membership: it is the one credential none of the six areas touch, and valuation, earn-out, indemnity and shareholder disputes that turn on a tax position are ADR territory. Reasoning for both is in `docs/01-architecture.md`. One review, two candidates | 2026-08-26 | The brief rates the Indigenous niche the most valuable single one, and omission there is a timing call rather than a permanent one. The tax case is the same shape and fails for the same reason today: a practice page is a claim of present capability, and a membership is a credential, not a caseload. Both stop being true at some point, and nothing will tell you when |
|
||
| R4 | **Insights cadence.** D9 commits to monthly. A blog that stops is worse than one that never started | 2026-08-26 | The section's whole value is compounding |
|
||
| R5 | **Fee review at 12 months.** Published rates are sticky; the right moment to move them is deliberate, not reactive. ⚠️ **ONE ITEM IS ALREADY WAITING AND IT IS ARITHMETIC RATHER THAN JUDGEMENT — added 2026-08-31:** the half-day-plus-overtime route is cheaper than the full-day rate at **every** session length, by $2,000 at three hours narrowing to $500 from six on, because the half-to-full step is $2,000 and three hours of overtime is $1,500. Written out in `docs/07` §Recorded dissent with the table, which is the section built for this review to test against. The **trigger** for the overtime hour is a separate open question — §9 Q59 | 2026-08-26 | D14 is priced for where the practice is going, not where it is. And the anomaly above was assigned to this reminder twice in one change set and written into neither place the reminder lives, which is the failure §12 exists to prevent |
|
||
| R6 | **Booking tool.** Parked by Pouya on 2026-08-26; `/contact/` ships with the intake form and a reserved slot for an embed | 2026-08-26 | He asked to be reminded. D10 committed to booking because it removes the back-and-forth that loses appointments — the form alone is a partial answer |
|
||
| R9 | **The SES alarms notify nobody until the `ses-alerts` email subscription is confirmed.** `SES-BounceRate-High` and `SES-ComplaintRate-High` are configured and live; the SNS email subscription to `info@smlcompany.ca` is **pending confirmation**, and an unconfirmed subscription drops every message | 2026-08-26 | A monitoring control that exists but does not deliver is worse than none, because it reads as covered. At this volume five bounces can cross the ~5% suspension threshold. Tracked in §7 and on the cutover checklist, but a one-click task nobody owns is exactly what §12 is for |
|
||
| R10 | ⚠️ **A THIRD SURFACE, 2026-08-30: `/process/` §Confidentiality renders `MEMBERSHIP_ORGS[0]` ("I am a member of the ADR Institute of Canada").** It is rendered from the constant rather than typed, so the sweep this reminder prescribes reaches it — that was `adversarial-reviewer`'s finding and the fix, in that order. **DISCHARGED AS WRITTEN 2026-08-28 — AND RE-ARMED WITH AN EVENT TRIGGER INSTEAD OF A DATE. STILL LIVE.** Pouya re-confirmed all four memberships as current (Q44), which discharges the prohibition this row carried, and `/about/` now publishes the Memberships group. **The row does not close, because he declined renewal-date tracking**, and that was his instruction for what to do about it: *"Without renewal months it cannot fire on a date, so make it fire on an event: re-confirm memberships before any cutover or major republish, and re-stamp §4 when confirmed."* **THE TRIGGER: re-confirm before any cutover, and before any major republish. Then re-stamp §4 the same day.** **His reason, kept verbatim because it is the general principle and not a membership detail:** *"§4 already carries OCNI as lapsed and unpublishable, and that was found roughly a year late. A stamp with no trigger behind it goes stale silently, which is exactly how OCNI got onto a list of things to feature."* **Two things the discharge did NOT license.** (1) **No currency warranty on the page** — list the memberships, promise nothing about their future state; the struck sentence stays struck and nothing replaces it. (2) ~~`memberOf` stays out of the JSON-LD~~ — **SUPERSEDED. Q53, ruled 2026-08-28: EMIT IT.** `/about/`'s Person node now carries the four memberships as `Organization` nodes. Pouya took `adversarial-reviewer`'s argument: they are already crawlable in `/about/`'s HTML, so withholding the triple reduced no exposure and only made the graph less complete than the page. **The consequence for THIS reminder is that it now covers two surfaces** — re-confirming before a cutover means `src/data/schema.ts` as well as the visible list, and they must not be allowed to diverge. **Renewal periods, stated once and not widened again:** the OBA sections and the CTF renew yearly; §4 records **nothing** about ADRIC's or ADRIO's period, and the widened form ("all four renew yearly") reached four files before it was swept. *Previous text described the prohibition and the withheld group; it held for one session and did its job.* | 2026-08-26 | A credential that lapses quietly is the failure mode §4 exists to prevent, and OCNI already did exactly this. The group is on a public page now, which raises the cost of a lapse rather than lowering it — *(This rationale ended by pointing at **Q48** as a possible widening of the row. Q48 closed 2026-08-28 as not site-relevant — ADRIO retention governs whether Pouya keeps a designation, not what the site may say about holding one — so the clause is struck. §12 is read aloud every session; a live reminder pointing at a struck row produces a false surface every time.)*, not just a list |
|
||
| R11 | **Re-check dependency currency at every phase boundary in the build order** (`docs/01-architecture.md` §Build order, 11 steps). Run `npm view <pkg> version` across **every** pin in `package.json` and compare; do not wait for something to break. Verified does not mean latest — record the reason for any deliberate hold in §7. **Carries one specific re-add trigger: at step 7, put `@lhci/cli` back.** Check for a patched release — do not assume `0.15.1` is still the ceiling just because it was on 2026-08-26 — pin it against `npm view` that day, write a `lighthouserc` with the budgets from `docs/04-seo-spec.md`, and delete the UNAVAILABLE notices this repo now carries in six places (§7 lists them). If the advisories are still unfixed, that is a decision to take deliberately, not a reason to leave the gap unstated | 2026-08-26 | `astro: "^5.0.0"` was recalled rather than checked and was two majors stale the day it was written, which meant a framework carrying high-severity XSS advisories. Between phases is cheap; after a phase of pages is written is not. The build order has ten more boundaries |
|
||
| R12 | **`compressHTML: true` is a deliberate deviation from the Astro 7 default (`'jsx'`).** Measured 2026-08-26: in an `.astro` template an inline pair split across two lines renders as `<em>a</em><strong>b</strong>` under the default — the space is silently deleted. MDX prose is unaffected | 2026-08-26 | It is a deviation, and undocumented deviations become folklore. Revisit **with a measurement**, not a preference — and re-measure after any Astro major, since the behaviour could change again |
|
||
| R13 | **The infinity mark ships as a RASTER, and that is temporary. RAISED 2026-08-27; Pouya ruled the committed SVG does NOT close it** — *"Keep it committed, keep the AVIF render path. Your own measurement is the reason: 257 KB wrapping seven embedded base64 PNGs. It renders faithfully because it IS the raster."* So the exception stands and the reminder stays live. `InfinityMark.astro` renders an optimised AVIF/WebP from `src/assets/brand/sml-infinity-mark.png` — a deliberate, documented exception to `docs/02`'s "inline SVG, never a PNG", because the mark is gradient-mesh artwork and no true vector master exists yet (Q38). **Removal trigger: the commissioned vector master lands.** Then replace the `<Picture>` with inline SVG, regenerate `favicon.ico` and `apple-touch-icon.png` from it, and delete the exception from `docs/02`, from the component, and from Q38 | 2026-08-26 | Pouya flagged this himself when he made the ruling: *an interim raster is exactly the kind of temporary measure that becomes permanent by never being raised.* It costs ~8 KB and works, which is precisely why nobody will notice it again. There is no build error to prompt anyone — only this row |
|
||
| R14 | **Anything a spec makes a claim about must be reachable from the repository.** If the artefact lives only in Drive, in a console, or on someone's disk, no reviewer can check the claim and the claim is unverifiable by construction — see the rule now in `CLAUDE.md` | 2026-08-26 | **This has now cost twice.** Q24 was `AWS-Hosting-Guide.md`, the only record of how the infrastructure was hand-built, living outside the repo. Q32 was the infinity mark: Claude Code traced it from the old site's *loading placeholder*, wrote a scrupulous provenance comment recording exactly that doubt — and **two adversarial review passes still could not catch it**, because the artwork they would have had to compare against was not in the repo. The doubt was correctly stated and structurally uncheckable. That is the failure mode: not a missing warning, a missing artefact |
|
||
| R15 | **Every page shares ONE Open Graph image — the portrait — and that is an interim for seventeen of the nineteen. RULED, DEFERRED, AND TRACKED HERE ON POUYA'S INSTRUCTION:** *"Record the trigger so it cannot quietly become permanent."* Q40, 2026-08-27. The portrait is the **decided** card for `/` and `/about/` — a face is the strongest social preview for a personal brand. It is the wrong card for the other seventeen, where a typed card carrying the page title does the work. **Removal trigger: build step 7**, where Insights needs per-article cards anyway — one generator (`satori` or `astro-og-canvas`, pinned against `npm view` that day per R11), one dependency, one review. Then delete the interim note from `docs/04` and the cutover line from `docs/06`. **Blocks cutover; does not block steps 3–6** | 2026-08-27 | Nobody on this project will ever see the defect. A link preview is rendered by LinkedIn, Slack and Teams for a reader who is not us, and `docs/04` requires a **unique** title and description per page — nineteen unique pages that all preview identically is the failure, and it is invisible from inside the repo. It costs nothing and works, which is exactly the R13 shape |
|
||
| R16 | **The one-page PDF bio does not exist, and it is deferred to build step 9 — not dropped. RULED AND TRACKED HERE ON POUYA'S INSTRUCTION:** *"Record the trigger so it doesn't become another quiet interim."* Q45, 2026-08-28. His reasoning: it is a **derived artefact**, so building it before `/about/` and `/fees/` are final means building it twice — and an appointment proposal needs the fee card as much as the bio. **Removal trigger: build step 9, alongside `/fees/`.** Two decisions travel with it and are **not** settled by the deferral: (a) generated at build (a dependency and an `npm audit` surface, against R11) or authored once as a designed artefact; (b) whether it carries anything the site does not — a matter list, a fee summary, referees — **each of which is a §4 question of its own**, and the matter list would collide with §4 Forbidden directly. Then delete `docs/01` §`/about/` item 7's pending note | 2026-08-28 | **It is the one artefact class this project's review apparatus cannot reach.** A web page is re-reviewed by every audit and re-checked by every build; a PDF circulated with an appointment proposal is read once, by the reader who matters most, and never seen by a reviewer again. `/about/` currently ships with no link to it, which is correct — a dead link on the page an appointing body reads is worse than the absence — and that means **nothing on the site will ever prompt anyone about this.** Only this row will |
|
||
| R17 | **THE DEPLOY KEY'S FIRST ROTATION IS DUE 2026-11-26, AND THAT DATE IS THE WHOLE ROW.** Access key for `adr-sml-deploy` created **2026-08-26**; D3 commits to **quarterly** rotation. Pouya's instruction when Q22 closed: *"Put the DATE in the R-series reminder, not the intention."* **Rotation procedure is in `docs/06-deployment.md` §Key rotation** — create the second key, update the Gitea secrets, verify a deploy, **then** delete the first; never delete before verifying, or the next push fails with no way to authenticate the fix. **Then set the next date here (2027-02-26) rather than deleting the row.** Also re-run **all nine** `simulate-principal-policy` checks after any policy edit (they are listed and reproducible in `docs/reference/deploy-credential-verification.md` §5) — the narrowness is the control (§10), and a widened policy is invisible from inside the repo. **The key is currently UNUSED — `AccessKeyLastUsed` returns `ServiceName`/`Region` = `N/A` and no `LastUsedDate`** — because deploys still run locally via `npm run deploy`; that does not pause the clock, and an unused long-lived key is exactly the one nobody remembers to rotate | 2026-08-28 | This is the reminder D3 has been waiting for a subject since 2026-08-26. §10 records the reason it matters more here than on a normal project: the secret lives on **jointly-administered** infrastructure, and the account also holds another business's client-database backups. A static key on shared infrastructure is only as safe as its age and its scope, and **nothing in the repo, the build, or AWS will prompt anyone on either.** §7 carries the inventory; this row carries the date |
|
||
| R18 | **THE SIX `docs/reference/` EXTRACTS BEHIND `/practice/*` ARE DATED 2026-08-29, AND SIX SHIPPED SENTENCES TURN ON FACTS THAT MOVE.** Build step 5 put statute, regulation, tribunal and bill status onto public pages — sourced, but **sourced as at one day**. The volatile ones, in order of how fast they move: **(a) federal Bill C-36** — `/practice/technology/` says it *"was introduced in June 2026 and was at second reading when this page was written"*; if it receives royal assent the page is wrong about the most load-bearing fact on it. **(b) the Ontario regulation under `Electricity Act` s. 28.1** — `/practice/energy/` says it *"had not been made as of August 2026"*. **(c) the ERO 026-0853 consultation**, comment period to **12 September 2026**. **(d) the Tribunals Ontario annual report** — `/practice/insurance/` publishes FY2024-25 figures and the extract records that a 2025-26 edition was never ruled out. **(e) the SABS**, amended with effect 1 July 2026. **(f) the ADRIC National Mediation Rules**, under review by ADRIC's own committee. **(g) ADRIC's Code of Ethics** — added 2026-08-30, build step 6. `/process/` §Confidentiality quotes it verbatim from `docs/reference/adr-institution-names.md` (retrieved 2026-08-29) **with a live link to ADRIC's page**, which is what makes it checkable and also what makes a stale quotation visible. It is the slowest-moving item here — a professional code, not a bill — so it does not change the cadence; it is listed because the trigger below says "all six" and there are now seven. **THE TRIGGER: re-check all seven extracts before any cutover, and before any republish that turns on one of them — the same event trigger R10 uses.** Then re-stamp the extract. **A page that was true when it was written and is false when it is read is still a false page**, and this is the first change set on the project to put that class of fact into public copy at volume | 2026-08-29 | Six sentences, six files, one retrieval date. Nothing here fires on its own; a fact with a shelf life and no owner is exactly what §12 exists for |
|
||
| ~~R7~~ | **RATIFIED / SUPERSEDED 2026-08-26.** (a) Cache-policy table matching the pipeline — **accepted**; documenting what the pipeline does beats documenting an intention. (b) `s3:AbortMultipartUpload` omitted — **accepted, reasoning corrected**: the lifecycle rule does not exist and is therefore not the cover; the actual cover is that `aws s3 sync` only goes multipart above 8 MB and the largest asset is a 357 KB portrait. Recorded in `docs/06-deployment.md` with a revisit trigger. (c) The `aws s3 ls` pre-flight — **superseded** by the variable guard now running as the workflow's first step | 2026-08-26 | — |
|
||
| ~~R8~~ | **PROMOTED TO A RULE 2026-08-26.** A reminder was too weak for a pattern that survived three entries. *A sweep is a command, not a claim* now sits in `CLAUDE.md` under Conventions, in `/build` Phase 6, and in `/wrap` step 3: any claim that a change was applied across files must cite the command and be written only after reading its output | 2026-08-26 | — |
|
||
|
||
---
|
||
|
||
# Change Log
|
||
|
||
## 2026-08-31 (ag) — Q58 and Q57 ruled and closed; §4's mediation row enumerates all six areas; `docs/03`'s compliance checklist stops paraphrasing §4 and cites it; and a derived fee term was struck from the one document that is the authority on money
|
||
|
||
**Four rulings from Pouya, plus what implementing them turned up.** Both of the
|
||
previous session's change sets are committed and pushed first, on his
|
||
instruction — `2ea4c0f` (the D20/Q55/Q56 rulings, 14 files, builds and passes on
|
||
its own at 12 pages) and `13b9784` (build step 6, 14 pages). The split was
|
||
prepared in the prior session and he ratified it: *"COMMIT AND PUSH both sets.
|
||
The split you prepared is correct."*
|
||
|
||
### Q58 — RULED, and Pouya attributed the ambiguity to his own document
|
||
|
||
*"The ambiguity is mine. My `docs/07` wording said 'up to 3.5 h, including 2 h
|
||
preparation', which is genuinely unclear: 3.5 was meant as the TOTAL time
|
||
committed, of which 2 is preparation — leaving 1.5 hours in the room. Your
|
||
arithmetic caught it: if prep sat inside, 3.5 and 7 wouldn't be exactly 2×,
|
||
because preparation doesn't scale with session length. The intended reading is
|
||
the market's, and my wording obscured it."*
|
||
|
||
The card now reads, in his words: **half day — up to 3 hours of session, fee
|
||
includes up to 2 hours of preparation, $2,000; full day — up to 6 hours of
|
||
session, up to 3 hours of preparation, $4,000.** His reason for 3 and 6 is the
|
||
market convention, and **`docs/07`'s own research table corroborates it** — which
|
||
is why the corroboration is recorded there rather than asserted: Patey publishes
|
||
3 h / 6 h in both tiers, Zuber 3 h video and 6 h full day, and ADR Chambers'
|
||
roster rate covers *"one half hour of preparation time per party **and** up to
|
||
three hours of mediation"*, preparation counted separately from a three-hour
|
||
session.
|
||
|
||
⚠️ **One provenance note, under R14 rather than as a doubt about the ruling.** He
|
||
recalled Patey and Zuber as publishing *"all or part of 3 hours"*. The committed
|
||
extract records their **hours** and not that phrase, so `docs/07` cites the hours
|
||
and the phrase is attributed to nobody. The hours carry the point on their own.
|
||
|
||
**Two things fell out of the ruling that the instruction did not name, and both
|
||
were defects rather than extensions.**
|
||
|
||
**(a) `docs/07` §All parameters confirmed was prescribing the flat form** —
|
||
*"must be stated on the page — 'including 2 hours of preparation'"*. That is the
|
||
sentence `/for-parties/` was built against, so **the spec was generating the
|
||
defect the same spec elsewhere forbids.** Corrected to require the cap: *"in
|
||
hours AND AS A CAP"*.
|
||
|
||
**(b) The cap had to reach the copy.** `/for-parties/` shipped *"including 2
|
||
hours of preparation"* — a flat entitlement where the allowance is capped. Now
|
||
*"including up to 2 hours of preparation"*. The session length also returned to
|
||
the page, interpolated from `FEES` rather than typed; it had been removed for one
|
||
build **only** because Q58 was open.
|
||
|
||
`FEES.mediation.*.hours` is corrected 3.5 → 3 and 7 → 6 and now means the
|
||
session. **It had no consumer in `src/` when the question was open**, which is
|
||
the only reason no page was ever wrong. `/fees/` is unblocked for step 9 on the
|
||
question Q58 asked.
|
||
|
||
### Q57 — CLOSED, and a closure is not a deferral
|
||
|
||
*"`/process/` stating when conflicts are run and what the check needs is
|
||
complete. A reader assumes the outcome, and the obvious undertaking ('if a
|
||
conflict is found I decline') adds nothing a reader doesn't already infer. Your
|
||
restraint was right — §4's gate held. Record it closed rather than open, so it
|
||
stops appearing in the live list."*
|
||
|
||
The answer is one of the two the question offered: the page says nothing further.
|
||
§4 gains no seventh undertaking; `CONDUCT_UNDERTAKINGS` still holds six. The
|
||
`TODO(pouya)` is replaced by the ruling at the place the question was, and **`src/`
|
||
now carries zero live `TODO(pouya)` markers.**
|
||
|
||
### §4's mediation row — all six areas, and the hedge struck
|
||
|
||
*"The register should match the site; 'illustrative' is a hedge covering a gap
|
||
that has a correct value. Technology and energy go in."*
|
||
|
||
Q56's ruling had named five, which was **four of the six areas plus the word
|
||
*commercial*** — a scope descriptor, not a seventh area. The row is now the
|
||
site's own six (construction, technology, energy, insurance, shareholder,
|
||
cross-cultural) and a reader comparing register against site finds them equal.
|
||
The six-area fact is stamped `[verified 2026-08-31 — Pouya]` against the row's
|
||
2026-08-26 opening stamp, on the split-stamp device this register ratified for
|
||
Q.Arb.
|
||
|
||
**The vocabulary sweep found the same hedge in `docs/03`**, which a
|
||
subject-anchored sweep would have missed:
|
||
|
||
```
|
||
$ git grep -n 'illustrative of breadth\|illustrative, not a closed' -- docs/ src/ AGENTS.md CLAUDE.md .claude/
|
||
AGENTS.md:1367:pages. The row now says the list is **illustrative of breadth, not a closed
|
||
docs/03-content-spec.md:101: matters"* — is **illustrative of breadth, not a closed set**: the site
|
||
```
|
||
|
||
`AGENTS.md:1367` is entry (ae) — append-only history, correctly left. `docs/03`
|
||
was live instruction and was corrected.
|
||
|
||
### `docs/03`'s compliance checklist — a structural fix, on the third instance
|
||
|
||
*"The checklist paraphrases §4 rows and drops qualifiers… Every time, the
|
||
checklist is what gets grepped and §4 is what's correct. So: the checklist must
|
||
CITE the §4 row, not restate it. Same single-source rule as §7 and operational
|
||
facts."*
|
||
|
||
Every item that bars something now names **what to look for on the page** and
|
||
**which §4 row decides it** — never the bar's own wording — and names the
|
||
`check:claims` pattern that sweeps `dist/` for it where one exists. **Item count
|
||
is unchanged: 12 before, 12 after.** This is a structural fix and deliberately
|
||
not a coverage change; the same discipline the frozen `check:claims` is under.
|
||
|
||
The three instances, all caught by review and never by the checklist, and in each
|
||
case §4 was right: *"no dollar figures"* for §4's *"attached to **past
|
||
matters**"*, which read as forbidding the rate card D8 commits to; *"no
|
||
testimonials"* for §4's bar on endorsements **of the practice or of Pouya**,
|
||
which read as forbidding the institutional quotations `docs/01` directs; and the
|
||
licence-capacity item, which unscoped rejected the exact sentence the section
|
||
above it exists to bless.
|
||
|
||
### An argument for the freeze, recorded because Pouya asked for it
|
||
|
||
*"That is twice the freeze has forced a copy change and twice the replacement was
|
||
better. Record that, it is an argument for the freeze."*
|
||
|
||
Both on `/med-arb/` and `/for-parties/`, `check:claims` failed the build on copy
|
||
that was **compliant on §4's wording** — *"my client"* used of a party, and five
|
||
uses of *"lawyer"* about the **reader**. There is no allowlist and the freeze
|
||
bars narrowing a pattern, so the copy moved instead. *"our client"* is better
|
||
than *"my client"* on a neutral's site whatever §4 says, and *"Should I get my
|
||
own legal advice?"* is better than *"Do I need my own lawyer?"* on the page
|
||
written for a party without one. **A tripwire slightly wider than the rule it
|
||
guards produces better copy at the cost of an argument you have to win twice.**
|
||
Narrowing it would have produced worse copy and a looser instrument.
|
||
|
||
### Ratified as shipped
|
||
|
||
The `/process/` contrast fix and its load-bearing `:not(.btn)`; the unrowed
|
||
terms-of-appointment claim replaced with the sourced ADRIC obligation; the
|
||
`/practice/` *"in commercial matters"* scoping breach; and the gloss lens's
|
||
fourth catch — the *"one sentence"* completeness claim, where the cited source
|
||
supplied its own counter-example.
|
||
|
||
### The review — two rounds, thirteen findings, all applied
|
||
|
||
`adversarial-reviewer` only, per D20. `claims-auditor` did **not** run and must
|
||
not until cutover. **Stopped at two rounds under D19**, and the cap is not
|
||
laxness: round 2 found five defects and **three of them were in round 1's own
|
||
fixes**, which is the measured reason round 2 exists — and past two the
|
||
manufacture rate exceeds the value of the marginal finding.
|
||
|
||
**Round 1 — seven findings, and three were mine to own.**
|
||
|
||
**(a) The sweep failure, and it is R8's sharpest edge committed two commits after
|
||
writing it into `CLAUDE.md`.** This change set wrote *"the preparation allowance
|
||
is CAPPED and must be published as capped"* into `docs/07` and applied it to one
|
||
surface. Three restatements still carried the flat or uncapped form:
|
||
`/mediation/` shipped *"with the preparation time bundled into each one stated
|
||
rather than folded into the hours"* — the *"preparation included"* form the new
|
||
rule bars, **in different words, so grepping the barred strings could never reach
|
||
it** — and its second clause described a distinction the corrected card no longer
|
||
draws; `site.ts` quoted a `docs/07` sentence that Q58 had just deleted; and
|
||
**§9's Q15/Q16/Q17 row prescribed the flat form**, which is what a later
|
||
implementer building `/fees/` reads. All three corrected.
|
||
|
||
**(b) A derived fee term asserted as applied fact in the document this file calls
|
||
the authority on money.** *"The overtime rate begins after 3 h and 6 h of session
|
||
respectively"* is nowhere in Pouya's ruling, nowhere in the card, and nowhere in
|
||
Q15–Q17's answer. Struck, and opened as **Q59**. `CLAUDE.md`'s rule for a fact we
|
||
do not have is a question, not an inference — and `/fees/` had just been declared
|
||
unblocked to publish from it.
|
||
|
||
**(c) The ruling struck less than the implementation did.** Pouya replaced
|
||
*"illustrative"* with a correct value; the clause saying the six are **not** the
|
||
authorised subject-matter list went with it, in both files. That would have
|
||
withdrawn the register's support from `/practice/cross-cultural/`'s shipped
|
||
*"commercial mediations and arbitrations"*, left deliberately on the recorded
|
||
ground that Q35(c)'s class is open. Restored, and the gate noted as not spent by
|
||
having been used six times.
|
||
|
||
The other four: `/for-parties/` measured the session cap *"in the room"* two
|
||
sentences after telling a party they may never be in the same room as the other
|
||
side — `docs/07` uses a format-neutral noun for exactly that reason and the page
|
||
had not carried it over; the cost answer dropped *"of preparation"* from its
|
||
second half, where the number collides with the new session figure; the page
|
||
stated a cap with no consequence, disclosing neither overtime nor the
|
||
additional-party fee; and **D19 — 40 comment lines in `src/` for 4 functional
|
||
lines**, roughly 13 of them pure revision history.
|
||
|
||
**Round 2 — five findings and one `consider`, and the sharpest was arithmetic.**
|
||
|
||
**⚠️ THE ARITHMETIC IN ROUND 1's OWN FIX WAS WRONG, AND WRONG IN THE DIRECTION
|
||
THAT UNDERSTATED THE THING IT EXISTED TO ESCALATE.** The Q59 note generalised the
|
||
full-day route as `500n + 1000` for all `n ≥ 3`. **The route is flat $4,000 until
|
||
hour 6**, so the formula was valid only from 6 h and the stated spread — *"$500
|
||
cheaper at every length"* — was wrong across the whole 3–6 h band. The real
|
||
spread is **$2,000 at three hours, narrowing to $500 from six on: up to four
|
||
times larger, and largest exactly where a half-day booking overruns.** The
|
||
document's own table contradicted the formula three lines above it. Pouya was
|
||
being asked to rule on whether the half/full step is a choice, on a number wrong
|
||
in the direction that makes it look like one. *A formula is an instrument, and a
|
||
measurement is a claim about your instrument.* The claim that the envelope
|
||
trigger is *"worse, not better"* was also half wrong: it is worse at six hours
|
||
and closes to **zero** from nine.
|
||
|
||
**And round 1's fix for the missing consequence supplied the very term Q59 says
|
||
must not be inferred.** Publishing *"Overtime is $500 an hour"* on a page that
|
||
now states an unambiguous *"up to 3 hours"* **defines the trigger by adjacency** —
|
||
there is no other quantity on the page for the charge to attach to, and the
|
||
answer travels alone into the `FAQPage` node where no context follows it. Under
|
||
the envelope reading a fourth hour carries nothing, so the inference makes a
|
||
party **over-state their own exposure by $500**. Same shape as D20's `/med-arb/`
|
||
ADRIC gloss: no sentence false, the defect is adjacency. **The rate came off the
|
||
page.** It now names the charge without its rate and without its trigger, and
|
||
Q59's Blocks column — which had asserted the page *"publishable as it stands"*,
|
||
closing the question against the page before Pouya read it — now names
|
||
`/for-parties/` as blocked.
|
||
|
||
**Round-1 finding (a) recurred inside its own fix.** The half/full anomaly was
|
||
assigned to R5's 12-month review **twice** and written into neither place R5
|
||
lives: not into `docs/07` §Recorded dissent — the section whose stated purpose is
|
||
*"so the 12-month review has something to test against"* — and not into §12's R5
|
||
row. Both now carry it, with the corrected table.
|
||
|
||
Also: `/mediation/`'s swept sentence claimed a disclosure it did not make — *"each
|
||
including a capped amount of preparation time, stated in hours"*, under a heading
|
||
reading **"Published in full"**, with no hours anywhere on the page, and it leaked
|
||
`docs/07`'s internal publication rule onto a public page. It now states the hours,
|
||
interpolated. And the D19 fix **did not land**: 39 comment lines for 7 functional
|
||
lines, a net reduction of one, including a block in `/for-parties/` restating the
|
||
one three lines above it, and a comment calling the overtime and additional-party
|
||
figures **"§4-publishable"** when they are D14/`docs/07` and `docs/03`'s own new
|
||
checklist item says in terms that no §4 row reaches the rate card. Folded, trimmed,
|
||
and the authority corrected.
|
||
|
||
The `consider` was taken: *"hours of session"* is an undefined unit on the page
|
||
`docs/01` requires to carry no jargon, and the page defines its other term of art.
|
||
It now reads *"up to 3 hours of mediation, a full day up to 6 hours"* — ADR
|
||
Chambers' own noun, quoted in `docs/07`, and the elided unit restored.
|
||
|
||
**Nothing was declined.** All thirteen findings and the `consider` were applied.
|
||
|
||
### Two things found by running a check rather than reading a row
|
||
|
||
**§7's TypeScript hold named one gate and there are two.** R11's check at the
|
||
step 6 → 7 boundary: 13 of 14 pins current, TypeScript the only hold.
|
||
`npm view typescript-eslint peerDependencies` returns
|
||
`{ typescript: '>=4.8.4 <6.1.0' }`, **tighter** than `@astrojs/check`'s
|
||
`^5.0.0 || ^6.0.0` — so the recorded removal trigger, *"`@astrojs/check` widens
|
||
the range to include 7"*, was **unreachable**: widening it alone would not lift
|
||
the hold. And the pin is a caret, so a future 6.1.x would move the tree into a
|
||
peer-range breach on a plain `npm install`, with nothing in the repo saying so.
|
||
Nothing is breached today: `npm ls typescript` resolves **6.0.3**, the highest
|
||
stable 6.x. Both gates are now named and the trigger requires both.
|
||
|
||
**`struck-universal-q39` is enforced on `dist/` and has no §4 row.** The bar
|
||
lives only in `scripts/check-claims.mjs` and in Q39's §9 entry, so the rewritten
|
||
`docs/03` checklist has nothing to point at and **deliberately does not carry a
|
||
line for it** — writing the bar into the checklist is the exact failure mode the
|
||
rewrite was for. Surfaced to Pouya rather than fixed: which side it gets fixed on
|
||
is his call, and it gates nothing today, so it is a note and not a numbered
|
||
question (D19).
|
||
|
||
### Verified — commands run, exit statuses read, never through a pipe
|
||
|
||
```
|
||
npm run check exit 0 0 errors / 0 warnings / 0 hints (34 files)
|
||
npm run lint exit 0
|
||
npm run build exit 0 14 pages
|
||
npm run check:claims exit 0 11 patterns, self-test clean
|
||
npm audit exit 0 0 vulnerabilities
|
||
minifier tripwire exit 1 (clean — no `animation` shorthand beside a timeline)
|
||
```
|
||
|
||
Also measured on `dist/`, not asserted: **zero `.js` files and zero `client:*`
|
||
directives**, so every page renders in full with JavaScript disabled; one `<h1>`
|
||
per page across all 14; unique title (50–60) and description (143–160) on every
|
||
page; canonical, 10 Open Graph and 5 Twitter tags on every page; all JSON-LD
|
||
parses, and `/for-parties/`'s `FAQPage` answers are byte-identical to the visible
|
||
copy because both come from one array. **Five distinct dangling internal links** —
|
||
`/contact/`, `/fees/`, `/insights/`, `/legal/privacy/`, `/legal/terms/` — all
|
||
pages on the build order not yet built, unchanged by this change set.
|
||
**Lighthouse: NOT RUN — tool unavailable.** `@lhci/cli` returns at step 7.
|
||
|
||
### The sweeps, with the commands and their output
|
||
|
||
```
|
||
$ git grep -n 'illustrative of breadth\|illustrative, not a closed' -- docs/ src/ AGENTS.md CLAUDE.md .claude/
|
||
AGENTS.md:1367:pages. The row now says the list is **illustrative of breadth, not a closed
|
||
docs/03-content-spec.md:105: "commercial", and this block called the list "illustrative of breadth, not a
|
||
```
|
||
|
||
`AGENTS.md:1367` is entry (ae) — append-only, correctly untouched. `docs/03:105`
|
||
is the labelled historical note that replaced the live instruction.
|
||
|
||
```
|
||
$ git grep -c 'TODO(pouya):' -- src/
|
||
(exit 1 — no matches)
|
||
|
||
$ awk '/^## Compliance checklist/,0' docs/03-content-spec.md | grep -c '^- \[ \]'
|
||
12 # HEAD: 12. Structural fix, not a coverage change.
|
||
```
|
||
|
||
⚠️ **And the sweep that mattered was the one round 1 caught me not running** — the
|
||
capped-form rule, swept by its **vocabulary** rather than by the barred strings,
|
||
because `/mediation/`'s breach used none of them.
|
||
|
||
---
|
||
|
||
## 2026-08-30 (af) — Build step 6: `/process/` and `/for-parties/`, the first step under D20 — and the frozen `check:claims` failed the build on compliant copy, which is the freeze working
|
||
|
||
**Two pages, 14 in `dist/` (was 12), zero JavaScript, one `<h1>` each, no skipped
|
||
heading levels.** The rulings they were built under are entry (ae) below.
|
||
|
||
**Reviewed by `adversarial-reviewer` only — D20, first application.**
|
||
`claims-auditor` was **not** run; it runs once, at cutover. Saying which agent
|
||
ran is now required by `/build` Phase 3, because "reviewed" reads as both.
|
||
|
||
### `/process/` — the shape of an engagement
|
||
|
||
`PROCESS` and `PROCESS_FRAMING` rendered from `src/data/site.ts`, so `/` and
|
||
`/process/` cannot drift on the five timings. **Q43's framing sits directly under
|
||
the last step**, not in the section lede — verified in the built bytes, not
|
||
asserted: the sentence follows *"Day 30 onward · Minutes of settlement — or an
|
||
award"* with nothing between them.
|
||
|
||
Conflicts, confidentiality and the non-settlement outcome are the three things
|
||
`docs/01` requires beyond the steps. Two of the three close with a **conduct
|
||
undertaking rendered from the constant**, never retyped — (d) on confidentiality
|
||
and (a) on the switch — and §4's "Where it ships" column is updated for both.
|
||
|
||
### The third one stops early, and the stop is the point — Q57
|
||
|
||
`/process/` §Conflicts says **when** the check runs and **what it needs**. It does
|
||
not say what happens when one turns something up, because **that sentence would
|
||
be a seventh conduct undertaking** and §4's gate for that class is one line:
|
||
*"an undertaking may be published only where Pouya has made it in terms. Not
|
||
'would obviously agree to', not 'follows from the process' — said."*
|
||
|
||
*"If a conflict appears I decline the appointment"* is exactly what that gate
|
||
refuses to let this repository infer, however obvious it looks. `TODO(pouya)` in
|
||
the source, **Q57** in §9. One sentence from him closes it.
|
||
|
||
### `/for-parties/` — and it is the page `docs/03` warns about
|
||
|
||
The one page in the second person. `NEUTRAL_ROLE_LINE` gets **its own section
|
||
above the questions** rather than a slot inside them: `docs/03` requires this
|
||
page to say it explicitly, and the sentence a party most needs is not one to make
|
||
them scroll for.
|
||
|
||
Eight questions, written as questions a party actually asks, so `FAQPage` is
|
||
honest — `docs/04` allows the node here *"only where the visible page genuinely
|
||
is Q&A"*. **One array feeds both the visible page and the node**, so a question
|
||
cannot enter the structured data without appearing on the page. The caucus
|
||
undertaking renders through `<Undertaking>` visibly and is joined into the
|
||
answer text for the node, which is plain text by schema — one source, two shapes,
|
||
neither typed twice. **Fee figures are interpolated from `FEES`**, so the page a
|
||
party reads cannot drift from D14's card.
|
||
|
||
**Reading level, measured rather than claimed, and the instrument checked both
|
||
ways.** `docs/03` requires grade 9. A syllable heuristic that **undercounts**
|
||
(it merges `ia`/`io` and eats `-le`) returns Flesch–Kincaid **4.5**; one
|
||
corrected to split those vowel groups **overcounts** and returns **4.9**. Both
|
||
bracket the true value well under the requirement, and the syllable-independent
|
||
metric agrees: **9.6 words per sentence** in `<main>`, longest sentence 36 words.
|
||
Reported as a range because a single estimate here would be a claim about the
|
||
counter.
|
||
|
||
### `check:claims` failed the build on compliant copy, and the copy moved
|
||
|
||
The page shipped *"Do I need my own lawyer?"*, *"coming without a lawyer"* and
|
||
*"you are not a lawyer"* — every one of them about the **reader**. §4 bars the
|
||
word *used of Pouya*, so all three are compliant on the register's own wording.
|
||
**`licensure-of-pouya` failed the build on five matches anyway**, because a bare
|
||
`\blawyer\b` cannot tell whose.
|
||
|
||
**The copy moved, not the gate**, and there were three reasons rather than one:
|
||
|
||
1. **There is no allowlist.** `mustNotMatch` fixtures only assert in the
|
||
self-test that a pattern stays silent on approved strings; they are **not**
|
||
applied when scanning `dist/`. Adding one would not have unblocked the build
|
||
— it would have made the self-test fail instead. Worth recording, because
|
||
"add it to the approved list" is the obvious first move and it does not exist.
|
||
2. **The precedent runs this way.** When `/med-arb/` shipped *"the neutral who
|
||
heard my client in caucus"* — counsel's voice, not Pouya's — the copy changed
|
||
to *"our client"* and the pattern widened. Same shape, same call.
|
||
3. **The freeze.** Narrowing `\blawyer\b` to exclude reader-owned uses is a
|
||
refactor of the strongest pattern on the site, on the page `docs/03` names as
|
||
where the barred phrasing is most tempting. That is the coverage work the
|
||
freeze bars.
|
||
|
||
The replacements are better copy, which is the part worth noting: *"Should I get
|
||
my own legal advice?"* uses `NEUTRAL_ROLE_LINE`'s own wording, and the hero lede
|
||
went from *"you are not a lawyer"* to *"nobody has explained what one is"* —
|
||
which targets the need rather than the reader's credential. The constraint is
|
||
recorded in the page header so the next editor does not re-introduce it.
|
||
|
||
### Two dangling internal links closed, on every page
|
||
|
||
`SECONDARY_NAV` in `src/data/site.ts` has linked `/process/` and `/for-parties/`
|
||
from the footer since step 1, and neither page existed. **Every one of the 12
|
||
previously built pages therefore shipped two broken internal links.** `site.ts`
|
||
is unchanged in this change set — the pages simply arrived. All internal links
|
||
now resolve except `/contact/`, `/fees/`, `/insights/` and `/legal/*`, which are
|
||
build steps 7–10.
|
||
|
||
### Structured data
|
||
|
||
`/process/` emits **`Person` only** — a new `pageGraph()`, which
|
||
`practiceIndexGraph()` now delegates to. **No `Service` node, deliberately**: the
|
||
five timings are publishable only under Q43's framing sentence, and a `Service`
|
||
node would carry the numbers into a field where no framing travels with them.
|
||
`/for-parties/` emits `Person` + `FAQPage`; `faqNode()` is factored out and
|
||
`medArbGraph()` now calls it instead of carrying its own copy of the mapping.
|
||
|
||
### R11 at the step 5 → 6 phase boundary — same one pin, same recorded reason
|
||
|
||
`npm view` run across all fourteen pins, exit status read. **Thirteen are
|
||
current.** `typescript` is pinned `^6.0.3` against a latest of `7.0.2` — the same
|
||
deliberate hold recorded at the step 4 → 5 boundary, and the trigger was
|
||
**re-verified rather than recalled**:
|
||
|
||
```
|
||
$ npm view @astrojs/check@0.9.10 peerDependencies
|
||
{ typescript: '^5.0.0 || ^6.0.0' }
|
||
```
|
||
|
||
`astro check` is the type gate both deploy paths run, so the hold stands.
|
||
**Removal trigger unchanged: `@astrojs/check` widens the range.** A hold on a
|
||
dependency's schedule, not on a judgement.
|
||
|
||
### The code review — 9 findings, 2 blocking, all accepted
|
||
|
||
`adversarial-reviewer` only, per D20. **`claims-auditor` was not run.**
|
||
|
||
**BLOCKING 1 — a body link shipped at 1.88:1, which is worse than the defect this
|
||
project treats as canonical.** `/process/`'s Code-of-Ethics link sits on
|
||
`.section-inverse` and inherited the global `a { color: var(--link) }` —
|
||
`--maroon-l`, a token whose own comment says *"links on cream 8.95:1"*. Nothing
|
||
overrode it for a dark ground. **Measured independently before acting**, and the
|
||
instrument was validated by reproducing three documented values exactly (8.95:1
|
||
maroon-l on cream, 11.09:1 gold-l on ink, 16.81:1 cream on ink):
|
||
|
||
```
|
||
1.88:1 --link (maroon-l #7a2a2c) on --bg-inverse (ink #1a1614)
|
||
1.10:1 :hover (maroon-d #3d1112) on the same ground
|
||
```
|
||
|
||
`CLAUDE.md` records gold-on-cream at **2.10:1** as the thing that must never
|
||
ship. This was worse, on hover by a factor of two. **`/process/` is the site's
|
||
first body link on a dark band** — `SiteFooter` colours its own, which is the
|
||
only reason the hole had never opened. Fixed in `global.css` beside the
|
||
`:focus-visible` rule that exists for exactly this reason, not in the page.
|
||
|
||
**And the `:not(.btn)` in that fix is load-bearing, not decoration.**
|
||
`.section-inverse a:not(.btn)` has specificity (0,2,1); `.btn-gold[data-astro-cid]`
|
||
has (0,2,0). Without the exclusion the new rule would have **overridden every
|
||
gold button on an inverse ground**, which is the repair introducing a second
|
||
defect — the exact shape `/build` Phase 4 exists to catch. Verified after the
|
||
fix by enumerating every non-`.btn` anchor inside any `.section-inverse` or
|
||
`.section-accent` across all 14 built pages: **one, and it is this link.**
|
||
|
||
**BLOCKING 2 — the fee shipped as "with preparation included", which `docs/07`
|
||
forbids in terms.** *"Preparation time is bundled and **must be stated on the
|
||
page** — 'including 2 hours of preparation'… **Do not quietly fold it into the
|
||
hours figure.**"* The allowance is **capped**, so the unqualified form sells an
|
||
uncapped one, to the reader least able to check it — and `/mediation/` already
|
||
ships the promise that the site does the opposite. `grep -n prepIncluded src/`
|
||
returned **only the declaration**: the constant existed for this exact sentence
|
||
and had no consumer anywhere. Now interpolated on both figures.
|
||
|
||
**And one finding I could not resolve, so it became Q58 rather than a guess.**
|
||
`docs/07`'s card reads *"Half day — up to 3.5 h, **including** 2 h
|
||
preparation"*, which makes 3.5 the **billed envelope** and the time in the room
|
||
**1.5 h**. Against that: 3.5 and 7 are exactly 2×, which they would not be if
|
||
preparation sat inside them. One of the two is wrong, and a draft of
|
||
`/for-parties/` had already answered *"What happens on the day?"* with *"A half
|
||
day is about 3.5 hours"* — the envelope presented as the day. **The sentence was
|
||
removed, not reconciled**; the page now says only that you book a half day or a
|
||
full day. `site.ts`'s `hours` field carries a warning against publishing it as a
|
||
duration. **`/fees/` at step 9 cannot be built without the answer.**
|
||
|
||
**The other six, all accepted:**
|
||
|
||
1. ***"on this it is one sentence"* was a completeness claim about a third
|
||
party's Code that the cited artefact contradicts.** The extract is a scrape
|
||
of one web page carrying three quoted lines, and **eighteen lines above** it
|
||
records a separate instrument — ADRIC's **Code of Conduct for Mediators** —
|
||
bearing on the same subject. The source cited supplied the counter-example.
|
||
Fourth instance of the named gloss pattern, after the LAT ellipsis, the IESO
|
||
"connection allocation" and the `/med-arb/` ADRIC gloss — **and the first one
|
||
caught before shipping.** Now reads *"and it says:"*.
|
||
2. **"Caucus" was undefined jargon on the one page whose spec bars jargon.** Used
|
||
twice, never defined; §11 has no entry; `/mediation/` — the *counsel*-facing
|
||
page — actually glosses it and `/for-parties/` did not. Glossed in the page
|
||
copy, **never inside `CONDUCT_UNDERTAKINGS.mediationCaucus`**. Note the
|
||
measurement's blind spot: Flesch–Kincaid put the page at grade 4–7, well
|
||
inside the grade-9 requirement, **because the formula cannot see a single
|
||
unfamiliar noun.** A reading-level score is not a jargon check.
|
||
3. **`docs/01` still instructed *"not your lawyer"*** — struck in `docs/03` on
|
||
2026-08-28 with a two-point explanation, and the sweep never reached
|
||
`docs/01`. **This change set edited `docs/01` and did not fix it.** The page
|
||
avoided the trap; the spec that directs the page did not. Replaced with a
|
||
pointer to `NEUTRAL_ROLE_LINE` and the struck forms.
|
||
4. **§4 undertaking row (d) recorded two surfaces and there are three** —
|
||
`/for-parties/` publishes it visibly and inside the `FAQPage` node. An
|
||
incomplete "where it ships" on the one class Pouya flagged as failing
|
||
*silently* is that column doing the opposite of its job.
|
||
5. **`/process/` hand-typed the ADRIC membership.** Character-identical to
|
||
`MEMBERSHIP_ORGS[0]`, and R10's re-confirm trigger sweeps the constants, not
|
||
the pages — so after a lapse this page would have kept asserting it. The OCNI
|
||
shape exactly. Now interpolated, and R10 records the third surface.
|
||
6. **`practiceIndexGraph` had become a pure alias** — one caller, zero
|
||
behaviour, 13 lines of comment over 3 lines of code, and the comment's
|
||
reasoning is about `/practice/` rather than about graph shape. My churn from
|
||
an hour earlier. Deleted; `practice.astro` imports `pageGraph` and the
|
||
reasoning now sits beside the call that makes the decision.
|
||
|
||
### One defect I introduced while fixing them, and what caught it
|
||
|
||
Removing the duration turned a template literal into a plain string — **but I
|
||
replaced the closing backtick and left the opening one**, so the frontmatter
|
||
fence broke and TypeScript read the rest of the file as one string. **`astro
|
||
check` returned exit 1 with 50 errors**, and both deploy paths run `check` before
|
||
`build`, so nothing could have shipped. Recorded because it is the case
|
||
`CLAUDE.md`'s truncation rule is about from the other side: the verdict was read
|
||
as an **exit status**, not as the tail of a pipe.
|
||
|
||
### Two limits on this pass, stated rather than omitted
|
||
|
||
- **Lighthouse: not run — tool unavailable.** `@lhci/cli` removed 2026-08-26,
|
||
returns at step 7 under R11.
|
||
- **Mobile layout at 390px: not measured.** Headless Chrome lays out at a wider
|
||
viewport and crops to the requested width; the reviewer validated that by
|
||
checking already-reviewed pages clip identically, so the clipping is the
|
||
instrument rather than the pages. Element-level widths at 390px remain
|
||
unmeasured and need a real driver — `puppeteer` is not installed, only an
|
||
empty `node_modules/@puppeteer` directory exists.
|
||
|
||
### And a sweep caveat worth keeping
|
||
|
||
**`git grep` silently misses untracked files.** Both new pages were untracked for
|
||
the whole of this build, so any `git grep` across step 6 returned a clean result
|
||
that meant nothing. Use plain `grep -rn` until the files are staged. Same family
|
||
as R8: a real command, read honestly, and the wrong command.
|
||
|
||
### And working the `docs/03` checklist against the pages found the checklist wrong
|
||
|
||
Not a review finding — this came from actually running the compliance checklist
|
||
rather than assuming it. Item 2 read *"No matter counts, settlement rates,
|
||
**dollar figures**, or time-to-award stats"*, and `/for-parties/` is **the first
|
||
page on the site to publish a fee** (`grep -roh '\$[0-9][0-9,]*' dist` returns
|
||
`$2,000` and `$4,000`, both on that page and nowhere else). Read literally, the
|
||
checklist forbade the page `docs/01` commits to and the rate card D8 commits to.
|
||
|
||
**§4's own row was never wrong** — it reads *"Aggregate value resolved; any
|
||
dollar figure attached to **past matters**"*. The checklist **dropped the
|
||
qualifier when it mirrored it**, which is `CLAUDE.md`'s duplicated-fact rule
|
||
exactly: the copy that goes stale is the one nobody re-reads. Item scoped, with
|
||
§4's wording cited rather than restated.
|
||
|
||
**Third instance of an unscoped checklist line flagging the copy the spec
|
||
requires** — the other two are the testimonials item and the capacity-phrasing
|
||
item, both corrected the same way, and `docs/03` records that the checklist *"is
|
||
what gets grepped"*.
|
||
|
||
### Verification — exit statuses read directly, never through a pipe
|
||
|
||
```
|
||
npm run check exit 0 0 errors / 0 warnings / 0 hints (34 files)
|
||
npm run lint exit 0
|
||
npm run build exit 0 14 pages
|
||
npm run check:claims exit 0 11 patterns, 26 approved strings, 14 pages
|
||
npm audit exit 0 0 vulnerabilities
|
||
```
|
||
|
||
Also run and read: the minifier trap (`grep -rE 'animation:[^;}]*(scroll\(\)|
|
||
view\(\))' dist --include='*.css'` → **exit 1, no match**); a secret scan whose
|
||
**own** exit status was read rather than a pipeline's (**exit 1, no match** —
|
||
the first attempt piped through `head` and reported `head`'s status, which is
|
||
the failure `CLAUDE.md` names); all 14 pages for one `<h1>`, no skipped heading
|
||
levels, canonical, OG/Twitter, JSON-LD parse, and title/description inside
|
||
50–60 / 140–160 (**14/14 in band, all unique**); every internal link resolved
|
||
except `/contact/`, `/fees/`, `/insights/` and `/legal/*`, which are steps 7–10;
|
||
zero `client:*` directives and zero non-JSON-LD `<script>` on either new page.
|
||
|
||
**`PROCESS_FRAMING` verified in the shipped bytes**, not asserted: it follows
|
||
*"Day 30 onward · Minutes of settlement — or an award"* with nothing between.
|
||
|
||
### And the `set -- $pair` bug recurred, in the direction that is dangerous
|
||
|
||
`CLAUDE.md` records a zsh digest-comparison loop that printed **`DIFFER` on all
|
||
five rows** because `set -- $pair` gave the loop body one argument. The same loop
|
||
shape was used here to confirm nine files matched a saved copy, and it printed
|
||
**`same` on all nine** — a uniformly *good* result from a comparison that never
|
||
ran. `shasum` was invoked as `shasum -a 256 "AGENTS.md AGENTS.md"`, errored, and
|
||
left **both** variables empty, so `[ "$a" = "$b" ]` compared `""` to `""` and
|
||
passed.
|
||
|
||
**The `DIFFER` version announces itself; this one does not.** "Uniformly bad"
|
||
gets re-checked because it is alarming. **"Uniformly good" is what you were
|
||
hoping for, and it ends the check.** Re-run in Python with an `os.path.isfile`
|
||
assertion on both sides — the step the shell loop skipped — and the nine files
|
||
are genuinely byte-identical. Add to the sweep discipline: **a comparison must
|
||
assert that both things it compares exist.**
|
||
|
||
---
|
||
|
||
## 2026-08-30 (ae) — D20 moves the claims pass to cutover; Q56 rules mediation UNSCOPED and records why the asymmetry with arbitration is designed; Q55 is closed without being resolved; and `check:claims` is frozen
|
||
|
||
**Three rulings and two conventions, all Pouya's, recorded in one entry because
|
||
they were one directive.** Build step 6 was run under them the same day and is recorded in its own entry.
|
||
|
||
### D20 — the per-step claims audit stops, and this must read as calibration
|
||
|
||
**New locked decision. `claims-auditor` runs ONCE, at cutover, over the whole
|
||
finished site.** Per step it is `adversarial-reviewer` alone, two rounds max
|
||
under D19. `npm run check:claims` is **unchanged** and still runs on every build
|
||
and both deploy paths. Pouya reads the copy as it is built; that is the human
|
||
pass.
|
||
|
||
**His reasoning, recorded in full in §3 D20 rather than summarised here**, because
|
||
"we stopped running the compliance check" is the kind of sentence a later reader
|
||
has to be able to weigh:
|
||
|
||
- **Nothing has shipped.** Every claims finding to date has been about a page no
|
||
visitor can reach — the entire risk is deferred to cutover already, and
|
||
auditing nine build steps then re-auditing the fixes is auditing a draft
|
||
nobody can read.
|
||
- **One pass over twenty finished pages catches MORE than nine over drafts**,
|
||
because it sees the site as a reader does. The `/med-arb/` ADRIC gloss is the
|
||
proof: no individual claim was false, the defect was **adjacency**, and
|
||
adjacency does not exist until the pages sit next to each other.
|
||
- **The code reviewer stays per step because what it catches compounds.** An
|
||
accessibility or crawlability defect propagates into the next page built on
|
||
it. A claims defect does not compound; it sits there until someone reads it.
|
||
|
||
**And what it costs is recorded, not glossed.** `claims-auditor` has caught the
|
||
struck false universal reaching a public page in the first person, a `<title>`
|
||
reading "Sole Arbitrator", "Every award I issue" on a practice with no completed
|
||
arbitration, four breaches of the Q54 gate on the day it was written, the
|
||
memberships currency warranty, and a §4 Verified row authorising exactly what
|
||
D16 forbids. D20 accepts that a defect of that class may now live in an
|
||
unpublished draft for weeks. **It must not survive cutover** — `docs/06` carries
|
||
two blocking items for it at the top of the checklist.
|
||
|
||
**One substitution, flagged rather than made silently.** Pouya's directive wrote
|
||
that several of those defects "read badly on a legal professional's site".
|
||
`CLAUDE.md` bars describing him as a legal professional **anywhere, that file
|
||
included**, so §3 D20 says "the site of a person who holds a JD". The
|
||
substitution is his rule applied to his own sentence; the meaning is unchanged.
|
||
|
||
### The D20 sweep, as a command
|
||
|
||
D20 was swept to the six destinations Pouya named plus §3 itself. Verified by
|
||
command, output read before this line was written:
|
||
|
||
```
|
||
$ git grep -c 'D20' -- CLAUDE.md AGENTS.md docs/ .claude/
|
||
.claude/agents/claims-auditor.md:4
|
||
.claude/commands/build.md:5
|
||
.claude/commands/review.md:3
|
||
AGENTS.md:3
|
||
CLAUDE.md:5
|
||
docs/06-deployment.md:3
|
||
docs/08-execution-protocol.md:5
|
||
```
|
||
|
||
`D17` and `D19` are amended in place rather than superseded: D17's "two
|
||
independent review agents" now describes the project rather than the step, and
|
||
**D19's two-round cap is explicitly scoped to the per-step code review** — it
|
||
does not govern the cutover claims pass, which has no second pass behind it and
|
||
runs until its findings are resolved.
|
||
|
||
Three residual per-step references were caught by re-reading rather than by the
|
||
sweep: `/build`'s "Both briefs carry the same boundary", `/build` Phase 5's
|
||
"a finding neither review agent has to spend a pass on", and `docs/08`'s
|
||
"Verifying they are loaded" block, which the edit had orphaned inside a new
|
||
subsection. All three corrected.
|
||
|
||
### Q56 — RULED. Mediation is NOT scoped commercial
|
||
|
||
Pouya: *"Correct the four 'Commercial Mediation' surfaces to 'Mediation'; leave
|
||
§4's mediation row unscoped."*
|
||
|
||
**The reason is recorded beside BOTH §4 rows so the asymmetry reads as designed
|
||
rather than as an oversight.** Arbitration is scoped commercial because of a
|
||
**legal gate** — Q39, family arbitration in Ontario requires prescribed training.
|
||
**Mediation has no such gate.** A later editor tidying the two rows into a
|
||
matching pair would be reintroducing the defect, and both rows now say so.
|
||
|
||
**Q56 named four surfaces. The sweep changed thirteen shipped strings across five
|
||
files, and `adversarial-reviewer` then found three more it had missed.** The
|
||
count matters because the enumeration is what a later auditor treats as the
|
||
completeness list — the same shape as the `Q.Arb` sweep that missed ten lines in
|
||
`docs/03`. What was corrected:
|
||
|
||
| Where | Was |
|
||
|---|---|
|
||
| `/mediation/` `<title>` | `Commercial Mediation · …` |
|
||
| `/mediation/` `Service.name` | `Commercial mediation` |
|
||
| `/mediation/` `Service.description` | `Sole-mediator appointments in commercial disputes.` |
|
||
| `/mediation/` meta description | `Sole mediator for commercial disputes in Toronto.` |
|
||
| `/mediation/` §Subject matter lede | `Where a commercial mediation usually turns on…` |
|
||
| `/mediation/` §The role | `What I bring to a commercial file…` ← **round 2** |
|
||
| `/` meta description | `Commercial mediation and arbitration in Toronto.` |
|
||
| `/` hero lede | `I mediate commercial disputes from Toronto…` |
|
||
| `/about/` hero lede | `I mediate commercial disputes and I accept…` |
|
||
| `/practice/` meta description | `Six areas where a commercial dispute…` ← **round 2** |
|
||
| `/practice/` hero lede | `Each of these is a place where a commercial dispute…` ← **round 2** |
|
||
| `/practice/` §The processes | `…choosing between, in commercial matters.` ← **round 2, BLOCKING** |
|
||
| `src/data/schema.ts` `ProfessionalService.description` | `Commercial mediation and arbitration for…` |
|
||
|
||
**The blocking one is the finding of this change set, and my sweep could not have
|
||
found it.** `/practice/` shipped *"These describe the process the parties are
|
||
choosing between, in commercial matters"* immediately above links to
|
||
`/mediation/`, `/arbitration/` and `/med-arb/` — so "these" scopes **mediation**,
|
||
on the page that distributes traffic to it, hours after this same change set
|
||
wrote *"do not scope it on a page"* into §4. **"Commercial" and "mediation" are
|
||
never in the same element**, so no proximity grep reaches it. Counsel with a SABS
|
||
mediation reads the six area cards, reads that the processes are offered in
|
||
commercial matters, and concludes the practice does not take their matter.
|
||
|
||
`docs/03` now carries the command **and its limit**: the proximity grep finds the
|
||
adjacent form only, and for the split form there is no pattern — read every
|
||
`commercial` in `src/` and `dist/` and ask what each one is scoping.
|
||
|
||
**Left deliberately, so the judgement is visible rather than missed:**
|
||
`/practice/cross-cultural/` ships *"These run as commercial mediations and
|
||
arbitrations, from Toronto"*. Its referent is the cross-cultural **commercial**
|
||
matters the page has just defined — §4's own words for that area — so it is
|
||
context, not a scope on the offering. It is the only literal `commercial
|
||
mediation` string left in `dist/`. Raised by `adversarial-reviewer` as a
|
||
judgement call; called this way, and recorded here so Pouya can reverse it.
|
||
|
||
**And §4's mediation enumeration is annotated rather than edited.** Pouya's
|
||
ruling lists five subject matters — *"commercial, construction, insurance/SABS,
|
||
shareholder and cross-cultural"* — against **six** published areas, every one of
|
||
which offers mediation. Technology and energy are absent. Read as an
|
||
enumeration the row is short by two and a later reader would strike two live
|
||
pages. The row now says the list is **illustrative of breadth, not a closed
|
||
set**, and that Q35's gate governs the authorised subject matter. The words are
|
||
his ruling, so they were annotated, not rewritten. **Flagged to him.**
|
||
|
||
### Q55 — CLOSED WITHOUT BEING RESOLVED, and the difference is the ruling
|
||
|
||
Pouya: *"The date is not published and nothing depends on it… A register that
|
||
says 'two inconsistent reports of an unpublished fact, neither relied on' is
|
||
complete. Do not put it to Pouya."*
|
||
|
||
§4's Q.Arb row now carries the **split stamp explicitly**, which it did not
|
||
before: `[verified 2026-08-29 — Pouya]` on the **status**, `[Pouya's stated basis
|
||
2026-08-29]` on the **date**. The 2026-08-26 (a) Change Log report of *commenced
|
||
August 2026* stands **unreconciled, permanently and on purpose** — the row says
|
||
so, and says not to reconcile it by inference, re-stamp it, or put it back to
|
||
him. The publication rule is untouched: no date ships.
|
||
|
||
### `check:claims` IS FROZEN — a tripwire, not a program
|
||
|
||
Pouya's ruling, on his own measurement: round 2 of the Q.Arb amendment found
|
||
**five defects in round 1's fixes to that script, two of which made it worse than
|
||
before the pattern existed**. At that point it was generating defects at roughly
|
||
the rate it caught them. The rule, now in `CLAUDE.md`:
|
||
|
||
- a pattern is added **only after a real breach has reached `dist/`**, never
|
||
speculatively;
|
||
- each addition ships with **a probe** proving it catches the actual breach
|
||
**and a negative fixture** proving it stays silent on the nearest approved
|
||
copy;
|
||
- **no refactors, no coverage improvements, no tidying.**
|
||
|
||
The script was not touched in this change set, and step 6 tested the freeze
|
||
within hours, on `/for-parties/` at build step 6.
|
||
|
||
### Two conventions into `CLAUDE.md`
|
||
|
||
1. **Sweep the vocabulary, not only the subject.** `git grep 'Q.Arb'` is
|
||
line-anchored and could not find ten lines entirely about Q.Arb that never
|
||
name it. R8's sharpest edge: a sweep can be a real command, read honestly,
|
||
and still be the wrong command. The `/practice/` finding above is the same
|
||
rule from a third angle — there the two words are not even in the same
|
||
element, so **no** pattern reaches it and only reading does.
|
||
2. **Agent definitions load at session start.** An edit to `.claude/agents/*.md`
|
||
does not reach the session that made it. Restart before relying on one, and
|
||
**say in the report which version actually ran.** Found when `claims-auditor`
|
||
reconstructed the gloss lens from this Change Log rather than having it in
|
||
its brief.
|
||
|
||
Convention 2 is also in `docs/08` beside the "verifying the agents are loaded"
|
||
instruction, which is where someone checking that would look.
|
||
|
||
### Verification
|
||
|
||
```
|
||
npm run check exit 0 0 errors / 0 warnings / 0 hints
|
||
npm run lint exit 0
|
||
npm run build exit 0
|
||
npm run check:claims exit 0
|
||
```
|
||
|
||
The `Commercial Mediation` correction was verified on `dist/` rather than on
|
||
`src/`: `grep -ric 'commercial mediation' dist/` returns **1**, and it is
|
||
`/practice/cross-cultural/`'s deliberate leave, recorded above. The reviewer
|
||
independently enumerated **all 62 occurrences of `commercial`** across the 14
|
||
built pages with 240 characters of context and read each one — **none scopes
|
||
mediation.**
|
||
|
||
---
|
||
|
||
## 2026-08-30 (ad) — Q.Arb is HELD; C.Med-Arb is struck entirely; the paired-disclosure condition dissolves with the stage it required — and this deviates from the strategy brief deliberately
|
||
|
||
**Type:** ruling + D3-class sweep. **20 files, +1064 / −607.** `src/` alone is
|
||
net **−196** (+291 / −487), which is the shape of a credential becoming simpler rather than
|
||
more qualified; the additions are concentrated in this record, the specs, and
|
||
`check:claims`.
|
||
|
||
### Pouya's ruling, recorded verbatim because two files quote it
|
||
|
||
> "Q.ARB IS HELD. C.MED-ARB IS OUT ENTIRELY. Treat this as D3-class."
|
||
>
|
||
> "§4 — Q.Arb becomes a held designation, `[verified 2026-08-29 — Pouya]`.
|
||
> Obtained July 2026; record internally, **DO NOT publish the date**. Public copy
|
||
> carries `Q.Arb (ADRIC / ADRIO)` beside Q.Med and nothing more. Delete every
|
||
> 'commenced', 'in progress', 'pathway', 'not yet' form."
|
||
>
|
||
> "**THE PAIRED-DISCLOSURE CONDITION DISSOLVES.** It existed only because Q.Arb
|
||
> was in progress. There is no stage left to disclose… Do not leave half
|
||
> standing."
|
||
>
|
||
> "**C.MED-ARB COMES OUT EVERYWHERE.** Pouya holds Q.Med and Q.Arb, which is
|
||
> what med-arb requires. The page says he conducts med-arb and stops."
|
||
>
|
||
> "**`/about/`'s ARC SECTION LOSES ITS SUBJECT.** Two held designations, no
|
||
> journey. Rewrite it as a plain credentials statement or delete it — do not
|
||
> edit phrase by phrase. An arc invites 'where are you on it'; two designations
|
||
> don't."
|
||
>
|
||
> "**REWRITE, DON'T EDIT**, anywhere copy earned credibility by being candid
|
||
> about an incomplete credential."
|
||
|
||
### ⚠️ THIS DEVIATES FROM THE STRATEGY BRIEF, AND THE DEVIATION IS THE RECORD
|
||
|
||
Pouya's instruction: *"Record that this deviates from the strategy brief, which
|
||
made C.Med-Arb 'the explicit long-term professional narrative'. Pouya has
|
||
dispensed with it. Note the deviation so nobody reinstates it from the brief."*
|
||
|
||
**The brief is not in this repository.** It is cited by `AGENTS.md`, `docs/01`,
|
||
`docs/03`, `docs/07` and `src/data/site.ts`, and no reader can open it — R14's
|
||
shape, pre-existing and not created here. That is precisely why this paragraph
|
||
matters: **the only defence against C.Med-Arb being reinstated from an
|
||
unreachable document is a written record that its removal was deliberate.** It
|
||
is now in four places — this entry, the struck §4 row, `docs/01` items 4 and 3
|
||
of `/med-arb/`, and `check:claims`.
|
||
|
||
### What the ruling touched
|
||
|
||
**§4.** `Q.Arb` becomes **HELD** (July 2026, recorded and unpublished).
|
||
`C.Med-Arb stated as long-term designation goal` is **struck**. The Forbidden
|
||
row barring "held, imminent, nearly complete" is struck **and replaced by a live
|
||
row barring the opposite** — a struck row whose surviving text does the opposite
|
||
of the strike is the Q25 shape, and `adversarial-reviewer` caught it here.
|
||
The paired-disclosure condition is dissolved with the reasoning kept, so the
|
||
dissolution is legible rather than a deletion. §11's `C.Med-Arb` row stays as a
|
||
**definition** and says so.
|
||
|
||
**`src/`.** `CREDENTIALS.inProgress`, `.goal` and `.goalName` are **deleted, not
|
||
emptied** — which turned every consumer into a `ts(2339)` build error and is how
|
||
`/arbitration/` and `/med-arb/` surfaced rather than being remembered. Pouya's
|
||
own principle from 2026-08-29: *"the pattern that actually worked was
|
||
mechanical."* `/about/`'s arc section, `/arbitration/`'s credentialing-stage
|
||
section, and their styles are gone; `/arbitration/`'s Appointments section
|
||
inherits the vacated `section-inverse` so the page keeps alternating.
|
||
`hasCredential` now **maps** `CREDENTIALS.designations` instead of indexing
|
||
`[0]` — indexing is what would have dropped Q.Arb from the graph silently.
|
||
|
||
**Specs.** `docs/01` items amended at `/`, `/about/`, `/arbitration/` and
|
||
`/med-arb/`, each carrying the strike and its date **inside the item**, because
|
||
the reinstatement risk is somebody reading the outline. `docs/03`, `docs/04`,
|
||
`docs/06`, `docs/07` follow.
|
||
|
||
**`check:claims`** gains `c-med-arb-struck` and an **inverted** `q-arb-as-a-stage`
|
||
— the predecessor barred Q.Arb reading as held.
|
||
|
||
### The sweeps, as commands — and one of them was run twice
|
||
|
||
```
|
||
$ git grep -nE 'Q\.?Arb' -- src/ docs/ ':!docs/reference' | grep -icE 'commenc|in progress|pathway|not yet'
|
||
10 # each one a strike notice or a check:claims fixture; none is live copy
|
||
```
|
||
|
||
⚠️ **THE `dist/` SWEEP WAS RUN TWICE, AND THE FIRST INSTRUMENT WAS WRONG.**
|
||
`grep -roh '.\{50\}Q\.Arb.\{50\}' dist/ | sort -u` returned **10 distinct
|
||
contexts**, and this entry was drafted around that number. `grep -o` takes
|
||
**non-overlapping** windows, so on minified HTML — where a page is a handful of
|
||
very long lines — an early match consumes characters a later one needs. The
|
||
visible symptom: *"I hold Q.Med and Q.Arb through…"* ships on two pages and
|
||
**did not appear in the list at all.** A `grep -o` window count is not an
|
||
enumeration. Re-run with an overlap-safe scan over every match:
|
||
|
||
```
|
||
49 occurrences of "Q.Arb" across 12 pages, in 13 distinct contexts:
|
||
x12 ...arbitration appointments. Q.Med and Q.Arb designations through ADRIC and ADRIO...
|
||
x12 "name":"Q.Arb (ADRIC / ADRIO)","credentialCategory":"Professional designation"
|
||
x12 Q.Med (ADRIC / ADRIO) · Q.Arb (ADRIC / ADRIO) footer, every page
|
||
x3 ...JD, Q.Med, Q.Arb — a Toronto mediator... meta/og/twitter desc
|
||
x2 <dt>Q.Arb</dt><dd>ADRIC / ADRIO designation</dd> credential row
|
||
x1 <title>About · … · Mediator, Q.Med, Q.Arb · Toronto</title> (+ og, + twitter)
|
||
x1 · Q.Arb (ADRIC / ADRIO) /about/ designation line
|
||
x1 <li>Q.Arb (ADRIC / ADRIO)</li> /about/ Designations
|
||
x1 Toronto, by appointment. Q.Med and Q.Arb designations held. ProfessionalService
|
||
x1 Mediation is where they meet. I hold Q.Med and Q.Arb through… /about/
|
||
x1 ...did not settle. I hold Q.Med and Q.Arb through… /med-arb/
|
||
|
||
Stage word within 60 chars of any of the 49: none
|
||
```
|
||
|
||
**This is the fifth time on this project that a number turned out to be a claim
|
||
about the instrument** — `CLAUDE.md` lists the other four. Same tell every time:
|
||
the figure looked plausible and nobody asked what it was a number *of*.
|
||
|
||
```
|
||
$ node scripts/check-claims.mjs → exit=0, c-med-arb-struck clean over 12 pages
|
||
```
|
||
|
||
**And the gate was tested against the copy it replaces**, which is the check that
|
||
matters: of the **nine** strings this change set removes, it now catches **eight**.
|
||
The ninth is the h1 *"Available now, and open about the stage"*, which names no
|
||
designation — recorded as a known limit in the pattern itself and assigned to
|
||
`claims-auditor` rather than papered over.
|
||
|
||
### Two review rounds — 26 findings, and four of mine were defects in my own fixes
|
||
|
||
**`claims-auditor` (R1 is the one that matters).** It found the register
|
||
contradicting itself on the acquisition date and would not let it pass:
|
||
2026-08-26 (a) records *"commenced August 2026"*; this ruling says *"obtained
|
||
July 2026"*; both `[verified — Pouya]`, three days apart. **Opened as Q55.**
|
||
It does not block — the site says *held*, which is his ruling either way, and the
|
||
date is unpublished — but §4's function is that a stamped claim is checkable, and
|
||
this one is contradicted on the face of the record. Also caught: `/med-arb/`
|
||
stating the arbitration offering **unscoped** (every §4 row is commercial); a
|
||
**wrong acquisition date invented in a `SiteHeader` comment**; `site.ts` holding a
|
||
second copy of a date §4 is the sole record for; `docs/04` contradicting itself
|
||
seven lines apart on `hasCredential`.
|
||
|
||
**`adversarial-reviewer`.** Its blocking finding was **mine**: the `/about/`
|
||
paragraph I wrote to restore the word count opened *"The matters I take are
|
||
commercial"* — **no §4 row** (Offerings scopes *arbitration* commercial; the
|
||
mediation row is unscoped) — and named the LAT inside its own commercial class
|
||
while `/practice/insurance/` ships *"Disputes between an insured person and an
|
||
insurer"*. Also: `q-arb-as-a-stage` firing on **compliant** copy, because bare
|
||
`once|when` in a 50-character window matches *"I hold Q.Med and Q.Arb… when a
|
||
party asks"*; `c-med-arb-struck` blind to `C.Med-Arbitrator` (a trailing `\b`
|
||
after `Med-Arb`); the gate **defeated by `<strong>`**, since `[^<]` cannot cross
|
||
inline markup and this site sets `<strong>` in prose; and a JSDoc detached from
|
||
`designationLine` by a guard I inserted between them.
|
||
|
||
**Both agents reported the handed diff was stale** — the working tree had moved
|
||
under it. Regenerate the diff at review time, or point reviewers at the tree.
|
||
|
||
⚠️ **AND `claims-auditor` DID NOT HAVE THE LENS ADDED IN ENTRY (ac).** Agent
|
||
definitions load at session start, so the lens committed hours earlier was not
|
||
in its brief; it reconstructed it from the Change Log and ran it anyway. **An
|
||
edit to `.claude/agents/*.md` does not take effect until a new session.** That is
|
||
the fifth stale-claim-inside-that-brief instance the brief itself predicts.
|
||
|
||
### Fixes to the fixes
|
||
|
||
The `once|when` repair, the two-view scan, and the `C.Med-Arbitrator` blend were
|
||
all corrections to patterns written **in this change set**. The scanner now reads
|
||
each page twice — as published, and with inline tags collapsed to a space and
|
||
block tags to a full stop — which preserves the do-not-leap-a-paragraph property
|
||
that made the `[^.<]` window worth having. Proved by injecting
|
||
`<strong>Q.Arb</strong> — the pathway commenced` into a built page: **raw view
|
||
missed, collapsed view caught.**
|
||
|
||
`DESIGNATIONS_HELD_LINE` now holds the one sentence `/about/` and `/med-arb/`
|
||
had **already** typed two different ways in the change set that introduced both.
|
||
|
||
### Round 2 — and the worst finding was one the round-1 sweep could not reach
|
||
|
||
**`claims-auditor` found ten lines in `docs/03` that instructed the struck
|
||
form, unstruck, imperative, eleven lines below this change set's own strike
|
||
notice on the same bullet.** They read *"'Pathway', never 'designation'"*, cited
|
||
the **struck** Forbidden row as live, told an implementer *"the limit being named
|
||
is the stage of the arc, stated plainly"*, and closed *"Precision about what you
|
||
cannot yet do makes the rest believable."*
|
||
|
||
**Why the 2026-08-29 sweep missed it, and this is the transferable part:
|
||
`git grep -nE 'Q\.?Arb'` is LINE-ANCHORED, and not one of those ten lines
|
||
contains the string.** The block is entirely about Q.Arb and never names it. A
|
||
sweep anchored on a subject cannot find prose that discusses the subject by
|
||
pronoun, by paraphrase, or across a line break — which is the same wrap defect
|
||
`/about/` already recorded for `as in\n * progress`. **Sweep the vocabulary, not
|
||
only the subject.** Re-run unanchored, on the stage words themselves:
|
||
|
||
```
|
||
$ git grep -nIE 'commenced (in )?August 2026|in progress|the arc\b|long-term (arc|narrative)|endpoint|newly commenced|not yet held|nearing completion|built toward' \
|
||
-- docs/ src/ scripts/ ':!docs/reference' | grep -v <strike-notice terms>
|
||
→ every survivor is a strike notice or an unrelated sense of "endpoint" (API, S3)
|
||
```
|
||
|
||
**And `docs/reference/adrio-designations.md` carried three claims asserting the
|
||
struck §4 row** — *"the designation §4 records as the practice's stated goal"*,
|
||
*"is Pouya's own stated goal and has a §4 row"*, *"not that he has **commenced**
|
||
Q.Arb"* — in the file an implementer opens to write designation copy. The
|
||
2026-08-29 sweep excluded `docs/reference/` on the reasoning that it holds
|
||
sourced extracts. **That reasoning is half right:** the quotations are evidence
|
||
and must not be touched; the *commentary around them* is this repo's own voice
|
||
and goes stale like any other. Corrected without touching an extract.
|
||
|
||
**The gloss lens earned itself on `/med-arb/`.** The page quoted ADRIC
|
||
accurately — *"requires a high level of practitioner competence to do
|
||
successfully"* — headed the next section *"Med-arb asks one neutral to be
|
||
competent at both"*, and answered it with the two held designations. **ADRIC
|
||
answers its own sentence with a different designation**: the same page points at
|
||
the Chartered Med-Arb and a Med-Arb Foundational Course, and
|
||
`docs/reference/adrio-designations.md` Finding 3 calls the Q-level designations
|
||
*"an intermediate step"*. So the page borrowed a third party's competence
|
||
standard and supplied an answer that party does not give — **by adjacency, which
|
||
is why no claim in it was individually false.** Heading and lede rewritten to
|
||
state what the practice holds and offers, with no competence proposition.
|
||
|
||
**Two register corrections, both about what a stamp means.** (1) The Q.Arb row
|
||
stamped `[verified 2026-08-29 — Pouya]` over the acquisition date **in the same
|
||
cell that says the register cannot vouch for it**. The stamp is now split:
|
||
status `[verified]`, date `[Pouya's stated basis 2026-08-29]` — the device §4
|
||
already uses for the commercial-arbitration proposition. (2) Q55's disposition
|
||
read *"the site is correct either way"*. It is not: it is **faithful to his most
|
||
recent instruction**, which is a different thing, and §4's premise is that
|
||
`[verified — Pouya]` establishes what he reported rather than the fact.
|
||
|
||
**`/about/`'s replacement paragraph was wrong a second time.** Round 1 struck
|
||
*"The matters I take are commercial"* (no §4 row). The replacement opened *"The
|
||
subject matter runs across…"*, which swaps a scope claim for a **coverage**
|
||
claim — also unrowed, and a bare present-tense indicative in §Background, the
|
||
one section where a reader defaults to reading history. It now reads *"I accept
|
||
appointments in six areas"*, which is exactly what Q35 grants: an area may be
|
||
named where he can competently accept an appointment **and the page frames it as
|
||
positioning, not claimed history.**
|
||
|
||
**One finding declined, with the reason recorded in the file.** The audit held
|
||
that the ground which struck the biography sentence should also reach
|
||
`/about/`'s hero — *"I mediate commercial disputes"*. It does not: the struck
|
||
sentence was a **universal** (nothing he takes is non-commercial — an exclusion
|
||
§4 has no row for); this one is **existential** (he mediates commercial
|
||
disputes — narrower than the §4 Offerings mediation row grants, and excluding
|
||
nothing). A claim narrower than its row is safe; a claim the row does not reach
|
||
is not.
|
||
|
||
**Smaller round-2 corrections:** *"put to ADRIC's membership"* → *"presented to
|
||
the membership at ADRIC's 2019 annual conference"* (the extract says
|
||
**presented**; *put to* connotes submission for decision); `docs/01`'s Indigenous
|
||
paragraph, where *"for a Q.Med on the C.Med-Arb pathway"* sat **outside** the
|
||
quotation marks in `docs/01`'s own voice while a parenthetical this change set
|
||
added called it *"the brief's framing, quoted"* — a quotation boundary the marks
|
||
do not draw, plus a struck stage form; two cutover-checklist bullets that ended
|
||
mid-sentence; a build-guard message naming a paragraph that had been deleted;
|
||
`CredentialRow`'s claim that the fourth slot *"got SHORTER"* (21 → 25
|
||
characters — it got longer, and the conclusion survives on the other half of the
|
||
sentence); and a `CREDENTIAL_ROW` JSDoc orphaned by the constant inserted above
|
||
it — the second detached-JSDoc defect in this change set, both caused by
|
||
inserting a declaration between a comment and its subject.
|
||
|
||
**`adversarial-reviewer`'s round-2 pass found five defects in the round-1 fixes
|
||
to `check:claims`, and two of them made the gate worse than before:**
|
||
|
||
1. **The dedup dropped real breaches.** Keying a `Set` on the matched text meant
|
||
`He is a lawyer.` twice on one page reported **once**, count 1. Before the
|
||
two-view change it reported 2. **The check was truncating its own output** —
|
||
the one thing `CLAUDE.md` says a check must never do — and the report is what
|
||
an operator acts on. Now counted per occurrence, published view authoritative.
|
||
2. **The collapsed view leapt paragraph boundaries**, and the comment claimed it
|
||
could not. Block tags collapsed to `' . '`, but the windows are written
|
||
`[^<]` and collapsed text contains no `<`, so they were bounded by nothing:
|
||
an `<h2>Q.Arb</h2>` joined to a paragraph reading *"took effect on 1 March
|
||
2025"* — approved copy that ships. Writing `[^.<]` instead would have
|
||
reintroduced the sentence-crossing the collapsed view exists for. **A
|
||
sentinel separates the two jobs**: block boundaries become `\uE000` (Private
|
||
Use Area, not a control character — `no-control-regex` bars `\u0000`), and
|
||
every window reads `[^<\uE000]`, bounded by `<` in one view and the sentinel
|
||
in the other.
|
||
3. **The self-test read only the published view**, so the entire false-positive
|
||
surface of the new view was untested *by construction* — the loosening
|
||
happened precisely where the instrument check could not look.
|
||
4. **Both patterns advertised coverage they lacked.** The `rule` line printed on
|
||
failure named *pending*, which the regex had never matched; `working toward`
|
||
— the exact phrase struck from `/med-arb/` — was missed; and
|
||
`c-med-arb-struck`'s trailing `\b` still blocked `C.Med-Arbitrators` and
|
||
`C.Med-Arbitration` after the round-1 repair moved it. The `once|when` repair
|
||
**narrowed rather than closed**: it still fired on *"when I hold a
|
||
preliminary conference"*, because `hold` takes any object. The hold-verb must
|
||
now take the designation, and that alternative had to move to the top level —
|
||
as a member of the stage group it swallowed the anchor and the self-test
|
||
caught it.
|
||
5. **`publishedText`'s JSDoc was detached** by the block inserted above it —
|
||
**the same defect this entry records catching on `designationLine`**, in the
|
||
same change set, by the same mechanism.
|
||
|
||
**Proved rather than asserted.** Three probe pages injected into a real `dist/`:
|
||
duplicates reported as **2 with both line numbers**; the paragraph-split approved
|
||
copy **silent**; `<strong>Q.Arb</strong> — the pathway commenced` **caught**.
|
||
|
||
**Two more structural findings, both about drift the change set created:**
|
||
|
||
- **`AREAS_NAMED_IN_BIO`'s message was unreachable.** `PRACTICE_AREAS` is
|
||
`as const`, so `.length` is the literal `6`; with the constant also literal
|
||
`6`, a seventh area makes `7 !== 6` non-overlapping literals and `astro check`
|
||
fails with **`ts(2367)`, which reads like lint noise** — and both deploy paths
|
||
run `check` before the build, so the message never renders. One token
|
||
(`: number`) fixes it. Probed: with a seventh area, zero `ts(2367)` and the
|
||
build throws the intended sentence.
|
||
- **`CREDENTIAL_ROW` hand-types the designations.** Harmless while the fourth
|
||
slot held a *stage* (an independent fact); on 2026-08-29 it became a duplicate
|
||
of `designations[1]`, and nothing connected them — so a third designation
|
||
would reach four surfaces and silently miss the credential row. The
|
||
map-not-index fix celebrated in `schema.ts` and `docs/04` had left this copy
|
||
alone. Now pinned by `_DesignationRowParity`, a type-level assertion in
|
||
`_MembershipParity`'s shape; probed by renaming one value, which fails
|
||
`npm run check` with `ts(2344)`.
|
||
|
||
**And a scope question that is Pouya's, opened as Q56.** §4 rows arbitration
|
||
scoped commercial three times and leaves the mediation row unscoped, while the
|
||
site says *"Commercial Mediation"*, *"I mediate commercial disputes"* and
|
||
`Service.name: "Commercial mediation"` — and `/practice/insurance/` offers
|
||
mediation in insured-versus-insurer SABS matters, which are not commercial.
|
||
Nothing is false (narrower than a row is safe), but the two halves cannot both
|
||
be the whole picture. **This change set had newly written the claim onto
|
||
`/med-arb/`; that sentence is removed pending his answer**, and the page's own
|
||
med-arb scoping — which §4 does row — is untouched.
|
||
|
||
**D19 trim applied to this change set's own comments:** `Pill.astro` 16 lines →
|
||
5, `about.astro`'s paragraph note 26 → 10, the `q-arb-as-a-stage` comment 24 →
|
||
16. Each kept its live constraint and dropped the narrative of its own drafts.
|
||
|
||
⚠️ **THE LOOP STOPS HERE — D19.** Round 1 reviewed the change; round 2 reviewed
|
||
the fixes, and again a majority of its findings were defects *in* round 1's
|
||
fixes. That is why round 2 exists and it is also why round 3 does not.
|
||
|
||
### Verification — 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, 25 approved strings)
|
||
```
|
||
|
||
12/12 pages: one `<h1>`, no skipped heading level, no adjacent duplicate ground.
|
||
`/about/` biography **404 words** — back inside `docs/01`'s 400–600 after the
|
||
deleted paragraph took it to 355. The `AREAS_NAMED_IN_BIO` guard was probed by
|
||
setting it to 5: build fails with the intended message.
|
||
|
||
### Open after this entry
|
||
|
||
1. **Q55 — the Q.Arb acquisition date.** Needs one line from Pouya. Does not
|
||
block; nothing published turns on it.
|
||
2. **`/about/` has no dark band.** The arc section was its only `section-inverse`;
|
||
the accent contact band still closes the page. Making the credentials section
|
||
inverse would restore the rhythm and needs a contrast pass — **not done, because
|
||
it is a design decision the ruling did not reach.**
|
||
3. **R1 (licensure framing)** — unchanged and unaffected by anything here.
|
||
|
||
---
|
||
|
||
## 2026-08-30 (ac) — Pouya ratifies build step 5; ADR Chambers struck from the page and from the spec; and the pattern behind three shipped defects gets a named lens in `claims-auditor`
|
||
|
||
**Type:** ruling + correction. **Files:** `src/pages/arbitration.astro`,
|
||
`docs/01-architecture.md`, `docs/reference/adric-rules.md`,
|
||
`.claude/agents/claims-auditor.md`, `AGENTS.md`.
|
||
|
||
### What Pouya ratified, so none of it is re-litigated
|
||
|
||
**Q54's stamp date — 2026-08-29 STANDS, and the question is closed.** His
|
||
words: *"You're right that a commitment cannot predate its own text. My
|
||
2026-08-27 was the date I ruled, not the date the undertakings existed."* The
|
||
ruling date and the stamp date are two different facts and the stamp records
|
||
the second. §4's stamp block and the §9 Q54 row both now carry the
|
||
ratification; the flag is discharged rather than deleted.
|
||
|
||
**The three sourced corrections — all ratified.** On the one that was his own:
|
||
*"'the 2026 privacy statute' in `docs/03` is mine and it was wrong. I took it
|
||
from the strategy brief's 'replacement privacy legislation in 2026' and never
|
||
checked whether it passed. Bill C-27 died without royal assent."* The LAT
|
||
ellipsis that deleted *"negotiation"*, and *"connection allocation"* — both
|
||
confirmed correct.
|
||
|
||
**`check:claims`, Q49, Q50, the §7 SES record, and R11's `typescript` hold —
|
||
ratified as shipped.** No change to any of them.
|
||
|
||
### ADR Chambers is struck — from `/arbitration/` AND from `docs/01` item 3
|
||
|
||
Pouya: *"Your instinct was right and my spec was the problem: the source shows
|
||
what the firm publishes, not that an outside neutral can be appointed under its
|
||
rules. Naming it implies a relationship that isn't established. ADRIC and ad hoc
|
||
are enough."*
|
||
|
||
This was the one review finding carried rather than fixed at step 5 — held
|
||
**because `docs/01` item 3 listed it**, which is exactly the wrong reason to
|
||
keep a claim, and the reason the spec was struck in the same ruling. **Both
|
||
halves had to go or the next build would reinstate it from the spec.**
|
||
|
||
- `src/pages/arbitration.astro` — the *"Or ADR Chambers"* paragraph and the
|
||
26-line comment whose entire subject was that paragraph. The replacement
|
||
comment records the strike and the reason, so nobody re-adds it.
|
||
- `docs/01-architecture.md` item 3 — now **"ADRIC, ad hoc"**, with the strike
|
||
and its date stated in the item itself.
|
||
- `docs/reference/adric-rules.md` — its exclusion note said *"`docs/01`
|
||
§`/arbitration/` names it as a rule option"*, which stopped being true the
|
||
moment the item changed. Corrected in the same pass rather than left to go
|
||
stale, which is the `docs/05` DKIM failure's shape.
|
||
- **§12 R18 loses limb (g)** — the ADR Chambers rules' amend-on-posting clause
|
||
was one of seven volatile shipped sentences and is no longer shipped. R18 now
|
||
reads **six**, in the header and in the trailing cell.
|
||
|
||
**The extract stays.** `docs/reference/adr-institution-names.md` is untouched:
|
||
it is a faithful record of what was retrieved, and R14's rule is that the
|
||
artefact is committed, not that every artefact must be cited by a page. What
|
||
changed is what the site asserts, not what was researched.
|
||
|
||
**`docs/07-fees.md` is NOT in scope and was not touched.** It cites ADR Chambers
|
||
for *published fee ranges* — internal benchmarking, a different claim, and not
|
||
public copy.
|
||
|
||
```
|
||
$ git grep -n -i 'ADR Chambers' -- src/ docs/01-architecture.md
|
||
docs/01-architecture.md:239: ⚠️ **ADR CHAMBERS WAS STRUCK FROM THIS ITEM AND FROM THE PAGE ON 2026-08-30
|
||
docs/01-architecture.md:244: rules, and the firm's own model clause reads *"at ADR Chambers"* — so naming
|
||
src/pages/arbitration.astro:209: ⚠️ ADR CHAMBERS IS NOT NAMED HERE, AND MUST NOT BE ADDED BACK.
|
||
src/pages/arbitration.astro:214: clause reads "at ADR Chambers". Naming it implies a relationship
|
||
```
|
||
|
||
**Four matches, and all four are the strike notices** — two in the `docs/01`
|
||
item, two inside an `.astro` comment that never renders. **This entry first
|
||
claimed `(no matches)`, written before the command was read**, which is the
|
||
exact failure `CLAUDE.md` names: *a sweep is a command, not a claim*. The
|
||
command was then run, the output read, and the claim replaced with it. The
|
||
sweep that actually settles the question is the one over shipped bytes:
|
||
|
||
```
|
||
$ grep -ril 'adr chambers' dist/ ; echo "exit=$?"
|
||
exit=1 # no matching file
|
||
```
|
||
|
||
### The pattern, named — and given to `claims-auditor` because it is not greppable
|
||
|
||
Pouya's instruction: *"NAME THE PATTERN, because it is now three-for-three: a
|
||
correct verbatim quote with an overreaching sentence beneath it. The quote
|
||
passes audit because it is accurate; the gloss fails because it says more than
|
||
the quotation establishes. Add it as an explicit lens to `claims-auditor`… It is
|
||
not greppable, so it needs a reviewer."*
|
||
|
||
`.claude/agents/claims-auditor.md` gains **§The second lens — does the gloss
|
||
stay inside the quote?**, placed before the existing catch-list and wired into
|
||
the Method as step 4. It states the distinction that makes it a second pass
|
||
rather than a bullet: **everything else in that brief audits claims about Pouya
|
||
against §4; this audits claims about the world against `docs/reference/`.** §4
|
||
holds no view on what the `Construction Act` says.
|
||
|
||
The four-step procedure is deliberately mechanical — read the quote, read the
|
||
sentence beneath, ask what a reader takes the second to mean, then ask whether
|
||
the first *establishes* it (not "is consistent with", not "is plausible
|
||
given"). It carries the four shapes it has actually taken here, each named so
|
||
the lens is not later trimmed as generic advice:
|
||
|
||
1. **A subject swapped between sentences** — the LAT gloss said *"mediation,
|
||
before filing and continuing after filing"*; the Tribunal's second sentence
|
||
was about **negotiation**. Shipped on three pages.
|
||
2. **A term the source never uses** — *"connection allocation"*; the IESO pages
|
||
contain zero occurrences of *"allocation"*. Shipped on three pages.
|
||
3. **A status assumed to have held** — *"the 2026 privacy statute"*; a forecast
|
||
in a brief read as an event. Caught before it shipped.
|
||
4. **A class asserted from one instance** — ADR Chambers' self-amendment clause,
|
||
quoted from the arbitration rules, written as *"amends them"* of all three
|
||
sets. `claims-auditor` caught that itself at step 5.
|
||
|
||
**It is four-for-four, not three-for-three.** The strike above is the same
|
||
defect one level up: the extract establishes that the firm *publishes* rules,
|
||
and the page read that as *an outside neutral can be appointed under them*. The
|
||
lens records it as (4)'s second half.
|
||
|
||
### Why this is its own entry and its own commit
|
||
|
||
The Q.Arb amendment Pouya issued in the same message is a separate change set
|
||
and is deliberately **not** in this one. Step 5 carries twenty review findings'
|
||
worth of fixes across thirty files and has to be reviewable on its own; mixing a
|
||
credential-wide sweep into it would make both unreadable in `git log`.
|
||
|
||
### Verification
|
||
|
||
Gates re-run after these edits, reading exit status, never truncated:
|
||
|
||
```
|
||
npm run check exit=0
|
||
npm run lint exit=0
|
||
npm run build exit=0
|
||
npm run check:claims exit=0
|
||
```
|
||
|
||
### Open after this entry
|
||
|
||
Unchanged from the previous entry except that **item 4 (ADR Chambers) is now
|
||
closed by ruling**, and the Q54 stamp-date item is closed by ratification. R1
|
||
(licensure framing) remains live and is unaffected by anything here.
|
||
|
||
---
|
||
|
||
## 2026-08-29 (ab) — `check:claims` makes §4 a build error; Q54 publishes six conduct undertakings and creates a third class in §4; build step 5 ships `/practice/` and the six area pages — and sourcing them found three wrong facts already on the site or in the specs
|
||
|
||
### The structural addition, and Pouya's reasoning is the whole design brief
|
||
|
||
He named the failure mode precisely, and it is mine:
|
||
|
||
> "Your recurring failure this project is a specific shape: you write a rule
|
||
> into a header comment, then breach it in the file below, in the same change
|
||
> set. Q53's sweep, Q54's gate four times, the D13 'cannot' phrasing fifty lines
|
||
> under your own warning about it. That is not a discipline problem — prose in a
|
||
> comment does not govern the writing that follows it. The pattern that actually
|
||
> worked was mechanical: deleting the `class` prop so passing one is a build
|
||
> error. Nobody has breached that since."
|
||
|
||
So `npm run check:claims` — `scripts/check-claims.mjs`, 10 patterns, greps `dist/`
|
||
after a build and exits non-zero. **Wired into `/build` Phase 5, both deploy
|
||
paths (`scripts/deploy-local.sh` after the build and before the first `s3 sync`;
|
||
`.gitea/workflows/deploy.yml` as a `Claim check` step before the AWS CLI is even
|
||
installed) and `CLAUDE.md`'s command list.**
|
||
|
||
**Seven patterns are his minimum list. Three are additions**, each named to an
|
||
incident in this record and each with near-zero false-positive surface on this
|
||
site's vocabulary — `S. M. Lawrence` / the template's company number; Q.Arb
|
||
described as held; and Q39's struck universal. Strike any of the three and the
|
||
rest stand.
|
||
|
||
**Every pattern carries an `incident` string that is PRINTED ON FAILURE** — his
|
||
instruction, *"so nobody deletes one for being noisy."* A pattern whose cost is
|
||
visible and whose reason is not is a pattern somebody deletes in week two.
|
||
|
||
### Four design decisions in that script, three of which came from measuring it
|
||
|
||
1. **`<style>` blocks are stripped before matching, and that is load-bearing.**
|
||
Measured against the step-4 build *before the file existed*: a
|
||
case-insensitive sweep for `leading` returned **26 hits, 25 of them
|
||
`var(--leading-body)`** inside Astro's inlined critical CSS. The 26th was
|
||
`Pleadings, disclosure,` on `/arbitration/` — **the exact false positive
|
||
`CLAUDE.md` already records.** Word boundaries kill the second (`\bleading\b`
|
||
does not match "pleadings"); only the strip kills the first. A check that
|
||
cries wolf on every page on its first run is a check nobody keeps.
|
||
**JSON-LD is deliberately NOT stripped** — proven by probe: an injected
|
||
`"award":"holds Q.Arb"` in `/about/`'s graph is caught.
|
||
2. **It self-tests before it sweeps.** Each pattern must match its own fixtures,
|
||
and no pattern may match 11 strings of real approved copy. **The self-test
|
||
failed on its first run** — and correctly: the CSS negative had been written
|
||
as a bare declaration rather than wrapped in `<style>`, so it was asserting
|
||
the wrong thing. A regex that has quietly stopped matching passes a clean
|
||
sweep forever and looks identical to a clean site, which is the exact shape
|
||
Q22 turned out to be.
|
||
3. **It refuses an empty or missing `dist/`.** *"An empty sweep reads exactly
|
||
like a clean one."*
|
||
4. **It refuses a STALE `dist/`** — if anything under `src/` or `public/` is
|
||
newer than the newest built page it exits 2 and names both files. A pass
|
||
against yesterday's build is the same false negative in slower motion.
|
||
|
||
All four guards were **run, not asserted**: the injected-breach probe caught 7
|
||
matches across 4 patterns including the JSON-LD one; the empty, missing and stale
|
||
guards each returned exit 2.
|
||
|
||
`eslint.config.js` gains a scoped `no-console: off` for `scripts/**` — printing
|
||
is what a CLI check is for. **It was placed above the block it overrides and had
|
||
no effect at all**; flat config applies matching blocks in order, last one wins.
|
||
Caught by re-running lint rather than by reading the config.
|
||
|
||
### Q54 — ANSWERED. All six publish, and the answer created a third class in §4
|
||
|
||
Pouya: *"Publish all six, including (c). (c) ships as drafted."* His reasoning on
|
||
the expensive one is recorded on the §4 row and in `CONDUCT_UNDERTAKINGS`,
|
||
because it is the part a later reader would otherwise have to reconstruct: the
|
||
arbitral phase runs on the evidentiary record, not the caucus, so the case where
|
||
a neutral genuinely cannot decide without confidential material is uncommon.
|
||
|
||
**§4 now carries `Conduct undertakings` as a class distinct from credentials and
|
||
offerings** — his framing: *"They are not facts about experience; they are
|
||
commitments Pouya has now made… and they bind."* The gate is one line: **he must
|
||
have said it in terms.** The three offering gates do not apply and do not
|
||
substitute; this is the class where the register holds no view and the architect
|
||
holds all of it.
|
||
|
||
**The six strings live in `CONDUCT_UNDERTAKINGS` (`src/data/site.ts`) and the
|
||
three pages render them.** That is his instruction made mechanical: *"any later
|
||
softening is a change to a published commitment, not a copy edit."* The
|
||
characteristic failure of this class is silent — nothing in a build fails when a
|
||
promise gets smaller, and the diff reads like tightening. One constant means one
|
||
diff.
|
||
|
||
(a)(b)(c) ship on `/med-arb/` in a new **What I undertake** section. (d) ships on
|
||
`/mediation/` §Confidentiality. **(e) and (f) REPLACE rather than join** the
|
||
third-person sentences already on `/arbitration/` — the page already ended a
|
||
paragraph *"What does not is a process whose shape nobody agreed to in advance"*
|
||
and opened another *"The date an award is due belongs in the first procedural
|
||
order"*, which are the observation forms of the same two commitments. Keeping
|
||
both would have set each undertaking beside its own paraphrase.
|
||
|
||
⚠️ **THE STAMP READS 2026-08-29, NOT THE 2026-08-27 HE NAMED, AND THIS IS NOT
|
||
THE SAME CALL AS THE MEMBERSHIPS ROW.** The drafts did not exist on 2026-08-27:
|
||
Q54 was raised on 2026-08-28 and (d) and (e) shipped for one pass that same day
|
||
before `claims-auditor` removed them. A commitment dated 2026-08-27 would
|
||
predate the text of the commitment. Flagged in §4; one line changes it if he
|
||
meant the stamp to record a decision reached earlier of which these six are the
|
||
wording.
|
||
|
||
New component `Undertaking.astro` gives the class one visual treatment across
|
||
three pages — because set as body prose a reader cannot tell *"the agreement
|
||
should settle the switch"* from *"I will not take the appointment unless it
|
||
does"*, and the second is the half a party weighs.
|
||
|
||
### Q49 and Q50 — both ratified, and Q50 records a reversal of his own ruling
|
||
|
||
**Q49 CONFIRMED as read.** One row, "Mediator"; `worksFor` stays out. The
|
||
register had flagged the decline as *a reading rather than a ruling*, because
|
||
Q49 asked for two rows and one was granted. The reading is now the ruling, and
|
||
`worksFor` is settled out of the graph rather than withheld pending anything.
|
||
|
||
**Q50 — the deviation is RATIFIED AS THE DECISION.** His words: *"My ruling was
|
||
wrong: on LocalBusiness, `name` means the business's name, and name + service
|
||
list + city is the name-stuffing pattern that gets rich results discarded — on
|
||
the one project whose premise is crawlability… Your reading beat mine; record it
|
||
as the decision, not as a deviation."* `schema.ts` and `docs/04` updated so
|
||
neither reads as pending. **The half that is mitigated rather than answered is
|
||
unchanged and still stated**: `slogan` still carries an unscoped "Arbitration".
|
||
|
||
### §7 — the `us-east-1` SES identity is being deleted, and the reason generalises
|
||
|
||
Pouya, on the `AWS_SES_DKIM_PENDING_TO_FAILED` health event of 2026-08-29 — the
|
||
expected outcome of DKIM CNAMEs that never resolved: **that is its third
|
||
false-alarm signal**, after the pending console dashboard and the near-miss on
|
||
requesting production access in the wrong region. His reason, recorded because it
|
||
is a monitoring principle rather than a cleanup note: *"A monitoring surface that
|
||
reports a failure you do not have trains you to discount the ones you do."*
|
||
`ca-central-1` re-verified by DNS the same day — all three live DKIM records
|
||
NOERROR, SPF and DMARC present — which is what makes "no impact" a result rather
|
||
than an assumption. Deletion removes the identity, not the records.
|
||
|
||
### R11 at the step 4 → 5 phase boundary — one pin is a major behind, deliberately
|
||
|
||
`npm view` run across all fourteen pins. Thirteen are current. **`typescript` is
|
||
pinned `^6.0.3` and latest is `7.0.2`** — one major behind, which is the exact
|
||
shape D1 was amended over, so the reason is recorded in §7 rather than left
|
||
silent: `@astrojs/check@0.9.10` declares `peerDependencies: { typescript:
|
||
'^5.0.0 || ^6.0.0' }`, and `astro check` is the type gate both deploy paths run.
|
||
**Removal trigger: `@astrojs/check` widens the range.** A hold on a dependency's
|
||
schedule, not on a judgement.
|
||
|
||
### Build step 5 — `/practice/` and the six area pages
|
||
|
||
Seven pages, 688–1,129 words each, zero JavaScript, one `<h1>` each, no skipped
|
||
heading levels. `/practice/<area>/` is **one route over a data file**, declared
|
||
`satisfies Record<PracticeSlug, PracticePage>` — so an area in the nav with no
|
||
page, or a page with no area, does not compile. `docs/01` calls the namespace
|
||
stable; that is what keeps it one.
|
||
|
||
**First `BreadcrumbList` on the site**, with a new `Breadcrumbs.astro`. docs/04
|
||
requires the markup to match the visible trail, so **one array feeds both** and
|
||
the match was verified by parsing the built HTML against the built JSON-LD on all
|
||
six pages, not by reading the source.
|
||
|
||
The `/practice/` **"also offered" strip ships** — ENE, dispute-system design,
|
||
pre-dispute technical advisory (Q46(a)). Both framing constraints are honoured:
|
||
ENE is described as an assessment delivered to **both parties together** and
|
||
never as advice to one, and the **conflict caution on pre-dispute advisory has
|
||
its own paragraph** rather than a clause inside a grid cell, because a caution a
|
||
reader has to find is a caution that was not given. Settlement counsel is not
|
||
there and is not coming back. Nothing on the page describes gate 1 as settled
|
||
law.
|
||
|
||
`NEUTRAL_ROLE_LINE` is extracted to `site.ts` — docs/03 predicted `/practice/`
|
||
would be the second place that sentence was needed and was right; a hand-typed
|
||
second copy of the sentence that took three attempts and two audits is the
|
||
highest-consequence drift available.
|
||
|
||
### Sourcing the six pages found three facts that were already wrong
|
||
|
||
A twelve-agent fan-out fetched primary sources for every external fact these
|
||
pages would state, with an adversarial pass over each extract asking only whether
|
||
the pasted quotations actually support the claims drawn from them. Six extracts
|
||
are committed to `docs/reference/` (R14), each carrying its sources, its verbatim
|
||
quotations, **what it does not establish**, and the overreach the adversarial
|
||
pass found in it. **Three of the findings were about material this repository
|
||
already held.**
|
||
|
||
**1. The LAT mediation gloss — WRONG, and it was on three shipped pages.**
|
||
`docs/reference/lat-case-conference.md` quotes the Tribunal's passage **verbatim
|
||
and correctly**. The sentence *underneath* the quote read: *"The Tribunal itself
|
||
points parties at private mediation, before filing and continuing after
|
||
filing."* Read the passage again: sentence 1 names **mediation**, for one moment
|
||
only — *"Before you apply."* Sentence 2 is about **negotiation** — *"Parties are
|
||
encouraged to attempt to **negotiate** the claim at all times, including before
|
||
filing… and continuing **negotiation** discussions after a claim has been
|
||
filed."* The word appears twice. The gloss carried the after-filing frame across
|
||
onto mediation, and added the word "private", which is not the Tribunal's.
|
||
|
||
`docs/01` then quoted the passage **with an ellipsis that deleted the second
|
||
"negotiation"** — the word that scopes the clause — which made the quotation
|
||
appear to support the gloss. And the published blurb, *"private mediation
|
||
alongside a LAT application, **before filing or after**"*, rested entirely on the
|
||
elided half. It shipped on `/`, `/mediation/` and would have shipped on
|
||
`/practice/`.
|
||
|
||
**The defect was in a gloss beneath a correctly-quoted source**, which is why two
|
||
review rounds and a claims audit read that file and passed it: the quote was
|
||
right there and appeared to say it. Caught by an independent re-fetch that read
|
||
the sentence structure. **Same shape as Q39's struck universal** — the source was
|
||
fine and the sentence drawn from it was wider than the source.
|
||
Corrected in the extract (correction box), `docs/01`, `src/data/site.ts` and §9
|
||
Q41(c). Now published: *"private mediation retained by the parties, not the
|
||
Tribunal's case conference"* — the distinction `docs/01` actually requires, and
|
||
fully supported. `/practice/insurance/` quotes the Tribunal's real sentence and
|
||
says in terms that it is quoted no wider than it goes.
|
||
|
||
**2. "Connection allocation" is not an Ontario term — also on three shipped
|
||
pages.** `docs/01` §`/practice/energy/` and `site.ts`'s energy blurb both used
|
||
it. The IESO's connection-process pages contain **zero** occurrences of
|
||
"allocation" of any kind. The real terms are *connection assessment and approval
|
||
(CAA)*, *System Impact Assessment (SIA)* and *Customer Impact Assessment (CIA)* —
|
||
and **Ontario has no interconnection queue**; the IESO says so in terms and works
|
||
from "committed projects". The genuinely adjacent term, the OEB's *Capacity
|
||
Allocation Model*, is about housing-development connections and is a different
|
||
thing. Same failure as "Model Mediation Rules": an institution's own vocabulary,
|
||
written from recall.
|
||
|
||
**3. "The 2026 privacy statute" does not exist.** `docs/03` §Practice areas
|
||
listed it among the market context for `/practice/technology/`. **Nothing
|
||
enacted federally or in Ontario in 2025 or 2026 is a privacy statute.** Bill C-27
|
||
— the Consumer Privacy Protection Act and the Artificial Intelligence and Data
|
||
Act — **died without royal assent** and was never reinstated. PIPEDA remains the
|
||
operative federal statute and **Canada has no federal AI statute.** Struck from
|
||
`docs/03` rather than corrected in place, so the phrase is not re-invented.
|
||
**Caught before a word of it reached a page**, and only because the phrase was
|
||
checked rather than trusted.
|
||
|
||
**4. "Prescribed training" is the wrong word for the family-arbitration hours** —
|
||
record only, gates nothing. **No hour figure appears anywhere in O. Reg. 134/07,
|
||
in any version.** Section 3 requires *"the training approved by the Attorney
|
||
General"* as set out on a Government of Ontario website: the **requirement** is
|
||
prescribed, the **content** is delegated to a web page. Corrected in §4 where the
|
||
reasoning is relied on, and **deliberately left standing as shorthand in four
|
||
other files** — rewriting them to sharpen a phrase that gates nothing is the
|
||
record-about-the-record work D19 exists to stop.
|
||
|
||
**And one thing the sourcing unblocked:** ADR Chambers is now **named on
|
||
`/arbitration/`**. `docs/01` item 3 listed it and the page omitted it because
|
||
nothing sourced what rules it publishes. It does now — ADR Chambers Arbitration
|
||
Rules, Mediation Rules and Expedited Arbitration Rules, under those exact titles.
|
||
**No edition date is published for them, deliberately**: the rules provide that
|
||
ADR Chambers may amend them in its sole discretion effective on posting, so a
|
||
date on the page would go stale without notice, which is a worse claim than none.
|
||
|
||
### Defects I found in my own step-5 work before the reviewers reported
|
||
|
||
1. **Two adjacent sections on the same ground, on all six area pages** — the
|
||
dispute-types section is fixed `alt` and every page's first declared section
|
||
was also `alt`, so each rendered as one doubled tinted block with a heading
|
||
floating in it. **`/med-arb/` had the cream-on-cream form of the same defect,
|
||
introduced by this session's own new section.** Found by extracting the
|
||
section classes from the built HTML, not by reading the source.
|
||
**Fixed, and then made a build error**: `[slug].astro` now throws on any two
|
||
adjacent grounds, checking the declared array against the fixed section at
|
||
each end. Proven by sabotaging one value and reading the failure. This is the
|
||
same lesson as `check:claims` — I had written a comment arguing that declaring
|
||
grounds explicitly was safer than computing them, and then got the
|
||
declarations wrong on six pages in the same file.
|
||
2. **"Two Ontario government consultations… were open"** — ERO 025-1001's comment
|
||
period **closed 4 November 2025**; only 026-0853 was open. The extract's own
|
||
`established` line said "two live consultations" while the notice data quoted
|
||
three sections above it read **"Closed"**. I copied the extract's overreach.
|
||
Corrected on the page and in the extract.
|
||
3. **The MIG contrast** — I wrote that the monetary limit *"sits in section 18 of
|
||
the Schedule itself rather than in the Guideline."* The extract's own
|
||
adversarial pass had flagged exactly that phrase: the Guideline's text was
|
||
never retrieved, so the negative half is unsupported. Rewritten to the
|
||
positive form.
|
||
4. **"Underserved by senior neutrals"** (insurance lede) — an unverifiable
|
||
comparative claim about other practitioners. Q41(b) is directly on point:
|
||
*"assert his capability, not the field's incapability."* Removed.
|
||
5. **"Most of which resolve"** (insurance context) — a settlement-rate
|
||
characterisation, which §4 Forbidden bars outright and which the extract
|
||
expressly warned against drawing from the combined settled/withdrawn row.
|
||
Removed.
|
||
6. **"The second half is the one that is rare"** (construction) and **"a material
|
||
share of technology disputes"** (technology) — a comparative about the field
|
||
and an unsourced quantified claim. Both rewritten. **"The only answer"** on
|
||
`/med-arb/` softened for the same reason.
|
||
|
||
7. **Statute stated wider than the statute.** Three, all caught by re-reading
|
||
the shipped text against the committed extract rather than against my memory
|
||
of writing it:
|
||
**(a)** `/practice/energy/` said leave to construct bites on a line *"over a
|
||
prescribed length"*. **There is no length in s. 92(1)** — the 2 km threshold
|
||
and the outright distribution carve-out are exemptions in O. Reg. 161/99.
|
||
**(b)** `/practice/shareholder/` said an OBCA s. 108(6)(b) clause means the
|
||
matter *"goes to arbitration"* and *"the forum is already chosen"*. The
|
||
provision is permissive twice over — an agreement **may provide** that a
|
||
matter **may be referred** — and the second clause was a legal conclusion
|
||
applied to the reader's own file, three lines above a note saying the page
|
||
does not do that.
|
||
**(c)** *"Both statutes also provide for winding up"* — the CBCA's s. 214 is
|
||
liquidation and dissolution. Reworded to cover both.
|
||
8. **"No Canadian statute requires data to be stored in Canada"** — a class
|
||
statement wider than the check behind it. The extract's own *"does NOT
|
||
establish"* section records that **BC's FIPPA and Nova Scotia's PIIDPA
|
||
public-sector residency provisions were not checked.** Scoped to "no federal
|
||
or Ontario statute", which is what was read. **This is Q39's shape exactly**,
|
||
in a change set whose own copy warns about it.
|
||
9. **Three smaller ones.** *"I build and operate these systems, and I have done
|
||
while running this practice"* — a concurrency claim §4 does not row and that
|
||
`/about/` had already removed once. *"Three engagements that are not
|
||
appointments"* — loose for ENE, which is delivered to the parties as a
|
||
neutral. And a consultation described in the past tense while it was still
|
||
open, rewritten to a date that stays true.
|
||
|
||
### The code review — 5 findings, two blocking, and the first one is mine
|
||
|
||
**BLOCKING 1 — `npm run check` was FAILING, and I reported it as passing four
|
||
times.** `astro check` exited **1 with 10 `ts(2339)`/`ts(7053)` errors** in
|
||
`[slug].astro`. Both deploy paths run `npm run check` before the build, so
|
||
nothing could have shipped.
|
||
|
||
**How I missed it is the finding, and it is a new `CLAUDE.md` convention.** I ran
|
||
`npm run check 2>&1 | tail -3`. The verdict prints as `- N errors`, `- N
|
||
warnings`, `- N hints`, followed by a blank line — so `tail -3` returns
|
||
**warnings, hints and the blank line, and drops the errors line.** Four runs,
|
||
four "0 warnings / 0 hints", zero sight of the number that mattered. **The
|
||
truncation only ever hides bad news, because the error line comes first.** This
|
||
is the stderr rule's twin — `2>/dev/null` turns "it failed" into "it found
|
||
nothing"; `| tail -3` turns "10 errors" into a clean bill — and it is easier to
|
||
commit, because the command really did run. **The fix is not a bigger `tail`: it
|
||
is reading the exit status**, which is the one signal a pipe cannot reshape.
|
||
Written into `CLAUDE.md` under Conventions.
|
||
|
||
**The cause was `as const satisfies Record<...>`.** `as const` fixes the declared
|
||
type as the literal object and `satisfies` does not widen it, so `page.sections`
|
||
became a heterogeneous tuple whose members genuinely lack the optional keys they
|
||
omit — `ground`, `lede`, `note`, `lead` all errors on the members that omit them.
|
||
`astro build` does not typecheck, **so `dist/` was green while the gate was
|
||
red.** Fixed by annotating instead, and the completeness guarantee was
|
||
re-verified by probe rather than assumed: renaming `energy` to `energyy` still
|
||
fails with `ts(2561) 'energyy' does not exist in type Record<...>`.
|
||
|
||
**BLOCKING 2 — the "also offered" labels rendered at 3.07:1.** `/practice/` is
|
||
the first page on the site to put `DefinitionGrid` on an inverse ground, and its
|
||
`<dt>` takes `--text-meta`, which is `--muted` — the token `tokens.css` marks
|
||
**"ON CREAM ONLY (3.07:1 on ink)"** and which `SiteFooter.astro` already records
|
||
the same prohibition for. Measured three independent ways by the reviewer (token
|
||
arithmetic, `getComputedStyle` against the served build, and a screenshot), all
|
||
agreeing; I reproduced 3.07:1 from the tokens myself before fixing. **The rule
|
||
was written down in two places and this change set breached it anyway** — which
|
||
is precisely Pouya's point about prose in comments. Fixed through the custom
|
||
property route the project already uses for `Pill`: `--def-name-fg`, set beside
|
||
`--pill-fg` in `global.css` and in the forced-colors block. **11.09:1 now, and
|
||
verified in the shipped bytes** rather than the source.
|
||
|
||
**SHOULD-FIX — `var(--text-primary)` does not exist.** I invented a token name in
|
||
`Breadcrumbs.astro`. An undefined custom property makes the declaration invalid
|
||
at computed-value time, so the current-page crumb and the link hover both fell
|
||
back to inherit and rendered identically — the trail's current item visually
|
||
indistinguishable from its links. The silent-no-op form of the tokens-only rule,
|
||
and the same family as the parent-scope trap: a rule that looks right in source
|
||
and never matches. `--text` is the token.
|
||
|
||
**SHOULD-FIX — six titles had dropped the practitioner's name.** `docs/04`'s
|
||
pattern is `"<Page> · Pouya Lajevardi"` with exactly one named exception
|
||
(articles, for a stated length reason). All six area titles omitted it, and the
|
||
string propagates to `og:title` and `twitter:title` — **six of twelve social
|
||
previews carrying no name, on a site whose entire strategy is a practitioner
|
||
brand.** Appending the suffix overruns the 60-char ceiling, so all six were
|
||
rewritten; every one now falls in 52–57.
|
||
|
||
**SHOULD-FIX — comments longer than the code they explain (D19).** Counted, not
|
||
estimated: `Undertaking.astro` at 35 comment lines to 20 of code; two 23–24 line
|
||
JSDoc blocks on 6-line functions in `schema.ts`; ~43 lines of comment on two
|
||
two-line strings in `site.ts`. Accepted and trimmed — **the constraints stay,
|
||
the revision narratives go to this entry, which is where a reader looks for how
|
||
something got here.** What was explicitly kept: the `serviceType` union
|
||
rationale, the `memberOf` opt-in warning, and `Undertaking`'s note that deleting
|
||
the `Props` interface re-disables call-site type checking — the reviewer probed
|
||
that last one (`<Undertaking bogusProp={1}>` does error) rather than taking the
|
||
comment's word for it.
|
||
|
||
**Nothing was declined in either round-1 report.** All eleven findings were real.
|
||
|
||
### What the code review found CLEAN, stated so the gaps are auditable
|
||
|
||
Zero `client:*` directives and zero JS in `dist/` (the only `<script>` tags are
|
||
twelve `application/ld+json`); unique title, 149–160 char description, canonical,
|
||
full OG/Twitter set and `robots index,follow` on all seven new pages; sitemap
|
||
carries all twelve URLs; JSON-LD parses everywhere; `BreadcrumbList` 1-based and
|
||
matching the visible trail name-for-name and URL-for-URL; one `<h1>` per page and
|
||
no skipped levels; breadcrumb and onward links measured ≥44px at 390 and 1280;
|
||
no base64-inlined images; pages 23–26 KB, CSS 24.8 KB total. **Overflow
|
||
re-measured at 320/360/390 with root font 16 and 32 — 0/0/0 and 63/23/0,
|
||
byte-identical to `docs/02`'s recorded site-wide floor, so no regression;** the
|
||
overflowing elements are the pre-existing header and footer brand.
|
||
|
||
### The claims audit — 6 findings, all accepted, and it caught a hole in `check:claims` itself
|
||
|
||
**It also independently found five of the defects listed above** — the LAT
|
||
"underserved", the resolution-rate inference, the MIG contrast, the s. 92
|
||
"prescribed length" and the s. 108(6) "the forum is already chosen" — verified
|
||
each against the live tree, found them already gone, and **reported only what
|
||
still shipped.** That is the right behaviour and it is worth recording: the diff
|
||
it was handed had gone stale under it, and it said so rather than reporting
|
||
fixed defects as live ones.
|
||
|
||
1. **BLOCKING — `/practice/energy/` asserted a connection queue on a card while
|
||
denying one 600 words below.** The dispute-type card read *"The connection
|
||
queue behind a data centre or other large load"*; the same page states *"the
|
||
IESO … does not use an interconnection queue."* **The word was corrected out
|
||
of `site.ts` and `docs/01` in this same change set and survived one card
|
||
over** — the incomplete-sweep shape this record has now paid for four times.
|
||
Fixed: "the connection assessment behind a data centre or other large load".
|
||
2. **BLOCKING — `/practice/cross-cultural/` shipped the election phrasing D13
|
||
bars.** *"What I do not do is advise on the law of another country."* Attempt
|
||
1 of docs/03's worked example, **narrowed by jurisdiction, which makes it
|
||
worse**: naming only foreign law invites the reader to supply the domestic
|
||
half. Already fixed on a self-audit minutes before the report landed; the
|
||
auditor found it independently.
|
||
**AND IT NAMED A HOLE IN `check:claims`, WHICH IS THE MORE VALUABLE HALF:**
|
||
the capacity pattern required the literal object *"legal advice"*, so
|
||
*"advise on the law of another country"* passed the mechanical gate. **The
|
||
pattern is widened** — a first-person negation within 25 characters of
|
||
give / provide / offer / advise / render — and the real sentence is now a
|
||
fixture. **The six approved first-person negations this site ships are all in
|
||
`mustNotMatch`**, including undertaking (c)'s *"If I cannot decide a remaining
|
||
issue…"*, which is the nearest miss. Proven by re-injecting the actual
|
||
sentence into a built page: it is caught.
|
||
3. **SHOULD-FIX — "I work with diaspora business communities."** §4 rows
|
||
*"cross-cultural fluency with diaspora business communities"*, not a client
|
||
relationship. **`/about/` had already solved this exact row** with wording
|
||
chosen to carry no quantity and no comparative, and the new page had reverted
|
||
past it. Fixed to `/about/`'s formulation.
|
||
4. **SHOULD-FIX — ADR Chambers: a class asserted from one instance.** The page
|
||
said the firm *"amends them"* — all three rule sets — at its discretion on
|
||
posting. The extract establishes the self-amendment clause for the
|
||
**arbitration rules only**; it carries a different provision for the mediation
|
||
rules and quotes nothing from the expedited rules on amendment. Scoped.
|
||
Naming ADR Chambers at all was unblocked by this session's sourcing, and the
|
||
first thing that happened was an overreach about it.
|
||
5. **CONSIDER, accepted — "what happens to a business while its owners
|
||
litigate"** offered as familiar from a row that verifies operating a company.
|
||
Knowledge of a shareholder dispute is not knowledge of running a company, and
|
||
§4 rows only the second. Replaced with an operating fact.
|
||
6. **CONSIDER, accepted — "These are commercial mediations and arbitrations,
|
||
conducted from Toronto"** reads as a body of arbitrations already conducted.
|
||
§4 records **no completed arbitration** — the row that made `claims-auditor`
|
||
strike *"Mediator and Commercial Arbitrator"* from the Person node on
|
||
2026-08-27. Reframed forward: "These run as…".
|
||
|
||
**Nothing was declined.** All six were real.
|
||
|
||
### Round 2 — 9 findings, all accepted, and four are defects the FIXES introduced
|
||
|
||
**Round 2's job is the repairs, and it earned itself.** Four of the nine did not
|
||
exist before round 1's fixes were written.
|
||
|
||
**Both reviewers found the same defect independently, and it is the one that
|
||
mattered:** `/practice/insurance/`'s JSON-LD offered **`serviceType:
|
||
['Mediation','Commercial arbitration']`** on a page whose `<h1>` reads *"Private
|
||
mediation, not the Tribunal's case conference"*, whose body recites Insurance Act
|
||
s. 280 exclusive jurisdiction, and in whose visible copy the word *arbitration*
|
||
appears only in the site header, the footer and the shared onward strip.
|
||
`practiceAreaGraph` hard-coded both processes for all six areas. **docs/04's own
|
||
principle is that structured data represents the page it sits on** — the reason
|
||
`/`'s Person node omits `memberOf` — and this is the same failure family as the
|
||
Person `description` carrying *"Mediator and Commercial Arbitrator"*, struck
|
||
2026-08-27. There is a second edge: §4 scopes every arbitration row to
|
||
**commercial**, and a SABS entitlement dispute is statutory. **Fixed per area:**
|
||
`serviceType` and a `serviceLabel` now come from the page data, the union still
|
||
constrains every member, and `/practice/insurance/` emits `serviceType:
|
||
"Mediation"` and `name: "Mediation — Insurance, SABS & LAT"`.
|
||
|
||
**Introduced by a fix — 1.** *"The Tribunal's own materials point parties toward
|
||
**it**"*, where the antecedent is *private mediation*. The extract corrected
|
||
earlier the same day says in terms: **"the word 'private' is not the Tribunal's
|
||
either — the sentence names no provider."** The note under that section closed
|
||
the *temporal* half of the old gloss and left the *provider* half open. **The
|
||
residue of the very gloss this change set corrected, re-entering through copy
|
||
written in the same change set.** Now: *"point parties toward mediation"*.
|
||
|
||
**Introduced by a fix — 2.** `[slug].astro`'s header still said `PRACTICE_PAGES`
|
||
is declared **`satisfies Record<…>`** — the exact construct round 1 removed for
|
||
producing the 10 errors. Two records in the same change set disagreeing about the
|
||
same declaration, and the one a reader hits first was the wrong one. The
|
||
reviewer re-proved the guarantee itself with an isolated `tsc --strict` probe
|
||
before reporting only the mechanism as false.
|
||
|
||
**Introduced by a fix — 3.** `/med-arb/` stated undertaking (a) **three times in
|
||
250 words**: the FAQ answer's tail, the `<h3>`, and the undertaking. Measured —
|
||
*"on the day because the room has run out of road"* occurred twice, 241 words
|
||
apart. **The replace-don't-duplicate judgement was applied on `/arbitration/` and
|
||
not one file over**, which is this project's signature failure. The FAQ tail is
|
||
trimmed and the `<h3>` reframed to *"Agreed first, or not at all."*; the
|
||
undertaking is untouched, because softening it is a change to a published
|
||
commitment.
|
||
|
||
**Introduced by a fix — 4.** The round-1 fix added a **15-line comment narrating
|
||
its own revision history** to explain a one-line type annotation. A direct D19
|
||
breach, inside the fix for a D19 finding. Cut to four lines: the constraint, and
|
||
a pointer to this entry.
|
||
|
||
**`check:claims` had a second hole, of the shape round 1 found the first.**
|
||
`\bmy clients\b` does not match **"my client"**, and `/med-arb/` was shipping
|
||
*"The neutral who heard my client in caucus"* in its FAQ and in the `FAQPage`
|
||
node. The possessive belonged to the counsel voicing the objection rather than to
|
||
Pouya — **which is exactly why it needed a decision rather than a silent gap.**
|
||
The copy now reads *"our client"*, the pattern is `\bmy clients?\b`, and both
|
||
edges are fixtures. **And the widened capacity pattern was narrowed in the same
|
||
pass:** it carried `offer`, which fires on *"I do not offer family arbitration"*
|
||
— an offering statement, not a capacity claim. The second alternative is now
|
||
`advise|advising` only; `give`/`provide`/`offer` are covered by the first, which
|
||
requires the literal object.
|
||
|
||
**Two more accepted.** *"Interconnection study"* is not a document any Ontario
|
||
body publishes — the IESO's is the **system impact assessment**, and the IESO
|
||
rejects the adjacent import *interconnection queue* in terms. **This is the
|
||
"connection allocation" defect again**, missed because the sweep that morning
|
||
looked for that phrase and not this one; swept from `/practice/`, `/mediation/`
|
||
(pre-existing from step 4) and the page data, and the two surviving matches in
|
||
`dist/` were read: OEB Act s. 92(1)'s *"or make an interconnection"* and the
|
||
IESO's own denial. And `/mediation/` §Confidentiality had been left setting an
|
||
**opt-out** caucus default one paragraph above an **opt-in** undertaking; the
|
||
framing paragraph moved, the undertaking did not.
|
||
|
||
**One CONSIDER accepted on 40% stated confidence** — `/practice/shareholder/`'s
|
||
*"the operating half of a shareholder dispute is familiar rather than abstract"*
|
||
attached shareholder-dispute events to him from a row that verifies operating a
|
||
company. Now *"the operating consequences … are legible rather than abstract"*.
|
||
|
||
**One CONSIDER carried, not fixed, and recorded as a judgement:** *"Or ADR
|
||
Chambers"* on `/arbitration/`. The reviewer's point is that the new source
|
||
establishes the rule sets' **names** — which is what the R14 hold was about — but
|
||
not that this practice can run an arbitration under them, and ADR Chambers' own
|
||
model clause reads *"at ADR Chambers"*. **Held because `docs/01` item 3 lists ADR
|
||
Chambers as one of this page's three rule options on the architect's own outline,
|
||
and the sentence asserts only what the firm publishes plus generic contract
|
||
advice.** If Pouya reads the placement as implying availability, one clause
|
||
reframes it as a rule set a contract may name. Flagged to him rather than
|
||
decided here.
|
||
|
||
**THE LOOP STOPS AT TWO ROUNDS — D19, and the reasoning is stated so a later
|
||
reader does not read the cap as laxness.** Round 1 reviews the change; round 2
|
||
reviews the fixes. Four of round 2's nine were defects in round 1's fixes, which
|
||
is exactly why round 2 exists — and it is also why round 3 does not: past two,
|
||
the manufacture rate exceeds the value of the marginal finding. Pouya's ruling,
|
||
2026-08-28, on 48 findings across two rounds.
|
||
|
||
### Verified — run, and the exit status read this time
|
||
|
||
```
|
||
npm run check exit=0 - 0 errors, 0 warnings, 0 hints (32 files)
|
||
npm run lint exit=0 eslint + prettier
|
||
npm run build exit=0 0 [ERROR] lines, 12 pages
|
||
npm run check:claims exit=0 10 patterns, self-test green, 12 pages
|
||
grep -rE 'animation:[^;}]*(scroll\(\)|view\(\))' dist exit=1 (no hits — clean)
|
||
```
|
||
|
||
Measured rather than asserted, each against the built output:
|
||
|
||
- **Zero JavaScript.** The only `<script>` tags in `dist/` are twelve
|
||
`application/ld+json`. The pages render their full content with JS disabled
|
||
because there is none to disable.
|
||
- **Metadata on all twelve pages** — unique `<title>`, one meta description,
|
||
one canonical, seven `og:*`, four `twitter:*`, one JSON-LD block each.
|
||
- **JSON-LD parses on every page**, and the node sets are what `docs/04`
|
||
specifies: `Person` on `/about/` and `/practice/`; `Service` + `Person` on the
|
||
three process pages; `+ FAQPage` on `/med-arb/`; `+ BreadcrumbList` on the six
|
||
area pages.
|
||
- **Breadcrumbs match**, verified by parsing the built HTML against the built
|
||
JSON-LD on all six pages — name-for-name and URL-for-URL, 1-based.
|
||
- **Heading structure** — one `<h1>` per page, no skipped levels, on all twelve.
|
||
- **No two adjacent sections share a ground** on any of the twelve, checked by
|
||
extracting the section classes from `dist/`.
|
||
- **The six undertakings are byte-identical** in `CONDUCT_UNDERTAKINGS`, in §4's
|
||
rows, and in the shipped HTML, each on exactly one page.
|
||
*(The first run of that check reported four as unshipped. It was the harness:
|
||
three files all named `index.html` keyed into one dict entry. Instrument, not
|
||
defect — re-run keyed by full path.)*
|
||
- **Sitemap** carries all twelve URLs.
|
||
|
||
**NOT RUN, stated rather than omitted:** Lighthouse. `@lhci/cli` was removed
|
||
2026-08-26 and is not re-added until build step 7 (R11, §7). The budget stands;
|
||
the instrument is absent. No manual DevTools run was substituted for it.
|
||
|
||
**Internal links that do not resolve yet, and they are the build order, not
|
||
defects:** `/contact/` (49 refs), `/fees/` (28), `/process/` (14),
|
||
`/for-parties/` (12), `/insights/` (12), `/legal/privacy/` (12),
|
||
`/legal/terms/` (12). All are steps 6–10. The state is unchanged from step 4
|
||
except in volume.
|
||
|
||
### Sweeps — the commands and their output (R8)
|
||
|
||
Every remaining match below was read with context. **All of them are
|
||
prohibitions naming the struck form** — a comment or spec note saying *never
|
||
write this* — and `dist/` is clean of all of them, which is what governs.
|
||
|
||
```
|
||
$ git grep -n 'before filing or after' -- src docs/0*.md
|
||
docs/01-architecture.md:452:> restore the "before filing or after" form** — it rested on the elided half.
|
||
src/data/site.ts:619: * application, **before filing or after**", and the comment here justified
|
||
|
||
$ git grep -ni 'connection allocation\|grid connection and allocation' -- src docs/01 docs/03
|
||
docs/01-architecture.md:387:> ⚠️ **"CONNECTION ALLOCATION" WAS THIS SECTION'S WORDING AND IT IS NOT AN
|
||
src/data/site.ts:567: * ⚠️ "CONNECTION ALLOCATION" IS NOT AN ONTARIO TERM, AND THIS BLURB USED IT.
|
||
|
||
$ git grep -n '2026 privacy statute' -- src docs
|
||
docs/03-content-spec.md:299:~~the 2026 privacy statute~~, LAT volumes.
|
||
|
||
$ grep -rn 'Model Mediation Rules' dist --include='*.html'
|
||
(no matches in dist)
|
||
|
||
$ git grep -ni 'anyone may be appointed an arbitrator\|nothing in law gates' -- src
|
||
src/pages/arbitration.astro:19: * Q39's struck universal — "anyone may be appointed an arbitrator in Ontario;
|
||
```
|
||
|
||
### Two non-gating notes, recorded rather than numbered (D19)
|
||
|
||
1. **Two table rows render with the wrong column count**, because they contain
|
||
unescaped `|` inside inline code and GFM splits on it even there — §7's
|
||
`Node` row and §9's `~~Q32-orig~~`. Both predate this change set; the §7 row
|
||
this session added had the same defect and its pipes are escaped (`\|`).
|
||
Checked by counting unescaped pipes per row against each table's header
|
||
across all 17 table blocks — and the first run of that check produced a
|
||
**false positive on the row it had just fixed**, because a naive count
|
||
counts escaped pipes too. Gates nothing, so it is here and not in §9.
|
||
2. **`docs/reference/` is in `.prettierignore` as a "frozen historical
|
||
record", and three extracts in it were CORRECTED this session** — the LAT
|
||
gloss, the energy "two live consultations" line, and the family-arbitration
|
||
hours framing. **No verbatim quotation was touched; only the analysis
|
||
beneath one.** The `.prettierignore` note is about *reformatting*, which
|
||
would obscure what a file originally said, and correcting a wrong gloss is
|
||
the opposite of that. Recorded so a later reader does not read the
|
||
corrections as a breach of the convention — and so the pattern is visible:
|
||
on all three, the quote was right and the sentence under it was wider.
|
||
|
||
|
||
### Open after this entry
|
||
|
||
**The Q-series is down to three, and none of them blocks step 6.**
|
||
|
||
- **Q23** — is a Gitea `act_runner` registered and are Actions enabled? Depends
|
||
on a second administrator, not on a fact to look up. Deploys run locally.
|
||
- **Q34** — the contested measurements of the site being replaced. Nothing in
|
||
public copy cites one.
|
||
- **Q38** — a true vector master for the infinity mark. R13 carries the trigger.
|
||
|
||
**No new numbered question was opened by this change set**, deliberately and per
|
||
D19: everything found here either blocked a page and was fixed, or gates nothing
|
||
and is a note in this entry. The one thing that needed an owner rather than a
|
||
fix became **§12 R18** — the six `docs/reference/` extracts are dated
|
||
2026-08-29 and seven shipped sentences turn on facts that move, Bill C-36 first
|
||
among them. It fires on the same event trigger R10 uses: before any cutover, and
|
||
before any republish that turns on one of them.
|
||
|
||
**For Pouya, three things that are his and not mine:**
|
||
|
||
1. **The Q54 stamp date.** §4 reads `[verified 2026-08-29]`, not the 2026-08-27
|
||
he named, because the drafts did not exist on the 27th. One line changes it.
|
||
2. **R1, surfaced again**, and step 5 gives it a third shape: six pages now
|
||
describe what he does in a subject matter, and `/practice/insurance/` and
|
||
`/practice/construction/` sit closest to the litigation-exposure wording.
|
||
Nothing here asks to change D13.
|
||
3. **The three additions to `check:claims` beyond his minimum list** — the
|
||
fabricated founder, Q.Arb-as-held, and Q39's struck universal. Each names an
|
||
incident in this record. Strike any and the rest stand.
|
||
4. **"Or ADR Chambers" on `/arbitration/`** — the one review finding carried
|
||
rather than fixed. The source establishes what the firm publishes; it does
|
||
not establish that a neutral outside the firm can be appointed under those
|
||
rules, and ADR Chambers' own model clause reads *"at ADR Chambers"*. It is on
|
||
the page because `docs/01` item 3 lists it as one of three rule options on
|
||
your outline. **One clause reframes it** as a rule set a contract may name
|
||
rather than an option on offer, if the placement reads wrong to you.
|
||
|
||
---
|
||
|
||
## 2026-08-28 (aa) — Build step 4: `/mediation/`, `/arbitration/`, `/med-arb/`. ADRIC's rules sourced, and `docs/01` had the wrong name for one of them
|
||
|
||
**Three pages, five in the build, zero JavaScript.** `/arbitration/` carries §4's
|
||
paired-disclosure condition on four surfaces; `/med-arb/` meets the
|
||
procedural-fairness objection at the level of process design and ships
|
||
deliberately **without** Pouya's own protocol commitments, which is **Q54**.
|
||
|
||
### The fetch earned itself before a word of copy was written
|
||
|
||
`docs/01` directed `/mediation/` to name the **"ADRIC Model Mediation Rules"**.
|
||
No such document exists. Measured across all four of ADRIC's rules pages:
|
||
|
||
```console
|
||
$ for f in *.txt; do printf '%-42s Model=%s National=%s\n' "$f" \
|
||
"$(grep -o -F 'Model Mediation Rules' "$f" | wc -l)" \
|
||
"$(grep -o -F 'National Mediation Rules' "$f" | wc -l)"; done
|
||
rules-codes.txt Model=0 National=2
|
||
rules-codes__national-mediation-rules.txt Model=0 National=10
|
||
rules-codes__arbrules.txt Model=0 National=2
|
||
rules-codes__adric-med-arb-rules.txt Model=0 National=2
|
||
```
|
||
|
||
The document's own heading is *"The ADRIC National Mediation Rules"*. **"Model"
|
||
belongs to the Model Dispute Resolution Clause**, a contract clause *inside* the
|
||
rules. This is the `Chartered Mediator-Arbitrator` shape a second time — a wrong
|
||
institutional name sitting in a spec, waiting to be copied onto a public page —
|
||
and it was caught only because R14 requires the source before the claim.
|
||
|
||
`docs/reference/adric-rules.md` + `adric-extract/` carry it, with a difference
|
||
from the ADRIO fetch that is measured rather than assumed: **the HTML digests
|
||
drift on every request** (page-builder class suffix, a rotating sponsor
|
||
carousel, Cloudflare email obfuscation, a challenge token — read out of a diff
|
||
of two fetches three minutes apart) while **the text extracts are byte-stable**.
|
||
So the extracts are the artefact and the digests only record what was fetched.
|
||
|
||
It also turned up the **ADRIC Med-Arb Rules**, which `docs/01` did not know
|
||
about, and corroborated `Chartered Med-Arbitrator` from a second body.
|
||
|
||
### What the four review passes found — 21 defects, and the pattern is mine
|
||
|
||
**The gate I built, breached four times.** `/med-arb/`'s header comment states
|
||
the rule — a first-person commitment about how Pouya runs an engagement is a
|
||
claim about his practice with no §4 row — and a `TODO(pouya)` sits ten lines
|
||
above it. The page then shipped *"What I will not do is agree to one where the
|
||
parties have not settled the switch in writing first"*, which is Q54(a). Three
|
||
more shipped on the neighbouring pages. Both agents found it independently.
|
||
Round 2 then found **two survivors of round 1's own fix**: *"I will work from a
|
||
bespoke protocol"* on `/mediation/`, and *"carry what I am given to carry"* —
|
||
Q54(d) in compressed positive form, in the hero lede.
|
||
|
||
**Three that would have reached a public page:**
|
||
|
||
- **`<title>`: "Arbitration · Pouya Lajevardi · Sole Arbitrator · Toronto"** —
|
||
`Name · Role · City` is a designation strip, and §4 grants exactly one
|
||
practised role. It is the form struck from `jobTitle` and `description` the
|
||
day before, reintroduced in the one string a search result renders. Now
|
||
*"Commercial Arbitration · Pouya Lajevardi · Toronto"*.
|
||
- **"Every award I issue"** — a habitual presupposing awards issued, where the
|
||
register records none. Now *"An award should be…"*.
|
||
- **"The rules are a starting point. They are not a constraint on how the day is
|
||
run"** — a claim about what ADRIC's rules permit. `adric-rules.md` Finding 4,
|
||
written the same hour, says the fetch reached landing pages and supports **no
|
||
statement of what any rule requires or permits**. The constraint was written
|
||
and then crossed two files later.
|
||
|
||
**And the arb-med definition survived being fixed.** *"the order of the phases is
|
||
the whole difference"* was replaced with *"the phases run in a different order"* —
|
||
which, on a page that defines med-arb as mediation→arbitration, **still defines
|
||
arb-med, by inversion**. The differentia is gone entirely now.
|
||
|
||
### Two instrument failures, caught before they became conclusions
|
||
|
||
Both mine, and both would have produced confident wrong numbers.
|
||
|
||
1. **Touch targets measured over `file://`** returned a uniform **18 px** —
|
||
including on a `.btn` carrying a 44 px floor. `file://` cannot resolve
|
||
`/_astro/…`, so **the page had no CSS at all**. Re-run over HTTP with the
|
||
instrument validated first (2 stylesheets, `.btn` = exactly 44 px, cream
|
||
background), the real numbers matched `adversarial-reviewer`'s to the pixel.
|
||
2. **`validator.schema.org` returned 0 warnings for every page**, including one
|
||
with a known-bad field. The response said `fetchError: NOT_FOUND`,
|
||
`numObjects: 0` — the wrong parameter name, so nothing was ever parsed.
|
||
Calibrated against a deliberately invalid probe (`Service` +
|
||
`availableLanguage` → 2 `UNKNOWN_FIELD`), the real result was **3 out-of-domain
|
||
fields on `/` and one on each new page**.
|
||
|
||
`availableLanguage` is removed from `Service` **and** from
|
||
`ProfessionalService` — the same defect existed on `/` and fixing it next door
|
||
while leaving it in place would have been worse. `serviceType` and `provider`
|
||
remain out of domain on `ProfessionalService`; they carry real information, the
|
||
modelled fix is a different node shape, and it is recorded in `schema.ts` for
|
||
the step-7 SEO pass rather than left as folklore.
|
||
|
||
⚠️ **The post-fix validator re-run on `/` is NOT RUN** — Google returned HTTP 302
|
||
to `/sorry/` (rate limited) mid-verification. What is verified by reading `dist`
|
||
is that the field is gone from all five pages.
|
||
|
||
### Structural changes the review produced
|
||
|
||
- **`DefinitionGrid.astro`** — `/mediation/`'s `.formats` and both of
|
||
`/arbitration/`'s `.cols` were one component under two names, with `.cols`
|
||
already serving two content types on one page. `/practice/*` wants it a fourth
|
||
time.
|
||
- **`.grid-autofit` in `global.css`** — five copies of the same five-line comment
|
||
explaining five identical declarations, plus a sixth differently-worded copy on
|
||
`/about/`. One home for the `min(Nrem, 100%)` guard and its measurement.
|
||
- **`/arbitration/`'s `.arc*` renamed to `.stage*`** — the names collided with
|
||
`/about/`'s `.arc` block, which renders differently, and one of the two rules
|
||
was dead on arrival because Astro's scoping kept them apart.
|
||
- **`serviceType` is a union type**, not a `string`. Four lines of comment asking
|
||
a caller not to pass an unscoped `"Arbitration"` became a build error.
|
||
- **`CREDENTIALS.goalName`** — the designation name that was wrong on a public
|
||
page last week is now read from the constant on both new pages instead of
|
||
hand-typed a third and fourth time.
|
||
|
||
### Measured, not asserted
|
||
|
||
Reflow at a 200% default font size (root 32 px), validated instrument, over HTTP:
|
||
|
||
| root 32px | 320 | 360 | 390 | 414–1024 |
|
||
|---|---|---|---|---|
|
||
| `/mediation/` | 63 | 23 | 3 | 0 |
|
||
| `/arbitration/` | 63 | 23 | 3 | 0 |
|
||
| `/med-arb/` | 63 | 23 | **0** | 0 |
|
||
|
||
Identical before and after the grid refactor, so it changed no rendering. At the
|
||
**default** root, 0 at all eleven widths. Touch targets: `/arbitration/` and
|
||
`/med-arb/` have **no** link under 44 px; `/mediation/`'s six are the
|
||
`PracticeCard` chips, whose real hit area is the **342 × 284 px** card via
|
||
`::after { inset: 0 }` — measured, and byte-identical to `/`.
|
||
|
||
`docs/02`'s 1280 px figure was **`/`-only and generalised**: every non-home page
|
||
measures **944**, because `SiteHeader` gates the tagline on `!isHome`. `/about/`
|
||
was already 944 when it joined that table. Corrected there.
|
||
|
||
Em-dashes per 1000 words: `/med-arb/` 13.3 → **3.8**, now the lowest of the four
|
||
content pages (`/about/` 8.2). Second person on `/arbitration/` 7 → 3, the
|
||
remainder being procedural (*"whatever your contract names"*) plus the shared
|
||
`ContactBand` line that `/` and `/about/` also carry.
|
||
|
||
### Verified
|
||
|
||
`npm run check` 0/0/0 · `eslint` + `prettier` clean · 5 pages · **0 `.js`** ·
|
||
non-JSON-LD `<script>` **0** · minifier guard **0**, `animation-timeline` **5**
|
||
surviving · one `<h1>` per page, no skipped levels · `Chartered
|
||
Mediator-Arbitrator` **0** in `dist` · `TODO(pouya)` **0** in `dist` · JSON-LD:
|
||
`Service` with scoped `serviceType` and `provider` resolving in-document,
|
||
`FAQPage` built from the same array the page renders (3/3 questions and answers
|
||
exact-match), no `BreadcrumbList`, no `worksFor`, no `memberOf` off `/about/`.
|
||
|
||
**NOT run:** Lighthouse — tool unavailable until step 7 (R11). HTML validator.
|
||
The `/` schema.org re-run — rate limited, stated above.
|
||
|
||
### Round 2 found four more, and two were defects in round 1's fixes
|
||
|
||
D19's cap exists for exactly this, and it showed up in the change set that
|
||
introduced D19.
|
||
|
||
- **`DefinitionGrid` re-implemented the guard the extraction removed.**
|
||
`.grid-autofit` uses `--grid-min`/18rem; the new component wrote its own
|
||
`minmax(min(var(--def-min), 100%), 1fr)` with a different variable and a
|
||
different default. A correction to the guard would have reached five call
|
||
sites and silently missed three — the exact failure the extraction was
|
||
justified by, reintroduced inside the extraction.
|
||
- **`.stage-item` matched no CSS rule at all.** Dead markup on three list items,
|
||
where `/about/`'s `.arc-item` counterpart carries a real rule. Removed.
|
||
- **Second person, four instances**, on two pages where `/` and `/about/` have
|
||
zero — and `docs/01`'s new annotation *quoted* one of them, so one in-scope
|
||
spec recorded the phrasing another in-scope spec bars. All five pages now
|
||
measure **0** excluding the shared `ContactBand` line.
|
||
- **`PublishableServiceType`'s comment said its members are §4's rows
|
||
"verbatim".** They are `docs/04`'s strings; §4's rows read *"Arbitration —
|
||
sole arbitrator (commercial)"*. An implementer widening the union "verbatim
|
||
from §4" would write the unscoped `Arbitration` the union exists to bar — in
|
||
the comment that **is** the gate.
|
||
|
||
**And it caught a number of mine that does not reproduce.** `docs/02`'s new
|
||
block said the element sweep names *"six `PracticeCard` chips"*. Re-run: **three**
|
||
(`right > clientWidth` — Construction, Technology, Shareholder). Six is the count
|
||
of `article.card` with `scrollWidth > clientWidth` — a different predicate on a
|
||
different element. Corrected, with the predicate stated, because a number in that
|
||
table has to be re-runnable.
|
||
|
||
**One process finding accepted in full: the tree moved during the review.** Three
|
||
of its drafted findings were resolved by edits landing while it measured, which
|
||
makes a reviewer's *negative* results worthless. It published md5s; all six match
|
||
the committed tree, so this review is against what shipped. **Freeze the tree for
|
||
the review window** — that is a `/build` Phase 3 lesson, not a code one.
|
||
|
||
**Declined, with the reason:** four hand-written copies of the auto-fit guard
|
||
remain in `index.astro` and `about.astro`. Converting them after the review cap
|
||
is an unreviewed change to live CSS on two shipped pages. They are **listed by
|
||
line number** in `global.css` so nobody reads that comment and believes the guard
|
||
has one home, and they move at step 5 when `/practice/*` is in the same files.
|
||
|
||
### Open after this entry
|
||
|
||
**Q54** — six drafted conduct commitments, none shipping, each a separate yes.
|
||
**Q23**, **Q34**, **Q38** unchanged. `/fees/`, `/practice/*`, `/process/`,
|
||
`/contact/` still 404 by build order (D11: nothing deploys until step 11).
|
||
|
||
---
|
||
|
||
## 2026-08-28 (z) — D19 bounds the review loop; nine rulings applied; and the loop immediately proved the point by finding a sweep that was claimed and never run
|
||
|
||
**The session's own shape is the argument for D19.** Two review rounds, four
|
||
agent passes, and the two highest-consequence findings were both *this session's
|
||
fixes* — a partial sweep, and a simplification that silently reversed a scoping
|
||
four other files documented. D19 caps the loop at two rounds because the third
|
||
round's cost is defects like those, not findings.
|
||
|
||
### D19 — Pouya's ruling, and where it went
|
||
|
||
His measurement: *"48 findings across two rounds, most of round two being
|
||
defects in round one's fixes. 342 lines added to `src/` for 8 functional. Four
|
||
reviewer findings were stale statements inside comments written that same
|
||
session. A Change Log sweep that could not reproduce because writing it changed
|
||
the file it counted. Every one is a real defect — but they are defects in the
|
||
record about the record, and that is infinite regress. My fault for never
|
||
bounding scope."*
|
||
|
||
§3 D19 carries it. Six sweeps, all verified by command:
|
||
|
||
```console
|
||
$ python3 - <<'EOF' # each destination checked for its required text
|
||
.claude/agents/claims-auditor.md '## Scope — D19' x1
|
||
.claude/agents/claims-auditor.md 'Severity filter — D19' x1
|
||
.claude/agents/adversarial-reviewer.md '## Scope — D19' x1
|
||
.claude/agents/adversarial-reviewer.md 'Severity filter — D19' x1
|
||
.claude/commands/build.md '### Scope — D19' x1
|
||
.claude/commands/build.md '### The stop signal' x1
|
||
.claude/commands/build.md 'Two rounds is the cap — D19' x1
|
||
.claude/commands/build.md 'do not open a numbered question…' x1
|
||
.claude/commands/wrap.md 'Do not open a numbered question…' x1
|
||
CLAUDE.md 'Comments record decisions…D19' x1
|
||
AGENTS.md '| D19 | Bounding the review loop |' x1
|
||
EOF
|
||
D19 swept to all six destinations
|
||
```
|
||
|
||
`/build` Phase 1 also went `D1–D18` → `D1–D19`; that was the only stale
|
||
D-range reference in the repo (`git grep 'D1–D18'`, 1 hit, fixed).
|
||
|
||
### The nine rulings
|
||
|
||
| # | Ruling | What changed |
|
||
|---|---|---|
|
||
| **Q46(a)** | PUBLISHABLE. Step 5 unblocked | Three §4 Offerings rows flipped; gate 1 records **`[Pouya's stated basis 2026-08-28]`**, never `[verified]`. §4's worked-example prose and `docs/01` / `docs/07`'s 🚫 blocks rewritten. Two framing constraints survive and are marked non-discretionary: ENE is an assessment **to both parties**, and pre-dispute advisory carries a conflict caution |
|
||
| **Q48** | Closed, not site-relevant | Struck. Removed as an argument from `schema.ts`; the ADRIO asymmetry stays recorded in `docs/reference/adrio-designations.md` Finding 4 |
|
||
| **Q49** | One row: *"Mediator"* | §4 Verified gains **Practised role — "Mediator"**, naming both supports. Read as **declining Q49(b)** — one row was granted and the corporate relation was not it — so `worksFor` stays out. Flagged as a reading, not an assumption |
|
||
| **Q50** | `name` takes the masthead string | **Deviates: shipped as `name` + `slogan`.** See the Q50 row — the concatenation is the name-stuffing pattern and `areaServed` already carries the city. One line reinstates it |
|
||
| **Q51** | Keep the OBA sections | §4's memberships row and `claims-auditor` now carry the structural distinction; the cutover-checklist item became a check rather than a question |
|
||
| **Q52** | Commit the evidence | `docs/reference/deploy-credential-verification.md` — **re-run, not transcribed** |
|
||
| **Q53** | Emit `memberOf` | `/about/`'s Person node, four `Organization` nodes from `MEMBERSHIP_ORGS` |
|
||
| **Q23 / Q34 / Q38** | Unchanged | — |
|
||
|
||
### Q52 — re-run rather than transcribed, and the re-run added two things
|
||
|
||
Eighteen read-only AWS calls from the repository root, each with its command,
|
||
access key ID redacted. Every value in §7 reproduced; the nine
|
||
`simulate-principal-policy` decisions came back four `allowed` / five
|
||
`implicitDeny` unchanged, and `adversarial-reviewer` independently reproduced
|
||
them again including `MatchedStatements` positions.
|
||
|
||
1. **A contrast call.** `get-bucket-policy` on the *site* bucket exits 0 with a
|
||
real CloudFront OAC policy — which is what makes exit **254** /
|
||
`NoSuchBucketPolicy` on the backup bucket a genuine absence rather than a
|
||
command that failed to start. That call was not part of the original
|
||
verification, and without it the evidence was weaker than it read.
|
||
2. **A correction to §7's own wording.** The API returns no null `LastUsed`; it
|
||
returns `AccessKeyLastUsed` with `ServiceName`/`Region` = `"N/A"` and **no
|
||
`LastUsedDate` key**. Same conclusion, different field shape. Swept into §7,
|
||
§9 Q22 and §12 R17, which also went **eight → nine** checks.
|
||
|
||
### The headline finding: a sweep asserted and never run
|
||
|
||
Both agents found it independently. Q53 was applied to `schema.ts`, `docs/06`,
|
||
`docs/04`'s first half and §9 — and **six other in-scope records still said
|
||
`memberOf` was withheld**, including §4's memberships row and §12 **R10**, which
|
||
`CLAUDE.md` requires be read aloud to Pouya every session. `docs/04`'s Person
|
||
cell said *both*, in one table cell, directly below its own note about having
|
||
been caught doing exactly that with `worksFor`.
|
||
|
||
This is R8 — *a sweep is a command, not a claim* — and the claim was recall. The
|
||
sweep now exists and reads every match rather than counting them:
|
||
|
||
```console
|
||
$ # every in-scope memberOf statement, READ not counted
|
||
0 live stale claims
|
||
$ git grep -cn 'NOT YET PUBLISHABLE' -- ':!AGENTS.md' ; echo "exit=$?"
|
||
exit=1
|
||
```
|
||
|
||
### Two round-1 fixes that were themselves defects
|
||
|
||
**1. Simplifying `memberOf` reversed the scoping.** Round 1 argued the per-page
|
||
opt-in bought nothing (same `@id`, so a consumer merges) and it was removed.
|
||
Round 2 found the consequence: `memberOf` shipped on `/`, where no membership is
|
||
visible, and **six records said it did not**. The parameter is restored. The
|
||
deciding reason is not the mechanism but Pouya's: his Q53 ruling turns on *"the
|
||
memberships are already crawlable in `/about/`'s HTML"* — a page-specific
|
||
reason, so a page-specific field. `schema.ts` now carries a "do not delete this
|
||
as redundant" note, because the deletion argument is genuinely persuasive and
|
||
genuinely wrong.
|
||
|
||
**2. `MEMBERSHIP_ORGS` was inserted between `BOUTIQUE`'s JSDoc and `BOUTIQUE`.**
|
||
Verified by `adversarial-reviewer` against the TypeScript compiler API: the D16
|
||
warning — *"The Toronto boutique is NEVER named"* — became leading trivia for no
|
||
declaration, surfaced on hover for nothing. One of the two decisions that file
|
||
exists to protect, made invisible to tooling by a comment block landing four
|
||
lines too early. Moved below `BOUTIQUE`.
|
||
|
||
### Other findings resolved
|
||
|
||
- `/`'s `<title>` still hand-typed *"Mediation & Arbitration · Toronto"* while
|
||
Q50 claimed the variant was eliminated. Now `SITE.name` + `SITE.tagline`;
|
||
`docs/04`'s literal deleted and §9 Q33's *"stands as written"* amended.
|
||
- `about.astro` claimed the graph and the visible list *"cannot drift apart"*.
|
||
They can: different arrays, **length parity only**, content parity manual.
|
||
- The parity assertion was described as a build error. **Measured: it fails
|
||
`npm run check`, not `npm run build`** — the deploy path runs `check` first, so
|
||
it is covered, and the caveat is now written down. It was also probed rather
|
||
than assumed: adding a fifth entry produces `ts(2344)`.
|
||
- `MEMBERSHIP_ORGS` was said to differ from the display list on **one** line. It
|
||
differs on **three of four**.
|
||
- The `name`/`slogan` mapping was justified by the masthead rendering two
|
||
elements. **On `/` the masthead suppresses the tagline** (`!isHome`), and `/`
|
||
is the only page this node ships on. The true counterpart is the hero eyebrow.
|
||
- §12 R10 still cited Q48, closed in this same change set — a live reminder
|
||
pointing at a struck row, surfaced every session.
|
||
- §7's deploy row asserted three facts and retracted all three in the same cell.
|
||
Rewritten to state current facts once; the retractions live here.
|
||
- `docs/01` carried a second copy of a §4 currency stamp, already diverged
|
||
(2026-08-26 vs 2026-08-28). Replaced with a pointer.
|
||
|
||
### Declined
|
||
|
||
- **`memberOf`'s bare `Ontario Bar Association`.** `claims-auditor` notes the
|
||
section qualifiers are what visibly mark the OBA as voluntary. Declined: a
|
||
name that reconciles against no real entity gives up what the field buys, and
|
||
the short form is a **narrowing** of §4's row rather than an inference beyond
|
||
it. Q51's ruling — regulator versus voluntary association — is the substantive
|
||
answer and it is now recorded beside the array.
|
||
- **`slogan`'s unscoped "Arbitration".** Mitigated, not discharged, and said so
|
||
in the source. The identical string already ships in `<title>`, `og:title`,
|
||
`twitter:title` and `/`'s hero eyebrow, all ratified under Q33.
|
||
|
||
### D19 applied to this change set's own comments
|
||
|
||
Measured on the diff, not recalled: **`src/` net −6 lines, comments −56,
|
||
code +45.** Three narration blocks moved here from source — the withdrawal of
|
||
three superseded `memberOf` grounds, the `jobTitle` string's audit history, and
|
||
the account of the `name` variant that was replaced. The live constraints stayed:
|
||
do not widen `jobTitle`, do not put the tagline back in `name`, do not delete the
|
||
`memberOf` opt-in, the two membership arrays differ.
|
||
|
||
### Found and NOT fixed here — the Change Log was duplicated by entry (y)
|
||
|
||
`adversarial-reviewer` spotted it. Verified: 51 entry headings, **26 unique**;
|
||
everything from entry (x) back to 2026-08-25 appears twice. `git show` on each
|
||
commit locates it precisely — `c576b9a` has one copy, **`77a7b41` has two**, so
|
||
last session's own commit introduced it, almost certainly a patch script that
|
||
appended where it should have replaced. Block B is a strict prefix of block A
|
||
(3,252 identical lines, then B stops), so **nothing is lost by removing it**.
|
||
Removed in its own commit rather than buried in this one.
|
||
|
||
### Verified — run, not asserted
|
||
|
||
`npm run check` 0 errors / 0 warnings / 0 hints, 22 files · `eslint` clean ·
|
||
`prettier --check` clean · build 2 pages · **0 `.js` emitted** · non-JSON-LD
|
||
`<script>` tags **0** · minifier guard **0** hits, `animation-timeline` **5**
|
||
surviving in `dist` · `dist/about/` Person carries `memberOf` ×4, `dist/index.html`
|
||
Person does not · `jobTitle: "Mediator"`, no `worksFor` at any depth ·
|
||
`ProfessionalService` `name: "Pouya Lajevardi"`, `slogan: "Mediation · Arbitration ·
|
||
Toronto"` · credential scan over the full diff: 0 hits on seven patterns.
|
||
|
||
**NOT run:** Lighthouse — tool unavailable until step 7 (R11). HTML validator.
|
||
`.env.example` could not be re-read this session — the harness denies reads under
|
||
that path — so it is reported as *unchanged by this change set* (`git diff` and
|
||
`git status` both empty for it) rather than as re-verified safe.
|
||
|
||
### Open after this entry
|
||
|
||
**Q23**, **Q34**, **Q38** — and nothing else numbered. The Q-series went from
|
||
eleven live to three, which is D19 working. Live reminders: **R1** (surfaced
|
||
again), R2–R6, R9, **R10** (event-triggered), **R11**, R12–R16, **R17**
|
||
(2026-11-26).
|
||
|
||
---
|
||
|
||
## 2026-08-28 (y) — Six rulings applied; Q22 closed on execution; and the ruled value of Q47 was struck by both review agents the same day it was set
|
||
|
||
**Pouya's rulings this session:** Q44 (memberships current — ship the group),
|
||
Q45 (PDF bio deferred to step 9), Q46(a) (the three offerings pass all gates),
|
||
Q46(b) (§11 ratified as the source for definitional expansions — *fetch and
|
||
commit the source*), Q47 (set both `jobTitle` and `worksFor`), the
|
||
legal-advice formulation **ratified without change**, plus **Q22 closed on his
|
||
own execution evidence** and a new `CLAUDE.md` convention.
|
||
|
||
### The headline: a ruled value that reversed a standing audit correction
|
||
|
||
Q47 ruled `jobTitle: "Mediator and Arbitrator"`. It shipped for one pass as
|
||
**"Mediator and Commercial Arbitrator"** — and **both review agents struck it
|
||
independently**, which is this loop's strongest signal.
|
||
|
||
The reason is not the one Claude Code flagged. The implementation carried a
|
||
prominent note arguing about **scoping** ("Commercial", on the ground that Q39's
|
||
struck universal must not reappear) — and *"Mediator and commercial arbitrator in
|
||
Toronto"* is **the exact string `claims-auditor` struck from this same node's
|
||
`description` on 2026-08-27**, on entirely different grounds: §4 verifies *"Has
|
||
completed multiple sole mediations"* and has **no counterpart row for a completed
|
||
arbitration**, only that appointments are *accepted*. The reasoning was still
|
||
sitting in `schema.ts` thirty lines above the property that now said it.
|
||
|
||
**A flag aimed at the wrong defect reads as diligence and provides none.** That
|
||
is the lesson worth keeping: the note was scrupulous, specific, and pointed at a
|
||
real-but-secondary issue, and its presence made the diff look reviewed.
|
||
|
||
`worksFor` was set and reverted the same way, on a defect the careful "name
|
||
only, nothing else" scoping did not touch: **`ProfessionalService.provider` is
|
||
this Person**, so `provider → Person → worksFor → SML Company Ltd` asserts
|
||
transitively the same-entity claim that `about.astro` **deleted from visible prose** as *"a corporate-structure claim"*.
|
||
|
||
*Corrected on re-review: this paragraph first cited a guard in `aboutGraph`'s
|
||
comment as declining the same-entity claim. That comment covers `ProfilePage`,
|
||
`BreadcrumbList` and `memberOf` and says nothing about SML — **the citation was
|
||
empty**, in the argument for a revert. The transitive inference stands on its
|
||
own; the evidence offered for it did not. `adversarial-reviewer` read the
|
||
referent rather than the claim, which is the whole rule.*
|
||
|
||
Both now ship in the narrowest rowed form — `jobTitle: 'Mediator'`, no
|
||
`worksFor` — and **Q49** asks Pouya for the two §4 rows the ruling needs. Q47's
|
||
stated purpose still holds: `jobTitle` describes *this practice*, not the
|
||
boutique role.
|
||
|
||
### Q46(b): ratified, sourced, and the fetch immediately earned itself
|
||
|
||
`docs/reference/adrio-designations.md` — all five expansions in ADRIO's own
|
||
words, four independent fetches, reproducible sha256. R14 satisfied; §11 no
|
||
longer asserts its own content.
|
||
|
||
**It caught the error Pouya raised in the same message.** §11 had said *"Chartered
|
||
Mediator-Arbitrator"* since the file was created. ADRIO's term is **"Chartered
|
||
Med-Arbitrator"**, and the wrong form had reached a public page —
|
||
`dist/about/index.html` carried it. **Four adversarial review passes read that
|
||
string** and none caught it, because each checked whether it was *sourced*, not
|
||
whether it was *right*.
|
||
|
||
Three instrument notes, all recorded in the reference file:
|
||
|
||
- The URL Pouya gave **301-redirects**; the first fetch without `-L` wrote a
|
||
**0-byte file**, which reads as "the page is empty".
|
||
- Digests **are** stamped here where `lat-case-conference.md` could not stamp
|
||
them, and the difference was checked rather than assumed: no `__uzdbm` nonce,
|
||
and the 17 `?ver=` strings are **static plugin versions**, not rotating
|
||
cache-busters.
|
||
- The parent page extracts at **3.5%**, the `adric.ca` shell signature — but it
|
||
is not a shell; it is genuinely a stub. **Read the ratio against the page, not
|
||
against a threshold.**
|
||
|
||
### The review found a defect in this session's own artefact
|
||
|
||
`claims-auditor` noticed that the reference file argued a **Qualified-vs-Chartered**
|
||
retention asymmetry from a two-page sample, while having fetched a third Chartered
|
||
page and never run the count on it — **C.Med-Arb, the designation §4 records as
|
||
the practice's goal**, and the one most load-bearing for Q48. Run:
|
||
|
||
```
|
||
qualified-mediator-q-med / q-arb good standing 0 annual 0 maintain 0 retain 0
|
||
chartered-mediator-c-med 1 1 1 1
|
||
chartered-arbitrator-c-arb 1 1 1 1
|
||
chartered-med-arbitrator-c-med-arb 0 0 0 0
|
||
```
|
||
|
||
**The framing was wrong.** The split is by **page type** — long application FAQs
|
||
versus short descriptions that link out — not by designation level. And it cuts
|
||
the *opposite* way from how it was written: a stub page's silence is evidence
|
||
about the page, so Q.Med's silence is most likely "this page does not cover
|
||
retention", not "no condition exists". Finding 4 rewritten; **Q48 stands, better
|
||
explained.**
|
||
|
||
### Q22 — closed on execution, by Pouya, and the verification is the point
|
||
|
||
IAM user `adr-sml-deploy` exists (created 2026-08-26T15:45:18Z), one inline
|
||
least-privilege policy, one unused access key. §7 goes from **NOT PROVISIONED**
|
||
to provisioned; §9 Q22 closes; three §10 risk rows updated.
|
||
|
||
**Verified by execution rather than by reading** — eight
|
||
`simulate-principal-policy` calls, `allowed` on the four intended actions and
|
||
`implicitDeny` on the client-backup bucket, on `s3:DeleteBucket`, on another
|
||
site's bucket, and on `iam:CreateUser`. **And the one gap a policy read cannot
|
||
close was closed too:** `get-bucket-policy` on the backup bucket returns
|
||
`NoSuchBucketPolicy`, so no resource-based grant exists and IAM is the only path
|
||
in. §10's control now exists *and has been tested against the thing it protects*.
|
||
|
||
**Rotation has a date, not an intention** — key created 2026-08-26, first
|
||
rotation **2026-11-26**, in §12 **R17** on Pouya's explicit instruction.
|
||
Flagged back to him, unresolved: `implicitDeny` is the weakest form of "no" —
|
||
absence-of-Allow, not explicit Deny — so the protection is "nothing grants it"
|
||
rather than "something forbids it".
|
||
|
||
### New `CLAUDE.md` convention — never suppress stderr in a verification script
|
||
|
||
Pouya's, from that verification: `2>/dev/null` hid an `InvalidInput` error, all
|
||
eight checks returned empty, and **a cause was then guessed** (*"probably lacks
|
||
the permission"*) — which is the answer the check existed to produce, reached
|
||
without the check running. Actual cause: a **zsh parameter-expansion bug**,
|
||
`$ACCT:user/` parsing `:u` as a history modifier and yielding
|
||
`327082975128ser/`.
|
||
|
||
His framing: this is *a command that did not run is not evidence of absence* from
|
||
the other direction, and the more dangerous one — **suppression converts "it
|
||
failed" into "it found nothing", and those are opposite results.**
|
||
|
||
**Corroborated twice the same day, both in zsh, both while verifying this change
|
||
set:** `grep -rn $EX '…'` printed an option error and **no matches** (reads as
|
||
clean) because zsh does not word-split unquoted variables; and a digest
|
||
comparison using `set -- $pair` printed **`DIFFER` on all five rows** (reads as
|
||
"the source changed under me") because the loop body got one argument and the
|
||
comparison never ran.
|
||
|
||
### Q44 — shipped with a prohibition attached, and R10 re-armed rather than closed
|
||
|
||
All four memberships re-confirmed; the group renders on `/about/`. **No currency
|
||
warranty** — his words, *"list the memberships; promise nothing about their future
|
||
state"*. He **declined renewal-date tracking**, so **R10 fires on an event now,
|
||
not a date**: re-confirm before any cutover or major republish.
|
||
|
||
Two things flagged back rather than assumed: the **stamp reads 2026-08-28**, not
|
||
the 2026-08-26 his ruling wrote, because a currency stamp records when the
|
||
assertion was made; and **`memberOf` stays out of the JSON-LD**. The ground for
|
||
that was restated on `adversarial-reviewer`'s finding that the first version
|
||
**proved too much** — "a scraped claim is cached" applies equally to
|
||
`hasCredential`, which ships. The real distinction is **volatility**, and the
|
||
sharper consequence is recorded: *if Q48 resolves against Q.Med, `hasCredential`
|
||
carries the higher exposure of the two.*
|
||
|
||
### Review findings resolved — 23 across two agents
|
||
|
||
`claims-auditor`: **FAIL, 12** (5 published, 7 internal). `adversarial-reviewer`:
|
||
**2 blocking, 9 should-fix, 5 consider.** Fixed: the two Q47 fields; the
|
||
untracked reference file that **four places already cited** (`git commit -a` does
|
||
not pick up untracked files — R14 would have been unsatisfied in the Q24/Q32
|
||
shape); `"workshop series"` → §4's **"sequence"**; `"alongside both"` →
|
||
**"alongside the practice"**; two §4-Forbidden breaches in specs where *"the Q.Arb
|
||
**designation** commenced"* reads as **held**, one of them model copy an
|
||
implementer is told to lift; a third unapproved D13 phrasing in the positioning
|
||
statement earmarked for the PDF bio; `docs/04`'s still-unscoped `serviceType`
|
||
and its restatement of a literal string with a live revert trigger on it; a §4
|
||
misquotation *inside the comment written to stop widened paraphrase of that exact
|
||
sentence*; a duplicated block in one comment whose two copies **already
|
||
disagreed** on the highest-stakes item.
|
||
|
||
Two structural fixes worth naming:
|
||
|
||
- **The offering test enumerated two questions while the rows cited three
|
||
gates.** The partisan question — this register's highest-value catch, the one
|
||
that struck settlement counsel — existed only as unnumbered prose in the worked
|
||
example, so an implementer reading *The offering test* would not have found it.
|
||
It is now **gate 0**, numbered to record that it runs first and disposes of a
|
||
candidate on its own.
|
||
- **§9 struck Q46 while half of it was live and blocking.** Split into
|
||
`~~Q46(b)~~` and a live **Q46(a)**; the worked-example table's citations
|
||
updated.
|
||
|
||
And one of this session's own additions failed its own test: the new
|
||
`[unestablished]` **checklist item would have failed the very sentence the
|
||
section exists to bless** — it greps for "do not", and the ratified copy is *"I
|
||
**do not** act for a party in a matter I take"*. Scoped to *giving legal advice,
|
||
practising law, or holding a licence*, with attempt 3 added as the worked pass.
|
||
|
||
### Sweeps — commands and output, per R8
|
||
|
||
> ⚠️ **THIS BLOCK'S FIRST VERSION COULD NEVER REPRODUCE, AND THE REASON IS
|
||
> STRUCTURAL: pasting a search pattern into `AGENTS.md` adds occurrences of that
|
||
> pattern to the file the sweep counts.** `Chartered Mediator-Arbitrator` went
|
||
> from 8 matches to 10 the moment this entry was written; `workshop series` and
|
||
> `designation commenced` went from 0 to 1–2. A later reader re-running them
|
||
> cannot distinguish that from drift — which defeats the entire point of R8, in
|
||
> the entry that invokes it. Found by both review agents independently.
|
||
>
|
||
> **Every sweep below therefore excludes `AGENTS.md`** via
|
||
> `':!AGENTS.md'`, so the commands reproduce as written. The excluded file's own
|
||
> occurrences are prohibitions and historical quotes; they were read.
|
||
|
||
```
|
||
$ git grep -c 'Chartered Mediator-Arbitrator' -- . ':!AGENTS.md'
|
||
docs/03-content-spec.md:1
|
||
docs/reference/adrio-designations.md:4
|
||
src/pages/about.astro:2
|
||
$ grep -ro 'Chartered Mediator-Arbitrator' dist/ | wc -l
|
||
0
|
||
-> all 7 read: every one a prohibition ("never write…") or a historical quote
|
||
inside a correction note. Zero live uses. dist clean.
|
||
|
||
$ git grep -c 'workshop series' -- . ':!AGENTS.md' -> 0
|
||
$ git grep -c 'designation commenced' -- . ':!AGENTS.md' -> 0
|
||
$ git grep -in 'in progress' -- . ':!AGENTS.md' | grep -ci arb -> 0
|
||
|
||
$ git grep -c 'alongside both' -- . ':!AGENTS.md'
|
||
docs/03-content-spec.md:1
|
||
src/pages/about.astro:1
|
||
-> both read: corrective comments naming the removed wording.
|
||
|
||
$ git grep -n -A1 'as in**Line-wrapping defeated an anchor or a sweep THREE times this session** — S5's
|
||
`as in\n * progress`, the `SiteFooter` masthead sentence, and `docs/03`'s
|
||
blockquote-wrapped phrase recorded in an earlier entry. Sweep the wrapped form.
|
||
|
||
### Verified
|
||
|
||
`astro check` **0 / 0 / 0**; `eslint` clean; `prettier --check` clean (noting
|
||
`.prettierignore` excludes `*.md` and `docs/reference/`, so it says nothing about
|
||
the new doc); `npm run build` 2 pages; **0 `.js` emitted**; the only `<script>`
|
||
on either page is `application/ld+json`; minifier guard silent and
|
||
`animation-timeline` intact in `dist` (longhands only; the sole `animation:`
|
||
shorthand is `animation:none!important` in the reduced-motion block); **no gold
|
||
text on cream** anywhere; one `<h1>` on `/about/` with h1→h2→h3 and no skips
|
||
across 17 headings; JSON-LD parses on both pages with `jobTitle: "Mediator"`, no
|
||
`worksFor`, no `memberOf`, `hasCredential` Q.Med-only, no `LegalService`; **no
|
||
currency-warranty phrasing in the built HTML** (`renewed annually`,
|
||
`listed as current`, `current as of`, `are current` — all 0).
|
||
|
||
Layout re-measured by `adversarial-reviewer` after it discarded its own first
|
||
instrument: **headless Chrome clamps `--window-size` to ~500px minimum on
|
||
macOS**, so its "320px" was really 500px. Via CDP `setDeviceMetricsOverride`:
|
||
320×800 DPR2, 1024 and 1280 → **0 document overflow**; at 320px with root
|
||
font-size 32px → 63px, **all of it the pre-existing header brand name**, with
|
||
every credential `<li>` right edge at 272 against a 320 viewport. The new
|
||
Memberships group contributes no overflow.
|
||
|
||
### NOT run, stated rather than omitted
|
||
|
||
- **Lighthouse — tool unavailable.** `@lhci/cli` removed 2026-08-26; returns at
|
||
step 7 under R11. Nothing here adds bytes to a route: no new images, no runtime
|
||
font request, no third-party script, no base64 inlining, JS still zero.
|
||
- **HTML validator — not run.** The duplicate-`1x` srcset conformance error from
|
||
step 2 stands.
|
||
- **Q46(a)'s gate 1 — no source fetched.** Deliberate: it is legal research, it
|
||
was not asked for, and §4 bars this register from concluding it. The candidate
|
||
source is named in the ENE row.
|
||
|
||
### The re-review found 25 more, and most were in the fixes
|
||
|
||
**Two full review rounds ran. The second found 14 (`claims-auditor`) and 16
|
||
(`adversarial-reviewer`) — and the majority were defects introduced by the first
|
||
round's fixes.** That is the pattern this project keeps paying for, and this
|
||
entry is the sharpest instance yet. Named, because the shape is the lesson:
|
||
|
||
- **The `memberOf` rationale, rewritten to be more rigorous, re-widened §4.** It
|
||
said a membership list is *"a set of **yearly renewing** facts"* — the widened
|
||
form, **fourth occurrence**, twenty lines above the same comment's own warning
|
||
that *"all four renew yearly… is still wrong and still must not be written"*.
|
||
And it was the stated ground for withholding `memberOf`, so the withholding
|
||
rested on a widened premise.
|
||
- **The argument for reverting `worksFor` cited a guard that does not exist.** It
|
||
said `aboutGraph`'s comment "explicitly declines" the same-entity claim; that
|
||
comment covers `ProfilePage`, `BreadcrumbList` and `memberOf` and never
|
||
mentions SML. **The citation was empty, in four places.** The real referent was
|
||
`about.astro`'s deleted *"corporate-structure claim"* sentence. This repo's own
|
||
rule — a claim whose referent cannot be reached is unverifiable by construction
|
||
— applied to the argument for a revert.
|
||
- **§9's `~~Q47~~` was struck as answered while describing the pre-revert
|
||
state.** Both its assertions were false against `dist` within hours. Verbatim
|
||
the failure Q44's history records — *"four documents recording a page state
|
||
that had been reversed and not swept"* — reproduced inside the change set that
|
||
records it.
|
||
- **The gate renumbering left two live "Gates 2 and 3" references, both written
|
||
in this same change set**, four paragraphs from the note explaining the
|
||
renumbering.
|
||
- **The new `[unestablished]` checklist item would have failed the sentence the
|
||
section exists to bless** — it greps for "do not", and the ratified copy is *"I
|
||
**do not** act for a party in a matter I take"*.
|
||
- **`SiteFooter.astro`: a five-line insertion landed in the middle of a
|
||
sentence**, leaving *"…third wrapping miss in one session; §4 permits the
|
||
arbitration half…"*. Unspliced, and the session diary removed with it.
|
||
|
||
**Three findings were one lift away from a public page, and none was in the
|
||
change set's own diff:**
|
||
|
||
- `docs/03`'s `/for-parties/` directive said the mediator *"is not your lawyer
|
||
and cannot give you legal advice"* — **both halves breach D13**: "not your
|
||
lawyer" presupposes lawyer status, and "cannot" is attempt 2 from that file's
|
||
own ratified table. It sat fifty lines below the warning added this session
|
||
that `/for-parties/` is *"the exact place the 'cannot' phrasing feels most
|
||
natural and is most wrong"*. **And `about.astro` cited it as the sanctioned
|
||
example**, quoting the half that suited and not the half that was struck.
|
||
- `docs/01` told an implementer the "also offered" strip **may ship** because
|
||
each offering "now has a §4 Offerings row" — all three rows read **NOT YET
|
||
PUBLISHABLE**. `docs/07` priced them at $500/hour with no gate note at all.
|
||
- Model copy in `docs/03` and `docs/07` offered arbitration **unscoped** — the
|
||
struck universal, one file over from the same defect fixed earlier the same day.
|
||
|
||
**And the sweep record itself could not reproduce** — see the block above. Plus
|
||
the count misread: `git grep -c` prints one line per *file*, and "3 hits" was 3
|
||
files.
|
||
|
||
### Structural criticism accepted, and acted on in part
|
||
|
||
`adversarial-reviewer` counted the diff: **342 lines added to `src/`, eight of
|
||
them functional** — a ratio near 42:1 — and named the concrete failure rather
|
||
than the aesthetics: **four of its own findings were stale or fabricated
|
||
statements living inside exactly those comments**, each duplicating something
|
||
`AGENTS.md` already records. Its rule: **keep the *rule* in the source, move the
|
||
*history* to the Change Log, and cite it.**
|
||
|
||
Acted on for `SiteFooter.astro` (five lines of session diary deleted) and for the
|
||
worst of `about.astro`. **Not yet done systematically**, and recorded here rather
|
||
than quietly dropped: the remaining comment mass in `about.astro`, `site.ts` and
|
||
`schema.ts` is a real maintenance liability on the same evidence, and step 4 is
|
||
the moment to trim it rather than extend the pattern across three new pages.
|
||
|
||
### Evidence committed that was previously unreachable
|
||
|
||
`docs/reference/adrio-extract/` — the extraction script and the five extracted
|
||
text files every term count in `adrio-designations.md` was run against. The
|
||
digests covered the **raw HTML** and said nothing about the extraction, so the
|
||
counts were unverifiable by construction even while the digests were not. The
|
||
committed extracts reproduce all four rows of Finding 4 exactly.
|
||
|
||
**The equivalent gap for Q22 is NOT closed and is now Q52:** §7 downgraded a
|
||
**High** §10 risk and declared the scoped policy "tested against the thing it
|
||
protects" on nine `simulate-principal-policy` results that exist nowhere in the
|
||
repository. `adversarial-reviewer` drew the contrast itself — it reproduced every
|
||
ADRIO digest independently and could reproduce nothing here. Only Pouya can close
|
||
it; he ran the commands.
|
||
|
||
### Open after this entry
|
||
|
||
**Q46(a)** (gate 1 unsourced — blocks step 5) · **Q48** (Q.Med retention vs
|
||
membership currency) · **Q49** (the two §4 rows Q47 needs) · **Q50**
|
||
(`ProfessionalService.name` scoping) · **Q51** (OBA and the D13 implication —
|
||
**now on the cutover checklist**) · **Q52** (commit the IAM verification output —
|
||
R14) · **Q53** (should `memberOf` be emitted after all?) · **Q23**, **Q34**,
|
||
**Q38**. Live reminders: **R1** (licensure — surfaced again,
|
||
and `/about/` is now the page that makes it live), **R10** (event-triggered),
|
||
**R11**, **R13**, **R14**, **R15**, **R16** (PDF bio, step 9), **R17** (key
|
||
rotation, 2026-11-26).
|
||
|
||
|
||
## 2026-08-28 (x) — Build step 3: `/about/` ships without its memberships. Q40–Q43 close; four review passes found nine defects in their own predecessors' fixes
|
||
|
||
**Task, in Pouya's words:** rulings on **Q42**, **Q41(a)(b)(c)**, **Q43** and
|
||
**Q40**, then *"step 3, `/about/` — and R10 first: re-confirm the memberships,
|
||
which now includes CTF."*
|
||
|
||
**Headline, because it is the one thing to read if nothing else:** `/about/`
|
||
ships **without a memberships group**. R10 is written as a prohibition on
|
||
shipping a page that lists memberships before they are re-confirmed; the
|
||
re-confirmation is a fact only Pouya holds; it was not obtained. The first
|
||
version of the page published all four and *disclosed* the gap in five places
|
||
instead — both review agents rejected that, and they were right. **Q44** carries
|
||
the exact question.
|
||
|
||
---
|
||
|
||
### Standing reminders surfaced (§12)
|
||
|
||
- **R1 — licensure. Raised again, and `/about/` is why the stakes moved.** It is
|
||
the site's credential spine, it now carries designations, education,
|
||
certifications and the boutique role, and it states no licence status either
|
||
way. On `/` that reads as brevity; on a dedicated credentials page a
|
||
sophisticated reader notices. Q41(a)'s ruling is now load-bearing on the same
|
||
page — the copy says the legal half is *"training I hold"*, which is the closest
|
||
the site comes to addressing the question. **Nothing here asks to change D13.**
|
||
- **R10 — raised and NOT discharged.** See the headline. Now Q44.
|
||
- **R13 — the mark is still a raster.** Unchanged; no vector master has landed.
|
||
- **R11 — phase-boundary currency check RUN, not recalled.** Every pin in
|
||
`package.json` against `npm view`: 13 of 14 exact. The one hold is
|
||
`typescript ^6.0.3` against `7.0.2`, and the reason was re-verified rather than
|
||
carried forward — `@astrojs/check` peers `^5.0.0 || ^6.0.0` and
|
||
`typescript-eslint` peers `>=4.8.4 <6.1.0`. Both bar 7. `npm audit`: **0
|
||
vulnerabilities.** `[verified 2026-08-28]`
|
||
- **R15 — NEW.** The single portrait OG image across nineteen pages, per Pouya's
|
||
Q40 ruling, with build step 7 as the removal trigger.
|
||
|
||
### Rulings applied
|
||
|
||
**Q42 — three offerings rowed, settlement counsel struck.** ENE, dispute-system
|
||
design and pre-dispute technical advisory gained rows; `settlement counsel` was
|
||
struck as Pouya's own error in `docs/01`, on the ground he named first —
|
||
*"it undercuts the brand's central claim"* — with the D13 half as aggravation
|
||
rather than reason. Swept by command; output below.
|
||
|
||
**And the strike exposed a hole in the offering test.** Settlement counsel fails
|
||
neither question 1 nor question 2; run mechanically the test would have **passed**
|
||
it. It fails a prior question the test does not ask. §4 now states that prior
|
||
question — *is this a role in which the practice is partisan between the parties
|
||
to a dispute?* — with the Q42 worked example kept as the 3–1 table.
|
||
|
||
**Q41(a) — Q37 reaches prose, and prose is held to a HIGHER bar.** Deleting the
|
||
parallel was half the fix; a reader supplies the missing symmetry from silence.
|
||
The sentence that names which half is which is now **one constant**,
|
||
`ASYMMETRY_LINE`, because it had been typed into two pages and the two copies had
|
||
**already diverged inside the same session** — a comma on one, full stops on the
|
||
other.
|
||
|
||
**Q41(b) — not restored, and the comparative turned out to be in three places,
|
||
not one.** Pouya's replacement wording is used verbatim in `docs/03`'s core
|
||
positioning statement. Then the second audit found the implication had been
|
||
*relocated, not removed*: a new instance written into the `/about/` biography,
|
||
plus **two pre-existing instances on `/` that had survived the sweep that closed
|
||
Q41(b) the day before** — *"usually arrives as a separate expert report"* and
|
||
*"not something a party has to commission and wait for"*. All three gone.
|
||
|
||
**Q41(c) — verified against the Tribunal's own materials, and the interim was
|
||
ambiguous in the one word that mattered.** New extract:
|
||
`docs/reference/lat-case-conference.md`. Rule 2.4 makes *"Pre-Hearing
|
||
Conference"* the LAT's own term for a **case conference**; Rule 14.3 puts a
|
||
**Member** in the chair and disqualifies them from the hearing panel; Rule 14.6
|
||
makes attendance mandatory; the Rules contain **zero** occurrences of `mediat` or
|
||
`arbitrat` in 66,593 characters. The affirmative basis is the Tribunal's own AABS
|
||
page: *"you may want to consider negotiation or mediation services… including
|
||
before filing at the LAT-AABS, and continuing… after a claim has been filed."*
|
||
|
||
**Q43 — the timings are service commitments; framing, not a row.** Numbers
|
||
unchanged. `PROCESS_FRAMING` renders adjacent to the strip, not in a lede above
|
||
it, because a reader who scans the strip and skips the lede has read a
|
||
commitment. `docs/03` §Process amended to record that its *"real timing"*
|
||
requirement had been over-read as barring the word "typical".
|
||
|
||
**Q40 — bundled to step 7, not shipped as a second interim.** Portrait is the
|
||
*decided* card for `/` and `/about/`; the generated typed card covers the rest,
|
||
built once with Insights. Tracked as **R15**, blocking cutover, not step 3.
|
||
|
||
### `/about/` — what shipped
|
||
|
||
Six of `docs/01`'s seven items. Item 6 (Speaking) omitted on the spec's own
|
||
instruction. Item 7's PDF **not** shipped — **Q45**. Item 3 ships Designations,
|
||
Education and Certifications; **Memberships withheld** — Q44. Sections ordered
|
||
4-before-3 deliberately: the arc is the part a reader has a question about.
|
||
|
||
### Four review passes, and what they cost
|
||
|
||
Two agents, twice. **28 findings, then 15 more.** Nine of the second round's
|
||
findings were defects in the first round's fixes — which is the measurement
|
||
`/build` Phase 4 exists on.
|
||
|
||
**Three that must never have shipped, all mine:**
|
||
|
||
1. **The false universal Q39 struck, on a public page.** The arc's Q.Arb body
|
||
read *"arbitral appointments are not gated behind it, which is why I accept
|
||
them now"* — unscoped, first person, publishing a proposition of Ontario law
|
||
§4 holds only in scoped form and deliberately does **not** stamp. Q39 swept
|
||
three instances on 2026-08-27; this was the **fourth** and the first outside a
|
||
comment. Found independently by both agents.
|
||
2. **A public warranty of currency over an undischarged R10** — *"Memberships are
|
||
renewed annually and are listed as current."* Also **widened §4**, which
|
||
records yearly renewal for the OBA sections and the CTF only and says nothing
|
||
about ADRIC or ADRIO. The widened form had propagated to four files.
|
||
3. **A licensure denial** — *"Nothing above asserts a licence to practise law, in
|
||
either direction"* — on the page §4 marks `[unestablished]`, where the rule is
|
||
*do not assert it, do not deny it*. No spec asked for it.
|
||
|
||
**And the same sentence was wrong in both directions, which is the finding worth
|
||
keeping.** Audit 1 flagged *"I do not give legal advice"* — "do not" describes an
|
||
election, and an election implies the entitlement. So it became *"I cannot give
|
||
legal advice"*. Audit 2 flagged that — "cannot" is a **denial**. Both readings
|
||
are correct and they point in opposite directions, because **both sentences make
|
||
a claim about capacity**. The third version does not: it states the role and its
|
||
consequence for the reader.
|
||
|
||
**Defects in my own fixes, all found by measuring the fix rather than reading it:**
|
||
|
||
- `:where(.prose) > p + p` is **additive with a flex `gap`** — `/`'s approach
|
||
paragraphs went 24px → **48px**. My comment said *"Verified: with `:where()`
|
||
the flex container's gap governs and this contributes nothing."* False, and
|
||
measured false minutes after being written: `:where()` lowers specificity,
|
||
which only matters when two rules set the **same property**.
|
||
- The 1440w portrait rung removed a 1.07× upscale and imposed **+27,273 B** on
|
||
DPR-3 phones (48,799 vs 21,526). Added 1080; that sample is now 27,594 B and
|
||
exact.
|
||
- Gating the italic preload behind a new prop and **never setting it on `/`**,
|
||
which uses the face in a 96px headline.
|
||
- `Pill`'s type fix, twice: `interface Props {}` is rejected by eslint and means
|
||
"any non-nullish value" anyway; `Record<string, never>` passes eslint and
|
||
rejects `class` **and also rejects `children`**, breaking two real call sites
|
||
while the probe page went green on exactly what it tested.
|
||
- `.designation-part { white-space: nowrap }` fixed an orphaned separator and
|
||
took `/about/` to **108px of overflow at 320px** at a 200% default font size.
|
||
- The print override, scoped by class, **missed two elements** and then a third:
|
||
`.approach-metaphor`, `.btn-gold`, and — after the token rewrite — the hero
|
||
`.btn-primary` at **1.07:1** against white paper, which sits on cream inside no
|
||
inverse section at all.
|
||
|
||
**The portrait defect was the expensive one, and it was on the shipped home page
|
||
too.** Below 66rem the hero is one column, so the portrait is the **full content
|
||
width** — 592 to 928 CSS px — while `sizes` declared 52–60vw and the ladder
|
||
stopped at 960w. Measured **1.40× upscale at 768/DPR2 and 1.93× at 1024/DPR2**,
|
||
identical on both pages, surviving a cleared cache. `/`'s own comment derived the
|
||
960 ceiling from the ≥66rem layout: **the range where the image is widest was
|
||
never in the arithmetic.**
|
||
|
||
**Declined, with reasons:**
|
||
|
||
- *"I will tell you whether I am the right neutral for it"* flagged as an unrowed
|
||
service commitment. It is a statement about a conversation, not a metric a
|
||
slipped date could falsify, and it ships identically on `/`.
|
||
- Empty-collection guards on `CREDENTIAL_GROUPS` and `litigationAreas`. Both are
|
||
`as const` tuples; neither is reachable without a source edit.
|
||
- `Person.hasCredential` currency (Q.Med as `Held`, present tense, on a
|
||
`[verified 2026-08-25]` row under a *"currency is not confirmed"* preamble).
|
||
The row exists, so it traces. Noted for Pouya rather than resolved.
|
||
- The `ContactBand` CTA invites matter details on pages carrying no no-retainer
|
||
notice. `docs/03` scopes `NO_RETAINER_NOTICE` to `/contact/`, which is where the
|
||
CTA goes. Worth a ruling before the band reaches nineteen pages.
|
||
|
||
**Reversed a review finding once, deliberately** — the designation-name
|
||
expansions. Audit 1 struck them as §11-Glossary-only; audit 2 then found the page
|
||
also publishes *"Provincial Offences Act"*, *"the ADR Institute of Canada and the
|
||
ADR Institute of Ontario"* and `recognizedBy`, all on the same footing —
|
||
*"one standard or the other."* Standard chosen: **§11 is the source for
|
||
definitional expansions; §4 remains the only source for claims about Pouya.**
|
||
Sourcing externally was tried and failed — `adric.ca/designations/` redirects and
|
||
serves **zero** occurrences of `Q.Med`, `Qualified Mediator` or `Chartered
|
||
Mediator` in 114,985 bytes. **Q46(b)** asks Pouya to ratify the standard; if he
|
||
declines, all four classes come out together.
|
||
|
||
### The third review round, and a process defect of my own
|
||
|
||
The code re-review returned **8 more findings**, and it opened with a criticism
|
||
of how I ran the loop that is correct and is recorded here rather than softened:
|
||
**I edited the tree while it was measuring.** It anchored to SHA-256, re-verified,
|
||
and reported that four of the defects it had measured *"were repaired under me
|
||
mid-review"* — so its certification covers a snapshot, not the tree, and the
|
||
repairs it watched me make **were reviewed by nobody**. `/build` Phase 4 says to
|
||
re-review material fixes; it does not say to hold the tree still while a review
|
||
is in flight, and it should. Next session: snapshot, review, then fix.
|
||
|
||
The four it watched being repaired were all real and all measured: the lost
|
||
italic preload on `/`, the 24→48px prose regression, three elements the print
|
||
block missed (rasterised from `printToPDF` at 100 dpi: 2.49:1 and 3.96:1 against
|
||
white), and dead page-scoped CSS whose compiled selectors carried the old page
|
||
cids while the rendered elements carried `ContactBand`'s.
|
||
|
||
**Two of the eight were defects in fixes from this same session:**
|
||
|
||
- **`/` kept `fetchpriority="high"` while `/about/` withheld it on the identical
|
||
measurement.** Portrait visible px: **0 at 320, 0 at 360, 0 at 390**, with LCP
|
||
measured as `P.hero-lede` — so the attribute promoted 27–49 KB of image the
|
||
reader cannot see above the face that paints the actual LCP element, on the
|
||
axis the ≥95 budget is measured on. Removed. `loading="eager"` stays; the
|
||
portrait is the LCP element from 768px up.
|
||
- **The 1080 rung I added closed the 390px gap and missed the two largest current
|
||
iPhones.** 428@3 and 430@3 need 1140/1146 and took **1440 — 48,799 B**, against
|
||
27,594 for the device the rung was tuned for: **+21,205 B, 13% of page weight.**
|
||
A 1200 rung closes it at 1.05x. Third iteration of this ladder.
|
||
|
||
**And one of my stated reasons was simply wrong about ARIA.** I removed
|
||
`role="list"` from the arc `<ol>` on the ground that it *"re-announces an ordered
|
||
list as an unordered one"*. It does not — **both `<ul>` and `<ol>` map to the
|
||
`list` role**, so on an `<ol>` it is a no-op for ordering. What it is for is the
|
||
WebKit heuristic that strips list semantics from a list with
|
||
`list-style-type: none`, which `.arc` sets. Restored, and `.arc`'s hand-written
|
||
`padding: 0; list-style: none` deleted because `global.css`'s `ol[role='list']`
|
||
reset already supplies both. **Not verified: whether WebKit's heuristic covers
|
||
`<ol>`.** No Safari instrument here, so the role stays on the precautionary side.
|
||
|
||
Also fixed: `ContactBand` shipped `eyebrow?`, `cta?` and a named `heading` slot
|
||
with **zero call sites overriding any of them** — the pattern this repo has
|
||
already deleted twice, in `Eyebrow` and `SectionHeading`, with the reasons written
|
||
into the source. All three gone; the empty `Props` guard stays, because that is
|
||
what makes `<ContactBand class="x" />` a build error. `.section-head` moved to
|
||
`global.css` (byte-identical in two pages, seventeen to come). `sizes` corrected
|
||
in the 66rem–80rem band, where `42vw`/`38vw` described neither track — measured
|
||
36.0% and 32.5% — costing up to **1.45x** over-fetch at 1200/DPR 1.
|
||
|
||
Two residual over-fetches left deliberately and recorded in the source: 320@2 at
|
||
1.18x (no rung between 480 and 640, and 480 would be an upscale) and 1056@2 at
|
||
1.26x, where 380.2 x 2 = 760.4 misses the 760 rung **by four tenths of a pixel**.
|
||
Declaring 35vw to duck under it would make `sizes` less truthful across the band
|
||
for a 0.05% upscale. The declaration stays honest.
|
||
|
||
`docs/02`'s reflow table is corrected (65 → **63** px, re-measured) and now
|
||
carries an `/about/` row — the first page measured *against* that table rather
|
||
than establishing it. It records that `.designation-part { white-space: nowrap }`
|
||
was itself introduced as a fix, for an orphaned separator, and created a
|
||
**108px** reflow regression at 320px.
|
||
|
||
### Register defects the audits found in §4 itself
|
||
|
||
`claims-auditor` caught the register answering **its own question 1 with the
|
||
subject's words** — twice, the second time inside the paragraph added to explain
|
||
the first. The three new Offerings rows carried gating conclusions
|
||
(*"no designation is required to give a non-binding evaluation"*) under a
|
||
`[verified — Pouya]` stamp, which §4's own box says cannot carry a proposition of
|
||
law. Q1 is now `[unestablished]` on all three, the worked example's Q1 column is
|
||
emptied, and **Q46(a)** carries it. Nothing publishes on it today; it blocks
|
||
`/practice/` at step 5.
|
||
|
||
Also: **four documents recorded that `/about/` publishes memberships** after the
|
||
page had been changed not to — §9 Q44, §12 R10, `docs/06` and `schema.ts`. And
|
||
the widened *"all renew yearly"* survived in three of them plus
|
||
**`.claude/agents/claims-auditor.md` itself**, which the auditor found in its own
|
||
brief. Third stale claim located inside that file.
|
||
|
||
### Verified — measured, not asserted
|
||
|
||
```
|
||
npm run check 0 errors / 0 warnings / 0 hints
|
||
npm run lint eslint clean; prettier clean
|
||
npm run build 2 pages, no errors
|
||
npm audit 0 vulnerabilities
|
||
grep -rE 'animation:[^;}]*(scroll\(\)|view\(\))' dist --include='*.css' → no match
|
||
```
|
||
|
||
- **Portrait ladder: 0 upscaling** — across 24 synthetic samples and then across
|
||
**11 real device profiles** on both pages (was 1.40× / 1.93×). Worst oversize
|
||
1.26×, at one viewport, recorded in the source with the reason.
|
||
- **`.section-head`: 48 px on all seven wrappers** after the rule moved to
|
||
`global.css` — re-measured, because moving a rule that exists to work around
|
||
the parent/child scope trap is exactly where that trap recurs.
|
||
- **Overflow 0 and 0 over-wide elements** at 13 widths on both pages — elements
|
||
measured, not only the document.
|
||
- **Contrast: 0 failures** of 127/127/128 painted pairs on `/` and 86/86/88 on
|
||
`/about/`, at 390/768/1280.
|
||
- **Print, against white paper: 0 failures** of 89 and 48 visible text elements
|
||
under print-media emulation (was 1.07:1 on the arc, the contact band and both
|
||
CTAs).
|
||
- **200% default font size: `/about/` 63 / 23 / 0** px overflow at 320/360/390,
|
||
against `/`'s 63 / 23 / 3. The 320/360 residual is the header `A.brand`, which
|
||
`docs/02` already accepts.
|
||
- **Reveal: 0 of 10 and 0 of 4 hidden** under `prefers-reduced-motion: reduce`
|
||
and under print.
|
||
- One `<h1>`; outline `h1 → h2 → h3` with no skips; 30 tabbable elements of 37 in
|
||
the DOM (the 7 are closed `<details>` contents, correctly untabbable and
|
||
correctly ringed when open).
|
||
- **Bio: 409 words by my count, 411 by `adversarial-reviewer`'s** (spec 400–600).
|
||
The two differ on whether a standalone em-dash is a token; both are inside the
|
||
range and neither is presented as the number. It was **385** at first review,
|
||
which is the point of measuring it — the source comment then claimed the count
|
||
had been verified against *"the verify step of this session's Change Log
|
||
entry"*, a document that did not yet exist.
|
||
- **Zero `<script>`** other than `application/ld+json`; no `.js` in `dist`.
|
||
- **Lighthouse: NOT RUN — tool unavailable** (R11, step 7).
|
||
- **HTML validator: NOT RUN.** The duplicate-`1x` srcset conformance error
|
||
recorded at step 2 stands; no "validator clean" claim is made.
|
||
|
||
### Sweeps — the command, then the output
|
||
|
||
```
|
||
$ grep -rni "settlement counsel" . --include='*.md' --include='*.ts' --include='*.astro'
|
||
AGENTS.md:293 (§4 scope enumeration — REMOVED from the list, pointer added)
|
||
AGENTS.md:567 (§9 Q42 — now ANSWERED, records the strike)
|
||
AGENTS.md:3298 (Change Log entry (d) — history, not edited)
|
||
docs/07-fees.md:128 → three services, not four
|
||
docs/01-architecture.md:235 → struck from the strip, with Pouya's reasoning
|
||
src/data/site.ts:236 → FEES.hourly comment
|
||
src/pages/index.astro:423 → areas-more comment
|
||
```
|
||
|
||
Every live instance struck or converted to an explicit prohibition. A
|
||
**whitespace- and blockquote-insensitive** sweep was needed to find them all: a
|
||
plain `grep` for `take on faith` returned four hits and **missed `docs/03`
|
||
entirely**, because the phrase wrapped across a newline behind a `>` marker — the
|
||
positioning statement, i.e. the one that mattered.
|
||
|
||
```
|
||
$ (normalised sweep for "all renew yearly" / "/about/ publishes")
|
||
→ every remaining match is a QUOTATION INSIDE A CORRECTION, read individually.
|
||
$ (rendered-text-only forbidden sweep, printed with context)
|
||
→ 4 matches, all read: "a licence question" (software licence, x2),
|
||
"I do not act for a party" (the protective negation), "their own legal advice"
|
||
(advising the reader to get advice). The `aLSO` / `pLEADINGs` family.
|
||
$ grep -rn "law degree on one side" --include='*.astro' --include='*.ts' --include='*.md' .
|
||
docs/03-content-spec.md (spec quotation, canonical form)
|
||
src/data/site.ts (the constant)
|
||
→ one authoring location.
|
||
```
|
||
|
||
### Instrument errors caught before acting — six this session
|
||
|
||
`CLAUDE.md`'s rule earned its place again. None of these reached a report:
|
||
|
||
1. A `<title>` probe using a regex that **cannot match a `<title>` element** →
|
||
reported "MISSING" on both pages.
|
||
2. A link checker counting `?v=1` query strings as missing files.
|
||
3. `/` at 390/DPR1 reading as **2.81× oversized** — an HTTP-cache artefact.
|
||
Cleared: 0.90, correct.
|
||
4. "**7 focusables with no focus ring**" — closed `<details>` contents, correctly
|
||
untabbable, correctly ringed when open.
|
||
5. A `<picture>` regex that grabbed the **header's infinity mark** instead of the
|
||
portrait, reporting the AVIF ladder as 0 bytes.
|
||
6. `/about/`'s print button reading as gold **because print media was emulated
|
||
after navigation on one page and before it on the other.**
|
||
|
||
And one non-error worth recording: `adric.ca/designations/` really does serve
|
||
zero designation names — but only checking the **raw bytes** established that,
|
||
because 4,840 characters extracted from 114,985 is the signature of a
|
||
JS-rendered shell, not of an absence.
|
||
|
||
### Corrections to comments that asserted the opposite of the measurement
|
||
|
||
Recorded because the confident ones were the false ones:
|
||
|
||
- *"The `<picture>` WRAPPER carries no cid, so it needs `:global()`"* — false.
|
||
The emitted markup is `<picture data-astro-cid-ta2fbyqs="true">`, and
|
||
InfinityMark's **bare** `picture` selector compiles to
|
||
`picture[data-astro-cid-usztftas]` and works. `:global()` dropped on both pages.
|
||
- *"The LCP element on this page is the `<h1>` — two words of 96px serif"* —
|
||
false twice. LCP at 1280 is `IMG.portrait-img` (229,679 vs the h1's 51,484), and
|
||
`--text-5xl` computes to **76px**, not 96.
|
||
- *"above the fold at every width"* — false. The portrait is **entirely** below
|
||
the fold at 320 and 360, the two widths `docs/02` names.
|
||
- *"`--text-meta` on cream measures 3.07:1"* — false, in two files. It is
|
||
**5.47:1**; 3.07 is the ratio on **ink**, which is what `tokens.css` says.
|
||
- *"the components have had their `class` props deleted so passing one is a build
|
||
error"* — false for `Pill`, which had **no `Props` interface at all**, so its
|
||
call sites were unchecked. `CLAUDE.md` names `Pill` as the next place the
|
||
parent-scope defect will happen; the guard documented as protecting it was
|
||
absent on exactly it.
|
||
- A comment citing *"the word-count assertion in the verify step of this session's
|
||
Change Log entry"* — **which did not exist yet.** The same shape §9's Q39 row
|
||
already records as a fair catch.
|
||
|
||
### Files
|
||
|
||
New: `src/pages/about.astro`, `src/components/ContactBand.astro`,
|
||
`docs/reference/lat-case-conference.md`. Changed: `AGENTS.md` (§4, §9, §12),
|
||
`CLAUDE.md`-adjacent agent brief, `docs/01`, `docs/03`, `docs/04`, `docs/06`,
|
||
`docs/07`, `src/data/{site,schema}.ts`, `src/layouts/BaseLayout.astro`,
|
||
`src/components/Pill.astro`, `src/styles/global.css`, `src/pages/index.astro`.
|
||
|
||
### Open for Pouya
|
||
|
||
**Q44** memberships (blocks the group + `memberOf` + cutover) · **Q45** the PDF
|
||
bio · **Q46** (a) ENE / DSD / advisory gating, (b) §11 as a source for
|
||
definitional expansions · **Q47** `jobTitle` without `worksFor` · plus
|
||
**Q23**, **Q34**, **Q38**. Live reminders: **R1**, **R10**, **R13**, **R15**.
|
||
|
||
**Next:** step 4 — `/mediation/`, `/arbitration/`, `/med-arb/`. `/arbitration/`
|
||
is where §4's paired-disclosure condition is hardest: it offers all three forms
|
||
and must state the Q.Arb stage plainly, *"and neither half may be dropped."*
|
||
|
||
## 2026-08-27 (w) — Build step 2: `/` ships. Q35, Q37 and Q39 close, and Q39's answer was that this register had been reasoning from a falsehood
|
||
|
||
**Pouya ruled on all five parked items in one message.** Four are implemented
|
||
here; R1 is acknowledged and stays live by design. The most important of them
|
||
did not confirm this file — it corrected it.
|
||
|
||
### Q39 — ANSWERED, and my assertion was FALSE as a universal
|
||
|
||
His words: *"My assertion was FALSE as a universal; correct it, then close the
|
||
question simply."* He checked rather than defended, against
|
||
`ontario.ca/page/training-family-arbitrators`.
|
||
|
||
**Family arbitration in Ontario is gated.** Prescribed training: 14 hours on
|
||
screening for domestic violence and power imbalances, 30 hours of Ontario family
|
||
law for arbitrators outside the Ontario or another Canadian bar, and 10 hours
|
||
ongoing per two-year period with five on domestic violence or power imbalance.
|
||
**`claims-auditor` produced this counter-example from inside the repo on
|
||
2026-08-26 and it was right.**
|
||
|
||
**The source is now IN THE REPO** — `docs/reference/ontario-family-arbitration-
|
||
training.md`, retrieved 2026-08-27 with its provenance and method. That closes
|
||
R14 for the half of the proposition it covers, and §4 now says which half that
|
||
is, because the distinction matters more than the citation:
|
||
|
||
- The extract establishes the **family** gate **directly**.
|
||
- It establishes the **commercial** half only by **absence** — it neither
|
||
mentions nor excludes commercial arbitration. A government page about family
|
||
arbitrators is not authority for what a commercial arbitrator needs.
|
||
|
||
So *"commercial arbitration in Ontario requires no licence and no designation"*
|
||
is recorded as **Pouya's stated position, deliberately unstamped**, with the
|
||
citation attached to the family half only. **A footnote must not be allowed to
|
||
promote the scoped form back into a universal.**
|
||
|
||
**What actually disposes of the question is the scope exclusion, not the law.**
|
||
Pouya does not do family arbitration. §4 Offerings carries it as **NOT
|
||
OFFERED — a scope exclusion, not a gating problem**, so the prescribed-training
|
||
requirement never bears on this practice at all. `Shareholder & Family Business`
|
||
means commercial disputes among family shareholders; its page must say plainly
|
||
that family law matters are not accepted — **one sentence, not a section**, on
|
||
his instruction that it earns its place only by saving a wasted intake call.
|
||
Recorded in `docs/01` §`/practice/shareholder/` for build step 5.
|
||
|
||
### The false universal had survived in three more places, and the grep found them
|
||
|
||
Correcting the paragraph that carried it was not the fix. `grep -rn "Anyone may
|
||
be appointed"` plus a paraphrase sweep for `No designation is required`:
|
||
|
||
```
|
||
$ grep -rn "anyone may be appointed\|Anyone may be\|No designation is required" \
|
||
--include='*.md' --include='*.astro' --include='*.ts' .
|
||
AGENTS.md:238 <- my new text, quoting what was struck (correct)
|
||
AGENTS.md:313 <- §4 BOUNDARY bullet: "Mediation and arbitration are ungated" FIXED
|
||
AGENTS.md:548 <- §9 Q33 closure row, bolded as an assertion FIXED
|
||
AGENTS.md:774 <- Change Log entry (v), append-only history (correct)
|
||
src/components/SiteHeader.astro:141 <- a live comment in shipped source FIXED
|
||
```
|
||
|
||
The §4 instance is the one worth dwelling on: it was in the paragraph headed
|
||
**THE BOUNDARY, AND IT IS NOT NEGOTIABLE**, which is the worst place in this
|
||
file for an unscoped claim about a class of activity. The boundary paragraph was
|
||
breaching its own boundary.
|
||
|
||
### Q35 — ANSWERED, all four items, and the answer supplied a gate that was missing
|
||
|
||
- **Med-Arb** — *"he holds Q.Med and now accepts arbitration appointments, so
|
||
both halves are live. Keep it in the nav. Removing it unilaterally orphaned
|
||
the page — restoring it was right."* Now its own §4 Offerings row. It stays in
|
||
the footer sitemap; `docs/01` keeps it out of the *primary* nav deliberately
|
||
and that is unchanged.
|
||
- **The six subject-matter labels** — *"subject-matter labels, already governed
|
||
by `docs/03`'s 'positioning, not history'. They pass test 1; test 2 is the
|
||
page's job."*
|
||
- **THE GATE** — *"Add the publication gate you identified was missing... That
|
||
hole is why Med-Arb sat in the footer under a paragraph telling readers not to
|
||
infer it."* §4 gains **Subject-matter areas — the publication gate**: a
|
||
practice area may be named where (1) he can competently accept an appointment
|
||
in that subject matter, and (2) the page frames it as positioning without
|
||
claiming history. Condition 1 is about the label; condition 2 is about the
|
||
page. **Nothing in the nav or footer is unrowed or ungated any more.**
|
||
|
||
### Q37 — ANSWERED. The label changes, and the reasoning is the finding
|
||
|
||
`JD + ML` is labelled **"Legal training and engineering practice"**, not "Law and
|
||
engineering". Pouya: *"The parallel was doing the implying — a degree and a
|
||
practice under one noun. The asymmetry is the honest part."* A JD is a degree;
|
||
engineering is a verified practice. Rendering them as two instances of one thing
|
||
invited the reader to supply the symmetry, and for "Law" the missing half is a
|
||
licence. It is longer and deliberately lopsided; `CredentialRow` carries a
|
||
comment telling the next reader not to tidy it back into a parallel.
|
||
|
||
### Q38 / R13 — the committed SVG does not close it, and my walk-back went too far
|
||
|
||
Pouya: *"Keep it committed, keep the AVIF render path. Your own measurement is
|
||
the reason: 257 KB wrapping seven embedded base64 PNGs. It renders faithfully
|
||
because it IS the raster. Your first characterisation was accurate and the
|
||
walk-back went too far."* Q38 and `docs/02` now hold both halves at once — the
|
||
fidelity is real, and it is bought with embedded raster, which is exactly why
|
||
fidelity was never the question. R13 stays open.
|
||
|
||
### Q32 — Pouya ratifies the reconciliation, and identifies that his own step 3 would have broken the layout
|
||
|
||
*"My 1.23:1 was measured from the path's coordinate hull rather than the curve,
|
||
and step 3 of my Q32 ruling would have broken the layout had you followed it.
|
||
Your reconciliation was right. The tangency was the only sound ground of the
|
||
three."* Recorded because a ruling that turns out to be wrong in one of its three
|
||
grounds is exactly the thing this file exists to keep visible.
|
||
### Build step 2 — `/` ships. Zero JavaScript, and six components
|
||
|
||
Eight sections specified in `docs/01` §`/`; **seven are built.** Hero ·
|
||
credential row · the approach · two processes · six practice areas · process
|
||
preview · contact band. New components, all from `docs/02`'s list: `Eyebrow`,
|
||
`SectionHeading`, `Pill`, `CredentialRow`, `PracticeCard`, `ProcessStep`, plus
|
||
`src/data/schema.ts` for the JSON-LD.
|
||
|
||
**Section 7, Latest insights, is NOT built, and that is the only spec item this
|
||
page does not deliver.** `src/content/insights/` is empty; the collection, the
|
||
`ArticleCard` component and the drafted slate all arrive together at step 7
|
||
(`docs/01` §Build order, D9). Rendering it now means shipping a component's
|
||
scoped CSS to every visitor for an empty block, plus a props surface with no
|
||
call site — already an open finding against `InfinityMark`. `SiteHeader` gates
|
||
the Insights nav item on the same collection, so the page and the nav appear
|
||
together. The omission is commented in the page source, not just here.
|
||
|
||
**Deviations from spec, each deliberate and each recorded in place:**
|
||
|
||
- **The credential row has FOUR slots, not `docs/01`'s three.** §4 Offerings'
|
||
paired-disclosure condition is the higher authority and requires the stage of
|
||
the arc stated wherever arbitration is offered; `/` says *arbitration
|
||
appointments* in its second sentence, so the stage belongs on this page and
|
||
not only in the footer. `docs/03` already authorised a fourth slot and now
|
||
records that on `/` it is required.
|
||
- **No booking link in the contact band**, which `docs/01` item 8 asks for.
|
||
Booking is parked (R6) and `CONTACT.bookingUrl` is `null`. Stated, not
|
||
silently dropped.
|
||
- **The masthead tagline is suppressed on `/`.** It is the same string as the
|
||
hero eyebrow, so at ≥76 rem the page opened with the same six words twice —
|
||
step-1 review finding #10, left open to "decide at step 2". The hero keeps it
|
||
(`docs/01` puts it there and gives it copy underneath to qualify it); the
|
||
masthead drops it, because the masthead is the placement Q33-orig objected to.
|
||
This only ever removes a claim from one page.
|
||
- **The step-1 proof sheet at `/type-scale/` is deleted**, as its own comment,
|
||
`InfinityMark`'s comment and `astro.config.mjs`'s sitemap filter all said it
|
||
would be. Five live references to it survived the deletion and were found by
|
||
`grep`, including §7's Client JS row, which cited
|
||
`dist/type-scale/index.html` as the file proving the site ships no JavaScript.
|
||
|
||
### R11 at the phase boundary — two pins were stale, one hold was too wide
|
||
|
||
Run before writing any code, which is what R11 asks. `astro` **7.2.7 → 7.2.9**
|
||
(two patches inside 48 hours). `typescript` **^5.9.3 → ^6.0.3** — a full major
|
||
behind and installable. §7 had recorded the TypeScript hold as "held at 5.x",
|
||
which was **too wide by a whole major**: 7.0.2 is genuinely blocked
|
||
(`typescript-eslint@8.68.0` peers `>=4.8.4 <6.1.0`, `@astrojs/check@0.9.10`
|
||
peers `^5 || ^6`), but 6.0.3 is stable and both peers accept it. The row now
|
||
names the version, the blocker, and the condition that ends the hold. Committed
|
||
separately as `8a2f513` so step 2's verification is not confounded by a
|
||
toolchain change.
|
||
### What the claims audit found — ten defects, and every one was implication or scope
|
||
|
||
`claims-auditor` returned **FAIL**. Not one finding was a fabrication of the kind
|
||
the old site carried; all ten were implication, scope, or a fact restated
|
||
loosely — *which is exactly where D13 says the risk lives.* All ten are fixed or
|
||
escalated. The four highest-value ones:
|
||
|
||
- **`I mediate and arbitrate commercial disputes`.** §4 verifies that he
|
||
**accepts** arbitral appointments, and separately verifies *"multiple completed
|
||
sole mediations"* — **there is no counterpart row for a completed
|
||
arbitration.** Present-indicative "arbitrate" beside "mediate" invites the
|
||
reader to supply a track record for both. Now offering-shaped: *"I mediate
|
||
commercial disputes from Toronto, and I accept arbitration appointments."* The
|
||
clean form was already on the same page, in the arbitration card.
|
||
|
||
- **The JSON-LD asserted arbitration twice and stated the stage nowhere.** The
|
||
visible page satisfied §4's paired-disclosure condition with the fourth
|
||
credential slot; the machine-readable graph did not. Both node descriptions
|
||
now carry *"the Q.Arb pathway commenced August 2026"*, and `hasCredential`
|
||
stays Q.Med-only — the stage belongs in prose, never in a field that means
|
||
*holds*. **A crawler-only claim is still a claim**, and this is the first time
|
||
the register has had to say so.
|
||
|
||
- **`at one published rate with preparation time included` misdescribed money.**
|
||
Checked against `docs/07-fees.md`: D14's card sets **two** day rates ($2,000
|
||
half, $4,000 full), so "one published rate" reads as one price for both. And
|
||
`docs/07` says in terms that the bundled prep is a **capped** allowance which
|
||
*"must be stated on the page — 'including 2 hours of preparation'... Do not
|
||
quietly fold it into the hours figure."* A home card is the wrong place to
|
||
state it properly and stating it improperly is worse than silence, so the fee
|
||
claim is gone from `/` in both places it appeared. "Published" was also
|
||
forward-looking: `/fees/` ships at step 9.
|
||
|
||
- **`Law and engineering are not blended here`** — Q37's struck parallel,
|
||
relocated from the credential label into body copy **one day after Pouya
|
||
struck it**, and strengthened by attributing both halves to him personally.
|
||
The section now reads *"what the documents say, and what the engineering
|
||
says"*: asymmetric, which was Pouya's whole point. The **argument** `docs/01`
|
||
and `docs/03` specify is unchanged. Whether Q37 formally reaches prose is his
|
||
call — **Q41(a)**.
|
||
|
||
Also fixed: *"what else is offered"* asserted four processes with no §4 row
|
||
(**Q42**); *"LAT pre-hearing mediation"* was a `docs/01` **search intent** read
|
||
as a service (**Q41c**); *"facts most neutrals take on faith"* is an
|
||
unverifiable comparative about third parties, replaced with *"the documents
|
||
rather than the pleadings"* (**Q41b**); the editorial *"with real timing"* is
|
||
gone while the timings themselves stand as specified (**Q43**); and the Q.Arb
|
||
noun is now §4's own — *pathway*, not *designation*.
|
||
|
||
**And the auditor found a stale copy of a fact in §9 itself.** Q8 still listed
|
||
memberships as *"ADRIC, ADRIO, OBA sections"* — **the Canadian Tax Foundation
|
||
was missing**, added to §4 on 2026-08-26. A second copy of a fact in a place
|
||
nobody re-reads is the failure mode §7's single-source rule exists to stop, and
|
||
this is the same shape as the stale enumeration that was found inside
|
||
`claims-auditor`'s own brief. Fixed, and rewritten as a pointer to §4 rather
|
||
than a second list. It would have bitten at step 3, the first page to publish
|
||
memberships.
|
||
|
||
### Seven defects I found in my own work before the reviewers reported
|
||
|
||
Kept because the pattern in them is the point, not the count. Full list in the
|
||
verification section; the three worth reading:
|
||
|
||
- **`<Picture widths>` declared the untouched 1600 px master as the `<img src>`
|
||
fallback** — 254,626 bytes, for a 476 px slot. Passing `width`/`height`
|
||
alongside `widths` pins it to the 960 variant (78,665 B) and the 1600 px file
|
||
stops being generated. **The build log hid it completely**: it printed
|
||
"before: 349kB" for every variant either way. Found by reading the emitted
|
||
`src` and that file's real dimensions.
|
||
|
||
- **Naming a prop `as` silently turned off prop type-checking for a whole
|
||
component.** `astro check` reported it only as `ts(6196) 'Props' is declared
|
||
but never used`, which reads like lint noise. It is not: `<Eyebrow dot as="h9"
|
||
bogusProp={1} />` compiled with **0 errors**, while the same probe against the
|
||
four other new components produced `ts(2322)` on all four. Renaming the single
|
||
identifier to `tag` restored it. **Do not silence a `ts(6196)` with
|
||
`Astro.props as Props`** — that hides the warning and leaves every call site
|
||
unchecked.
|
||
|
||
- **96 px of cream sandwiched between the maroon contact band and the ink
|
||
footer.** Found by looking at a full-page screenshot, not by reading CSS.
|
||
|
||
### And one alarm of my own that was wrong, in the direction of panic
|
||
|
||
Measuring the marks, `img.naturalWidth` came back **64 at every DPR** — which
|
||
looks exactly like *the density ladder is not being generated at all*, i.e. a
|
||
shipped step-1 defect on the header mark of every page. **It is not.** For an
|
||
image chosen from a `srcset` with an `x` descriptor, `naturalWidth` is
|
||
**density-corrected**: a 192 px file selected at 3x correctly reports 64.
|
||
Ground truth from disk: 64×41, 128×82, 192×123, in all three formats.
|
||
|
||
The real defect underneath was smaller and mine: the home page added a **225.5
|
||
px** call site to a component whose ladder was sized for 50 px and 56 px, so it
|
||
upscaled 3.52× at DPR 3. `InfinityMark` now takes `width` and `loading`; the
|
||
approach mark passes `width={232}` (→ 232/464/696, covering 676 device px) and
|
||
`loading="lazy"`, since it sits a screen and a half down. All three instances
|
||
now measure ≤1.0× upscale at DPR 1, 2 and 3.
|
||
|
||
**That is the fifth time on this project that my own instrument misread**, and
|
||
the pattern across all five is the same: a number that looks like a finding, from
|
||
a probe nobody checked. `naturalWidth` joins `timeout`, the coordinate-hull
|
||
bbox, the worst-deviating-instance filter, and the document-level overflow check.
|
||
`CLAUDE.md` gains the general rule.
|
||
|
||
### What the code review found — and finding 1 is the same defect for the FOURTH time
|
||
|
||
`adversarial-reviewer` returned **fourteen findings, three blocking.** It also
|
||
noted that the working tree moved under it mid-review, because the claims fixes
|
||
above were being applied while it ran, and it re-verified each finding against
|
||
the current tree so it could say which were still live. That is the right
|
||
behaviour and it is worth recording as the reason the two reviewers should not
|
||
be run against a moving target next time — brief them, then stop editing.
|
||
|
||
**1. BLOCKING. `class="section-head"` on `<SectionHeading>` never matched, and
|
||
three section headings collided with their content.**
|
||
|
||
This is the defect `CLAUDE.md` already records twice under *"A parent cannot
|
||
style a child component's root element"*, which then recurred a third time with
|
||
`<Picture>` inside `InfinityMark` — and I wrote a fresh warning about it into
|
||
`Eyebrow` and `Pill` in this very diff and then did it again in the page.
|
||
|
||
The emitted evidence, side by side:
|
||
|
||
```
|
||
dist/_astro/index.*.css .section-head[data-astro-cid-lcdefpme]{margin-block-end:var(--space-7)}
|
||
dist/index.html <div class="heading-block section-head" data-astro-cid-ypavld2q>
|
||
```
|
||
|
||
Measured before the fix: `margin-block-end: 0px` and a **0 px gap** to the next
|
||
block on all three call sites — 48 px of intended separation gone. Not merely
|
||
tight: `.display` sets `line-height: 0.98`, so the glyphs overflow the line box
|
||
and *"Two processes."* sat over the top edge of the Mediation and Arbitration
|
||
cards. **`astro check` reported 0 errors and `eslint` was clean**, which is
|
||
exactly what `CLAUDE.md` says this failure looks like: no error, no warning, and
|
||
the CSS reads correctly in the source.
|
||
|
||
**I had looked at a full-page screenshot of this section and passed over it.**
|
||
The gap looked plausible because a serif's descender space reads as air. A
|
||
screenshot is not a substitute for a computed-style assertion, and the reverse is
|
||
also true — three of my own findings today came only from looking.
|
||
|
||
Fixed by wrapping each in a page-owned `<div class="section-head">`. Measured
|
||
after: **48 px margin, 48 px gap, all three.** And the prop is gone —
|
||
`SectionHeading` no longer accepts `class`, so passing one is now a **build
|
||
error** rather than a silent no-op. Same deletion applied to `CredentialRow`,
|
||
`Pill`, `ProcessStep`, `PracticeCard` and `Eyebrow`, all of which declared a
|
||
`class` prop with no call site: five more invitations to the same mistake.
|
||
|
||
**2. BLOCKING, already fixed in flight — the mark was upscaled 3.5× on the home
|
||
page.** Covered above. The reviewer added the follow-up that mattered: the fix
|
||
**invalidated a figure cited as load-bearing reasoning in three places.**
|
||
`docs/02` §Components and §9 Q38 both argued *"257,278 ÷ 3,063 = 84×"* against
|
||
the committed SVG, and none was updated when a second, larger ladder appeared —
|
||
the home page's mark takes **14,555 B** at DPR 2, so the ratio there is ~11×.
|
||
That is the SES-DKIM duplication in a new costume: the copy nobody re-reads goes
|
||
stale. All three now carry both ladders and the instruction to **quote the size
|
||
with the call site, never on its own.**
|
||
|
||
**3. BLOCKING, partly fixed in flight — 234 px of horizontal content loss at a
|
||
large default font size.** The three `minmax(Nrem, 1fr)` grids were mine to fix
|
||
and were fixed; the reviewer then re-measured and found **83 px still going**,
|
||
from two elements this diff introduced:
|
||
|
||
- `.feature` measured **411 px in a 342 px container** — `padding: var(--space-7)`
|
||
is 192 px a side at root 32 px, and `.feature-title`'s min-content did not
|
||
shrink because **`overflow-wrap: break-word` permits a break at layout time
|
||
but does not reduce min-content size.** Now a clamped padding plus
|
||
`overflow-wrap: anywhere`.
|
||
- `.contact-action { flex: none }` is `0 0 auto`, so the button could not shrink
|
||
below its **425 px** max-content. Now `0 1 auto` with `min-inline-size: 0`.
|
||
|
||
**4. The credential row was never "two up on a phone", and its comment said it
|
||
was.** `repeat(auto-fit, minmax(11rem, 1fr))` resolved to a **single 342 px
|
||
track** at 390 px with all four items stacked and the band ~430 px tall — with
|
||
`Q.Arb / Commenced August 2026`, which §4's paired-disclosure condition puts on
|
||
this page, at the bottom of it. The arithmetic is not subtle: two 176 px tracks
|
||
plus a 24 px gap need 376 px and the container is 342. **A measured-sounding
|
||
comment that was false**, which is this project's own named failure mode, written
|
||
by me on the same day I added the rule about it to `CLAUDE.md`.
|
||
|
||
Now explicit: `repeat(2, minmax(0, 1fr))`, becoming four at 56 rem where four
|
||
genuinely fit. Measured after: **2 rows at 320 / 390 / 640 / 768** (band height
|
||
296 / 280 / 272 / 260 px, down from ~430), **1 row from 896 px.**
|
||
|
||
**5. A §9 row cited a `grep` "in the Change Log" before the entry existed.** Q39
|
||
said so in the present tense while the newest heading was still `(v)` — because
|
||
`/build` writes the entry at Phase 6, after review. Fair catch, and the reviewer
|
||
independently re-ran the sweep and confirmed it was genuinely complete. Q39 now
|
||
names the entry.
|
||
|
||
**7. `PROCESS` was hardcoded in the page, against the reason written in
|
||
`site.ts` for centralising the practice blurbs.** *"`/` and `/practice/` both
|
||
render them and two copies of a claim-bearing sentence is one copy that will
|
||
eventually be wrong."* `PROCESS` is the same shape of content, `/process/`
|
||
renders the same five steps at step 6, and the staged step-3 body carried the
|
||
fee claim the claims audit had just found to be **wrong**. It existed in one
|
||
place today and would have existed in two. Moved to `src/data/site.ts`.
|
||
|
||
**8. The section-7 omission was recorded only in a comment in the file that
|
||
deviates.** `docs/01` was edited in this same diff and not amended. Compare
|
||
`SiteHeader`'s sticky-threshold deviation, which was written back into `docs/02`
|
||
— the project's own precedent. `docs/01` §`/` item 7 now records it.
|
||
|
||
**9. Two of FOUR above-the-fold faces were not preloaded, and the comment said
|
||
"the two faces used above the fold".** Network probe on a cold cache: `/`
|
||
requests four. The **serif italic** sets `<em class="it">the room</em>` inside
|
||
the `<h1>`, and a swap there moves the last line of a 96 px headline — now
|
||
preloaded. **Geist Mono** sets the eyebrow, which is the first visible text, and
|
||
is deliberately **not**: preloading it puts 95,688 B of font on the critical path
|
||
instead of 72,560 B, for one short line of 12 px reflow. A trade, stated as one,
|
||
revisited against Lighthouse at step 7. *The reviewer was straight about its own
|
||
limit here: throttled to slow 4G + 4× CPU it measured **LCP 896 ms, CLS 0.000**
|
||
and could not reproduce a shift.*
|
||
|
||
**10. Dead API surface.** `Eyebrow`'s `tag` prop had zero call sites, so its
|
||
`<span>` branch was unreachable and the file carried two near-identical
|
||
templates for it — deleted, keeping the `as`-naming discovery. `PORTRAIT_ALT` in
|
||
`schema.ts` was exported and referenced nowhere — deleted. `SectionHeading`
|
||
exposed both a `title` prop and a `heading` slot for one job — the prop is gone.
|
||
Five `class?: string` props — gone, per finding 1.
|
||
|
||
**11–14, all `consider`, all recorded rather than churned.** The
|
||
duplicate-density `srcset` and the `/about/`-404-in-JSON-LD note are now **§7
|
||
rows** so neither is re-discovered as a defect in this repo. The portrait's 1:1
|
||
declaration under a 4:5 crop stays, with its reasoning already in the source and
|
||
CLS measured at 0. The named-landmark inconsistency is fixed by **removing**
|
||
`aria-labelledby` from the four content sections that have visible `<h2>`s and
|
||
keeping `aria-label` only on the credential band, which has no heading — the rule
|
||
being *name a region only where it has no heading of its own.* That takes the
|
||
region list from eleven entries to six.
|
||
|
||
**And one of its findings was wrong, which it said itself.** The reviewer
|
||
reported seeing **two** portrait fetches at 390 px / DPR 3, flagged it
|
||
low-confidence, and named the likely artefact — `setDeviceMetricsOverride`
|
||
applied around navigation. Checked: **one fetch at 390/DPR 1, 2 and 3 and at
|
||
1280/DPR 2 and 3**, cache cleared each time. It was the artefact. A reviewer that
|
||
states its own uncertainty is doing the job; the answer was to run the probe, not
|
||
to dismiss it.
|
||
|
||
**What it checked and found clean**, so the gap is auditable: 26 real `Tab`
|
||
keydowns dispatched, all 26 focused elements matched `:focus-visible` with a
|
||
visible ring, skip link first; **72/72** hit-test points across eight cards
|
||
resolved to the card's link; heading outline dumped, 23 headings, no skips; every
|
||
computed contrast pair recomputed from scratch including `.approach-metaphor` at
|
||
**11.09:1**; zero `client:*` directives and zero non-JSON-LD `<script>` tags;
|
||
**41 KB total transfer** cold-cache at 1280/DPR 2 with **zero JS bytes**; zero
|
||
`data:` and zero `base64,` in the HTML and CSS; no third-party host; and both
|
||
minifier traps re-verified in the emitted CSS.
|
||
|
||
### Verification — run, not asserted
|
||
|
||
Harness: a zero-dependency CDP driver (Node 22+ has a global `WebSocket`)
|
||
against `--headless=new` Chrome, serving `dist/` over `python3 -m http.server`.
|
||
Every figure below came from a command whose output was read.
|
||
|
||
| Gate | Result |
|
||
|---|---|
|
||
| `npx tsc --version` | 6.0.3 |
|
||
| `npm run check` | **0 errors, 0 warnings, 0 hints** (19 files) |
|
||
| `npm run lint` | clean — ESLint + Prettier |
|
||
| `npm run build` | complete, 1 page |
|
||
| `npm audit` | **0 vulnerabilities** |
|
||
| **Lighthouse** | **NOT RUN — tool unavailable.** `@lhci/cli` removed 2026-08-26; R11's re-add trigger is step 7. Stated, not omitted |
|
||
|
||
**Zero JavaScript, in the emitted page.** `dist/index.html` carries **1**
|
||
`<script>` and it is `type="application/ld+json"`; non-JSON-LD scripts **0**;
|
||
`dist/_astro/*.js` no matches. With script execution disabled at the protocol
|
||
level: **444 DOM nodes, 6,578 characters of visible text, 5,665 px of content** —
|
||
the identical page.
|
||
|
||
**Phase 5, the minifier check.** `grep -o 'animation:[^;}]*' dist/_astro/*.css`
|
||
returns only `animation:none!important` twice, which is the reduced-motion and
|
||
print override. No `animation` shorthand beside `animation-timeline`. Both
|
||
longhand blocks survived: `animation-timeline:scroll()` with
|
||
`animation-name:header-lift`, and `animation-timeline:view()` with
|
||
`animation-name:reveal-in`.
|
||
|
||
**Layout, 14 widths (320 → 1920).** Document overflow **0 at every one**, with
|
||
zero elements past the viewport. **And the elements were measured, not only the
|
||
page** — this is the correction entry (v) owed: every rendered infinity mark
|
||
came back at aspect **1.5654–1.5657** against the master's 1.5657, at all 14
|
||
widths. Header **189 px** ≤414, **141 px** 640–1024, **81 px `sticky`** from
|
||
1056, matching `--header-h`.
|
||
|
||
**Accessibility.** One `<h1>`; heading levels never skipped (outline dumped and
|
||
read). Landmarks 1/2/1/1. **Focus order == DOM order** across 44 focusables.
|
||
Every `<img>` has `alt` and explicit `width`/`height`; 0 missing either; 0 empty
|
||
links. **Contrast: 32 distinct foreground/background/size triples computed from
|
||
what the browser actually painted, at 390 / 768 / 1280 px — 0 failures.** Print
|
||
media: 0 revealed elements at opacity < 1 (10 targets). Reduced motion: 0 hidden.
|
||
|
||
**Touch targets, and the instrument mattered here.** The eight cards report
|
||
26–39 px-tall `<a>` boxes and are **not** a finding: hit-testing nine points per
|
||
card at three widths put **9/9 inside the link on all 24 cards** — the whole card
|
||
is the target via `::after { inset: 0 }`. Two standalone paragraph links **were**
|
||
real at 18 px tall and are fixed. One inline link (164 × 21) is deliberately left
|
||
under WCAG 2.5.8's sentence exception.
|
||
|
||
**Reflow, and one case that is not clean.** Page zoom passes: 1280 at 200% is the
|
||
640 column and at 400% is the 320 column, both 0 overflow, so WCAG 1.4.4 and
|
||
1.4.10 are covered. With the reader's **default font size** at 200% (root 32 px —
|
||
not page zoom) `/` started at **234 px** of overflow at 390 and came down in
|
||
three measured steps to **3 px at 390 and 65 px at 320**: the three
|
||
`minmax(Nrem, 1fr)` grids guarded with `min()`, then `.credentials` made
|
||
explicit, then `.feature`'s padding clamped with `overflow-wrap: anywhere` on its
|
||
title and `.contact-action` allowed to shrink. **`overflow-wrap: break-word`
|
||
permits a break at layout time but does not reduce min-content size** —
|
||
`anywhere` does, and that was the whole of one fix. The residual is the header's
|
||
deliberate `flex-wrap: nowrap` above 66 rem (**602 px** at 1280) plus
|
||
`white-space: nowrap` on the brand name and the headline's 104 px floor; undoing
|
||
either re-opens the measured step-1 header decision, so they stand. Beyond what
|
||
`docs/02`'s floor requires, since page zoom is clean — a robustness margin, not a
|
||
failure. The table is in `docs/02`.
|
||
|
||
**Payload.** HTML **27,334 B** · CSS **26,572 B** (linked, over the 4 kB inline
|
||
threshold) · hero portrait AVIF **5.6 / 7.3 / 11.1 / 14.8 / 21.5 kB** across five
|
||
widths, `<img src>` fallback now the 960 variant at **78,665 B** · mark AVIF
|
||
**1,720 / 3,063 / 4,843 B** at 64 px and **6,017 / 14,555 / 22,639 B** at 232 px
|
||
· fonts ~50 kB preloaded. **JS 0 B** against a 100 kB budget.
|
||
|
||
**Not verified, and named as such.** Lighthouse (above). **The HTML validator was
|
||
not run, and the page carries a known conformance error:** 4 of 12 `srcset`
|
||
attributes declare two candidates at 1x, because Astro's `densities` emits
|
||
`url, url 1x, url 2x, url 3x` and a descriptor-less candidate is implicitly 1x.
|
||
Harmless in browsers; step-1 review finding #8, still open. **Do not claim
|
||
"validator clean".** *(And my first check of it reported "ok" — it compared
|
||
`undefined` against the string `'1x'`.)*
|
||
|
||
### Sweeps — the commands, not the claims (R8)
|
||
|
||
```
|
||
$ grep -rn "anyone may be appointed\|Anyone may be\|No designation is required" \
|
||
--include='*.md' --include='*.astro' --include='*.ts' .
|
||
-> 5 hits: 2 correct (my new text quoting the struck line; entry (v) history),
|
||
3 FIXED (§4 boundary bullet, §9 Q33 row, SiteHeader comment)
|
||
|
||
$ grep -rn "Med-arb\|med-Arb" --include='*.astro' --include='*.ts' --include='*.md' .
|
||
-> 1 hit, FIXED (index.astro:313 -> Med-Arb, the form §4 and docs/01 use)
|
||
|
||
$ grep -rn "Law and engineering" --include='*.md' --include='*.ts' --include='*.astro' .
|
||
-> label FIXED in site.ts + docs/03; the PROSE instance on / is reworded and
|
||
the two spec instances (docs/01:136, docs/03:150) are Q41(a) for Pouya
|
||
|
||
$ grep -rn "type-scale\|proof sheet" ... | grep -v dist
|
||
-> 5 live references to the deleted page, all FIXED (§7 Client JS row,
|
||
robots.txt, docs/05, brand-assets.md, InfinityMark.astro). Change Log
|
||
entries (u) and the struck Q33-orig row keep theirs — append-only history
|
||
|
||
$ grep -cEi 'OCNI|Law Society|LSO|testimonial|Since 20|London|New York' dist/index.html
|
||
-> 1, and it is a FALSE POSITIVE: "I aLSO practise". Case-sensitive: 0
|
||
|
||
$ grep -cEi 'leading|premier|top-rated|best|proven|guarantee|extensive' dist/index.html
|
||
-> 2, both FALSE POSITIVES: "the pLEADINGs" twice. No superlative on the page
|
||
|
||
$ grep -cE 'LegalService|worksFor|priceRange|aggregateRating' dist/index.html
|
||
-> 0
|
||
```
|
||
|
||
### Superseded
|
||
|
||
**Entry (v)'s "⏸ RESUME HERE" section is spent.** All five items it listed as
|
||
awaiting a ruling — Q35, Q39, Q37, Q38/R13, R1 — were ruled on 2026-08-27 and are
|
||
handled above. Its six non-blocking review findings: **#7 fixed** (`--text-2xs`,
|
||
`--space-05`, `--focus-offset` added), **#8 still open and now measured** (4 of 12
|
||
srcsets; see Verification), **#9 unchanged** (`--header-h` has 0.81 px of
|
||
headroom), **#10 fixed** (the masthead tagline is suppressed on `/`), **#11
|
||
unchanged** (~3.16 MB of brand binaries), **#12 fixed, and by deletion rather than by
|
||
use** — `InfinityMark`'s `class` prop is **removed**. It had no call site and
|
||
`class:list` put it on the `<img>`, so a parent writing
|
||
`<InfinityMark class="foo" />` would have got a rule compiled against the
|
||
parent's cid that never matches: the exact defect `CLAUDE.md` records twice on
|
||
this project, offered as an API. `label` stays with its reason written down (all
|
||
three current call sites are decorative; the next one may not be), and `width`
|
||
and `loading` are new and used. Entry (v) is not edited; this is where the
|
||
state lives now.
|
||
|
||
---
|
||
|
||
## 2026-08-26 (v) — The mark was wrong; §4 gains an Offerings category; and two of my own tools lied to me
|
||
|
||
**Who:** Pouya ruled on the mark (Q32), on arbitration (Q33, Q36), and on the
|
||
asset convention. Claude Code implemented; `adversarial-reviewer` and
|
||
`claims-auditor` ran on the result. **The claims audit returned FAIL with 13
|
||
findings, and the sharpest of them were against text written an hour earlier in
|
||
this same entry's work.** Most of what follows is those findings.
|
||
|
||
### Q32 — the infinity mark was a wrong shape, and it had shipped
|
||
|
||
Pouya rendered the committed path against the master and rejected it. Two of his
|
||
three grounds reproduce from the path alone and are now verified here:
|
||
|
||
- **TANGENT, NOT CROSSING.** All four cubic branches meet the origin at exactly
|
||
90°, so the loops are mutually tangent on a vertical line rather than crossing.
|
||
At stroke-width 28 that renders as **two kissing circles** — the one thing an
|
||
infinity mark must not be `[verified 2026-08-26 — tangent vector computed per
|
||
segment]`. This alone disqualifies the shape.
|
||
- **WRONG PROPORTION.** The master's ink bounding box is **2668 × 1704 =
|
||
1.5657:1** `[verified 2026-08-26 — measured]`.
|
||
- **FLAT.** Two uniform strokes standing in for a shaded ribbon: a band of
|
||
variable width twisting in three dimensions, maroon into champagne, passing
|
||
over itself at the crossing.
|
||
|
||
**The 1.23:1 figure is reconciled, and it was a real measurement.** It is the
|
||
bounding box of the path's **coordinates**, not of the **curve**: control points
|
||
sit at y = ±160 where the curve reaches only ±120, so the coordinate hull is
|
||
400 × 320, and with stroke-width 28 on all four sides **428 × 348 = 1.2299**.
|
||
Pouya's number exactly. It is a trap rather than a slip — x is monotone on every
|
||
segment, so the control points give the *right* width and a 33% inflated height,
|
||
and the usual "does the width look right?" check passes.
|
||
|
||
Two consequences worth keeping. **The direction was inverted:** measured from the
|
||
curve, the traced path is 6.4% *wider* than the master, not squatter. And the
|
||
declared viewBox 440:280 = 1.5714 sits within **0.35%** of 1.566 — so step 3 of
|
||
the ruling, re-tune the layout to the true aspect, was **0.18px of work at the
|
||
shipped 2rem**, and re-tuning to 1.23 would have *broken* it: for any
|
||
given width, 1.2299 allocates 1.5657/1.2299 = **27% more height** than the mark
|
||
actually occupies, so the header would have been rebuilt around a box a quarter
|
||
too tall. Where 1.566 does matter is step 2: a tight crop to ink is
|
||
exactly the measurement where 1.667 and 1.566 differ visibly, which is why the
|
||
render source is cropped to the master's ink box and pinned at `667 / 426` rather
|
||
than inheriting 11:7. **The ratio was never sufficient grounds on its own.
|
||
Tangency was, and it is exact** — both lobes are confined to their own
|
||
half-plane, so the signed crossing number is 0, and at 2rem the strokes fuse into
|
||
a single mass across 61% of the mark's height.
|
||
|
||
**The traced path is deleted, not kept as a fallback**, on Pouya's instruction:
|
||
*a wrong mark that renders is worse than a missing one, because it stops looking
|
||
wrong.* `public/favicon.svg` deleted with it; the favicon chain is regenerated
|
||
from the real artwork.
|
||
|
||
### Why two review passes could not catch it — and the rule that follows
|
||
|
||
`InfinityMark.astro` carried a scrupulous provenance comment stating that the
|
||
path was traced from the **old site's loading placeholder** and that a
|
||
placeholder is not necessarily canonical. It was correct, it was prominent, and
|
||
**it did not help**, because the artwork it would have to be checked against was
|
||
not in the repository. The doubt was stated and structurally uncheckable.
|
||
|
||
**New rule in `CLAUDE.md`, and R14:** *anything a spec makes a claim about must
|
||
be reachable from the repository.* If the artefact lives only in Drive, in a
|
||
console, or on a laptop, the claim is **unverifiable by construction**, not
|
||
merely unverified. Second occurrence — Q24 was `AWS-Hosting-Guide.md`, the only
|
||
record of how the infrastructure was built, living outside the repo.
|
||
|
||
### Two process failures of my own, both in the same shape
|
||
|
||
1. **I reported the brand assets unreachable. They never were.** Four commands of
|
||
the form `timeout 60 ls "$DRIVE"` returned empty output; I read that as an
|
||
empty directory and told Pouya the ruling could not be executed. **`timeout`
|
||
is not installed on macOS** — the commands had never run. The Drive was fully
|
||
readable the whole time and the masters were found within a minute of using a
|
||
tool that exists.
|
||
2. **I reported malformed HTML** — `<picture="true">` and
|
||
`style="block-size:2rem"="true"` — and rewrote a component around it. It was
|
||
**my own regex**, stripping an attribute's name and leaving its value. The
|
||
markup was always valid. The rewrite was reverted.
|
||
|
||
Both are the same failure as *a sweep is a command, not a claim*: an assertion
|
||
resting on output that was never produced, or was produced by my own filter.
|
||
**New rule in `CLAUDE.md`:** *a command that did not run is not evidence of
|
||
absence* — check the tool exists, read exit status, not just stdout.
|
||
|
||
### What the mark is now
|
||
|
||
`src/assets/brand/` holds the master (3000 × 3000, alpha), the tight crop that is
|
||
the render source (2668 × 1704, so **the file's aspect ratio is the mark's**),
|
||
the full lockup, and the SVG Pouya added. `InfinityMark.astro` renders it through
|
||
Astro's `<Picture>`; a browser downloads **3,063 bytes** of AVIF on a Retina device.
|
||
|
||
**Correction inside this entry.** The SVG was first described here and in three
|
||
files as "a raster in a vector wrapper". That was unfair: rasterised at 8333 px
|
||
it **reproduces the master exactly, at the same 1.566:1** `[verified 2026-08-26]`.
|
||
What rules it out is **payload and composition** — 257,278 bytes against 9,468,
|
||
plus seven embedded base64 PNGs that would breach `CLAUDE.md`'s no-base64 rule.
|
||
Corrected in the component, `docs/02`, Q38 and `docs/reference/brand-assets.md`.
|
||
|
||
**`width={320}` on `<Picture>` is load-bearing.** Without it Astro emits the
|
||
untouched 2668 px master as the `<img src>` fallback — **1,146,406 bytes** — sitting
|
||
in `dist` looking like an optimisation had happened.
|
||
|
||
**Documented, temporary exception to `docs/02`'s "inline SVG, never a PNG"**,
|
||
tracked as **Q38** (a vector master that is faithful *and* light) with **R13** so
|
||
it cannot become permanent by neglect — Pouya's own warning when he made the
|
||
ruling.
|
||
|
||
### Q33 and Q36 — arbitration, and a new §4 category
|
||
|
||
**Both answered: Pouya accepts arbitration appointments now** — sole,
|
||
party-appointed and co-arbitration. His reasoning: ADR designations are
|
||
**voluntary credentials, not licences**, so the constraint was always
|
||
**positional**, never legal. `Mediation · Arbitration · Toronto` is **restored to
|
||
the masthead**; `docs/04`'s home `<title>` stands as specified.
|
||
|
||
**§4 gains an Offerings subsection** — a second category beside the credential
|
||
register, with the test: **competence for an offering, permission for a
|
||
credential.** Three specs that asserted the converse were swept
|
||
(`docs/01`, `docs/03`, `docs/07-fees.md`) — and that sweep had been *claimed* in
|
||
the Q36 closure before it was *run*, which `claims-auditor` caught. `docs/03`'s
|
||
model sentence was wrong in **both** halves and in opposite directions, which is
|
||
why it had survived two audits.
|
||
|
||
### What the claims audit found in the new section, and how it was resolved
|
||
|
||
Four structural defects in text written the same hour:
|
||
|
||
- **The masthead justification answered the wrong objection.** Q33-orig had
|
||
objected to **placement** — a line under his name on every page *"where nothing
|
||
qualifies it"* — not to entitlement. The section refuted an entitlement
|
||
objection nobody raised. Corrected, and the substitution is recorded rather
|
||
than tidied away.
|
||
- **§4's own paired-disclosure condition was unmet by the shipped build.** The
|
||
section says the site *"makes the first while stating the second plainly"* and
|
||
*"neither half may be dropped"* — yet the masthead shipped on every page while
|
||
the Q.Arb stage shipped on none, and `CREDENTIALS.inProgress` existed in
|
||
`site.ts` rendered nowhere. **The footer designation strip now reads
|
||
`Q.Med (ADRIC / ADRIO) · Q.Arb — commenced August 2026` on every page.**
|
||
- **The offering test handed the gating question to the subject.** Its closing
|
||
sentence, *"that is his call, not the register's"*, attached to the whole
|
||
preceding question including *whether the activity is gated* — a clean
|
||
walk-through for a future writer. Split in two: **gating is this register's
|
||
question and needs a checkable source; competence is his and only his.**
|
||
- **The category had no gate and no defined extent.** No rule said an offering
|
||
needs a row before it may be published, and `Med-Arb` was sitting in the
|
||
site-wide footer as an offering three sentences below a paragraph saying not to
|
||
infer exactly that. Both fixed: the publication rule is stated, scope is
|
||
defined (**an offering is a PROCESS; a subject-matter area is not**), and
|
||
**Med-Arb is removed from the footer pending Q35(a)**.
|
||
|
||
**And the finding that matters most: four unsourced propositions of Ontario
|
||
law.** *"Anyone may be appointed an arbitrator in Ontario. Nothing in law gates
|
||
the role behind a designation."* `[verified — Pouya]` means *the subject reported
|
||
it*, which can establish what he offers and **cannot establish a proposition of
|
||
law**. The auditor produced a counter-example from inside the repo: the site
|
||
ships a **Shareholder & Family Business** practice area, and **family**
|
||
arbitration in Ontario is understood to be one of the places where arbitrator
|
||
qualification *is* prescribed. §4 now carries the proposition as **the
|
||
architect's stated basis, deliberately unstamped**, scoped to **commercial**
|
||
arbitration, with the universal removed — and **Q39** opened. This record will
|
||
not assert Ontario law, and neither will a self-report.
|
||
|
||
### Questions and reminders
|
||
|
||
**Closed:** Q32 (the reconstruction was wrong), Q33, Q36.
|
||
**Narrowed:** Q35 — `Arbitration` resolved; **Med-Arb** and the two
|
||
subject-matter labels remain, now under the scope note that says which rule
|
||
governs them.
|
||
**Opened:** **Q38** (vector master), **Q39** (family arbitration and gating).
|
||
**§12:** **R13** (the raster is temporary), **R14** (assets must be in-repo).
|
||
|
||
### Verification — run, not asserted
|
||
|
||
`npm run check` 0/0/0 · `npm run lint` clean · `npm run build` 0 errors ·
|
||
`npm audit` **0 vulnerabilities**.
|
||
|
||
Measured in headless Chrome at 320/375/640/768/1000/1023/1024/1100/1199/1200/1201/1279/1280/1281/1440/1600,
|
||
**with a seventh nav item injected** for the step-7 state:
|
||
|
||
- **0 overflow, 0 focus-order inversions, 0 tap targets under 44 × 44** at every
|
||
width; closed `<details>` panels contribute 0 hidden tab stops
|
||
- Header a constant **81px** at every sticky width — 32 padding + 48 reserved
|
||
brand block + **the 1px border I had forgotten**, which is why `--header-h` is
|
||
measured rather than added up
|
||
- Restoring the tagline **broke the 64rem fit** (84px past the content box at
|
||
1024 with seven items) and was re-tuned: tagline gated at 75rem, nav gap moved
|
||
to **80rem so two things do not grow at one breakpoint** — 4px of spill at
|
||
exactly 1200px caught that
|
||
- **0 `<script>` tags, 0 `.js` files**; both scroll-driven animations attach live
|
||
- Print: all four revealed cards present · **760 words** with no JavaScript
|
||
|
||
### ⏸ RESUME HERE — session ended mid-flight, 2026-08-26
|
||
|
||
Pouya went mobile. The tree is committed and green; nothing is half-applied.
|
||
**Pick up at the numbered list below.**
|
||
|
||
**State:** `npm run check` 0/0/0 · `npm run lint` clean · `npm run build` 0
|
||
errors · `npm audit` 0 vulnerabilities. Both `adversarial-reviewer` blocking
|
||
findings on the mark are fixed and re-measured. Build step 1 is complete; step 2
|
||
is `/` (`docs/01` §Build order).
|
||
|
||
**Waiting on Pouya — nothing proceeds on these without a ruling:**
|
||
|
||
1. **Q35** — may the nav and footer name `Med-Arb`, `Energy, Grid & Regulatory`
|
||
and `Shareholder & Family Business`? Both halves go to him **together**;
|
||
`Med-Arb` was removed from the footer for a few hours and restored, because
|
||
acting on one half unilaterally was wrong and orphaned the page.
|
||
2. **Q39** — family arbitration. §4's arbitration rows are scoped to
|
||
**commercial** pending an answer. This one has a legal dimension the register
|
||
cannot resolve from a self-report.
|
||
3. **Q37** — is `JD + ML → "Law and engineering"` the right label? Answer before
|
||
step 2 renders the credential row.
|
||
4. **Q38 / R13** — the commissioned vector master. Until it lands the mark ships
|
||
as a raster under a documented exception.
|
||
5. **R1** — the licensure framing is interim and now carried by shipped pages.
|
||
|
||
**Unresolved review findings, all non-blocking, none shipped-defect:**
|
||
|
||
- `adversarial-reviewer` #7: `gap: 2px` and `font-size: 0.6875rem` in
|
||
`SiteHeader` are magic numbers; add `--text-2xs` / `--space-05` or record the
|
||
deviation.
|
||
- #8: Astro's `<Picture>` + `densities` emits a duplicate `1x` descriptor in
|
||
`srcset` — an HTML conformance error, harmless in browsers. Do not claim
|
||
"validator clean" on a page carrying it.
|
||
- #9: `--header-h` has 0.81 px of headroom at ≥76 rem. A font-metric change
|
||
pushes the brand past its 48 px reservation with no build error.
|
||
- #10: the masthead tagline duplicates the home hero eyebrow, so `/` will open
|
||
with the same words twice. Decide at step 2.
|
||
- #11: ~3.16 MB of brand binaries; the 1.1 MB derived crop is reproducible from
|
||
the committed master and could go if Astro could crop at build time.
|
||
- #12: `InfinityMark`'s `label` and `class` props have no call site.
|
||
|
||
**One correction owed to the record.** Entry (v)'s verification section says
|
||
"0 overflow at every width". That was true and **misleading** — the page-level
|
||
check passed *because* the brand block absorbed the deficit by crushing the
|
||
logo. The harness now asserts the rendered aspect ratio of every mark instance,
|
||
not just document overflow. Measure the elements, not only the page.
|
||
|
||
### Declined and deferred
|
||
|
||
- **The remaining Q35 labels** — locked architecture; not an implementer's call.
|
||
- **A verification workflow was run and half of it was wasted, which is worth
|
||
recording rather than hiding.** It was launched while the artwork was believed
|
||
unreachable, and briefed accordingly; the premise died four minutes later when
|
||
the assets were found. Its *design* strand — three proposals for coping without
|
||
the artwork — was answered by reality and discarded. Its *geometry* strand did
|
||
not depend on that premise at all, and it is what **reconciled 1.23:1** above,
|
||
proved the zero crossing number, and computed the fused-waist figure. The
|
||
lesson is not "don't delegate" but "scope a brief to what cannot change under
|
||
it": a premise about the environment goes stale, a question about the contents
|
||
of a committed file does not.
|
||
- **`Technology, AI & Data` and the other three practice labels**, raised as
|
||
offering claims with no rows: answered structurally rather than individually —
|
||
subject-matter areas are **not** offerings, so the Offerings table is not the
|
||
rule that governs them. `docs/03`'s framing rule and Q35 are.
|
||
- **`docs/reference/brand-assets.md` reproducing R14** — the auditor was right
|
||
that every measurement derived from a master outside the repo. **Fixed, not
|
||
declined:** the uncropped master is now committed, so the crop is re-derivable
|
||
in-repo, and every figure carries a stamp.
|
||
|
||
---
|
||
|
||
## 2026-08-26 (u) — Build step 1. Zero JavaScript, and both review passes found defects in the first pass's fixes
|
||
|
||
**Who:** Pouya ruled on CTF, Q30, Q31 and the Lighthouse gap, and set the
|
||
direction for step 1. Claude Code implemented under `/build`;
|
||
`adversarial-reviewer` and `claims-auditor` each ran **twice**, and the second
|
||
pass is where most of this entry comes from.
|
||
|
||
### What Pouya decided
|
||
|
||
- **Canadian Tax Foundation membership** added to §4 and to
|
||
`CREDENTIALS.memberships`, `[verified 2026-08-26 — Pouya]`, **for now** — it
|
||
renews yearly, so **R10 was widened** from "OBA section membership" to
|
||
"annually-renewing memberships" covering both.
|
||
- **Not a seventh practice area at launch.** CTF is a credential none of the six
|
||
areas touch and tax-adjacent disputes are ADR territory, but there is no track
|
||
record to point at. Recorded in `docs/01` beside the Indigenous-engagement
|
||
omission, and **R3 widened from one candidate to two** — one month 12–18
|
||
review, two questions.
|
||
- **Q31 CLOSED — Plausible**, decided rather than defaulted. Pouya checked and
|
||
found his own assumption wrong: Fathom is Canadian-owned but stores non-EU
|
||
traffic on US servers, isolating in the EU only for EU visitors; Plausible
|
||
holds everything in the EU. **D15 amended** from "Plausible **or** Fathom" to
|
||
Plausible, with that reasoning and with Fathom recorded as rejected on data
|
||
residency rather than on quality.
|
||
- **Q30 CLOSED — SML Company Ltd is incorporated FEDERALLY, under the CBCA.**
|
||
Two facts were being conflated and one was wrong: `site.ts` carried
|
||
`'SML Company Ltd. · Ontario, Canada'`, which reads as a jurisdiction of
|
||
incorporation and named the wrong one. Jurisdiction of incorporation is
|
||
federal; place of business is Toronto, Ontario; they are different facts.
|
||
**Neither is published** — the footer reads `© <year> SML Company Ltd` and
|
||
stops, on Pouya's direction given twice. No corporation number: none is held
|
||
and none is needed. §4 carries the caution that "federally incorporated" says
|
||
nothing about licensure and nothing about where the practice may operate, and
|
||
must not be read together with the **Licence status — NOT ESTABLISHED** row
|
||
into an implication neither makes.
|
||
- **The Lighthouse gap, ratified and closed as a documented-control problem.**
|
||
Removing `@lhci/cli` was right — seven high-severity advisories for a tool
|
||
that could not run — but it left `docs/04`, `CLAUDE.md` and `/build` Phase 5
|
||
all requiring a check that had silently become impossible. That is Q22's
|
||
defect in a different costume. The unavailability is now stated in **six
|
||
places**, listed in §7, and `adversarial-reviewer` is told **not** to raise the
|
||
absence as a finding. **R11 carries the re-add trigger** for step 7, including
|
||
"check for a patched release; do not assume `0.15.1` is still the ceiling".
|
||
|
||
### What shipped
|
||
|
||
`src/layouts/BaseLayout.astro`, `src/components/{SEO,SiteHeader,SiteFooter,Button,InfinityMark}.astro`,
|
||
`public/fonts/` (six cuts), `public/favicon.{svg,ico}`, `public/apple-touch-icon.png`,
|
||
and a temporary proof sheet at `/type-scale/` that step 2 deletes.
|
||
|
||
**The fonts were never on disk.** `global.css` declared six `@font-face` rules
|
||
pointing at `/fonts/*.woff2` and `public/fonts/` did not exist, so every face had
|
||
been silently falling back to Georgia and the system sans. The design system had
|
||
never once rendered as specified. Six cuts committed, **123,804 bytes** (not the
|
||
136 K `du -sh` reports — that is disk blocks, and §7 is read in a performance
|
||
context), provenance and SIL OFL licences in `docs/reference/fonts-provenance.md`.
|
||
Every URL carries `?v=1` because the deploy script serves `/fonts/*` `immutable`
|
||
for a year and no invalidation reaches a browser cache.
|
||
|
||
**The infinity mark was recoverable, and is not a redrawing.** The deployed site
|
||
serves its own loading-thumbnail SVG labelled `smlMark`; `InfinityMark.astro` is
|
||
that path verbatim, with the source's `translate(60 0)` folded into the
|
||
coordinates. Stroke widths (28/6) and the 0.7 inner opacity are the source's.
|
||
Geometry verified to fit its viewBox with 6 units of margin, so it cannot clip at
|
||
any size. **Q32 opened** — a loading placeholder is not necessarily the canonical
|
||
file, and D7 says the mark carries over *unchanged*.
|
||
|
||
**The proof sheet computes rather than restates.** It reads `tokens.css` at build
|
||
time and runs the WCAG luminance formula over it. All eleven ratios reproduce
|
||
`docs/02`'s measured table exactly — 16.81, 11.75, 12.29, 8.95, 5.47, 3.11, 2.10
|
||
on cream; 16.81, 11.09, 8.00, 3.07 on ink. It cannot drift from the tokens
|
||
because it is derived from them.
|
||
|
||
**Insights is gated, not hardcoded.** `docs/01` keeps the section out of primary
|
||
nav until two pieces are live, so `SiteHeader` reads the collection count at
|
||
build time. It does not render today and appears by itself at step 7.
|
||
|
||
### Decisions taken during implementation
|
||
|
||
- **ZERO JavaScript, not "minimal".** The reveal was an inline
|
||
`IntersectionObserver` in `<head>`. `docs/05` specifies `script-src 'self'`
|
||
with no `unsafe-inline` — so the only script on the site was the one thing the
|
||
site's own CSP would refuse to execute, and a per-build hash drifts from the
|
||
policy pinning it. Replaced with `animation-timeline: view()` behind
|
||
`@supports`. **0 `<script>` tags and 0 `.js` files in `dist/`.** `docs/02`
|
||
§Motion amended: the `IntersectionObserver` route is now ruled out, not merely
|
||
second choice. `docs/05` gained the converse note — inline `style=` attributes
|
||
are now load-bearing, so hashing `style-src` would collapse the infinity mark.
|
||
- **Header sticky from 64rem, not `docs/02`'s "sticky".** Measured: the one-row
|
||
header must hold brand + **seven** nav items + CTA, which it does at 1024px
|
||
with 32px clearance and not below. Below 64rem the nav takes its own row and
|
||
the header is 137px (tablet) / 185px (phone) — more of a small viewport than a
|
||
sticky header is worth. `docs/02` amended with the measured numbers.
|
||
- **"Condenses on scroll" is now a rule and a shadow, not a size change.** A
|
||
`position: sticky` header stays in normal flow, so shrinking its padding
|
||
shortens its layout box at the top of the document and lifts every page below
|
||
it — a scroll-linked layout shift on every page, against the CLS < 0.05 budget.
|
||
- **`--section-y` corrected.** `6vw + 2rem` reaches its own upper bound only at a
|
||
2133px viewport, so the "160px desktop" half of `docs/02` was never delivered
|
||
(measured 108.8px at 1280, 128px at 1600). Now `9vw + 1rem` — 160px at 1600px.
|
||
- **The measure is opt-in.** A global `p { max-inline-size: 68ch }` capped every
|
||
paragraph in every card and footer, forced components to opt back out, and made
|
||
`.prose` a class with no effect. Moved onto `.prose`.
|
||
- **`robots.txt` disallows nothing.** `Disallow` + `noindex` on the same path
|
||
cancel out: a crawler forbidden to fetch a URL never reads the `noindex`. The
|
||
legal pages are footer-linked from every page, so the pair would likely have
|
||
produced bare-URL listings with the suppressing directive unread. `docs/04`
|
||
amended.
|
||
|
||
### What the reviews found — including in each other's fixes
|
||
|
||
**Round 1 — code (5 blocking, 7 should-fix).** All fixed and re-measured:
|
||
the `animation` shorthand silently collapsed by Lightning CSS (dead in every
|
||
production build, alive in dev); a seven-item nav that fit at no width; parent
|
||
styles that never reach a child component's root in Astro; gold text shipped at
|
||
**1.76:1**; 27 touch targets under 44px; revealed content printing blank; a skip
|
||
link landing behind the sticky header; 72px of overflow at 320px masked by
|
||
`body { overflow-x: hidden }`.
|
||
|
||
**Round 1 — claims (FAIL, 8).** The masthead tagline `Mediation · Arbitration ·
|
||
Toronto` — never specified for the header, and unqualified `Arbitration` beneath
|
||
a name reads as a held capability against §4's Q.Arb row. Removed; **Q33 opened**
|
||
for the form the question takes at step 2. A four-stage service timeline and two
|
||
unverified assertions about the previous build, both removed from a page that
|
||
exists to demonstrate CSS.
|
||
|
||
**Round 2 found defects in round 1's fixes — four of them.**
|
||
|
||
1. **The minifier bug was written back into its own fix.** Having just diagnosed
|
||
that `animation:` beside `animation-timeline` gets folded into an invalid
|
||
declaration, the replacement reveal used the same shorthand. Caught only
|
||
because the print test still failed. Both are longhand-only;
|
||
**`/build` Phase 5 now greps `dist` for it** and `CLAUDE.md` carries the rule.
|
||
2. **The claims fixes were silently lost.** The patch applying all four aborted
|
||
on a later assertion *before* writing the file, having already reported four
|
||
successes. The service timeline was still in the source and still in the
|
||
build.
|
||
3. **The colour-alone fix used the banned pairing.** Nav state was given a gold
|
||
underline so colour would not carry meaning alone — gold on cream is 2.10:1,
|
||
below WCAG 1.4.11's 3:1 for a state indicator, so it carried nothing and the
|
||
state reverted to colour alone. Now maroon at 12.29:1, 2px, dotted for section
|
||
and solid for current page.
|
||
4. **`--header-h` was stamped `[measured]` before anything was measured.** It
|
||
said 4.75rem. Actual is **77px** at every sticky width, six items and seven.
|
||
5. Plus: a retracted "470 KB PNG" figure surviving in a file written the same
|
||
day; two "measured" comments giving 34px and 14px for the same measurement;
|
||
`docs/02` amended to a 60rem threshold the code no longer used; flex `order`
|
||
putting focus order out of step with visual order between 640 and 1023px.
|
||
|
||
**Round 2 — claims (FAIL, 10).** The most serious was inside the review
|
||
apparatus: **`.claude/agents/claims-auditor.md` said "Memberships. ADRIC, ADRIO,
|
||
OBA sections **only**"** — contradicting a §4 that had gained CTF that morning.
|
||
It would have flagged a verified membership as unverified and would not have
|
||
noticed CTF being dropped. That file has now hosted a stale claim **twice**, so
|
||
the list was not updated — it was **removed**, replaced by an instruction to read
|
||
the §4 row at audit time. Also fixed: two specs instructing a public phone onto
|
||
pages against a §4 row that records none (Q3, answered four entries ago); a
|
||
`robots.txt` reproduced inline in `docs/04` that had already drifted; Q.Arb
|
||
described as "in progress" where §4 pins "commenced August 2026"; and headline
|
||
option 3 struck as asserting party, counsel *and* neutral.
|
||
|
||
**`ROLE` added to `site.ts`** — there was no constant for *"Director of Firm
|
||
Operations"* or *"active litigation exposure"*, the two highest-risk strings on
|
||
the site, and both were headed for hand-typing at step 3 and in the `Person`
|
||
JSON-LD. `npm run check` then caught a temporal-dead-zone error in that fix.
|
||
|
||
### Declined, with reasons
|
||
|
||
- **The nav and footer naming `Arbitration`, `Med-Arb`, `Energy` and
|
||
`Shareholder`** — raised on both claims passes. Every one is locked
|
||
architecture (D5, §6, `docs/01`), and §4 registers claims about Pouya rather
|
||
than enumerating service lines. Removing them is not an implementer's call.
|
||
**Opened as Q35** so the judgement is visible rather than missed.
|
||
- **Inlining critical CSS.** `docs/04` names it, but the bundle is 22.5 KB
|
||
against a 4 KB `inlineStylesheets: 'auto'` threshold; inlining it into all
|
||
nineteen pages costs more than the one round trip it saves and destroys
|
||
cross-page caching. Revisit at step 11 against real Lighthouse numbers.
|
||
- **Simplifying `PRACTICE_SLUGS` / `PRACTICE_AREAS`.** A fair simplicity finding,
|
||
but it touches the content schema a prior review round hardened, and rewriting
|
||
it as a rider on step 1 is exactly how defects 1 and 2 above happened.
|
||
Deferred to its own change before step 7.
|
||
- **The sitemap 404.** `<link rel="sitemap">` removed as inert (it is not a
|
||
registered link relation and no crawler consumes it); the `robots.txt`
|
||
`Sitemap:` line resolves at step 2. **Step 1 is not deployed** — no deploy
|
||
credential exists (Q22) and deploys are manual.
|
||
- **Second-person copy on the proof sheet.** `docs/03` bars it on counsel-facing
|
||
pages; an internal proof sheet is not one, and the page is deleted at step 2.
|
||
|
||
### Verification — run, not asserted
|
||
|
||
`npm run check` 0/0/0 · `npm run lint` clean · `npm run build` 0 errors ·
|
||
`npm audit` **0 vulnerabilities** · **R11 dependency sweep: 13 of 14 pins at
|
||
registry `latest`**, the only drift being the deliberate `typescript` hold.
|
||
|
||
Measured in headless Chrome across 320/375/640/768/900/1000/1023/1024/1100/1200/1280/1440/1600,
|
||
**with a seventh nav item injected** to test the step-7 state that does not exist yet:
|
||
|
||
- Header **77px, one row, sticky** at every width ≥1024 with six items and seven;
|
||
137px static below; **0 overflow at every width including 320px**
|
||
- **0 tap targets under 44×44** at any width
|
||
- **0 focus-order inversions** (`checkVisibility`-filtered); closed `<details>`
|
||
panels contribute **0** hidden tab stops
|
||
- State indicators **12.29:1**; `--section-y` reaches exactly **160px at 1600px**
|
||
- `scroll-padding-top` computes to **93px** = 77 + 16, matching `--header-h`
|
||
- **0 `<script>` tags, 0 `.js` files**; both scroll-driven animations attach live
|
||
(`header-lift`/`scroll()`, `reveal-in`/`view()`)
|
||
- Printed to PDF: all four revealed cards present (they were absent before the
|
||
print override)
|
||
- **755 words** of body text from `curl` with no JavaScript — the old site
|
||
returns three
|
||
|
||
### Sweeps — the commands, not the claims (R8)
|
||
|
||
```
|
||
$ grep -rE 'animation:[^;}]*(scroll\(\)|view\(\))' dist --include='*.css'
|
||
(no output)
|
||
|
||
$ grep -rn "OBA sections only" . --exclude-dir={node_modules,.git,dist,.astro}
|
||
.claude/agents/claims-auditor.md:58:enumerate "ADRIC, ADRIO, OBA sections only"; the Canadian Tax Foundation was
|
||
(the sole hit is the note recording its removal)
|
||
|
||
$ grep -c '<script' dist/type-scale/index.html -> 0
|
||
$ find dist -name '*.js' | wc -l -> 0
|
||
$ grep -c "Mediation · Arbitration · Toronto" dist/type-scale/index.html -> 0
|
||
```
|
||
|
||
The `470 KB` sweep is the one worth recording as a near-miss: after retracting
|
||
the figure from `docs/02`, `grep -rn "470 KB"` found it **still asserted in
|
||
`src/components/InfinityMark.astro`, a file written the same day**. Without the
|
||
grep this entry would have claimed a completed retraction. Three previous entries
|
||
made exactly that mistake.
|
||
|
||
### Questions
|
||
|
||
**Closed:** Q30 (federal, CBCA), Q31 (Plausible).
|
||
**Opened:** **Q32** (canonical vector for the infinity mark) · **Q33** (how
|
||
arbitration is described in one-line site-wide copy before Q.Arb) · **Q34**
|
||
(whether §2's measurements of the previous build still hold — a re-fetch found
|
||
zero `base64,` occurrences, but the real application is in nine unfetched
|
||
bundles, so this is a question and not a correction; §2 now carries the caveat
|
||
inline, and `CLAUDE.md`, `docs/02` and `adversarial-reviewer.md` all cite it
|
||
where they quote the figure) · **Q35** (may the nav name a service the register
|
||
does not establish) · **Q36** (is co-arbitration work available now — asserted in
|
||
three specs, in no §4 row) · **Q37** (is "Law and engineering" the right label
|
||
under `JD + ML`).
|
||
|
||
**§12:** R3 widened to two candidates, R10 widened to all annually-renewing
|
||
memberships, R11 given the `@lhci/cli` re-add trigger. **R1 remains live and was
|
||
surfaced** — nothing in this change describes Pouya as licensed or as a legal
|
||
professional, and the header tagline that triggered Q33 is verified absent from
|
||
`dist`.
|
||
|
||
### Commit shape
|
||
|
||
Split in two on `adversarial-reviewer`'s own recommendation: instructions that
|
||
narrow a reviewer's scope should not travel in the same commit as the work that
|
||
reviewer is checking. The `.claude/` changes go in their own `chore:` commit so
|
||
the narrowing reads as a decision rather than as a line in a feature diff.
|
||
|
||
---
|
||
|
||
## 2026-08-26 (t) — Astro 5 → 7. The review found a defect in the fix, twice
|
||
|
||
**Who:** Pouya approved the upgrade and set the version-pin rule. Claude Code
|
||
implemented under `/build`; `adversarial-reviewer` and `claims-auditor` both ran
|
||
and both failed the first attempt.
|
||
|
||
**This entry resolves the escalation left open at the end of entry (s).** That
|
||
entry recorded the upgrade as *proposed, not done*; it is done now.
|
||
|
||
### D1 amended — the major is pinned, not inherited
|
||
|
||
Old → new: *"Astro, static output"* → **"Astro, static output, v7.x"**, with the
|
||
reasoning in the decision itself so the next reader knows the version was chosen.
|
||
|
||
Pouya's own account of the original pin, recorded at his instruction: `^5.0.0`
|
||
was **recalled, not checked, and was two majors stale on the day it was
|
||
written.** That is a different failure class from the sweep problem in entries
|
||
(l) through (o) — not a change that failed to propagate, but a fact asserted
|
||
that one command would have settled.
|
||
|
||
Verified with `npm view`, and the staleness was not confined to Astro:
|
||
|
||
| | was pinned | registry `latest` |
|
||
|---|---|---|
|
||
| `astro` | `^5.0.0` | **7.2.7** |
|
||
| `@astrojs/mdx` | `^4.0.0` | **7.0.8** — three majors |
|
||
| `eslint` | `^9.0.0` | **10.9.1**; npm flags 9.x deprecated |
|
||
| `sharp` | `^0.33.0` | 0.35.4 |
|
||
| `@lhci/cli` | `^0.14.0` | 0.15.1 |
|
||
|
||
**The rule is now in `CLAUDE.md`**: a version pin is verified against the
|
||
registry, never recalled. **R11** requires re-checking currency at every phase
|
||
boundary in the build order — ten remain.
|
||
|
||
A caveat the rule needs, learned here: **verified does not mean latest.**
|
||
`typescript` 7.0.2 exists and is unusable — `typescript-eslint` peers `<6.1.0`
|
||
and `@astrojs/check` peers `^5 || ^6`. `@eslint/js` latest is 10.0.1, but on
|
||
ESLint 9 it must track 9.x exactly. The check tells you the number; you still
|
||
have to know why you chose it. Both holds are now recorded in §7 so the next
|
||
agent running R11 does not re-derive them or break the build discovering them.
|
||
|
||
**The rule was then not applied to its own manifest**, which the second review
|
||
caught: `eslint-plugin-astro` was left at `^1.3.0` while §7 asserted a hold at
|
||
1.7.0, and `typescript` at `^5.7.0` against an installed 5.9.3. Both re-pinned.
|
||
Every one of the twelve pins is now verified against `npm view`.
|
||
|
||
### The migration
|
||
|
||
Astro 5 introduced the Content Layer API and `src/content.config.ts`; **Astro 6
|
||
removed the legacy `src/content/config.ts` fallback**. Verified by moving the
|
||
file back and reproducing `LegacyContentConfigError` — an earlier draft of this
|
||
entry attributed the move to Astro 6, which `claims-auditor` caught as a version
|
||
fact recalled rather than checked, *in the change that raised recalling-versions
|
||
to a rule.*
|
||
|
||
`type: 'content'` → `loader: glob(...)`, `z` from `astro/zod`. `schema: ({ image
|
||
}) => …` still works — verified, not assumed.
|
||
|
||
**An empty build proves nothing**, so a throwaway page and article exercised
|
||
`getCollection`, `render(entry)`, `entry.id`, MDX rendering, the `image()`
|
||
helper resolving to a hashed asset, and sitemap emission at `/sitemap-0.xml`
|
||
with no trailing-slash conflict. Then deleted.
|
||
|
||
### `compressHTML` — held at `true`, and the first rationale was wrong
|
||
|
||
Astro 7 changed the default to `'jsx'`. I asserted this would eat spaces in
|
||
prose, measured **MDX**, and found no difference — the premise was unsupported
|
||
as written. Measuring the `.astro` path instead:
|
||
|
||
```
|
||
'jsx': <em>inline</em><strong>pair</strong> ← space silently deleted
|
||
true: <em>inline</em> <strong>pair</strong>
|
||
```
|
||
|
||
Real hazard, wrong file. `adversarial-reviewer` reproduced both outputs
|
||
independently. The comment now names `.astro` templates specifically and records
|
||
that MDX is unaffected, so nobody inherits the original claim. **R12** makes the
|
||
deviation revisitable only with a measurement.
|
||
|
||
### What the review caught — seven defects in the fix itself
|
||
|
||
**Both reviewers, independently:** two source files cited *this entry* before it
|
||
existed. Current Truth had been rewritten in place with no append-only record,
|
||
and `astro.config.mjs` pointed at it as the authority for a measurement. Rules
|
||
1–3 of this file's own constitution, broken in the change that adds a rule about
|
||
not recalling things. Writing this entry is the fix.
|
||
|
||
**`z.coerce.date()` turned a plausible typo into 1970.** Reproduced: unquoted
|
||
`publishDate: 20260801` — valid YAML, the obvious slip for `2026-08-01` — coerces
|
||
from epoch milliseconds to **1970-01-01** with no error, and would ship as
|
||
`datePublished` in the article's JSON-LD and sort the piece last in a
|
||
reverse-chronological index. The reviewer also tested my justification for the
|
||
coercion and found it false: plain `z.date()` accepts unquoted YAML dates fine.
|
||
Replaced with a bounded union — `z.date()` or an ISO-shaped string — which
|
||
accepts both real forms and rejects numbers.
|
||
|
||
**The title bound made the SEO spec unsatisfiable.** `docs/04-seo-spec.md` puts
|
||
50–60 characters on the *rendered* `<title>`, whose pattern is
|
||
`"<headline> · Pouya Lajevardi"`. The suffix is 18 characters, so applying 50–60
|
||
to the headline guaranteed a rendered title of **68–78** — over the spec's own
|
||
ceiling on every article — while `.min(50)` hard-failed the build on a good short
|
||
headline (`"What Med-Arb Actually Is"`). The schema now enforces the *rendered*
|
||
length, adds an optional `seoTitle` override, and reports the computed title in
|
||
the failure message. `docs/01-architecture.md` updated to match.
|
||
|
||
**An article could ship an image with no alt text** — `image` and `imageAlt` were
|
||
independently optional, and the schema is the only gate that exists before the
|
||
`/insights/` route is written. Now coupled.
|
||
|
||
**Two comments asserted controls that did not exist**: "every piece must link to
|
||
a practice-area page" (`.min(1)` checks a *declaration*, not a link) and "an
|
||
article with `draft:false` and `reviewedByPouya:false` is a bug" (nothing
|
||
enforced it). The second is now true — a refinement fails the build. All four
|
||
invariants were then tested, each with a failing and a passing case; each fires.
|
||
|
||
**The schema diverged from two specs** — `docs/01` and `docs/02` both specify
|
||
`topics[]` plural and `readingTime`; the collection had singular `topic` and no
|
||
reading time. Pre-existing, carried through a wholesale rewrite without notice.
|
||
Fixed to the specs.
|
||
|
||
**`eslint.config.js` imported two undeclared packages**, one resolving by
|
||
hoisting accident: `globals` was 14.0.0 at the root against 16.5.0 nested under
|
||
the Astro plugin, so which major linting used depended on npm's hoisting.
|
||
|
||
### The second review pass found six more, four of them in the first round's fixes
|
||
|
||
The loop requires re-review after material fixes, and this is why.
|
||
|
||
**`frontmatterDate` accepted impossible dates** — the fix for the 1970 defect
|
||
introduced its own. The regex was unanchored at the end and nothing checked the
|
||
parsed result, so `2026-13-45` and `2026-08-01 nonsense` both **passed**, each
|
||
producing an `Invalid Date` bound for `datePublished` in the article's JSON-LD;
|
||
and `2026-02-30` silently rolled over to **2026-03-02** — a wrong date shipped
|
||
with no error, which is worse than a failed build. The comment claimed it
|
||
accepted "both real forms and nothing else." Now anchored, date-only, parsed as
|
||
UTC and **round-tripped** so the day that comes back must be the day written.
|
||
A time component is rejected rather than guessed at: quoted
|
||
`2026-08-01T10:00:00` parses as local time while the unquoted YAML form parses
|
||
as UTC, so the same frontmatter would mean different instants on a laptop and on
|
||
a CI runner.
|
||
|
||
**The title rule rejected all five planned launch articles.** The arithmetic was
|
||
right and the rule was still wrong. Every headline in `docs/03-content-spec.md`'s
|
||
launch slate is 50–67 characters; with the ` · Pouya Lajevardi` suffix they
|
||
render at 68–85 and **5 of 5 fail**, making `seoTitle` mandatory on every article
|
||
— a second title field to hand-keep in sync forever, on the highest-volume
|
||
content type. Two specs contradicted each other and the schema enforced one.
|
||
Resolved by making articles the documented exception: **an article's headline is
|
||
its `<title>`, with no suffix.** Under that rule 4 of 5 launch headlines pass and
|
||
`seoTitle` is a genuine exception. `docs/04-seo-spec.md` — which owns the title
|
||
rule and had not been swept — now states it.
|
||
|
||
**`PRACTICE_SLUGS` and `PRACTICE_AREAS` could drift silently.** Splitting one
|
||
derived source into two literals bought back the literal types but lost the
|
||
guarantee: deleting an area while leaving its slug declared passed `astro check`
|
||
cleanly, so an article could name a practice area with no page, no nav child and
|
||
no chip. My first completeness check was written as a conditional type and
|
||
**did not fire** — verified by deleting a row and getting 0 errors. Replaced with
|
||
an `AssertNever` constraint that does: a missing area now fails with
|
||
`ts(2344)`, and a typo'd slug fails with `ts(2820)` plus a "did you mean".
|
||
Zero runtime cost.
|
||
|
||
**Three narrower schema gaps**, each reproduced: `imageAlt: " "` passed, so an
|
||
image could ship with a whitespace-only accessible name — the exact thing the
|
||
coupling check exists to prevent; duplicate `topics` and `practiceAreas` passed
|
||
and would render duplicate pills; and `seoTitle` was bounded *and* re-checked,
|
||
so one mistake produced two errors. Trimmed, de-duplicated, and the field bound
|
||
dropped so the refinement is the single check.
|
||
|
||
**`scripts/deploy-local.sh` claimed to do "EXACTLY" what CI does.** It did not:
|
||
the workflow guards six values, the script guarded four, and the workflow runs
|
||
`npm run check` before building while the script ran neither check nor `npm ci`.
|
||
A local deploy — currently the **only** way this site ships, since Q22 and Q23
|
||
are open — was skipping the type and template gate. Guards brought to parity,
|
||
`npm run check` added, and the claim rewritten to name the two remaining
|
||
differences instead of denying them.
|
||
|
||
**Sweep misses:** `README.md` stated an engines floor of `>=22.12.0` after
|
||
`package.json` had moved to `>=22.13.0` for ESLint 10 — a duplicated version fact
|
||
of exactly the kind §7 exists to prevent, now replaced with a pointer.
|
||
`package-lock.json`'s root `engines` still carried the pre-bump value because the
|
||
bump was made without reinstalling. `engines.node` was described as "the
|
||
intersection of every dependency's floor" and was not one — `>=22.13.0` admits
|
||
Node 23.x, which ESLint 10 excludes; it now reads `^22.13.0 || >=24`.
|
||
`eslint.config.js` still called itself an "ESLint 9 flat config", and
|
||
`.gitea/workflows/deploy.yml` still carried the Gitea version as `[assumed]`
|
||
after Q23 verified it as 1.27.2.
|
||
|
||
**Three claims in `src/data/site.ts` bound for public pages**, all pre-existing
|
||
and all found by `claims-auditor`: `entity: 'SML Company Ltd. · Ontario, Canada'`
|
||
asserted a jurisdiction of incorporation §4 does not verify (**Q30**);
|
||
`provider: 'plausible'` was a guessed value where D15 records the choice as
|
||
undecided, in a file whose own header says not to guess one to make the build
|
||
pass (**Q31**); and `NO_RETAINER_NOTICE` was missing the third element
|
||
`docs/01-architecture.md` requires — that submitting the form does not itself
|
||
create a conflict check. The notice is fixed; the other two are nulled with
|
||
`TODO(pouya)` and numbered.
|
||
|
||
**One finding declined.** `claims-auditor` reported that no build order exists in
|
||
the repository and that R11's "ten more boundaries" was therefore untraceable. It
|
||
does exist — `docs/01-architecture.md` §Build order, eleven numbered steps. The
|
||
audit grepped lowercase `"build order"` and missed the capitalised heading. R11
|
||
now carries the file and section so the next reader does not repeat the search.
|
||
|
||
### Declined, with reasons
|
||
|
||
**Accessibility linting is ON, and I was wrong about it twice.**
|
||
`adversarial-reviewer` recommended `eslint-plugin-astro@3.1.0` for the
|
||
`eslint-plugin-jsx-a11y` peer. I tested that upgrade, hit ERESOLVE (v3 requires
|
||
`eslint >=10` *and* peers `jsx-a11y >=6.10.2`, whose latest peers `eslint ^3..^9`),
|
||
and concluded it was "not installable" — recording in §7 that
|
||
**"there is no automated accessibility linting"**.
|
||
|
||
Wrong the first time: **the already-installed `eslint-plugin-astro@1.7.0` ships
|
||
36 `jsx-a11y/*` rules and a `flat/jsx-a11y-recommended` config.** I had tested a
|
||
different upgrade path and generalised its failure to the capability. The stale
|
||
peer range is a *declaration*, not a runtime incompatibility.
|
||
|
||
Wrong the second time: having added a one-line `overrides` entry to fix that
|
||
declaration, I retested v3.1.0 — **and it installs cleanly.** The ERESOLVE was
|
||
never about v3; it was about the missing `overrides`. So the plugin is now on the
|
||
current major, not held two behind, and there is no stale pin left in the
|
||
manifest except `typescript`, whose hold is forced by peer ranges.
|
||
|
||
Verified by execution at each step — rules fired on a deliberately inaccessible
|
||
`.astro` file: `html-has-lang`, `alt-text`, `heading-has-content`,
|
||
`click-events-have-key-events`, `no-static-element-interactions`,
|
||
`no-noninteractive-tabindex`, `tabindex-no-positive`. Those are the checks
|
||
`docs/02-design-system.md` §Accessibility floor names.
|
||
|
||
One cost, recorded rather than discovered later: v3.1.0 declares
|
||
`node ^22.22.3 || ^24.16.0 || >=26.3.0`, which **excludes Node 25.6.0** — so
|
||
`npm install` prints EBADENGINE on Pouya's machine. Dev-time only; `nvm use`
|
||
clears it, and `.nvmrc` already says 22.
|
||
|
||
This mattered more than the ERESOLVE did. **§7 is the single source of
|
||
operational truth, and it carried a false capability claim on the eve of the
|
||
step that writes every landmark, heading and focus state**, under a CLAUDE.md
|
||
rule that accessibility is a build requirement rather than a polish pass.
|
||
|
||
**`@lhci/cli` advisories carried, not fixed.** All ten remaining findings trace
|
||
to it alone; 0.15.1 *is* `latest`, so there is no clean upgrade, and
|
||
`npm audit fix --force` installs `@lhci/cli@0.1.0` — a fourteen-minor downgrade,
|
||
which is not a fix. Dev-only, never on the CloudFront origin.
|
||
|
||
**Two `Consider` items taken rather than deferred**, both in files already being
|
||
edited: `image.service` was dead configuration (it set Astro's own default) under
|
||
a comment describing a convention it did not enforce — deleted, convention stays
|
||
in `CLAUDE.md`; and `sitemap({ lastmod: new Date() })` stamped every URL with the
|
||
build time, telling crawlers all 17 pages changed whenever one did, which spends
|
||
the signal `docs/04-seo-spec.md` wants. Removed, with step 7 named as the place
|
||
to reinstate it per-entry from `updatedDate`.
|
||
|
||
**Two `Consider` items declined:** the six extraneous `@img`/`@emnapi` packages
|
||
are cosmetic and `npm ci --dry-run` is clean; and no `.npmrc` with
|
||
`engine-strict` was added — the engines floor is a declaration, and making it
|
||
fatal is a decision with its own blast radius.
|
||
|
||
### `npm audit` — the actual result, and it is now zero
|
||
|
||
```
|
||
after the upgrade: 10 vulnerabilities (2 low, 1 moderate, 7 high)
|
||
npm audit --omit=dev: found 0 vulnerabilities
|
||
after removing @lhci/cli: found 0 vulnerabilities
|
||
```
|
||
|
||
**Every Astro advisory is cleared** — zero findings against `astro`,
|
||
`@astrojs/mdx`, `@astrojs/sitemap` or `sharp`. `adversarial-reviewer` confirmed
|
||
the rationale independently by installing `astro@^5.0.0` in a scratch directory
|
||
and reproducing **8 high-severity advisories, 6 of them distinct XSS**.
|
||
|
||
`npm ls` traced all 10 residual findings to `@lhci/cli` alone. It was first
|
||
carried as acceptable dev-only risk; on the second pass that was reconsidered
|
||
and it is now **removed**. The reasoning: 0.15.1 *is* `latest`, so there was no
|
||
clean upgrade; `npm audit fix --force` would install `@lhci/cli@0.1.0`, a
|
||
fourteen-minor downgrade; and the tool **cannot run at all today** — no pages,
|
||
no `lighthouserc`. Carrying seven high-severity advisories for an unusable tool
|
||
is not a trade worth making when deferring it to step 7 costs nothing. Recorded
|
||
in §7; R11 forces a fresh pin when it returns.
|
||
|
||
**A discrepancy with entry (s), stated rather than quietly dropped.** Entry (s)
|
||
recorded 16 vulnerabilities and attributed the high-severity set to Astro ≤
|
||
7.0.9. After the upgrade the high count was still 7, all from `@lhci/cli` — so
|
||
(s)'s attribution cannot have been right as written. (s) is append-only and
|
||
stands; this is the correction. What is verifiable now is the audit output
|
||
above.
|
||
|
||
### Verification
|
||
|
||
Run, not asserted: `npm run check` (0 errors, 0 warnings, **0 hints** — three
|
||
`ZodIssueCode is deprecated` hints appeared mid-change and were fixed to the
|
||
string literal), `npm run build`, `npm run lint` (ESLint clean, Prettier clean).
|
||
`npm audit` and `npm audit --omit=dev` as above. `npm install --dry-run` for both
|
||
candidate lint upgrades. Each of the four schema invariants exercised with a
|
||
failing and a passing article. A deliberately broken `.astro` file linted to
|
||
confirm the plugin is live under ESLint 10. `node -v` → v25.6.0.
|
||
|
||
Not run: Lighthouse (removed — see above), the no-JavaScript render check (no
|
||
pages), link resolution (no pages). Those belong to build step 1
|
||
(`docs/01-architecture.md` §Build order), which entry (s) began and which
|
||
continues after this.
|
||
|
||
**Still open:** Q23 (runner registration — needs the second administrator), R6.
|
||
**Standing reminders surfaced at the start of this build:** R1 (licensure — the
|
||
layout about to be written is what carries it), R9 (the SES alarms still notify
|
||
nobody until the `ses-alerts` subscription is confirmed), R6, R10.
|
||
|
||
---
|
||
|
||
## 2026-08-26 (s) — Q22/Q23/Q27/Q28 answered; toolchain installed; build step 1 begun
|
||
|
||
**Who:** Pouya answered four questions mid-session and corrected one earlier
|
||
instruction. Claude Code implemented and started build step 1.
|
||
|
||
### Q22 — ANSWERED, and the answer is that it does not exist
|
||
|
||
`aws iam get-user --user-name adr-sml-deploy` returns **`NoSuchEntity`**. §7 now
|
||
carries **Deploy credential — NOT PROVISIONED**, and it is a **to-do** rather
|
||
than a question: the creation commands are with Pouya. Swept by command; no file
|
||
describes the credential as existing.
|
||
|
||
**Pouya has been authenticating as `user/pouya`** — the broadly-permissioned
|
||
personal user the Q10 inventory captured. Recorded in §7 as interim, and in §10
|
||
as a **High** risk: fine at an interactive keyboard, never as a CI credential.
|
||
`scripts/deploy-local.sh` **refuses to run** if `sts get-caller-identity` returns
|
||
that ARN, so the rule is enforced rather than merely written down.
|
||
|
||
### Q23 — correction: the version is verified, and the blocker is a person
|
||
|
||
**Old → new:** entry (r) recorded the Gitea version `[assumed]` on Pouya's
|
||
instruction. It is now **1.27.2** at git.larsnolden.com
|
||
`[verified 2026-08-26 — /api/v1/version]`, comfortably above the ~1.21 floor for
|
||
the `vars` context. The first-step guard is therefore belt-and-braces rather than
|
||
load-bearing — which is the right outcome: it was built so the answer would not
|
||
matter, and now it does not.
|
||
|
||
**What remains is not a fact to look up.** The instance is **jointly
|
||
administered**, so enabling Actions in `app.ini` and registering an `act_runner`
|
||
both depend on a second administrator. Q23 is rewritten to say so.
|
||
|
||
**So the local path is documented, not treated as a workaround.**
|
||
`npm run deploy` → `scripts/deploy-local.sh` (new) performs *exactly* what the
|
||
workflow performs: same guard, same three sync passes in the same order with the
|
||
same cache headers, same invalidation. At this scale the pipeline changes only
|
||
**how a deploy is triggered**, not what it does. `docs/06` leads with it, and
|
||
both files say the script and the workflow are one artefact in two places.
|
||
|
||
### §10 — a new risk that changes what the IAM policy is for
|
||
|
||
The deploy secret will live in a repository on **jointly-administered
|
||
infrastructure**, where an instance admin can generally reach repo secrets or
|
||
register a runner that receives them. That is inherent to how Actions runners are
|
||
fed credentials, not a flaw in this setup, and it does not change the plan.
|
||
|
||
It changes the **reading** of the scoped policy. Four actions, one bucket, one
|
||
distribution is no longer hygiene — it is the actual control standing between a
|
||
shared Gitea instance and an AWS account holding another business's
|
||
client-database backups. §10 now says so, and says that any request to widen it
|
||
is a security decision rather than a convenience one.
|
||
|
||
### Q27 and Q28 — answered, and both are facts with obligations attached
|
||
|
||
**Q27 — two business days.** In `src/data/site.ts` as `responseTime`, with a
|
||
derived `responseTimeShort` so the confirmation email cannot drift from the page.
|
||
Added to §4 Verified as a **public commitment** that must read identically on
|
||
`/contact/`, in the inquirer email, and in any bio. `docs/05` says to render it
|
||
from `SITE`, never retype it. Swept for the superseded "one business day": no
|
||
occurrences.
|
||
|
||
**Q28 — OBA Construction & Infrastructure, ADR, and Civil Litigation**
|
||
`[verified 2026-08-26 — Pouya]`, **for now**. §4's row and `site.ts` both carry
|
||
the "for now". Section membership renews yearly, so this is a fact with a shelf
|
||
life — **R10** added, with OCNI as the precedent: §4 already records it as
|
||
lapsed and not publishable, which is exactly this failure arriving a year late.
|
||
|
||
### Build step 1 — started
|
||
|
||
**Dependencies installed; `package-lock.json` exists.** That alone closes a
|
||
blocker documented since entry (m): `npm ci` had no lockfile, so the CI pipeline
|
||
could not get past its first step.
|
||
|
||
**`npm run check` and `npm run build` both pass** — 0 errors, 0 warnings. Worth
|
||
recording because entry (m) F6 asserted both would *fail* on an empty
|
||
`src/pages/`. `adversarial-reviewer` doubted that and was right: `astro build`
|
||
emits zero pages and exits 0. **Correcting it here rather than editing (m).**
|
||
|
||
**ESLint and Prettier are now wired**, closing the "not yet wired" rows:
|
||
|
||
- `eslint.config.js` — flat config, `js.configs.recommended` +
|
||
`typescript-eslint` + `eslint-plugin-astro`. **`typescript-eslint` added as a
|
||
devDependency** because `.astro` frontmatter *is* TypeScript and the plugin
|
||
cannot parse a component without it. Deliberately not type-aware: `astro check`
|
||
already type-checks, and running both would be slower and would disagree at the
|
||
edges.
|
||
- `.prettierrc.json` — 80 columns, single quotes, `prettier-plugin-astro`.
|
||
- **`.prettierignore` excludes `*.md` and `src/styles/tokens.css`, deliberately.**
|
||
Prettier's reformat of `AGENTS.md` alone is an **892-line diff** with no reading
|
||
benefit, and it collapses the aligned comment column in `tokens.css` that lets
|
||
the measured contrast ratios be scanned down the page — the one thing that file
|
||
exists for. Both exclusions carry their reason in the file.
|
||
|
||
`npm run lint` now passes clean. `npm run lighthouse` remains unwired, and now
|
||
honestly so: there are no pages to measure.
|
||
|
||
**`npm audit` reports 16 vulnerabilities (7 high) — not fixed, flagged.** The
|
||
high-severity set is Astro ≤ 7.0.9 (XSS via `define:vars`, spread attribute
|
||
names, `transition:*` values, slot names; SSRF in a prerendered error page) plus
|
||
transitive `esbuild`/`sharp`, and a `cookie` advisory reached only through
|
||
`@lhci/cli`. `npm audit fix --force` wants **Astro 7.2.7, a major upgrade**, and
|
||
`@lhci/cli@0.1.0`, a catastrophic downgrade. Most of the Astro advisories need
|
||
authoring patterns this project does not use (no server islands, no
|
||
`define:vars`, no view transitions, static output, no spread props yet). **This
|
||
needs a deliberate decision, not an automated fix** — see the escalation below.
|
||
|
||
### Escalated
|
||
|
||
**Astro major upgrade.** The project pins `astro@^5.0.0`; the advisories are
|
||
fixed in 7.x. Doing it now, before any pages exist, is far cheaper than doing it
|
||
after — there is nothing to migrate. Doing it later means shipping on a
|
||
known-vulnerable major. This is a D-series decision (D1 names Astro but not a
|
||
version), so it is yours.
|
||
|
||
### Verification
|
||
|
||
`npm run check` — 0 errors, 0 warnings, 5 files. `npm run build` — completes,
|
||
0 pages, as expected. `npm run lint` — ESLint clean, Prettier clean.
|
||
`bash -n scripts/deploy-local.sh` — syntax OK. `node --check astro.config.mjs` —
|
||
OK. `package.json` re-parsed as JSON after editing. Sweeps run as commands with
|
||
output read: `adr-sml-deploy` (no file claims it exists), `one business day` (no
|
||
occurrences), operational identifiers in `docs/*.md` (no matches).
|
||
|
||
**One error of mine, caught by my own sweep and recorded rather than quietly
|
||
fixed:** the three new §7 rows initially landed in the **§3 decisions table**,
|
||
overwriting D15's label, because the anchor I matched on (`| Analytics |`)
|
||
appears in both sections. The `adr-sml-deploy` sweep surfaced it. §3 is restored
|
||
— `git diff` over the decisions table is empty — and the rows are in §7. An
|
||
anchor that is not unique is not an anchor.
|
||
|
||
**Closed:** Q22, Q27, Q28, and the version half of Q23. **Still open:** Q23
|
||
(runner registration — needs the second administrator), R6 (parked). **Added:**
|
||
R9 (SES subscription pending), R10 (OBA renewal).
|
||
|
||
---
|
||
|
||
## 2026-08-26 (r) — Q19 closed; SES monitoring recorded; §7 made the single source of operational truth
|
||
|
||
**Who:** Pouya closed Q19, supplied the monitoring configuration, ruled on Q29,
|
||
and made the structural call below. Claude Code implemented.
|
||
|
||
### Q19 — CLOSED. Nothing now blocks `/contact/`
|
||
|
||
**Production access granted** in `ca-central-1`, confirmed by AWS in writing,
|
||
effective immediately. §7's SES account row and §9's Q19 both record it; §10's
|
||
**High** risk row for the sandbox is struck as resolved.
|
||
|
||
The per-region trap is kept in §7 as a **standing caution rather than an open
|
||
task** — it was avoided, and it applies again to any future SES request. Deleting
|
||
the row would delete the lesson.
|
||
|
||
### Monitoring exists, and one part of it does not work yet
|
||
|
||
Recorded in §7 (the facts) and `docs/05-backend-spec.md` (why it matters):
|
||
|
||
- **SNS topic `ses-alerts`**, `ca-central-1`. The email subscription to
|
||
`info@smlcompany.ca` is **PENDING CONFIRMATION**, stamped that way deliberately.
|
||
An unconfirmed SNS subscription **drops every message**, so as things stand the
|
||
alarms below fire into nothing. That is now a cutover checklist item in its own
|
||
right, checked with `sns list-subscriptions-by-topic` rather than assumed.
|
||
- **`SES-BounceRate-High`** (≥ `0.03`) and **`SES-ComplaintRate-High`**
|
||
(≥ `0.001`), both `ca-central-1`, `treat-missing-data: notBreaching`.
|
||
- **Bounce and complaint handling is SES email feedback forwarding** — the
|
||
default — **not an SNS feedback topic**, deliberately. Under 100 messages a
|
||
month there is nothing to consume a programmatic feed, and an unused topic is
|
||
one more thing to keep correct. Revisit when code needs to *act* on a bounce:
|
||
suppression lists, retry logic, marking a record undeliverable.
|
||
|
||
`docs/05` records why these are a real control rather than a formality: **SES
|
||
suspends sending above roughly a 5% bounce rate, and at this volume five bounces
|
||
crosses it.** An intake form is exactly where mistyped addresses arrive. The
|
||
alarms sit well below that line so there is room to react.
|
||
|
||
### The structural fix — §7 is the single source of truth for operational facts
|
||
|
||
**Old → new.** Specs in `docs/` carried their own copies of resource IDs,
|
||
regions, DNS records, and service state. They now **cite** §7 instead.
|
||
|
||
The reasoning is entry (q)'s DKIM inversion, generalised: the same operational
|
||
fact lived in §7 and in `docs/05`, a correction reached one of them, and the
|
||
stale copy ended up instructing an operator to delete the three records that
|
||
authenticate outbound mail — under the heading "Never delete". Same class as the
|
||
D3 amendment surviving three sweeps. **A duplicated fact is a fact that will
|
||
eventually be wrong in one place, and the copy that goes stale is the one nobody
|
||
re-reads.**
|
||
|
||
The rule is now in `CLAUDE.md` under Conventions, with that incident as its
|
||
stated reason so it is not softened later by someone who does not know the cost.
|
||
|
||
**Swept.** `docs/05` no longer restates the DKIM token sets, the DNS records, the
|
||
MX, the region, or the table name — it cites §7 and keeps only the two facts it
|
||
*depends* on, stated as dependencies. `docs/06` no longer restates the region,
|
||
bucket, distribution ID, intake endpoint, or account ID; its variable table now
|
||
points at §7 rows, and the IAM substitutions say explicitly that they are not
|
||
repeated and why. Verified by command:
|
||
|
||
```
|
||
grep -rn "ca-central-1\|adr-smlcompany-site\|E1OK7G98KNKUTA\|4tl0m5igkj\|327082975128\|adr-intake-submissions\|d26v23dhgsp2ta\|jkddzztszm" docs/*.md
|
||
```
|
||
|
||
Output read: **no matches.** Every operational identifier in `docs/` is now a
|
||
reference.
|
||
|
||
### Q29 — the guard is widened on both counts
|
||
|
||
Both gaps `adversarial-reviewer` found are closed:
|
||
|
||
- **`AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY` are guarded.** By Q22 nobody
|
||
has confirmed the IAM user or its key exists, so an unset key is the single
|
||
likeliest first-run failure — excluding it defeated the guard's stated purpose.
|
||
**Only emptiness is tested and no value is ever echoed**, so nothing can leak
|
||
into a run log.
|
||
- **`INTAKE_ENDPOINT` promoted to job-level `env:` and guarded.** An empty one
|
||
does not fail a build; it **ships a live contact form posting to nothing**. A
|
||
silent production defect is worse than a failed build.
|
||
|
||
The build step still reads `${{ vars.INTAKE_ENDPOINT }}` rather than the `env`
|
||
context — depending on Gitea's expression-context support is the exact thing the
|
||
guard exists not to do. Coverage checked against every `vars.*` and `secrets.*`
|
||
the workflow consumes: all guarded except `BOOKING_URL`, which is empty by
|
||
decision (R6).
|
||
|
||
### Also done
|
||
|
||
**`docs/06`: the account ID is out of the backup-bucket callout**, pointing at
|
||
§10 instead — the same removal entry (m) made in `README.md`. Operational
|
||
usefulness does not outweigh pairing a live account number with a statement about
|
||
what the account holds, in a file that gets pasted around. The billing check now
|
||
derives the account from `sts get-caller-identity` rather than hard-coding it.
|
||
|
||
**`astro.config.mjs`: `prefetch` removed entirely** — recorded here as a decision,
|
||
not a silent deletion. *Any* prefetch setting ships Astro's prefetch script to
|
||
every page, against CLAUDE.md's "default to zero JS", for a marginal gain on a
|
||
small static site already served from CloudFront. **Revisit only against real
|
||
Lighthouse numbers**, once pages exist to measure. Entry (q) had set it to
|
||
`hover`; that was still JS on every page.
|
||
|
||
**Gitea version stays `[assumed]`** at Pouya's direction — he is running the
|
||
check. The guard is designed not to need the answer.
|
||
|
||
### Verification
|
||
|
||
The widened guard's `run:` block was **executed** under `sh -e` across four input
|
||
states — all set, all empty, secret empty, intake empty. Exit 0 only when
|
||
everything is present; exit 1 naming exactly the missing items otherwise; no
|
||
value printed in any case. `node --check astro.config.mjs` passes. The
|
||
duplication sweep was run as the `grep` above and its output read — no matches.
|
||
|
||
`npm run lint`, `check` and `build` still **cannot run**: `node_modules` is
|
||
absent and `npm ci` needs a lockfile. Installing dependencies is the first
|
||
concrete task of build step 1.
|
||
|
||
**Closed:** Q19 (and with it the last blocker on `/contact/`). **Still open:**
|
||
Q22 (deploy credential), Q23 (runner registration), Q27, Q28, R6 (parked).
|
||
**Q29 closed by implementation.**
|
||
|
||
---
|
||
|
||
## 2026-08-26 (q) — Guard built; and the audit found an inverted DKIM table that would have broken production mail
|
||
|
||
**Who:** Pouya ruled on entry (o)'s escalations, ratified R7, promoted R8, and
|
||
reversed his own F5. Claude Code implemented, ran `claims-auditor` and
|
||
`adversarial-reviewer` in parallel, and resolved 31 + 17 findings.
|
||
|
||
### The six rulings, implemented
|
||
|
||
1. **Q23 hardened, not checked.** `.gitea/workflows/deploy.yml` now runs a guard
|
||
as `steps[0]` — before checkout, before `npm ci`, before any AWS call — that
|
||
fails the run naming any of `AWS_REGION`, `S3_BUCKET`,
|
||
`CLOUDFRONT_DISTRIBUTION_ID` that is empty. It tests the env names
|
||
(`AWS_DEFAULT_REGION`) and reports the **Gitea variable** names, which is the
|
||
mapping most likely to be got wrong. `adversarial-reviewer` executed the
|
||
extracted block under `bash -e`, `sh -e`, and `bash -euo pipefail` across
|
||
all-unset / all-set / one-empty / whitespace-only and confirmed it fails
|
||
closed and is POSIX-clean.
|
||
2. **R7(3) dropped** — the `aws s3 ls` pre-flight is out; the guard supersedes it.
|
||
3. **R7(1) ratified** — the cache table stays matched to the pipeline.
|
||
4. **R7(2) reasoning corrected.** Old → new: "the intended cover is an S3
|
||
lifecycle rule" → **no lifecycle rule exists and is not the cover**; the cover
|
||
is that `aws s3 sync` only goes multipart above 8 MB. Corrected once more
|
||
after audit: the figure now measures **what is uploaded**, with
|
||
`src/assets/pouya-lajevardi.jpg` at 357,627 bytes `[verified — stat]` as the
|
||
largest source asset and an instruction to re-measure `./dist` after the first
|
||
build. The old wording measured the repository, which is not what syncs.
|
||
5. **R8 promoted to a rule** in `CLAUDE.md`, `/build` Phase 6, `/wrap` step 3.
|
||
6. **R1 put in the conditional** — there is no site; `src/pages/` is empty.
|
||
|
||
### The finding that mattered most was nowhere near the diff
|
||
|
||
**`docs/05-backend-spec.md` had the two SES DKIM sets exactly inverted.** It
|
||
labelled `3zsn…` / `jejgp…` / `xpiwy…` "**Live.** Matches SES exactly. Never
|
||
delete", and `f5pu…` / `jdue…` / `kznn…` "Orphans from an earlier verification.
|
||
Inert." §7 records the opposite, `[verified 2026-08-26 — DNS]`: the `f5pu` set is
|
||
the one that **resolves** and backs the healthy `ca-central-1` identity; the
|
||
`3zsn` set is NXDOMAIN and belongs to a stray `us-east-1` identity.
|
||
|
||
Entry (j) corrected this. **The correction reached §7 and never reached
|
||
`docs/05`.** An operator tidying DNS from that table deletes the three CNAMEs
|
||
that make SES DKIM work — and since SES has no custom MAIL FROM, DKIM is the
|
||
*only* thing satisfying DMARC. Outcome: intake mail from `ca-central-1` starts
|
||
failing authentication, silently, and the table said "Never delete" over the
|
||
wrong three records. Both rows rewritten from §7. The "six CNAMEs" claim below
|
||
them now says three, which is how many answer.
|
||
|
||
### Current Truth was stale in three more places
|
||
|
||
**§7 SPF and DMARC still read "ABSENT"** `[verified 2026-08-26]`, and §10 still
|
||
carried a live **High** risk row for it — while Q20, in the same file, records
|
||
both records added and independently verified the same day. Rule 2 requires
|
||
Current Truth updated in place; it was not. Both §7 rows now record the live
|
||
values; the §10 risk row is struck as **RESOLVED**, with the residual
|
||
`p=none` → `quarantine` tightening described as monitoring rather than risk.
|
||
`docs/05` opened with "**it is not in place**" and a table headed "Add both of
|
||
these" for records that already exist — rewritten, with the superseded state kept
|
||
visible as a caution.
|
||
|
||
**§9 carried Q24, Q25 and Q26 twice each, struck and open, with opposite
|
||
verdicts.** The live Q25 still asserted §4's boutique-naming permission stands —
|
||
against D16 — after entry (p) had struck it. This is the duplicate-question
|
||
defect entry (o) fixed for Q22, reintroduced three times in one session: entry
|
||
(p) added struck rows rather than striking the existing ones. The three
|
||
superseded open rows are deleted.
|
||
|
||
### The guide added in entry (p) was a live procedure for the architecture being replaced
|
||
|
||
`docs/reference/AWS-Hosting-Guide.md` was added **untracked** — so Q24's answer
|
||
("copied into `docs/reference/`") was true of one working tree and false of the
|
||
repository — with no reference-only marker, in fully executable imperative voice.
|
||
Following it creates an IAM user with `AdministratorAccess` in account
|
||
`327082975128`, rebuilds the site through the standalone-HTML pipeline D1 and D3
|
||
replace, and wires SES to `adr@` / `intake@smlcompany.ca` against D18's
|
||
`info@`. It is now `git add`ed and carries a **do-not-execute** banner tabulating
|
||
seven contradictions with Current Truth, each resolved in Current Truth's favour.
|
||
|
||
**It also called Pouya a lawyer** — "**Audience:** You (a lawyer, not a
|
||
sysadmin)" — and proposed public copy reading "does not create a lawyer-client
|
||
relationship", which is what `NO_RETAINER_NOTICE` in `src/data/site.ts` was
|
||
written to avoid. Both corrected.
|
||
|
||
**The R8 sweep command recorded in entry (o) could not have caught either.**
|
||
`grep -rn -i "licensed\|legal professional"` does not match "lawyer". The rule
|
||
promoted this session is right; the pattern it was demonstrated with was
|
||
incomplete. The corrected sweep is:
|
||
|
||
```
|
||
grep -rn -iE "\blawyer\b|licensed|legal professional|litigator" \
|
||
--include="*.md" --include="*.ts" --include="*.astro" .
|
||
```
|
||
|
||
Run, output read. Every surviving hit is rule text, Change Log history, or
|
||
"lawyer" referring to the *reader* or a third party (`docs/03:20`, `docs/03:161`,
|
||
`docs/01:291`, `docs/08:111`) — none describes Pouya.
|
||
|
||
### Copy defects one step from shipped pages
|
||
|
||
- **"a working litigator"** — `AGENTS.md` §1's positioning sentence and
|
||
`docs/03-content-spec.md:71`, the line designated for the hero, the About page
|
||
and the PDF bio. Not in §4; in Ontario it asserts conducting litigation, which
|
||
§4 Forbidden bars. §1's own line asserted "each element is verified"; it was
|
||
not. Both now read "close to live litigation". §1's correction is annotated in
|
||
place rather than silently rewritten.
|
||
- **"an active litigation practice"** — `docs/03:118`, `docs/01:211`,
|
||
`docs/01:246`. §4's Verified row was itself corrected from "practice" to
|
||
"**exposure**" in entry (l); the copy decks kept the barred word. Fixed to the
|
||
register's own substitute.
|
||
- **`LegalService` JSON-LD** — `docs/04-seo-spec.md` specified it for the home
|
||
page. schema.org defines `LegalService` as a business providing legal advice
|
||
and **representation**: it asserts in machine-readable form precisely what D13
|
||
bars. Changed to `ProfessionalService`, with the reason recorded so it is not
|
||
changed back. `worksFor` on the `Person` node had no register-safe value —
|
||
populating it either names the boutique (D16) or misstates the employer — so
|
||
it is dropped in favour of `jobTitle`.
|
||
- **Tribunal-secretary work** — `docs/01:173,180` and `docs/03:32` instructed
|
||
offering it; `docs/07-fees.md:116` records Pouya removing the rate and barring
|
||
the offer. Three files against one; the one was right.
|
||
- **§4's Forbidden table and `docs/03:52`** justified the superlative ban with
|
||
"LSO marketing rules" — the **fourth** surviving form of the licensure claim,
|
||
two rows below the `NOT ESTABLISHED` row. Restated on grounds that do not
|
||
depend on licence status. *(The §4 instance is the architect's to apply.)*
|
||
- **`docs/07-fees.md`** opened with "pending Pouya's sign-off — Q14" and
|
||
"**Nothing in this document publishes until Pouya confirms the figures**",
|
||
then contradicted itself 85 lines later with "This is the card. Build `/fees/`
|
||
from it." An implementer reading top-to-bottom blocks the page. Header
|
||
rewritten to D14 as confirmed.
|
||
- **Nine stale `Q` blockers** across five spec files — Q4, Q10, Q11, Q12, Q14,
|
||
Q20, Q5 — all answered or re-tracked, three of them gating `/fees/`, whose
|
||
figures are confirmed. Swept.
|
||
|
||
### Code defects
|
||
|
||
- **`src/data/site.ts`** published `responseTime: 'Inquiries are answered within
|
||
one business day.'` — a service level a reader can hold him to, not in §4. Set
|
||
`null` with a `TODO(pouya)`; **Q27**.
|
||
- **The memberships block** carried a blanket `[verified]` stamp over the OBA
|
||
section names, which §4 marks `[assumed]`. Downgraded, flagged; **Q28**.
|
||
- **`src/content/config.ts`** — `/** Drafts are excluded from the build, the
|
||
index, and the sitemap. */` describes three controls, **none implemented**;
|
||
the sitemap filter covers `/legal/` only. Same defect class as Q22. Restated
|
||
as intent with a deadline. Its `title`/`description` bounds also contradicted
|
||
`docs/04` (max 70 / min 70 against 50-60 / 140-160); tightened to the spec.
|
||
- **`astro.config.mjs`** set `prefetch: { prefetchAll: true, defaultStrategy:
|
||
'viewport' }`, injecting Astro's prefetch script and an IntersectionObserver
|
||
into **every** page and speculatively fetching every link that scrolls into
|
||
view — against CLAUDE.md's "default to zero JS" and §7's "most pages ship zero
|
||
JS", with no Change Log entry. Set to `prefetchAll: false` /
|
||
`defaultStrategy: 'hover'`, the setting the written conventions imply. If
|
||
prefetch-all is wanted, it needs a decision entry.
|
||
- **`src/styles/tokens.css`** attached the ink contrast figure (11.09:1) to both
|
||
ink and maroon; on maroon `--gold-l` measures 8.11:1. Both pass AA, so no
|
||
accessibility consequence — but the token file is what developers read.
|
||
|
||
### Also corrected
|
||
|
||
`docs/06` cited a billing **alarm** verified by `cloudwatch describe-alarms`; the
|
||
guide set up an AWS **Budget**, which that command never returns — and nothing
|
||
records either as created. Now names `budgets describe-budgets` and says confirm,
|
||
do not assume. The booking cutover check is marked conditional on R6, since
|
||
`BOOKING_URL` is empty by decision. `scripts/aws-discover.sh` and `docs/06`
|
||
claimed "every call is a list or describe" — four are not (`sts
|
||
get-caller-identity`, `apigatewayv2 get-apis`, `s3api get-bucket-versioning`,
|
||
`configure get`); all are genuinely read-only, so the substance held and the
|
||
wording did not. Four stale `AWS-Hosting-Guide.md` paths repointed at
|
||
`docs/reference/`. The reference workflow still said "Two passes" above three
|
||
sync steps — the one file entry (o)'s three-pass sweep missed, and a
|
||
twelve-character grep would have caught it. The IAM procedure had 22 lines of
|
||
multipart prose between "attach this policy" and "create an access key", which
|
||
also broke the ordered list in CommonMark; moved below step 3.
|
||
|
||
### Declined, with reasons
|
||
|
||
**The guard was not widened.** `adversarial-reviewer` showed it does not cover
|
||
the secrets — and by Q22, an unset key is the *most likely* first-run failure, so
|
||
the stated benefit ("one second instead of a full build") does not apply to the
|
||
likeliest case — nor `vars.INTAKE_ENDPOINT`, whose absence would **ship a live
|
||
form posting to an empty endpoint**. Both are real. Neither was done: the ruling
|
||
named three variables, and `INTAKE_ENDPOINT` additionally needs promoting to
|
||
job-level `env:`. **What was fixed instead is the guard's comment**, which
|
||
claimed it converted the problem "on every Gitea version" into a clean failure —
|
||
broader than what it implements. It now states its scope and points at **Q29**.
|
||
|
||
**The Gitea 1.21 claim is stamped `[assumed]`, not verified.** The version could
|
||
be confirmed with one command on the instance. It was not run here; the guard is
|
||
designed to work without knowing the answer, so the stamp is the honest record.
|
||
|
||
**`docs/06` still pairs the account ID with the backup-bucket callout** — the
|
||
pairing entry (m) removed from `README.md` as an inference vector. `docs/06` is
|
||
an operational document where the account ID is load-bearing, unlike the README.
|
||
Flagged rather than changed; if you want it out, it moves to `aws-inventory.txt`,
|
||
which is gitignored.
|
||
|
||
### Verification
|
||
|
||
The guard's `run:` block was extracted from parsed YAML and **executed** by
|
||
`adversarial-reviewer` under three shells and four input states — fail-closed
|
||
confirmed. Both workflow YAMLs parse. The barred-word sweep was run as the
|
||
`grep -iE` above and its output read. `stat` gave 357,627 bytes. `npm run lint`,
|
||
`check` and `build` were **not run**: `node_modules` is absent and `npm ci`
|
||
cannot install without a lockfile, so the `astro.config.mjs`, `site.ts` and
|
||
`config.ts` edits are **unverified by any type-checker** — they are small and
|
||
syntactically simple, and that is the whole of the assurance.
|
||
|
||
**Opened:** Q27, Q28, Q29. **Still open:** Q22, Q19 (blocking), Q23 (runner
|
||
half), Q5/R6 (parked). **Closed by entry (p), confirmed here:** Q24, Q25, Q26.
|
||
|
||
**Lesson.** Entry (o) said the sweep must be a command whose output is read.
|
||
This entry adds what that costs when the command is wrong: the pattern
|
||
`licensed|legal professional` cannot match "lawyer", so a compliant sweep still
|
||
missed a file added in the same session. **And the largest finding of the session
|
||
was in a file nothing had asked either reviewer to look at.** Both reviewers were
|
||
pointed at a diff; the destructive defect was three files away, left by a
|
||
correction that reached one file and stopped. Scope the audit to the *decision*
|
||
that changed, not the lines that changed.
|
||
|
||
---
|
||
|
||
## 2026-08-26 (p) — Q24, Q25, Q26 answered; R7 ratified; R8 promoted to a rule
|
||
|
||
**Who:** Pouya relaying Claude Code's session close. Claude (architect) deciding.
|
||
|
||
**Q25 — struck. This was the dangerous one and it was mine.** §4's Verified table
|
||
carried "The boutique **may be named on the site**", authorising precisely what
|
||
**D16 — never named** forbids. Sequence: Pouya said it could be named, then
|
||
reversed; D16 recorded the reversal; **the permission was never removed.** A
|
||
locked decision and the table copy is written from disagreed, and the table was
|
||
the more permissive of the two. Struck.
|
||
|
||
The general defect: reversing a decision requires removing the permission it
|
||
granted, not only recording the new position. Same shape as the D3 amendment that
|
||
went unswept three times.
|
||
|
||
**Q26 — answered, and the third form of the same claim is gone.** §4's opening
|
||
asserted "Every public claim on this site is subject to Law Society of Ontario
|
||
marketing rules" — which asserts regulatory status by implication, since those
|
||
rules bind licensees. Claude Code was right that this is the same half-measure as
|
||
the "legal professional" reversal, one level further down.
|
||
|
||
Old → new: the register's rationale no longer rests on licensure at all. It rests
|
||
on the fabricated-credentials history, which is documented, sufficient, and true
|
||
regardless of licence status. The paragraph's own history is kept in place as a
|
||
caution — three progressively weaker forms of one unverified claim, each
|
||
surviving a sweep.
|
||
|
||
**§4 now carries a `Licence status — NOT ESTABLISHED` row.** Stamped
|
||
`[unestablished]`, a new stamp for this case. It records the honest position: this
|
||
file does not know, Pouya's instruction was about the *site* and not a statement
|
||
of fact either way, and nothing may assert, deny, or infer it. Claude Code was
|
||
also right that the two licensure rows were stamped `[verified]` as *directives*,
|
||
which is a different thing from a verified fact — this row separates the two.
|
||
|
||
**Q24 — closed.** `AWS-Hosting-Guide.md` copied to `docs/reference/`. It is the
|
||
only record of how the hand-built infrastructure was created, so it belongs in
|
||
the repo rather than in a Drive folder the repo cites but cannot reach. Scanned
|
||
before copying: no access keys, no secrets, no account ID.
|
||
|
||
**Q23 — answered by hardening rather than by version-checking.** The risk is real
|
||
— on Gitea below ~1.21, `${{ vars.* }}` interpolates empty and the sync target
|
||
becomes `s3://`. But a version check is a fact that goes stale. Ruling: add a
|
||
**pre-flight guard step** to `.gitea/workflows/deploy.yml` that fails the run if
|
||
any required variable is empty, before any AWS call. That converts a silent
|
||
destructive misfire into a clean failure on every Gitea version, and it
|
||
subsumes R7's third item.
|
||
|
||
**R7 ratified, with one amendment.**
|
||
1. Cache-policy table amended to match the pipeline — **accepted.** Documenting
|
||
what the pipeline does beats documenting an intention. `robots.txt` and
|
||
`sitemap*.xml` at `max-age=0, must-revalidate` is immaterial at this size.
|
||
2. `s3:AbortMultipartUpload` omitted, lifecycle rule as intended cover —
|
||
**accepted, with the reasoning corrected.** The lifecycle rule does not exist,
|
||
so it is not the cover. The actual cover is that `aws s3 sync` only goes
|
||
multipart above 8 MB and the largest asset in the repo is a 357 KB portrait.
|
||
Record *that*, and add a note to revisit if any asset ever approaches 8 MB.
|
||
Do not document a control that does not exist — that is Q22's defect again.
|
||
3. `aws s3 ls` pre-flight documented but not implemented — **superseded** by the
|
||
guard step above, which covers more.
|
||
|
||
**R8 promoted from a reminder to a rule.** *"A sweep is a command whose output is
|
||
read, not a claim."* Entries (l), (m) and (n) each asserted a completed sweep;
|
||
instances survived all three — one of them inside `claims-auditor.md`, the
|
||
definition of the agent whose job is to catch it. A reminder is the wrong
|
||
instrument for something this reliable. It belongs in `/build` Phase 6 and
|
||
`/wrap`: any claim that a change was applied across files must cite the command
|
||
and be made only after reading its output.
|
||
|
||
**R1's wording corrected:** it says "the site currently asserts the JD only".
|
||
There is no site — `src/pages/` is empty. Restated in the conditional.
|
||
|
||
**Closed:** Q23, Q24, Q25, Q26. **Still blocking the build:** nothing.
|
||
**Still blocking `/contact/`:** Q19. **Still open:** Q22, Q5 (parked).
|
||
|
||
---
|
||
|
||
## 2026-08-26 (o) — Five rulings implemented; both reviewers run; the D3 sweep finally completed
|
||
|
||
**Who:** Pouya ruled on entry (m)'s escalations and reversed his own F5 ruling.
|
||
Claude Code implemented, ran `claims-auditor` **and** `adversarial-reviewer` in
|
||
parallel on the diff, and resolved 27 + 17 findings.
|
||
|
||
### The five rulings, implemented
|
||
|
||
1. **§4 and §10 "licensed"** — the architect's, done in entry (n).
|
||
2. **Reversal on "a legal professional's"** — cut from `README.md:35` and
|
||
`CLAUDE.md` (twice). The sentences now assert nothing about professional
|
||
status and state the reason instead.
|
||
3. **`s3:PutObjectAcl` dropped** from the policy in `docs/06-deployment.md`. §10's
|
||
"four actions" is now accurate without §10 being touched, and every file that
|
||
states a count agrees with the policy: `README.md:77`, `docs/06:82`,
|
||
`.gitea/workflows/deploy.yml:13`, `AGENTS.md` §10.
|
||
4. **`.github/workflows/deploy.yml` → `docs/reference/github-actions-oidc.yml.example`**
|
||
via `git mv`; `.github/` removed entirely. It held exactly one file — no
|
||
CODEOWNERS, no dependabot, no templates — and nothing referenced the path.
|
||
References updated in `README.md`, `CLAUDE.md`, `docs/06`, `.gitea`, and §7.
|
||
5. **Q22** left open with the designed-not-confirmed phrasing intact.
|
||
|
||
### The reviewers found that the D3 sweep had never actually reached `docs/06`
|
||
|
||
Both agreed on the same blocking defect, independently. `docs/06-deployment.md`
|
||
is the file `README.md` points to as "Full procedure, IAM policy, runner setup" —
|
||
and it still opened with:
|
||
|
||
- `Authority: AGENTS.md §3 D3 (git + GitHub Actions → ...)` — D3 as amended says
|
||
Gitea;
|
||
- a topology diagram, **the first content block in the file**, reading
|
||
`GitHub push to main → GitHub Actions → assume AWS role via OIDC (no stored
|
||
keys)`. That is the exact sentence entry (l) called "the serious one", six
|
||
lines above the section that contradicts it;
|
||
- an entire 19-line section, `## Why OIDC and not access keys`, in the
|
||
imperative — *"IAM → Identity providers → add OIDC provider..."* — with **no
|
||
marker that it does not apply**, naming a third principal `adr-site-deploy`
|
||
that conflicts with `adr-sml-deploy`, and citing Q9, which is answered.
|
||
|
||
`adversarial-reviewer` named the concrete failure: an operator working the
|
||
document top-to-bottom adds a GitHub federation trust to account `327082975128`
|
||
— the account §10 rates High blast-radius — that nothing will ever use, and
|
||
plausibly never creates `adr-sml-deploy` at all. Two mutually exclusive
|
||
credential procedures in one file with no signpost saying which is live.
|
||
|
||
**Fixed.** Authority line cites D3 as amended. Topology rewritten to Gitea +
|
||
static key. The OIDC section is retitled *Why OIDC would have been better — and
|
||
why it is unavailable*, opens with a **do not execute** block, and its executable
|
||
steps are gone.
|
||
|
||
### The "licensed" sweep had missed three more files, including the auditor's own persona
|
||
|
||
Entry (n) scoped the reversal to "`README.md`, `CLAUDE.md` (twice), and this
|
||
file." Five instances survived in three files it did not name:
|
||
|
||
- **`.claude/agents/claims-auditor.md:8`** — *"You audit public copy for a
|
||
**licensed legal professional's** marketing site."* This is the system prompt
|
||
of the agent that enforces the rule. Its opening sentence asserted the exact
|
||
claim its own §"Licensure (D13)" instructs it to flag.
|
||
- **`.claude/agents/adversarial-reviewer.md:9`** — *"a legal professional's
|
||
dispute resolution practice"*, the precise phrase entry (n) reverses.
|
||
- **`docs/08-execution-protocol.md:63`** — *"a licensed professional's public
|
||
marketing page"*. **This file was edited in that same diff**, eleven lines
|
||
above the surviving phrase.
|
||
|
||
Entry (n) said "twice in two entries that a claim about a sweep was made without
|
||
the sweep being verified. The pattern, not the instances, is the finding." This
|
||
was the third. It is now swept by command, not by recall:
|
||
|
||
```
|
||
grep -rn -i "licensed\|legal professional" --include="*.md" --include="*.yml" .
|
||
```
|
||
|
||
Every surviving hit is either rule text stating the prohibition, or Change Log
|
||
history, which rule 3 forbids editing.
|
||
|
||
### Also fixed
|
||
|
||
**Register and rule accuracy.** §4's internal-docs rule cited a `[assumed]` stamp
|
||
on licensure that **does not exist** — the two licensure rows are stamped
|
||
`[verified]` as *directives not to publish*, which is a different thing. A reader
|
||
following the pointer found nothing there, in the sentence stating the rule.
|
||
Reworded here and in `CLAUDE.md:30` to say what is true: the Verified table does
|
||
not establish licence status either way. **Duplicate `Q22`** — two rows, two
|
||
scopes, one number, one of them mine; merged into the fuller statement, keeping
|
||
the architect's `aws iam get-user` check command. **§7 Node** re-stamped
|
||
`[verified]` — it was `[assumed]` for something directly checkable.
|
||
|
||
**Claims that overstated what exists.** `CLAUDE.md:164` still said *"deploys use
|
||
OIDC role assumption"* — verbatim the F1 claim, in a file both prior sweeps
|
||
touched; it and `CLAUDE.md:119` are corrected. `.gitea/workflows/deploy.yml` and
|
||
`CLAUDE.md` asserted the deploy credential in the present tense; both now cite
|
||
Q22. `docs/06` asserted five blocking PR checks — the workflow has **no
|
||
`pull_request` trigger** and neither `lint` nor `lighthouse` is wired, so nothing
|
||
gates a merge today; retitled *planned, not implemented*. `README.md:5` and
|
||
`docs/06`'s "every push deploys" both hedged against the never-run-green fact the
|
||
same files establish elsewhere.
|
||
|
||
**The moved reference file carried the defect the move was meant to contain.**
|
||
Its line 16 still read *"OIDC role assumption — no long-lived AWS credentials in
|
||
this repository"*: present tense, about this repository, and false. It also
|
||
carried a live `TODO(pouya): AGENTS.md Q9, Q10` against two struck rows — which
|
||
`CLAUDE.md`'s definition of done treats as a build failure — for a variable that
|
||
will never be set. Both fixed, along with its claim that the file is usable on
|
||
GitLab (different CI schema entirely; it is the design there, not the
|
||
implementation).
|
||
|
||
**Two security-posture claims narrowed.** `docs/06` said the workflow's
|
||
`aws sts get-caller-identity` pre-flight means "a credential problem fails loudly
|
||
and early rather than halfway through a sync." `sts:GetCallerIdentity` requires
|
||
**no IAM permission** — it succeeds for any valid key regardless of policy. It
|
||
catches a missing or revoked key and misses an under-scoped one, which is exactly
|
||
the risk this diff introduced by removing an action. Narrowed, with the one-line
|
||
`aws s3 ls` check that would make it load-bearing. And `README.md` had re-dropped
|
||
§10's *"which by its name is"* hedge on `mlp-clientdb-prod-backups` — the defect
|
||
entry (m) F2 records as fixed — as had `docs/06:113`, escalated in entry (n) and
|
||
not done. Both restored.
|
||
|
||
**Documentation matching implementation.** The cache section described **two**
|
||
sync passes; the workflow runs **three**, and two ordering dependencies are
|
||
load-bearing and undocumented — pass 3 re-walks the tree and preserves pass 2's
|
||
image headers only because `sync` skips just-uploaded objects, and pass 3's
|
||
excludes also exclude those prefixes from `--delete`, which is why hashed assets
|
||
from old deploys are kept deliberately. Both now stated. The `robots.txt` /
|
||
`sitemap*.xml` row claimed `max-age=3600`; nothing implements it, so the table
|
||
now records what the pipeline does. Two conflicting variable tables for the same
|
||
five names — one under **Secrets** with real values, one under **Variables** with
|
||
placeholders — merged; entering those as secrets would have masked them in the
|
||
logs the doc says to read them from. Duplicate booking references (Q5 vs R6)
|
||
resolved to R6. `README.md` said "no `src/pages/`"; the directory exists and is
|
||
empty, which is not what a reader would find.
|
||
|
||
**`docs/08-execution-protocol.md`** — entry (n)'s inserted block landed between
|
||
*"`claims-auditor` reads the copy..."* and its follow-up *"It is a separate agent
|
||
on purpose"*, leaving "It" twelve lines from its antecedent and reading as though
|
||
the frontmatter were a separate agent. Block moved below.
|
||
|
||
### Declined, with reasons
|
||
|
||
**`s3:AbortMultipartUpload` not added.** `adversarial-reviewer` traced every AWS
|
||
call in the workflow against the policy and found the happy path fully covered,
|
||
with this one gap: objects over 8 MB upload multipart, and an interrupted
|
||
transfer cannot clean up its own parts. It recommended against adding the
|
||
permission — an S3 lifecycle rule aborting incomplete uploads after 7 days solves
|
||
it without widening the policy. Agreed, and left as an operational item below
|
||
rather than a policy change.
|
||
|
||
**The `aws s3 ls` pre-flight is documented, not implemented.** Adding it changes
|
||
the deploy pipeline, which was not in scope. It is written into `docs/06` as the
|
||
fix for the narrowed claim.
|
||
|
||
**§4's tables untouched.** Two findings land in the register itself; both are
|
||
escalated below rather than edited. §4 is the architect's instrument.
|
||
|
||
### Escalated — for the architect
|
||
|
||
*(All four now tracked: 1 and 2 as **Q25** and **Q26** in §9; 3 folded into Q26;
|
||
4 left in R1, which already owns the licensure framing.)*
|
||
|
||
1. **§4's Verified table authorises what D16 forbids.** `AGENTS.md:153` reads
|
||
*"The Toronto litigation and ADR boutique **may be named on the site** ... the
|
||
name itself is pending, see Q7."* D16 says **"Never named."** Q7 is answered:
|
||
*"Pouya reverted to generic. The boutique is never named."* A **Verified** row
|
||
currently permits publication of the exact thing a locked decision bars — the
|
||
same shape as the F5 defect in entry (l), in the same table, and the register
|
||
is where copy is written from.
|
||
2. **§4's opening asserts regulatory status by implication.** *"Every public
|
||
claim on this site is subject to Law Society of Ontario marketing rules"* —
|
||
LSO marketing rules bind licensees. Stating flatly that they govern this site
|
||
asserts the licensure §4 declines to verify, in the sentence that replaced
|
||
"Pouya is a licensed legal professional". A half-measure of the same shape as
|
||
the "legal professional" reversal.
|
||
3. **Consider an explicit §4 row** — *"LSO licence status | UNKNOWN / not
|
||
verified either way"* — which would make the internal-docs rule's pointer land
|
||
somewhere real instead of being reworded around.
|
||
4. **R1 (§12)** describes "the site currently asserts the JD only". There is no
|
||
site; `src/pages/` is empty. R1 is the reminder that must not ossify, so it
|
||
should be accurate about what it describes.
|
||
5. **Operational:** add an S3 lifecycle rule aborting incomplete multipart
|
||
uploads after 7 days; and once Q22 is answered, run
|
||
`aws s3 sync ./dist s3://adr-smlcompany-site --dryrun` under the new key to
|
||
confirm no `s3:GetBucketLocation` call is needed.
|
||
6. **Minor:** `.yml.example` is not a Prettier-recognised extension, so the moved
|
||
reference file has silently dropped out of `prettier --check` coverage. Frozen
|
||
reference material, so near-harmless — but nothing validates it as YAML now.
|
||
|
||
**Q23–Q26 opened, none blocking the build.** Q23: is an `act_runner` registered, and is the Gitea
|
||
instance ≥ 1.21 for the `vars` context the workflow depends on throughout? On an
|
||
older instance `vars.S3_BUCKET` interpolates empty and the sync target becomes
|
||
`s3://`. Q24: `AWS-Hosting-Guide.md` is cited by `docs/06` as the source for
|
||
existing infrastructure and two cutover checks, and **does not exist in the
|
||
repository**; the two dependent checks have been restated self-containedly, so
|
||
nothing is blocked. Q25 and Q26 carry the two §4 escalations above.
|
||
|
||
**R7 and R8 added to §12.** R7 records three spec decisions made on Pouya's
|
||
behalf and not ratified — the amended cache-policy row, the omitted
|
||
`s3:AbortMultipartUpload`, and the documented-not-implemented `aws s3 ls`
|
||
pre-flight. R8 records the sweep-verification lesson as a standing discipline
|
||
rather than a lesson buried in one entry, which is what let it recur three times.
|
||
|
||
### Verification
|
||
|
||
`npm run lint`, `npm run check`, and `npm run build` were **not run** —
|
||
`node_modules` is absent, and `npm ci` cannot install without a lockfile. No
|
||
JavaScript, TypeScript, or Astro source was touched. The `.gitea` workflow and
|
||
the `.yml.example` were not YAML-parsed either: PyYAML is unavailable in this
|
||
environment and the project has no YAML tooling installed. Both were changed only
|
||
in comment blocks, and the indentation of every edited comment was checked by
|
||
eye. The "licensed" sweep was executed as the grep above and its output read, not
|
||
asserted. Every prose line added to `README.md` and `CLAUDE.md` is ≤ 80 columns.
|
||
|
||
**Lesson.** Entry (m) recorded that a correction is a change and gets reviewed
|
||
like one. This pass adds the sharper version: **the sweep must be a command, and
|
||
its output must be read.** Three consecutive entries claimed a completed sweep;
|
||
three times instances survived, and the third time one of them was inside the
|
||
definition of the agent whose job is to catch it. The `/wrap` step should require
|
||
pasting the grep, not describing it.
|
||
|
||
---
|
||
|
||
## 2026-08-26 (n) — Register corrected; a declined finding reversed on appeal
|
||
|
||
**Who:** Pouya relaying Claude Code's re-audit. Claude (architect) recording.
|
||
|
||
**Correction to entry (l), which was false.** It claimed all three files had been
|
||
rewritten off "licensed". Two were. **This file still said it twice** — §4's own
|
||
opening sentence ("Pouya is a licensed legal professional") and §10's risk row
|
||
("professional-conduct exposure for a licensed practitioner"). The register was
|
||
asserting as established fact the very thing it marks `[assumed]`, in the section
|
||
that exists to prevent exactly that. Entry (l) stands as written per rule 3; this
|
||
is the correction. Both lines are now fixed.
|
||
|
||
That is twice in two entries that a claim about a sweep was made without the
|
||
sweep being verified. The pattern, not the instances, is the finding.
|
||
|
||
**Reversal — "a legal professional's" is out too.** `claims-auditor` wanted the
|
||
phrase cut entirely, arguing that in Ontario it reads as an LSO licensee and so
|
||
trips the same bar as "licensed". Claude Code declined it, correctly, because it
|
||
was my explicit ruling — and recorded the reasoning rather than silently keeping
|
||
it, which is what let it be revisited.
|
||
|
||
**On appeal the auditor is right and I was wrong.** "Legal professional" was a
|
||
half-measure: a weaker assertion of the same unverified thing. The fix is to
|
||
assert nothing about professional status and state the reason instead — the
|
||
previous site carried fabricated credentials, which is true regardless of licence
|
||
status and carries the full force of the rule. Applies to `README.md`,
|
||
`CLAUDE.md` (twice), and this file.
|
||
|
||
Worth preserving: **the mechanism worked because the decline was reasoned rather
|
||
than silent.** A finding dropped quietly is a finding that cannot be appealed.
|
||
|
||
**Q22 opened — does `adr-sml-deploy` exist?** Claude Code caught that its own
|
||
README rewrite asserted a control nothing records as in place. `docs/06` is
|
||
written imperatively — "Create the user", "Create an access key" — a procedure,
|
||
not a record. Nothing in this file says it was performed. Its framing of this as
|
||
"same failure class, inverted" is exactly right: the original README understated
|
||
the credential risk, its replacement overstated the control. **The §10 rotation
|
||
obligation has no subject until Q22 is answered.**
|
||
|
||
**Accepted — §10's "four actions" resolves by tightening the policy, not editing
|
||
the count.** `docs/06` grants five: `ListBucket`, `PutObject`, `PutObjectAcl`,
|
||
`DeleteObject`, `CreateInvalidation`. `s3:PutObjectAcl` is unused by `aws s3 sync`
|
||
without `--acl`, and inert under OAC with ACLs disabled. Dropping it makes §10
|
||
accurate **and** the policy tighter — strictly better than correcting the number.
|
||
Handed to Claude Code.
|
||
|
||
**Accepted — move the GitHub workflow out of `.github/`.** Gitea falls back to
|
||
`.github/workflows` when `.gitea/workflows` is absent, so a live `push:` trigger
|
||
sitting there is conditionally inert, not inert. Moving it to
|
||
`docs/reference/github-actions-oidc.yml.example` makes it structurally inert.
|
||
Handed to Claude Code.
|
||
|
||
**Also noted, no action:** Claude Code reported that `npm run lint` and
|
||
`npm run check` could not run because `node_modules` is absent, and said so
|
||
rather than reporting a check it did not run. That is the Phase 5 rule working.
|
||
|
||
**Opened:** Q22. **Still blocking the build:** nothing. **Still blocking
|
||
`/contact/`:** Q19.
|
||
|
||
---
|
||
|
||
## 2026-08-26 (m) — README corrected against D3-as-amended; second audit found nine more
|
||
|
||
**Who:** Pouya ruled on the five findings in entry (l); Claude Code implemented,
|
||
re-ran `claims-auditor` on the result, and resolved the second pass.
|
||
|
||
### The architect's rulings, applied
|
||
|
||
**F5 — no change, as ruled.** D13 bars "practice" for the boutique role, not for
|
||
Pouya's own ADR practice. `README.md:3` and `package.json:5` stand.
|
||
|
||
**F2 — scope corrected, wording changed.** The Forbidden table governs published
|
||
pages, not repository documentation; that scope is now stated in §4. The real
|
||
defect was different and the architect identified it: licensure is `[assumed]`
|
||
in §4, so no file should call Pouya "licensed". `README.md:36` now reads *a legal
|
||
professional's public marketing surface* — the clause that follows, about the
|
||
previous site's fabricated credentials, already carries the reasoning.
|
||
|
||
**F1, F3, F4 — Deployment section rewritten** against §7 and
|
||
`docs/06-deployment.md`. The section had been written against D3 as originally
|
||
decided and never swept when D3 was amended to Gitea. It now names
|
||
`.gitea/workflows/deploy.yml` as the live pipeline, says Gitea Actions rather
|
||
than GitHub Actions, states plainly that a long-lived AWS credential is involved
|
||
and why (Gitea is not an AWS OIDC provider), and names the quarterly rotation
|
||
obligation. `format` and `lighthouse` added to the scripts table.
|
||
|
||
### The second audit found nine findings in the replacement text
|
||
|
||
Seven fixed, one declined, one escalated. The re-audit was worth running: the
|
||
rewrite traded the original defect for its mirror image.
|
||
|
||
**F1 (fixed) — the replacement asserted a control state that may not exist.**
|
||
The new text said deploys *do* authenticate as IAM user `adr-sml-deploy` with a
|
||
key in Gitea secrets. Only the **decision** is verified (D3 as amended, §7).
|
||
`docs/06-deployment.md` is written entirely in the imperative — "Create the
|
||
user", "Create an access key" — i.e. a procedure to perform, not a record of one
|
||
performed, and `adr-sml-deploy` appears nowhere else in this file. The old README
|
||
understated the credential risk; the new one asserted a control that nothing
|
||
records as in place. Same failure class, inverted. Now phrased as designed-not-
|
||
confirmed, and **raised as Q22**.
|
||
|
||
**F2 (fixed) — a hedge was dropped, and an account number was disclosed.** §10
|
||
says `mlp-clientdb-prod-backups` is "**which by its name is** a law firm's
|
||
production client-database backups" — only the bucket name was ever observed.
|
||
The README stated the contents flatly. It also paired the live account ID with
|
||
that statement in the repo's most pasteable file, and D16 says the boutique is
|
||
never named — "this account holds a law firm's client database" is an inference
|
||
vector that costs nothing to remove. The account number and the bucket name are
|
||
both now out of the README; the security reasoning stays, pointing at §10.
|
||
|
||
**F3 (fixed).** The bullet led with "**The key is rotated quarterly**" — a
|
||
description of an operating control — and conceded four lines later that the
|
||
task has no owner. Now an obligation: *must be rotated quarterly, and nobody
|
||
owns that yet.*
|
||
|
||
**F4 (fixed).** "It does not run. Editing it changes nothing." is conditional,
|
||
not absolute: Gitea falls back to `.github/workflows` when `.gitea/workflows` is
|
||
absent, and that file carries a live `push` trigger on `main`. Realised risk is
|
||
low — it would fail on `role-to-assume` with no OIDC provider rather than
|
||
mis-deploy — but describing a trigger-eligible file as inert invites someone to
|
||
treat it as safe. Now states the condition. **The auditor's better fix was
|
||
declined for scope:** moving it to `docs/reference/github-oidc-deploy.yml.example`
|
||
would make the claim structurally true instead of dependent on Gitea's
|
||
resolution order. Worth doing; not done here.
|
||
|
||
**F6 (fixed) — "Pushes to `main` build and deploy automatically" was not true.**
|
||
Verified against the filesystem, not inferred: there is no `package-lock.json`,
|
||
so `.gitea/workflows/deploy.yml:46`'s `npm ci` exits non-zero at step one; there
|
||
is no `src/pages/`, so both `npm run check` and `npm run build` fail; and whether
|
||
an `act_runner` is registered is recorded nowhere, which `docs/06:125-130` warns
|
||
"looks exactly like a broken pipeline." The README now says the pipeline has
|
||
never run green and names all three reasons.
|
||
|
||
**F7 (fixed).** "No wildcard actions, no wildcard resources" is literally false —
|
||
the policy uses `arn:aws:s3:::BUCKET_NAME/*`, correctly scoped but a wildcard. In
|
||
a paragraph whose entire job is to stop a future maintainer widening the policy,
|
||
an overstatement is the wrong error: the first reader who notices it discounts
|
||
the rest. Now: no `Action: "*"`, no `Resource: "*"`, nothing outside one bucket
|
||
and one distribution.
|
||
|
||
**F8 (fixed).** `npm run lint` and `npm run lighthouse` are listed in a table a
|
||
reader takes as "these work." Neither does — there is no ESLint flat config, and
|
||
ESLint 9 (pinned `^9.0.0`) errors without one, so the command dies before
|
||
Prettier runs; and there is no `lighthouserc`, so `lhci autorun` has no budgets
|
||
even though `docs/06:221-222` makes Lighthouse a blocking check. Both rows are
|
||
now marked **not yet wired**.
|
||
|
||
**F9 (fixed).** Two precision defects. The README restated the project's single
|
||
most important rule more narrowly than §4 states it — "no factual claim **about
|
||
the practice**" versus §4's "him, his credentials, his experience, or his
|
||
practice" — in the file a new contributor reads first. And it said `/build` runs
|
||
two review agents unconditionally, where `.claude/commands/build.md:52-53` allows
|
||
skipping `claims-auditor` when no copy changed. Both now mirror their sources.
|
||
|
||
**F5 (declined) — the auditor asked to cut "a legal professional's" entirely,**
|
||
on the grounds that in Ontario the phrase reads as an LSO licensee and so trips
|
||
§4's bar on "phrasing that *implies* entitlement to practise law." Declined
|
||
because the architect ruled this exact wording four hours earlier, having already
|
||
considered and rejected "licensed", and because the same phrase now appears
|
||
deliberately in `CLAUDE.md`. Recorded rather than silently kept: the auditor's
|
||
reasoning is not obviously wrong, and if the phrase is judged to imply licensure
|
||
it needs changing in three files at once, not one.
|
||
|
||
### Escalated to the architect — not fixed here
|
||
|
||
1. **Entry (l) records `CLAUDE.md`, `AGENTS.md`, and `README.md` as all rewritten
|
||
off "licensed". Two of the three were.** `CLAUDE.md` is clean. **This file
|
||
still says it twice** — line 110, "Pouya is a licensed legal professional",
|
||
in the opening sentence of §4 itself, and line 303, "professional-conduct
|
||
exposure for a licensed practitioner", in §10. The register is asserting as
|
||
fact the thing it marks `[assumed]`, in the section whose whole purpose is to
|
||
stop that. Not edited here because §4 is the architect's instrument.
|
||
|
||
2. **§10 says the deploy policy "grants four actions on one bucket and one
|
||
distribution."** It grants five: `s3:ListBucket`, `s3:PutObject`,
|
||
`s3:PutObjectAcl`, `s3:DeleteObject`, `cloudfront:CreateInvalidation`. The
|
||
discrepancy resolves in a useful direction — `s3:PutObjectAcl` is unused by
|
||
`aws s3 sync` and inert under OAC with ACLs disabled (`docs/06:205-206`), so
|
||
the policy is one action wider than it needs to be. Dropping it makes the
|
||
§10 count correct and the policy tighter at the same time. `docs/06:108` also
|
||
drops §10's "by its name" hedge on the backup bucket.
|
||
|
||
3. **The `.github` workflow's location** — see F4 above.
|
||
|
||
### Verification
|
||
|
||
`npm run lint` and `npm run check` were **not run**: `node_modules` is absent, so
|
||
neither can execute. This change touches only `README.md`, which is outside
|
||
`astro check` and ESLint; Prettier has no config in the repo, so its default
|
||
`proseWrap: "preserve"` leaves markdown prose unreflowed. Line widths were
|
||
checked by hand and every line Claude Code wrote is ≤ 80 columns.
|
||
|
||
**Lesson, extending entry (l)'s.** (l) recorded that amending a decision requires
|
||
sweeping every file that referenced the original. This pass adds the corollary:
|
||
**a correction is a change, and gets reviewed like one.** Seven of the nine
|
||
findings above were in text written specifically to fix an audit finding. The
|
||
first rewrite of a false claim is the most dangerous moment for it, because
|
||
everyone involved is now confident the area is clean.
|
||
|
||
---
|
||
|
||
## 2026-08-26 (l) — First adversarial review run; it found defects in the specs
|
||
|
||
**Who:** Pouya ran `claims-auditor` against `README.md` to verify the agents load.
|
||
It loaded, and returned five findings before any site code exists.
|
||
|
||
**The agents are confirmed working.** R1 was surfaced unprompted, as §12 requires.
|
||
F2 and F5 were escalated rather than silently edited — the behaviour the brief
|
||
asks for on judgement calls.
|
||
|
||
**Two register-level defects fixed here (architect's, not Claude Code's):**
|
||
|
||
**F5 root cause — §4 contradicted D13.** Old → new: the Verified table read
|
||
*"Active litigation practice: personal injury, construction, regulatory (POA),
|
||
insurance (SABS)"* → **"Active litigation exposure: …"**. The row quoted the
|
||
strategy brief verbatim and used the exact word D13 bars in exactly the context
|
||
D13 bars it. Anyone writing copy from the register would have inherited the
|
||
violation **from the register itself** — the worst place for it to live.
|
||
|
||
D13 now also states the distinction explicitly: "practice" is barred **for the
|
||
boutique role**, not for Pouya's own ADR practice. So "the dispute resolution
|
||
practice of Pouya Lajevardi" is correct — `README.md:3` and `package.json:5` need
|
||
no change. **F5 resolved, no edit to the README.**
|
||
|
||
**F2 — the Forbidden table's scope was overbroad.** Old → new: heading read "must
|
||
not appear **anywhere**" → **"must not appear on the site"**, with the scope
|
||
stated: published pages including JSON-LD, not repository documentation.
|
||
|
||
The auditor was right that something was wrong, though the rule it cited was the
|
||
wrong one. `README.md`, `CLAUDE.md`, and this file all called Pouya "a licensed
|
||
professional" while §4 marks licensure **`[assumed]`**. Internal docs were
|
||
asserting as fact what the register cannot vouch for. A new rule now covers this
|
||
directly. The three phrases are rewritten to state the *reason* for the
|
||
strictness — the previous site carried fabricated credentials — rather than a
|
||
credential we cannot confirm.
|
||
|
||
**F1, F3, F4 — handed to Claude Code.** One root cause: `README.md`'s Deployment
|
||
section was written against D3 as originally decided and never updated when D3
|
||
was amended to Gitea. `CLAUDE.md`, `docs/06`, and this file were all updated; the
|
||
README was missed.
|
||
|
||
F1 is the serious one. "Deploys via OIDC — there are no long-lived AWS credentials
|
||
in this repository" is **false**, and dangerous in the specific way the auditor
|
||
identified: it is narrowly defensible, since the key is not tracked in git — which
|
||
is exactly why it would suppress the quarterly rotation obligation in D3, in an
|
||
account §10 rates High blast-radius because it holds `mlp-clientdb-prod-backups`.
|
||
|
||
**Lesson recorded.** Amending a decision requires sweeping every file that
|
||
referenced the original, not the files that happen to come to mind. The review
|
||
caught it; the amendment process should have. Worth adding to `/wrap`.
|
||
|
||
---
|
||
|
||
## 2026-08-26 (k) — Q21 resolved: nothing broken; SES sandbox is per-region
|
||
|
||
**Who:** Pouya ran the per-region check.
|
||
|
||
**Q21 closed — the good case.**
|
||
|
||
| Region | Verified | DKIM | Tokens |
|
||
|---|---|---|---|
|
||
| `ca-central-1` | `true` | **SUCCESS** | `kznn…` `jdue…` `f5pu…` — resolve correctly |
|
||
| `us-east-1` | `false` | PENDING | `3zsn…` `jejgp…` `xpiwy…` — doubled domain |
|
||
|
||
The region that matters is healthy. The three broken CNAMEs belong to a stray
|
||
`us-east-1` identity that nothing in this project uses; it is PENDING precisely
|
||
*because* those records were entered with the domain doubled. **No fix required.**
|
||
|
||
Recommendation recorded: **leave the three dead CNAMEs in DNS.** They are inert,
|
||
and the only way to cause harm is deleting the wrong row from a list of six
|
||
visually similar records. Optionally delete the `us-east-1` identity itself so it
|
||
stops reporting PENDING — that is a control-plane action with no DNS risk.
|
||
|
||
**New finding, and it would have cost a day: the SES sandbox is per-region.**
|
||
`ProductionAccessEnabled: false` was read from `ca-central-1`, which is where the
|
||
intake Lambda, DynamoDB, and API Gateway all live. The AWS console defaults to
|
||
`us-east-1`, and the panel Pouya screenshotted was `us-east-1` — so the natural
|
||
path would have been to request production access in the wrong region, wait a
|
||
day, and find the confirmation email still failing. Flagged in §7 and on Q19.
|
||
|
||
**Also worth noting for the record:** entry (j)'s correction was itself only
|
||
half the story. DNS proved which records resolved; it could not prove which
|
||
*mattered*. That needed the control plane. Neither source is sufficient alone —
|
||
the data plane says what exists, the control plane says what is expected, and a
|
||
discrepancy between them is the finding.
|
||
|
||
**Closed:** Q21. **Still blocking:** Q19 only.
|
||
|
||
---
|
||
|
||
## 2026-08-26 (j) — SPF/DMARC live; and a correction: three DKIM records are broken
|
||
|
||
**Who:** Pouya added the two TXT records. Claude verified independently.
|
||
|
||
**Q20 closed.** SPF and DMARC are both live and correct, confirmed by direct DNS
|
||
query rather than taken on report. Also confirmed unchanged: both existing `@`
|
||
TXT records, `google._domainkey`, `MX 1 smtp.google.com`, and
|
||
`adr.smlcompany.ca` → CloudFront. Nothing was disturbed.
|
||
|
||
**Correction to entries (h) and (i) — I had the two DKIM sets backwards.**
|
||
|
||
- Old → new: "`3zsn…`/`jejgp…`/`xpiwy…` are the live set; `f5pu…`/`jdue…`/`kznn…`
|
||
are inert orphans" → **the opposite.** The `f5pu` set resolves NOERROR at the
|
||
correct names. The `3zsn` set returns **NXDOMAIN**.
|
||
- **Root cause found.** `3zsnvsjg…._domainkey.smlcompany.ca.smlcompany.ca`
|
||
resolves; the correct name does not. Those three were entered into Namecheap's
|
||
Host field with the **full name including the domain**, so Namecheap appended
|
||
the domain a second time. This is precisely the gotcha flagged in entry (h) —
|
||
which was written before checking whether the existing records had already
|
||
fallen into it.
|
||
- **Why I got it wrong:** I inferred "live" from the SES console listing them and
|
||
did not verify against DNS. The console shows what SES *expects*, not what
|
||
exists. Lesson worth keeping: a control-plane listing is not evidence about the
|
||
data plane.
|
||
- **No harm done.** The advice in (i) was "leave both sets alone", which happened
|
||
to be the safe action either way.
|
||
|
||
**Q21 opened.** SES is regional, and `ca-central-1` reported
|
||
`VerifiedForSendingStatus: true` — only consistent with the `f5pu` set. So the
|
||
console panel screenshotted was probably a different region's identity. Until
|
||
that is confirmed per region, it is unknown whether the broken records matter.
|
||
Nothing should be deleted before that check.
|
||
|
||
**Closed:** Q20. **Opened:** Q21. **Still blocking:** Q19 (SES production access).
|
||
|
||
---
|
||
|
||
## 2026-08-26 (i) — SES DNS panel resolves the DKIM ambiguity; MAIL FROM absent
|
||
|
||
**Who:** Pouya sent the SES "Domain DNS records" panel.
|
||
|
||
**The six DKIM CNAMEs are now fully explained.** SES lists exactly three for
|
||
`smlcompany.ca`: `3zsnvsjg…`, `jejgp7na3…`, `xpiwyftpo…`. The other three in
|
||
Namecheap — `f5puwearz…`, `jdue2r22c…`, `kznn3cklv…` — are **not** referenced by
|
||
SES and are residue from an earlier verification of the same domain. Note the
|
||
TTLs corroborate this: the live set reads "1 min", the orphans "Automatic",
|
||
consistent with two separate additions.
|
||
|
||
**Recommendation recorded: leave the orphans in place.** They are inert. The only
|
||
way this becomes a problem is deleting the wrong three, which would break SES
|
||
DKIM and therefore DMARC. There is no upside to tidying a DNS zone.
|
||
|
||
**Custom MAIL FROM is not configured** — "No MAIL FROM records found". This
|
||
independently confirms the correction in entry (h): SES's envelope sender is at
|
||
`amazonses.com`, its SPF pass is unaligned with `smlcompany.ca`, and DMARC is
|
||
satisfied through DKIM alone. Configuring a custom MAIL FROM would add SPF
|
||
alignment as belt-and-braces; it is optional and not on the critical path.
|
||
|
||
**AWS's suggested DMARC value is `v=DMARC1; p=none;`** — valid but minimal, with
|
||
no `rua`, so it produces no reports. Using `v=DMARC1; p=none; rua=mailto:info@smlcompany.ca; fo=1`
|
||
instead so the monitoring period actually yields data before tightening to
|
||
`quarantine`.
|
||
|
||
**Net action for Q20 is two TXT records and nothing else.**
|
||
|
||
---
|
||
|
||
## 2026-08-26 (h) — DNS inspected; earlier SPF reasoning corrected
|
||
|
||
**Who:** Pouya sent the Namecheap DNS panel, asking exactly what to change
|
||
without breaking anything.
|
||
|
||
**Correction to entry (g) — the SPF reasoning was wrong.** Old → new: "SES needs
|
||
SPF or mail lands in spam" → **SES authenticates via DKIM, not SPF.** Without a
|
||
custom MAIL FROM domain, SES's envelope sender sits at `amazonses.com`, so its
|
||
SPF pass is not aligned with `smlcompany.ca` and contributes nothing to DMARC.
|
||
The six `*.dkim.amazonses.com` CNAMEs already in Namecheap are what make SES
|
||
DMARC-compliant, and they are working. The SPF record's real value is
|
||
authenticating **Google Workspace** mail, which has none. `include:amazonses.com`
|
||
stays because it is harmless and becomes live if a custom MAIL FROM is added.
|
||
Entry (g) is left as written per rule 3; this is the correction.
|
||
|
||
**Also found in the DNS panel:**
|
||
- Six SES DKIM CNAMEs where three are needed — the domain was verified twice.
|
||
Harmless, but do not prune without checking SES first.
|
||
- Two ACM validation CNAMEs → `jkddzztszm.acm-validations.aws`. **Flagged as
|
||
never-delete**: they auto-renew the `adr.smlcompany.ca` certificate, and
|
||
removing them breaks HTTPS silently at the next renewal rather than
|
||
immediately. This is the only genuinely destructive mistake available in that
|
||
panel.
|
||
- `@` carries a Namecheap URL Redirect to `sml-coming-soon.ca`. TXT records
|
||
coexist with it, so adding SPF does not disturb the redirect.
|
||
|
||
**DMARC `rua` changed** from `pouya@` to `info@smlcompany.ca` — the mailbox
|
||
confirmed to exist.
|
||
|
||
**Still blocking:** Q19 (SES production access), Q20 (the two TXT records).
|
||
|
||
---
|
||
|
||
## 2026-08-26 (g) — SES purpose clarified; D18; SPF and DMARC found missing
|
||
|
||
**Who:** Pouya asked why SES is needed given he already has an `info@` mailbox.
|
||
Fair question — the answer exposed two things.
|
||
|
||
**The distinction, recorded because it will come up again.** A mailbox receives
|
||
mail and a person logs into it. SES lets *code* send mail — the intake Lambda has
|
||
no mailbox and no login. They are complementary, not alternatives: SES sends
|
||
**to** `info@smlcompany.ca`. Verifying the address in SES did not create a
|
||
mailbox; it authorised sending.
|
||
|
||
**D18 — two emails per submission (new decision).** The sandbox blocks only one
|
||
of the two: the notification to Pouya works (his address is verified), the
|
||
**receipt to the inquirer** does not. That receipt was Claude's addition in
|
||
`docs/05-backend-spec.md`, not part of the original AWS-guide build, so it was
|
||
put back to Pouya as a real choice rather than treated as a defect. **He confirmed
|
||
he wants it** — so Q19 is genuinely blocking rather than optional.
|
||
|
||
**Q20 opened — the domain has no email authentication at all.** A DNS query of
|
||
`smlcompany.ca` on 2026-08-26 returned:
|
||
|
||
- TXT: only `anthropic-domain-verification` and `google-site-verification`.
|
||
**No `v=spf1` record of any kind.**
|
||
- `_dmarc.smlcompany.ca`: **no record.**
|
||
- MX `1 smtp.google.com` and `google._domainkey` present — Google Workspace with
|
||
DKIM configured.
|
||
- `adr.smlcompany.ca` CNAME → `d26v23dhgsp2ta.cloudfront.net`, as expected.
|
||
|
||
Old → new (planned): no SPF, no DMARC → one SPF record covering **both** Google
|
||
and Amazon SES, plus a DMARC record starting at `p=none`.
|
||
|
||
**This is wider than this project.** Pouya's existing business email from
|
||
`smlcompany.ca` is sending unauthenticated today. Google Workspace's DKIM carries
|
||
it, but Gmail and Yahoo both penalise missing SPF and DMARC, so mail he sends as a
|
||
human is already more likely to be filtered than it should be. Raised to **High**
|
||
in §10 and flagged to him directly. Both records should go in before the SES
|
||
production-access request — AWS weighs domain authentication when reviewing, so
|
||
it improves the odds of first-time approval as well.
|
||
|
||
**Opened:** Q20. **Still blocking:** Q19, Q20.
|
||
|
||
---
|
||
|
||
## 2026-08-26 (f) — SES sandbox confirmed; execution protocol built into the repo
|
||
|
||
**Who:** Pouya. Claude recording.
|
||
|
||
**Q18 closed, Q19 confirmed as a live blocker.** `smlcompany.ca` **is** verified
|
||
for sending (`true`) — the earlier `None` was a query artefact, not a fault. But
|
||
`ProductionAccessEnabled: false`: **the account is in the SES sandbox.** Mail
|
||
reaches only pre-verified addresses, so an inquirer's confirmation email fails
|
||
silently. Raised from Medium to **High** in §10: this is the failure mode where
|
||
the site looks like it works and the inquirer concludes they were ignored.
|
||
Production access must be requested; ~24 h turnaround, and it is the only
|
||
dependency on this project with external lead time.
|
||
|
||
**D17 — working method, made structural (new decision).**
|
||
- Old → new: an implicit understanding that Claude Code implements what Pouya
|
||
decides → **an explicit six-phase loop encoded in the repository**, so it
|
||
applies without being restated in each prompt.
|
||
- Why: Pouya's direction — he architects, Claude Code programs and then
|
||
adversarially reviews, with deep reasoning on, permanently.
|
||
- Added:
|
||
- `.claude/agents/adversarial-reviewer.md` — code, accessibility,
|
||
crawlability, performance, security, simplicity. Instructed to **treat
|
||
uncertainty as a defect** and told that an approving review which misses a
|
||
real defect is a failure.
|
||
- `.claude/agents/claims-auditor.md` — every factual assertion traced to §4.
|
||
Separate agent on purpose: a generic reviewer consistently under-weights
|
||
professional-conduct checks, which is this project's highest-stakes failure
|
||
mode. It also audits JSON-LD, since a machine-readable misrepresentation is
|
||
still a misrepresentation.
|
||
- `.claude/commands/build.md` — the loop. `/review` — phase 3 alone.
|
||
`/wrap` — the session-end `AGENTS.md` ritual.
|
||
- `.claude/settings.json` — thinking on, high effort, and a read-deny on
|
||
`.env*` and `aws-inventory.txt`.
|
||
- `CLAUDE.md` — the protocol and the reasoning behind it.
|
||
- `docs/08-execution-protocol.md` — the prompt template Pouya writes from.
|
||
- **The design decision worth preserving:** the reviewers are given the diff and
|
||
the specs, and deliberately **not** the implementer's rationale. Explaining why
|
||
the work is correct anchors the reviewer and converts review into agreement.
|
||
Independence is the mechanism, not a courtesy. If a future change to this
|
||
protocol removes that, it removes the value.
|
||
|
||
**Closed:** Q18. **Still blocking:** Q19 (SES production access).
|
||
|
||
---
|
||
|
||
## 2026-08-26 (e) — AWS inventory captured; Q10 closed; blast-radius risk logged
|
||
|
||
**Who:** Pouya ran `scripts/aws-discover.sh`. Claude recording.
|
||
|
||
**Q10 closed.** All identifiers in §7. Bucket `adr-smlcompany-site`,
|
||
distribution `E1OK7G98KNKUTA`, region `ca-central-1`, intake API
|
||
`4tl0m5igkj`. Certificate ISSUED. **S3 versioning is already Enabled**, so the
|
||
rollback path in `docs/06-deployment.md` works as written — no change needed.
|
||
|
||
**Data residency confirmed.** Hosting, Lambda, and DynamoDB are all in
|
||
`ca-central-1`. `docs/05-backend-spec.md` treated Canadian residency as a
|
||
selling point conditional on the table's region; it is now a verified fact and
|
||
`/legal/privacy/` can state it plainly.
|
||
|
||
**New risk logged — deploy-credential blast radius.** The inventory shows this is
|
||
a shared account across at least five unrelated properties, including
|
||
`mlp-clientdb-prod-backups-327082975128`. A Gitea runner holding a static AWS key
|
||
for this site sits in the same account as a law firm's client-database backups.
|
||
Nothing about the plan changes — the scoped IAM policy was already correct — but
|
||
its narrowness is now load-bearing rather than good practice, and that is
|
||
recorded so nobody widens it later for convenience.
|
||
|
||
**Q18 and Q19 opened — SES.** `list-email-identities` returned
|
||
`VerifiedForSendingStatus: None` for all six identities, and sandbox status was
|
||
not checked. Either condition means the intake confirmation email silently fails.
|
||
This is the failure mode where the site appears to work and inquirers think they
|
||
have been ignored, so it is on the cutover checklist, not the nice-to-have list.
|
||
|
||
**Closed:** Q10. **Opened:** Q18, Q19.
|
||
|
||
---
|
||
|
||
## 2026-08-26 (d) — Memberships, analytics, prep time, firm naming; one blocker left
|
||
|
||
**Who:** Pouya. Claude recording.
|
||
|
||
**Q16 closed — preparation time is bundled and stated.** 2 h in the half day,
|
||
3 h in the full day, printed on `/fees/`. The carried-forward assumption is now a
|
||
decision. At $4,000 a day counsel will assume preparation happened; saying so
|
||
converts the assumption into a selling point and forecloses an argument about
|
||
what the fee covered.
|
||
|
||
**Q15 and Q17 closed.** Non-mediation hourly (ENE, settlement counsel,
|
||
dispute-system design, technical advisory) and mediation overtime both **$500/h**,
|
||
matching the arbitration rate.
|
||
|
||
**Q8 closed — memberships.** Old → new: five `[assumed]` bodies from the strategy
|
||
brief → **ADRIC, ADRIO, and OBA sections, verified.** OCNI is **not current** and
|
||
must not be published; the brief listed it as aspirational positioning for the
|
||
nuclear niche, which is a different thing from a membership.
|
||
|
||
- **LSO was deliberately not offered as an option and is not published.** Listing
|
||
the Law Society in a credentials block implies licensure, which D13 bars. Worth
|
||
recording explicitly so a later reader does not "helpfully" add it back.
|
||
- Which OBA sections remains `[assumed]` — the brief names Construction &
|
||
Infrastructure, ADR, and Civil Litigation. Low stakes; confirm in passing.
|
||
|
||
**D15 — analytics (new decision).** Old → new: unchosen → **privacy-first and
|
||
cookieless**, Plausible or Fathom. No GA4, no consent banner, no personal data
|
||
leaving the site, one honest line in the privacy policy. Consistent with a
|
||
practice whose privacy posture is part of its offer, on a site where visitors are
|
||
often describing live disputes.
|
||
|
||
**D16 — the boutique is never named (new decision).** Old → new: "may be named,
|
||
name pending" → **generic throughout**: *a Toronto litigation and ADR boutique*.
|
||
Pouya reversed his earlier answer. Trade-off, recorded for the record: naming a
|
||
recognisable firm is a meaningful credibility signal to appointing bodies, and
|
||
the generic phrasing gives that up in exchange for zero coordination cost and no
|
||
dependency on anyone else's sign-off. Do not infer the name from his email domain
|
||
or from anything else.
|
||
|
||
**Closed:** Q7, Q8, Q11, Q15, Q16, Q17. **Opened:** none.
|
||
|
||
**Q10 is now the only blocker.** Everything else needed to build is answered.
|
||
R6 (booking) stays parked by choice and does not block `/contact/`.
|
||
|
||
---
|
||
|
||
## 2026-08-26 (c) — Contact, headshot, LinkedIn; booking parked
|
||
|
||
**Who:** Pouya. Claude recording.
|
||
|
||
**Closed.** Q3 — contact is `info@smlcompany.ca`, no public phone, consultations
|
||
by scheduled call. Q6 — headshot supplied; committed as
|
||
`src/assets/pouya-lajevardi.jpg` (1600×1600 master, for Astro to derive AVIF and
|
||
WebP from at build) and `src/assets/og-portrait.jpg` (1200×630, cropped high so
|
||
the face is not centred under the fold of a link preview). Q12 — LinkedIn URL,
|
||
which now feeds `sameAs` in the `Person` JSON-LD.
|
||
|
||
**Q5 parked, not closed.** Old → new: "choose a booking tool" → **deferred at
|
||
Pouya's request**; `/contact/` ships with the intake form and a reserved slot for
|
||
an embed, so adding one later is a drop-in rather than a rebuild. He asked to be
|
||
reminded, so it is now **R6** in §12 rather than a question that quietly expires.
|
||
Worth restating when it comes back up: D10 chose booking because it removes the
|
||
scheduling back-and-forth that loses appointments, and the form alone only
|
||
half-solves that.
|
||
|
||
**Q7 partially answered.** The boutique may be named. The name itself was not
|
||
given. His email domain (`meshkinilaw.ca`) points to **Meshkini Law**, but an
|
||
inferred firm name is exactly the kind of thing §4 exists to stop — asked for
|
||
confirmation rather than published.
|
||
|
||
---
|
||
|
||
## 2026-08-26 (b) — Fees confirmed; Gitea; licensure wording; standing reminders
|
||
|
||
**Who:** Pouya, answering the second round. Claude recording.
|
||
|
||
**D14 closed — rate card confirmed, and it is not what was recommended.**
|
||
- Old → new: two-tier card (Tier A insurance/SABS at $1,800/day, Tier B
|
||
commercial at $3,200/day) → **one rate for all mediation matters: $2,000 half
|
||
day, $4,000 full day, $500 per party beyond two.** Arbitration $500/h, hearing
|
||
day $4,000, documents-only flat $6,500 simple / $9,500 complex. Tribunal-
|
||
secretary line removed. Cancellation terms adopted as recommended.
|
||
- Why: Pouya's decision.
|
||
- **Recorded dissent, for the 12-month review (R5).** A single premium rate puts
|
||
the insurance / SABS / LAT segment out of reach — the published market there
|
||
runs roughly $800–$1,200 a day, and $4,000 is three to five times it. That is
|
||
the segment the strategy brief (§IV.7) identifies as the highest realistic
|
||
near-term volume, flowing directly from the firm's existing accident-benefits
|
||
work. The trade is deliberate if it is deliberate: a premium specialist
|
||
position that forgoes volume. It is a mistake if the volume was being counted
|
||
on. Flagged once, implemented as directed.
|
||
- Three parameters were not specified and are carried forward as assumptions,
|
||
logged as Q15–Q17: non-mediation hourly ($500), bundled prep hours (2 h half
|
||
day / 3 h full day), mediation overtime ($500/h).
|
||
|
||
**D13 refined — approved wording for the boutique role.**
|
||
- Old → new: "describe the role factually" → the specific approved phrases are
|
||
**"active litigation exposure"** and **"involvement in litigation and ADR
|
||
matters"**. The word **"practice"** is barred in that context.
|
||
- Pouya asked to be **continuously reminded** that this is interim. That request
|
||
is now structural rather than a note — see the new §12.
|
||
|
||
**New §12, Standing Reminders.** Five items (R1–R5) that any agent must surface
|
||
at the start of a substantial session. Added because a parked decision otherwise
|
||
becomes permanent by never being raised again — and R1 is Pouya's explicit
|
||
instruction to keep raising it.
|
||
|
||
**D3 amended again — Gitea.**
|
||
- Old → new: "private git server, software unknown" → **self-hosted Gitea with
|
||
Gitea Actions**, clone at `/Users/pouya/Dev/Websites/adr-sml`.
|
||
- Consequence: Gitea Actions uses GitHub Actions syntax, so the workflow ports
|
||
almost unchanged into `.gitea/workflows/deploy.yml`. But **Gitea is not an AWS
|
||
OIDC provider**, so the OIDC role assumption is replaced by a scoped IAM user
|
||
whose key lives only in Gitea's secret store. The IAM policy stays exactly as
|
||
narrow. Quarterly rotation is now an operational obligation that OIDC would
|
||
have made unnecessary — noted in `docs/06-deployment.md`.
|
||
|
||
**Closed:** Q4, Q9, Q13, Q14. **Opened:** Q15, Q16, Q17.
|
||
**Still open:** Q3, Q5, Q6, Q7, Q8, Q10, Q11, Q12, Q15, Q16, Q17.
|
||
|
||
---
|
||
|
||
## 2026-08-26 (a) — Licensure decision; Q.Arb dated; git host changed; fees researched
|
||
|
||
**Who:** Pouya, answering the blocking questions from §9. Claude recording.
|
||
|
||
**Date correction.** The entry below is stamped 2026-08-25. The correct date of
|
||
that work was **2026-08-26** — the session clock was a day behind. Per rule 3 the
|
||
entry is left as written rather than edited; this note is the correction. Facts
|
||
touched today are re-stamped `[verified 2026-08-26]`.
|
||
|
||
**D13 — licensure left out of the site (new decision).**
|
||
- Old → new: "confirm LSO licence status before launch" → **the site asserts the
|
||
JD and makes no licensure claim at all.**
|
||
- Why: Pouya's direction.
|
||
- **Consequence, and it is not small.** The strategy brief describes an *"active
|
||
litigation practice in personal injury, construction, regulatory (POA), and
|
||
insurance (SABS) matters."* Copy written that way would imply entitlement to
|
||
practise law without stating it — which is the risk the decision is meant to
|
||
avoid, restated in different words. So the Forbidden table now bars implication
|
||
as well as assertion, and the About page describes the role factually:
|
||
*Director of Firm Operations at a Toronto litigation and ADR boutique*, plus
|
||
the matter types worked on. **Flagged back to Pouya**: if he is in fact
|
||
licensed and in good standing, that is a material credential for exactly the
|
||
audience this site targets, and omitting it costs more than it protects.
|
||
|
||
**Q.Arb dated.** Old → new: `[assumed]`, stage unknown → **commenced August
|
||
2026** `[verified 2026-08-26]`. Describe as newly commenced. Not as held, not as
|
||
nearing completion.
|
||
|
||
**D3 amended — the repository is not on GitHub.**
|
||
- Old → new: "git repo + GitHub Actions" → **repo `adr-sml` on a private git
|
||
server**; the GitHub Actions workflow in `.github/workflows/` is retained as a
|
||
working reference implementation, to be translated once the server software is
|
||
known (**Q13**).
|
||
- Why: Pouya is running his own git server.
|
||
- Knock-on: GitHub's OIDC provider is unavailable. GitLab CE can federate to AWS
|
||
by OIDC; Gitea/Forgejo and bare git cannot, so those need a scoped IAM user
|
||
with rotated keys, or deploys run from Pouya's machine. The choice is real and
|
||
waits on Q13.
|
||
|
||
**D14 — fee structure recommended (new decision, pending sign-off).** Market
|
||
research completed against the Ontario mandatory-mediation tariff, ADR Chambers
|
||
published ranges, and four published Ontario practitioner rate cards. A two-tier
|
||
structure is recommended so the price-sensitive SABS/LAT volume work does not
|
||
anchor the commercial rate. Figures are in the response to Pouya and are **not
|
||
written into any page until he signs off (Q14).**
|
||
|
||
**Still open:** Q3, Q5, Q6, Q7, Q8, Q10, Q11, Q12, Q13, Q14.
|
||
|
||
---
|
||
|
||
## 2026-08-25 — Project initiated; architecture decided; repo bundle authored
|
||
|
||
**Who:** Pouya Lajevardi with Claude (Cowork session), acting as architects. Claude Code to implement.
|
||
|
||
**What was discussed.** Pouya asked for a modernization of `adr.smlcompany.ca`
|
||
going beyond appearance — content and codebase included — with Claude Code doing
|
||
the implementation and deploying to AWS.
|
||
|
||
**What was found.** An audit of the live site and the local sources established
|
||
the facts in Current Truth §2. The headline finding: the site is a browser-
|
||
compiled single-file React bundle that serves crawlers three words of content.
|
||
For a personal-brand site whose function is discoverability, this is the
|
||
dominant problem, ahead of any question of looks or copy.
|
||
|
||
**What was decided.** Twelve decisions, D1–D12, recorded in §3. In summary: an
|
||
Astro static rebuild, full content re-architecture, ~20 pages, English only,
|
||
git + GitHub Actions onto the existing S3/CloudFront, palette and infinity mark
|
||
retained with a modernized execution, a published rate card, an Insights section
|
||
launching with drafted content, a rebuilt intake form plus booking, and a single
|
||
clean cutover.
|
||
|
||
- Old → new (framework): browser-compiled React single file → Astro static site
|
||
- Old → new (publishing): manual `rebuild-standalone.py` + console upload → git + GitHub Actions with OIDC
|
||
- Old → new (structure): one scrolling page → ~20 pre-rendered pages
|
||
- Old → new (content): partially-corrected placeholder template → written fresh against a claim register
|
||
- Old → new (record-keeping): none → this file, under the AGENTS constitution
|
||
|
||
**Why.** Discoverability is the practice's growth constraint and the current
|
||
architecture forecloses it. Every other decision follows from fixing that, with
|
||
the content decisions following from the strategy brief of 2026-05-26.
|
||
|
||
**Also decided, not yet discussed with Pouya:** no Indigenous engagement practice
|
||
page at launch (§6), on the reasoning recorded there. Flag this to him.
|
||
|
||
**Planned, not yet done.** Astro implementation; all page copy; 3–5 Insights
|
||
drafts; intake backend rework; CI/CD wiring; pre-cutover audit. Twelve blocking
|
||
questions are open in §9 — several pages cannot be written until they are
|
||
answered.
|
||
-- src docs | grep -B1 progress
|
||
src/pages/about.astro: * ...which ended "...stated openly as in
|
||
src/pages/about.astro- * progress" — so THIS FILE cited docs/03 as REQUIRING...
|
||
-> the one hit is the corrective note itself. THE WRAPPED FORM IS WHY THIS
|
||
SWEEP MISSED FIRST TIME: 'as in\n * progress' does not match a one-line
|
||
grep, and about.astro cited docs/03 as both requiring and barring the
|
||
phrase, six lines apart.
|
||
|
||
$ git grep -n 'worksFor' -- src | grep -cv '\*\|//'
|
||
0
|
||
-> ZERO live properties. 13 lines mention it, all comments.
|
||
THE FIRST VERSION OF THIS BLOCK REPORTED "3 hits" — which was the number of
|
||
FILES 'git grep -c' printed, read as a number of matches. The instrument
|
||
shape CLAUDE.md catalogues, in the entry documenting instrument misreads.
|
||
|
||
$ git grep -n 'NoSuchEntity|does not exist yet|has not been created|nobody owns that' -- README.md docs/
|
||
-> 2 hits, both inside the corrective notes added this session.
|
||
THIS SWEEP DID NOT EXIST IN THE FIRST VERSION OF THIS BLOCK, and that was
|
||
the gap: Q22's flip to PROVISIONED was swept in AGENTS.md and NOWHERE ELSE.
|
||
docs/06 still told an operator "adr-sml-deploy does not exist… Create it",
|
||
and README asserted the same in three places. An operator would have
|
||
created a SECOND IAM user, or hand-provisioned one outside the
|
||
least-privilege policy. Same shape as the SES-DKIM inversion; found by
|
||
adversarial-reviewer.
|
||
|
||
$ git show :docs/reference/adrio-designations.md | grep '^## Finding 4'
|
||
-> matches the working tree. THE STAGED COPY HAD THE FALSIFIED FINDING 4:
|
||
the file was 'git add'ed BEFORE the rewrite, so a staged-only commit would
|
||
have landed the version this entry claims to have fixed. The mirror of the
|
||
untracked-file hazard recorded above — once tracked, 'commit -a' works and
|
||
bare 'commit' does not. Verify with 'git diff --cached' before committing.
|
||
```
|
||
|
||
**Line-wrapping defeated an anchor or a sweep THREE times this session** — S5's
|
||
`as in\n * progress`, the `SiteFooter` masthead sentence, and `docs/03`'s
|
||
blockquote-wrapped phrase recorded in an earlier entry. Sweep the wrapped form.
|
||
|
||
### Verified
|
||
|
||
`astro check` **0 / 0 / 0**; `eslint` clean; `prettier --check` clean (noting
|
||
`.prettierignore` excludes `*.md` and `docs/reference/`, so it says nothing about
|
||
the new doc); `npm run build` 2 pages; **0 `.js` emitted**; the only `<script>`
|
||
on either page is `application/ld+json`; minifier guard silent and
|
||
`animation-timeline` intact in `dist` (longhands only; the sole `animation:`
|
||
shorthand is `animation:none!important` in the reduced-motion block); **no gold
|
||
text on cream** anywhere; one `<h1>` on `/about/` with h1→h2→h3 and no skips
|
||
across 17 headings; JSON-LD parses on both pages with `jobTitle: "Mediator"`, no
|
||
`worksFor`, no `memberOf`, `hasCredential` Q.Med-only, no `LegalService`; **no
|
||
currency-warranty phrasing in the built HTML** (`renewed annually`,
|
||
`listed as current`, `current as of`, `are current` — all 0).
|
||
|
||
Layout re-measured by `adversarial-reviewer` after it discarded its own first
|
||
instrument: **headless Chrome clamps `--window-size` to ~500px minimum on
|
||
macOS**, so its "320px" was really 500px. Via CDP `setDeviceMetricsOverride`:
|
||
320×800 DPR2, 1024 and 1280 → **0 document overflow**; at 320px with root
|
||
font-size 32px → 63px, **all of it the pre-existing header brand name**, with
|
||
every credential `<li>` right edge at 272 against a 320 viewport. The new
|
||
Memberships group contributes no overflow.
|
||
|
||
### NOT run, stated rather than omitted
|
||
|
||
- **Lighthouse — tool unavailable.** `@lhci/cli` removed 2026-08-26; returns at
|
||
step 7 under R11. Nothing here adds bytes to a route: no new images, no runtime
|
||
font request, no third-party script, no base64 inlining, JS still zero.
|
||
- **HTML validator — not run.** The duplicate-`1x` srcset conformance error from
|
||
step 2 stands.
|
||
- **Q46(a)'s gate 1 — no source fetched.** Deliberate: it is legal research, it
|
||
was not asked for, and §4 bars this register from concluding it. The candidate
|
||
source is named in the ENE row.
|
||
|
||
### Open after this entry
|
||
|
||
**Q46(a)** (gate 1 unsourced — blocks step 5) · **Q48** (Q.Med retention vs
|
||
membership currency) · **Q49** (the two §4 rows Q47 needs) · **Q50**
|
||
(`ProfessionalService.name` scoping) · **Q51** (OBA and the D13 implication) ·
|
||
**Q23**, **Q34**, **Q38**. Live reminders: **R1** (licensure — surfaced again,
|
||
and `/about/` is now the page that makes it live), **R10** (event-triggered),
|
||
**R11**, **R13**, **R14**, **R15**, **R16** (PDF bio, step 9), **R17** (key
|
||
rotation, 2026-11-26).
|