Module catalogue

Executive summary

Faurenis is 19 modules in six domains — capture, reason, see, produce, operate and govern — all writing through the clinical spine. Every module is specified on one template: purpose, pipeline, data owned, models, guardrails, rollout status, interfaces, invariants and known limits. A module that makes no model calls says so explicitly; most of the operational modules are deterministic code.

Catalogue

06.01 Voice OS
Domain
Capture
Status
Production
In one line
One microphone and one voice for the whole application: streaming recognition for notes and charting, spoken answers, and a speech-to-speech assistant that can also see through the intraoral camera.
06.02 Scribe
Domain
Capture
Status
Production
In one line
Scribe turns the conversation in the chair, or a dictation, into a structured clinical note and visit dossier.
06.03 Perio
Domain
Capture
Status
Production
In one line
Perio charts a full periodontal exam by voice: the clinician calls out probing depths, recession, bleeding and mobility while the assistant keeps their hands free.
06.04 Copilot
Domain
Reason
Status
Production
In one line
Copilot is the assistant at the centre of the workspace.
06.05 Evidence base
Domain
Reason
Status
Production
In one line
The evidence base retrieves literature from 9 open sources in parallel, ranks it deterministically, checks licences and retractions, and verifies whether each passage actually supports a claim.
06.06 Patient memory and digital twin
Domain
Reason
Status
Production
In one line
Patient memory is the longitudinal context Copilot reads: summarised history, extracted items and the timeline of confirmed facts.
06.07 Imaging Intelligence
Domain
See
Status
Production
In one line
Imaging ingests radiographs and DICOM studies, renders them in a DICOM viewer, and supports manual measurement and annotation today.
06.08 3D Studio and clinical HUD
Domain
See
Status
Pilot
In one line
The 3D Studio is a patient-bound planning space — restorative, implant, bridge and arch views — rendered with three.js; the clinical HUD surfaces chairside suggestions while the clinician works.
06.09 Clinical Documents
Domain
Produce
Status
Production
In one line
Clinical Documents drafts the paperwork a visit needs — visit summaries, aftercare instructions, perio reports, referral and recall letters, consent forms, treatment plans with costs — from sources a clinician has already reviewed.
06.10 Document Intelligence
Domain
Produce
Status
Production
In one line
Document Intelligence reads what patients and other providers send — referrals, lab results, prior records — and turns it into reviewable structured data.
06.11 Treatment Planning
Domain
Produce
Status
Production
In one line
Treatment Planning is a versioned plan aggregate: options, phases, steps with dependencies, safety checks, fees, patient acceptance and scheduling.
06.12 Operatory and scheduling
Domain
Operate
Status
Production
In one line
The operatory module runs the clinic’s day: chairs as schedulable resources, appointments with their clinical requirements, a live board, waitlist, recall and confirmation workflows, and a briefing for each visit.
06.13 Patient Mode and aftercare
Domain
Operate
Status
Production
In one line
Patient Mode turns the chairside screen toward the patient and shows exactly one released artifact, nothing else; aftercare hands patients their instructions through a single-use link.
06.14 Notifications
Domain
Operate
Status
Production
In one line
Notifications deliver the clinic inbox, native push to iOS and Android, web push and email.
06.15 Billing and entitlements
Domain
Operate
Status
Production
In one line
Billing runs subscriptions through Stripe, a credit wallet with an append-only ledger, and a usage ledger whose unit is a documented encounter (ADR 0020).
06.16 Practice-system integrations
Domain
Operate
Status
Pilot
In one line
Integrations synchronise patients, appointments and records with the practice-management systems clinics already run, and expose a FHIR surface.
06.17 Clinic intelligence
Domain
Operate
Status
Production
In one line
Clinic intelligence gives owners and managers the operational picture: chair occupancy, recall performance, roster, compliance state and AI usage, with trends and insights.
06.18 Administration and platform console
Domain
Govern
Status
Production
In one line
Two consoles with different reach.
06.19 Investor Data Room
Domain
Govern
Status
Production
In one line
The Data Room is an access-controlled due-diligence space with its own authentication domain, its own tables and its own hash-chained activity log.

