feat: build step 3 — /about/, minus its memberships; close Q40–Q43
Build and deploy / build-and-deploy (push) Failing after 6s

Applies Pouya's rulings on Q42, Q41(a)(b)(c), Q43 and Q40, then builds
`/about/` — six of docs/01's seven items.

`/about/` ships WITHOUT a memberships group. R10 is a prohibition on
shipping a page that lists memberships before they are re-confirmed; the
re-confirmation is a fact only Pouya holds and was not obtained. The
first version published all four and disclosed the gap in five places
instead; both review agents rejected that. Q44 carries the question.

Rulings:
- Q42 — ENE, dispute-system design and pre-dispute technical advisory
  rowed; settlement counsel struck as a partisan role. The strike
  exposed a hole in the offering test, which now states the prior
  question it was missing.
- Q41(a) — Q37 reaches prose, and prose is held to a higher bar. The
  sentence is now one constant, ASYMMETRY_LINE, because two hand-typed
  copies had already diverged inside one session.
- Q41(b) — not restored; the implication turned out to be in three
  places, two of which survived the sweep that closed it.
- Q41(c) — verified against the LAT's own Rules and extracted into
  docs/reference/lat-case-conference.md. Rule 2.4 makes "Pre-Hearing
  Conference" the Tribunal's own term for a case conference; the Rules
  contain zero occurrences of `mediat` in 66,593 characters.
- Q43 — the timings are service commitments; PROCESS_FRAMING renders
  adjacent to them, not in a lede above.
- Q40 — bundled to step 7 as R15, blocking cutover.

Four review passes, 43 findings, nine of them defects in their own
predecessors' fixes. The worst was mine: the false universal Q39 struck
reached a public page. Also fixed a portrait ladder that upscaled 1.93x
at 1024/DPR2 on BOTH pages — the shipped home page included — because
its 960 ceiling was derived from the layout range where the image is
narrowest.

Verified: check/lint/build/audit clean; 0 upscaling across 11 device
profiles; 0 overflow and 0 over-wide elements at 13 widths; 0 contrast
failures across 127 and 88 painted pairs; 0 print failures against white
paper; reveal 0 hidden under reduced-motion and print; zero JavaScript.
Lighthouse NOT RUN — tool unavailable until step 7 (R11). HTML validator
NOT RUN.

