gjata-legacy/ess-mai-poc-004-gcl-law0-global-continuity

ESS-MAI POC 004 — GCL LAW-0 Global Uncertainty Continuity

ESS-MAI is experimental, governance-first AI systems research by Bledar Gjata (Gjata Legacy), developed in Tirana, Albania. Albania denotes where the research is developed; ESS-MAI is not an Albanian-language model and not a national or sovereign AI system. Its relevance to AI governance is, in the repository's words, “an invitation to evaluate the project, not a claim of academic validation, regulatory compliance, or safety assurance”; it is not a legal or compliance framework, and governance-first control as such is prior art, not claimed as new.

This repository is a verbatim single-capsule mirror of publications/executable-prior-art/poc-004-gcl-law0-global-continuity/ from the canonical ESS-MAI repository on GitHub, as released in the collection ess-mai-executable-prior-art-v1.1.1. It contains no model, no demo and no part of the ESS-MAI core beyond the allowlisted capsule files. The capsule files are the authority. This card summarizes them and adds no claim.

Abstract

POC 004 is a bounded, executable theory proof of concept (THEORY_POC, capsule version 0.2.0) of the LAW-0 uncertainty ledger in the shared gcl-constitution crate of the ESS-MAI v1.8.9 (v189) baseline. The falsifiable claim under test is that, for an accepted LAW-0 transcript, no new step may enlarge the ledger's current candidate space. After the first step, every accepted transition must therefore satisfy next.before == previous.after, finite(next.before) && finite(next.after), 0 <= next.after <= next.before and the phase order Coordination <= Reasoning <= Verification. Once terminal Verification reaches zero, the transcript must be closed. The capsule contains the complete five-file minimal crate closure and one Shadow verification-receipt source file. All six files match their v189 origins by byte count and SHA-256, and no production source was edited. It also contains new experiment glue that calls the public production API without replacing or modifying it. In the tested cases the implementation enforces the local part of the theory: an individual caller-reported tuple is accepted only when after <= before, and a direct expansion is rejected without appending the step. The same byte-identical code also produces concrete counterexamples to the stronger global claim. The result is therefore classified PARTIAL_MATERIALIZATION. In the capsule's words, "the failures define the engineering work required for advancement; they do not change the artifact class." The production rule permits equality, so after <= before is "a non-expansion safety property, not proof of strict reduction, convergence, or termination." Within this POC, "uncertainty" is a caller-reported count of remaining candidate possibilities. It is not Shannon entropy, probability, semantic truth or model confidence.

Constitutional placement (from THEORY.md)

GCL
 ├─ Coordination / Light
 ├─ Reasoning / Quantum
 └─ Verification / Shadow

GCL is the parent constitutional authority. Coordination, Reasoning, and Verification are subordinate jurisdictions with distinct responsibilities, listed in the phase order that the theory requires. "No phase becomes sovereign merely because it records a transition." The phase order is a requirement of the theory under test. For the current ledger, the capsule records PHASE_ORDER = NOT_ENFORCED.

Identity

Field	Value
Author and architect	Bledar Gjata
Author ORCID iD	0009-0003-7854-266X
Organization	Gjata Legacy
Public contact	[email protected]
Capsule	poc-004-gcl-law0-global-continuity, capsule version 0.2.0
Artifact class	THEORY_POC
Experimental status	PARTIAL_MATERIALIZATION
Verification date (capsule)	2026-08-23
Collection release	ess-mai-executable-prior-art-v1.1.1, tag commit d38c2bab85e7bc9e1683da2cdfccc43e958639ad (2026-09-14)
Archival record (collection level)	First archived in collection v1.0.0 (POC 003 + POC 004): DOI 10.5281/zenodo.22074028, 2026-08-24 · Also contained in collection v1.1.1 (POC 003–006): DOI 10.5281/zenodo.22750188, 2026-09-14 · All versions: concept DOI 10.5281/zenodo.22074027
Canonical GitHub path	https://github.com/gjatalegacy-create/ESS-MAI/tree/ess-mai-executable-prior-art-v1.1.1/publications/executable-prior-art/poc-004-gcl-law0-global-continuity
License	Apache-2.0 (capsule LICENSE, NOTICE.md, CITATION.cff)

Notes on identity:

