ExperimentEXP-2026-0001v0.1
AER-0 MVP v0.1 closure: are the invariants executable?
The approved Python + SQLite runtime was built under mssp-tdd-apr and closed on behavioural, structural and discriminative witnesses: candidate gate, provenance validation, stale-version conflict, stable-vs-volatile scheduling, shock activation, verifier rejection, workflow reuse/adapt/create, model swap, model-free core, end-to-end verified commit. 25 tests; the refresh benchmark selected 2 nodes under fixed TTL versus 1 volatile node under tension scheduling; a clean extracted replay of the sealed archive passed before release.
Hypothesis
hypothesis- The scoped MVP invariants (canonical state ownership, candidate gating, provenance, versioned commit, selective refresh, capability/container separation, workflow reuse, model replaceability) can be implemented with positive and falsifying executable witnesses.
Setup
software_environment- Python 3.11+, SQLite; no network, no external database, no LLM API required.
Procedure
procedure- TDD under mssp-tdd-apr; full suite, research-assistant demo and refresh benchmark run before packaging; checksum-verified clean extraction replayed after sealing.
Runs
run_count- 1
metricstests_passed- 25
refresh_benchmarkfixed_6h_ttl_nodes_refreshed- 2
aer_tension_nodes_refreshed- 1
closurebehavioral- PASS
structural- PASS
discriminative- PASS
independent_twin- NotMeasured
production_readiness- NotClaimed
general_ai_superiority- NotMeasured
Interpretation
interpretation- A mechanism closure, not a claim of AI superiority: the declared invariants exist in code, are exercised by falsifying witnesses, and survive a fresh-process replay.
Limitations
limitations- DEGRADED-TWIN: only one live execution context; no simulated independent verdict claimed.
- Not measured: performance against production agent frameworks, live research accuracy, distributed semantics, security hardening, real heterogeneous backends, multi-day drift.
Reproduction
reproduction_instructions- Extract the round's FINAL bundle; python -m pytest -q; python -m examples.research_assistant_demo; python -m benchmarks.<round benchmark>. Checksums in SHA256SUMS.txt.
Recorded fields
completed_at- 2026-09-08
Relations
| Source | Relation | Target | Status | ID |
|---|---|---|---|---|
EXP-2026-0001 AER-0 MVP v0.1 closure: are the invariants executable? | runs_on | SYS-2026-0001 AER-0 — Adaptive Epistemic Runtime MVP | ACTIVE | REL-2026-0099 |
EXP-2026-0001 AER-0 MVP v0.1 closure: are the invariants executable? | uses_benchmark | BEN-2026-0002 AER-0 architecture-comparison suite (R1–R6) | ACTIVE | REL-2026-0100 |
EXP-2026-0001 AER-0 MVP v0.1 closure: are the invariants executable? | tests | THY-2026-0002 Canonical symbolic state and candidate → verify → commit authority | ACTIVE | REL-2026-0101 |
EXP-2026-0001 AER-0 MVP v0.1 closure: are the invariants executable? | tests | THY-2026-0001 Asymmetric spacetime tension: temporally heterogeneous world knowledge | ACTIVE | REL-2026-0102 |
EXP-2026-0001 AER-0 MVP v0.1 closure: are the invariants executable? | tests | THY-2026-0007 Capability memory and substrate-neutral compute: Reuse ≻ Adapt ≻ Create | ACTIVE | REL-2026-0103 |
EXP-2026-0001 AER-0 MVP v0.1 closure: are the invariants executable? | produced | ART-2026-0014 AER-0 MVP v0.1 FINAL artifact://evemisslab/adaptive-epistemic-systems/AER-0_MVP_v0.1_FINAL.zip | ACTIVE | REL-2026-0104 |
EXP-2026-0002 R1 — deterministic semantics comparison against four baselines | extends | EXP-2026-0001 AER-0 MVP v0.1 closure: are the invariants executable? | ACTIVE | REL-2026-0110 |
History and provenance
- Canonical URL
- https://evemisslab.com/ai/experiments/EXP-2026-0001/
- Machine-readable
/ai/experiments/EXP-2026-0001/index.json- Snapshot
AI-SNAPSHOT-v0.1-fe85b9694a45- Provenance
source- EveMissLab research collection: Adaptive Epistemic Systems (真本體論13)
extracted_by- Splice (Claude Code), reading the canonical UTF-8 sources and each lab's own result reports
extracted_at- 2026-09-11
generator- tools/extract_aes/extract.py
claim_boundary- status, evidence level and result type follow the source artifact's own stated claim boundary; nothing is upgraded beyond what the report supports