Files
adr-sml/src/pages/arbitration.astro
T
Pouya LajevardiandClaude Opus 5 610edc24fd
Build and deploy / build-and-deploy (push) Failing after 4s
feat: Q.Arb is held; strike C.Med-Arb entirely; dissolve the paired disclosure
Pouya's ruling, 2026-08-29. Treated as D3-class and swept accordingly.

§4
  Q.Arb becomes a HELD designation. Obtained July 2026 — recorded in the
  register, deliberately not published. Public copy carries "Q.Arb (ADRIC /
  ADRIO)" beside Q.Med and nothing more. Every stage form is struck:
  "commenced", "in progress", "pathway", "not yet".

  C.Med-Arb as a stated goal is struck. This DEVIATES FROM THE STRATEGY BRIEF,
  which made it "the explicit long-term professional narrative"; the brief is
  not in this repository, so the deviation is recorded in four places so nobody
  reinstates it from a document no reader can open. The designation stays in
  §11 as a definition — what is struck is its status as a goal of his.

  The paired-disclosure condition dissolves. It existed only because Q.Arb was
  in progress; there is no stage left to disclose, and a condition with no
  subject cannot be half-kept.

Pages
  /about/'s credentialing arc is DELETED, not rewritten — two held designations
  are not a journey. /arbitration/ loses its stage section and its "Available
  now, and open about the stage" h1. /med-arb/'s endpoint section is rewritten.
  Deleting CREDENTIALS.goal/goalName rather than emptying them turned every
  consumer into a build error, which is how the last two surfaced.

  hasCredential now maps CREDENTIALS.designations instead of indexing [0];
  _DesignationRowParity pins the visible credential row to the same constant.

check:claims
  q-arb-as-a-stage (inverted from the predecessor, which barred Q.Arb reading
  as HELD) and c-med-arb-struck. Each page is now scanned twice — as published,
  and with inline tags collapsed — because [^<] cannot cross <strong>, which
  this site sets in prose.

Two open questions for Pouya, neither blocking:
  Q55 — the acquisition date. §4 says obtained July 2026; the Change Log of
  2026-08-26 records "commenced August 2026", both stamped [verified — Pouya].
  They cannot both be true. Nothing published turns on it.
  Q56 — is the mediation offering scoped commercial? §4 leaves it unscoped;
  four surfaces say "commercial mediation"; /practice/insurance/ offers
  mediation in insured-versus-insurer SABS matters.

Two review rounds, all findings applied or declined with a stated reason.
Round 2 found ten lines in docs/03 still instructing the struck form — the
2026-08-29 sweep missed them because `git grep 'Q.Arb'` is line-anchored and
the block never names it. Sweep the vocabulary, not only the subject.

Gates, exit statuses read directly, never through a pipe:
  npm run check        exit=0  (0 errors, 0 warnings, 0 hints)
  npm run lint         exit=0
  npm run build        exit=0  (12 pages)
  npm run check:claims exit=0  (11 patterns, 26 approved strings)
  npm audit            exit=0

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Md3GndFqWPzK78xAoebsg5
2026-08-30 10:37:19 -04:00

281 lines
11 KiB
Plaintext

