UNASKED v0.2.0 - Non-certifying M0 development path
Scope
UNASKED v0.2.0 publishes the P0 evidence-authority foundation and an unsealed M0
development execution path. It is a research harness for blind, evidence-gated repository
investigation.
This release is explicitly NON_CERTIFYING:
m0_demonstrated=false;- no independently held sealed benchmark was used;
trials certifyfails closed until custody and complete evidence bundles can be
independently authenticated;- the local executor and subprocess provider do not prove OS-level network or filesystem
isolation; - actor IDs and external custody/replay issuers are recorded but not cryptographically
authenticated.
Included
- immutable Git snapshot observation and a frozen knowledge boundary;
- Git 2.45+ fail-closed object reads, config-isolated metadata views, self-contained temporary
repositories, and internal no-follow/ADS-aware mutation manifests; - content-addressed artifacts and a hash-chained append-only event ledger;
- deterministic lifecycle, evidence, replay, review, and authority gates;
- a bounded single-provider Explorer with strict JSON actions and finite budgets;
- deterministic baselines and five preregistered ablation arms;
- 20 public JSON Schemas and fail-closed M0 trial aggregation;
- wheel-bundled protocols, examples, custody guidance, templates, and governance documents;
- cross-platform CI, reproducible-build verification, wheel smoke tests, and SHA-256 release
checksums.
NO_VERIFIED_DISCOVERY remains a valid and expected result.