DigiEmu Core 2.0

DigiEmu Core 2.0 defines a deterministic decision-state verification layer for AI governance, replay, interoperability, and audit evidence.

This release establishes DigiEmu as a bounded verification layer: it produces canonical decision-state artifacts, replay evidence, hash references, and structured verification reports, while explicitly avoiding claims about agent identity, trust certification, legal liability, regulatory approval, or full system safety.

Release status

• Branch: main
• Tag: core-2.0.0
• Test status: go test ./... passed

Highlights

• Core 2.0 interoperability boundary
• Deterministic decision-state verification scope
• PASS / FAIL preservation rule with structured report references
• External system non-redefinition rule
• External review note for partners and auditors
• TBN / trust boundary example
• AntifragileOS before-splice example
• Minimal interop example package
• README links for external reviewers

New materials

• docs/CORE_2_INTEROP_CONTRACT.md
• docs/CORE_2_EXTERNAL_REVIEW_NOTE.md
• examples/interop/README.md
• examples/interop/digiemu_snapshot.json
• examples/interop/digiemu_verification_report.json
• examples/interop/tbn_receipt_reference_example.json
• examples/interop/antifragile_before_splice_example.json

Boundary principle

One state identity is produced under one declared DigiEmu canonicalization profile by one accountable state producer.

External systems may carry this identity.

External systems do not compute, redefine, or overwrite this identity.

Non-claims

DigiEmu Core 2.0 does not claim to provide:

• agent identity verification
• agent certification
• trust-tier assignment
• legal liability attribution
• regulatory approval
• moral judgment
• model alignment guarantees
• full system safety guarantees

DigiEmu Core 2.0 should be reviewed as a deterministic decision-state verification layer, not as a complete trust, identity, liability, compliance, or safety system.

The boundary is the value.

DigiEmu Core 2.0 Draft 4 Self-Audit

This release marks a documentation hardening and self-audit checkpoint for DigiEmu Core 2.0.

It adds:

• Core 2.0 verification boundary clarification
• Threat Model boundary addendum
• Conformance documentation
• Andrei-oriented requirements traceability
• Go module / release tagging safety documentation
• Clear separation between DigiEmu Core and external trust / attestation layers such as TBN

DigiEmu Core verifies deterministic decision-state integrity through canonical JSON, SHA-256 snapshot hashing, and replay/verify checks.

It does not certify agent identity, trustworthiness, authorization, action legitimacy, or legal compliance.

Checks completed:

• go test ./... passed
• go vet ./... passed
• Core 2.0 conformance report: 11/11 passed

Important release note:

This is not a real Go v2.0.0 tag.
Do not use real Git tags starting with v2.0.0 unless the Go module path intentionally ends in /v2 and all internal imports are updated accordingly.

What's Changed

• docs: add Core 2.0 actual-vs-expected comparison design by @DigiEmu in #67
• feat: add Core 2.0 observed-vs-expected comparison helper by @DigiEmu in #68
• feat: integrate Core 2.0 observed-vs-expected comparison in runner by @DigiEmu in #69
• test: add Core 2.0 unsupported canonicalization profile conformance case by @DigiEmu in #70
• docs: add Core 2.0 post-draft.3 hardening summary by @DigiEmu in #71
• docs: mark MISSING_REFERENCE conformance case as pending by @DigiEmu in #72
• docs: add Core 2.0 MISSING_REFERENCE schema consideration by @DigiEmu in #73
• docs: add Core 2.0 Draft 4 readiness notes by @DigiEmu in #74

Full Changelog: v2.0.0-draft.3...v2.0.0-draft.4

Contributors

• @DigiEmu

What's Changed

• docs: add Core 2.0 partner handoff package for v2.0.0-draft.2 by @DigiEmu in #58
• docs: add Core 2.0 partner feedback intake process by @DigiEmu in #59
• docs: add Core 2.0 Draft 2 review summary by @DigiEmu in #60
• test: expand Core 2.0 conformance pack edge cases by @DigiEmu in #61
• docs: add Core 2.0 reason code review by @DigiEmu in #62
• docs: add Core 2.0 runner execution design by @DigiEmu in #63
• feat: parse Core 2.0 conformance input JSON in runner by @DigiEmu in #64
• test: cover missing Core 2.0 conformance case files by @DigiEmu in #65
• docs: add Core 2.0 Draft 3 readiness notes by @DigiEmu in #66

Full Changelog: v2.0.0-draft.2...v2.0.0-draft.3

Contributors

• @DigiEmu

Summary

This release marks the second DigiEmu Core 2.0 draft milestone.

v2.0.0-draft.2 builds on v2.0.0-draft.1 and adds repository-level visibility and CI validation for the Docker-based Core 2.0 conformance path.

This is a draft/pre-release milestone, not a stable Core 2.0 release.

Status

