S13 · Solution for professional firms

Practice Platform for professional firms

One platform in five parts for a professional firm: website, knowledge library, firm assistant, front door and answer-engine presence, all on one approved library and one set of boundaries.

Status · Proposed · 2026-10-09

The problem it answers

A professional firm's website, its knowledge, its inquiries and its presence in answer engines are four separate things maintained by different people, and none of them is governed; iSystematic's Practice Platform puts all four under one library and one set of boundaries.

Each answer the firm gives, on any of them, is a statement the firm may have to stand behind.

What it does

The Practice Platform is one platform in five parts, built on one approved knowledge library and one set of boundaries, so that the website, the staff assistant, the front door and the answer engines all say the same thing, from the same sources, under the same rules.

Designed from current delivery work for a professional firm. No client is named, and no result is shown until a pilot measurement closes.

The five parts

The five parts are the website, the knowledge library, the firm assistant, the front door, and the firm's presence in answer engines and search.

Part 1

Website

Public pages, each with an owner, a review date and its source in the library.

Part 2

Knowledge library

The approved corpus: guides, FAQs, case and rule summaries, fee and process pages; classified, versioned, and retired on a date.

Part 3

Firm assistant

Staff research and drafting from the library and approved sources.

Part 4

Front door

Inquiries on every channel, answered from the library under an action policy, on ARIA by Simplification.io, which the firm subscribes to directly.

Part 5

Answer engines and search (GEO and AEO)

An entity block, passage rules, llms.txt and a monthly answer panel that records how engines describe the firm.

Built from

It is built from four catalogue workflows, five catalogue patterns, two other solutions and ARIA.

Id	Name	What it brings
W02	Inbox Triage and Draft Replies	Inquiries classified and replies drafted for review
W03	Approved FAQ Assistant	The method for building the library's approved answers
W11	Lead Intake and Next-Step Draft	Inquiry summaries and next-step drafts, held for review
W12	Client Onboarding	Checklist and welcome pack once the scope is agreed
P01	Retrieve, Ground, Draft, Review	Every answer grounded in the library
P04	Approval Before Commitment	Nothing booked, charged or sent beyond an acknowledgement without a person
P09	Minimise and Isolate Data	The least data and access; client and firm contexts kept apart
P10	Inspect Retrieved Instructions	An inquiry cannot instruct the assistant or the front door
P11	Keep a Workflow Receipt	Each inquiry leaves a receipt
S3	Front Door Agent	The front door, configured for the firm
S6	Knowledge Desk	The library's rules: cite the source, refuse when it is missing
ARIA	ARIA by Simplification.io	The front-door platform, which the firm subscribes to directly

What it is built on

Each of the five parts is built on named frameworks, and each leaves a record the firm keeps.

