THE QUESTION IT ANSWERS
Which part of this is the source, not the signal?
- ACCOUNT
- DETECT
- ISOLATE
- SUPPRESS
01
The problem
Multi-source training creates a model no one can fully account for. A scanner hardware change, a new site protocol, or a divergent data batch shifts the model's behaviour, and no one can say by how much or trace it to which specific component.
02
What it delivers
Delivers three distinct objects: a source-invariant core model, bounded named source components, and a definitive separation record. Each data source's contribution is explicitly named, mathematically bounded, and entirely removable without retraining.
03
Who it is for
A fit for
- Medical imaging consortiums
- Pathology labs
- Regulated finance institutions
- Biotech firms
- Multi-tenant AI operators
Funded via governance and risk budgets.
04
How it works
The Separator is built from 4 of the six capabilities of the ORMAS architecture. Each is a property of how the network trains, not a tool bolted on afterwards.
- 01ACCOUNTEmit a bounded, timestamped, causally attributed record of every modification the network made to itself.
- 02DETECTIdentify which samples are damaging which component, and separate mislabelled from hard-but-correct.
- 03ISOLATEAllocate dedicated capacity bound to a named sample set, under a bound, with the binding recorded.
- 04SUPPRESSRemove an isolated component and ship without it, with a bounded statement about what changed.
05
In your industry
This is why ORMAS is one product rather than seven. The Separator is the same mechanism in every row below — only the customer's own vocabulary changes.
- Medical
- site — the hospital
- Finance
- region or desk
- Biotech
- batch — the assay run
- AI lab
- source — the corpus
- SaaS
- tenant — the customer
06
Markets using it
- AI TrainingSegments by scale
- Regulated FinanceSegments by industry
- Medical AISegments by industry
- Data ObligationSegments by obligation
- Defense & Safety-CriticalSegments by industry
07
Questions
No. ORMAS is one product under one licence, and The Separator is one of the seven things it is proven at. You turn on what your situation needs; there is no separate purchase, no separate integration and no separate contract.
The mechanism does not know what industry it is in. What changes between them is the noun, not the method — the table above is the same mechanism with each sector's own vocabulary substituted, which is why one product serves all of them.
On your infrastructure. The licence is on-premise and per-institution: nothing is sent to a third party, there is no hosted tier, and no usage metering phones home. In a hospital enclave or a controlled environment, that is a requirement rather than a preference.
Pre-book ORMAS with The Separator in scope.
Every engagement starts with one specific problem — a run that died, an audit that asked a question you could not answer, a dataset you cannot vouch for.
We reply within a few days. Every message is read by a person.
Pre-book a deployment
One licence, no price list. Terms are agreed per institution and written into the contract, and pre-booking fixes them ahead of general availability.
Useful to bring
- What you train, and roughly at what scale
- The obligation driving it — SR 26-2, the EU AI Act, Article 17, a PCCP, an internal policy
- What a failed run currently costs you to diagnose