• Draft release
• Pre-release
• Partner-testable
• Docker-CI validated
• Not stable Core 2.0
• v1.0 behavior remains unchanged
• Experimental Core 2.0 commands remain under the experimental namespace

Added since v2.0.0-draft.1

• README alignment for the Core 2.0 draft milestone
• Docker conformance path validation in GitHub Actions
• Docker build validation in CI
• Docker human-readable conformance run in CI
• Docker JSON conformance run in CI
• Go builder version fix for Docker compatibility

Core 2.0 Draft Capabilities

• Experimental conformance CLI
• Human-readable conformance output
• Machine-readable JSON conformance reports
• Conformance report schema
• Schema validation tests
• OpenAPI contract draft
• OpenAPI structural validation test
• Docker usage path
• Docker CI validation
• CI conformance checks
• Partner integration notes
• Compatibility matrix
• Release checklist and tagging plan

Validation

Before tagging, the following checks passed:

go test ./...
go run ./cmd/digiemu experimental conformance run testdata/core_2_conformance
go run ./cmd/digiemu experimental conformance run testdata/core_2_conformance --json

Expected human-readable output:

Conformance run summary: total=3 passed=3 failed=0

Expected JSON report fields:

{
 "report_version": "core-2-conformance-report-v1",
 "status": "PASS",
 "total": 3,
 "passed": 3,
 "failed": 0
}

Compatibility

• No v1.0 behavior changed
• No snapshot hash behavior changed
• No stable Core 2.0 CLI promotion
• No HTTP API server implemented
• No signing, key custody, orchestration, authentication, tenancy, or policy judgement added

Notes

This release creates a stronger review point for partners and future integration work.

v2.0.0-draft.2 should be used as the current Core 2.0 draft reference for Docker-based partner evaluation.

Summary

This release marks the first partner-testable DigiEmu Core 2.0 draft milestone.

v2.0.0-draft.1 is a draft milestone, not a stable Core 2.0 release.

Status

• Draft release
• Partner-testable
• Not stable
• Experimental Core 2.0 surfaces remain under the experimental namespace
• v1.0 behavior remains unchanged

Included

• Core 2.0 boundary model
• Core 2.0 hardening plan
• Crypto agility draft
• Migration from v1 guidance
• Verify Result v2 draft
• Reason codes registry
• Verify Result v2 JSON Schema
• Verify Result v2 examples
• Profile registry
• Conformance pack
• Hash boundary vectors
• Canonicalization audit and decision record
• Canonicalization behavior tests
• Conformance runner MVP
• Experimental conformance CLI
• Human-readable conformance output
• JSON conformance report output
• Conformance report schema
• Schema validation tests
• OpenAPI contract draft
• OpenAPI structural validation test
• Docker usage path
• Partner integration notes
• Compatibility matrix
• Release checklist
• Tagging plan
• CI conformance checks

Validation

Before tagging, the following checks passed:

go test ./...
go run ./cmd/digiemu experimental conformance run testdata/core_2_conformance
go run ./cmd/digiemu experimental conformance run testdata/core_2_conformance --json

Expected conformance output:

Conformance run summary: total=3 passed=3 failed=0

Expected JSON report fields:

{
 "report_version": "core-2-conformance-report-v1",
 "status": "PASS",
 "total": 3,
 "passed": 3,
 "failed": 0
}

Compatibility

• No v1.0 behavior changed
• No snapshot hash behavior changed
• No stable Core 2.0 CLI promotion
• No HTTP API server implemented
• No signing, key custody, orchestration, authentication, tenancy, or policy judgement added

Notes

This tag creates a reproducible review point for partner testing, technical review, and future Core 2.0 hardening.

This is the first official DigiEmu Core 2.0 draft marker for the partner-testable milestone.
are/v1.0.0...v2.0.0-draft.1

Summary

DigiEmu Core v1.0.0 establishes the baseline for deterministic knowledge snapshot infrastructure.

This release introduces a foundational system for creating, transporting, replaying, and verifying deterministic knowledge bundles with integrity-oriented semantics.

Core capabilities

• deterministic snapshot engine
• replay verification
• bundle verification
• cryptographic bundle signatures
• trusted identity layer
• identity fingerprinting
• portable bundle transport

Bundle operations

Bundles can be:

• created
• verified
• replayed
• replay-verified
• signed
• signature-verified
• exported
• imported
• bound to a trusted identity
• referenced by identity fingerprint

Release significance

This is the first public baseline release of DigiEmu Core.

It defines the initial operational foundation for:

• deterministic replay
• verifiable system state reconstruction
• portable trust artifacts
• identity-bound knowledge transport

Notes

This release is intended for evaluation, integration, and controlled environments.

Enterprise hardening and extended guarantees will follow in subsequent releases.

Full commit history:
https://github.com/DigiEmu/core/commits/v1.0.0