Module	Domain	Status	In one line
06.01 Voice OS	Capture	Production	One microphone and one voice for the whole application: streaming recognition for notes and charting, spoken answers, and a speech-to-speech assistant that can also see through the intraoral camera.
06.02 Scribe	Capture	Production	Scribe turns the conversation in the chair, or a dictation, into a structured clinical note and visit dossier.
06.03 Perio	Capture	Production	Perio charts a full periodontal exam by voice: the clinician calls out probing depths, recession, bleeding and mobility while the assistant keeps their hands free.
06.04 Copilot	Reason	Production	Copilot is the assistant at the centre of the workspace.
06.05 Evidence base	Reason	Production	The evidence base retrieves literature from 9 open sources in parallel, ranks it deterministically, checks licences and retractions, and verifies whether each passage actually supports a claim.
06.06 Patient memory and digital twin	Reason	Production	Patient memory is the longitudinal context Copilot reads: summarised history, extracted items and the timeline of confirmed facts.
06.07 Imaging Intelligence	See	Production	Imaging ingests radiographs and DICOM studies, renders them in a DICOM viewer, and supports manual measurement and annotation today.
06.08 3D Studio and clinical HUD	See	Pilot	The 3D Studio is a patient-bound planning space — restorative, implant, bridge and arch views — rendered with three.js; the clinical HUD surfaces chairside suggestions while the clinician works.
06.09 Clinical Documents	Produce	Production	Clinical Documents drafts the paperwork a visit needs — visit summaries, aftercare instructions, perio reports, referral and recall letters, consent forms, treatment plans with costs — from sources a clinician has already reviewed.
06.10 Document Intelligence	Produce	Production	Document Intelligence reads what patients and other providers send — referrals, lab results, prior records — and turns it into reviewable structured data.
06.11 Treatment Planning	Produce	Production	Treatment Planning is a versioned plan aggregate: options, phases, steps with dependencies, safety checks, fees, patient acceptance and scheduling.
06.12 Operatory and scheduling	Operate	Production	The operatory module runs the clinic’s day: chairs as schedulable resources, appointments with their clinical requirements, a live board, waitlist, recall and confirmation workflows, and a briefing for each visit.
06.13 Patient Mode and aftercare	Operate	Production	Patient Mode turns the chairside screen toward the patient and shows exactly one released artifact, nothing else; aftercare hands patients their instructions through a single-use link.
06.14 Notifications	Operate	Production	Notifications deliver the clinic inbox, native push to iOS and Android, web push and email.
06.15 Billing and entitlements	Operate	Production	Billing runs subscriptions through Stripe, a credit wallet with an append-only ledger, and a usage ledger whose unit is a documented encounter (ADR 0020).
06.16 Practice-system integrations	Operate	Pilot	Integrations synchronise patients, appointments and records with the practice-management systems clinics already run, and expose a FHIR surface.
06.17 Clinic intelligence	Operate	Production	Clinic intelligence gives owners and managers the operational picture: chair occupancy, recall performance, roster, compliance state and AI usage, with trends and insights.
06.18 Administration and platform console	Govern	Production	Two consoles with different reach.
06.19 Investor Data Room	Govern	Production	The Data Room is an access-controlled due-diligence space with its own authentication domain, its own tables and its own hash-chained activity log.

The module template

Overview
Answers
What the module is for, and its overall status
Pipeline
Answers
What happens, in order, on the main path
Data owned
Answers
Which stores the module is the system of record for
Models and engines
Answers
Which model family or deterministic engine runs each step — or that there is none
Guardrails
Answers
What stops the module from doing the wrong thing
Rollout and status
Answers
Per-capability status, using the five-status vocabulary
Interfaces
Answers
What it consumes from, and emits to, the rest of the platform
Invariants and known limits
Answers
The numbered rules it must not regress, and what is not built yet

Section	Answers
Overview	What the module is for, and its overall status
Pipeline	What happens, in order, on the main path
Data owned	Which stores the module is the system of record for
Models and engines	Which model family or deterministic engine runs each step — or that there is none
Guardrails	What stops the module from doing the wrong thing
Rollout and status	Per-capability status, using the five-status vocabulary
Interfaces	What it consumes from, and emits to, the rest of the platform
Invariants and known limits	The numbered rules it must not regress, and what is not built yet

Cross-module interfaces

Modules do not call each other’s storage. They meet on the spine — encounters, artifacts, facts and audit — and on a small number of in-process buses and outboxes.

