The case enters with context
Intent, status and signals arrive in the same flow.
Compliance
The rule runs before the reply. The evidence is created at the same time.
Cortex brings limits, responsible gaming, human approval and traceability into every conversation.
sourceApproved source
The reply begins with approved content and the authorized event.
Gate 1 of 4
Compliance does not appear at the end as a report. It determines what can happen now.
The same rule set follows every session, including when a case needs to leave automation.
Control in four moves
A reply moves forward only when the rule set allows it.
The platform checks the approved source, applies limits, verifies risk signals and calls a person when the case needs authority.
The rule set is checked
Source, limit, protection and authority are applied.
The flow releases or routes
Exceptions go to a person with reason and context.
The trail is created with it
Event, owner, decision and hash remain reviewable.
Chained evidence
The trail shows the decision, not only the final message.
Intake, rule, proposal and approval remain in sequence. Audit can see who did what and when.
trace #064B17A2 · sample data
14:32:08Message received
Atena · check rule
14:32:09Rule checked
Nêmesis · require authority
14:32:10Send blocked
Apolo · route case
14:33:02Decision recorded
Human · take case
Clear accountability
Cortex applies and records. The operator still decides the policy.
Technology does not move regulatory responsibility. It makes the rule set executable and the decision reviewable.
OperatorDefines and remains accountable
Sets policy, limits and approval thresholds.
CortexApplies and records
Brings the controls into the conversation and preserves the evidence.
Frequently asked questions
Direct answers, paired with the same visual evidence the operation can review.
What does Cortex check before replying?
A reply goes through the approved knowledge base, operating limits, responsible-gaming signals and the required authority for that case.
four gates for the same decision
SourceApproved base
Controlled content
LimitContract and window
Cap and authority
ProtectionSignal applied
Responsible gaming
PersonHuman approval
Exception routed
Does Nêmesis decide KYC, AML or fraud?
No. Those decisions belong to the operator. Nêmesis uses the signal defined by the operation to apply who can be contacted, when and with which message.
OperatorDefines the policy and signal
KYC, AML, fraud and responsible gaming remain the operator's responsibility.
CortexApplies and records
The signal becomes a block, route or suppression in the conversation.
Where does conversation data stay?
The knowledge base and trail remain in Brazil. Before language-model processing, Cortex reduces data to what is necessary. The operator remains the controller.
BrazilBase and trail
Origin and evidence
Before processingMinimisation
Only what is needed proceeds
ModelProcessing
Reply generation
What can a regulator review?
The operation can review the session sequence, applied rule, involved actor and recorded decision. Filing and responding to the regulator remains the operator's responsibility.
01Timestamp
02Owner
03Decision
04Chained hash