- Added `FilesystemPackRunProvenanceWriter` to write provenance manifests to the filesystem. - Introduced `MongoPackRunArtifactReader` to read artifacts from MongoDB. - Created `MongoPackRunProvenanceWriter` to store provenance manifests in MongoDB. - Developed unit tests for filesystem and MongoDB provenance writers. - Established `ITimelineEventStore` and `ITimelineIngestionService` interfaces for timeline event handling. - Implemented `TimelineIngestionService` to validate and persist timeline events with hashing. - Created PostgreSQL schema and migration scripts for timeline indexing. - Added dependency injection support for timeline indexer services. - Developed tests for timeline ingestion and schema validation.
1.8 KiB
1.8 KiB
VEX Consensus Lens agent guide
Mission
VEX Lens computes deterministic consensus across conflicting VEX statements while preserving raw provenance.
Key docs
- Module README
- Architecture
- Implementation plan
- Task board
- Observability runbook (offline import friendly)
How to get started
- Review ./architecture.md for consensus algorithm, trust model, and export contracts.
- Open sprint file
/docs/implplan/SPRINT_*.mdand locate stories for this component. - Check ./TASKS.md and update status before/after work.
- Read README/architecture for design context and update as the implementation evolves.
Guardrails
- Uphold Aggregation-Only Contract boundaries when consuming ingestion data.
- Preserve determinism and provenance in all derived outputs.
- Document offline/air-gap pathways for any new feature.
- Update telemetry/observability assets alongside feature work.
Required Reading
docs/modules/vex-lens/README.mddocs/modules/vex-lens/architecture.mddocs/modules/vex-lens/implementation_plan.mddocs/modules/platform/architecture-overview.md
Working Agreement
-
- Update task status to
DOING/DONEin both correspoding sprint file/docs/implplan/SPRINT_*.mdand the localTASKS.mdwhen you start or finish work.
- Update task status to
-
- Review this charter and the Required Reading documents before coding; confirm prerequisites are met.
-
- Keep changes deterministic (stable ordering, timestamps, hashes) and align with offline/air-gap expectations.
-
- Coordinate doc updates, tests, and cross-guild communication whenever contracts or workflows change.
-
- Revert to
TODOif you pause the task without shipping changes; leave notes in commit/PR descriptions for context.
- Revert to