Part	Frameworks at work	What the firm keeps
1 Website	The Boundary Invariant on public claims (no outcome or timeline promises; the profession's advertising rules where they apply); every page sourced from the library; release through gate G4 of the Five-Gate Deployment Model™	Page register: owner, review date, source
2 Knowledge library	AI Data Governance Framework™: classify (public, internal, privileged), bound (what may reach which model and where), prove (each item traced to an official or firm source with its date), gate (review before release), release (with a BOE record); retired items leave the corpus on the day	Source register with lineage; retirement log
3 Firm assistant	PEVG (the verifier checks every claim against the library or the cited authority; the generator asserts only what passed); Governed Routing Policy and Tiered Model Pool (confidential matters only to permitted model classes, in the jurisdiction required); Structure-Only Trajectory Logging (logs keep structure, never privileged content); Benchmark Before Authority (new tasks only after a benchmark); Budget as Boundary, all from the Pattern Language	Verifier rules; routing evidence; benchmark records; spend log
4 Front door	PARA as iSystematic configures it on ARIA; the action policy as Tiered Human-in-the-Loop; Capability Contracts for booking and payment links; the AI Vendor Risk Framework (AVRF)™ on ARIA and every model provider	Agent registry entry; action policy; vendor records
5 GEO and AEO	Passage rules (definition first, self-contained, one sourced fact) applied to library-backed pages; one entity description everywhere; the monthly answer panel as the G5 monitoring record for how engines describe the firm	Entity block; answer panel log
Across all five	A quick profile under the MESA Framework™ at the start; CADRE™ (AI governance operating model) scaled to a small firm; the five gates; the AI Incident Response Protocol (AIRP)™; one event identity per inquiry, from form or message to reply, booking and file note	Profile; decision-rights table; gate records; incident records

The boundaries, declared an example for a law firm

This is an example set of boundaries for a law firm, not any client's configuration: each boundary becomes a BOE Declaration, with an optimiser free to improve and the evidence that shows the boundary held.

Boundary (never crossed)	Optimiser (free to improve)	Evidence it held
No legal advice in any public answer, page or message	Helpfulness, clarity, tone	Verifier refusals; reviewed samples
No outcome, timeline or fee promised except the published fee pages	Speed and warmth of reply	Action policy log
Client and privileged material reach only permitted model classes and locations	Model choice, cost, latency	Routing evidence per request
Nothing booked, charged or sent beyond an acknowledgement without a person	Response time	Approval records
Library content only from attested sources, dated	Coverage and freshness	Lineage records
Monthly AI spend within the cap	Quality per unit of spend	Spend log

The five gates, at firm scale

At firm scale, each of the five gates names one person, at the firm or at iSystematic, and leaves one record.

Gate	What it means here	Named person	Record
G1 Data and Design	Library classified and sourced; no client files used; vendors cleared under AVRF (site host, ARIA, model providers, booking and payment services)	The firm's data owner (often the office manager)	Classification, lineage, vendor records
G2 Validation	Fictional inquiries, including urgent deadlines, ambiguous facts and adversarial messages; the assistant benchmarked per task; validated by someone who did not build it	A senior lawyer, or an iSystematic reviewer outside the build team	Validation report
G3 Approval	The firm signs off on the evidence, not on the demo	The principal	Approval record
G4 Deployment	Released configuration: library version, routing policy version, action policy version; rollback tested	iSystematic platform owner	Release record; rollback test
G5 Operation	Triggers armed: a rule or policy change, a model version change, a complaint, a confidence drop, a wrong citation in the answer panel; any of them can reopen G2	The principal or the named deputy	Trigger register; monthly note

When something goes wrong an illustration

This is a fictional illustration of AIRP at firm scale, not an event at any firm: an answer engine quotes an outdated passage from the firm's site.

Signal

The monthly answer panel shows the outdated quote.

Classify

Public, and not specific to any client.

Contain

The library item and the page are corrected, and the front door stops using the passage.

Escalate

The principal is told.

Reconstruct

The event identity shows which library version the page carried and when it changed.

Close

A retirement date is added to every passage of that type, and the panel gains a test that would have caught it.

The evidence it leaves behind

The platform leaves records the firm keeps.

A source register with lineage, and a retirement log
A page register: owner, review date and source for each page
Routing evidence
Gate records
An answer panel log
Verifier rules, benchmark records and a spend log
The front door's agent registry entry, action policy and vendor records
Incident records

For whom

The Practice Platform is for professional firms, law firms first; the same platform fits accounting firms and clinics, each with its own boundaries declared. For a clinic, nothing clinical is automated.

The typical buyer is a managing partner or an office manager. Firms reach it from law firms, accounting firms and clinics when they want the whole platform rather than one workflow.

Status

Proposed, as of 9 October 2026. The Practice Platform was designed from current delivery work for a professional firm; that firm is not named, and no result is shown until a pilot measurement closes. A solution becomes Piloting or Released only after a documented pilot.

Engagement shape

The engagement runs in five phases, and its price basis is scoped.

Discover

A MESA quick profile, and AVRF run on the firm's existing vendors.

Build

The knowledge library and the website.

Assistant and front door

The firm assistant, and the front door on ARIA under the action policy.

GEO and AEO

Passage rules, the entity block and the monthly answer panel.

Operate

Monthly operation.

How to start

Start with a conversation about the firm's site, its knowledge and its inquiries; the first phase is Discover, and the scope and price are set from it.

Talk to us about the Practice Platform

Tell us about your firm's site, its knowledge and its inquiries; the first phase is Discover.

How we build Talk to us →