• The capsule directory has the same git tree object (547ba84a343ea4ff455732d2e7d90fc5e7c1d9f0) at the v1.0.0 and v1.1.1 tags. This was checked in a local clone of the canonical repository. Capsule version 0.2.0 is therefore the version contained in both archival records.
• The release tag and the DOIs are collection-level records that were issued after the capsule text was written. The capsule files are published unchanged, so their release-state wording reflects the time of writing. Examples are RELEASE_CANDIDATE_NOT_YET_TAGGED in PUBLICATION_MANIFEST.md and the statement in README.md that no DOI is claimed until one is issued.
• Version numbers belong to separate namespaces. In the capsule's words: "The project baseline directory is named v1.8.9, the extracted Rust package declares version 1.7.8, the experiment crate remains version 0.1.0, and this superseding publication capsule is version 0.2.0; these are separate version namespaces, not a claim that the numbers are identical."

Repository contents

Path	Content
poc-004-gcl-law0-global-continuity/	Verbatim copy of the capsule directory (44 files) as released at the v1.1.1 tag
data/poc.jsonl	The single POC-004 row of the collection table data/pocs.jsonl: question tested, what was shown and not shown, status, recorded tests, repeatability, artifact-manifest SHA-256 and links. It adds no claim.
MIRROR_MANIFEST_REVERIFIED.sha256	SHA-256 of the mirrored files, recomputed at mirror time
README.md	This card

Publication boundary, verbatim from the capsule README.md: "This Apache-2.0 capsule is a surgical disclosure of the allowlisted files only. It does not disclose or license the full ESS-MAI v189 core."

from datasets import load_dataset
poc = load_dataset("gjata-legacy/ess-mai-poc-004-gcl-law0-global-continuity", split="collection_v1.1.1")

Question tested

Does the locally enforced LAW-0 rule (each caller-reported step must satisfy after <= before) establish global continuity of the candidate space across steps, phases and process boundaries?

What was shown

• Clean offline locked build; 19/19 tests (11 GCL production, 2 Shadow receipt, 6 POC harness); 5/5 runs with identical output.
• A tuple is accepted only when after <= before; the direct expansion 2 -> 5 is rejected without appending a step.
• The reference chain 16 -> 3 -> 2 -> 1 -> 1 -> 0 is accepted and classified as collapsed.
• A harness-only, domain-separated binding of the existing receipt ID and the LAW-0 digest changes when the LAW-0 digest is altered and detects the substitution — an advancement probe, not production integration.

The capsule records these results as a locally reproduced build, not as independent certification. The run counts come from disclosed maintainer evidence and are not presented as independent replication. From the capsule README.md: "A passing experiment test for a counterexample means the implementation gap was reproduced exactly. It does not mean the stronger LAW-0 invariant passed."

What was not shown (failures and counterexamples)

• 16 -> 1 followed by 100 -> 50 is accepted; the ledger's current state grows from 1 to 50.
• A terminal Verification 1 -> 0 can be followed by Coordination 100 -> 50, reopening a collapsed ledger.
• 1 -> -1 and +infinity -> +infinity are accepted; the report omits the injected before=100.
• Changing only the LAW-0 close report leaves the current Shadow receipt identifier unchanged, because LAW-0 is not an input to it.
• Current Light-to-Quantum and Quantum-to-Shadow wires carry no continuous LAW-0 transcript (static source mapping, not executed).
• "Uncertainty" here is a caller-reported candidate-space count, not Shannon entropy, probability or truth.

THEORY.md gives six conditions under which the global theory is falsified for the current implementation. It then records: "The experiment reproduces the first five. The byte-identical Shadow receipt probe also reproduces the missing receipt binding. Static wire analysis establishes that the cross-platform mechanisms are present but their LAW-0 continuity connection is not materialized."

Experiment matrix (verbatim from RESULTS.md)

