stella-ops.org/git.stella-ops.org
1
0
Fork 0
Code Issues Pull Requests Actions 16 Releases Wiki Activity
Files
108d1c64b323808d6085fca05818fc581c6b003a
git.stella-ops.org/docs/modules/excitor/README.md
master dd217b4546
Some checks failed
Docs CI / lint-and-preview (push) Has been cancelled
Details
feat: Implement approvals workflow and notifications integration 
- Added approvals orchestration with persistence and workflow scaffolding.
- Integrated notifications insights and staged resume hooks.
- Introduced approval coordinator and policy notification bridge with unit tests.
- Added approval decision API with resume requeue and persisted plan snapshots.
- Documented the Excitor consensus API beta and provided JSON sample payload.
- Created analyzers to flag usage of deprecated merge service APIs.
- Implemented logging for artifact uploads and approval decision service.
- Added tests for PackRunApprovalDecisionService and related components.
2025-11-06 08:48:13 +02:00

1.6 KiB
Raw Blame History

StellaOps Excitor

Excitor computes deterministic consensus across VEX claims, preserving conflicts and producing attestable evidence for policy suppression.

Latest updates (2025-11-05)

  • Consensus API beta documented with canonical JSON samples and DSSE packaging guidance (docs/updates/2025-11-05-excitor-consensus-beta.md).
  • README links to Link-Not-Merge consensus milestone and preview endpoints for downstream integration.

Responsibilities

  • Ingest Excititor observations and compute per-product consensus snapshots.
  • Provide APIs for querying canonical VEX positions and conflict sets.
  • Publish exports and DSSE-ready digests for downstream consumption.
  • Keep provenance weights and disagreement metadata.

Key components

  • Consensus engine and API host in StellaOps.Excitor.* (to-be-implemented).
  • Storage schema for consensus graphs.
  • Integration hooks for Policy Engine suppression logic.

Integrations & dependencies

  • Excititor for raw observations.
  • Policy Engine and UI for suppression stories.
  • CLI for evidence inspection.

Operational notes

  • Deterministic consensus algorithms (see architecture).
  • Planned telemetry for disagreement counts and freshness.
  • Offline exports aligning with Concelier/Excititor timelines.

Related resources

  • ./scoring.md
  • ../../vex/consensus-json.md (beta consensus payload sample)

Backlog references

  • DOCS-EXCITOR backlog referenced in architecture doc.
  • CLI parity tracked in ../../TASKS.md (CLI-GRAPH/VEX stories).

Epic alignment

  • Epic 7 – VEX Consensus Lens: deliver trust-weighted consensus snapshots, disagreement metadata, and explain APIs.