π€ Auto-filed as prerequisite for artifact-attestation schema.
Repo: WasmAgent/wasmagent-protocol
Milestone: Milestone 4 β Evidence types beyond execution
Prerequisite for: artifact-attestation schema addition
Task
Create the foundational AEP (Artifact Evidence Protocol) infrastructure that individual AEP schemas depend on.
Files to create/modify
New files:
schemas/aep/ - Create AEP directory for artifact evidence schemas
schemas/aep/_base.schema.json (or similar base pattern) - Base schema that AEP schemas extend from (defines common fields like evidence_type, timestamp, etc.)
tests/fixtures/aep/README.md - Document fixture pattern for AEP schemas
Verify: Confirm schemas/index.json exists and is ready to register new AEP schemas
Acceptance criteria
schemas/aep/ directory exists
- A base schema or pattern exists that defines the common structure for AEP evidence types
schemas/index.json exists and can accept new AEP schema registrations
- Directory structure
tests/fixtures/{valid,invalid}/ exists and is ready for AEP fixtures
Implementation note
This is a foundational prerequisite. Once this infrastructure exists, individual AEP schema types (like artifact-attestation) can be added independently because:
- The parent directory structure exists
- The base schema pattern to extend from exists
- The index.json is ready to accept registrations
- The fixture structure is in place
Verify-first should return PROCEED for this issue since these are truly new foundational files that can be created independently.
π€ Auto-filed as prerequisite for artifact-attestation schema.
Repo: WasmAgent/wasmagent-protocol
Milestone: Milestone 4 β Evidence types beyond execution
Prerequisite for: artifact-attestation schema addition
Task
Create the foundational AEP (Artifact Evidence Protocol) infrastructure that individual AEP schemas depend on.
Files to create/modify
New files:
schemas/aep/- Create AEP directory for artifact evidence schemasschemas/aep/_base.schema.json(or similar base pattern) - Base schema that AEP schemas extend from (defines common fields like evidence_type, timestamp, etc.)tests/fixtures/aep/README.md- Document fixture pattern for AEP schemasVerify: Confirm
schemas/index.jsonexists and is ready to register new AEP schemasAcceptance criteria
schemas/aep/directory existsschemas/index.jsonexists and can accept new AEP schema registrationstests/fixtures/{valid,invalid}/exists and is ready for AEP fixturesImplementation note
This is a foundational prerequisite. Once this infrastructure exists, individual AEP schema types (like artifact-attestation) can be added independently because:
Verify-first should return PROCEED for this issue since these are truly new foundational files that can be created independently.