Datasets:

gjata-legacy
/

ess-mai-executable-prior-art

poc_id stringclasses 4 values	title stringclasses 4 values	class stringclasses 2 values	capsule_version stringclasses 2 values	collection_status stringclasses 2 values	experimental_status stringclasses 4 values	question_tested stringclasses 4 values	what_was_shown listlengths 4 4	what_was_not_shown listlengths 3 6	cargo_build stringclasses 1 value	recorded_tests stringclasses 4 values	repeatability stringclasses 3 values	artifact_manifest_sha256 stringclasses 4 values	capsule_github stringclasses 4 values	capsule_hugging_face stringclasses 4 values	prior_art stringclasses 4 values	claim_boundary stringclasses 4 values	license stringclasses 1 value	collection_release stringclasses 1 value	collection_doi stringclasses 1 value	author stringclasses 1 value	organization stringclasses 1 value
POC-003	POC 003 — System cold-start reachability	SYSTEM_POC	0.2.0	released_in_collection_v1.0.0	PARTIAL_SYSTEM_MATERIALIZATION_WITH_CAUSAL_CONTROL	From generation zero — an empty Shadow knowledge state — can the bounded real authority path (GCL → Light/Besa → separate Shadow selection → Quantum/Asht → separate Shadow selection) reach the post-Asht final-Shadow point?	[ "Locked offline Cargo build; 84/84 disclosed tests pass (11 GCL, 13 Shadow-contract, 44 Quantum, 10 system unit, 6 integration).", "Wrong-phase GCL directives are rejected by the extracted Light and Quantum state machines.", "Besa accepts a complete empty selection through a separate Shadow process; Asht then f...	[ "From the empty state the post-Asht probe is not reached: the cold-start reachability gap is reproduced, not closed.", "No production Shadow judgment, transaction, WAL commit or terminal receipt is executed; the positive control is not a production fix.", "The proposed GCL-authorized one-time genesis route is f...	PASS	84 passed; 0 failed	3/3 empty cold-start gap reproduced; 1/1 exact-pair positive control passed	f43f7439830c77b4802c3d4cc4000e3d0d8c2b3e5fce12e5f1fd8d5aaa8fc92c	https://github.com/gjatalegacy-create/ESS-MAI/tree/ess-mai-executable-prior-art-v1.1.1/publications/executable-prior-art/poc-003-system-cold-start-reachability	https://huggingface.co/datasets/gjata-legacy/ess-mai-executable-prior-art/tree/main/executable-prior-art/poc-003-system-cold-start-reachability	https://github.com/gjatalegacy-create/ESS-MAI/blob/ess-mai-executable-prior-art-v1.1.1/publications/executable-prior-art/poc-003-system-cold-start-reachability/PRIOR_ART.md	https://github.com/gjatalegacy-create/ESS-MAI/blob/ess-mai-executable-prior-art-v1.1.1/publications/executable-prior-art/poc-003-system-cold-start-reachability/CLAIM_BOUNDARY.md	Apache-2.0	ess-mai-executable-prior-art-v1.1.1	10.5281/zenodo.22750188	Bledar Gjata	Gjata Legacy
POC-004	POC 004 — GCL LAW-0 global continuity	THEORY_POC	0.2.0	released_in_collection_v1.0.0	PARTIAL_MATERIALIZATION	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?	[ "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 cl...	[ "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 t...	PASS	19 passed; 0 failed	5/5 success and counterexamples reproduced	e8ef70d0af825f46709edcd20d9fed36459d6471c5869782c67e88d64fc56ee3	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	https://huggingface.co/datasets/gjata-legacy/ess-mai-executable-prior-art/tree/main/executable-prior-art/poc-004-gcl-law0-global-continuity	https://github.com/gjatalegacy-create/ESS-MAI/blob/ess-mai-executable-prior-art-v1.1.1/publications/executable-prior-art/poc-004-gcl-law0-global-continuity/PRIOR_ART.md	https://github.com/gjatalegacy-create/ESS-MAI/blob/ess-mai-executable-prior-art-v1.1.1/publications/executable-prior-art/poc-004-gcl-law0-global-continuity/CLAIM_BOUNDARY.md	Apache-2.0	ess-mai-executable-prior-art-v1.1.1	10.5281/zenodo.22750188	Bledar Gjata	Gjata Legacy
POC-005	POC 005 — FFI LAW-0 authority non-duplication	THEORY_POC	1.1.1	verified_for_collection_v1.1.1	PARTIAL_POC_LOCAL_PROPERTY_READY_GLOBAL_THEORY_NOT_MATERIALISED	Does the existing v189 FFI gate let one freshly issued, generation-bound CapHandle cross authority validation at most once — refusing copied replay, forged nonce and unknown generation — while withholding a direct knowledge write when no committed superior verdict is present?	[ "Native v189 focal tests 8/8; strict release all-targets build; detached tests 15/15; 3/3 independent process receipts identical.", "Copy(CapHandle) != Copy(Authority) for one issued generation: forged nonce -3; first valid non-empty call reaches CompatibilityHold (-8); copied and third replays -1; unknown genera...	[ "Two fresh generations for the same module and payload each reach -8: generation-local non-duplication is not semantic non-duplication.", "Durable consumption across restart, an idempotent knowledge sink and end-to-end FFI-to-Vault persistence are not materialised.", "No default-production in-repository caller ...	PASS	native: 8 passed; 0 failed \| detached: 15 passed; 0 failed	3/3 independent process receipts identical	ca935c761d490afd717dcd435f07501af4166b8a52f76f3057b4083cd4b445d1	https://github.com/gjatalegacy-create/ESS-MAI/tree/ess-mai-executable-prior-art-v1.1.1/publications/executable-prior-art/poc-005-ffi-law0-authority-nonduplication	https://huggingface.co/datasets/gjata-legacy/ess-mai-executable-prior-art/tree/main/executable-prior-art/poc-005-ffi-law0-authority-nonduplication	https://github.com/gjatalegacy-create/ESS-MAI/blob/ess-mai-executable-prior-art-v1.1.1/publications/executable-prior-art/poc-005-ffi-law0-authority-nonduplication/PRIOR_ART.md	https://github.com/gjatalegacy-create/ESS-MAI/blob/ess-mai-executable-prior-art-v1.1.1/publications/executable-prior-art/poc-005-ffi-law0-authority-nonduplication/CLAIM_BOUNDARY.md	Apache-2.0	ess-mai-executable-prior-art-v1.1.1	10.5281/zenodo.22750188	Bledar Gjata	Gjata Legacy
POC-006	POC 006 — Living Negative Knowledge: verified re-entry	THEORY_POC	1.1.1	verified_for_collection_v1.1.1	PARTIAL_POC_NARROW_VERIFIED_REENTRY_READY_GLOBAL_LIFECYCLE_NOT_MATERIALISED	Does the existing v189 negative-knowledge import and filtering code bring valid, required, sealed history into READY state and hard-block a semantically matching later candidate, while preventing reasoning when the required history is missing, corrupt or downgraded?	[ "Strict release build; detached tests 30/30; 3/3 independent process receipts identical. Native v189 runs 12/12, 19/19 and 1/1 are separate runs, not summed.", "Valid sealed history imports one entry as READY; the matching later candidate is hard-blocked with score 0.000.", "Missing (DEGRADED), corrupt (NOT_REA...	[ "The cycle response carries negative_persisted as a Boolean, not a typed, independently verifiable negative-commit receipt (source inspection, not runtime-measured).", "Detached terminate/reopen recovery through the authoritative Shadow Vault and the next Quantum process is not executed; WAL recovery passes only ...	PASS	native: separate runs: 12/12, 19/19, 1/1; four focused verdict filters each 1/1 (overlap not summed) \| detached: 30 passed; 0 failed	3/3 independent process receipts identical	3054c5ee1288dae7d08fd280f4d7b97b1c7be6afeba79e4e10e3c58bb8a3c2cd	https://github.com/gjatalegacy-create/ESS-MAI/tree/ess-mai-executable-prior-art-v1.1.1/publications/executable-prior-art/poc-006-living-negative-knowledge-verified-reentry	https://huggingface.co/datasets/gjata-legacy/ess-mai-executable-prior-art/tree/main/executable-prior-art/poc-006-living-negative-knowledge-verified-reentry	https://github.com/gjatalegacy-create/ESS-MAI/blob/ess-mai-executable-prior-art-v1.1.1/publications/executable-prior-art/poc-006-living-negative-knowledge-verified-reentry/PRIOR_ART.md	https://github.com/gjatalegacy-create/ESS-MAI/blob/ess-mai-executable-prior-art-v1.1.1/publications/executable-prior-art/poc-006-living-negative-knowledge-verified-reentry/CLAIM_BOUNDARY.md	Apache-2.0	ess-mai-executable-prior-art-v1.1.1	10.5281/zenodo.22750188	Bledar Gjata	Gjata Legacy

ESS-MAI Executable Prior Art — POC Collection

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.

Shqip. ESS-MAI është kërkim eksperimental në sistemet e inteligjencës artificiale (IA) me qasje governance-first: teston nëse qeverisja mund të veprojë si ligj konstitutiv i arsyetimit, para dhe gjatë tij, e jo si kontroll pas tij — hipotezë e deklaruar, jo rezultat. Projekti zhvillohet në Tiranë, Shqipëri, nga Bledar Gjata (Gjata Legacy). Katër POC të ekzekutueshme në Rust (003–006) janë publike (burimi kanonik: GitHub), bashkë me sukseset, dështimet, kundërshembujt dhe kufijtë e pretendimeve të tyre. Një test që kalon tregon vetëm atë që u testua; nuk e provon teorinë.

Verbatim mirror of the canonical public collection publications/executable-prior-art/ from the ESS-MAI repository on GitHub. Nothing in this repository is a model, a demo, or the ESS-MAI core.

Field	Value
Author and architect	Bledar Gjata
Author ORCID iD	0009-0003-7854-266X
Project	ESS-MAI
Organization and affiliation	Gjata Legacy
Public contact	gjatalegacy@gmail.com
Canonical repository	https://github.com/gjatalegacy-create/ESS-MAI
Canonical path	`publications/executable-prior-art/`
Reading page	https://huggingface.co/spaces/gjata-legacy/ess-mai — what each POC showed and did not show
Mirror source	GitHub `main` @ `70478d6599db3623a3d97aba1a64a6db6d014626` (2026-09-14T21:09:07Z)
Release	`ess-mai-executable-prior-art-v1.1.1` → commit `d38c2bab85e7bc9e1683da2cdfccc43e958639ad` (published 2026-09-14T07:26:33Z)
Archival record	Zenodo v1.1.1 DOI 10.5281/zenodo.22750188 · v1.0.0 DOI 10.5281/zenodo.22074028 · concept DOI 10.5281/zenodo.22074027
License	Apache-2.0 (inherited from the canonical collection: `executable-prior-art/LICENSE`, `CITATION.cff`, `codemeta.json`, GitHub repository license)
Integrity	`MIRROR_MANIFEST_REVERIFIED.sha256` (every mirrored file, recomputed at mirror time) · `executable-prior-art/artifact_hashes.sha256` (shipped by the collection; verified 0 mismatches at mirror time)

Table view (`data/pocs.jsonl`)

The Dataset Viewer shows one row per public POC (003–006): question tested, what was shown, what was not shown, experimental status, recorded tests, repeatability, artifact-manifest SHA-256 and links to each capsule, its PRIOR_ART.md and its CLAIM_BOUNDARY.md. Every text value is copied from the capsule summaries on the reading page and from the collection manifest.json; the table adds no claim. The capsule files themselves are under executable-prior-art/ and remain the authority.

from datasets import load_dataset
pocs = load_dataset("gjata-legacy/ess-mai-executable-prior-art", split="collection_v1.1.1")

Per-POC repositories

Each capsule is also published as its own dataset (verbatim capsule, identical to GitHub, with a one-row table):

Scientific context (hypotheses, not results): gjata-legacy/ess-mai-publications.

Review: Independent review requested: POC 003–006.

What this repository is

The four proof-of-concept capsules below are the public, executable, hash-bound part of ESS-MAI. Each capsule carries its own claim boundary, source-to-runtime map, experiment protocol, results, known failures, prior-art declaration and artifact hashes. The collection's own reading rule applies unchanged:

Read each capsule's own claim boundary, extraction identity, reproducibility procedure, results, known failures, and artifact hashes together. No collection-level description expands a capsule's claim.

POC	Directory	Version	Class	Executed result (as recorded in `manifest.json`)
POC 003	`poc-003-system-cold-start-reachability/`	0.2.0	SYSTEM_POC	build PASS; 84 passed, 0 failed; 3/3 empty cold-start gap reproduced; 1/1 exact-pair positive control
POC 004	`poc-004-gcl-law0-global-continuity/`	0.2.0	THEORY_POC	build PASS; 19 passed, 0 failed; 5/5 success and counterexamples reproduced
POC 005	`poc-005-ffi-law0-authority-nonduplication/`	1.1.1	THEORY_POC	strict build PASS; native 8/8; detached 15/15; 3/3 identical process receipts; direct FFI knowledge write not materialised
POC 006	`poc-006-living-negative-knowledge-verified-reentry/`	1.1.1	THEORY_POC	strict build PASS; detached 30/30; 3/3 identical process receipts; verified K− re-entry; full negative receipt wire not materialised

Experimental status strings are copied from manifest.json and are part of the claim: PARTIAL_SYSTEM_MATERIALIZATION_WITH_CAUSAL_CONTROL (003), PARTIAL_MATERIALIZATION (004), PARTIAL_POC_LOCAL_PROPERTY_READY_GLOBAL_THEORY_NOT_MATERIALISED (005), PARTIAL_POC_NARROW_VERIFIED_REENTRY_READY_GLOBAL_LIFECYCLE_NOT_MATERIALISED (006).

Claim boundary (verbatim from the v1.1.1 release notes)

NARROW_CLAIM_STATUS=POC_READY
GLOBAL_THEORY_STATUS=THEORY_NOT_MATERIALISED_GLOBALLY
POC_STATUS=PARTIAL_POC

This seals only the disclosed POC questions. It does not declare the complete ESS-MAI v189 architecture closed, production-certified or fully materialised.

Passing tests establish only what the disclosed experiment demonstrates. A test count is not a proof of the theory. The release claims behavioural reproducibility and records every runtime-witness hash; it does not claim bit-for-bit binary reproducibility (Windows executable SHA-256 values differed across clean build roots).

Method

Every capsule follows the published ESS-MAI Cargo POC experimental method:

theory -> current source -> production mechanism -> isolated experiment
       -> baseline -> target -> ablation -> adversarial failure
       -> counterexample -> recovery boundary -> repeatability -> verdict

and the collection's advancement rule:

experimental success + experimental failure = advancement method

Successes and failures are published together. A failure is preserved as a typed boundary or unresolved gap; advancement means identifying the smallest architecture-preserving connection, constraint or experiment that can close it.

Authority root, as declared in manifest.json: GCL is the sovereign constitutional parent; subordinate platform authorities remain bounded. Constructive K+ and rigorous-negative K− are distinct sibling outcomes under GCL; HOLD is neither.

Reproduce

Each capsule directory contains a Cargo workspace, REPRODUCIBILITY.md / EXPERIMENT_PROTOCOL.md, expected outputs and hashes. Clone or download the capsule, then follow its own procedure; do not rely on this card for any command. Verify the mirror first:

sha256sum -c MIRROR_MANIFEST_REVERIFIED.sha256
cd executable-prior-art && sha256sum -c artifact_hashes.sha256

Prior art and public disclosure

Each capsule declares its own prior art in PRIOR_ART.md (established external foundations, adjacent work, later independent work, and ESS-MAI's earlier public disclosure) and records the limits of its search. The collection states, verbatim: Later independent work is declared without alleging copying or making a universal priority claim.

Public disclosure records (media records with dates; they are attribution and chronology, not technical evidence):

Date	Record
2026-06-03	Business Magazine — used by the collection only as public conceptual attribution of "Dija Negative" to Bledar Gjata and ESS-MAI (see `RELEASE_NOTES_v1.1.1.md`, `poc-006/.../PUBLIC_DISCLOSURE_TRACE.md`)
2026-06-09	Televizioni SCAN, "Një AI shqiptare e krijuar në Shqipëri? Nga të dhënat tek përfitimet..." — https://www.youtube.com/watch?v=i23jeqIwqJA (YouTube `datePublished` 2026-06-09)
2026-08-24	Zenodo v1.0.0 deposit (POC 003 + POC 004), DOI 10.5281/zenodo.22074028
2026-09-14	GitHub release `ess-mai-executable-prior-art-v1.1.1` and Zenodo v1.1.1 deposit, DOI 10.5281/zenodo.22750188

Author profiles: ORCID https://orcid.org/0009-0003-7854-266X · LinkedIn https://www.linkedin.com/in/bledar-gjata-1a527030b/ · X https://x.com/Gjata_Legacy · GitHub https://github.com/gjatalegacy-create

Where ESS-MAI appears

Author profiles: ORCID · GitHub · LinkedIn · X · TikTok · YouTube · Facebook · Facebook page GJATA · Hugging Face · OpenAlex

Media (in Albanian): Business Magazine Albania, 2026-06-03 · Televizioni SCAN (YouTube), 2026-06-09 · ACP, 2026-08-20

Posts by the author: LinkedIn 2026-05-17 · LinkedIn 2026-05-19 · LinkedIn 2026-06-06 · X 2026-06-22 · X 2026-08-07 · X 2026-08-11 · X 2026-08-13 · LinkedIn 2026-08-13 · LinkedIn 2026-08-14 · X 2026-08-18 · LinkedIn 2026-08-21 · X 2026-09-04 · X 2026-09-04

Records: Zenodo — Concept DOI (all versions) 10.5281/zenodo.22074027 · Zenodo — v1.1.1 · Zenodo — v1.0.0 · OpenAIRE — v1.1.1 research-software record · OpenAIRE — v1.0.0 research-software record · Software Heritage — Archived POC collection directory · ORCID — works list

Media and posts establish chronology and attribution, not technical evidence.

Not included (verbatim exclusions from `manifest.json`)

full private ESS-MAI v1.8.9 core
private source-workspace manifests
C01 and C02 evidence
targets, caches, binaries, archives, WAL/vault/hold files
credentials, private keys, tokens, environment dumps, private absolute paths
unissued DOI, tag, release, archive, or timestamp claims

Only released capsules are mirrored here; no unreleased proof-of-concept work is included.

Non-claims

This repository does not claim: that ESS-MAI is complete, production-certified or fully materialised; that any test count proves a theory; bit-for-bit binary reproducibility; universal priority over later independent work; or that any unpublished component exists in the form described by any public text.

Citation

@software{gjata_ess_mai_executable_prior_art_2026,
  author    = {Gjata, Bledar},
  title     = {ESS-MAI Executable Prior Art v1.1.1 — POC 003–006; Standard-Method Closure for POC 005–006},
  year      = {2026},
  month     = {9},
  version   = {1.1.1},
  publisher = {Zenodo},
  doi       = {10.5281/zenodo.22750188},
  url       = {https://github.com/gjatalegacy-create/ESS-MAI}
}

Machine-readable metadata: executable-prior-art/CITATION.cff, executable-prior-art/codemeta.json.

Provenance of this mirror

See MIRROR_PROVENANCE.md for the exact mirror procedure, the git blob comparison against GitHub main and the v1.1.1 tag, and the recorded release asset hash (ess-mai-executable-prior-art-v1.1.1-poc-only.zip, SHA-256 d7a322bf2b09f82803201b2194b75fb433c3f44eafd98441c7eec72d5b673bee as recorded in the GitHub release notes and on Zenodo).