Institutional FAQ: Titan V2 Compendium
Technical, Operational, and Commercial Disclosures
DCE Australia operates with Deterministic Finality. This FAQ provides 100% accurate
disclosures regarding the engine's deterministic boundaries, sovereign constraints, and institutional
obligations.
1. Engine Logic: How is deterministic finality achieved?
1.1 What is "Deterministic Redaction"?
Unlike AI (LLMs) or NLP tools which use probability to guess if a string is PII,
DCE uses Computational Checksums (Mod-11, Mod-89, Luhn). A number is only redacted
if it passes the exact weighting criteria used by Australian Government agencies (ATO, Services
Australia). If it doesn't match the checksum, it remains untouched.
1.2 Does DCE redact personal names?
No. DCE is a structured-identifier engine. It does not redact
names or street addresses from free text because they lack a deterministic checksum. DCE provides the
"Deterministic Foundation"—it catches the leakage points that AI systems miss or hallucinate.
1.3 How does "Checksum Cascade" work?
The engine scans for candidate strings and applies a cascade of tests. It validates
Medicare numbers (10-11 digits), TFNs (8-9 digits), ABNs (11 digits), IHIs (16 digits starting with
80036), and several others. It eliminates homoglyphs (e.g., O as 0, S as 5) before verification to
ensure accuracy.
2. Sovereignty: How is zero-retention physically enforced?
2.1 Is the engine truly Stateless?
Yes. The engine runs entirely within transient V8 Isolate memory. It does not
possess a permanent database, persistent logs, or a scratch disk. Once the request lifecycle
completes, the data is computationally destroyed from the isolate's RAM.
2.2 Where is the data processed?
DCE utilizes Jurisdictional Locking. For Australian clients, all
execution and transient data remains strictly within the Oceania (OC) region. No metadata,
telemetry, or PII shards ever leave the Australian jurisdiction.
2.3 Do you have a "Zero-Retention" policy?
We go beyond policy; it is a Physical Constraint. The engine is
hard-coded to return the redacted output and increment a usage counter in KV. It does not store the
original payload. Even if the platform were breached, there is no "historical data" to steal.
3. Valuation: Why is the $1.20 metered rate institutional-grade?
3.1 Why is it $1.20 per call?
The $1.20 valuation is a "Legal Liability Ceiling". By pricing
calls at an institutional utility rate, we establish a high-integrity barrier that prevents
non-institutional utilization and aligns the service with the risk profiles of Medicare and AU-Tax
compliance.
3.2 What happens to my license if I don't use it?
DCE Australia operates on a Standard Recurring Schedule.
Since there are no pre-paid assets to 'expire', your license remains valid as long as the
Sovereign Master Agreement is in effect. Billing only occurs for successful metered calls.
3.3 How do I manage my balance?
DCE utilizes Automated Settlement. Under the Master License, there
is
no need for manual top-ups. Your usage is tracked on a recurring standard schedule, and settlement
occurs automatically via your linked procurement method. This ensures zero downtime and volumetric
compute availability.
4. Compliance: How does TITAN align with MDPR 2026?
4.1 Does this meet the July 2026 Healthcare Mandate?
Yes. Titan V2 is specifically designed for the "Point of
Claim" mandate requiring real-time PII neutralization. Our deterministic accuracy
ensures that Medicare and IHI leakage is physically neutralized before it enters your downstream
analytics or AI training sets.
4.2 What is my "Duty of Care" as a Licensee?
Under the Sovereign License, you host the engine within your private isolate. This
means the Security Responsibility for the incoming data stream transfers to you.
DCE provides the tool; you provide the secure perimeter.
5. Operations: What are the payload and V8 memory limits?
5.1 What are the payload limits?
The default ingestion limit is 40MB per request. This is a
deliberate safety guard to prevent memory exhaustion in the stateless isolate. For larger datasets,
payloads should be chunked into deterministic streams.
5.2 Can I modify the source code?
The Institutional Enterprise License includes Full Source Access.
You have the right to audit, modify, and build upon the core engine logic to meet your specific
internal compliance requirements.
The Titan V2 FAQ provides technical, legal, and operational disclosures for the
Deterministic Compliance Engine. Gated by sovereign finality, this document establishes
the deterministic boundaries of the OMEGA engine, ensuring institutional transparency for
18+ PII types verified under the July 2026 Australian Healthcare mandate.
Return
to Terminal