# JCEE Labs Public Registry — Version 1.0

**Public record**  
**Published:** August 31, 2026  
**Status:** Current public projection  
**Scope:** Selected public systems, research programs, and governing standards

## Reading this registry

The JCEE Public Registry is a sanitized projection of the internal JCEE research and build record. It records public status, evidence boundary, and known limitation without publishing private source code, attack corpora, verifier internals, patent-counsel material, customer information, or enabling implementation detail.

A status label never overrides the stated boundary.

## Status language

- **Verified Milestone:** A specific bounded claim survived its named gate and the supporting evidence was preserved.
- **Experimental:** Results exist, but reproduction, transfer, adversarial review, or external verification remains incomplete.
- **Defined Specification:** A stable public specification or contract exists; implementation and transfer claims remain separately bounded.
- **Adopted Standard:** A governance rule adopted by JCEE Labs. It is not an empirical result.

## Public entries

### 1. JCEE VOW 1.1

**Class:** Execution runtime  
**Status:** Verified Milestone · Active Hardening  
**Public support:** A defined release exists and its covered behavior completed the named internal release gate.  
**Boundary:** Not independent certification, universal safety, default legal compliance, or production readiness in every environment.

### 2. QCS-2.0

**Class:** Transition calculus research  
**Status:** Verified Milestone · Core Frozen  
**Public support:** The frozen normative core passed its planned reproduction gate across the two tested authority classes.  
**Boundary:** Not universal correctness, production readiness, or guaranteed transfer to every future substrate.

### 3. JEC 1.0

**Class:** Portable evidence contract  
**Status:** Defined Specification · Bounded Validation  
**Public support:** A stable public concept and bounded structural-validation record for portable execution evidence.  
**Boundary:** A well-formed or signed record does not by itself prove that its source was competent, complete, current, or truthful.

### 4. JCEE Assurance

**Class:** Claim-scoped verification  
**Status:** Experimental · Frozen Verifier Stages  
**Public support:** Deterministic verifier stages and adversarial evidence work exist within recorded experimental boundaries.  
**Boundary:** Not a universal exactly-once guarantee, generalized Byzantine-resilience claim, or third-party certification.

### 5. IEJ

**Class:** Independent evidence judgment  
**Status:** Experimental · Deterministic Baseline  
**Public support:** A bounded deterministic baseline and staged evaluation record.  
**Boundary:** The current record does not establish general-purpose judgment correctness or replace qualified external review.

### 6. Evidence Engine

**Class:** Inspection and replay  
**Status:** Experimental · Bounded Shadow Slice  
**Public support:** A bounded local shadow-slice milestone and preserved evidence package.  
**Boundary:** Presentation does not strengthen the underlying evidence, establish external truth, or substitute for an independent verifier.

### 7. JRP-000 — The Evidence Boundary

**Class:** Research governance  
**Status:** Adopted Standard  
**Adopted:** August 13, 2026  
**Public support:** A governing JCEE Labs research standard.  
**Boundary:** An institutional standard, not an empirical result, external consensus standard, or independent certification.

### 8. JCEE First Principle

**Class:** Institutional governance  
**Status:** Adopted Standard  
**Adopted:** August 31, 2026  
**Public support:** A governing separation between hypothesis generation, empirical claim, system state, and consequential authority.  
**Boundary:** The principle does not settle metaphysical questions; it constrains what JCEE may claim or authorize from available evidence.

## Responsible disclosure

Evidence-first research does not require making every working artifact public.

JCEE may withhold source code, private evidence packages, attack corpora, security-sensitive details, patent material, customer information, and counsel work product while keeping each public claim inside a clear evidence boundary.

A withheld artifact cannot justify an unlimited public claim. Where independent review is required, it must occur through an appropriate confidential process.