Add post-release roadmap documents

docs/CORE_2_ENTERPRISE_READINESS_PLAN.md

@@ -0,0 +1,96 @@
+# DigiEmu Core 2.0 Enterprise Readiness Plan
+
+- **Status:** Draft
+- **Scope:** 2026 enterprise-readiness work after Core 2.0 release
+
+---
+
+## Objective
+
+The objective is to turn Core 2.0 from a released verification core into an enterprise-reviewable, partner-integrable, audit-ready foundation.
+
+This plan defines the 2026 work required to make Core 2.0 ready for partner pilot discussions, external review, and enterprise evaluation.
+
+---
+
+## Enterprise Readiness Pillars
+
+The 2026 readiness work focuses on:
+
+| Pillar | Description |
+|--------|-------------|
+| **Documentation maturity** | Clear, consistent, complete documentation for all external audiences |
+| **API and CLI usability** | Stable, intuitive interfaces for integration and operation |
+| **Deterministic replay reliability** – | Verified, reproducible replay across environments |
+| **Conformance and test coverage** | Comprehensive test vectors and conformance validation |
+| **Audit evidence packaging** | Structured evidence export for audit and compliance use |
+| **Partner interoperability** | Clear integration patterns for external systems |
+| **Security and integrity review** | Hardened security posture and clear integrity guarantees |
+| **Compliance positioning** | Explicit scope and non-claims for regulatory contexts |
+| **Website and one-pager alignment** | Consistent external messaging and positioning |
+
+---
+
+## Priority Workstreams
+
+### Documentation and messaging
+- Release notes and changelog maturity
+- Partner review packages (curated docs for specific audiences)
+- Enterprise demo flows and use cases
+
+### API and interface refinement
+- OpenAPI specification refinement and stabilization
+- CLI examples and integration patterns
+- Verification report examples for common scenarios
+
+### Audit and compliance readiness
+- Audit packet export direction
+- Evidence chain documentation
+- Structured diagnostic output standardization
+
+### Security and reliability
+- Security boundary documentation
+- Replay reliability verification across platforms
+- Cryptographic integrity hardening
+
+---
+
+## Partner Readiness
+
+Core 2.0 enterprise readiness prepares for engagement with:
+
+- **TBN** – Trust boundary integration and evidence reference patterns
+- **AntifragileOS** – Operational validation and before-splice workflows
+- **CLARIXO** – Attribution and responsibility evidence integration
+- **BFH / Innosuisse** – Academic and innovation ecosystem alignment
+- **Compliance and audit reviewers** – Audit-ready evidence and clear scope documentation
+
+---
+
+## Non-Goals for 2026
+
+The following are explicitly **not** 2026 targets:
+
+- **Core 3.0 is not the 2026 delivery target** – Core 3.0 remains a 2027 research direction
+- **No broad platform rewrite** – Core 2.0 is the foundation; evolution is incremental
+- **No unbounded trust or liability claims** – DigiEmu remains a verification layer, not a trust authority
+- **No collapse of identity, attribution, compliance, and verification into one system** – Boundary preservation is maintained
+
+---
+
+## Success Criteria
+
+Enterprise readiness is achieved when:
+
+- [ ] External reviewers can understand the DigiEmu boundary and non-claims
+- [ ] Partners can reference DigiEmu artifacts in their own systems
+- [ ] Examples are reproducible and illustrative
+- [ ] Tests remain green across all supported platforms
+- [ ] Enterprise-facing documentation is coherent and complete
+- [ ] Core 2.0 can support pilot discussions with potential partners
+
+---
+
+## Closing Principle
+
+**Core 2.0 is the enterprise foundation. Core 3.0 should be informed by real review, partner feedback, and enterprise requirements.**

docs/CORE_2_RELEASE_ANNOUNCEMENT.md

