Repository navigation
Closed
Labels
epic:evaluationE3: Evaluation FrameworkE3: Evaluation Frameworkrelease:v0.41.0Targeted for v0.41.0Targeted for v0.41.0type:featureNew capabilityNew capabilitywaza41Factory membership for epic #755Factory membership for epic #755
Milestone
Description
Context and outcome
Externally executed work can publish immutable artifacts through idempotent create and finalize operations.
Release parent: Roadmap v0.41.0
Scope
- Define content-addressed artifact and result manifests.
- Define idempotent create and finalize semantics.
- Detect corruption, partial uploads, and conflicting content.
Delivery completeness
- Implement canonical manifest serialization, content addressing, idempotent create/finalize operations, and fail-closed verification for partial, corrupt, or conflicting content.
- Add hash/serialization unit tests, storage-backend contract tests, concurrent integration tests, and failure-injection end-to-end tests for interrupted uploads and conflicting finalization.
- Document publication and recovery workflows for users and the manifest/storage contract for developers; add documentation-site manifest examples, state diagrams, and integrity troubleshooting.
- Add release and migration notes for new manifest schemas, immutability rules, and migration from mutable result locations.
- Extend
waza dashboard --labwith artifact and manifest digests, upload/finalization state, integrity verification, and corruption/conflict diagnostics.
Non-goals
- No mutable shared result directory.
- No ownership of storage replication or availability guarantees.
Dependencies
- Depends on the v0.40.0 runner contract and terminal result envelope.
Acceptance criteria
- Repeated create and finalize operations are safe and deterministic.
- Published artifacts are immutable and content verification fails closed.
- Partial uploads and conflicting content produce actionable diagnostics.
- Manifest publication and verification are implemented through the documented immutable contract.
- Unit, storage-contract, concurrency, and failure-injection tests cover idempotency, interruption, corruption, and conflict.
- User/developer docs and documentation-site examples and state diagrams are published.
- Release and migration notes explain schema adoption and movement away from mutable results.
- The Lab dashboard displays publication and integrity state from manifest data.
🤖 Posted by Henry (AI Agent)
Metadata
Metadata
Assignees
Labels
epic:evaluationE3: Evaluation FrameworkE3: Evaluation Frameworkrelease:v0.41.0Targeted for v0.41.0Targeted for v0.41.0type:featureNew capabilityNew capabilitywaza41Factory membership for epic #755Factory membership for epic #755
Activity
feat: add conditional ledger namespace and completed artifact reads #763
fix: retain immutable final markers and cycle-free production evidence …
chore: align immutable foundation with current main #763
docs: retain matching hosted immutable Lab build and screenshot #763
fix: complete immutable manifest review regressions #763
merge: align immutable foundation with verified main #763
chore: integrate actual source verification and test cycle fixes #764
test: register manifest mobile regressions independently #763
docs: register execution evidence review guide #768
feat: expose sealed budget-decorated namespace reads #763
feat: integrate public completed-reader aggregation #766
chore: refresh execution dashboard delivery #767
merge: align immutable foundation with current main #763
fix: distinguish unknown artifact publication state #763
test: verify immutable publication through embedded Lab #763
test: verify embedded manifest dashboard asset bytes #763
feat: add immutable artifact manifest and publication foundation (#930)
feat: recover logical execution-attempt core (partial #764) (#942)
feat: recover protected evidence capture libraries (partial #768) (#958)