FRAMEWORK

Primitive Definition Layer

Three atomic primitives: Authority, Agreements, and Rights Accounting, specified before a single line of code. The foundation every implementation must honor.

Request Early Access

The Primitive Definition Layer / 01

Different category, not faster execution.

Traditional finance and blockchain both run economic activity as a chain of operations spread out over time. Conduit commits three primitives in one atomic step. Everything downstream stops being an operation.

time
Sign the agreement days–weeks
Verify the parties compliance check
Move the rights T+1, custodian
Settle the payment same day
Reconcile the books end of day
after the fact

Calculate risk

Exists because the rights state is spread across systems.

after the fact

Resolve disputes

Exists because records disagree across custodians, ERPs, and contracts.

one atomic event
Authorityprovenance proof
Agreementsstate machine
Rights Accountingrights movement
Under 100ms
Primitive Definition Layer
The Primitive Definition Layer

Settlement

→ part of the atomic operation

Reconciliation

→ nothing to reconcile

Risk

→ query the current state

Dispute resolution

→ query the event store

SequentialTradFi and blockchain
chain of operationsone atomic step
AtomicConduit

Operations that stop being operations.

The downstream work does not disappear as a concept. With the three primitives committed atomically, each one follows as a consequence of the atomic state or reduces to a query against it.

Settlement
part of the atomic operation
Reconciliation
nothing to reconcile
Risk
query the current state
Dispute resolution
query the event store

The Primitive Definition Layer / 01

Different category, not faster execution.

Traditional finance and blockchain both run economic activity as a chain of operations spread out over time. Conduit commits three primitives in one atomic step. Everything downstream stops being an operation.

Sequential: TradFi and blockchain

  1. Sign the agreementdays–weeks
  2. Verify the partiescompliance check
  3. Move the rightsT+1, custodian
  4. Settle the paymentsame day
  5. Reconcile the booksend of day
one atomic event
Authorityprovenance proof
Agreementsstate machine
Rights Accountingrights movement
Under 100ms
Primitive Definition Layer

Downstream operations become

Settlement→ part of the atomic operation
Reconciliation→ nothing to reconcile
Risk→ query the current state
Dispute resolution→ query the event store

A different category of transaction, not an optimization of the old one.

Under the Primitive Definition Layer, the transaction stops being a sequence of independent steps and becomes three primitives executed atomically as one operation.

The three primitives.

Primitive 01

Rights Accounting

A graph-based ledger of who holds what, expressing each party's position as decomposable economic rights.

Primitive 02

Authority

A cryptographic proof of permission to act, bound to scope, principal, and delegation chain.

Primitive 03

Agreements

State machines that express what parties agreed to and the transitions available under the agreement.

Where this layer fits in the stack.

Specifications live in the Primitive Definition Layer, hardware-anchored implementation in the Trusted Execution Layer, and the deployed network in the Economic Network Layer.

  1. Layer 1

    Primitive Definition Layer

    Specifications, patterns, standards, and DSLs that express Authority, Agreements, and Rights Accounting.

  2. Layer 2

    Trusted Execution Layer

    Two halves: hardware enforces the atomic boundary, software conforms to the specification. Both required.

    Hardware

    Conduit-Compliant Appliance

    Software

    Conduit Software

  3. Layer 3

    Economic Network Layer

    The privacy-preserving counterparty-oriented temporal ledger that emerges from many distributed appliances under aligned incentives.

See the Trusted Execution Layer

Maximizing the velocity of capital.

Private Alpha. Access by invitation.

Request Early Access