Case	Input	Required by full theory	Observed	Verdict
Reference chain	16 -> 3 -> 2 -> 1 -> 1 -> 0	accept and collapse	accepted; 5 steps; collapsed	PASS
Direct expansion	2 -> 5	reject without mutation	rejected; empty ledger preserved	PASS
Nonempty rejection atomicity	seed 10 -> 5, then 5 -> 6	reject; preserve seed state	rejected; length, current state, and report unchanged	PASS
Cross-step continuity	16 -> 1, then 100 -> 50	reject second step	second step accepted; current state grows 1 -> 50	FAIL
Report completeness	same discontinuous chain	expose every boundary	injected before=100 absent from report	FAIL
Phase/terminal order	Verification 1 -> 0, then Coordination 100 -> 50	reject reopening	accepted; ledger changes from collapsed to uncollapsed	FAIL
Non-negative domain	1 -> -1	reject	accepted and classified collapsed	FAIL
Finite domain	+infinity -> +infinity	reject	accepted	FAIL
Shadow local durable close	local Verification 1 -> 0 marker	bind close to committed cycle	source mapping shows the report digest entering cycle, transaction ID, WAL and replay-validation paths; full runtime not executed here	STATIC SOURCE MAPPED / NOT E2E RUN
Shadow public receipt binding	change only LAW-0 report/digest	outward receipt must change	byte-identical receipt algorithm returns the same ID because LAW-0 is not an input	FAIL / UNLINKED
Harness-only connection	existing receipt ID + LAW-0 digest	tamper changes connection identity	domain-separated connection digest changes and rejects the altered digest	ADVANCEMENT PROBE PASS
Cross-platform continuity	Light -> Quantum -> Shadow	one verifiable transcript	components and transport paths exist, but the continuity head is not connected across the boundaries	COMPONENTS PRESENT / UNLINKED

From RESULTS.md: "A green Cargo test therefore reproduces the gap; it does not relabel that gap as constitutional success."

Status

PARTIAL_MATERIALIZATION

The class is THEORY_POC and the collection status is released_in_collection_v1.0.0 (collection manifest.json). The status string is part of the claim.

Experimental verdict, verbatim from THEORY.md:

LOCAL_TUPLE_NON_EXPANSION_CHECK = MATERIALIZED
DIRECT_REJECTION_ATOMICITY      = MATERIALIZED
GLOBAL_STEP_CONTINUITY          = NOT_ENFORCED
PHASE_ORDER                     = NOT_ENFORCED
TERMINAL_IMMUTABILITY           = NOT_ENFORCED
FINITE_NONNEGATIVE_DOMAIN       = NOT_ENFORCED
SHADOW_LOCAL_DURABLE_BINDING    = MATERIALIZED
SHADOW_RECEIPT_TRANSPORT        = MATERIALIZED
LAW0_TO_PUBLIC_RECEIPT          = UNLINKED
CROSS_PLATFORM_TRANSCRIPT       = COMPONENTS_PRESENT_UNLINKED
OVERALL                         = PARTIAL_MATERIALIZATION

This result is intentionally not rounded up to full enforcement and not rounded down to absence. It identifies precisely which part of the theory exists in executable form.

Claim boundary. The following is verbatim from CLAIM_BOUNDARY.md, section "Claims not supported":

• This POC does not show that every ESS-MAI runtime state is recorded.
• It does not prove global LAW-0 enforcement or one continuous Light-to-Quantum-to-Shadow ledger.
• It does not execute the full v189 system or its three production binaries end to end.
• It does not prove that caller-reported numbers came from real candidate sets or from the module named by the caller.
• It does not prove semantic uncertainty reduction, truth, correctness, confidence calibration, Shannon-information reduction, convergence, or termination.
• is_collapsed() is not a verified truth verdict; the current predicate also accepts negative values as collapsed.
• The local Shadow digest is an integrity binding for a constant local close marker, not a per-cycle upstream transcript, origin authentication, or a global attestation.
• The current public receipt does not independently prove the LAW-0 digest or durable commit.
• The harness-only connection hash is an advancement feasibility result, not current production integration.
• chain_report is not a complete audit trail under the current API.
• Byte identity applies only to the six files listed in EXTRACTION_IDENTITY.md; it is not a claim that three runtime binaries are identical.
• The artifact does not establish production readiness, security certification, patent novelty, patent invalidity, freedom to operate, legal priority […].

Architectural invariant for advancement, verbatim from CLAIM_BOUNDARY.md:

GCL authority
  -> bounded Coordination evidence
  -> bounded Reasoning evidence
  -> bounded Verification evidence

The receipt may carry continuity; it may not transfer sovereignty. No child phase may mint the parent authority or assume a sibling's jurisdiction.

