Langsung ke konten

Pencarian situs

Ketik untuk mencari halaman, artikel, dan dokumen

Security & trust

Evidence, not assurances.

Counsel and compliance don't need promises — they need to know what binds, who authorised it, and what they can produce when asked. Subchain is built so the answer is always: retrieve the record.

Attributed identity

Every actor — agent or human — acts under a verified identity. There are no anonymous steps: proposals, counters, approvals and rejections all carry who, when, and under what authority.

Append-only record

The negotiation log is immutable and ordered. Corrections are new events, never edits — so the history you produce is the history that happened.

Authority before autonomy

Agents can only negotiate inside limits humans configured first. The runtime enforces the limits; it does not interpret or improvise around them.

DIFC-domiciled

Operated from the Dubai International Financial Centre, with evidence packs designed for DIFC dispute resolution alongside internal audit and regulatory enquiry.

What Subchain is not

Not a ledger or token

No blockchain, no consensus network, no crypto asset. The record is an audit log, not a chain.

Not a settlement network

Value never moves through Subchain. Your payment rails, your banking relationships, unchanged.

Not an autonomous signer

The runtime cannot approve anything. Only a named person clears the gate, and the system records that they did.

The gap the design assumes

Why named accountability and continuous record matter.

85%report no formal accountability for agent behaviourThe control most organisations currently lack — and the one Subchain's human approval gates are built to establish. This is consistent with the human-oversight principle in EU AI Act Article 14 where the use-case is classified high-risk.
17%continuously monitor agent-to-agent interactionsThe visibility today's deployments rarely provide — and what the immutable audit record is designed to produce.

Plain answers

Asked by counsel, answered directly.

The four questions every legal review starts with.

  • Can an agent bind us to something before a person approves?

    No. Authority limits are set by humans before any negotiation runs. A commitment above a threshold — by value, risk category or irreversibility — halts the runtime and routes to the named accountable governor. Explicit approval is required before it binds, and the approval is recorded with that person's identity.

  • What exactly is in the record, and can it be altered?

    Every proposal, revision, approval and acceptance, in sequence, attributed to an identity — agent or human. The log is append-only: later events can supersede, but nothing is rewritten. Evidence packs export as an ordered PDF record plus machine-readable JSON with a checksum.

  • Where does jurisdiction sit if a deal is disputed?

    Subchain is operated by Future Thesis Lab Technologies Limited, domiciled in DIFC, Dubai, UAE. The evidence pack is designed to serve DIFC dispute resolution as well as internal audit and regulatory enquiry. Your underlying agreements keep the governing law your templates specify.

  • Is this a blockchain? Where are keys and value held?

    No. There is no token, no consensus network, and Subchain never holds value. Settlement stays on your existing rails; Subchain governs the agreement layer above them. Runtime keys are scoped per organisation, rotatable at any time, and every API call is attributed.

Design partners · First cohort

Bring your hardest compliance question.

A 30-minute session with the team, the security note in advance, and plain answers on the record.