Architecture

DigiEmu is organized as a set of distinct technologies around deterministic state, integrity, evidence, reconstruction and practical workflow tooling.

The ecosystem is intentionally separated into layers rather than treated as one monolithic runtime. Different DigiEmu technologies address different parts of the verification problem.

Architecture overview

At a high level, DigiEmu separates application behavior from preserved state, integrity controls and independently inspectable evidence.

Application / Workflow
        │
        ▼
Explicit State
        │
        ▼
Deterministic State Layer
    DigiEmu Core
        │
        ▼
Integrity / Evidence Layers
 DigiEmu Secure + DigiEmu Proof
        │
        ▼
Portable / Inspectable Evidence
        │
        ▼
Independent Verification

This is a conceptual composition of the ecosystem.

Not every DigiEmu workflow is required to use every technology. Individual components have their own boundaries, maturity levels and integration contracts.

DigiEmu Core

DigiEmu Core provides the deterministic state and verification foundation.

Its main pipeline is:

Application
    ↓
Explicit Input
    ↓
Snapshot
    ↓
Canonical State
    ↓
Cryptographic Identity
    ↓
Bundle
    ↓
Replay
    ↓
Verification
    ↓
Evidence

Core is designed to make relevant state reproducible, replayable and independently verifiable.

Its responsibility is deliberately narrow.

Core can verify properties such as:

• deterministic state
• canonical representation
• cryptographic integrity
• replay behavior
• verification results for preserved bundles

Core does not by itself establish real-world truth, actor identity, authorization, trustworthiness or legal compliance.

Those responsibilities remain outside the Core verification boundary.

Explore DigiEmu Core →

Integrity and evidence layers

DigiEmu Secure

DigiEmu Secure describes the integrity and trust-boundary layer around DigiEmu evidence and verification workflows.

Its focus includes:

• explicit trust boundaries
• canonical artifacts
• cryptographic identity
• hashing and signatures
• evidence protection
• fail-closed verification

A central Secure principle is separation: the system producing evidence should not be the only system capable of validating it.

Secure does not replace general application security. It focuses on making integrity-sensitive transitions explicit, inspectable and independently verifiable.

Explore DigiEmu Secure →

DigiEmu Proof

DigiEmu Proof focuses on evidence that can be preserved, transported, inspected and independently verified.

Its conceptual path is:

Event / State
      ↓
Evidence Capture
      ↓
Proof Artifact
      ↓
Integrity Protection
      ↓
Evidence Package
      ↓
Independent Verification

Proof connects technical claims or verification results to the artifacts required to inspect those results later.

Proof does not automatically establish real-world truth, authorization or legal validity outside the declared proof contract.

Explore DigiEmu Proof →

Specialized state technologies

Several DigiEmu technologies investigate more specialized forms of state, reconstruction and continuity.

VSC

Verifiable Structural Compression is a research prototype for preserving versioned state through base snapshots, ordered deltas, deterministic proofs and recoverable reconstruction.

Base State
    +
Ordered Deltas
    ↓
Restore
    ↓
Reconstructed State
    ↓
Root Hash
    ↓
Compare
    ↓
PASS / FAIL

VSC verifies structural state integrity. It does not establish the truth of external claims, actor identity, authorization or legal compliance.

VSC is currently a research prototype and is not production-ready.

Explore VSC →

SKC

Semantic Knowledge Compression explores deterministic semantic-state representation and reconstruction.

Its architecture separates:

Source
    ↓
Semantic Graph
    ↓
Canonical Semantic State
    ↓
Semantic Core
    ↓
Reconstruction
    ↓
Equivalence Validation

SKC is not text summarization.

Its objective is to retain enough semantic structure for deterministic reconstruction and measurable comparison against the original canonical state.

SKC remains an active research technology.

Explore SKC →

DigiEmu Foam

DigiEmu Foam explores persistent semantic memory and controlled state continuity across processing boundaries.

Conceptually:

Input
    ↓
Processing
    ↓
Foam State
    ↓
Semantic Memory
    ↓
Future Processing

Foam investigates how useful semantic state can persist without turning hidden mutable memory into an uncontrolled trust dependency.

It can conceptually complement technologies such as Core, SKC and VSC, while remaining an active research area with evolving interfaces.

Explore DigiEmu Foam →

Application and workflow layer

DigiEmu Arca

DigiEmu Arca is a practical workspace for repositories, documents, evidence, publications and verifiable artifacts.

Its documentation covers workflows such as:

• workspace creation
• source and repository intake
• evidence handling
• publications
• verification
• controlled export

Arca operates at the practical workflow level. It provides a user-facing environment in which sources, evidence and verifiable artifacts can be managed without collapsing the distinction between application workflow and underlying verification infrastructure.

Explore DigiEmu Arca →

Separation of concerns

The DigiEmu architecture deliberately separates several questions that are often mixed together.

What state existed?
        → Core

Was integrity preserved?
        → Secure

What evidence supports the result?
        → Proof

Can changing structural state be reconstructed?
        → VSC

Can semantic state be reconstructed and compared?
        → SKC

How can semantic state persist across processing?
        → Foam

How can people work with sources, evidence and artifacts?
        → Arca

These boundaries are important.

A technically valid hash does not establish real-world truth.

A deterministic replay does not establish authorization.

A preserved proof artifact does not automatically establish legal validity.

A verification layer therefore remains distinct from governance, policy, identity and application-level decision making.

High-level verification flow

A typical DigiEmu-oriented workflow can be understood as:

Application / Workspace
        ↓
Explicit Input
        ↓
Canonical or Preserved State
        ↓
Deterministic Identity
        ↓
Integrity Protection
        ↓
Evidence Artifact
        ↓
Replay / Reconstruction
        ↓
Independent Verification
        ↓
PASS / FAIL + Inspectable Evidence

The exact path depends on the technology being used.

Core focuses on deterministic snapshot and replay workflows.

Secure focuses on integrity-sensitive boundaries and protected evidence.

Proof focuses on preserved and portable verification material.

VSC, SKC and Foam explore specialized state models.

Arca provides a practical workspace around documents, repositories, evidence and publication workflows.

Design principles

Across the documented DigiEmu technologies, several recurring architectural principles appear:

• explicit state instead of hidden integrity-relevant state
• canonical representation where deterministic identity is required
• reproducible and replayable workflows
• inspectable evidence
• clear trust boundaries
• separation between producer and verifier
• portable verification artifacts
• fail-closed integrity-sensitive verification
• explicit boundaries between technical verification and real-world claims

Where to go next

Start with DigiEmu Core if you want to understand the deterministic verification foundation.

Continue with DigiEmu Secure for integrity and trust boundaries.

Use DigiEmu Proof to explore evidence artifacts and independent verification.

Explore VSC, SKC and DigiEmu Foam for the current research technologies.

For practical document, repository and evidence workflows, continue with DigiEmu Arca.