The supported claims are listed in the same file, in two separate sections: one for claims supported by execution and one for claims supported only by static production mapping.

Theory and prior art

The capsule's focused prior-art note (search and review date 2026-08-23) treats the following as established:

• candidate-set reduction (Mitchell 1977);
• local pruning of search spaces (Mackworth 1977);
• monotone ordered reasoning and global data-flow analysis (Cousot and Cousot 1977; Kildall 1973);
• typestate ordering of transitions (Strom and Yemini 1986);
• well-founded termination arguments (Lee, Jones and Ben-Amram 2001);
• producer-to-consumer proof objects (Necula 1997);
• append-only Merkle audit structures (RFC 9162).

It cites Shannon (1948) only to keep candidate counts distinct from information-theoretic entropy.

The stated contribution of the POC is the explicit, reproducible split between supported local behavior, executable counterexamples to the stronger global theory, and a bounded architecture-preserving advancement seam. The note states that this contribution "is not represented as completed production integration." The limited review did not identify an exact description of the named repository-specific composition. The note adds that this observation "is not evidence of novelty and must not be represented as a novelty conclusion."

The review was focused, English-language and source-led. It did not search every patent family, non-English disclosure, thesis, repository, standard, commercial system or unpublished work. It is not an exhaustive patent search, a novelty opinion, a freedom-to-operate analysis or legal advice.

Full texts at the v1.1.1 tag: PRIOR_ART.md · THEORY.md

Reproduce

Follow the capsule's own REPRODUCIBILITY.md (also at poc-004-gcl-law0-global-continuity/REPRODUCIBILITY.md in this repository). This card has not re-executed the procedure.

The capsule records these prerequisites:

• Windows PowerShell;
• Cargo 1.98.0 and rustc 1.98.0;
• no C compiler;
• the locked sha2 dependency available in the local Cargo cache;
• network disabled by --offline, so no package is downloaded during verification.

Run the commands from the capsule root. In this repository that is poc-004-gcl-law0-global-continuity/. The canonical location is <ESS_MAI_REPOSITORY>/publications/executable-prior-art/poc-004-gcl-law0-global-continuity. The commands below are verbatim from REPRODUCIBILITY.md.

Verify extraction:

.\verify_extraction.ps1

Expected end state:

EXTRACTION_IDENTITY=PASS
FILES_VERIFIED=6

Format, clean build, and tests:

$pocCargo = Join-Path $env:USERPROFILE '.cargo\bin\cargo.exe'
& $pocCargo fmt --all -- --check
& $pocCargo clean
& $pocCargo build --workspace --locked --offline
& $pocCargo test --workspace --locked --offline

Expected unit-test result:

gcl-constitution: 11 passed; 0 failed
experiment:       8 passed; 0 failed
total:            19 passed; 0 failed

The eight experiment-binary tests are the two tests carried unchanged in the extracted Shadow receipt module and the six POC harness tests. Run cargo clean only from the POC root, because its target is <POC_ROOT>/target.

Five executions:

1..5 | ForEach-Object {
    & $pocCargo run --quiet --package gcl-law0-global-continuity-experiment --locked --offline
    if ($LASTEXITCODE -ne 0) { throw "POC execution $_ failed" }
}

Each execution must end with:

GLOBAL_CONTINUITY_ENFORCEMENT=FAIL
PHASE_ORDER_ENFORCEMENT=FAIL
UNCERTAINTY_DOMAIN_ENFORCEMENT=FAIL
PRODUCTION_END_TO_END_EXECUTION=NOT_RUN
SHADOW_LOCAL_LAW0_DURABLE_PATH=SOURCE_MATERIALIZED
SHADOW_VERIFICATION_RECEIPT_PATH=SOURCE_MATERIALIZED
LAW0_DIGEST_TO_VERIFICATION_RECEIPT=UNLINKED
CROSS_PLATFORM_LEDGER_CONTINUITY=COMPONENTS_PRESENT_CONNECTION_UNLINKED
MATERIALIZATION_STATUS=PARTIAL
EXPERIMENTAL_STATUS=SUCCESS_AND_FAILURE_REPRODUCED
POC_CLASS=THEORY_POC

The program output should be byte-identical across the five runs. A Cargo environment warning may appear before the program output. The capsule states: "The build demonstrates standalone compilation of the exact extracted crate in this local reproduction. Static source locations outside the extraction are provenance mapping, not executed end-to-end evidence."

