ISETGovernance
Governance · accountability · proof

Infrastructure that proves itself — before anyone has to trust it.

The registry asks institutions to run their trade on it. That invitation only means something if the registry can be checked — its keys published, its audit chain verifiable, its capabilities reported honestly, its legal posture stated plainly. This page is that check.

The five proofs

How ISET is held accountable.

Not policy promises — mechanisms that anyone can exercise, most of them keyless.

Key transparency

Published signing keys

Every record is signed with ML-DSA-65 (NIST FIPS 204). The verifying key is published at a well-known location with fingerprint 6f7a09c2 8760bff1, so any party can independently verify signatures without asking ISET. Key rotation follows the published crypto-suite registry — quantum-agile by design, never silent.

/.well-known/ml-dsa65-public.json · /.well-known/crypto-suite.json
Audit by anyone

A hash chain, re-verified on read

Every lifecycle event is written to a hash-chained audit ledger — and the chain is re-verified every time an audit record is read, not just when it is written. Tampering breaks the chain loudly. Audit evidence is structured for court admission.

GET /api/audit/{audit_id}
Honest capabilities

Never a fabricated pass

The capabilities manifest publishes every capability area with its provider and status. An unconfigured provider answers NOT_CONFIGURED — the system reports what it cannot do instead of pretending. This principle is enforced in code, not in marketing.

Consent-first data

RA 10173, carried at every stage

Personal data is processed under the Data Privacy Act with consent attached to the record at every lifecycle stage. Performance ratings draw only from signed transaction history, under consent — never from behavioral inference.

Privacy notice: /privacy/
Law-embedded posture

The categories are enforced, not suggested

Only the four negotiable classes cite the UNCITRAL Model Law, always as MLETR-aligned — the Model Law is not enacted in the Philippines. A credit is an undertaking, an invoice a perfected receivable, a certificate an attestation. The register refuses unlawful moves with a 403 before the engine sees them.

RA 8792 · RA 11057 · UCP 600 · eUCP 2.1
Non-custodial by architecture

Nothing to steal, nothing to lend

ISET holds no client funds — settlement happens on counterparties' own rails and the register records the signed proof. The strongest custody control is not needing one: there is no float, no wallet, no deposit book to attack or mismanage.

Legal notices: /terms/ · registry posture in the site footer
FOR REGULATORS AND INSTITUTIONS — Verification of any record is keyless and public: GET /api/etr/verify/{reference}. The sandbox (/sandbox/) exposes the full enforcement surface read-only with no signup, including the refusal gallery of unlawful moves. Supervisory and counterparty inquiries: /contact/ — engagement requires bilateral counterparty arrangement; nothing on this site is an offer to the public.