// Process & Methodology — per-engagement deep dives // Each engagement gets its own scrollable section with phase breakdown + bespoke schematic. const ENGAGEMENT_FLOWS = [ { id: 'mediation', n: '01', title: 'Mediation', tagline: 'Privately-administered mediation for technically complex commercial disputes.', phases: [ { p: 'Pre-session', d: 'Position statements (confidential to mediator), key-evidence designation, technical briefings where the matter requires them. Daniel issues a session agenda 7\u201310 days ahead.' }, { p: 'Joint opening', d: 'Each party presents position briefly, with technical demonstrations as needed. Daniel frames the day, sets ground rules for confidentiality, and identifies the technical questions to be tackled.' }, { p: 'Caucus rounds', d: 'Iterative private sessions. Daniel translates technical positions and tests assumptions in each room. Where the matter turns on a verifiable fact, a forensic component is invoked to resolve it on the spot.' }, { p: 'Convergence', d: 'Settlement architecture drafted, including any technical remediation, audit, or escrow terms. Daniel surfaces the structure both rooms will accept.' }, { p: 'Documentation', d: 'Term sheet executed by all parties. Where stipulated, Daniel provides a written summary of agreements reached for inclusion in court approval orders or arbitration awards.' }, ], schematic: 'mediation', }, { id: 'special-master', n: '02', title: 'Special Master / Discovery Referee', tagline: 'Court-appointed for ESI protocols, discovery management, and complex protective orders.', phases: [ { p: 'Appointment', d: 'Order of appointment from the court, scope-of-authority defined. Daniel issues a brief acknowledgment outlining initial procedural framework and reporting cadence.' }, { p: 'Initial protocol', d: 'Draft ESI protocol distributed to parties: custodians, sources, search terms / TAR design, privilege handling, production format, claw-back terms. 10\u201314 day comment window.' }, { p: 'Active management', d: 'Real-time dispute resolution. Disputes raised by letter brief; Daniel rules within 5 business days. Where the issue is technical (sampling validity, search term efficacy, cross-border production), Daniel may issue a written analysis with the ruling.' }, { p: 'Spoliation / sanctions', d: 'Where preservation failures are alleged, Daniel conducts a fact-finding inquiry under FRCP 37(e) standards and issues findings with recommended sanctions if warranted.' }, { p: 'Reporting', d: 'Periodic reports to the appointing court. Final report on dissolution of the appointment with summary of disputes resolved and any open issues.' }, ], schematic: 'special-master', }, { id: 'forensic', n: '03', title: 'Forensic Neutral', tagline: 'Independent third-party technical expert appointed by tribunal or counsel.', phases: [ { p: 'Scoping', d: 'Question put to the neutral defined precisely. Investigation protocol drafted: targets (devices, accounts, repositories), tools, custody chain, hashing strategy, reporting format, deadlines.' }, { p: 'Acquisition', d: 'Forensic images acquired from in-scope sources. Hashes calculated and recorded. Original media sealed and stored under access-logged custody.' }, { p: 'Analysis', d: 'Examination per the protocol. Technical findings recorded contemporaneously. Where the finding affects scope (e.g. discovery of a previously unknown source), parties are notified.' }, { p: 'Authentication', d: 'For evidence destined for the record \u2014 emails, chats, messaging app artifacts, smartphone exports, deepfakes \u2014 chain of custody, hash verification, and tooling provenance documented for FRE 901 admission.' }, { p: 'Report', d: 'Written report to the tribunal and parties: methodology, findings, limitations, supporting exhibits. Daniel is available for cross-examination if the report is contested at hearing.' }, ], schematic: 'forensic', }, { id: 'ai-disputes', n: '04', title: 'AI Disputes — Tribunal Services', tagline: 'Arbitrator and protocol architect under emerging AI dispute frameworks.', phases: [ { p: 'Framework selection', d: 'JAMS AI Disputes Clause and Rules where the parties\u2019 contract incorporates them. Where the contract is silent, Daniel can propose a tailored framework with parties\u2019 consent.' }, { p: 'Tiered protective order', d: 'Standing protective order template for AI matters \u2014 distinguishing model weights, training data, prompts, inference logs, and outputs into separate access tiers. Reviewer credentialing handled per tier.' }, { p: 'Discovery scoping', d: 'System cards, evaluation reports, RAG configurations, retrieval logs, fine-tuning datasets, inference timestamps. What is probative; what is fishing into trade secrets dressed as discovery.' }, { p: 'Technical adjudication', d: 'Daniel as arbitrator may pose questions of his own to parties\u2019 experts where the record is incomplete. Hearings may include live model interrogation under controlled conditions.' }, { p: 'Award', d: 'Reasoned award addressing the technical and legal questions. Where the matter turns on machine behavior, the award sets out the model behavior actually observed and the legal consequences turning on it.' }, ], schematic: 'ai', }, { id: 'arbitration', n: '05', title: 'Arbitration', tagline: 'Sole or panel arbitrator for technically complex commercial matters.', phases: [ { p: 'Constitution of tribunal', d: 'Sole arbitrator on appointment; chair or wing on three-member panels. Conflicts disclosure under L.C.I.A., H.K.I.A.C., AAA, JAMS, or party-stipulated rules.' }, { p: 'Terms of reference', d: 'Procedural calendar, scope of pleadings, evidentiary rules, language and seat. Where the matter is technical, Daniel often expands the standard order to address source-code review, expert evidence framework, and protective order.' }, { p: 'Evidentiary phase', d: 'Documentary production per agreed scope. Witness statements; expert reports. Hearings either in person at the seat or virtual / hybrid.' }, { p: 'Hearing', d: 'Oral testimony, cross-examination, expert hot-tubbing where useful. Daniel poses tribunal questions where the record is silent on a determinative technical fact.' }, { p: 'Award', d: 'Reasoned award addressing all submitted issues. Daniel routinely issues awards within 60\u201390 days of close of hearings.' }, ], schematic: 'arbitration', }, ]; const ProcessPage = ({ onNav }) => (
Process · Methodology

