7503c19b8f
- Implemented comprehensive tests for verdict artifact generation to ensure deterministic outputs across various scenarios, including identical inputs, parallel execution, and change ordering. - Created helper methods for generating sample verdict inputs and computing canonical hashes. - Added tests to validate the stability of canonical hashes, proof spine ordering, and summary statistics. - Introduced a new PowerShell script to update SHA256 sums for files, ensuring accurate hash generation and file integrity checks.
24 lines
882 B
Markdown
24 lines
882 B
Markdown
# VEX Consensus API (Contract Overview)
|
|
|
|
This document provides a high-level overview of consensus endpoints. The gateway and module dossiers define the authoritative routing, auth, and schema details.
|
|
|
|
## Common Headers
|
|
|
|
- `Authorization: Bearer <token>` (or DPoP where configured)
|
|
- `X-StellaOps-Tenant: <tenantId>` (required)
|
|
|
|
## Typical Endpoints
|
|
|
|
- `GET /v1/vex/consensus?artifact=...&advisory=...` — returns a single consensus record (plus conflicts).
|
|
- `GET /v1/vex/conflicts` — list outstanding conflicts with summary metadata.
|
|
- `GET /v1/vex/consensus/export` — deterministic JSONL export for Offline Kit / Export Center bundles.
|
|
- `POST /v1/vex/trust/weights` — tenant-admin update of trust tiers/weights (when enabled).
|
|
|
|
## Output Shape
|
|
|
|
See `docs/vex/consensus-json.md` for the record payload reference.
|
|
|
|
## References
|
|
|
|
- `docs/modules/vex-lens/architecture.md`
|