Voice OS
Consumes
Copilot clinical lane (answers to spoken clinical questions) · Chart and workspace state (live tools that read the app)
Emits
Transcripts to Scribe, Perio and dictation · Resolved intents to workspace navigation and Copilot · Proposals and dispatch assertions to audit
Scribe
Consumes
Voice OS transcripts · Encounter binding from the clinical spine
Emits
SOAP note and dossier artifacts · Proposed clinical facts · Accepted sources for Clinical Documents · Chairside suggestions for the HUD
Perio
Consumes
Voice OS streaming recognition · Encounter binding
Emits
Completed exams to timeline, memory, digital twin and facts · Staging and report artifacts · Perio sources for Clinical Documents
Copilot
Consumes
Evidence base (snapshots, passages, entailment) · Patient memory, facts and timeline · Voice OS (spoken turns)
Emits
Claims with evidence links · Report artifacts · Spoken answers via the voice output bus
Evidence base
Consumes
Claims from Copilot and Clinical Documents
Emits
Evidence snapshots · Support relations per claim
Patient memory and digital twin
Consumes
Confirmed facts and completed exams
Emits
Patient context for Copilot, HUD and Treatment Planning
Imaging Intelligence
Consumes
Encounter binding · Signed model releases from the research plane
Emits
Imaging finding artifacts · Accepted findings to facts and chart reconciliation
3D Studio and clinical HUD
Consumes
Chart, twin and plan state · Scribe context (HUD)
Emits
Staged proposals to Treatment Planning · Chairside suggestions
Clinical Documents
Consumes
Accepted Scribe dossiers, completed perio exams, accepted plan steps and acceptances · Clinic fee schedule
Emits
Signed clinical documents and renditions · Patient-facing documents for Patient Mode and aftercare links
Document Intelligence
Consumes
Uploads and integration documents
Emits
Extraction and interpretation artifacts · Proposed facts on acceptance
Treatment Planning
Consumes
Confirmed facts · Studio proposals and Copilot drafts · Clinic fee schedule
Emits
Accepted plan versions · Appointment links · Plan sources for Clinical Documents · Billing inputs
Operatory and scheduling
Consumes
Accepted treatment-plan steps · Clinic configuration
Emits
Encounters at check-in · Board change events · Reminders and recall notifications
Patient Mode and aftercare
Consumes
Signed clinical documents · Performed work
Emits
Disclosure evidence
Notifications
Consumes
Domain events across modules
Emits
Inbox entries, push and email
Billing and entitlements
Consumes
Documented encounters · AI decision log (token and cost)
Emits
Entitlements · Budget refusals (HTTP 429)
Practice-system integrations
Consumes
Vendor webhooks and APIs
Emits
Patients, appointments and documents into Faurenis · Updates back to the vendor system
Clinic intelligence
Consumes
Operational events and AI usage
Emits
Dashboards and insights
Administration and platform console
Consumes
Audit trail · Rollout and entitlement state
Emits
Grants, releases and entitlements · Security anomalies
Investor Data Room
Consumes
Architecture facts (full edition)
Emits
Activity chain · Engagement analytics

Module	Consumes	Emits
Voice OS	Copilot clinical lane (answers to spoken clinical questions) · Chart and workspace state (live tools that read the app)	Transcripts to Scribe, Perio and dictation · Resolved intents to workspace navigation and Copilot · Proposals and dispatch assertions to audit
Scribe	Voice OS transcripts · Encounter binding from the clinical spine	SOAP note and dossier artifacts · Proposed clinical facts · Accepted sources for Clinical Documents · Chairside suggestions for the HUD
Perio	Voice OS streaming recognition · Encounter binding	Completed exams to timeline, memory, digital twin and facts · Staging and report artifacts · Perio sources for Clinical Documents
Copilot	Evidence base (snapshots, passages, entailment) · Patient memory, facts and timeline · Voice OS (spoken turns)	Claims with evidence links · Report artifacts · Spoken answers via the voice output bus
Evidence base	Claims from Copilot and Clinical Documents	Evidence snapshots · Support relations per claim
Patient memory and digital twin	Confirmed facts and completed exams	Patient context for Copilot, HUD and Treatment Planning
Imaging Intelligence	Encounter binding · Signed model releases from the research plane	Imaging finding artifacts · Accepted findings to facts and chart reconciliation
3D Studio and clinical HUD	Chart, twin and plan state · Scribe context (HUD)	Staged proposals to Treatment Planning · Chairside suggestions
Clinical Documents	Accepted Scribe dossiers, completed perio exams, accepted plan steps and acceptances · Clinic fee schedule	Signed clinical documents and renditions · Patient-facing documents for Patient Mode and aftercare links
Document Intelligence	Uploads and integration documents	Extraction and interpretation artifacts · Proposed facts on acceptance
Treatment Planning	Confirmed facts · Studio proposals and Copilot drafts · Clinic fee schedule	Accepted plan versions · Appointment links · Plan sources for Clinical Documents · Billing inputs
Operatory and scheduling	Accepted treatment-plan steps · Clinic configuration	Encounters at check-in · Board change events · Reminders and recall notifications
Patient Mode and aftercare	Signed clinical documents · Performed work	Disclosure evidence
Notifications	Domain events across modules	Inbox entries, push and email
Billing and entitlements	Documented encounters · AI decision log (token and cost)	Entitlements · Budget refusals (HTTP 429)
Practice-system integrations	Vendor webhooks and APIs	Patients, appointments and documents into Faurenis · Updates back to the vendor system
Clinic intelligence	Operational events and AI usage	Dashboards and insights
Administration and platform console	Audit trail · Rollout and entitlement state	Grants, releases and entitlements · Security anomalies
Investor Data Room	Architecture facts (full edition)	Activity chain · Engagement analytics

SOURCE OF TRUTH

src/pages/architecture/spec/moduleTemplate.ts
src/pages/architecture/spec/chapters/modules/