How the
work runs.

Five engagement types, each with its own protocol, deliverable, and rhythm. The methodology section below walks through each — phase by phase, from appointment to award or report.

{/* TOC */}
{ENGAGEMENT_FLOWS.map(e => ( · {e.n} {e.title.split('—')[0].split('/')[0].trim()} ))}
{ENGAGEMENT_FLOWS.map((e, i) => (
{e.n}
Engagement

{e.title}

{e.tagline}

{e.schematic === 'mediation' && } {e.schematic === 'special-master' && } {e.schematic === 'forensic' && } {e.schematic === 'ai' && } {e.schematic === 'arbitration' && }
PHASE PROTOCOL
    {e.phases.map((ph, j) => (
  1. {String(j + 1).padStart(2, '0')}

    {ph.p}

    {ph.d}

    2. ))}
))} {/* Cross-engagement principles */}
Cross-Engagement

Five principles that hold across every role.

{[ ['I.', 'Confidentiality', 'Protective orders, encrypted channels, access-logged storage \u2014 standard in every engagement.'], ['II.', 'Technical fluency', 'The neutral can read the source code, model weights, and audit logs, not just hear about them.'], ['III.', 'Reproducibility', 'Methodology recorded, hashes captured, custody chain documented \u2014 anyone with the same record could reach the same finding.'], ['IV.', 'Proportionality', 'Scope of investigation calibrated to the question put to the neutral. No fishing dressed as discovery.'], ['V.', 'Speed', 'Protocols issued within days; rulings within a week; awards within 60\u201390 days of hearings.'], ].map(([n, t, d]) => (
{n}

{t}

{d}

))}
Begin a matter

Eight questions. One considered match.

); window.ProcessPage = ProcessPage;