Opens Q44 (memberships), Q45 (PDF bio), Q46 (offering-test gating; the
glossary standard), Q47 (jobTitle without worksFor). Adds R15.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0148NztQskLKKApP5SzAA78e
This commit is contained in:
Pouya Lajevardi
2026-08-28 12:10:41 -04:00
co-authored by Claude Opus 5
parent 165d259f5c
commit c576b9a85f
17 changed files with 2603 additions and 147 deletions
+180
View File
@@ -0,0 +1,180 @@
# Reference — how the Licence Appeal Tribunal actually runs its pre-hearing step
**Why this file exists.** `AGENTS.md` Q41(c) asked what `LAT pre-hearing
mediation` means as an offering. Pouya's ruling of 2026-08-27: *"'LAT pre-hearing
mediation' is imprecise and must not imply appointment by the tribunal. Verify
against LAT's own materials how its case-conference process is conducted and who
conducts it."* This is that verification, committed rather than cited, under
`CLAUDE.md`'s rule that anything a spec makes a claim about must be reachable
from the repository (R14).
---
## Provenance — read this before quoting anything below
| | |
|---|---|
| Source 1 | `https://tribunalsontario.ca/documents/lat/LAT-Rules.html`*Licence Appeal Tribunal, Animal Care Review Board and Fire Safety Commission Rules of Practice and Procedure*, effective July 21, 2023 |
| Source 2 | `https://tribunalsontario.ca/lat-aabs/application-and-hearing-process/` — LATAABS, *Application and hearing process* |
| Retrieved | **2026-08-28** |
| Method | `curl -sS -o <file> '<url>'` — HTTP **200** both; **88,429 B** (rules) and **107,996 B** (AABS page) |
| Text extraction | script/style stripped, tags stripped, entities unescaped, whitespace collapsed → **66,593** and **33,696** characters |
> ⚠️ **NO HASHES, AND THE REASON IS THE POINT.** This table carried `sha256`
> prefixes `07d9c077e41cc8bd` and `08eff9a73b683cc5`. They are removed because
> **they cannot be reproduced, and a stamp that cannot be re-checked is worse
> than no stamp** — a future reader who re-fetches and gets a different digest
> would conclude the source had changed when it had not.
>
> Found by `adversarial-reviewer`, which re-fetched both URLs and got two
> different digests, then two more on two further fetches. Cause isolated by
> diffing consecutive responses: `LAT-Rules.html` carries a per-request
> bot-detection nonce (`__uzdbm_1`, `__uzdbm_2`), and the AABS page carries
> rotating WordPress `?ver=` cache-busters. **The sha256 of these URLs is not a
> stable quantity.**
>
> What *does* reproduce, and was independently reproduced: **both byte counts
> exactly**, **all ten verbatim quotes** with their rule numbers and headings, and
> **all four term counts**. So the substance of this file is verified twice over;
> only the hashes were spurious. Same family as the `1.23:1` bounding box and the
> `timeout 60 ls` in `CLAUDE.md` — a number that looks like verification, from a
> probe nobody validated.
**Instrument check, because `CLAUDE.md` requires one.** The word counts below were
taken from the **raw fetched bytes**, not from a `WebFetch` answer. `WebFetch`
answers through a summarising model, so a "quote" it returns may be a paraphrase
— and the first pass here did return a plausible-looking Rule 14.4 quote
(*"The case conference is an important opportunity to discuss settlement"*) that
turned out to be **correct**, and a Rule 14.6 gloss that was **not** how the rule
reads. Both were then checked against the literal text. Quotes in this file are
literal; where the two disagreed the literal text won.
A second instrument note: the rules document repeats every heading in a table of
contents before the body, so a naive "find the heading" extraction returns the
**TOC** and reports the rules as empty. The bodies are present, ~35 KB further in.
---
## Finding 1 — the LAT's settlement step is a *case conference*, and a Tribunal Member conducts it
**Rule 2.4, verbatim:**
> "Case Conference" has the same meaning as "Pre-Hearing Conference" as defined
> in the SPPA.
So **"pre-hearing" is the LAT's own term, and what it names is a case
conference** — not a mediation.
**Rule 14.2 — Scope of case conference subject matter, verbatim opening:**
> The Tribunal may on its own initiative, or in response to a party's written
> request, direct the parties to participate in a case conference to consider:
> The settlement of any or all of the issues; […]
**Rule 14.3 — Member not to participate on a hearing panel, verbatim:**
> A Member who presides at or otherwise takes part in a case conference shall not
> participate as a Member of a panel at a subsequent hearing of the appeal except
> with the consent of the parties.
**Rule 14.4 — Settlement discussions, verbatim:**
> The case conference is an important opportunity to discuss settlement of the
> issues without the need for a hearing. The parties are expected to come to the
> case conference prepared to discuss settlement.
>
> All settlement discussions in a case conference and the documents put forward
> solely for the purpose of settlement are confidential. Settlement discussions
> are held on a "without prejudice" basis. Settlement discussions shall not be
> communicated to the Member that participates in the hearing or otherwise be
> relied on in a hearing before the Tribunal for any purpose unless the parties
> consent.
**Rule 14.6 — Party attendance, verbatim first sentence:**
> A party as defined under Rule 2.16 must attend their case conference.
**Rule 12 — Format, verbatim:**
> In accordance with applicable provisions of the SPPA, the Tribunal may hold a
> hearing or case conference in any of the following formats, as it considers
> appropriate: In-person; Electronic; Written; or Any combination of the above.
The public LATAABS page adds, of the same step: *"A case conference is led by an
adjudicator whose role is to guide and support the parties in working to resolve
the dispute."*
**Consequence:** the neutral in the LAT's pre-hearing step is a **Member /
adjudicator of the Tribunal**. It is directed by the Tribunal, attendance is
mandatory, and the Member is disqualified from the subsequent hearing panel. A
privately retained neutral is not appointed to it and cannot be.
## Finding 2 — the LAT Rules never use the words "mediation", "mediator" or "arbitration"
Counted on the literal extracted text, case-sensitively for both cases:
```
lat-rules.html 66,593 chars 'mediat' 0 'Mediat' 0 'arbitrat' 0 'Arbitrat' 0
lat-aabs.html 33,696 chars 'mediat' 1 'Mediat' 0 'arbitrat' 0 'Arbitrat' 0
```
**Zero** in the Rules. There is no rule providing for the Tribunal to appoint an
external mediator, and no rule about a party retaining a private neutral —
because the Rules do not contemplate the concept at all.
## Finding 3 — the single match, read rather than counted
`CLAUDE.md`: *a grep that matches is not a finding until you read what it
matched.* The one `mediat` on the AABS page, printed with its heading, is this —
and it is the affirmative basis for the offering rather than a problem for it:
> **4. Consider other ways to resolve your dispute**
>
> Before you apply to the LATAABS, you may want to consider negotiation or
> mediation services. Parties are encouraged to attempt to negotiate the claim
> at all times, including before filing at the LATAABS, and continuing
> negotiation discussions after a claim has been filed.
The Tribunal itself points parties at private mediation, **before filing and
continuing after filing.** That is exactly the space a privately retained
mediator occupies, and it is the Tribunal's own words for it.
---
## What this establishes, and what it does not
**Establishes:**
1. The LAT's pre-hearing settlement step is a **case conference conducted by a
Tribunal Member**. `LAT pre-hearing mediation` therefore describes a thing
that does not exist, and the half a reader would recognise — *pre-hearing*
is the Tribunal's own label for a step nobody outside the Tribunal conducts.
2. Private mediation of accident-benefits and SABS disputes is **compatible with
a LAT application, before filing or after**, and the Tribunal says so.
**Does not establish:**
- Anything about whether Pouya holds a roster position with the LAT or Tribunals
Ontario. Nothing here bears on that. §4 has no such row, so the site claims
none — per Pouya's ruling: *"If Pouya holds a roster position that makes more
than that true, it is a §4 addition — absent a row, it isn't."*
- Anything about *commercial* arbitration gating. Same caution as
`ontario-family-arbitration-training.md`: a source about one process is not
authority about another. These documents do not mention arbitration at all.
## The wording that follows from it
**Never publish** `LAT pre-hearing mediation`, or any phrasing in which a LAT
proceeding appears to appoint or host the mediator.
**Published instead**`src/data/site.ts`, `PRACTICE_AREAS``insurance`:
> Accident benefits and SABS entitlement, MIG disputes, and private mediation
> alongside a LAT application, before filing or after.
`docs/01` keeps `LAT pre-hearing mediation` as a **search intent** — people do
type it — with a note that it must never be lifted into copy. That lift is
exactly what happened once already.
`/practice/insurance/` at build step 5 must state that the mediation offered is
**private**, retained by the parties, and **not the Tribunal's case conference**.