Layer 1 Overview · Agreement Ledger · 0.0.41

Keep the path to agreement
as visible as the agreement itself.

An agreement ledger is a structured history of the material people used to reach an agreement: propositions, sources, questions, party positions, consent conditions, and revisions. It makes room for different understandings while consolidating only the terms people have explicitly accepted.

What the ledger means

A claim is recorded with its status, preserving context and provenance.

The ledger records whether an item is a claim, a reference, an assumption, a condition, an accepted term, or an unresolved question. Recording an assertion preserves its provenance without automatically promoting it to universal fact.

Each party attaches their own relationship to an item: accepted, qualified, contested, under review, or out of scope. The shared agreement is then compiled from declared consent.

What it holds

Material

Claims, references, evidence, definitions, assumptions, and relevant versions.

Perspectives

What each party understands, accepts, qualifies, questions, or declines.

Consolidation

The terms that reached the stated M-of-N consent threshold, plus dissent and open items.

Receipts

The version of the agreement and instrument used for each bounded execution.

Layer 2 · Illustrative Ledger

A multi-party agreement with preserved party perspectives

Three parties are defining a shared procedure for a local community referral tool, recording which terms are accepted, qualified, or still open.

01 · Referral information

accepted

Claim / service criteria v3

A referral should contain declared contact and consent fields before it can be reviewed.

Resident group: accepted if missing fields are explained plainly.

Service: accepted.

Worker: accepted.

02 · Sensitive situations

qualified

Condition / consent guidance

Some situations need person-to-person review rather than a prepared referral alone.

Resident group: accepts, asks for clear escalation.

Service: accepts, names review pathway.

Worker: accepts with professional discretion.

03 · Eligibility language

open

Scope question / no shared term yet

Should the tool state whether someone is eligible for a service?

Resident group: prefers no automated eligibility label.

Service: wants the matter reviewed later.

Worker: says eligibility needs human assessment.

Consolidated agreement

Only accepted terms become the shared procedure

Terms ready to package

  • Check whether the declared referral information is present.
  • Explain missing information in clear language and hold the record until it is supplied.
  • Route sensitive situations to a named human-review path.
  • Record the policy version and the outcome of the bounded preparation step.

Items retained, not erased

  • The open question about automated eligibility language.
  • The resident group's request for plain-language explanations.
  • The worker's qualification that sensitive cases need professional discretion.
  • The source versions and each party's recorded position.

Layer 3 & 4 · Formal Specification · Identifier Fabric (IDF-01–IDF-05)

How the Agreement Ledger Maps to the Four-Plane Identifier Fabric

Under the hood, QualiaDB stores agreement ledger entries as 48-byte NQuin records in the EnforceBilateralMicroCommons routing lane (AgreementDID::compile_to_super_quins), gated by the SuspendedTransactionQueue for M-of-N consensus ratification and author-scoped Ed25519/ML-DSA-65 Merkle roots (compute_scoped_merkle_root). Every record is validated against ontologies/identifier_fabric_shapes.ttl across four disjoint planes:

1. Entity (Who Plane)

Signatories and represented principals: NaturalAgent (living-SHACL), LegalEntity, and SystemAgent. Never merged by similarity, handle, wallet, location, or biometrics; owl:sameAs is forbidden on the Who plane (SameAsError::WhoPlaneForbidden).

2. Claim Plane

Ledger propositions, qualifications, and liability traces (VerifiableCredential, idf:ClaimOpinion, idf:AssertionClaim, idf:RelianceRecord, idf:AssumptionChain, idf:RootCauseBundle, idf:BlastRadiusMap, and deontic/epistemic norms). VCs prove cryptographic origin integrity of an issuer's statement, not universal ontological truth.

3. Handle Plane

Revocable, rotatable network or directory locators (idf:SpatiotemporalHandle, DNI / idf:DigitalNetworkIdentifier, idf:RelationScopedLocator, DNS, email, did:qi endpoints). Revoking a handle closes the channel without erasing the Entity or historical agreement receipts.

4. Instrument Plane

Cryptographic keys, M-of-N idf:CoAttestationBundle records, hardware tokens, and software tools (idf:Instrument, idf:AiAgent) classified by InstrumentProofClass (CryptographicOriginIntegrity, HardwareChannelPossession, SemanticClaimEvaluation) and closed KeyRole (IdentityAssertion, CredentialSigning, TransportHandshake, StorageEncryption, RecoveryBootstrap).

Typed Cross-Plane Evidence Morphisms

@prefix idf: <urn:qualia:idf:> .

ex:referral-term-01 a idf:ClaimOpinion ;
    idf:plane "Claim" ;
    idf:assertedBy ex:resident-group-principal ;
    idf:aboutSubject ex:referral-procedure-v3 ;
    idf:assertedAbout ex:referral-procedure-v3 ;
    idf:supportedByInstrument ex:co-attestation-2of3 ;
    idf:observedAtHandle ex:relation-scoped-locator-01 .

F5 & F6 Anti-Feature Firewalls

Both the F5 (compile-time VibeScript) and F6 (runtime ingress/query) firewalls reject person_score, identity_confidence, and same_person, ensuring that agreement ledgers never collapse party positions or compute hidden reputational scores.

# Co-attestation requires >= 2 members & closed KeyRole (IDF-01)
idf:CoAttestationBundleShape a sh:NodeShape ;
    sh:targetClass idf:CoAttestationBundle ;
    sh:property idf:CoAttestationBundle-memberProp ;       # sh:minCount 2
    sh:property idf:CoAttestationBundle-timeIntervalProp ; # sh:minCount 1
    sh:property idf:CoAttestationBundle-keyRoleProp .

The semantic instrument

Makes the consolidated procedure runnable

The resulting instrument accepts a declared referral record, checks only the shared conditions, returns ready, held, or needs human review, and writes a receipt bounded by the agreement label.

The agreement ledger

Keeps the instrument accountable to its origin

A later reader can see which version, parties, sources, consent threshold, qualifications, and open questions shaped the instrument. A new agreement creates a new version while preserving the historical context of earlier runs.

Continue

Explore the agreement-to-instrument model

Read the broader explanation of how a multi-party agreement becomes a declared, bounded Semantic Instrument — then return to the instrument playground to try defining one.