@@ -0,0 +1,69 @@
+# DigiEmu Core 2.0 Release Announcement
+
+- **Status:** Released
+- **Release date:** 15 June 2026
+- **Tag:** `core-2.0.0`
+
+---
+
+## Summary
+
+DigiEmu Core 2.0 defines a deterministic decision-state verification layer for AI governance, replay, interoperability, and audit evidence.
+
+It provides canonical artifacts that external trust, identity, attribution, compliance, and operational systems may reference without redefining DigiEmu state identity.
+
+---
+
+## What Core 2.0 Provides
+
+DigiEmu Core 2.0 provides:
+
+- **Deterministic decision-state snapshots** – canonical captures of agent decision state
+- **Canonicalization profile boundary** – explicit declared profile under which state is produced
+- **Decision-state hash references** – cryptographic integrity markers
+- **Replay consistency evidence** – proof that decision state can be reproduced deterministically
+- **Structured verification reports** – machine-readable evidence of verification outcomes
+- **PASS / FAIL outcome preservation** – portable binary results with preserved links to full evidence
+- **Interop examples for external systems** – minimal examples for TBN, AntifragileOS, CLARIXO, compliance, and audit integrations
+- **External review material** – documentation supporting external reviewer evaluation
+
+---
+
+## What Core 2.0 Does Not Claim
+
+DigiEmu Core 2.0 does not claim to provide:
+
+- **Agent identity verification** – DigiEmu verifies decision state, not who produced it
+- **Agent certification** – Certification is outside DigiEmu scope
+- **Trust-tier assignment** – Trust tiers are determined by external systems
+- **Legal liability attribution** – Legal responsibility assignment is external
+- **Regulatory approval** – Regulatory status is determined by external authorities
+- **Full system safety guarantee** – Safety is a property of the complete deployed system
+
+DigiEmu verifies deterministic decision-state integrity and replay consistency within its declared scope.
+
+---
+
+## Interoperability
+
+DigiEmu Core 2.0 is designed to interoperate with external systems as a verification layer:
+
+- **TBN-style trust systems** – May reference DigiEmu evidence without computing or redefining DigiEmu state identity
+- **AntifragileOS-style operational validation** – May use PASS/FAIL outcomes for before-splice validation without DigiEmu becoming the deployment authority
+- **CLARIXO-style attribution systems** – May use DigiEmu artifacts as upstream evidence for responsibility tracking
+- **Compliance layers** – May incorporate DigiEmu reports into compliance documentation
+- **Audit partners** – May reference DigiEmu evidence in audit trails
+
+---
+
+## Release Materials
+
+- [Core 2.0 Interop Contract](CORE_2_INTEROP_CONTRACT.md) – Defines the interoperability boundary
+- [Core 2.0 External Review Note](CORE_2_EXTERNAL_REVIEW_NOTE.md) – Guidance for external reviewers
+- [Core 2.0 Interop Examples](../examples/interop/README.md) – Minimal illustrative examples
+
+---
+
+## Closing Principle
+
+**The boundary is the value.**

docs/CORE_3_2027_RESEARCH_DIRECTION.md

@@ -0,0 +1,73 @@
+# DigiEmu Core 3.0 — 2027 Research Direction
+
+- **Status:** Research direction
+- **Target horizon:** 2027
+- **Relationship to Core 2.0:** Builds on Core 2.0 enterprise feedback
+
+---
+
+## Positioning
+
+Core 3.0 should not replace Core 2.0 prematurely. Core 2.0 remains the 2026 enterprise foundation and the basis for partner integration, external review, and pilot discussions.
+
+Core 3.0 is positioned as a 2027 research and release direction that emerges from the evidence and requirements gathered during Core 2.0 enterprise readiness work.
+
+---
+
+## Candidate Research Themes
+
+The following themes are candidates for Core 3.0 exploration:
+
+| Theme | Description |
+|-------|-------------|
+| **Multi-system evidence chains** – | Linking DigiEmu evidence across multiple verification events |
+| **Cross-system verification receipts** | Standardized receipts that reference DigiEmu, TBN, and other system evidence |
+| **Civil proof and audit layers** | Enhanced evidence packaging for legal and regulatory audit contexts |
+| **ENSO-style de-escalation** | Verification of refusal-state correctness and de-escalation handling |
+| **Three-layer architecture** | DigiEmu + TBN + CLARIXO integration patterns for verification, trust, and attribution |
+| **Enterprise audit packet standardization** | Standard formats for audit evidence export and consumption |
+| **Richer decision-state reconstruction** | More detailed decision-state capture and replay capabilities |
+| **Multi-party canonical evidence references** | Evidence references that can be shared and verified across organizational boundaries |
+
+---
+
+## What Must Be Learned Before Core 3.0
+
+Core 3.0 design must be informed by:
+
+- **Feedback from external reviewers** – What do reviewers need that Core 2.0 does not provide?
+- **Partner integration requirements** – What do TBN, AntifragileOS, CLARIXO, and others need from the DigiEmu interface?
+- **Enterprise pilot requirements** – What evidence and capabilities do enterprise pilots require?
+- **Audit and compliance expectations** – What do audit and compliance reviewers expect from the evidence structure?
+- **Operational before-splice requirements** – What do operational remediation flows need from verification?
+- **Attribution and responsibility boundary feedback** – What boundaries need clarification for attribution systems?
+
+---
+
+## Guardrails
+
+Core 3.0 research and development must maintain the following guardrails:
+
+- **Core 3.0 must not blur DigiEmu's core boundary** – DigiEmu remains a decision-state verification layer
+- **Core 3.0 must not claim agent certification** – Certification must remain with external trust systems
+- **Core 3.0 must not assign legal responsibility by itself** – Liability assignment is external to DigiEmu
+- **Core 3.0 must preserve deterministic verification as the foundation** – Determinism remains the core capability
+
+---
+
+## 2026 to 2027 Transition
+
+The year 2026 should be used to:
+
+- **Harden Core 2.0** – Fix issues, improve reliability, enhance documentation
+- **Collect feedback** – Engage reviewers, partners, and pilot users
+- **Build partner confidence** – Demonstrate that Core 2.0 can support real integration scenarios
+- **Identify what Core 3.0 actually needs to become** – Use evidence from 2026 to define 2027 priorities
+
+Core 3.0 should not be a speculative leap. It should be a response to real requirements identified through Core 2.0 enterprise work.
+
+---
+
+## Closing Principle
+
+**Core 3.0 should emerge from evidence, not ambition.**