Use-case library
The operational patterns Nebbos was designed to serve. Each use case names the department shape, the Pearls involved, the approval graphs, and the audit-chain evidence the compliance officer holds at the end.
Regulated financial services
Investment operations, risk & compliance, KYC review, transaction monitoring.
Deployment shape:
- Compliance department: Pearl trained on ratified policies + past investigation outcomes
- Investigation department: Pearl trained on triage decisions from senior analysts
- Approval graphs for escalations to the CCO
- Every Pearl recommendation carries citation trail; every override lands in the chain
Compliance evidence produced: SEC / FINRA-ready audit chain segment per case; regulator can walk end-to-end without contacting Nebbos.
K-12 school districts
Curriculum operations, student support workflows, administrative decisioning — tenant-isolated per district under a FERPA-preventive substrate posture.
Deployment shape:
- Curriculum department: Pearl trained on approved lesson-plan patterns
- Admin department: Pearl trained on district policy decisions
- Row-level isolation ensures no student record crosses building or district boundaries
- FERPA-preventive posture at the substrate
Compliance evidence produced: every access to a scoped record is a chain entry; district office holds their own export bundle continuously.
Government & public sector
Regulatory operations, cross-agency coordination, FOIA-responsiveness, program administration.
Deployment shape:
- Air-gapped tier for classified content (never touches the network)
- Redacted-to-cloud tier for FOIA-responsive summarisation
- Cross-agency approval graphs with Architect-tier gates for interstate operations
- Every request the substrate refuses is itself a chain entry — legible to inspector general
Compliance evidence produced: end-to-end reconstruction of every decision-making chain across agencies; FOIA-response artefact assembled from chain queries.
Healthcare operations
Clinical operations, credentialing, care coordination, medical records handling.
Deployment shape (once BAA is executed):
- Clinical operations department with row-level isolation at the patient level
- Care coordination Pearl trained on care-pathway decisions
- Approval graphs with Host tier for clinical actions and Architect tier for records-management substrate mutations
- Portability bundle includes structured HL7-adjacent JSON export
Compliance evidence produced: BAA-compliant audit chain; portability satisfies HIPAA right-to-access on request.
Enterprise operations at scale
Fortune-scale operations across finance, HR, legal, compliance, IT, procurement, and engineering.
Deployment shape:
- One department per business function; one Pearl per department
- Cross-department approval graphs for operations that span functions
- Federated Pearl access at Architect tier for cross-function coordination
- Signals surface risks the Orchestrator observes across the whole graph
Compliance evidence produced: SOX-adequate audit chain for financial operations; ISO 27001-aligned records for IT and security operations.