feat: build step 3 — /about/, minus its memberships; close Q40–Q43
Build and deploy / build-and-deploy (push) Failing after 6s
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
co-authored by
Claude Opus 5
Claude Opus 5
parent
165d259f5c
commit
c576b9a85f
+68
-3
@@ -134,7 +134,10 @@ four audiences to its surface.
|
||||
2. **Credential row.** Three slots: `Q.Med` · `JD + ML` · `EN · FA`. Never
|
||||
matter counts — `AGENTS.md` §4.
|
||||
3. **The approach.** The "two directions at once" argument — law and engineering
|
||||
converging on the same dispute. Infinity mark as the visual anchor.
|
||||
converging on the same dispute. ⚠️ **The noun pair "law and engineering" is
|
||||
the construction Q37 struck and Q41(a) extended to prose. The argument
|
||||
stands; do not lift the phrase into copy** — it reached `/` once already.
|
||||
State the asymmetry instead: `docs/03` §The credential row. Infinity mark as the visual anchor.
|
||||
4. **Two practices.** Mediation and Arbitration cards → `/mediation/`, `/arbitration/`.
|
||||
Med-Arb named here as the long-term arc, linking to `/med-arb/`.
|
||||
5. **Practice areas.** Six-card grid → `/practice/*`. This is the most important
|
||||
@@ -173,6 +176,17 @@ to an appointment. This page carries the verifiable record.
|
||||
7. `Person` JSON-LD. Downloadable one-page PDF bio — brief §VIII lists this as
|
||||
an asset for circulation with appointment proposals.
|
||||
|
||||
> **The PDF bio does NOT ship with build step 3, and the omission is stated
|
||||
> rather than silent** — `AGENTS.md` Q45, opened 2026-08-28. No such file exists
|
||||
> in the repo, and a link to one that does not exist is a broken link on the
|
||||
> page an appointing body reads. It is also not a formatting job: a one-page bio
|
||||
> is a **credential document** whose every line has to trace to §4 exactly as a
|
||||
> web page does, and it will be circulated detached from the site, where no
|
||||
> reviewer sees it again. Two decisions are Pouya's — whether it is generated at
|
||||
> build (a dependency, against R11) or authored once as a designed artefact, and
|
||||
> whether it carries anything the site does not. Everything else on this page
|
||||
> ships.
|
||||
|
||||
### `/mediation/`
|
||||
|
||||
**Job:** convert counsel who have already decided on mediation and are choosing a
|
||||
@@ -232,8 +246,23 @@ long-term narrative.
|
||||
### `/practice/` — index
|
||||
|
||||
Six cards, one paragraph each, linking onward. Also the natural home for the
|
||||
"also offered" strip: early neutral evaluation, settlement counsel, dispute-
|
||||
system design, and pre-dispute technical advisory.
|
||||
"also offered" strip: **early neutral evaluation, dispute-system design, and
|
||||
pre-dispute technical advisory** — three, and each now has an `AGENTS.md` §4
|
||||
Offerings row, which is what the strip needs before it may ship.
|
||||
|
||||
> **`settlement counsel` IS STRUCK FROM THIS STRIP AND MUST NOT BE RESTORED.**
|
||||
> `AGENTS.md` Q42, 2026-08-27. Pouya struck it as his own error in this document:
|
||||
>
|
||||
> > "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 which objection comes first. This is not primarily a compliance problem —
|
||||
> it is a **positioning** problem, and it would have been wrong on a site with
|
||||
> no licensure question at all. The compliance half is the aggravation, not the
|
||||
> reason. Never priced, never offered, never listed: it is a struck row in §4
|
||||
> Offerings so that a later reader finds the decision rather than the gap.
|
||||
|
||||
### `/practice/construction/`
|
||||
|
||||
@@ -275,6 +304,35 @@ a claim of existing volume.**
|
||||
**Search intent:** `SABS mediation`, `LAT pre-hearing mediation`,
|
||||
`accident benefits mediator Ontario`, `MIG dispute`.
|
||||
|
||||
> ⚠️ **`LAT pre-hearing mediation` IS A SEARCH INTENT AND NOTHING ELSE. It must
|
||||
> never be published as an offering** — `AGENTS.md` Q41(c), closed 2026-08-27,
|
||||
> verified 2026-08-28 against the Tribunal's own materials and extracted into
|
||||
> **`docs/reference/lat-case-conference.md`**. It reached `src/data/site.ts` as a
|
||||
> service blurb once already; this note exists because a search-intent list is
|
||||
> where that lift starts.
|
||||
>
|
||||
> What the verification found, in one line each:
|
||||
>
|
||||
> - **LAT Rule 2.4:** *"'Case Conference' has the same meaning as 'Pre-Hearing
|
||||
> Conference' as defined in the SPPA."* **"Pre-hearing" is the Tribunal's own
|
||||
> label**, and what it labels is a case conference.
|
||||
> - **Rule 14.3:** a **Member** presides and is then disqualified from the
|
||||
> hearing panel; **Rule 14.6:** parties must attend. The neutral is the
|
||||
> Tribunal's. A privately retained one is not appointed to it and cannot be.
|
||||
> - The LAT Rules contain **zero** occurrences of `mediat` or `arbitrat` —
|
||||
> 0 in 66,593 characters. The concept is not in them.
|
||||
> - The LAT-AABS page itself, though, says: *"Before you apply to the LAT-AABS,
|
||||
> you may want to consider negotiation or mediation services… including before
|
||||
> filing at the LAT-AABS, and continuing… after a claim has been filed."*
|
||||
> **That is the affirmative basis for the offering, in the Tribunal's words.**
|
||||
>
|
||||
> **The page must state that the mediation offered is PRIVATE, retained by the
|
||||
> parties, and is not the Tribunal's case conference.** Published blurb:
|
||||
> *"Accident benefits and SABS entitlement, MIG disputes, and private mediation
|
||||
> alongside a LAT application, before filing or after."* If Pouya holds a roster
|
||||
> position that makes more than that true, it is a §4 addition — absent a row,
|
||||
> it is not.
|
||||
|
||||
Highest realistic near-term volume — it flows directly from the existing
|
||||
personal-injury and SABS work, and brief §IV.7 notes the segment is
|
||||
underserved by senior mediators. Unglamorous and worth doing well.
|
||||
@@ -319,6 +377,13 @@ and framing (1–7) · pre-session exchange (7–21) · the session (21–30) ·
|
||||
conclusion (30+). Also: conflicts checking, confidentiality, and what happens if
|
||||
a matter does not settle.
|
||||
|
||||
**The timings are published as the TYPICAL shape of an engagement, explicitly
|
||||
not a guarantee** — `AGENTS.md` Q43, Pouya 2026-08-27. Render `PROCESS_FRAMING`
|
||||
(`src/data/site.ts`) **adjacent to the steps**, on this page and on `/`. The
|
||||
numbers above are unchanged; what is required is that they never appear
|
||||
unframed. *"Published as typical, they are honest and useful; published as
|
||||
commitments, the first matter that slips makes the page false."*
|
||||
|
||||
### `/fees/`
|
||||
|
||||
**Unblocked — `AGENTS.md` Q4/Q14 answered (D14). Build from the confirmed card
|
||||
|
||||
@@ -231,7 +231,34 @@ Not a polish pass. A build requirement.
|
||||
|---|---|---|
|
||||
| as first built | 234 px | 304 px |
|
||||
| `minmax(min(Nrem, 100%), 1fr)` on three grids | 83 px | 153 px |
|
||||
| `.credentials` made explicit `repeat(2, minmax(0, 1fr))`; `.feature` padding clamped and `overflow-wrap: anywhere` on its title; `.contact-action` `flex: 0 1 auto` + `min-inline-size: 0` | **3 px** | **65 px** |
|
||||
| `.credentials` made explicit `repeat(2, minmax(0, 1fr))`; `.feature` padding clamped and `overflow-wrap: anywhere` on its title; `.contact-action` `flex: 0 1 auto` + `min-inline-size: 0` | **3 px** | **63 px** |
|
||||
|
||||
**`65 px` corrected to `63 px` on 2026-08-28**, re-measured independently on
|
||||
the same page and setting. Two pixels, and it is recorded because a table that
|
||||
reads as the site-wide record has to be re-measurable rather than remembered.
|
||||
|
||||
**`/about/` added 2026-08-28** — step 3, and the first page to be measured
|
||||
against this table rather than establishing it:
|
||||
|
||||
| Page and fix | 390 px | 360 px | 320 px |
|
||||
|---|---|---|---|
|
||||
| `/about/` as first built | 38 px | 68 px | 108 px |
|
||||
| `.designation-part` `white-space: nowrap` removed (the separator is held by an NBSP instead) and `overflow-wrap: anywhere` on `.hero-h` | **0 px** | **23 px** | **63 px** |
|
||||
|
||||
Two findings from that page specifically. The `nowrap` was **introduced as a
|
||||
fix** for an orphaned `·` at the end of a wrapped line, and it made the whole
|
||||
designation item unbreakable — a fix that created a reflow regression, caught
|
||||
only because this table existed to regress against. And **the type scale is
|
||||
rem-based**, so an `<h1>` at `--text-5xl` computes to 88 px at root 32 and a
|
||||
single unbreakable 9-character name ("Lajevardi") exceeds the 224 px content
|
||||
box at 320 px; `overflow-wrap: anywhere` is the only remedy that reduces
|
||||
min-content size. `/about/` now measures equal to or better than `/` at all
|
||||
three widths, and its 320/360 residual is the same header decision.
|
||||
|
||||
Command, so the numbers are re-runnable rather than quoted: headless Chrome
|
||||
over the built `dist`, `document.documentElement.style.fontSize = '32px'`, then
|
||||
`documentElement.scrollWidth - documentElement.clientWidth`, plus an
|
||||
enumeration of every element wider than `clientWidth` to name the offender.
|
||||
|
||||
Two things worth keeping. **`overflow-wrap: break-word` permits a break at
|
||||
layout time but does not reduce min-content size** — `anywhere` does, and that
|
||||
|
||||
+81
-3
@@ -85,13 +85,32 @@ Reused, adapted, across the hero, the About page, and the PDF bio:
|
||||
> The dispute resolution practice of Pouya Lajevardi — a credentialed neutral
|
||||
> who is also close to live litigation and a practising machine-learning and
|
||||
> infrastructure engineer. Built for commercial, construction, energy,
|
||||
> technology, and cross-cultural disputes that turn on facts most neutrals take
|
||||
> on faith: the contract, the code, the engineering documents, and the
|
||||
> regulatory overlay around them.
|
||||
> technology, and cross-cultural disputes that turn on the contract, the code,
|
||||
> the engineering documents, and the regulatory overlay around them.
|
||||
|
||||
Every version of this must survive the §4 check. It does: each element is
|
||||
verified.
|
||||
|
||||
**AMENDED 2026-08-27 — `AGENTS.md` Q41(b). The statement read *"disputes that
|
||||
turn on facts most neutrals take on faith: the contract…"* and the comparative
|
||||
is struck.** It was not restored, and Pouya gave two reasons, the second of
|
||||
which is the one to remember:
|
||||
|
||||
> "That is an unverifiable empirical claim about other practitioners, and
|
||||
> comparative claims must be factual and verifiable. **It is also weaker copy:
|
||||
> assert his capability, not the field's incapability.** Rewrite to claim only
|
||||
> about himself — 'built for disputes that turn on the contract, the code, and
|
||||
> the engineering documents'. Same force, nothing to defend."
|
||||
|
||||
So the compliance objection and the editorial objection point the same way.
|
||||
The checklist item below — *"any comparative claim is factual and verifiable"* —
|
||||
had been overridden in practice by the fact that this paragraph was **approved
|
||||
copy**, which is how an unverifiable claim ends up inside the document that
|
||||
forbids it. The approved copy is what changed.
|
||||
|
||||
**This is now the ONLY sanctioned form of the statement.** Any earlier draft
|
||||
carrying the comparative is superseded, wherever it is quoted.
|
||||
|
||||
## Approved headline options
|
||||
|
||||
From the content brief; all three sit honestly with the practice.
|
||||
@@ -124,6 +143,37 @@ invited the reader to supply the symmetry, and for "Law" the missing half is a
|
||||
licence — which D13 bars by implication as hard as by assertion. The replacement
|
||||
is longer and deliberately lopsided. Do not tidy it back into a parallel.
|
||||
|
||||
**AND THE RULE IS NOT SCOPED TO THIS LABEL — `AGENTS.md` Q41(a), Pouya
|
||||
2026-08-27.** Q37 was asked about a credential label; the reasoning applies to
|
||||
every surface, prose included:
|
||||
|
||||
> "Yes, Q37's reasoning reaches prose. 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.**"
|
||||
|
||||
Read the second half carefully, because it sets a **higher** bar for prose, not
|
||||
a looser one. Deleting the parallel is only half the job — a reader can still
|
||||
supply the missing symmetry from silence. Prose has room to say which half is
|
||||
which, so it must. Naming the legal half as **training** is what makes the licence
|
||||
implication impossible rather than merely absent.
|
||||
|
||||
**THE SENTENCE IS A CONSTANT, NOT COPY TO BE RETYPED** — `ASYMMETRY_LINE` in
|
||||
`src/data/site.ts`:
|
||||
|
||||
> "The two halves are not the same kind of thing, and the asymmetry is the honest
|
||||
> part. A law degree on one side. A working engineering practice on the other.
|
||||
> One is training I hold. The other is work I still do."
|
||||
|
||||
It lives beside `ROLE` for the reason that file gives: *"these are the two where
|
||||
the wording IS the compliance."* This paragraph previously quoted it inline and
|
||||
cited it as living at "`/`, §The approach" — and by then it had been typed into
|
||||
`/about/` too, so there were **three copies and two of them had already
|
||||
diverged**: a comma here and on `/`, full stops on `/about/`, all inside the
|
||||
session that wrote them. Consume the constant on any page that needs the
|
||||
sentence. Do not retype it, do not paraphrase it, and do not quote a variant of
|
||||
it in a spec.
|
||||
|
||||
Fourth slot where the layout has one: **Q.Arb — commenced August 2026.** Use
|
||||
that wording, not "in progress": §4 pins it, and the weaker form drifts toward
|
||||
"nearly complete", which §4 Forbidden bars outright.
|
||||
@@ -151,6 +201,14 @@ Hero headline from the approved list. Positioning paragraph above. CTAs:
|
||||
dispute — and keeps the infinity metaphor: *disputes are loops; the work is
|
||||
redrawing the loop into a line.* First person: "my mark", not "our mark".
|
||||
|
||||
> ⚠️ **"law and engineering" IS THE STRUCK CONSTRUCTION. Do not lift this
|
||||
> sentence into copy.** The *argument* it names is Pouya's and stands; the noun
|
||||
> pair carrying it is what Q37 struck and Q41(a) extended to prose. It reached
|
||||
> the page once already, as *"Law and engineering are not blended here"* — the
|
||||
> struck parallel relocated from the credential label into body copy, one day
|
||||
> after it was struck, and strengthened by attributing both halves to him
|
||||
> personally. A spec phrase describing an argument is not approved copy.
|
||||
|
||||
### About
|
||||
400–600 words of narrative, then structured credentials. Tell the three tracks
|
||||
as one arc, not three lists: a JD and active litigation exposure; a parallel
|
||||
@@ -187,6 +245,26 @@ neither.
|
||||
Five steps with real timing. Say what happens if the matter does not settle —
|
||||
counsel want to know the downside shape before they commit a client's day.
|
||||
|
||||
**AMENDED 2026-08-27 — `AGENTS.md` Q43, and it overrides this section's previous
|
||||
reading.** "Real timing" was being read as *barring* the word "typical", which
|
||||
is why the step-2 build shipped the five timings as bare numbers and escalated
|
||||
the question instead of framing them. Pouya ruled the other way:
|
||||
|
||||
> "The five process timings are **service commitments, 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: the **numbers do not change** — softening them was never the fix and
|
||||
inventing them was never on. What "real timing" bars is a *vague* timing
|
||||
("promptly", "in a matter of weeks"), not an honest statement of what the
|
||||
numbers are. The framing is `PROCESS_FRAMING` in `src/data/site.ts` and it is
|
||||
**not optional**: every page that renders the steps renders it, 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.
|
||||
|
||||
### Fees
|
||||
**Unblocked — Q4/Q14 answered, D14.** Build from the confirmed card in
|
||||
`docs/07-fees.md`. Plain table, no "starting from"
|
||||
|
||||
+28
-3
@@ -66,9 +66,34 @@ twitter:card summary_large_image
|
||||
robots index,follow — except /legal/* which is noindex,follow
|
||||
```
|
||||
|
||||
**OG images:** 1200 × 630. Generate at build with `satori` or `astro-og-canvas`
|
||||
using the site's own type and palette. One template: display headline on cream,
|
||||
infinity mark, designation line. Never a screenshot.
|
||||
**OG images:** 1200 × 630. Never a screenshot.
|
||||
|
||||
**RULED 2026-08-27 (`AGENTS.md` Q40, R15) — TWO kinds of card, not one, and the
|
||||
generator is deferred to build step 7.** This spec said "one template" for all
|
||||
nineteen pages. Pouya split it:
|
||||
|
||||
> "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:
|
||||
|
||||
| Pages | Card |
|
||||
|---|---|
|
||||
| `/` and `/about/` | The **portrait** crop, `src/assets/og-portrait.jpg`. Not an interim — the decided answer |
|
||||
| Every other page | Generated at build with `satori` or `astro-og-canvas`, using the site's own type and palette: display headline on cream, infinity mark, designation line |
|
||||
| Each article | Per-article card from the same generator — the reason the two jobs are one build |
|
||||
|
||||
**Until step 7 every page shares the portrait, and that is a RECORDED interim
|
||||
that blocks cutover, not build step 3.** It is tracked as **R15** in
|
||||
`AGENTS.md` §12 with its removal trigger, because a link preview nobody on the
|
||||
team ever sees is exactly the kind of interim that becomes permanent by
|
||||
never being raised. The dependency choice is made against R11 on the day, not
|
||||
recalled from this paragraph.
|
||||
|
||||
## Structured data
|
||||
|
||||
|
||||
@@ -329,6 +329,18 @@ Then invalidate `/*`.
|
||||
|
||||
**Content and compliance**
|
||||
- [ ] Every claim traced to `AGENTS.md` §4 Verified
|
||||
- [ ] **Memberships re-confirmed with Pouya, then published** — `AGENTS.md` §12
|
||||
**R10** and **Q44**. ADRIC, ADRIO, the three OBA sections and the Canadian
|
||||
Tax Foundation are `[verified 2026-08-26]`. **§4 records yearly renewal for
|
||||
the OBA sections and the CTF only** — it says nothing about ADRIC's or
|
||||
ADRIO's period, and an earlier version of this line asserted "all renew
|
||||
yearly", which §4 does not support. **`/about/` currently publishes NO
|
||||
memberships group**: R10 is a prohibition and the re-confirmation was not
|
||||
obtained, so the group is withheld behind a `TODO(pouya)`. OCNI already
|
||||
lapsed quietly and §4 records it as "not current, do not publish" — that is
|
||||
the failure mode, and a stamp is not a renewal receipt. Re-confirm,
|
||||
re-stamp §4 and `CREDENTIALS.memberships`, restore the group to
|
||||
`CREDENTIAL_GROUPS`, and add `memberOf` to the Person JSON-LD
|
||||
- [ ] No `TODO(pouya)` remains in any shipped page
|
||||
- [ ] No matter counts, rates, dollar figures, or testimonials anywhere
|
||||
- [ ] Q.Arb described as **commenced August 2026** everywhere it appears — §4's
|
||||
@@ -346,6 +358,12 @@ Then invalidate `/*`.
|
||||
- [ ] All internal links resolve; no orphan pages
|
||||
- [ ] Sitemap generated and correct; `robots.txt` served, not 403
|
||||
- [ ] Rich Results Test passes; OG previews render in LinkedIn and Slack
|
||||
- [ ] **OG cards are per-page, not one portrait on all nineteen** — `AGENTS.md`
|
||||
Q40 / **R15**. The portrait is the decided card for `/` and `/about/`; every
|
||||
other page needs the generated typed card, built at step 7 with Insights.
|
||||
**This blocks cutover.** A link preview is the surface a general counsel
|
||||
actually sees when a colleague pastes the URL into Teams, and the interim
|
||||
makes nineteen unique titles look identical
|
||||
- [ ] 404 returns a 404 status
|
||||
- [ ] Security headers present (`securityheaders.com` A or better)
|
||||
- [ ] **SES identities verified for sending** — confirmed 2026-08-26, re-check at cutover: `aws sesv2 get-email-identity --email-identity smlcompany.ca` and confirm `VerifiedForSendingStatus: true`
|
||||
|
||||
+15
-2
@@ -125,8 +125,21 @@ offer tribunal-secretary work on the site.
|
||||
|
||||
### Other services — hourly
|
||||
|
||||
Early neutral evaluation, settlement counsel, dispute-system design, and
|
||||
pre-dispute technical advisory: **$500 / hour**.
|
||||
Early neutral evaluation, dispute-system design, and pre-dispute technical
|
||||
advisory: **$500 / hour**.
|
||||
|
||||
**THREE services, not four. `settlement counsel` is struck and must not be
|
||||
priced** — `AGENTS.md` Q42, Pouya 2026-08-27, correcting his own entry 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."
|
||||
|
||||
A struck row exists in §4 Offerings so the decision is findable. Same treatment
|
||||
as the tribunal-secretary rate above, and for a related reason: a rate on a fee
|
||||
page is an offer.
|
||||
|
||||
### Cancellation — adopted as recommended
|
||||
|
||||
|
||||
@@ -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/` — LAT‑AABS, *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 LAT‑AABS 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 LAT‑AABS, 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 LAT‑AABS, 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**.
|
||||
Reference in New Issue
Block a user