UNASKED v0.4.0 - Authenticated evidence verification

UNASKED v0.4.0

UNASKED v0.4.0 adds an authenticated external trust plane while preserving the separation
between a software release and a research milestone claim.

Authenticated verification capability

• exact-byte SHA-256-pinned trust policies with Ed25519 role keys and threshold rules;
• DSSE PAE and in-toto Statement v1 verification for custody, isolation, ledger checkpoints,
  discovery authorization, trial evaluation, and M0 certification;
• a locked prepare/commit authority path that binds signed external inputs to a deterministic
  pre-state graph and an adjacent commit marker;
• full 35-run M0 verification against actual result bytes, ledger chains, final checkpoints,
  complete certificate sets, the evaluator statement, and the certifier statement;
• fail-closed CLI behavior for incomplete, unsafe, schema-invalid, substituted, or tampered
  bundles.

Hard claim boundary

This release is not an M0 result:

• repository and release metadata remain m0_demonstrated=false;
• no independently held sealed benchmark was run for this release;
• the bundled trust policy is explicitly SHADOW, includes public keys only, and carries no
  production authority;
• the package contains no private signing key, hidden case, ground truth, or sealed manifest;
• legacy and incomplete certification returns M0_NOT_DEMONSTRATED;
• a future M0_DEMONSTRATED result requires independently operated PRODUCTION keys, strict
  cross-role actor separation, sealed custody before Explorer development, authenticated
  external isolation and final checkpoints, a complete 5-by-7 run, zero false verified
  controls, and complete replay/context evidence.

Cryptographic validity authenticates configured keys and exact bytes; it does not by itself
prove real-world independence, secrecy, isolation, or absence of collusion. NO_VERIFIED_DISCOVERY
and M0_NOT_DEMONSTRATED remain valid and expected outcomes.

UNASKED v0.3.0 - Non-certifying M0 development path

UNASKED v0.3.0

UNASKED v0.3.0 adds preregistered, budget-bound M0 trial runs and a public structural
evidence audit.

Structural audit

• init --trial-preregistration ... --budget ... freezes the case/variant, commit,
  protocol, budget, and model before provider execution;
• trials audit recomputes the report and validates every indexed run, ledger head, result
  artifact, and complete current VERIFIED certificate set;
• unsafe workspace locators, self-hash tampering, rollback, missing evidence, certificate
  cherry-picking, and finding-flag laundering fail closed;
• a structurally complete all-false trial can honestly return audit_result=PASS without
  implying model discovery.

This release remains explicitly NON_CERTIFYING:

• m0_demonstrated=false;
• actor and custody identities are not authenticated;
• no external attestation trust root or external ledger checkpoint is verified;
• structural PASS does not unlock trials certify;
• no independently held sealed benchmark was used for this software release.

NO_VERIFIED_DISCOVERY remains a valid and expected result.

UNASKED v0.2.2 - Non-certifying M0 development path

UNASKED v0.2.2

UNASKED v0.2.2 is a fail-closed security patch for the public P0 research harness and its
unsealed M0 development path.

Security changes

• provider timeout, output-overflow, and normal-exit cleanup now terminate ordinary
  descendant processes through a Windows Job Object or POSIX process group;
• concurrent ledger writers are serialized across threads and processes around the complete
  verify-plus-fsync append transaction;
• external replay receipts must structurally bind their replay subject, but remain
  unauthenticated and cannot authorize VERIFIED without a future external signature trust
  root.

This release remains explicitly NON_CERTIFYING:

• m0_demonstrated=false;
• no independently held sealed benchmark was used;
• actor IDs and custody declarations are not cryptographically authenticated;
• the local executor and provider lifecycle controls do not prove OS-level filesystem,
  network, or hostile-provider isolation.

NO_VERIFIED_DISCOVERY remains a valid and expected result.

UNASKED v0.2.1 - Non-certifying M0 development path

Scope

UNASKED v0.2.1 is the first public source-visible release of the P0 evidence-authority
foundation and unsealed M0 development execution path. It adds public governance and
automated security review while preserving the v0.2 claim boundary.

This release is explicitly NON_CERTIFYING:

• m0_demonstrated=false;
• public visibility is not research evidence;
• no independently held sealed benchmark was used;
• trials certify fails 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.

Changes since v0.2.0

• add a reserved-rights LICENSE and explicit contribution, security, support, conduct,
  issue, and pull-request policies;
• add CodeQL, Dependabot, Bandit, and locked dependency vulnerability auditing;
• pin current Node 24 workflow actions by immutable commit;
• replace remaining runtime assertions at security/integrity boundaries with explicit
  fail-closed handling and regression tests;
• keep reproducible build, exact metadata/member allowlists, tag binding, checksum, and
  wheel smoke-test gates.

NO_VERIFIED_DISCOVERY remains a valid and expected result.

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 certify fails 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.