SOLUTIONS

Solution areas and their workflows

Each solution area corresponds to a workflow in the operator ledger or the verifier portal.

Operator sign-inSign in to the verifier portal
SOLUTION · OPERATORS

CBAM declarations tied to their sources

DAHLIA prepares CBAM emissions data as a sealed evidence package.

SEALED IDENTITYseal format 5
methodology pack
cbam/aluminium-extrusion
version
2027.01.1
effective from
2027-01-01
seal root
bee6d1…937d

The values are read from the synthetic sample package and are not typed onto the page.

  1. 01CURRENT PRACTICE

    Period figures are assembled in spreadsheets and sent as PDFs that do not show which methodology version produced them.

  2. 02WITH DAHLIA

    Measurements are bound at a knowledge time and calculated with the cbam/aluminium-extrusion methodology pack, and the evidence package is sealed.

  3. 03RESULT

    The sealed evidence package carries the value, its lineage and the document digests.

SOLUTION · OPERATORS

Correction record

A correction does not overwrite the earlier record; it is appended to the ledger together with its reason.

THREE TIMES IN THE SYNTHETIC SAMPLE PACKAGE
  1. valid timeMarch 2027

    the period the measurement belongs to

  2. knowledge time30 September 2027

    what the ledger knew then

  3. sealed at1 October 2027

    when the seal root was fixed

The dates are read from the synthetic sample package; the filing-day view is rebuilt from these time axes.

  1. 01CURRENT PRACTICE

    Spreadsheet cells are overwritten; the view of what was known on the filing day is lost.

  2. 02WITH DAHLIA

    Measurements carry valid time alongside knowledge time. Corrections are appended; filing-day views remain reconstructible.

  3. 03RESULT

    The record shows what changed and as of which knowledge time.

SOLUTION · VERIFIERS

Verifier access

The verifier reviews the sealed evidence package without write access to the operator ledger.

ATTESTATION SIGNATURE
signature scheme
Ed25519
accreditation
TR-AK-ORNEK
bound seal root
bee6d1…937d

The values are read from the synthetic sample package. The signature is made on the client and verified on the server; the private key never touches the server.

  1. 01CURRENT PRACTICE

    The same invoice is requested again; a digest field never recomputed from the bytes is trusted.

  2. 02WITH DAHLIA

    Portal access to sealed evidence packages is grant-scoped; the package downloads as JSON and the download is written to the audit log.

  3. 03RESULT

    The verifier's opinion is signed with a key held on the verifier's own machine.

SOLUTION · OPERATORS

Proposal approval

The decision step between a proposal and the ledger belongs to the operator.

THE WRITE PATH
  1. 01proposalthe machine proposes; the ledger does not change
  2. 02approvalan operator accepts or rejects
  3. 03ledgera row is appended only after approval

A proposal enters the ledger only with the operator's approval.

  1. 01CURRENT PRACTICE

    Entry is either entirely manual, or the machine writes to the record without approval.

  2. 02WITH DAHLIA

    Proposals are first held in a staging area. The ledger changes only when an operator approves.

  3. 03RESULT

    A proposal enters the ledger only with an operator's approval.

Workspaces by role

The Operator and Verifier pages show the actions in the daily queue.

Operator pageVerifier page