---
/**
* `/arbitration/` — build step 4. Spec: docs/01 §`/arbitration/`, docs/03.
*
* ⚠️ THE PAIRED-DISCLOSURE CONDITION IS GONE, AND SO IS THE SECTION IT
* REQUIRED. Until 2026-08-29 this page was built around §4's condition that the
* arbitration offering ship beside the STAGE of the Q.Arb pathway — an h1
* reading "Available now, and open about the stage", and a whole section headed
* "Where I am in the arc". Q.Arb is held; the condition dissolved with its
* subject; the section was deleted rather than rewritten.
*
* ⚠️ AND DO NOT REPRODUCE IT FROM MEMORY. The characteristic failure now is a
* page that offers arbitration and then reaches for something qualifying to
* say. There is nothing to qualify: §4 Offerings rows all three forms, the
* designations are held, and the hero's `CredentialRow` names them. What
* remains of the old framing is the commercial scope — which was never part of
* the condition and is Pouya's own choice (Q39).
*
* ⚠️ AND NOTHING HERE MAY SAY OR IMPLY THAT ARBITRATION IS UNGATED IN ONTARIO.
* Q39's struck universal — "anyone may be appointed an arbitrator in Ontario;
* nothing in law gates the role behind a designation" — was FALSE as a
* universal, has been swept four times, and reached a public page once. The
* page states what is offered. It makes no claim about what the law requires of
* anyone.
*/
import BaseLayout from '../layouts/BaseLayout.astro';
import Button from '../components/Button.astro';
import ContactBand from '../components/ContactBand.astro';
import DefinitionGrid from '../components/DefinitionGrid.astro';
import CredentialRow from '../components/CredentialRow.astro';
import Eyebrow from '../components/Eyebrow.astro';
import SectionHeading from '../components/SectionHeading.astro';
import Undertaking from '../components/Undertaking.astro';
import { getImage } from 'astro:assets';
import ogDefault from '../assets/og-portrait.jpg';
import { serviceGraph } from '../data/schema';
import {
CONDUCT_UNDERTAKINGS,
CREDENTIAL_ROW,
CREDENTIAL_ROW_ARB,
} from '../data/site';
const ldImage = await getImage({
src: ogDefault,
format: 'jpeg',
width: 1200,
height: 630,
});
const graph = serviceGraph({
path: '/arbitration/',
name: 'Commercial arbitration',
serviceType: 'Commercial arbitration',
description:
'Sole-arbitrator, party-appointed and co-arbitration appointments in ' +
'commercial matters. Documents-only, expedited and full hearing tracks.',
imageUrl: new URL(ldImage.src, Astro.site).href,
});
/* §4 Offerings rows all three, each `[verified 2026-08-26 — Pouya, Q33/Q36]`,
each scoped commercial. Do not add a fourth without a row. */
const APPOINTMENTS = [
{
name: 'Sole arbitrator',
body: 'One arbitrator, appointed by agreement or by the mechanism the contract names.',
},
{
name: 'Party-appointed',
body: 'Appointed by one side to a three-member tribunal, deciding with the other two.',
},
{
name: 'Co-arbitration',
body: 'Sitting with co-arbitrators, usually where the matter spans more than one discipline.',
},
];
/* Tracks are docs/01 §`/arbitration/` item 2. The flat fees behind the first
two are D14's card and live on `/fees/`; no figure appears here. */
const TRACKS = [
{
name: 'Documents only',
body: 'No hearing. Written submissions, the documentary record, and an award. The right track where the dispute is about what the contract says rather than about what happened.',
},
{
name: 'Expedited',
body: 'A compressed timetable fixed at the outset, with page limits and a short hearing. Chosen when the commercial cost of the dispute staying open exceeds the value of a full process.',
},
{
name: 'Full hearing',
body: 'Pleadings, disclosure, witnesses, experts, oral argument. Where the facts are genuinely contested and someone has to hear them tested.',
},
];
---
<BaseLayout
title="Commercial Arbitration · Pouya Lajevardi · Toronto"
description="Sole, party-appointed and co-arbitration appointments in commercial matters, Toronto. Tracks, rules, and how an award is written and when it is due."
jsonLd={graph}
>
{/* ---- 1. Hero -------------------------------------------------------- */}
<section class="section hero">
<div class="wrap">
<Eyebrow dot>Arbitration</Eyebrow>
<h1 class="display hero-h">Sole, party-appointed, co-arbitration.</h1>
<p class="hero-lede">
I accept all three in commercial matters. This page covers how much
process the dispute needs, whose rules it runs under, and how the award
gets written.
</p>
<div class="hero-creds">
<CredentialRow slots={[...CREDENTIAL_ROW, CREDENTIAL_ROW_ARB]} />
</div>
</div>
</section>
{/* ---- 2. Appointments ------------------------------------------------ */}
{
/* INVERSE, and it inherited the ground rather than choosing it. The deleted
credentialing-stage section was this page's only `section-inverse`; left
cream, this section would have sat cream-on-cream against the hero and
rendered as one doubled block — the defect `/practice/[slug].astro` now
throws on. */
}
<section class="section section-inverse reveal">
<div class="wrap">
<div class="section-head">
<SectionHeading
eyebrow="Appointments"
level={2}
lede="Commercial matters. I do not accept family arbitration."
>
<span slot="heading">Three forms.</span>
</SectionHeading>
</div>
<DefinitionGrid items={APPOINTMENTS} />
</div>
</section>
{/* ---- 3. Tracks ------------------------------------------------------ */}
<section class="section section-alt reveal">
<div class="wrap">
<div class="section-head">
<SectionHeading
eyebrow="Tracks"
level={2}
lede="Settled with the parties before the first procedural order, not defaulted to."
>
<span slot="heading">How much process the dispute needs.</span>
</SectionHeading>
</div>
<DefinitionGrid items={TRACKS} />
</div>
</section>
{/* ---- 4. Rules ------------------------------------------------------- */}
<section class="section reveal">
<div class="wrap">
<div class="section-head">
<SectionHeading eyebrow="Rules" level={2}>
<span slot="heading">Under whose rules.</span>
</SectionHeading>
</div>
<div class="prose">
{
/* Sourced: docs/reference/adric-rules.md.
⚠️ ADR CHAMBERS IS NOT NAMED HERE, AND MUST NOT BE ADDED BACK.
Struck by Pouya 2026-08-30 from this page and from `docs/01` item 3
in the same ruling. `docs/reference/adr-institution-names.md`
establishes what the firm publishes — it does not establish that an
outside neutral can be appointed under its rules, and its own model
clause reads "at ADR Chambers". Naming it implies a relationship
this repository does not source. ADRIC and ad hoc are enough. */
}
<p>
<strong>The ADRIC Arbitration Rules.</strong> The ADR Institute of Canada
adopted a new edition effective 1 March 2025, alongside an arbitrator appointment
protocol and a set of forms — notice to arbitrate, request to administer,
request for the appointment of an arbitrator, urgent interim measures, challenge
to an arbitrator, notice of appeal.
</p>
<p>
<strong>Or ad hoc, or whatever the contract names.</strong> Where a contract
names a rule set, a seat and a language and leaves the rest to the tribunal,
that works.
</p>
{
/* Q54(e), rowed in §4 as a conduct undertaking. It REPLACED the
third-person sentence that made the same point as an observation;
do not restore that sentence beside it. */
}
<Undertaking>{CONDUCT_UNDERTAKINGS.arbitrationProcedure}</Undertaking>
</div>
</div>
</section>
{/* ---- 5. Awards ------------------------------------------------------ */}
<section class="section section-alt reveal">
<div class="wrap">
<div class="section-head">
<SectionHeading eyebrow="Awards" level={2}>
<span slot="heading">In writing, with reasons.</span>
</SectionHeading>
</div>
<div class="prose">
<p>
An award should be in writing and give reasons — what was in dispute,
what the record showed, and why the conclusion follows. An award that
announces a result without the reasoning is not much use to the party
that lost, and it is no use at all to the relationship that has to
survive it.
</p>
{
/* THE DATE IS A COMMITMENT ABOUT PROCESS, NOT A PUBLISHED TURNAROUND.
§4 Forbidden bars a time-to-award statistic outright; no figure
appears here and none may be added. */
}
{
/* Q54(f), answered by Pouya 2026-08-29 and rowed in §4 as a conduct
undertaking. Same replacement as in the Rules section above: this
paragraph opened "The date an award is due belongs in the first
procedural order", the observation form of the same commitment. The
sentence that follows it is unchanged and is the one doing the §4
Forbidden work. */
}
<Undertaking>{CONDUCT_UNDERTAKINGS.arbitrationAwardDate}</Undertaking>
<p>
No number is published here: a turnaround time advertised in advance
of a record is a guess dressed as a commitment.
</p>
</div>
</div>
</section>
{/* ---- 6. Fees --------------------------------------------------------- */}
<section class="section reveal">
<div class="wrap">
<div class="section-head">
<SectionHeading eyebrow="Fees" level={2}>
<span slot="heading">Published in full.</span>
</SectionHeading>
</div>
<div class="prose">
<p>
Hourly, hearing day, and flat fees for documents-only and expedited
matters at two levels of complexity. The cancellation schedule is on
the same page.
</p>
</div>
<div class="cta">
<Button href="/fees/" variant="ghost">The rate card &rarr;</Button>
</div>
</div>
</section>
<ContactBand />
</BaseLayout>
<style>
.hero {
padding-block-start: var(--space-9);
}
.hero-h {
margin-block: var(--space-4) var(--space-5);
font-size: var(--text-5xl);
max-inline-size: 20ch;
}
.hero-lede {
max-inline-size: 58ch;
font-size: var(--text-lg);
line-height: var(--leading-body);
color: var(--text-secondary);
}
.hero-creds {
margin-block-start: var(--space-8);
}
.cta {
margin-block-start: var(--space-6);
}
</style>