Governed intelligence
for decisions that matter

Document analysis, evidence and governance in one platform. Every execution declares its perimeter, its limits and its verifiable trace.

Request information
  • From document to evidence

    Traceable analysis, not an opaque answer

  • Governed by construction

    Control precedes execution, it does not follow it

  • Built for organisations

    Isolation, roles and revocation enforced server-side

The sequence

A complex case file

1 / 9

Hundreds of pages, multiple sources, no quick way to verify them.

Illustrative representation of the model. Not a real session.

R-TITAN
  • Multi-agent
  • Governance
  • Assurance
  • Traceability
  • Security

Product preview

Multi-agent analysis

Specialised agents working on the same corpus

Governance

Policies applied before execution, not after

Security

Isolation, roles and revocation enforced server-side

Assurance

Verified outputs, traceable back to the source

Three tools, one control structure

Every service applies the same principles: perimeter declared before execution, source traceability, and the system's right to state that it cannot conclude.

Operational mandate library

Eight predefined instructions for the analysis of case files and complex documentation. These are not generic requests: each mandate states what it produces, what it authorises, what it does not authorise, and under which conditions the system must abstain.

  • Timeline reconstruction, contradiction matrix, documentary basis for a pleading
  • Claim verification against the corpus: supported, contradicted or undeterminable
  • Version comparison, regulatory mapping, compliance audit, Red Team against your own position
Mandates available
8
Versioning
Identifier and version in the receipt
Abstention
Declared for each mandate
Browse the mandate libraryAccess the service

Governed translation

Governed translation with a catalogue of 24 selectable European languages, governed by seven constitutional principles of the project. Engine availability is checked in the console; professional language qualification remains pending. The result is not only the rendered text: it is a file preserving the source, terminology choices and terms without functional equivalent across legal systems.

  • Where an institute has no functional equivalent, the original term is preserved and explained rather than replaced with the nearest match
  • Names of judicial bodies, case numbers and statutory references remain in their original form
  • A rendering may neither add precision absent from the source nor reduce the source's precision
Target languages
24 European options
Model
Gemini on Vertex AI, EU region
Framework applied
CE-I, seven articles
R-TITAN · Console24 languages
Actual governed translation screen: SELENE document and catalogue of 24 selectable languages
From the actual console · synthetic SELENE document. Source, language and domain remain explicit.

Normattiva linking

From a statutory reference to the official text, through a permanent link built on the public URN-NIR standard. This is not a search across private databases: the user lands on the institutional portal, where verification remains theirs.

  • Codes and fundamental texts recognised through a verified correspondence table
  • Ordinary acts built from type, date of enactment and number
  • No content extraction from third-party sources: links to the official source only
Standard
URN-NIR, permanent
Version referenced
Consolidated or original text
Source
Normattiva, official portal

Three modes, one control structure

The profile determines how much autonomy is granted and which controls apply. Commercial names are readable; technical identifiers are never translated.

Select a mode to see how a request is handled.

Request path

GOVERNED_STANDARD
  1. 1RequestRelevant action on the authorised corpus
  2. 2GatewayRule applied: review is required
  3. 3ReviewerHuman decision, requester excluded
  4. 4ExecutionHeld pending the decision
REQUIRE_REVIEW

No automatic execution. Review does not override a runtime constraint.

Illustration of the governance model. Not a real session, and not execution data.

Four possible outcomes, all stated

No request ends in silence. Every decision is shown for what it is, with its reason.

Allowed

ALLOW

The action proceeds within the authorised perimeter. It is not a judgement on the quality of the result.

Review required

REQUIRE_REVIEW

A human decision is needed before proceeding. No automatic execution.

Denied

DENY

The action is blocked. No automatic downgrade to a less controlled profile.

Abstention

ABSTAIN

The system states it cannot conclude. A valid outcome, shown as such.

From upload to evidence

Storage, technical admission and analysis authorisation remain three distinct steps.

  1. 1UploadThe file enters a separate private area. The server computes the digest of the bytes it received.
  2. 2QuarantineNo processing until checks on type, size and content are complete.
  3. 3AdmissionThe document becomes available only after those checks. If a check does not respond, it stays out.
  4. 4Authorised analysisExecution starts only with profile, perimeter and limits declared in advance.
  5. 5EvidenceEvery execution leaves a verifiable trace, including when it ends in an error or an abstention.

What we guarantee, and what we don't

A governance product loses its point if it promises more than it can demonstrate. This section stays by choice, not by obligation.

Principles applied to the platform

  • Tenant isolation enforced on the server, not only in the interface.
  • Private archive: no document is reachable without a current authorisation check.
  • Gateway decisions cannot be rewritten by the web layer.
  • Documents and email treated as untrusted data: they do not alter instructions or permissions.

Stated limits

  • This is a product preview. The content of the demonstrations on this page does not come from real executions.
  • The connectors in the «Ecosystem» section are planned and start disabled.
  • No compliance certification is claimed or implied.
  • A cryptographic digest proves byte correspondence, not publisher identity.

Verifiable evidence

Discover the evidence verification method, the tests already performed and the functions still being integrated.

Integrations

Tools connected to R-TITAN, brought together in the console with explicit authorisation and human control.

Gmail

Read authorised communications, with user control over the sources.

Configured

PEC

Acquire certified email communications within the authorised scope.

Configured

Google Drive

Connection to user-selected TXT files, with explicit version and retention.

Configured

Brevo

Transactional email, with the recipient and content subject to authorisation.

Configured

Document AI

Document OCR acquisition, with a preview and review against the original pages.

Configured

DSS

Verify document digital signatures and inspect the corresponding evidence.

Configured

Open the console

This catalogue presents configured integrations. Availability, authorisation and the outcome of each operation are checked in the console.

Let's talk about your use case

R-TITAN is in active development. Get in touch for project updates or to discuss a specific application within your organisation.

Email R-TITAN

We answer qualified enquiries within a few working days.

Company
EDT R-TITAN
Product
R-TITAN — governed document analysis platform