Integrity

• MIRROR_MANIFEST_REVERIFIED.sha256 (repository root) holds the SHA-256 of the mirrored files, recomputed at mirror time. To check it, run this from the repository root:

  sha256sum -c MIRROR_MANIFEST_REVERIFIED.sha256
  

• poc-004-gcl-law0-global-continuity/evidence/artifact_hashes.sha256 is shipped by the capsule. It holds the SHA-256 of the publication files and excludes target/, .git/, the hash manifest itself, generated binaries and compiler metadata. The file's own SHA-256 is the capsule artifact_manifest_sha256, recorded in the collection manifest.json and in data/poc.jsonl:

  e8ef70d0af825f46709edcd20d9fed36459d6471c5869782c67e88d64fc56ee3  evidence/artifact_hashes.sha256
  

  cd poc-004-gcl-law0-global-continuity
  sha256sum evidence/artifact_hashes.sha256
  sha256sum -c evidence/artifact_hashes.sha256
  

• EXTRACTION_MANIFEST.sha256 and verify_extraction.ps1 hold the per-origin hashes of the six extracted production files. Byte identity is claimed only for those six files.

A matching hash establishes only that a file is identical to the recorded one. It does not establish that the theory is correct.

Part of

• Full collection mirror (POC 003–006): https://huggingface.co/datasets/gjata-legacy/ess-mai-executable-prior-art. This capsule is at executable-prior-art/poc-004-gcl-law0-global-continuity/ in that repository.
• Reading page, with what each POC showed and did not show: https://huggingface.co/spaces/gjata-legacy/ess-mai
• Canonical source: https://github.com/gjatalegacy-create/ESS-MAI (publications/executable-prior-art/)
• Other single-capsule repositories:
  • POC 003 — System cold-start reachability: https://huggingface.co/datasets/gjata-legacy/ess-mai-poc-003-system-cold-start-reachability
  • POC 005 — FFI LAW-0 authority non-duplication: https://huggingface.co/datasets/gjata-legacy/ess-mai-poc-005-ffi-law0-authority-nonduplication
  • POC 006 — Living Negative Knowledge: verified re-entry: https://huggingface.co/datasets/gjata-legacy/ess-mai-poc-006-living-negative-knowledge-verified-reentry

Each capsule carries its own claim boundary. No collection-level description expands a capsule's claim.

Test and refute

Agreement with the theory is not required. The most useful external work is adversarial: find an authority bypass, an invalid state assumption, a non-reproducible result, a receipt-substitution path, a documentation/source mismatch, or an overbroad theoretical claim. For this capsule, the falsification rule in THEORY.md and the experiment matrix in RESULTS.md state what would count against each recorded verdict.

• Independent technical review discussion: https://github.com/gjatalegacy-create/ESS-MAI/discussions/12
• Submit an independent reproducibility report: https://github.com/gjatalegacy-create/ESS-MAI/issues/new?template=reproducibility-report.yml
• Security-sensitive findings: report them privately, as described in SECURITY.md.

Citation

The capsule CITATION.cff states: "If you use this bounded ESS-MAI theory POC, cite this artifact version."

@software{gjata_2026_ess_mai_poc_004,
  author    = {Gjata, Bledar},
  title     = {{ESS-MAI POC 004 — GCL LAW-0 Global Uncertainty Continuity}},
  version   = {0.2.0},
  year      = {2026},
  publisher = {Zenodo},
  doi       = {10.5281/zenodo.22750188},
  url       = {https://github.com/gjatalegacy-create/ESS-MAI/tree/main/publications/executable-prior-art/poc-004-gcl-law0-global-continuity},
  license   = {Apache-2.0},
  note      = {Capsule contained in ESS-MAI Executable Prior Art, collection version 1.1.1}
}

The same capsule version was first archived in collection v1.0.0, DOI 10.5281/zenodo.22074028. To refer to all collection versions, use the concept DOI 10.5281/zenodo.22074027. Machine-readable metadata: poc-004-gcl-law0-global-continuity/CITATION.cff.

Author

Bledar Gjata · Gjata Legacy · [email protected] · GitHub · ORCID · LinkedIn · X · TikTok · YouTube · Facebook · Facebook page GJATA