Trisilva Docs

Two bodies of documentation sit here. The standard says what an insurance policy, a claim or a receipt is, and how a caller asks for one. The platform documentation says how Trisilva implements that standard, and what a tenant, a region and an audit record mean on our side of the boundary. The standard is open and governed in public, so a third group below covers how it changes and where to argue with it.

Where to start

The open standard

Insurance conceptsThe vocabulary every module assumes: the parties, the policy, the money, the claim. Start here if you are good at software and new to insurance. The standardWhat the open standard covers across twelve modules, what it leaves to the market, and where to look up an entity or a field. Build an integrationThe rules that apply on every call: authentication, the error model, pagination and idempotency. Then tenancy and scopes, for what a credential may reach. Vietnam profileWhat this market requires that others do not, and why the profile is deliberately thin.

The platform

ArchitectureHow the platform is put together: two deployment planes, six services, and why the split decides everything else. The integration surfaceOne generated contract, the clients and tools derived from it, the event stream, and the agent surface that shares its authorisation model. Design decisionsWhat each architectural choice cost, because a decision recorded without its cost is a decision nobody can argue with. Engineering standardsThe gates every change passes before it merges, and what they do not cover.

Governance

Propose a changeWho decides what changes, how to argue against a decision, and where that argument happens. CommunityWhere a defect gets raised, without any relationship with Trisilva. The standard is open and so is its issue tracker.

The three tiers

The platform is built on three layers, and each one strictly extends the layer below it. Nothing in a higher tier redefines a term the tier below already settled.

Tier	What it is	Who authors it
Baseline	The OPIN data standard and API design. The shared vocabulary for parties, products, coverage, claims, premium and receipts.	Trisilva, published open. Originated by the Open Insurance Initiative
Market profile	What one national market requires that a global standard cannot decide for it. Vietnam is the first profile.	Trisilva, published as an open profile
Platform	The Trisilva implementation: multi-region topology, tenancy and scopes, the audit log, the document service.	Trisilva

The first two tiers are open, and they are developed in public at github.com/trisilva/opin under MPL 2.0. You can read them, build against them, and report a defect without any relationship with Trisilva. That is deliberate. A standard that only one vendor can see is not a standard.

The third tier is ours. It is described here in full because the architecture is not the moat, but it is not open source and it is not governed by the process the standard is governed by.

How to read this

Conventions applies to every module, so read it before the module you are working in. Motor is worth reading even if you are not building motor, because every other module’s surface mirrors the shape declared there.

On the platform side, read Architecture first. Tenancy, regions and documents are each a consequence of the two-plane split it describes, and none of them reads correctly on its own.

Read Scope and design before you commit to anything. It draws the boundary of the standard, including what it will never cover.

If a question is specific to your integration, talk to us. A document answers the general case and a person answers yours.