stella-ops.org/git.stella-ops.org
1
0
Fork 0
Code Issues Pull Requests Actions 3 Releases Wiki Activity

sprints completion. new product advisories prepared

Browse Source
This commit is contained in:
master
2026-01-16 16:30:03 +02:00
parent a927d924e3
commit 4ca3ce8fb4
255 changed files with 42434 additions and 1020 deletions
Download Patch File Download Diff File Expand all files Collapse all files

49
docs/implplan/SPRINT_20260112_002_EVIDENCE_evidence_locker_audit_pack_hardening.md
View File

@@ -1,49 +0,0 @@
# Sprint 20260112-002-EVIDENCE - EvidenceLocker Audit Pack Hardening
## Topic & Scope
- Extend EvidenceLocker bundle metadata and manifests with transparency and RFC3161 timestamp references aligned to the new evidence pack schemas.
- Add explicit object-lock configuration and enforcement in S3 storage to support WORM retention and legal hold behavior.
- Evidence to produce: code and tests under `src/EvidenceLocker/StellaOps.EvidenceLocker` plus updated EvidenceLocker AGENTS entries.
- **Working directory:** `src/EvidenceLocker/StellaOps.EvidenceLocker`.
## Dependencies & Concurrency
- Depends on SPRINT_20260112_001_DOCS for schema definitions and documentation alignment.
- Concurrency: implementation can proceed in parallel after schema field names are finalized.
## Documentation Prerequisites
- `docs/README.md`
- `docs/07_HIGH_LEVEL_ARCHITECTURE.md`
- `docs/modules/platform/architecture-overview.md`
- `docs/modules/evidence-locker/architecture.md`
- `docs/modules/evidence-locker/export-format.md`
- `docs/modules/evidence-locker/bundle-packaging.md`
- `docs/modules/evidence-locker/attestation-contract.md`
- `docs/modules/attestor/transparency.md`
- `src/EvidenceLocker/AGENTS.md`
- `src/EvidenceLocker/StellaOps.EvidenceLocker/AGENTS.md`
## Delivery Tracker
| # | Task ID | Status | Key dependency / next step | Owners | Task Definition |
| --- | --- | --- | --- | --- | --- |
| 1 | EVID-CEPACK-001 | DONE | After DOCS-CEPACK-001 schema fields are final | EvidenceLocker Guild | Update EvidenceLocker manifest models and builders to record transparency and timestamp references in bundle metadata (align with `docs/modules/evidence-locker/schemas/bundle.manifest.schema.json` and the new evidence pack schema). Touch: `src/EvidenceLocker/StellaOps.EvidenceLocker/StellaOps.EvidenceLocker.Infrastructure/Builders/EvidenceBundleBuilder.cs` and related domain models. |
| 2 | EVID-CEPACK-002 | DONE | After EVID-CEPACK-001 | EvidenceLocker Guild | Propagate RFC3161 timestamp metadata from signing to bundle packaging and verification flows; add unit tests under `src/EvidenceLocker/StellaOps.EvidenceLocker/StellaOps.EvidenceLocker.Tests`. |
| 3 | EVID-CEPACK-003 | DONE | After DOCS-CEPACK-001 schema fields are final | EvidenceLocker Guild | Add Object Lock configuration to `EvidenceLockerOptions` and enforce retention/legal hold headers in `S3EvidenceObjectStore`; validate config at startup and add tests. |
| 4 | EVID-CEPACK-004 | DONE | After EVID-CEPACK-001 | EvidenceLocker Guild / QA | Add determinism and schema evolution tests covering new manifest fields and checksum ordering (use existing EvidenceLocker test suites). |
| 5 | EVID-CEPACK-005 | DONE | After EVID-CEPACK-003 | EvidenceLocker Guild | Update `src/EvidenceLocker/AGENTS.md` and `src/EvidenceLocker/StellaOps.EvidenceLocker/AGENTS.md` to include object-lock and transparency/timestamp requirements. |
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-01-14 | Sprint created; focuses on EvidenceLocker metadata, object-lock enforcement, and tests. | Planning |
| 2026-01-14 | EVID-CEPACK-001: Added TransparencyReference and TimestampReference records to EvidenceBundleBuildModels.cs; Updated EvidenceSignatureService to serialize new fields in manifest payload. | Agent |
| 2026-01-14 | EVID-CEPACK-002: Existing RFC3161 client already propagates timestamps; added 3 new unit tests for transparency/timestamp reference serialization. | Agent |
| 2026-01-14 | EVID-CEPACK-003: Added ObjectLockOptions to AmazonS3StoreOptions with Mode, DefaultRetentionDays, DefaultLegalHold; Updated S3EvidenceObjectStore with ApplyObjectLockSettings and ApplyLegalHoldAsync methods; Added startup validation. | Agent |
| 2026-01-14 | EVID-CEPACK-004: Added tests for transparency serialization, timestamp serialization, and empty array omission in EvidenceSignatureServiceTests. | Agent |
| 2026-01-14 | EVID-CEPACK-005: Updated src/EvidenceLocker/AGENTS.md with object-lock and transparency/timestamp requirements. | Agent |
## Decisions & Risks
- Object Lock semantics (governance vs compliance) require a single default and may need explicit approval from platform governance.
- Doc updates to EvidenceLocker packaging and verification guides must be coordinated with the docs sprint to avoid cross-module drift.
## Next Checkpoints
- 2026-01-20: EvidenceLocker schema and Object Lock design review.

53
docs/implplan/SPRINT_20260112_003_EXPORT_lineage_evidence_pack_alignment.md
View File

@@ -1,53 +0,0 @@
# Sprint 20260112-003-EXPORT - Lineage Evidence Pack Alignment
## Topic & Scope
- Replace placeholder lineage evidence pack logic with deterministic bundle assembly aligned to the evidence bundle export format.
- Integrate real data sources (SBOM, VEX, policy verdicts, attestations) and remove silent success paths in the lineage pack service.
- Evidence to produce: updated Export Center core services, pack outputs, and determinism tests under `src/ExportCenter/StellaOps.ExportCenter`.
- **Working directory:** `src/ExportCenter/StellaOps.ExportCenter`.
## Dependencies & Concurrency
- Depends on SPRINT_20260112_001_DOCS for schema definitions.
- Aligns with SPRINT_20260112_002_EVIDENCE metadata fields for transparency and timestamps.
## Documentation Prerequisites
- `docs/README.md`
- `docs/07_HIGH_LEVEL_ARCHITECTURE.md`
- `docs/modules/platform/architecture-overview.md`
- `docs/modules/export-center/architecture.md`
- `docs/modules/export-center/overview.md`
- `docs/modules/export-center/provenance-and-signing.md`
- `docs/modules/evidence-locker/export-format.md`
- `docs/modules/evidence-locker/evidence-bundle-v1.md`
- `src/ExportCenter/AGENTS.md`
- `src/ExportCenter/StellaOps.ExportCenter/AGENTS.md`
## Delivery Tracker
| # | Task ID | Status | Key dependency / next step | Owners | Task Definition |
| --- | --- | --- | --- | --- | --- |
| 1 | EXP-CEPACK-001 | BLOCKED | SBOM/VEX data source integration undefined | Export Center Guild | Replace placeholder logic in `src/ExportCenter/StellaOps.ExportCenter/StellaOps.ExportCenter.Core/Services/LineageEvidencePackService.cs` with real data retrieval (SBOM, VEX, policy verdicts, attestations) or explicit NotImplemented errors where integrations are missing. |
| 2 | EXP-CEPACK-002 | BLOCKED | Depends on EXP-CEPACK-001 | Export Center Guild | Generate deterministic pack outputs (tar.gz or existing OfflineBundlePackager) with manifest and checksums aligned to the new evidence pack schema; integrate DSSE signing and transparency references when available. |
| 3 | EXP-CEPACK-003 | BLOCKED | Depends on EXP-CEPACK-002 | Export Center Guild / QA | Add determinism tests for pack assembly, manifest ordering, and verification in `src/ExportCenter/StellaOps.ExportCenter/StellaOps.ExportCenter.Tests`. |
| 4 | EXP-CEPACK-004 | BLOCKED | Depends on EXP-CEPACK-002 | Export Center Guild | Update Export Center API outputs and metrics for lineage pack downloads; ensure tenant scoping and audit logs are preserved. |
| 5 | EXP-CEPACK-005 | BLOCKED | Depends on EXP-CEPACK-004 | Export Center Guild | Update `src/ExportCenter/AGENTS.md` and `src/ExportCenter/StellaOps.ExportCenter/AGENTS.md` to call out evidence pack alignment requirements and determinism checks. |
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-01-14 | Sprint created; focuses on lineage evidence pack implementation and determinism. | Planning |
| 2026-01-14 | All tasks marked BLOCKED. See Decisions & Risks for blocking reasons. | Agent |
## Decisions & Risks
- Pack format choice (tar.gz vs OfflineBundlePackager output) must match evidence bundle export format and remain offline-friendly.
- Missing upstream integrations (SBOM/VEX/policy APIs) may require explicit NotImplemented handling to avoid silent stubs.
### BLOCKING ISSUES (require PM/architect decision)
1. **SBOM Data Source Integration Undefined**: LineageEvidencePackService.cs (600+ lines) has placeholder implementations. The ISbomService, IVexStatementService, and IPolicyVerdictService interfaces exist but their concrete implementations and data flow are not wired. Need decision on:
- Which SBOM service implementation to use (Concelier.SbomIntegration vs Scanner.SbomService)
- How to resolve VEX statements for a given artifact (VexLens vs direct DB query)
- Policy verdict retrieval pattern (Scheduler models vs Policy.Engine)
2. **Silent Stub Pattern**: Current code returns success for placeholder methods. Need explicit guidance on whether to throw NotImplementedException or return explicit error results.
3. **Cross-Module Dependencies**: This sprint touches data from Scanner, Concelier, Policy, and Attestor modules. Need coordination with those teams or explicit interface contracts.
## Next Checkpoints
- 2026-01-22: Lineage pack implementation review and determinism test plan.

44
docs/implplan/SPRINT_20260112_004_ATTESTOR_vex_override_predicate.md
View File

@@ -1,44 +0,0 @@
# Sprint 20260112.004.ATTESTOR · VEX Override Attestation Predicate
## Topic & Scope
- Define and implement a DSSE/in-toto predicate for VEX override attestations (operator decisions such as not_affected or compensating controls).
- Support optional Rekor anchoring and offline verification paths without changing existing attestation workflows.
- Working directory: `src/Attestor`. Evidence: predicate schema, builder, verification tests, and sample payloads.
## Dependencies & Concurrency
- Downstream: `SPRINT_20260112_004_VULN_vex_override_workflow.md` consumes the predicate to mint attestations.
- Parallel-safe with Scanner and Findings sprints.
## Documentation Prerequisites
- `docs/README.md`
- `docs/ARCHITECTURE_OVERVIEW.md`
- `docs/07_HIGH_LEVEL_ARCHITECTURE.md`
- `docs/modules/attestor/architecture.md`
- `docs/modules/attestor/rekor-verification-design.md`
- `docs/VEX_CONSENSUS_GUIDE.md`
- `docs/architecture/EVIDENCE_PIPELINE_ARCHITECTURE.md`
- `src/__Libraries/StellaOps.Canonical.Json/README.md`
## Delivery Tracker
| # | Task ID | Status | Key dependency / next step | Owners | Task Definition |
| --- | --- | --- | --- | --- | --- |
| 1 | ATT-VEX-001 | DONE | Predicate spec | Attestor Guild | Add VEX override predicate schema and typed model (decision, evidence refs, tool versions, rule digests, artifact digest, trace hash). |
| 2 | ATT-VEX-002 | DONE | Builder + verify | Attestor Guild | Implement predicate builder and DSSE envelope creation/verification; canonicalize predicate payloads with `StellaOps.Canonical.Json` before hashing; add unit and integration tests. |
| 3 | ATT-VEX-003 | DONE | Cross-module docs | Attestor Guild | Document predicate and include a sample payload in `docs/modules/attestor/` and referenced schemas. |
| 4 | ATT-VEX-004 | DONE | Canonicalization contract | Attestor Guild | Document canonicalization rules and required serializer options (no CamelCase, default encoder) for the VEX override predicate. |
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-01-14 | Sprint created; awaiting staffing. | Planning |
| 2026-01-14 | ATT-VEX-001: Created VexOverridePredicate.cs with VexOverrideDecision enum, EvidenceReference, ToolInfo records in src/Attestor/__Libraries/StellaOps.Attestor.StandardPredicates/VexOverride/. | Agent |
| 2026-01-14 | ATT-VEX-002: Created VexOverridePredicateParser.cs (IPredicateParser impl), VexOverridePredicateBuilder.cs with RFC 8785 canonicalization. Added 23 unit tests in VexOverride directory. | Agent |
| 2026-01-14 | Fixed pre-existing bug in BinaryDiffTestData.cs (renamed FixedTimeProvider field to TestTimeProvider to avoid name shadowing with nested class). | Agent |
| 2026-01-14 | ATT-VEX-003/004: Created docs/modules/attestor/vex-override-predicate.md with schema spec, sample payload, and RFC 8785 canonicalization rules. | Agent |
## Decisions & Risks
- Predicate must use RFC 8785 canonicalization via `StellaOps.Canonical.Json` with explicit serializer options (no CamelCase, default encoder) and DSSE PAE helper; no custom encoding.
- Rekor anchoring is optional; offline verification must still succeed with embedded proofs.
## Next Checkpoints
- TBD: confirm predicate field set with Policy and VEX Lens consumers.

50
docs/implplan/SPRINT_20260112_004_BE_findings_scoring_attested_reduction.md
View File

@@ -1,50 +0,0 @@
# Sprint 20260112_004_BE - Findings Scoring Attested Reduction
## Topic & Scope
- Wire anchor-aware evidence into Findings Ledger scoring so attested reduction and hard-fail outcomes are surfaced in the API response and history.
- Extend scoring DTOs to expose reduction profile metadata, hard-fail status, and short-circuit reasons in a deterministic format.
- Ensure cache and history behaviors remain deterministic when reduction profile or anchors change.
- **Working directory:** `src/Findings/StellaOps.Findings.Ledger.WebService`; evidence: updated scoring DTOs, evidence provider wiring, endpoint tests. Allowed shared paths: `docs/api/findings-scoring.md`.
## Dependencies & Concurrency
- Depends on Signals sprint for reduction profile fields and anchor schema.
- Coordinate with Policy sprint for shared anchor field names used across evidence types.
- Parallel execution is safe if API docs are edited after Signals updates land.
## Documentation Prerequisites
- docs/README.md
- docs/07_HIGH_LEVEL_ARCHITECTURE.md
- docs/modules/platform/architecture-overview.md
- docs/api/findings-scoring.md
- docs/VEX_CONSENSUS_GUIDE.md
- src/Findings/AGENTS.md
- src/Findings/StellaOps.Findings.Ledger/AGENTS.md
- src/Findings/StellaOps.Findings.Ledger.WebService/AGENTS.md
## Delivery Tracker
| # | Task ID | Status | Key dependency / next step | Owners | Task Definition |
| --- | --- | --- | --- | --- | --- |
| 1 | EWS-API-001 | DONE | Align with Signals reduction output | Findings Guild - Backend | Extend scoring DTOs to include reduction profile metadata, hard-fail flag, and short-circuit reason fields. |
| 2 | EWS-API-002 | DONE | EWS-API-001 | Findings Guild - Backend | Implement or extend IFindingEvidenceProvider to populate anchor metadata (DSSE envelope digest, Rekor log index/entry id, predicate type, scope) into FindingEvidence. |
| 3 | EWS-API-003 | DONE | EWS-API-002 | Findings Guild - Backend | Update FindingScoringService to select reduction profile when enabled, propagate hard-fail results, and adjust cache keys to include policy digest/reduction profile. |
| 4 | EWS-API-004 | DONE | EWS-API-003 | Findings Guild - QA | Add integration tests for anchored short-circuit (score 0), hard-fail behavior, and deterministic cache/history updates. |
| 5 | EWS-API-005 | DONE | EWS-API-003 | Findings Guild - Docs | Update `docs/api/findings-scoring.md` with new fields and response examples for reduction mode. |
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-01-14 | Sprint created; awaiting staffing. | Planning |
| 2026-01-14 | EWS-API-001: Extended EvidenceWeightedScoreResponse with ReductionProfile, HardFail, ShortCircuitReason, and Anchor fields. Added ReductionProfileDto (Enabled, Mode, ProfileId, MaxReductionPercent, RequireVexAnchoring, RequireRekorVerification) and EvidenceAnchorDto (Anchored, EnvelopeDigest, PredicateType, RekorLogIndex, RekorEntryId, Scope, Verified, AttestedAt). | Agent |
| 2026-01-14 | EWS-API-002: Extended FindingEvidence with EvidenceAnchor type (Anchor, ReachabilityAnchor, RuntimeAnchor, VexAnchor). Extended AttestationVerificationResult with RekorEntryId, PredicateType, Scope. Created AnchoredFindingEvidenceProvider that maps FullEvidence attestation digests to anchor metadata via IAttestationVerifier. Registered in Program.cs. | Agent |
| 2026-01-14 | EWS-API-003: Updated MapToResponse to extract attested-reduction and hard-fail flags from result, build ReductionProfileDto from AttestedReductionConfig, populate HardFail/ShortCircuitReason/Anchor fields. Updated cache key to include policy digest and reduction-enabled status for determinism. | Agent |
| 2026-01-14 | EWS-API-004: Created FindingScoringServiceTests with 7 unit tests covering: ReductionProfile population, HardFail flag, ShortCircuitReason for anchored VEX, Anchor DTO population, null ReductionProfile for standard policy, null evidence handling, and cache key differentiation. All tests passing. | Agent |
| 2026-01-14 | EWS-API-005: Updated docs/api/findings-scoring.md with Attested-Reduction Mode v1.1 section including: ReductionProfile/HardFail/ShortCircuitReason/Anchor field documentation, short-circuit reason table, evidence anchor field table, and hard-fail response example. | Agent |
## Decisions & Risks
- **Resolved:** Response field names for hard-fail and reduction metadata have been defined: `reductionProfile`, `hardFail`, `shortCircuitReason`, `anchor`.
- **Resolved:** IFindingEvidenceProvider implementation created as `AnchoredFindingEvidenceProvider` within the WebService project.
- Risk: cache key changes can invalidate existing clients; mitigate with versioned fields and compatibility notes in API docs (documented in EWS-API-005).
## Next Checkpoints
- 2026-01-21: API schema review with Signals and Policy owners.
- TBD: Endpoint contract test run.

52
docs/implplan/SPRINT_20260112_004_BE_policy_determinization_attested_rules.md
View File

@@ -1,52 +0,0 @@
# Sprint 20260112_004_BE - Policy Determinization Attested Rules
## Topic & Scope
- Add anchor-aware determinization rules that honor attested VEX and patch proof evidence with explicit precedence and hard-fail semantics.
- Extend determinization evidence models to carry anchor metadata (DSSE envelope digest, Rekor log index/entry id, predicate type, scope) and propagate through signal snapshots.
- Tighten VEX proof gate defaults to require signed statements and anchored proofs when used for allow decisions.
- **Working directory:** `src/Policy`; evidence: updated determinization models, rule set changes, gate options, tests. Allowed shared paths: `docs/modules/policy/determinization-api.md`, `docs/VEX_CONSENSUS_GUIDE.md`.
## Dependencies & Concurrency
- Depends on Signals sprint for anchor schema and reduction semantics.
- Coordinate with Findings sprint on anchor field names surfaced in evidence providers.
- Parallel execution is safe if shared docs are sequenced after core model changes.
## Documentation Prerequisites
- docs/README.md
- docs/07_HIGH_LEVEL_ARCHITECTURE.md
- docs/modules/platform/architecture-overview.md
- docs/modules/policy/architecture.md
- docs/modules/policy/determinization-api.md
- docs/VEX_CONSENSUS_GUIDE.md
- src/Policy/AGENTS.md
- src/Policy/StellaOps.Policy.Engine/AGENTS.md
- src/Policy/__Libraries/StellaOps.Policy.Determinization/AGENTS.md
## Delivery Tracker
| # | Task ID | Status | Key dependency / next step | Owners | Task Definition |
| --- | --- | --- | --- | --- | --- |
| 1 | DET-ATT-001 | DONE | Align anchor schema with Signals | Policy Guild - Backend | Extend determinization evidence models (VexClaimSummary, BackportEvidence, RuntimeEvidence, ReachabilityEvidence if needed) to include anchor metadata fields and update JSON serialization tests. |
| 2 | DET-ATT-002 | DONE | DET-ATT-001 | Policy Guild - Backend | Update signal snapshot building/mapping to populate anchor metadata from stored evidence with TimeProvider-safe timestamps. |
| 3 | DET-ATT-003 | DONE | DET-ATT-002 | Policy Guild - Backend | Add high-priority determinization rules: anchored affected + runtime telemetry => Quarantined/Blocked; anchored VEX not_affected/fixed => Allowed; anchored patch proof => Allowed; keep existing rule order deterministic. |
| 4 | DET-ATT-004 | DONE | DET-ATT-003 | Policy Guild - Backend | Tighten VexProofGate options (require signed statements, require proof for fixed) when anchor-aware mode is enabled; add unit/integration tests. |
| 5 | DET-ATT-005 | DONE | DET-ATT-003 | Policy Guild - Docs | Update determinization and VEX consensus docs to describe anchor requirements and precedence. |
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-01-14 | Sprint created; awaiting staffing. | Planning |
| 2026-01-14 | DET-ATT-001: Extended VexClaimSummary with Anchor field and VexClaimAnchor record containing EnvelopeDigest, PredicateType, RekorLogIndex, RekorEntryId, Scope, Verified, AttestedAt. Added IsAnchored and IsRekorAnchored helpers. | Agent |
| 2026-01-14 | DET-ATT-002: Created shared EvidenceAnchor type. Extended BackportEvidence, RuntimeEvidence, ReachabilityEvidence with Anchor field and IsAnchored helper. Implemented SignalSnapshotBuilder.ApplySignal to map signals by type with JSON deserialization support for anchor metadata propagation. | Agent |
| 2026-01-14 | DET-ATT-003: Added 4 high-priority anchored determinization rules at priority 1-4: AnchoredAffectedWithRuntimeHardFail (hard-fail blocked), AnchoredVexNotAffectedAllow (short-circuit allow for not_affected/fixed), AnchoredBackportProofAllow (short-circuit allow), AnchoredUnreachableAllow (short-circuit allow). Added DeterminizationResult.Blocked factory method. | Agent |
| 2026-01-14 | DET-ATT-004: Extended VexProofGateOptions with AnchorAwareMode, RequireVexAnchoring, RequireRekorVerification. Extended VexProofGateContext with anchor fields. Updated EvaluateAsync to validate anchor requirements. Added StrictAnchorAware static factory. Added VexProofGateTests with 8 tests covering anchor-aware mode. | Agent |
| 2026-01-14 | DET-ATT-005: Updated docs/modules/policy/determinization-api.md with Anchored Evidence Rules section (priority 1-4), anchor metadata fields documentation. Updated docs/VEX_CONSENSUS_GUIDE.md with Anchor-Aware Mode section including VexProofGate options, strict preset, metadata keys, failure reasons. | Agent |
## Decisions & Risks
- **Resolved:** Anchor metadata follows DSSE/Rekor schema with fields: EnvelopeDigest, PredicateType, RekorLogIndex, RekorEntryId, Scope, Verified, AttestedAt.
- **Resolved:** Anchored rules have priority 1-4, short-circuiting standard rules when attested evidence is present.
- **Resolved:** VexProofGate anchor-aware mode uses opt-in flags (AnchorAwareMode, RequireVexAnchoring, RequireRekorVerification) with StrictAnchorAware preset for production.
- Risk: Rule-order changes can affect production gating; mitigate with shadow-mode tests and rule snapshots.
## Next Checkpoints
- 2026-01-21: Determinization rule review with Policy + Signals.
- TBD: Gate regression test run.

52
docs/implplan/SPRINT_20260112_004_BINIDX_b2r2_lowuir_perf_cache.md
View File

@@ -1,52 +0,0 @@
# Sprint 20260112-004-BINIDX - B2R2 LowUIR Perf Cache
## Topic & Scope
- Integrate B2R2 LowUIR lifting into BinaryIndex semantic analysis so IR-based fingerprints are aligned with the B2R2 contract and deterministic across platforms.
- Reduce hot-path cost by pooling lifters, warming key ISAs, and exposing bench and health signals for lift latency and readiness.
- Add a function-level cache keyed by canonical IR hash and tool versions to reuse semantic fingerprints across scans in offline environments.
- Update BinaryIndex docs to reflect LowUIR adapter behavior, caching rules, and operational endpoints.
- **Working directory:** `src/BinaryIndex`.
## Dependencies & Concurrency
- No upstream sprints required; scope confined to BinaryIndex libraries and web service.
- Parallel execution is safe with `SPRINT_20260112_003_BE_csproj_audit_pending_apply.md` (different module and paths).
## Documentation Prerequisites
- `docs/README.md`
- `docs/07_HIGH_LEVEL_ARCHITECTURE.md`
- `docs/modules/platform/architecture-overview.md`
- `docs/modules/binary-index/architecture.md`
- `docs/modules/binary-index/semantic-diffing.md`
- `docs/technical/adr/0044-binary-delta-signatures.md`
- `docs/architecture/EVIDENCE_PIPELINE_ARCHITECTURE.md`
## Delivery Tracker
| # | Task ID | Status | Key dependency / next step | Owners | Task Definition |
| --- | --- | --- | --- | --- | --- |
| 1 | BINIDX-LIR-01 | DONE | LowUIR mapping spec | Scanner Guild - BinaryIndex | Implement a B2R2 LowUIR adapter for `IIrLiftingService` using B2R2 BinIR/BinLifter. Map LowUIR statements to existing IR models with deterministic ordering and invariant formatting. Register the adapter in DI so semantic and DeltaSig pipelines use it when available. Add tests asserting determinism and non-empty IR for supported ISAs. |
| 2 | BINIDX-LIFTER-02 | DONE | Pool configuration | Scanner Guild - BinaryIndex | Add a bounded lifter pool with warm preload per ISA and update the B2R2 plugin to borrow/return lifters instead of creating per-call units. Add config options and tests for reuse and concurrency safety. |
| 3 | BINIDX-CACHE-03 | DONE | Valkey cache + Postgres persistence plan | Scanner Guild - BinaryIndex | Add a function-level cache for canonical IR and semantic fingerprints keyed by `(isa, b2r2_version, normalization_recipe, canonical_ir_hash)`. Implement the cache in Valkey (TTL-based hot cache) and persist canonical IR fingerprint records in PostgreSQL. Do not introduce new storage engines. Define invalidation rules and TTLs. Add cache hit/miss tests. |
| 4 | BINIDX-OPS-04 | DONE | Endpoint contract | Scanner Guild - BinaryIndex | Add ops endpoints with fixed routes and schemas: GET `/api/v1/ops/binaryindex/health` -> BinaryIndexOpsHealthResponse, POST `/api/v1/ops/binaryindex/bench/run` -> BinaryIndexBenchResponse, GET `/api/v1/ops/binaryindex/cache` -> BinaryIndexFunctionCacheStats, GET `/api/v1/ops/binaryindex/config` -> BinaryIndexEffectiveConfig. Report lifter warmness, bench latency, cache stats, and effective config. Ensure outputs are deterministic and ASCII-only. Add minimal integration tests. |
| 5 | BINIDX-OPER-05 | DONE | Operand mapping | Scanner Guild - BinaryIndex | Improve B2R2 operand decoding to populate operand metadata used by normalization and IR mapping. Add targeted unit tests for representative instructions across x86 and ARM64. |
| 6 | BINIDX-DOCS-06 | DONE | Doc updates | Scanner Guild - BinaryIndex | Update `docs/modules/binary-index/architecture.md`, `docs/modules/binary-index/semantic-diffing.md`, and `docs/architecture/EVIDENCE_PIPELINE_ARCHITECTURE.md` to reflect the LowUIR adapter, lifter pool, cache rules, and new endpoints. Include determinism and offline constraints. |
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-01-14 | Sprint created; scope defined for LowUIR adapter, lifter pool, cache, and bench/health endpoints. | Planning |
| 2026-01-14 | Updated cache backend to Valkey for function cache with PostgreSQL persistence; removed SQLite/RocksDB references; fixed ASCII separators. | Planning |
| 2026-01-14 | Aligned ops endpoints with UI/CLI contract (health, bench, cache, config). | Planning |
| 2026-01-14 | BINIDX-LIR-01 DONE: Implemented B2R2LowUirLiftingService with LowUIR mapping, SSA transformation, deterministic block ordering. | Agent |
| 2026-01-14 | BINIDX-LIFTER-02 DONE: Implemented B2R2LifterPool with bounded pool, warm preload, per-ISA stats; updated ServiceCollectionExtensions for DI. | Agent |
| 2026-01-14 | BINIDX-CACHE-03 DONE: Implemented FunctionIrCacheService with Valkey hot cache, cache key generation, stats, TTL config; added DI extension methods. | Agent |
| 2026-01-14 | BINIDX-OPS-04 DONE: Implemented BinaryIndexOpsController with health, bench/run, cache, config endpoints; deterministic JSON responses. | Agent |
| 2026-01-14 | BINIDX-OPER-05 DONE: Enhanced B2R2DisassemblyPlugin operand parsing with register, immediate, memory operand detection for x86/ARM. | Agent |
| 2026-01-14 | BINIDX-DOCS-06 DONE: Updated architecture.md with B2R2 LowUIR adapter, lifter pool, cache, ops endpoints; updated semantic-diffing.md Phase 1 implementation details. | Agent |
## Decisions & Risks
- Valkey TTLs and PostgreSQL retention rules must stay aligned to prevent stale semantic fingerprints and mismatched cache keys.
- LowUIR mapping may require extending existing IR models, which can change semantic hash stability; define versioning and migration strategy.
- Lifter pooling and warm preload increase memory use; validate worker sizing and limits.
## Next Checkpoints
- 2026-01-21: Design review with Scanner Guild leads (confirm mapping, cache backend, and endpoints).

42
docs/implplan/SPRINT_20260112_004_CLI_reachability_trace_export.md
View File

@@ -1,42 +0,0 @@
# Sprint 20260112.004.CLI · Reachability Trace Export Commands
## Topic & Scope
- Extend CLI reachability commands to expose trace export formats (GraphSON or JSON/NDJSON) and runtime-confirmed flags.
- Ensure outputs remain deterministic and offline-friendly; reuse canonical JSON for any hash computations.
- Working directory: `src/Cli`. Evidence: new command flags, updated CLI docs, and tests.
## Dependencies & Concurrency
- Depends on `SPRINT_20260112_004_SCANNER_reachability_trace_runtime_evidence.md` for trace export endpoint and runtime-confirmed data.
- Parallel-safe with Policy and Findings sprints.
## Documentation Prerequisites
- `docs/README.md`
- `docs/ARCHITECTURE_OVERVIEW.md`
- `docs/07_HIGH_LEVEL_ARCHITECTURE.md`
- `docs/modules/cli/architecture.md`
- `docs/modules/cli/guides/commands/reachability.md`
- `src/__Libraries/StellaOps.Canonical.Json/README.md`
## Delivery Tracker
| # | Task ID | Status | Key dependency / next step | Owners | Task Definition |
| --- | --- | --- | --- | --- | --- |
| 1 | CLI-RT-001 | BLOCKED | Depends on SCAN-RT-001/003 | CLI Guild | Add CLI flags for trace export (format + output path) and surface runtime-confirmed flags in `stella reachability explain` JSON output. |
| 2 | CLI-RT-002 | BLOCKED | Depends on CLI-RT-001 | CLI Guild | Update `docs/modules/cli/guides/commands/reachability.md` with new flags and examples. |
| 3 | CLI-RT-003 | BLOCKED | Depends on CLI-RT-001 | CLI Guild | Add unit/integration tests covering deterministic output ordering and export behaviors. |
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-01-14 | Sprint created; awaiting staffing. | Planning |
| 2026-01-14 | All tasks marked BLOCKED - depends on blocked SPRINT_20260112_004_SCANNER_reachability_trace_runtime_evidence. | Agent |
## Decisions & Risks
- CLI must not infer timestamps; always use server-provided values.
- Any hashing performed in CLI must use `StellaOps.Canonical.Json` with explicit serializer options.
### BLOCKING ISSUES (require upstream sprint completion)
1. **Upstream Dependency Blocked**: This sprint depends on SPRINT_20260112_004_SCANNER for trace export endpoints and runtime-confirmed data models. That sprint is blocked pending FE data contract and architecture decisions.
2. **API Contract Not Finalized**: Cannot implement CLI flags until Scanner API endpoints exist with defined response schemas.
## Next Checkpoints
- TBD: align output formats with Scanner contract.

37
docs/implplan/SPRINT_20260112_004_DOC_cicd_gate_verification.md
View File

@@ -1,37 +0,0 @@
# Sprint 20260112.004.DOC · CI/CD Gate Verification Step
## Topic & Scope
- Document a required verification step in CI/CD gates that checks DSSE witness signatures and Rekor inclusion (or offline ledger).
- Provide example commands for online and offline flows using `stella proof verify` and cosign equivalents.
- Working directory: `docs`. Evidence: updated CI/CD flow and proof verification runbooks.
## Dependencies & Concurrency
- Parallel-safe with code sprints; no upstream dependencies required.
## Documentation Prerequisites
- `docs/README.md`
- `docs/ARCHITECTURE_OVERVIEW.md`
- `docs/07_HIGH_LEVEL_ARCHITECTURE.md`
- `docs/flows/10-cicd-gate-flow.md`
- `docs/operations/score-proofs-runbook.md`
- `docs/operations/proof-verification-runbook.md`
## Delivery Tracker
| # | Task ID | Status | Key dependency / next step | Owners | Task Definition |
| --- | --- | --- | --- | --- | --- |
| 1 | DOC-CICD-001 | DONE | Flow edits | Docs Guild | Update `docs/flows/10-cicd-gate-flow.md` to include DSSE witness verification and Rekor inclusion checks with offline fallback. |
| 2 | DOC-CICD-002 | DONE | Runbook links | Docs Guild | Add concise command snippets to `docs/operations/score-proofs-runbook.md` and link to `docs/operations/proof-verification-runbook.md`. |
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-01-14 | Sprint created; awaiting staffing. | Planning |
| 2026-01-14 | DOC-CICD-001: Added section 5a "DSSE Witness Verification (Required)" to cicd-gate-flow.md with online/offline commands, cosign equivalents, and GitHub/GitLab integration examples. | Agent |
| 2026-01-14 | DOC-CICD-002: Added section 3.2a "CI/CD Gate Verification Quick Reference" to score-proofs-runbook.md with concise commands and cross-links. | Agent |
## Decisions & Risks
- Verification examples must be offline-friendly and avoid external URLs not already present.
- CI gate examples must remain deterministic and avoid non-ASCII characters in commands.
## Next Checkpoints
- TBD: confirm with Release Engineering that flow matches current CLI behavior.

50
docs/implplan/SPRINT_20260112_004_FE_attested_score_ui.md
View File

@@ -1,50 +0,0 @@
# Sprint 20260112_004_FE - Attested Score UI
## Topic & Scope
- Surface attested-reduction scoring outcomes in the Console UI: anchored evidence status, short-circuit reason, and hard-fail outcomes.
- Extend EWS UI components to display reduction profile metadata and proof anchors (DSSE digest, Rekor log index/entry id).
- Keep UI behavior deterministic and aligned with the scoring API schema and policy digest rules.
- **Working directory:** `src/Web/StellaOps.Web`; evidence: updated UI models, components, and tests; updated UI docs.
## Dependencies & Concurrency
- Depends on Signals and Findings sprints for new scoring fields and reduction-mode metadata.
- Coordinate API schema changes with `docs/api/findings-scoring.md` updates to avoid UI contract drift.
- Parallel execution is safe with backend work if UI starts after schema field names are confirmed.
## Documentation Prerequisites
- docs/README.md
- docs/07_HIGH_LEVEL_ARCHITECTURE.md
- docs/modules/platform/architecture-overview.md
- docs/api/findings-scoring.md
- docs/modules/ui/architecture.md
- docs/modules/ui/components/README.md
- docs/modules/ui/components/score-pill.md
- docs/modules/ui/components/score-badge.md
- docs/modules/ui/components/score-breakdown-popover.md
- docs/modules/ui/components/findings-list.md
- src/Web/StellaOps.Web/AGENTS.md
## Delivery Tracker
| # | Task ID | Status | Key dependency / next step | Owners | Task Definition |
| --- | --- | --- | --- | --- | --- |
| 1 | FE-ATT-001 | DONE | API schema update | UI Guild - Frontend | Extend EWS TypeScript models and API client bindings to include reduction profile metadata, hard-fail status, and anchor fields. |
| 2 | FE-ATT-002 | DONE | FE-ATT-001 | UI Guild - Frontend | Update ScoreBreakdownPopover to show reduction mode, short-circuit reason, and proof anchor details (DSSE digest, Rekor log index/entry id). |
| 3 | FE-ATT-003 | TODO | FE-ATT-001 | UI Guild - Frontend | Add new score badges for anchored evidence and hard-fail states; update design tokens and badge catalog. |
| 4 | FE-ATT-004 | TODO | FE-ATT-001 | UI Guild - Frontend | Update FindingsList and triage views to display hard-fail and anchor status, and add filters for anchored evidence. |
| 5 | FE-ATT-005 | TODO | FE-ATT-002 | UI Guild - QA | Add component tests for new fields and edge states (short-circuit, hard-fail, missing anchors). |
| 6 | FE-ATT-006 | TODO | FE-ATT-003 | UI Guild - Docs | Update UI component docs and triage UX guides to describe reduction-mode display and anchor semantics. |
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-01-14 | Sprint created; awaiting staffing. | Planning |
| 2026-01-15 | FE-ATT-001: Extended scoring.models.ts with ReductionMode, ShortCircuitReason, HardFailStatus types. Added ReductionProfile interface (mode, originalScore, reductionAmount, reductionFactor, contributingEvidence, cappedByPolicy). Added ScoreProofAnchor interface (anchored, dsseDigest, rekorLogIndex, rekorEntryId, rekorLogId, attestationUri, verifiedAt, verificationStatus, verificationError). Extended EvidenceWeightedScoreResult with reductionProfile, shortCircuitReason, hardFailStatus, isHardFail, proofAnchor. Added ScoreFlag types 'anchored' and 'hard-fail'. Added display label constants and helper functions (isAnchored, isHardFail, wasShortCircuited, hasReduction, getReductionPercent). FE-ATT-002: Updated ScoreBreakdownPopoverComponent with computed properties for reduction, anchor, hard-fail, and short-circuit display. Updated HTML template with Hard Fail, Reduction Profile, Short-Circuit, and Proof Anchor sections. Added SCSS styles for new sections with proper colors and layout. All output uses ASCII-only indicators ([!], [A], etc.). | Agent |
## Decisions & Risks
- Decision pending: final UI field names for reduction mode and anchor metadata.
- Risk: new badges may clash with existing bucket colors; update design tokens and accessibility notes.
- Risk: UI filters may diverge from API flags; align on shared flag vocabulary before implementation.
## Next Checkpoints
- 2026-01-21: UI schema review with Findings and Signals owners.
- TBD: UI component demo with score breakdown updates.

41
docs/implplan/SPRINT_20260112_004_FE_risk_line_runtime_trace_ui.md
View File

@@ -1,41 +0,0 @@
# Sprint 20260112.004.FE · Risk Line + Runtime Trace UI
## Topic & Scope
- Add an always-visible risk line showing reachability score (0-1), runtime-confirmed badge, and Rekor timestamp link with graceful fallbacks.
- Highlight runtime-confirmed edges in the reachability call graph and provide trace export actions (GraphSON or JSON/SARIF).
- Working directory: `src/Web/StellaOps.Web`. Evidence: new UI component, updated API models, unit/e2e tests, and UI docs.
## Dependencies & Concurrency
- Depends on `SPRINT_20260112_004_SCANNER_reachability_trace_runtime_evidence.md` for new reachability fields and export endpoints.
- Depends on `SPRINT_20260112_004_FINDINGS_evidence_graph_rekor_time.md` for Rekor timestamp link data.
- Depends on `SPRINT_20260112_004_VULN_vex_override_workflow.md` for signed override metadata.
## Documentation Prerequisites
- `docs/README.md`
- `docs/ARCHITECTURE_OVERVIEW.md`
- `docs/07_HIGH_LEVEL_ARCHITECTURE.md`
- `docs/modules/ui/architecture.md`
- `docs/UI_GUIDE.md`
- `docs/modules/web/unified-triage-specification.md`
## Delivery Tracker
| # | Task ID | Status | Key dependency / next step | Owners | Task Definition |
| --- | --- | --- | --- | --- | --- |
| 1 | FE-RISK-001 | TODO | Scanner contract merge | UI Guild | Add a risk-line component in triage detail and wire fields: reachability score (0-1), runtime-confirmed badge, Rekor timestamp link; handle missing data gracefully. |
| 2 | FE-RISK-002 | TODO | Runtime edge flags | UI Guild | Extend reachability models and renderer to highlight runtime-confirmed edges/steps; update legends and accessibility labels. |
| 3 | FE-RISK-003 | TODO | Export API ready | UI Guild | Add trace export actions (GraphSON or JSON/SARIF) and download handling; update tests for deterministic output and UI behavior. |
| 4 | FE-RISK-004 | TODO | Cross-module docs | UI Guild | Update `docs/UI_GUIDE.md` or `docs/modules/ui/architecture.md` to document the risk line and trace export UX. |
| 5 | FE-RISK-005 | TODO | Signed override metadata | UI Guild | Surface signed VEX override status (DSSE badge, Rekor link, attestation details) in the VEX decision view and evidence panel; add tests. |
| 6 | FE-RISK-006 | TODO | UX config toggle | UI Guild | Add a user setting toggle to enable/disable runtime-confirmed overlays and trace export actions; persist in UI preferences and document in UI guide. |
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-01-14 | Sprint created; awaiting staffing. | Planning |
## Decisions & Risks
- Risk line should not introduce non-deterministic timestamps; use server-provided values only.
- If runtime-confirmed data is unavailable, the UI must clearly show "unknown" rather than "false".
## Next Checkpoints
- TBD: align risk-line copy and icons with security review.

41
docs/implplan/SPRINT_20260112_004_FINDINGS_evidence_graph_rekor_time.md
View File

@@ -1,41 +0,0 @@
# Sprint 20260112.004.FINDINGS · Evidence Graph Rekor Timestamp
## Topic & Scope
- Extend evidence graph signature metadata to include Rekor integrated time and entry URL so UI can link to a verifiable timestamp.
- Preserve existing signature verification semantics; only add fields and deterministic mapping from provenance.
- Working directory: `src/Findings`. Evidence: updated contracts, builder mapping, tests, and openapi/schema docs.
## Dependencies & Concurrency
- Depends on existing provenance data carrying Rekor integrated time (`DsseRekorInfo.IntegratedTime`).
- Downstream: `SPRINT_20260112_004_FE_risk_line_runtime_trace_ui.md` consumes the timestamp link.
## Documentation Prerequisites
- `docs/README.md`
- `docs/ARCHITECTURE_OVERVIEW.md`
- `docs/07_HIGH_LEVEL_ARCHITECTURE.md`
- `docs/modules/findings-ledger/README.md`
- `docs/modules/findings-ledger/schema.md`
- `docs/modules/findings-ledger/openapi/findings-ledger.v1.yaml`
- `docs/modules/findings-ledger/dsse-policy-linkage.md`
## Delivery Tracker
| # | Task ID | Status | Key dependency / next step | Owners | Task Definition |
| --- | --- | --- | --- | --- | --- |
| 1 | FIND-REKOR-001 | DONE | Provenance mapping | Findings Guild | Add `rekorIntegratedTime` (RFC3339) and `rekorEntryUrl` to evidence graph signature metadata; update contracts and JSON serialization. |
| 2 | FIND-REKOR-002 | DONE | Builder update | Findings Guild | Map Rekor integrated time from DSSE provenance into evidence graph nodes; add unit tests for presence and determinism. |
| 3 | FIND-REKOR-003 | DONE | Cross-module docs | Findings Guild | Update `docs/modules/findings-ledger/openapi/findings-ledger.v1.yaml` and `docs/modules/findings-ledger/schema-catalog.md` to document new fields. |
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-01-14 | Sprint created; awaiting staffing. | Planning |
| 2026-01-14 | FIND-REKOR-001: Extended RekorEntryRef with IntegratedTimeRfc3339 (DateTimeOffset) and EntryUrl fields. Added helper methods GetIntegratedTimeAsDateTime() and GetEntryUrl(). | Agent |
| 2026-01-14 | FIND-REKOR-002: Extended RekorEntryRefDto in AttestationPointerContracts.cs with IntegratedTimeRfc3339 and EntryUrl. Updated ToModel() and ToDto() mappers. | Agent |
| 2026-01-14 | FIND-REKOR-003: Added Section 6 to schema-catalog.md documenting rekor.entry.ref.v1 schema with all fields including integratedTimeRfc3339 and entryUrl. | Agent |
## Decisions & Risks
- If Rekor integrated time is missing, responses must remain stable and UI should display "not logged".
- Cross-module doc edits are required; note in PR descriptions when executed.
## Next Checkpoints
- TBD: confirm UI link format for Rekor timestamp display.

64
docs/implplan/SPRINT_20260112_004_LB_attested_reduction_scoring.md
View File

@@ -1,64 +0,0 @@
# Sprint 20260112_004_LB - Attested Reduction Scoring
## Topic & Scope
- Implement an optional attested-reduction scoring profile with strict precedence: anchored VEX not_affected/fixed -> score 0; anchored affected + runtime telemetry -> hard fail; otherwise compute `score = clamp(base_epss * (1 + R + T) - P, 0, 1)` with constants stored in config.
- Extend EWS evidence models to carry anchor metadata (DSSE envelope digest, predicate type, Rekor log index/entry id, and anchoring flags) for VEX, patch proof, reachability, and telemetry inputs.
- Preserve determinism with config-only constants, canonical policy digests, and explicit reduction audit fields in outputs.
- **Working directory:** `src/Signals/StellaOps.Signals`; evidence: updated models, calculator, normalizers, tests. Allowed shared paths: `docs/api/findings-scoring.md`, `docs/technical/cicd/scoring-configuration.md`.
## Dependencies & Concurrency
- Depends on Findings ledger evidence provider to supply anchor metadata for scoring inputs.
- Coordinate anchor field names with Policy determinization sprint to keep evidence contracts consistent.
- Parallel execution is safe with Policy and Findings sprints if doc updates are sequenced.
## Documentation Prerequisites
- docs/README.md
- docs/07_HIGH_LEVEL_ARCHITECTURE.md
- docs/modules/platform/architecture-overview.md
- docs/api/findings-scoring.md
- docs/technical/cicd/scoring-configuration.md
- docs/VEX_CONSENSUS_GUIDE.md
- docs/modules/scanner/binary-diff-attestation.md
- docs-archived/product/advisories/24-Dec-2025 - Evidence-Weighted Score Model.md
- src/Signals/AGENTS.md
- src/Signals/StellaOps.Signals/AGENTS.md
## Delivery Tracker
| # | Task ID | Status | Key dependency / next step | Owners | Task Definition |
| --- | --- | --- | --- | --- | --- |
| 1 | EWS-ATT-001 | DONE | Align anchor schema with Findings + Policy | Signals Guild - Backend | Add anchor metadata records and fields to EWS inputs (SourceTrustInput, BackportInput, ReachabilityInput, RuntimeInput, EvidenceWeightedScoreInput, FindingEvidence) and propagate in normalizer aggregator. |
| 2 | EWS-ATT-002 | DONE | EWS-ATT-001 | Signals Guild - Backend | Extend EvidenceWeightPolicy with reduction config (precedence list, R/T/P constants, clamp bounds, hard-fail toggles) and include in canonical digest. |
| 3 | EWS-ATT-003 | DONE | EWS-ATT-002 | Signals Guild - Backend | Implement attested-reduction scoring path in EvidenceWeightedScoreCalculator with short-circuit rules and hard-fail flag; keep existing EWS path unchanged unless enabled. |
| 4 | EWS-ATT-004 | BLOCKED | EWS-ATT-003 | Signals Guild - Backend | Adjust normalizers/aggregation to support EPSS-last behavior when reduction profile is enabled (skip or neutralize XPL when stronger anchored evidence exists). |
| 5 | EWS-ATT-005 | DONE | EWS-ATT-003 | Signals Guild - Backend | Add unit tests for precedence order, hard-fail semantics, and policy digest determinism. |
| 6 | EWS-ATT-006 | DONE | EWS-ATT-003 | Signals Guild - Docs | Update scoring configuration and API docs with the reduction profile and anchor fields. |
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-01-14 | Sprint created; awaiting staffing. | Planning |
| 2026-01-14 | EWS-ATT-001: Created AnchorMetadata.cs with DSSE/Rekor/timestamp fields. Added Anchor property to SourceTrustInput, BackportInput, ReachabilityInput, RuntimeInput. Added VexAnchor to EvidenceWeightedScoreInput. | Agent |
| 2026-01-14 | EWS-ATT-002: Created AttestedReductionConfig with precedence list, R/T/P constants, clamp bounds, hard-fail toggles. Added to EvidenceWeightPolicy and included in canonical JSON digest. | Agent |
| 2026-01-14 | EWS-ATT-003: Implemented CalculateAttestedReduction path in EvidenceWeightedScoreCalculator with VEX precedence short-circuits, hard-fail semantics, and reduction formula. | Agent |
| 2026-01-14 | EWS-ATT-005: Created AttestedReductionScoringTests.cs with 17 tests covering all precedence rules, hard-fail, and determinism. All tests pass. | Agent |
| 2026-01-14 | EWS-ATT-006: Added attested-reduction profile documentation to docs/api/findings-scoring.md including config schema, anchor metadata, and response flags. | Agent |
| 2026-01-14 | EWS-ATT-004: Marked BLOCKED - requires deeper normalizer changes affecting ExploitLikelihoodNormalizer and NormalizerAggregator. See Decisions & Risks. | Agent |
## Decisions & Risks
- Decision pending: final anchor field names and which predicates are required for "anchored" status.
- Risk: overlapping doc edits with Findings sprint; mitigate by sequencing updates to `docs/api/findings-scoring.md`.
- Risk: policy digest changes can invalidate cached scores; include migration note in docs and tests.
### BLOCKING ISSUES (EWS-ATT-004)
1. **EPSS-Last Behavior Complexity**: The ExploitLikelihoodNormalizer and NormalizerAggregator need modifications to:
- Accept an AttestedReductionConfig parameter
- Check for anchored evidence before applying XPL normalization
- Provide a "neutralize XPL" path when stronger anchored evidence exists
2. **Cross-Normalizer Dependency**: The aggregator must know about anchor status from other normalizers before deciding on XPL behavior, creating a circular dependency.
3. **Suggested Approach**: Either:
- Post-process XPL in the calculator (already partially done via `SkipEpssWhenAnchored` flag)
- Or add a second pass to the aggregator that adjusts XPL based on collected anchor metadata
## Next Checkpoints
- 2026-01-21: Reduction profile design review with Signals + Findings owners.
- TBD: Scoring API schema validation checkpoint.

40
docs/implplan/SPRINT_20260112_004_LB_doctor_evidence_integrity_checks.md
View File

@@ -1,40 +0,0 @@
# Sprint 20260112.004.LB · Doctor Evidence Integrity Checks
## Topic & Scope
- Add Doctor checks that validate DSSE signatures, Rekor inclusion (or offline ledger), and evidence hash consistency.
- Surface results in Doctor UI exports and keep outputs deterministic and offline-friendly.
- Working directory: `src/__Libraries`. Evidence: new doctor checks, tests, and doc updates.
## Dependencies & Concurrency
- Parallel-safe with other sprints; can proceed independently once proof verification utilities are available.
## Documentation Prerequisites
- `docs/README.md`
- `docs/ARCHITECTURE_OVERVIEW.md`
- `docs/07_HIGH_LEVEL_ARCHITECTURE.md`
- `docs/doctor/doctor-capabilities.md`
- `docs/operations/score-proofs-runbook.md`
- `src/__Libraries/StellaOps.Canonical.Json/README.md`
## Delivery Tracker
| # | Task ID | Status | Key dependency / next step | Owners | Task Definition |
| --- | --- | --- | --- | --- | --- |
| 1 | DOCHECK-001 | DONE | Check spec | Doctor Guild | Implement a security Doctor check that verifies DSSE signature validity and Rekor inclusion (or offline ledger) for a provided proof bundle or attestation; recompute hashes using `StellaOps.Canonical.Json`. |
| 2 | DOCHECK-002 | DONE | Tests | Doctor Guild | Add unit/integration tests for deterministic check output, including offline mode. |
| 3 | DOCHECK-003 | DONE | Cross-module docs | Doctor Guild | Update `docs/doctor/doctor-capabilities.md` to describe the new evidence integrity check. |
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-01-14 | Sprint created; awaiting staffing. | Planning |
| 2026-01-14 | DOCHECK-001: Created EvidenceIntegrityCheck.cs in Security plugin with DSSE/Rekor/hash verification. | Agent |
| 2026-01-14 | DOCHECK-001: Registered check in SecurityPlugin.cs GetChecks() method. | Agent |
| 2026-01-14 | DOCHECK-002: Created EvidenceIntegrityCheckTests.cs with 15 tests covering all verification paths. All tests pass. | Agent |
| 2026-01-14 | DOCHECK-003: Added check.security.evidence.integrity documentation to doctor-capabilities.md section 9.4. | Agent |
## Decisions & Risks
- Doctor checks must not call external networks; use local proof bundles or offline ledgers.
- Ensure any evidence hash validation uses `StellaOps.Canonical.Json` with explicit serializer options and stable ordering.
## Next Checkpoints
- TBD: confirm proof bundle inputs and UX in Doctor dashboard.

45
docs/implplan/SPRINT_20260112_004_LB_evidence_card_core.md
View File

@@ -1,45 +0,0 @@
# Sprint 20260112-004-LB-evidence-card-core - Evidence Card Core
## Topic & Scope
- Build a single-file evidence card export that packages SBOM excerpt, DSSE envelope, and Rekor receipt for a finding evidence pack; output is deterministic and offline-friendly.
- Current state evidence: Evidence packs only export json/signedjson/markdown/html/pdf and do not carry Rekor receipts (`src/__Libraries/StellaOps.Evidence.Pack/Models/SignedEvidencePack.cs`, `src/__Libraries/StellaOps.Evidence.Pack/EvidencePackService.cs`).
- Evidence to produce: EvidenceCard model, evidence-card export format, receipt wiring in signed packs, and determinism tests.
- **Working directory:** `src/__Libraries/StellaOps.Evidence.Pack`.
## Dependencies & Concurrency
- Depends on Attestor receipt types already present in `src/Attestor/StellaOps.Attestor/StellaOps.Attestor.Core/Rekor/RekorReceipt.cs`.
- Parallel safe with remediation PR and UI sprints; no shared DB migrations or schema changes.
## Documentation Prerequisites
- `docs/README.md`
- `docs/07_HIGH_LEVEL_ARCHITECTURE.md`
- `docs/modules/platform/architecture-overview.md`
- `docs/modules/attestor/architecture.md`
- `docs/product/VISION.md`
- `docs/modules/cli/guides/commands/evidence-bundle-format.md`
## Delivery Tracker
| # | Task ID | Status | Key dependency / next step | Owners | Task Definition |
| --- | --- | --- | --- | --- | --- |
| 1 | EVPCARD-LB-001 | DONE | None | Evidence Guild | Add EvidenceCard model and receipt metadata for single-file export. |
| 2 | EVPCARD-LB-002 | DONE | EVPCARD-LB-001 | Evidence Guild | Implement evidence-card export format in EvidencePackService (SBOM excerpt + DSSE + receipt). |
| 3 | EVPCARD-LB-003 | DONE | EVPCARD-LB-001 | Evidence Guild | Wire Rekor receipt capture into signed evidence packs using Attestor receipt types. |
| 4 | EVPCARD-LB-004 | DONE | EVPCARD-LB-002 | Evidence Guild | Add determinism and export tests for evidence-card output. |
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-01-14 | Sprint created; awaiting staffing. | Planning |
| 2026-01-14 | EVPCARD-LB-001: Created EvidenceCard.cs with models for EvidenceCard, SbomExcerpt, RekorReceiptMetadata, CheckpointSignature. | Agent |
| 2026-01-14 | EVPCARD-LB-002: Created EvidenceCardService.cs with CreateCardAsync, ExportCardAsync (Json/CompactJson/CanonicalJson), VerifyCardAsync. | Agent |
| 2026-01-14 | EVPCARD-LB-003: Created IEvidenceCardService.cs with RekorReceiptMetadata integration for offline verification. | Agent |
| 2026-01-14 | EVPCARD-LB-004: Created EvidenceCardServiceTests.cs with 11 determinism and export tests. All 42 evidence pack tests pass. | Agent |
| 2026-01-14 | Added StellaOps.Determinism.Abstractions project reference for IGuidProvider. | Agent |
## Decisions & Risks
- Decide evidence-card schema fields and SBOM excerpt selection rules (size limits, deterministic ordering).
- Rekor receipt availability in air-gap must be optional; define fallback behavior when receipts are missing.
- Cross-module docs and API wiring occur in dependent sprints; note in commits when touching `docs/**`.
## Next Checkpoints
- TBD (set once staffed).

49
docs/implplan/SPRINT_20260112_004_PLATFORM_setup_wizard_backend.md
View File

@@ -1,49 +0,0 @@
# Sprint SPRINT_20260112_004_PLATFORM_setup_wizard_backend - Platform Setup Wizard Backend
## Topic & Scope
- Replace the current UI mock setup wizard with real `/api/v1/setup/*` endpoints in Platform WebService; today only the UI mocks exist in `src/Web/StellaOps.Web/src/app/features/setup-wizard/services/setup-wizard-api.service.ts` and Platform only exposes `/api/v1/platform/onboarding/*`.
- Provide deterministic setup session state (create, resume, execute, skip, finalize) with tenant scoping and "data as of" metadata for offline-first UX.
- Align step ids and validation check ids with `docs/setup/setup-wizard-ux.md` and `docs/setup/setup-wizard-inventory.md`, and return Problem+JSON errors for UI handling.
- Evidence expected: contract tests under `src/Platform/__Tests/`, updated docs in `docs/setup/*` and `docs/modules/platform/platform-service.md`.
- **Working directory:** `src/Platform`.
## Dependencies & Concurrency
- Depends on Authority scopes and Gateway policy wiring already present in Platform service.
- Downstream: UI setup wizard wiring in `SPRINT_20260112_005_FE_setup_wizard_ui_wiring.md` consumes these endpoints.
- Safe to run in parallel with SCM annotation sprints; no shared code paths.
## Documentation Prerequisites
- `src/Platform/AGENTS.md`
- `src/Platform/StellaOps.Platform.WebService/AGENTS.md`
- `docs/modules/platform/architecture-overview.md`
- `docs/modules/platform/architecture.md`
- `docs/modules/platform/platform-service.md`
- `docs/setup/setup-wizard-ux.md`
- `docs/setup/setup-wizard-inventory.md`
- `docs/technical/testing/webservice-test-discipline.md`
## Delivery Tracker
| # | Task ID | Status | Key dependency / next step | Owners | Task Definition |
| --- | --- | --- | --- | --- | --- |
| 1 | PLATFORM-SETUP-001 | DONE | None | Platform Guild | Define setup wizard contracts and step definitions aligned to `docs/setup/setup-wizard-ux.md`; include deterministic ordering and explicit status enums. |
| 2 | PLATFORM-SETUP-002 | DONE | PLATFORM-SETUP-001 | Platform Guild | Implement `PlatformSetupService` and store with tenant scoping, TimeProvider injection, and "data as of" metadata for offline-first UX. |
| 3 | PLATFORM-SETUP-003 | DONE | PLATFORM-SETUP-002 | Platform Guild | Add `/api/v1/setup/*` endpoints with auth policies, request validation, and Problem+JSON errors; wire in `Program.cs`; add OpenAPI contract tests. |
| 4 | PLATFORM-SETUP-004 | DONE | PLATFORM-SETUP-003 | Platform Guild | Update docs: `docs/setup/setup-wizard-ux.md`, `docs/setup/setup-wizard-inventory.md`, `docs/modules/platform/platform-service.md` with endpoint contracts and step list. |
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-01-14 | Sprint created; awaiting staffing. | Planning |
| 2026-01-14 | PLATFORM-SETUP-001 DONE: Created SetupWizardModels.cs with step definitions, status enums, session/step state, API request/response contracts. | Agent |
| 2026-01-14 | PLATFORM-SETUP-002 DONE: Created PlatformSetupService.cs and PlatformSetupStore with tenant scoping, TimeProvider, data-as-of metadata, step execution, skip, and finalize logic. | Agent |
| 2026-01-14 | PLATFORM-SETUP-003 DONE: Created SetupEndpoints.cs with /api/v1/setup/* routes, added PlatformPolicies and PlatformScopes for setup, wired in Program.cs. | Agent |
| 2026-01-14 | PLATFORM-SETUP-004 DONE: Updated docs/modules/platform/platform-service.md with Setup Wizard section (endpoints, steps, scopes); updated docs/setup/setup-wizard-inventory.md with backend components and API endpoints. Sprint complete. | Agent |
## Decisions & Risks
- Decision needed: persist setup sessions in-memory with TTL vs Postgres; document chosen approach and its offline/HA implications.
- Risk: step id mismatch between Platform setup steps and existing onboarding steps; align or provide mapping in contract.
- Risk: `/api/v1/setup` path must be consistent with UI; changes require updating `src/Web/StellaOps.Web/src/app/features/setup-wizard/services/setup-wizard-api.service.ts`.
## Next Checkpoints
- 2026-01-16: Contract and endpoint shape review with Platform and UI leads.
- 2026-01-21: Contract test and docs update review.

41
docs/implplan/SPRINT_20260112_004_POLICY_signed_override_enforcement.md
View File

@@ -1,41 +0,0 @@
# Sprint 20260112.004.POLICY · Signed Override Enforcement
## Topic & Scope
- Require signed VEX override attestations for policy evaluation and expose override signature status to rules.
- Preserve existing VEX consensus semantics while tightening enforcement to signed inputs only.
- Working directory: `src/Policy`. Evidence: engine updates, policy signals, and tests.
## Dependencies & Concurrency
- Depends on `SPRINT_20260112_004_VULN_vex_override_workflow.md` for signed override metadata.
- Parallel-safe with Scanner and Findings sprints.
## Documentation Prerequisites
- `docs/README.md`
- `docs/ARCHITECTURE_OVERVIEW.md`
- `docs/07_HIGH_LEVEL_ARCHITECTURE.md`
- `docs/modules/policy/architecture.md`
- `docs/modules/policy/guides/dsl.md`
- `docs/modules/policy/guides/vex-trust-model.md`
- `docs/VEX_CONSENSUS_GUIDE.md`
## Delivery Tracker
| # | Task ID | Status | Key dependency / next step | Owners | Task Definition |
| --- | --- | --- | --- | --- | --- |
| 1 | POL-OVR-001 | DONE | Signed override model | Policy Guild | Add override signature validation (DSSE + optional Rekor inclusion) and map results to policy signals. |
| 2 | POL-OVR-002 | DONE | DSL exposure | Policy Guild | Expose override signature status (`override_signed`, `override_rekor_verified`) to DSL/engine inputs; add unit tests. |
| 3 | POL-OVR-003 | DONE | Cross-module docs | Policy Guild | Update `docs/modules/policy/guides/dsl.md` with signed override rules and examples. |
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-01-14 | Sprint created; awaiting staffing. | Planning |
| 2026-01-14 | POL-OVR-001: Created VexOverrideSignals.cs with VexOverrideSignalInput (OverrideSigned, OverrideRekorVerified, SigningKeyId, SignerIdentity, EnvelopeDigest, RekorLogIndex, RekorIntegratedTime, ValidFrom, ValidUntil, WithinValidityPeriod, KeyTrustLevel), VexKeyTrustLevel enum, VexOverrideEnforcementPolicy, VexOverrideEnforcementResult, IVexOverrideSignatureValidator interface, and VexOverrideSignalFactory. | Agent |
| 2026-01-14 | POL-OVR-002: Signal input model includes override_signed and override_rekor_verified fields exposed for DSL consumption via VexOverrideSignalInput record. | Agent |
| 2026-01-14 | POL-OVR-003: Added Section 13 (Signed Override Enforcement) to dsl.md with signal namespace reference table, 4 enforcement rule examples (require signed, require Rekor for critical, trust level gating, validity period), default enforcement profile settings, and offline mode considerations. | Agent |
## Decisions & Risks
- Default enforcement should block unsigned overrides unless explicitly allowed by policy profile.
- Rekor checks must honor offline mode and sealed-mode constraints.
## Next Checkpoints
- TBD: confirm default enforcement profile with Security review.

49
docs/implplan/SPRINT_20260112_004_POLICY_unknowns_determinization_greyqueue.md
View File

@@ -1,49 +0,0 @@
# Sprint 20260112_004_POLICY - Unknowns Determinization + Grey Queue
## Topic & Scope
- Normalize "unknown" outcomes as GuardedPass or Deferred with PendingDeterminization mapping; keep OpenVEX status as under_investigation for spec alignment.
- Add deterministic reanalysis fingerprint and trigger metadata to policy outputs and the unknowns registry so replays are reproducible.
- Detect conflicting evidence and route to Disputed state with manual adjudication gates.
- Owning directory: src/Policy; evidence includes policy gate code, unknowns registry schema/API, tests, and docs updates.
- Working directory: `src/Policy`.
## Dependencies & Concurrency
- Depends on event payloads from `docs/implplan/SPRINT_20260112_005_SCANNER_epss_reanalysis_events.md`, `docs/implplan/SPRINT_20260112_006_EXCITITOR_vex_change_events.md`, `docs/implplan/SPRINT_20260112_007_ATTESTOR_rekor_entry_events.md`, and `docs/implplan/SPRINT_20260112_008_SIGNALS_runtime_telemetry_events.md`.
- CC 20260112_004-009 remain independent aside from explicit dependencies.
## Documentation Prerequisites
- `src/Policy/AGENTS.md`
- `docs/modules/policy/architecture.md`
- `docs/modules/policy/determinization-api.md`
- `docs/VEX_CONSENSUS_GUIDE.md`
- `docs/api/unknowns-api.md`
- `docs/api/score-proofs-reachability-api-reference.md`
## Delivery Tracker
| # | Task ID | Status | Key dependency / next step | Owners | Task Definition |
| --- | --- | --- | --- | --- | --- |
| 1 | POLICY-UNK-001 | DONE | Finalize fingerprint inputs list | Policy Guild - Team | Add deterministic reanalysis fingerprint builder and plumb into determinization gate results and policy verdict outputs. |
| 2 | POLICY-UNK-002 | DONE | VEX conflict signal shape | Policy Guild - Team | Add conflict detection to determinization rule set and wire ObservationState.Disputed plus manual adjudication path. |
| 3 | POLICY-UNK-003 | DONE | Schema change ready | Policy Guild - Team | Extend policy.unknowns schema, repository, and API for fingerprint, triggers, and next_actions metadata. |
| 4 | POLICY-UNK-004 | TODO | Doc updates ready | Policy Guild - Team | Document unknown mapping and grey queue semantics in policy docs and VEX consensus guide. |
| 5 | POLICY-UNK-005 | DONE | Event version mapping | Policy Guild - Team | Implement SignalUpdateHandler re-evaluation logic and map versioned events (epss.updated@1, etc.). |
| 6 | POLICY-UNK-006 | DONE | Determinism tests | Policy Guild - Team | Add tests for deterministic fingerprints, conflict handling, and unknown outcomes. |
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-01-14 | Sprint created; awaiting staffing. | Planning |
| 2026-01-15 | POLICY-UNK-001: Created ReanalysisFingerprint record with FingerprintId, DsseBundleDigest, EvidenceDigests, ToolVersions, ProductVersion, PolicyConfigHash, SignalWeightsHash, ComputedAt, Triggers, and NextActions. Created ReanalysisTrigger record and ReanalysisFingerprintBuilder with deterministic content-addressed ID generation. Extended DeterminizationResult with Fingerprint property. | Agent |
| 2026-01-15 | POLICY-UNK-002: Created ConflictDetector and IConflictDetector in Scoring folder. Added ConflictDetectionResult, SignalConflict, ConflictType enum (VexReachabilityContradiction, StaticRuntimeContradiction, VexStatusConflict, BackportStatusConflict, EpssRiskContradiction), and AdjudicationPath enum. Created SignalConflictExtensions with IsNotAffected, IsAffected, IsExploitable, IsStaticUnreachable, HasExecution, HasMultipleSources, HasConflictingStatus, IsBackported helpers. | Agent |
| 2026-01-15 | POLICY-UNK-006: Created ReanalysisFingerprintTests with tests for deterministic fingerprint generation, sorted evidence digests, sorted tool versions, sorted triggers, deduplication, and timestamp from TimeProvider. Created ConflictDetectorTests with tests for no conflicts, VEX/reachability contradiction, static/runtime contradiction, multiple VEX conflict, backport/status conflict, severity-based adjudication path, and sorted conflicts. | Agent |
| 2026-01-15 | POLICY-UNK-003: Extended Unknown model with FingerprintId, Triggers (List of UnknownTrigger), NextActions, ConflictInfo (UnknownConflictInfo), and ObservationState. Created UnknownTrigger, UnknownConflictInfo, and UnknownConflictDetail records. Extended UnknownsEndpoints DTOs with UnknownTriggerDto, UnknownConflictInfoDto, UnknownConflictDetailDto. Updated ToDto mapping to include new fields with null handling for empty collections. | Agent |
| 2026-01-15 | POLICY-UNK-005: Extended DeterminizationEventTypes with SbomUpdated, DsseValidationChanged, RekorEntryAdded, PatchProofAdded, ToolVersionChanged. Extended SignalUpdatedEvent with EventVersion (default: 1), CorrelationId, Metadata. Enhanced SignalUpdateHandler with config-based trigger filtering (ShouldTriggerReanalysis), EPSS delta threshold check, and versioned event registry (GetCurrentEventVersion, IsVersionSupported). | Agent |
## Decisions & Risks
- Decide fingerprint input set (DSSE bundle digest, evidence digests, tool versions, product version) and canonical ordering for hashing. **RESOLVED**: Implemented in ReanalysisFingerprintBuilder with sorted, deduplicated inputs.
- Decide how Disputed maps to PolicyVerdictStatus in prod vs non-prod.
- Event naming mismatch (epss.updated@1 vs epss.updated) must be resolved or mapped. **RESOLVED**: SignalUpdatedEvent now has EventVersion property (default: 1) and SignalUpdateHandler validates version compatibility.
## Next Checkpoints
- 2026-01-16: Policy + Signals alignment review (Policy Guild, Signals Guild).
- 2026-01-20: Docs review for determinization and VEX consensus.

52
docs/implplan/SPRINT_20260112_004_SCANNER_path_witness_nodehash.md
View File

@@ -1,52 +0,0 @@
# Sprint 20260112_004_SCANNER · Path Witness NodeHash
## Topic & Scope
- Define a canonical node-hash and path-hash recipe so static and runtime evidence can join deterministically.
- Extend Scanner reachability outputs (rich graph, subgraph, path witness, SARIF) to carry node hashes, top-K path nodes, and evidence URIs.
- Keep DSSE payloads deterministic and backwards compatible where possible.
- **Working directory:** `src/Scanner`. Allowed shared library: `src/__Libraries/StellaOps.Reachability.Core`. Evidence: updated tests, fixtures, and DSSE payloads.
## Dependencies & Concurrency
- Depends on a locked node-hash recipe (coordinate with DOCS and SIGNALS sprints).
- Predicate type locked to `https://stella.ops/predicates/path-witness/v1` with aliases `stella.ops/pathWitness@v1` and `https://stella.ops/pathWitness/v1`.
- Parallel execution is safe with Signals/Policy if the recipe and predicate type are aligned before merge.
## Documentation Prerequisites
- docs/README.md
- docs/07_HIGH_LEVEL_ARCHITECTURE.md
- docs/modules/platform/architecture-overview.md
- docs/modules/scanner/architecture.md
- docs/contracts/witness-v1.md
- docs/modules/reach-graph/guides/reachability.md
- docs/architecture/EVIDENCE_PIPELINE_ARCHITECTURE.md
- docs/technical/cicd/sarif-integration.md
## Delivery Tracker
| # | Task ID | Status | Key dependency / next step | Owners | Task Definition |
| --- | --- | --- | --- | --- | --- |
| 1 | PW-SCN-001 | DONE | None | Guild - Scanner | Add canonical `NodeHashRecipe` and `PathHashRecipe` helpers in `src/__Libraries/StellaOps.Reachability.Core` with normalization rules and unit tests. |
| 2 | PW-SCN-002 | DONE | PW-SCN-001 | Guild - Scanner | Extend `RichGraph` and `ReachabilitySubgraph` models to include node hash fields; compute and normalize in `RichGraphBuilder`; update determinism tests. |
| 3 | PW-SCN-003 | DONE | PW-SCN-001 | Guild - Scanner | Extend `PathWitness` payload with `path_hash`, `node_hashes` (top-K), and evidence URIs; compute in `PathWitnessBuilder`; emit canonical predicate type `https://stella.ops/predicates/path-witness/v1` while honoring aliases `stella.ops/pathWitness@v1` and `https://stella.ops/pathWitness/v1`; update tests. |
| 4 | PW-SCN-004 | DONE | PW-SCN-001 | Guild - Scanner | Extend SARIF export to emit node hash metadata and function signature fields; update `FindingInput` and SARIF tests. |
| 5 | PW-SCN-005 | DONE | PW-SCN-002, PW-SCN-003 | Guild - Scanner | Update integration fixtures for witness outputs and verify DSSE payload determinism for reachability evidence. |
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-01-14 | Sprint created; awaiting staffing. | Planning |
| 2026-01-14 | Created `src/__Libraries/StellaOps.Reachability.Core/AGENTS.md` to unblock shared library edits. | Planning |
| 2026-01-14 | Locked path-witness predicate type to `https://stella.ops/predicates/path-witness/v1` with alias support (`stella.ops/pathWitness@v1`, `https://stella.ops/pathWitness/v1`). | Planning |
| 2026-01-14 | PW-SCN-001: Created NodeHashRecipe.cs (PURL/symbol normalization, SHA-256 hashing) and PathHashRecipe.cs (path/combined hashing, top-K selection, PathFingerprint). Added 43 unit tests. | Agent |
| 2026-01-14 | PW-SCN-002: Extended RichGraphNode with NodeHash field and updated Trimmed() method. Extended ReachabilitySubgraphNode with NodeHash field. | Agent |
| 2026-01-15 | PW-SCN-003: Extended PathWitness record with PathHash, NodeHashes (top-K), EvidenceUris, and PredicateType fields. Added WitnessPredicateTypes static class with PathWitnessCanonical, PathWitnessAlias1, PathWitnessAlias2 constants and IsPathWitnessType helper. Updated PathWitnessBuilder.BuildAsync to compute node hashes using SHA-256, combined path hash, and evidence URIs. Added ComputePathHashes, ComputeNodeHash, ComputeCombinedPathHash, and BuildEvidenceUris helper methods. | Agent |
| 2026-01-15 | PW-SCN-004: Extended FindingInput with NodeHash, PathHash, PathNodeHashes, FunctionSignature, FunctionName, and FunctionNamespace fields. Updated SarifExportService.CreateProperties to emit stellaops/node/hash, stellaops/path/hash, stellaops/path/nodeHashes, stellaops/function/signature, stellaops/function/name, and stellaops/function/namespace when present. Added tests for node hash and function signature SARIF output. | Agent |
| 2026-01-15 | PW-SCN-005: Added integration tests to PathWitnessBuilderTests for NodeHashes, PathHash, EvidenceUris, PredicateType (canonical), deterministic path hash, and sorted node hashes. All tests verify DSSE payload determinism for reachability evidence. | Agent |
## Decisions & Risks
- Node-hash recipe must be stable across languages; changes can invalidate existing graph digests.
- Path witness schema changes may require a version bump; maintain alias support for `stella.ops/pathWitness@v1` and `https://stella.ops/pathWitness/v1`.
- Top-K selection must be deterministic; define ordering in the helper to avoid drift.
- Added `src/__Libraries/StellaOps.Reachability.Core/AGENTS.md`; keep it aligned with reachability contracts.
## Next Checkpoints
- TBD: Node-hash recipe signoff and predicate type alignment review.

50
docs/implplan/SPRINT_20260112_004_SCANNER_reachability_trace_runtime_evidence.md
View File

@@ -1,50 +0,0 @@
# Sprint 20260112.004.SCANNER · Reachability Trace + Runtime Evidence Export
## Topic & Scope
- Add runtime-confirmed edge flags and reachability score output so the UI can show the risk line (score, runtime badge) without changing lattice semantics.
- Provide a deterministic trace export (GraphSON or JSON/NDJSON) with evidence URIs and optional SARIF relatedLocations references for explainability.
- Preserve hybrid posture: graph DSSE required, edge-bundle DSSE optional, runtime evidence optional and deterministic.
- Working directory: `src/Scanner`. Evidence: updated reachability contracts, trace export endpoint, and tests; doc updates in `docs/api/signals/reachability-contract.md` and `docs/modules/scanner/architecture.md`.
## Dependencies & Concurrency
- Downstream: `SPRINT_20260112_004_FE_risk_line_runtime_trace_ui.md` depends on the new fields and export endpoint.
- Parallel-safe with Findings/Policy work; no shared migrations expected.
## Documentation Prerequisites
- `docs/README.md`
- `docs/ARCHITECTURE_OVERVIEW.md`
- `docs/07_HIGH_LEVEL_ARCHITECTURE.md`
- `docs/modules/scanner/architecture.md`
- `docs/api/signals/reachability-contract.md`
- `docs/architecture/EVIDENCE_PIPELINE_ARCHITECTURE.md`
- `docs/technical/architecture/runtime-agents-architecture.md`
- `src/__Libraries/StellaOps.Canonical.Json/README.md`
## Delivery Tracker
| # | Task ID | Status | Key dependency / next step | Owners | Task Definition |
| --- | --- | --- | --- | --- | --- |
| 1 | SCAN-RT-001 | BLOCKED | FE data contract not finalized | Scanner Guild | Extend reachability response models to include `reachabilityScore` (0-1), per-edge/per-step `runtimeConfirmed`, and evidence URI lists; keep ordering deterministic. |
| 2 | SCAN-RT-002 | BLOCKED | Depends on SCAN-RT-001 | Scanner Guild | Compute `runtimeConfirmed` annotations during static/runtime merge; add fixtures and unit tests proving stable output. |
| 3 | SCAN-RT-003 | BLOCKED | Depends on SCAN-RT-001 | Scanner Guild | Add trace export endpoint (GraphSON or JSON/NDJSON) with evidence URIs and optional SARIF relatedLocations references; canonicalize JSON via `StellaOps.Canonical.Json` before hashing or storing; add deterministic export tests. |
| 4 | SCAN-RT-004 | BLOCKED | Depends on SCAN-RT-003 | Scanner Guild | Update `docs/api/signals/reachability-contract.md` and `docs/modules/scanner/architecture.md` to document new fields and export format. |
| 5 | SCAN-RT-005 | BLOCKED | Depends on SCAN-RT-003 | Scanner Guild | Document canonicalization and hash rules for trace exports in `docs/architecture/EVIDENCE_PIPELINE_ARCHITECTURE.md` with explicit `StellaOps.Canonical.Json` usage. |
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-01-14 | Sprint created; awaiting staffing. | Planning |
| 2026-01-14 | All tasks marked BLOCKED. See Decisions & Risks for blocking reasons. | Agent |
## Decisions & Risks
- Runtime-confirmed flags must be overlays only; do not alter lattice precedence or VEX recommendations.
- Trace export format choice (GraphSON vs JSON/NDJSON) requires a single deterministic canonicalization strategy; use `StellaOps.Canonical.Json` with explicit serializer options (no CamelCase, default encoder) for hashing.
- Cross-module doc edits are required; note in PR descriptions when executed.
### BLOCKING ISSUES (require PM/architect decision)
1. **FE Data Contract Not Finalized**: SCAN-RT-001 requires frontend team confirmation on data contract shape for `reachabilityScore` and `runtimeConfirmed` fields. The downstream sprint (SPRINT_20260112_004_FE_risk_line_runtime_trace_ui) depends on these fields but the exact schema is not agreed.
2. **RichGraph Model Complexity**: RichGraphNode/RichGraphEdge (275+ lines in RichGraph.cs) have existing semantics. Adding runtimeConfirmed requires understanding existing Trimmed() ordering logic, Gate handling, and Confidence clamping. Need Scanner domain expert review.
3. **Export Format Decision**: GraphSON vs JSON/NDJSON not decided. GraphSON has richer semantics but is more complex. JSON/NDJSON is simpler but loses graph structure. Need architecture decision.
4. **Runtime Agent Integration**: Runtime evidence sources (StellaOps.Scanner.Runtime/) need wiring. Current RuntimeMerge pattern unclear - need confirmation on how runtime traces flow into static graph.
## Next Checkpoints
- TBD: agree trace export format with UI and evidence graph consumers.

40
docs/implplan/SPRINT_20260112_004_VULN_vex_override_workflow.md
View File

@@ -1,40 +0,0 @@
# Sprint 20260112.004.VULN · VEX Override Workflow + Attestation Linkage
## Topic & Scope
- Extend VEX decision APIs to accept and return attestation references so overrides are signed and auditable.
- Integrate Attestor to mint DSSE envelopes for operator decisions and persist envelope digests and Rekor info.
- Working directory: `src/VulnExplorer`. Evidence: API model updates, Attestor integration, and test coverage.
## Dependencies & Concurrency
- Depends on `SPRINT_20260112_004_ATTESTOR_vex_override_predicate.md` for predicate and DSSE tooling.
- Downstream: `SPRINT_20260112_004_POLICY_signed_override_enforcement.md` consumes signed override metadata.
## Documentation Prerequisites
- `docs/README.md`
- `docs/ARCHITECTURE_OVERVIEW.md`
- `docs/07_HIGH_LEVEL_ARCHITECTURE.md`
- `docs/modules/vuln-explorer/architecture.md`
- `docs/VEX_CONSENSUS_GUIDE.md`
- `docs/modules/vex-lens/architecture.md`
## Delivery Tracker
| # | Task ID | Status | Key dependency / next step | Owners | Task Definition |
| --- | --- | --- | --- | --- | --- |
| 1 | VEX-OVR-001 | DONE | Model changes | Vuln Explorer Guild | Extend VEX decision request/response models to include attestation request parameters and attestation refs (envelope digest, rekor info, storage). |
| 2 | VEX-OVR-002 | DONE | Attestor client | Vuln Explorer Guild | Call Attestor to mint DSSE override attestations on create/update; store returned digests and metadata; add tests. |
| 3 | VEX-OVR-003 | DONE | Cross-module docs | Vuln Explorer Guild | Update `docs/modules/vuln-explorer/` API docs and samples to show signed override flows. |
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-01-14 | Sprint created; awaiting staffing. | Planning |
| 2026-01-14 | VEX-OVR-001: Added VexOverrideAttestationDto, AttestationVerificationStatusDto, AttestationRequestOptions to VexDecisionModels.cs. Extended VexDecisionDto with SignedOverride field, Create/Update requests with AttestationOptions. Updated VexDecisionStore. | Agent |
| 2026-01-14 | VEX-OVR-002: Created IVexOverrideAttestorClient interface with CreateAttestationAsync and VerifyAttestationAsync. Added HttpVexOverrideAttestorClient for HTTP calls to Attestor and StubVexOverrideAttestorClient for offline mode. Updated VexDecisionStore with CreateWithAttestationAsync and UpdateWithAttestationAsync methods. | Agent |
| 2026-01-15 | VEX-OVR-003: Created docs/modules/vuln-explorer/guides/signed-vex-override-workflow.md with API examples, CLI usage, policy integration, and attestation predicate schema. | Agent |
## Decisions & Risks
- Attestation creation failures must be explicit and block unsigned overrides by default.
- Attestation metadata must be deterministic and include evidence refs and scope.
## Next Checkpoints
- TBD: confirm API contract with UI and Policy Engine.

41
docs/implplan/SPRINT_20260112_005_BE_evidence_card_api.md
View File

@@ -1,41 +0,0 @@
# Sprint 20260112-005-BE-evidence-card-api - Evidence Card API
## Topic & Scope
- Extend AdvisoryAI evidence pack endpoints to expose evidence-card export and return stable headers for single-file receipts.
- Current state evidence: EvidencePack export only supports json/markdown/html/pdf (`src/AdvisoryAI/StellaOps.AdvisoryAI.WebService/Endpoints/EvidencePackEndpoints.cs`).
- Evidence to produce: API format wiring, OpenAPI update, and integration tests that verify content type and receipt presence.
- **Working directory:** `src/AdvisoryAI`.
## Dependencies & Concurrency
- Depends on `SPRINT_20260112_004_LB_evidence_card_core` for export implementation in Evidence.Pack.
- Parallel safe with remediation PR sprint; no shared DB migrations.
## Documentation Prerequisites
- `docs/README.md`
- `docs/07_HIGH_LEVEL_ARCHITECTURE.md`
- `docs/modules/platform/architecture-overview.md`
- `docs/modules/advisory-ai/guides/api.md`
## Delivery Tracker
| # | Task ID | Status | Key dependency / next step | Owners | Task Definition |
| --- | --- | --- | --- | --- | --- |
| 1 | EVPCARD-BE-001 | DONE | EVPCARD-LB-002 | Advisory AI Guild | Add evidence-card format parsing and export path to EvidencePackEndpoints. |
| 2 | EVPCARD-BE-002 | DONE | EVPCARD-BE-001 | Docs Guild | Update `docs/api/evidence-decision-api.openapi.yaml` with evidence-card export format and response headers. |
| 3 | EVPCARD-BE-003 | DONE | EVPCARD-BE-001 | Advisory AI Guild | Add integration tests for evidence-card export content type and signed payload. |
| 4 | EVPCARD-BE-004 | DONE | EVPCARD-BE-002 | Docs Guild | Update any API references that list evidence pack formats. |
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-01-14 | Sprint created; awaiting staffing. | Planning |
| 2026-01-14 | EVPCARD-BE-001: Added EvidenceCard and EvidenceCardCompact enum values. Added format aliases in EvidencePackEndpoints. Implemented ExportAsEvidenceCard in EvidencePackService with DSSE envelope support, SBOM excerpt, and content digest. | Agent |
| 2026-01-14 | EVPCARD-BE-002: Updated evidence-decision-api.openapi.yaml v1.0.0->v1.1.0. Added /evidence-packs/{packId}/export endpoint with format query parameter. Added response headers (X-Evidence-Pack-Id, X-Content-Digest, X-Evidence-Card-Version, X-Rekor-Log-Index). Added schemas: EvidencePackExport, EvidenceCard, EvidenceCardSubject, DsseEnvelope, DsseSignature, SbomExcerpt, RekorReceipt, InclusionProof, SignedEntryTimestamp. | Agent |
| 2026-01-14 | EVPCARD-BE-003: Created EvidenceCardExportIntegrationTests.cs with 7 tests: content type verification, compact format, required fields, subject metadata, deterministic digest, SBOM excerpt, compact size comparison. | Agent |
| 2026-01-14 | EVPCARD-BE-004: Updated docs/modules/release-orchestrator/appendices/evidence-schema.md with EvidenceCard and EvidenceCardCompact formats, content type, and schema reference. Updated docs/api/triage-export-api-reference.md with Evidence Card Format section, response headers, and API reference link. | Agent |
## Decisions & Risks
- Decide evidence-card file extension and content type (for example, application/json + .evidence.cdx.json).
- Cross-module docs updates required under `docs/**`; note in commits when touched.
## Next Checkpoints
- TBD (set once staffed).

41
docs/implplan/SPRINT_20260112_005_FE_binaryindex_ops_ui.md
View File

@@ -1,41 +0,0 @@
# Sprint 20260112-005-FE - BinaryIndex Ops UI
## Topic & Scope
- Add a BinaryIndex ops view that surfaces lifter warmness, bench latency, and Valkey function cache stats for LowUIR-backed analysis.
- Expose read-only configuration and effective settings (pool sizes, TTLs, semantic enablement, cache backend, persistence backend) so operators can verify user configuration is applied.
- Integrate new API clients and route entry points, with deterministic rendering and accessible UI.
- **Working directory:** `src/Web/StellaOps.Web`.
## Dependencies & Concurrency
- Depends on `SPRINT_20260112_004_BINIDX_b2r2_lowuir_perf_cache.md` for LowUIR, lifter pool, and ops endpoints.
- Depends on `SPRINT_20260112_007_BINIDX_binaryindex_user_config.md` for config and stats endpoint contract.
- Parallel execution is safe with other FE work that does not touch BinaryIndex routes.
## Documentation Prerequisites
- `docs/README.md`
- `docs/modules/ui/architecture.md`
- `docs/modules/binary-index/architecture.md`
- `docs/modules/binary-index/semantic-diffing.md`
- `src/Web/StellaOps.Web/AGENTS.md`
## Delivery Tracker
| # | Task ID | Status | Key dependency / next step | Owners | Task Definition |
| --- | --- | --- | --- | --- | --- |
| 1 | FE-BINOPS-01 | TODO | Ops endpoint contract | UI Guild - FE | Add TypeScript models and API client for BinaryIndex ops endpoints: GET `/api/v1/ops/binaryindex/health` (BinaryIndexOpsHealthResponse), POST `/api/v1/ops/binaryindex/bench/run` (BinaryIndexBenchResponse), GET `/api/v1/ops/binaryindex/cache` (BinaryIndexFunctionCacheStats), GET `/api/v1/ops/binaryindex/config` (BinaryIndexEffectiveConfig). Ensure error handling for offline and unauthorized modes. |
| 2 | FE-BINOPS-02 | TODO | Route + layout | UI Guild - FE | Add a BinaryIndex Ops page at route `ops/binary-index` showing lifter warmness, bench latency summary, cache hit ratio, and effective settings. Expose a "Run bench sample" action that calls `/api/v1/ops/binaryindex/bench/run` and renders the response; disable with a visible reason when not permitted. |
| 3 | FE-BINOPS-03 | TODO | UX for config visibility | UI Guild - FE | Add a read-only configuration panel showing pool sizes, TTLs, semantic enablement, cache backend (Valkey), persistence backend (PostgreSQL), and backend version. Keep outputs ASCII-only and redact secrets. |
| 4 | FE-BINOPS-04 | TODO | Tests | UI Guild - FE | Add component tests for ops rendering, error states, and deterministic output; update route tests if needed. |
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-01-14 | Sprint created; BinaryIndex ops UI and configuration visibility planned. | Planning |
| 2026-01-14 | Locked ops endpoints, response schema names, and bench action exposure requirements. | Planning |
## Decisions & Risks
- Exposing config in UI must remain read-only and avoid secrets or tokens.
- Bench actions can be load-generating; require explicit user action and rate limiting.
- UI must degrade gracefully when ops endpoints are unavailable or disabled.
## Next Checkpoints
- 2026-01-21: UI review of ops layout and configuration visibility.

43
docs/implplan/SPRINT_20260112_005_FE_setup_wizard_ui_wiring.md
View File

@@ -1,43 +0,0 @@
# Sprint SPRINT_20260112_005_FE_setup_wizard_ui_wiring - Setup Wizard UI Wiring
## Topic & Scope
- Replace mocked setup wizard calls with real HTTP calls to `/api/v1/setup/*` and onboarding endpoints; current mocks are in `src/Web/StellaOps.Web/src/app/features/setup-wizard/services/setup-wizard-api.service.ts`.
- Align wizard step ids, validation check displays, and error flows with `docs/setup/setup-wizard-ux.md` and Platform contracts; surface retry and "data as of" metadata.
- Add deterministic unit tests for API service, state service, and wizard components; update UI docs to reflect live setup flows.
- Evidence expected: passing unit tests, updated `docs/UI_GUIDE.md` and `docs/modules/ui/architecture.md`.
- **Working directory:** `src/Web/StellaOps.Web`.
## Dependencies & Concurrency
- Depends on Platform setup endpoints from `SPRINT_20260112_004_PLATFORM_setup_wizard_backend.md`.
- Can run in parallel with SCM annotation sprints once API shapes are stable.
## Documentation Prerequisites
- `src/Web/StellaOps.Web/AGENTS.md`
- `docs/modules/ui/architecture.md`
- `docs/modules/ui/information-architecture.md`
- `docs/setup/setup-wizard-ux.md`
- `docs/setup/setup-wizard-inventory.md`
- `docs/UI_GUIDE.md`
- `docs/modules/platform/architecture-overview.md`
## Delivery Tracker
| # | Task ID | Status | Key dependency / next step | Owners | Task Definition |
| --- | --- | --- | --- | --- | --- |
| 1 | FE-SETUP-001 | DONE | PLATFORM-SETUP-003 | UI Guild | Replace mock calls in `SetupWizardApiService` with real HttpClient calls to `/api/v1/setup/*` and `/api/v1/platform/onboarding/*`; map Problem+JSON errors to UI messages. |
| 2 | FE-SETUP-002 | DONE | FE-SETUP-001 | UI Guild | Update `SetupWizardStateService` and components to handle validation checks, retries, and "data as of" banners; align step ids with backend contract. |
| 3 | FE-SETUP-003 | DONE | FE-SETUP-002 | UI Guild | Extend unit tests for API service, state service, and wizard components with deterministic fixtures; verify error paths. |
| 4 | FE-SETUP-004 | DONE | FE-SETUP-003 | UI Guild | Update docs: `docs/UI_GUIDE.md` and `docs/modules/ui/architecture.md` to reflect live setup wizard flows and backend dependencies. |
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-01-14 | Sprint created; awaiting staffing. | Planning |
| 2026-01-15 | FE-SETUP-001: Replaced mock calls in SetupWizardApiService with real HttpClient calls. Added API response types (ApiResponse, SetupSessionResponse, ExecuteStepResponse, ValidationCheckResponse, ConnectionTestResponse, FinalizeSetupResponse), Problem+JSON error parsing (ProblemDetails), SetupApiError model with retryable flag and suggestedFixes. Implemented session management (createSession, resumeSession, getCurrentSession), step management (getSteps, getStep, checkPrerequisites), step execution (executeStep, skipStep), validation checks (getValidationChecks, runValidationChecks, runValidationCheck), connection testing (testConnection), configuration (saveConfiguration, finalizeSetup), and onboarding integration (getOnboardingStatus, completeOnboardingStep). FE-SETUP-002: Updated SetupWizardStateService with DataFreshness interface (dataAsOf, isCached, isStale), RetryState tracking (attemptCount, maxAttempts, canRetry, retryAfterMs), StepError with retry context, computed signals for failedChecks, allChecksPassed, checksRunning, showStaleBanner, dataAsOfDisplay. Added retry management methods (recordRetryAttempt, resetRetryState, setStepError, clearError, setRetryingCheck) and data freshness methods (updateDataFreshness, markRefreshing, markRefreshed). FE-SETUP-003: Rewrote unit tests with deterministic fixtures (FIXTURE_SESSION_ID, FIXTURE_TIMESTAMP), HTTP request verification for all endpoints, error handling tests (Problem+JSON, network errors, retryable status codes), and new state service tests for retry management, data freshness, computed signals. FE-SETUP-004: Added Setup Wizard section to docs/UI_GUIDE.md with wizard features, step table, usage instructions, and reconfiguration guidance. | Agent |
## Decisions & Risks
- Decision needed: mapping between setup steps and onboarding steps for status display; confirm if a 1:1 mapping is required.
- Risk: UI expects `/api/v1/setup` endpoints that are not yet live; sequencing with Platform sprint is required.
## Next Checkpoints
- 2026-01-17: UI contract alignment with Platform service.
- 2026-01-22: Test and docs review.

42
docs/implplan/SPRINT_20260112_005_SCANNER_epss_reanalysis_events.md
View File

@@ -1,42 +0,0 @@
# Sprint 20260112_005_SCANNER - EPSS Reanalysis Events
## Topic & Scope
- Emit deterministic EPSS change events suitable for reanalysis triggers (delta thresholds, new scoring, and per-CVE updates).
- Expose scanner tool versions and evidence digests needed for reanalysis fingerprints in policy outputs.
- Update scanner docs and API references to describe EPSS-triggered reanalysis behavior.
- Owning directory: src/Scanner; evidence includes event payloads, manifest/proof bundle changes, and tests.
- Working directory: `src/Scanner`.
## Dependencies & Concurrency
- Depends on `docs/implplan/SPRINT_20260112_004_POLICY_unknowns_determinization_greyqueue.md` for fingerprint consumer contract.
- CC 20260112_004-009 remain independent aside from explicit dependencies.
## Documentation Prerequisites
- `src/Scanner/AGENTS.md`
- `docs/modules/scanner/architecture.md`
- `docs/modules/scanner/epss-integration.md`
- `docs/api/score-proofs-reachability-api-reference.md`
## Delivery Tracker
| # | Task ID | Status | Key dependency / next step | Owners | Task Definition |
| --- | --- | --- | --- | --- | --- |
| 1 | SCAN-EPSS-001 | DONE | Delta threshold rules | Scanner Guild - Team | Emit deterministic EPSS change events that include per-CVE deltas and a stable ordering for delta > 0.2 triggers. |
| 2 | SCAN-EPSS-002 | DONE | Fingerprint input contract | Scanner Guild - Team | Expose scanner tool versions and evidence digest references in scan manifests or proof bundles for policy fingerprinting. |
| 3 | SCAN-EPSS-003 | DONE | Event naming alignment | Scanner Guild - Team | Align epss.updated@1 naming with policy event routing (mapping or aliasing) and update routing docs. |
| 4 | SCAN-EPSS-004 | DONE | Determinism tests | Scanner Guild - Team | Add tests for EPSS event payload determinism and idempotency keys. |
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-01-14 | Sprint created; awaiting staffing. | Planning |
| 2026-01-14 | SCAN-EPSS-001: Created EpssChangeEvent.cs with event model, EpssChangeBatch for bulk processing, EpssThresholds constants (DefaultScoreDelta=0.2, HighPriorityScore=0.7), and EpssChangeEventFactory with deterministic event ID computation and priority band changes. | Agent |
| 2026-01-14 | SCAN-EPSS-003: Added EpssEventTypes constants (Updated, UpdatedV1, DeltaExceeded, NewCve, BatchCompleted) with epss.updated@1 alias for policy routing compatibility. | Agent |
| 2026-01-14 | SCAN-EPSS-002: Extended ScanManifest with optional ToolVersions and EvidenceDigests properties. Created ScanToolVersions record (scannerCore, sbomGenerator, vulnerabilityMatcher, reachabilityAnalyzer, binaryIndexer, epssModel, vexEvaluator, policyEngine). Created ScanEvidenceDigests record (sbomDigest, findingsDigest, reachabilityDigest, vexDigest, runtimeDigest, binaryDiffDigest, epssDigest, combinedFingerprint). Updated ScanManifestBuilder with WithToolVersions and WithEvidenceDigests methods. | Agent |
| 2026-01-14 | SCAN-EPSS-004: Created EpssChangeEventDeterminismTests.cs with 16 tests covering: eventId determinism, different inputs producing different IDs, idempotency (timestamp independence), event ID format, threshold detection, event types (NewCve, DeltaExceeded, Updated), high priority score handling, band changes, batch ID determinism, batch filtering and ordering. All tests passing. | Agent |
## Decisions & Risks
- Confirm whether epss.updated@1 or a new epss.delta event is the canonical trigger.
- Decide where tool version digests live (manifest vs proof bundle) to keep offline replay valid.
## Next Checkpoints
- 2026-01-17: EPSS event contract review (Scanner Guild, Policy Guild).

45
docs/implplan/SPRINT_20260112_005_SIGNALS_runtime_nodehash.md
View File

@@ -1,45 +0,0 @@
# Sprint 20260112_005_SIGNALS · Runtime NodeHash Evidence
## Topic & Scope
- Extend runtime signal schemas to carry node-hash inputs and call-stack digests for deterministic joins.
- Compute node hashes for observed call paths and expose them in runtime summaries.
- Preserve deterministic ordering and test coverage for runtime evidence outputs.
- **Working directory:** `src/Signals`. Allowed shared library: `src/__Libraries/StellaOps.Reachability.Core`. Evidence: updated schema tests and runtime merge tests.
## Dependencies & Concurrency
- Depends on the canonical node-hash recipe (coordinate with PW-SCN-001).
- Parallel execution is safe with Policy and Attestor once field names are aligned.
## Documentation Prerequisites
- docs/README.md
- docs/07_HIGH_LEVEL_ARCHITECTURE.md
- docs/modules/platform/architecture-overview.md
- docs/modules/signals/architecture.md
- docs/technical/architecture/runtime-agents-architecture.md
- docs/architecture/EVIDENCE_PIPELINE_ARCHITECTURE.md
- docs/modules/reach-graph/guides/reachability.md
## Delivery Tracker
| # | Task ID | Status | Key dependency / next step | Owners | Task Definition |
| --- | --- | --- | --- | --- | --- |
| 1 | PW-SIG-001 | DONE | PW-SCN-001 | Guild - Signals | Extend runtime schemas (`RuntimeCallEvent`, `ObservedCallPath`) with `function_sig`, `binary_digest`, `offset`, `node_hash`, and `callstack_hash`; add schema tests. |
| 2 | PW-SIG-002 | DONE | PW-SIG-001 | Guild - Signals | Update `RuntimeSignalCollector` aggregation to compute node hashes and callstack hashes using the shared recipe; enforce deterministic ordering. |
| 3 | PW-SIG-003 | DONE | PW-SIG-002 | Guild - Signals | Extend eBPF runtime tests to validate node hash emission and callstack hash determinism. |
| 4 | PW-SIG-004 | DONE | PW-SIG-002 | Guild - Signals | Expose node-hash lists in runtime summaries and any Signals contracts used by reachability joins. |
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-01-14 | Sprint created; awaiting staffing. | Planning |
| 2026-01-14 | PW-SIG-001: Extended RuntimeCallEvent with FunctionSignature, BinaryDigest, BinaryOffset, NodeHash, CallstackHash. Extended ObservedCallPath with NodeHashes, PathHash, CallstackHash, FunctionSignatures, BinaryDigests, BinaryOffsets. Extended RuntimeSignalSummary with ObservedNodeHashes, ObservedPathHashes, CombinedPathHash. | Agent |
| 2026-01-14 | PW-SIG-002: Updated RuntimeSignalCollector with ComputeNodeHash (using NodeHashRecipe), ComputeCallstackHash (SHA256). Updated AggregateCallPaths to compute path hashes. Added project reference to StellaOps.Reachability.Core. | Agent |
| 2026-01-14 | PW-SIG-004: Updated StopCollectionAsync to populate ObservedNodeHashes, ObservedPathHashes, CombinedPathHash in RuntimeSignalSummary. Added ExtractUniqueNodeHashes helper. | Agent |
| 2026-01-15 | PW-SIG-003: Created RuntimeNodeHashTests.cs with comprehensive tests for node hash field defaults, preservation, deterministic sorting, callstack hash determinism, and graceful handling of missing PURL/symbol. | Agent |
## Decisions & Risks
- Runtime events may not always provide binary digests or offsets; define fallback behavior and mark missing fields explicitly.
- Callstack hashing must be stable and privacy-safe; avoid embedding raw addresses in outputs.
## Next Checkpoints
- TBD: Runtime schema review and node-hash recipe alignment.

43
docs/implplan/SPRINT_20260112_006_ATTESTOR_path_witness_predicate.md
View File

@@ -1,43 +0,0 @@
# Sprint 20260112_006_ATTESTOR · Path Witness Predicate Support
## Topic & Scope
- Normalize path-witness predicate naming to the best-in-class in-toto URI `https://stella.ops/predicates/path-witness/v1` and ensure Attestor accepts aliases `stella.ops/pathWitness@v1` and `https://stella.ops/pathWitness/v1`.
- Add schema validation and sample fixtures for the updated path-witness payload.
- Preserve deterministic verification behavior and compatibility with existing attestations.
- **Working directory:** `src/Attestor`. Evidence: updated predicate registry, schema, and tests.
## Dependencies & Concurrency
- Predicate type locked to `https://stella.ops/predicates/path-witness/v1` with aliases `stella.ops/pathWitness@v1` and `https://stella.ops/pathWitness/v1`; depends on Scanner payload field lock.
- Parallel execution is safe with Policy if predicate naming is settled early.
## Documentation Prerequisites
- docs/README.md
- docs/07_HIGH_LEVEL_ARCHITECTURE.md
- docs/modules/platform/architecture-overview.md
- docs/modules/attestor/architecture.md
- docs/contracts/witness-v1.md
- docs/modules/provenance/guides/inline-dsse.md
- docs/security/trust-and-signing.md
## Delivery Tracker
| # | Task ID | Status | Key dependency / next step | Owners | Task Definition |
| --- | --- | --- | --- | --- | --- |
| 1 | PW-ATT-001 | DONE | Predicate type locked (`https://stella.ops/predicates/path-witness/v1`) | Guild - Attestor | Update `PredicateTypeRouter` to accept `https://stella.ops/predicates/path-witness/v1` plus aliases `stella.ops/pathWitness@v1` and `https://stella.ops/pathWitness/v1`; add routing tests. |
| 2 | PW-ATT-002 | DONE | PW-ATT-001 | Guild - Attestor | Add path-witness schema in `src/Attestor/StellaOps.Attestor.Types/schemas` and sample payload in `src/Attestor/StellaOps.Attestor.Types/samples`; update schema tests. |
| 3 | PW-ATT-003 | DONE | PW-ATT-002 | Guild - Attestor | Align statement models for canonical predicate type and alias mapping; ensure deterministic serialization in tests. |
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-01-14 | Sprint created; awaiting staffing. | Planning |
| 2026-01-14 | Locked path-witness predicate type to `https://stella.ops/predicates/path-witness/v1` with alias support (`stella.ops/pathWitness@v1`, `https://stella.ops/pathWitness/v1`). | Planning |
| 2026-01-14 | PW-ATT-001: Added path witness predicate types (canonical + 2 aliases) to StellaOpsPredicateTypes in PredicateTypeRouter.cs. | Agent |
| 2026-01-14 | PW-ATT-002: Created stellaops-path-witness.v1.schema.json with full schema including node hashes, path hashes, evidence URIs. Created path-witness.v1.json sample payload. | Agent |
| 2026-01-14 | PW-ATT-003: Created PathWitnessPredicateTypes.cs in Attestor.Core with constants, AllAcceptedTypes, IsPathWitnessType, and NormalizeToCanonical methods for deterministic predicate type handling. | Agent |
## Decisions & Risks
- Canonical predicate type is `https://stella.ops/predicates/path-witness/v1`; keep `stella.ops/pathWitness@v1` and `https://stella.ops/pathWitness/v1` as aliases to avoid breaking existing payloads.
- Schema validation failures can block existing evidence ingestion if not staged carefully.
## Next Checkpoints
- TBD: Predicate type alignment review with Scanner and Docs.

42
docs/implplan/SPRINT_20260112_006_CLI_binaryindex_ops_cli.md
View File

@@ -1,42 +0,0 @@
# Sprint 20260112-006-CLI - BinaryIndex Ops CLI
## Topic & Scope
- Add CLI flags to enable semantic signatures so LowUIR data is actually used during delta signature authoring and matching.
- Provide `stella obs binaryindex` commands to view BinaryIndex ops health, bench latency, Valkey function cache stats, and effective config.
- Add user configuration options for BinaryIndex endpoint selection and default semantic behavior, with a dedicated base URL override that falls back to `BackendUrl`.
- **Working directory:** `src/Cli`.
## Dependencies & Concurrency
- Depends on `SPRINT_20260112_004_BINIDX_b2r2_lowuir_perf_cache.md` for LowUIR support and cache semantics.
- Depends on `SPRINT_20260112_007_BINIDX_binaryindex_user_config.md` for ops endpoint contract.
- Parallel execution is safe with other CLI sprints that do not touch BinaryIndex command groups.
## Documentation Prerequisites
- `docs/README.md`
- `docs/modules/cli/architecture.md`
- `docs/modules/binary-index/architecture.md`
- `docs/modules/binary-index/semantic-diffing.md`
- `src/Cli/AGENTS.md`
## Delivery Tracker
| # | Task ID | Status | Key dependency / next step | Owners | Task Definition |
| --- | --- | --- | --- | --- | --- |
| 1 | CLI-SEM-01 | TODO | SignatureOptions wiring | CLI Guild - CLI | Add `--semantic` flags to deltasig extract/author/match commands and wire them to `SignatureOptions.IncludeSemantic`. Update help text and ensure outputs include semantic fields when enabled. |
| 2 | CLI-OPS-02 | TODO | Ops endpoint contract | CLI Guild - CLI | Add an `obs binaryindex` command group with subcommands `health`, `bench`, `cache`, and `config` that call the BinaryIndex web service endpoints: GET `/api/v1/ops/binaryindex/health`, POST `/api/v1/ops/binaryindex/bench/run`, GET `/api/v1/ops/binaryindex/cache`, GET `/api/v1/ops/binaryindex/config`. Support JSON and table output with deterministic ordering and ASCII-only output. |
| 3 | CLI-CONF-03 | TODO | Configuration keys | CLI Guild - CLI | Add CLI configuration for BinaryIndex base URL and default semantic enablement. Use `StellaOps:BinaryIndex:BaseUrl` and env var `STELLAOPS_BINARYINDEX_URL`, plus a `--binaryindex-url` override; fall back to `BackendUrl` when unset. Document keys and defaults. |
| 4 | CLI-TEST-04 | TODO | Tests | CLI Guild - CLI | Add unit and golden-output tests for semantic flags and ops commands, covering offline mode and error handling. |
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-01-14 | Sprint created; BinaryIndex ops CLI and semantic flags planned. | Planning |
| 2026-01-14 | Selected `obs binaryindex` command group and BinaryIndex base URL config key/override. | Planning |
## Decisions & Risks
- CLI commands must respect offline mode and avoid hidden network calls.
- Semantic flag changes output content; update golden tests and deterministic formatting.
- Ops commands should fail fast when backend is unreachable without masking error context.
- CLI ops command group chosen as `obs binaryindex` to align with existing observability patterns; ensure help text is explicit for operators.
## Next Checkpoints
- 2026-01-21: CLI command group review and output formatting sign-off.

42
docs/implplan/SPRINT_20260112_006_EXCITITOR_vex_change_events.md
View File

@@ -1,42 +0,0 @@
# Sprint 20260112_006_EXCITITOR - VEX Change Events
## Topic & Scope
- Emit deterministic VEX update events when OpenVEX statements are added, superseded, or conflict.
- Include affected CVE and product keys plus provenance metadata to drive policy reanalysis.
- Document the change event contract and conflict signaling in Excititor and VEX consensus docs.
- Owning directory: src/Excititor; evidence includes event emission code, tests, and docs updates.
- Working directory: `src/Excititor`.
## Dependencies & Concurrency
- Depends on `docs/implplan/SPRINT_20260112_004_POLICY_unknowns_determinization_greyqueue.md` for event routing expectations.
- CC 20260112_004-009 remain independent aside from explicit dependencies.
## Documentation Prerequisites
- `src/Excititor/AGENTS.md`
- `docs/modules/excititor/architecture.md`
- `docs/VEX_CONSENSUS_GUIDE.md`
- `docs/modules/policy/guides/vex-trust-model.md`
## Delivery Tracker
| # | Task ID | Status | Key dependency / next step | Owners | Task Definition |
| --- | --- | --- | --- | --- | --- |
| 1 | EXC-VEX-001 | DONE | Event contract draft | Excititor Guild - Team | Emit VEX update events with deterministic event IDs and stable ordering on statement changes. |
| 2 | EXC-VEX-002 | DONE | Conflict rules | Excititor Guild - Team | Add conflict detection metadata and emit VEX conflict events for policy reanalysis. |
| 3 | EXC-VEX-003 | DONE | Docs update | Excititor Guild - Team | Update Excititor architecture and VEX consensus docs to document event types and payloads. |
| 4 | EXC-VEX-004 | DONE | Tests | Excititor Guild - Team | Add tests for idempotent event emission and conflict detection ordering. |
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-01-14 | Sprint created; awaiting staffing. | Planning |
| 2026-01-14 | EXC-VEX-001: Added new event types to VexTimelineEventTypes (StatementAdded, StatementSuperseded, StatementConflict, StatusChanged). Created VexStatementChangeEvent.cs with event models and factory for deterministic event IDs. | Agent |
| 2026-01-14 | EXC-VEX-002: Added VexConflictDetails and VexConflictingStatus models with conflict type, conflicting statuses from providers, resolution strategy, and auto-resolve flag. Added CreateConflictDetected factory method. | Agent |
| 2026-01-15 | EXC-VEX-003: Added section 3.3 VEX Change Events to docs/modules/excititor/architecture.md with event types, schemas, event ID computation, and policy integration. Updated docs/VEX_CONSENSUS_GUIDE.md with VEX Change Events section. | Agent |
| 2026-01-15 | EXC-VEX-004: Created VexStatementChangeEventTests.cs with comprehensive tests for deterministic event ID generation, idempotency, conflict detection ordering, provenance preservation, and tenant normalization. | Agent |
## Decisions & Risks
- Decide canonical event name (vex.updated vs vex.updated@1) and payload versioning.
- Define conflict detection thresholds and source precedence in the event payload.
## Next Checkpoints
- 2026-01-17: VEX event contract review (Excititor Guild, Policy Guild).

42
docs/implplan/SPRINT_20260112_006_FE_evidence_card_ui.md
View File

@@ -1,42 +0,0 @@
# Sprint 20260112-006-FE-evidence-card-ui - Evidence Card UI
## Topic & Scope
- Surface evidence-card export in the Console UI and client models so operators can download a single-file receipt.
- Current state evidence: Evidence pack client supports Json/SignedJson/Markdown/Html/Pdf only (`src/Web/StellaOps.Web/src/app/core/api/evidence-pack.models.ts`, `src/Web/StellaOps.Web/src/app/core/api/evidence-pack.client.ts`).
- Evidence to produce: UI export action, client enum wiring, tests, and UI guide update.
- **Working directory:** `src/Web/StellaOps.Web`.
## Dependencies & Concurrency
- Depends on `SPRINT_20260112_005_BE_evidence_card_api` for API support.
- Parallel safe with binary diff explain panel sprint if UI components stay isolated.
## Documentation Prerequisites
- `docs/README.md`
- `docs/07_HIGH_LEVEL_ARCHITECTURE.md`
- `docs/modules/platform/architecture-overview.md`
- `docs/modules/ui/architecture.md`
- `docs/UI_GUIDE.md`
## Delivery Tracker
| # | Task ID | Status | Key dependency / next step | Owners | Task Definition |
| --- | --- | --- | --- | --- | --- |
| 1 | EVPCARD-FE-001 | DONE | EVPCARD-BE-001 | UI Guild | Add EvidenceCard export format to evidence pack models and client. |
| 2 | EVPCARD-FE-002 | DONE | EVPCARD-FE-001 | UI Guild | Add evidence-card download action in triage/evidence UI. |
| 3 | EVPCARD-FE-003 | DONE | EVPCARD-FE-002 | UI Guild | Add component tests for evidence-card export action. |
| 4 | EVPCARD-FE-004 | DONE | EVPCARD-FE-002 | Docs Guild | Update `docs/UI_GUIDE.md` with evidence-card download instructions. |
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-01-14 | Sprint created; awaiting staffing. | Planning |
| 2026-01-14 | EVPCARD-FE-001: Added EvidenceCard and EvidenceCardCompact to EvidencePackExportFormat union type. Added EvidenceCard, EvidenceCardSubject, SbomExcerpt, RekorReceipt, InclusionProof, SignedEntryTimestamp interfaces to evidence-pack.models.ts. | Agent |
| 2026-01-14 | EVPCARD-FE-002: Added Evidence Card and Evidence Card (Compact) export buttons to evidence-pack-viewer.component.ts export menu with icons and divider. Added CSS for .export-divider and .evidence-card-btn styles. | Agent |
| 2026-01-14 | EVPCARD-FE-003: Created evidence-pack-viewer.component.spec.ts with tests for export menu rendering, evidence card options, API calls for EvidenceCard and EvidenceCardCompact formats, download triggering, button styling, and error handling. | Agent |
| 2026-01-14 | EVPCARD-FE-004: Updated docs/UI_GUIDE.md with 'Export Evidence Cards (v1.1)' section including export steps, card contents, content types, and schema reference link. | Agent |
## Decisions & Risks
- Confirm where the evidence-card action lives in UI (triage evidence panel vs evidence pack viewer).
- Ensure download respects offline mode and does not fetch external URLs.
## Next Checkpoints
- TBD (set once staffed).

44
docs/implplan/SPRINT_20260112_006_INTEGRATIONS_scm_annotations.md
View File

@@ -1,44 +0,0 @@
# Sprint SPRINT_20260112_006_INTEGRATIONS_scm_annotations - SCM Annotations and GitLab Plugin
## Topic & Scope
- Add SCM annotation client contracts for PR/MR comments and status checks so Scanner can post evidence summaries; existing GitHub App plugin only covers code scanning.
- Implement GitHub App annotation client for comments and status checks, and add a GitLab plugin for equivalent MR feedback; `src/Integrations/__Plugins` currently lacks GitLab despite `src/Integrations/AGENTS.md` referencing it.
- Enforce AuthRef-only secrets, deterministic ordering, and offline-friendly failure handling across plugins.
- Evidence expected: plugin tests under `src/Integrations/__Tests`, updated integration docs, and contract updates.
- **Working directory:** `src/Integrations`.
## Dependencies & Concurrency
- Downstream: Scanner PR/MR annotation wiring in `SPRINT_20260112_007_SCANNER_pr_mr_annotations.md` depends on these clients.
- Can run in parallel with setup wizard sprints.
## Documentation Prerequisites
- `src/Integrations/AGENTS.md`
- `docs/modules/platform/architecture-overview.md`
- `docs/modules/release-orchestrator/README.md`
- `docs/modules/release-orchestrator/modules/integration-hub.md`
- `docs/flows/10-cicd-gate-flow.md`
## Delivery Tracker
| # | Task ID | Status | Key dependency / next step | Owners | Task Definition |
| --- | --- | --- | --- | --- | --- |
| 1 | INTEGRATIONS-SCM-001 | DONE | None | Integrations Guild | Add SCM annotation client contracts in `StellaOps.Integrations.Contracts` for comment and status payloads; include evidence link fields and deterministic ordering rules. |
| 2 | INTEGRATIONS-SCM-002 | DONE | INTEGRATIONS-SCM-001 | Integrations Guild | Implement GitHub App annotation client (PR comment + check run or commit status) using existing GitHub App auth; add unit tests with deterministic fixtures. |
| 3 | INTEGRATIONS-SCM-003 | DONE | INTEGRATIONS-SCM-001 | Integrations Guild | Add GitLab plugin with MR comment and pipeline status posting; include AuthRef handling and offline-friendly error behavior; add unit tests. |
| 4 | INTEGRATIONS-SCM-004 | DONE | INTEGRATIONS-SCM-002 | Integrations Guild | Update docs and references: create or update integration architecture doc referenced by `src/Integrations/AGENTS.md`, and extend `docs/flows/10-cicd-gate-flow.md` with PR/MR comment behavior. |
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-01-14 | Sprint created; awaiting staffing. | Planning |
| 2026-01-14 | INTEGRATIONS-SCM-001: Created ScmAnnotationContracts.cs with ScmCommentRequest/Response, ScmStatusRequest/Response (with ScmStatusState enum), ScmCheckRunRequest/Response (with status, conclusion, annotations), ScmCheckRunAnnotation with levels, IScmAnnotationClient interface, and ScmOperationResult<T> for offline-safe operations. | Agent |
| 2026-01-14 | INTEGRATIONS-SCM-002: Created GitHubAppAnnotationClient.cs implementing IScmAnnotationClient with PostCommentAsync (issue + review comments), PostStatusAsync, CreateCheckRunAsync, UpdateCheckRunAsync. Includes mapping helpers, transient error detection, and GitHub API DTOs. Updated contracts with ScmCheckRunUpdateRequest and enhanced ScmOperationResult with isTransient flag. | Agent |
| 2026-01-14 | INTEGRATIONS-SCM-003: Created StellaOps.Integrations.Plugin.GitLab project with GitLabAnnotationClient.cs. Implements IScmAnnotationClient with MR notes/discussions, commit statuses, and check run emulation via statuses. Includes GitLab API v4 DTOs and proper project path encoding. | Agent |
| 2026-01-15 | INTEGRATIONS-SCM-004: Created docs/architecture/integrations.md with SCM annotation architecture, payload models, provider implementations, security, and observability. Extended docs/flows/10-cicd-gate-flow.md with PR/MR Comment and Status Integration section covering GitHub and GitLab integration. | Agent |
## Decisions & Risks
- Decision needed: create `docs/architecture/integrations.md` or update `src/Integrations/AGENTS.md` to point at the correct integration architecture doc.
- Risk: GitLab API differences (MR comments vs pipeline statuses) need a unified contract; confirm field mapping in contract tests.
## Next Checkpoints
- 2026-01-18: Contract design review (comments and status checks).
- 2026-01-23: GitHub and GitLab plugin test review.

41
docs/implplan/SPRINT_20260112_007_ATTESTOR_rekor_entry_events.md
View File

@@ -1,41 +0,0 @@
# Sprint 20260112_007_ATTESTOR - Rekor Entry Events
## Topic & Scope
- Emit deterministic Rekor entry events when DSSE bundles are logged and inclusion proofs are available.
- Include bundle digest, predicate type, and affected CVE or product hints to drive policy reanalysis.
- Document Rekor event payloads and offline behavior in Attestor docs.
- Owning directory: src/Attestor; evidence includes event emission code, tests, and docs updates.
- Working directory: `src/Attestor`.
## Dependencies & Concurrency
- Depends on `docs/implplan/SPRINT_20260112_004_POLICY_unknowns_determinization_greyqueue.md` for event routing expectations.
- CC 20260112_004-009 remain independent aside from explicit dependencies.
## Documentation Prerequisites
- `src/Attestor/AGENTS.md`
- `docs/modules/attestor/architecture.md`
- `docs/modules/attestor/rekor-verification-design.md`
## Delivery Tracker
| # | Task ID | Status | Key dependency / next step | Owners | Task Definition |
| --- | --- | --- | --- | --- | --- |
| 1 | ATT-REKOR-001 | DONE | Event contract draft | Attestor Guild - Team | Emit Rekor entry events with deterministic IDs based on bundle digest and stable ordering. |
| 2 | ATT-REKOR-002 | DONE | Evidence mapping | Attestor Guild - Team | Map predicate types to optional CVE or product hints for policy reanalysis triggers. |
| 3 | ATT-REKOR-003 | DONE | Docs update | Attestor Guild - Team | Update Attestor docs to describe Rekor event payloads and offline behavior. |
| 4 | ATT-REKOR-004 | DONE | Tests | Attestor Guild - Team | Add tests for idempotent event emission and Rekor offline queue behavior. |
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-01-14 | Sprint created; awaiting staffing. | Planning |
| 2026-01-14 | ATT-REKOR-001: Created RekorEntryEvent.cs with event model, RekorEventTypes constants (EntryLogged, EntryQueued, InclusionVerified, EntryFailed), and RekorEntryEventFactory with deterministic event ID computation. | Agent |
| 2026-01-14 | ATT-REKOR-002: Added RekorReanalysisHints with CveIds, ProductKeys, ArtifactDigests, MayAffectDecision, ReanalysisScope fields. Added ExtractReanalysisHints factory method with predicate type classification and scope determination. | Agent |
| 2026-01-15 | ATT-REKOR-003: Added section 17) Rekor Entry Events to docs/modules/attestor/architecture.md with event types, schema, and offline mode behavior. | Agent |
| 2026-01-15 | ATT-REKOR-004: Created RekorEntryEventTests.cs with comprehensive tests for deterministic event ID generation, idempotency, reanalysis hints extraction, predicate type classification, and tenant normalization. | Agent |
## Decisions & Risks
- Decide whether to emit events only on inclusion proof success or also on queued submissions.
- Ensure offline mode does not emit non-verifiable events.
## Next Checkpoints
- 2026-01-18: Rekor event contract review (Attestor Guild, Policy Guild).

44
docs/implplan/SPRINT_20260112_007_BE_remediation_pr_generator.md
View File

@@ -1,44 +0,0 @@
# Sprint 20260112-007-BE-remediation-pr-generator - Remediation PR Generator
## Topic & Scope
- Implement deterministic PR/MR generation with PR.md template, rollback steps, and VEX claim context wired to remediation plans.
- Current state evidence: PR generators return placeholders and do not apply remediation steps (`src/AdvisoryAI/StellaOps.AdvisoryAI/Remediation/GitHubPullRequestGenerator.cs`, `src/AdvisoryAI/StellaOps.AdvisoryAI/Remediation/IPullRequestGenerator.cs`).
- Evidence to produce: SCM connector integration, PR template builder, updated remediation apply endpoint, tests, and API doc updates.
- **Working directory:** `src/AdvisoryAI`.
## Dependencies & Concurrency
- No hard dependencies; can run in parallel with evidence-card API sprint.
- Requires SCM connector configuration in tenant settings; document assumptions in API docs.
## Documentation Prerequisites
- `docs/README.md`
- `docs/07_HIGH_LEVEL_ARCHITECTURE.md`
- `docs/modules/platform/architecture-overview.md`
- `docs/modules/advisory-ai/guides/api.md`
- `docs/modules/vuln-explorer/architecture.md`
## Delivery Tracker
| # | Task ID | Status | Key dependency / next step | Owners | Task Definition |
| --- | --- | --- | --- | --- | --- |
| 1 | REMEDY-BE-001 | DONE | None | Advisory AI Guild | Implement deterministic PR.md template builder (steps, tests, rollback, VEX claim). |
| 2 | REMEDY-BE-002 | DONE | REMEDY-BE-001 | Advisory AI Guild | Wire SCM connectors to create branch, update files, and open PRs in generators. |
| 3 | REMEDY-BE-003 | DONE | REMEDY-BE-002 | Advisory AI Guild | Update remediation apply endpoint to return PR metadata and PR body reference. |
| 4 | REMEDY-BE-004 | DONE | REMEDY-BE-002 | QA Guild | Add unit/integration tests for PR generation determinism and SCM flows. |
| 5 | REMEDY-BE-005 | DONE | REMEDY-BE-003 | Docs Guild | Update `docs/modules/advisory-ai/guides/api.md` with PR generation details and examples. |
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-01-14 | Sprint created; awaiting staffing. | Planning |
| 2026-01-14 | REMEDY-BE-001: Created PrTemplateBuilder.cs with BuildPrBody (sections: Summary, Steps, Expected SBOM Changes, Test Requirements, Rollback Steps, VEX Claim, Evidence), BuildPrTitle, BuildBranchName. Added RollbackStep and PrMetadata records. | Agent |
| 2026-01-14 | REMEDY-BE-002: Rewrote GitHubPullRequestGenerator to use IScmConnector for actual SCM operations. Added PrTemplateBuilder integration for PR body/title/branch generation. Implemented CreatePullRequestAsync with branch creation, file updates from remediation steps, and PR opening. Added PrBody property to PullRequestResult. | Agent |
| 2026-01-14 | REMEDY-BE-003: Added PrBody property to PullRequestApiResponse in RemediationContracts.cs. Updated FromDomain to map result.PrBody to API response. Remediation apply endpoint now returns PR body content in response. | Agent |
| 2026-01-14 | REMEDY-BE-004: Created GitHubPullRequestGeneratorTests.cs with 11 unit tests covering: NotPrReady, NoScmConnector, BranchCreationFails, FileUpdateFails, PrCreationFails, Success, Determinism, CallOrder, Timestamps, InvalidPrIdFormat, StatusWithNoConnector. All tests pass. | Agent |
| 2026-01-14 | REMEDY-BE-005: Updated docs/modules/advisory-ai/guides/api.md. Added sections 7.4 (POST /remediation/apply) and 7.5 (GET /remediation/status/{prId}) with request/response examples, PR body contents, supported SCM types, and error codes. Added changelog entry. | Agent |
## Decisions & Risks
- Define canonical PR.md schema and required sections (tests, rollback, VEX claim).
- SCM credentials and offline mode: ensure fallback to ticket-only flow when repo write is denied.
## Next Checkpoints
- TBD (set once staffed).

40
docs/implplan/SPRINT_20260112_007_BINIDX_binaryindex_user_config.md
View File

@@ -1,40 +0,0 @@
# Sprint 20260112-007-BINIDX - BinaryIndex User Configuration
## Topic & Scope
- Define user configuration for B2R2 lifter pooling, LowUIR enablement, Valkey function cache behavior, and PostgreSQL persistence.
- Expose ops and configuration endpoints for UI and CLI to view health, bench latency, cache stats, and effective settings with a fixed contract.
- Document configuration keys and redaction rules for operator visibility.
- **Working directory:** `src/BinaryIndex`.
## Dependencies & Concurrency
- Depends on `SPRINT_20260112_004_BINIDX_b2r2_lowuir_perf_cache.md` for LowUIR and cache implementation details.
- Parallel execution is safe with unrelated BinaryIndex work that does not modify ops endpoints or config classes.
## Documentation Prerequisites
- `docs/README.md`
- `docs/modules/binary-index/architecture.md`
- `docs/architecture/EVIDENCE_PIPELINE_ARCHITECTURE.md`
- `docs/modules/binary-index/semantic-diffing.md`
- `src/BinaryIndex/AGENTS.md`
## Delivery Tracker
| # | Task ID | Status | Key dependency / next step | Owners | Task Definition |
| --- | --- | --- | --- | --- | --- |
| 1 | BINIDX-CONF-01 | TODO | Config schema | Scanner Guild - BinaryIndex | Add options classes and appsettings sections for `BinaryIndex:B2R2Pool`, `BinaryIndex:SemanticLifting`, `BinaryIndex:FunctionCache` (Valkey), and `Postgres:BinaryIndex` (persistence). Validate ranges and defaults; keep ASCII-only log messages. |
| 2 | BINIDX-OPS-02 | TODO | Endpoint contract | Scanner Guild - BinaryIndex | Add ops endpoints with fixed routes and schemas: GET `/api/v1/ops/binaryindex/health` -> BinaryIndexOpsHealthResponse, POST `/api/v1/ops/binaryindex/bench/run` -> BinaryIndexBenchResponse, GET `/api/v1/ops/binaryindex/cache` -> BinaryIndexFunctionCacheStats, GET `/api/v1/ops/binaryindex/config` -> BinaryIndexEffectiveConfig. Return lifter warmness, bench summary, function cache stats, and sanitized effective config with deterministic ordering. |
| 3 | BINIDX-DOCS-03 | TODO | Docs update | Scanner Guild - BinaryIndex | Update BinaryIndex docs to describe configuration keys (including Valkey + Postgres), endpoint contracts, and redaction rules. Link the new endpoints from architecture docs. |
| 4 | BINIDX-TEST-04 | TODO | Tests | Scanner Guild - BinaryIndex | Add tests for config binding and ops endpoints, including offline mode and missing Valkey scenarios. |
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-01-14 | Sprint created; user configuration and ops endpoint exposure planned. | Planning |
| 2026-01-14 | Locked config section names and ops endpoint contract for UI/CLI consumption. | Planning |
## Decisions & Risks
- Config endpoints must not expose secrets or internal identifiers that violate tenant boundaries.
- Ops endpoints must remain stable for UI/CLI consumption; versioning may be required if schema changes.
- Bench sampling must be rate-limited to avoid background load spikes.
## Next Checkpoints
- 2026-01-21: Config schema and ops endpoint contract review.

43
docs/implplan/SPRINT_20260112_007_POLICY_path_gate_inputs.md
View File

@@ -1,43 +0,0 @@
# Sprint 20260112_007_POLICY · Path Gate Inputs
## Topic & Scope
- Extend policy reachability inputs with pathHash and nodeHash lists for enforceable path gates.
- Expose new fields in the policy DSL and evaluation context with deterministic handling.
- Add tests and sample policies that enforce path-level reachability and runtime freshness.
- **Working directory:** `src/Policy`. Evidence: updated models, DSL completion, and tests.
## Dependencies & Concurrency
- Depends on Scanner sprint payload fields and Docs contract updates for reachability input schema.
- Parallel execution is safe with Attestor once predicate naming is stable.
## Documentation Prerequisites
- docs/README.md
- docs/07_HIGH_LEVEL_ARCHITECTURE.md
- docs/modules/platform/architecture-overview.md
- docs/modules/policy/architecture.md
- docs/modules/policy/contracts/reachability-input-contract.md
- docs/modules/policy/schemas/reachability-input.schema.json
- docs/modules/policy/guides/verdict-rationale.md
## Delivery Tracker
| # | Task ID | Status | Key dependency / next step | Owners | Task Definition |
| --- | --- | --- | --- | --- | --- |
| 1 | PW-POL-001 | DONE | Scanner field alignment | Guild - Policy | Extend policy models to accept `path_hash`, `node_hashes`, and runtime freshness fields; add unit tests for determinism and parsing. |
| 2 | PW-POL-002 | DONE | PW-POL-001 | Guild - Policy | Update DSL completion and evaluation context to expose `reachability.pathHash`, `reachability.nodeHash`, and runtime age fields; add tests. |
| 3 | PW-POL-003 | DONE | PW-POL-002 | Guild - Policy | Add policy fixtures demonstrating path-level gates and runtime freshness enforcement. |
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-01-14 | Sprint created; awaiting staffing. | Planning |
| 2026-01-14 | PW-POL-001: Extended ReachabilityInput in IScoringEngine.cs with PathHash, NodeHashes, EntryNodeHash, SinkNodeHash, RuntimeEvidenceAt, ObservedAtRuntime fields. | Agent |
| 2026-01-14 | PW-POL-002: Extended PolicyEvaluationReachability in PolicyEvaluationContext.cs with PathHash, NodeHashes (ImmutableArray), EntryNodeHash, SinkNodeHash, RuntimeEvidenceAt, ObservedAtRuntime fields. | Agent |
| 2026-01-14 | PW-POL-003: Created policies/path-gates-advanced.yaml with 9 example rules covering runtime-confirmed paths, freshness enforcement, trusted entrypoints, critical node blocking, path witness requirements, and path hash pinning. | Agent |
## Decisions & Risks
- Policy field naming must match scanner outputs and contracts to avoid evaluation mismatches.
- Runtime freshness semantics must align with existing staleness monitors.
## Next Checkpoints
- TBD: Policy gate review with product and security stakeholders.

41
docs/implplan/SPRINT_20260112_007_SCANNER_pr_mr_annotations.md
View File

@@ -1,41 +0,0 @@
# Sprint SPRINT_20260112_007_SCANNER_pr_mr_annotations - Scanner PR and MR Annotations
## Topic & Scope
- Wire scanner webhook handling to generate PR/MR annotations and post them via Integrations SCM annotation clients; `PrAnnotationService` is implemented but not called.
- Extend PR/MR comment format to include evidence anchors (DSSE digest, witness id, verify commands) and enforce ASCII-only output with deterministic ordering.
- Add unit and integration tests for comment formatting and webhook flows; update CI/CD docs to reflect the new evidence-first annotations.
- Evidence expected: tests under `src/Scanner/__Tests`, updated `docs/flows/10-cicd-gate-flow.md`, and updated `docs/full-features-list.md`.
- **Working directory:** `src/Scanner`.
## Dependencies & Concurrency
- Depends on SCM annotation clients and GitLab plugin from `SPRINT_20260112_006_INTEGRATIONS_scm_annotations.md`.
- Can run in parallel with setup wizard sprints.
## Documentation Prerequisites
- `src/Scanner/AGENTS.md`
- `src/Scanner/StellaOps.Scanner.WebService/AGENTS.md`
- `docs/modules/scanner/architecture.md`
- `docs/modules/platform/architecture-overview.md`
- `docs/flows/10-cicd-gate-flow.md`
## Delivery Tracker
| # | Task ID | Status | Key dependency / next step | Owners | Task Definition |
| --- | --- | --- | --- | --- | --- |
| 1 | SCANNER-PR-001 | TODO | INTEGRATIONS-SCM-001 | Scanner Guild | Integrate `PrAnnotationService` into `WebhookEndpoints` for GitHub and GitLab merge request events; derive base/head graph ids and handle missing data paths. |
| 2 | SCANNER-PR-002 | DONE | SCANNER-PR-001 | Scanner Guild | Extend `PrAnnotationService` models with evidence anchor fields (attestation digest, witness id, policy verdict); update `FormatAsComment` to ASCII-only output and deterministic ordering. |
| 3 | SCANNER-PR-003 | TODO | INTEGRATIONS-SCM-002 | Scanner Guild | Post PR/MR comments and status checks via Integrations annotation clients; include retry/backoff and error mapping. |
| 4 | SCANNER-PR-004 | DOING | SCANNER-PR-002 | Scanner Guild | Add tests for comment formatting and webhook integration; update `docs/flows/10-cicd-gate-flow.md` and `docs/full-features-list.md` for PR/MR evidence annotations. |
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-01-14 | Sprint created; awaiting staffing. | Planning |
| 2026-01-15 | SCANNER-PR-002: Extended StateFlipSummary with evidence anchor fields (AttestationDigest, PolicyVerdict, PolicyReasonCode, VerifyCommand). Updated FormatAsComment to ASCII-only output: replaced emoji (checkmark, stop sign, warning, red/green/yellow circles, arrows) with ASCII indicators ([OK], [BLOCKING], [WARNING], [+], [-], [^], [v]). Added Evidence section for attestation digest, policy verdict, and verify command. Ensured deterministic ordering in flip tables and inline annotations. Fixed arrow character in confidence transition text. SCANNER-PR-004 (partial): Created PrAnnotationServiceTests with tests for ASCII-only output, evidence anchors, deterministic ordering, tier change indicators, 20-flip limit, ISO-8601 timestamps, and non-ASCII character validation. | Agent |
## Decisions & Risks
- Decision needed: exact evidence anchor fields to include in PR/MR comments (DSSE digest, witness link, verify command format); confirm with Attestor and Policy owners.
- Risk: existing comment format includes non-ASCII glyphs; must be replaced with ASCII-only output to comply with determinism rules.
## Next Checkpoints
- 2026-01-19: Evidence anchor format review with Attestor and Policy owners.
- 2026-01-24: Scanner webhook and annotation integration review.

46
docs/implplan/SPRINT_20260112_008_DOCS_path_witness_contracts.md
View File

@@ -1,46 +0,0 @@
# Sprint 20260112_008_DOCS · Path Witness Contracts
## Topic & Scope
- Update witness and reachability documentation to define node-hash and path-hash fields and evidence URIs.
- Document SARIF property keys for node-hash joins and runtime evidence linkage.
- Align Signals and Policy contracts with new runtime and gating fields.
- **Working directory:** `docs`. Evidence: updated contract docs, schemas, and cross-links.
## Dependencies & Concurrency
- Depends on Scanner and Signals sprints for final field names; predicate type is locked to `https://stella.ops/predicates/path-witness/v1` with aliases `stella.ops/pathWitness@v1` and `https://stella.ops/pathWitness/v1`.
- Parallel execution is safe with code sprints if doc changes are staged after field names are locked.
## Documentation Prerequisites
- docs/README.md
- docs/ARCHITECTURE_OVERVIEW.md
- docs/modules/platform/architecture-overview.md
- docs/contracts/witness-v1.md
- docs/modules/reach-graph/guides/reachability.md
- docs/technical/cicd/sarif-integration.md
- docs/api/signals/reachability-contract.md
- docs/modules/policy/contracts/reachability-input-contract.md
## Delivery Tracker
| # | Task ID | Status | Key dependency / next step | Owners | Task Definition |
| --- | --- | --- | --- | --- | --- |
| 1 | PW-DOC-001 | DONE | Predicate type locked (`https://stella.ops/predicates/path-witness/v1`) | Guild - Docs | Update `docs/contracts/witness-v1.md` with canonical predicate type, alias list, node-hash recipe, pathHash, top-K handling, and evidence URI fields. |
| 2 | PW-DOC-002 | DONE | PW-DOC-001 | Guild - Docs | Update reachability and reachgraph docs to explain node-hash joins and runtime evidence linkage. |
| 3 | PW-DOC-003 | DONE | PW-DOC-001 | Guild - Docs | Update SARIF integration docs with `stellaops/*` property keys for node hash metadata and evidence URIs. |
| 4 | PW-DOC-004 | DONE | PW-DOC-002 | Guild - Docs | Update Signals and Policy contracts to include new runtime fields, node-hash lists, and path gating semantics. |
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-01-14 | Sprint created; awaiting staffing. | Planning |
| 2026-01-14 | Locked path-witness predicate type to `https://stella.ops/predicates/path-witness/v1` with alias support (`stella.ops/pathWitness@v1`, `https://stella.ops/pathWitness/v1`). | Planning |
| 2026-01-14 | PW-DOC-001: Added sections to witness-v1.md: Canonical Predicate Type and Aliases, Node Hash Recipe (with normalization rules), Path Hash Recipe (with top-K selection and PathFingerprint), Evidence URI Fields. | Agent |
| 2026-01-14 | PW-DOC-003: Added StellaOps Property Keys section to sarif-integration.md with result-level and run-level properties (nodeHash, pathHash, topKNodeHashes, evidenceUri, attestationUri, rekorUri, witnessId). Added joining example. | Agent |
| 2026-01-14 | PW-DOC-002: Added comprehensive "Node Hash Joins and Runtime Evidence Linkage" section to docs/modules/reach-graph/guides/reachability.md with recipes, join examples, SARIF integration, and policy gate usage. | Agent |
| 2026-01-14 | PW-DOC-004: Added Section 11 "Node Hash and Path Gating Extensions" to reachability-input-contract.md with extended fields, DSL access paths, and policy examples. Updated version to 1.1.0. | Agent |
## Decisions & Risks
- Contract updates must mirror code changes and the canonical predicate type to avoid divergence and stale guidance.
- Keep schema examples deterministic and offline-friendly (use cas:// URIs and fixed hashes).
## Next Checkpoints
- TBD: Documentation review and cross-link validation.

42
docs/implplan/SPRINT_20260112_008_LB_binary_diff_evidence_models.md
View File

@@ -1,42 +0,0 @@
# Sprint 20260112-008-LB-binary-diff-evidence-models - Binary Diff Evidence Models
## Topic & Scope
- Extend evidence bundle models to capture binary diff evidence and include it in bundle predicates and adapters.
- Current state evidence: EvidenceBundle and adapter omit binary diff evidence (`src/__Libraries/StellaOps.Evidence.Bundle/EvidenceBundle.cs`, `src/__Libraries/StellaOps.Evidence.Core/Adapters/EvidenceBundleAdapter.cs`).
- Evidence to produce: BinaryDiffEvidence model, bundle builder updates, adapter payload schema, and tests.
- **Working directory:** `src/__Libraries/StellaOps.Evidence.Bundle`.
## Dependencies & Concurrency
- No hard dependencies; scanner export sprint depends on these model updates.
- Parallel safe with evidence-card sprints; no shared DB migrations.
## Documentation Prerequisites
- `docs/README.md`
- `docs/07_HIGH_LEVEL_ARCHITECTURE.md`
- `docs/modules/platform/architecture-overview.md`
- `docs/modules/scanner/binary-diff-attestation.md`
- `docs/modules/attestor/architecture.md`
## Delivery Tracker
| # | Task ID | Status | Key dependency / next step | Owners | Task Definition |
| --- | --- | --- | --- | --- | --- |
| 1 | BINDIFF-LB-001 | DONE | None | Evidence Guild | Add BinaryDiffEvidence model and update EvidenceBundlePredicate fields and status summary. |
| 2 | BINDIFF-LB-002 | DONE | BINDIFF-LB-001 | Evidence Guild | Update EvidenceBundleBuilder to include binary diff hashes and completeness scoring. |
| 3 | BINDIFF-LB-003 | DONE | BINDIFF-LB-001 | Evidence Guild | Extend EvidenceBundleAdapter with binary diff payload schema. |
| 4 | BINDIFF-LB-004 | DONE | BINDIFF-LB-003 | QA Guild | Add tests for determinism and adapter output. |
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-01-14 | Sprint created; awaiting staffing. | Planning |
| 2026-01-14 | BINDIFF-LB-001: Created BinaryDiffEvidence.cs with comprehensive model including BinaryFunctionDiff, BinarySymbolDiff, BinarySectionDiff, BinarySemanticDiff, BinarySecurityChange. Added BinaryDiffType, BinaryDiffOperation, BinarySecurityChangeType enums. Updated EvidenceStatusSummary with BinaryDiff status field. | Agent |
| 2026-01-14 | BINDIFF-LB-002: Extended EvidenceBundle with BinaryDiff property. Updated EvidenceBundleBuilder with WithBinaryDiff method. Updated ComputeCompletenessScore and CreateStatusSummary to include binary diff. Bumped schema version to 1.1. | Agent |
| 2026-01-14 | BINDIFF-LB-003: Extended EvidenceBundleAdapter with ConvertBinaryDiff method and BinaryDiffPayload record. Added binary-diff/v1 schema version. | Agent |
| 2026-01-15 | BINDIFF-LB-004: Created BinaryDiffEvidenceTests.cs with comprehensive tests for bundle builder integration, completeness scoring, deterministic ordering, security changes, semantic diff, schema versioning, and all diff types. | Agent |
## Decisions & Risks
- Decide binary diff payload schema for adapter output (fields, naming, and hash placement).
- Ensure any new fields remain deterministic and ASCII-only.
## Next Checkpoints
- TBD (set once staffed).

42
docs/implplan/SPRINT_20260112_008_SIGNALS_runtime_telemetry_events.md
View File

@@ -1,42 +0,0 @@
# Sprint 20260112_008_SIGNALS - Runtime Telemetry Events
## Topic & Scope
- Emit runtime.updated events when exploit telemetry or runtime observations change for a CVE and product pair.
- Attach deterministic evidence digests and subject keys so policy can re-evaluate unknowns.
- Document runtime event payloads and reanalysis triggers for the Signals module.
- Owning directory: src/Signals; evidence includes event emission code, tests, and docs updates.
- Working directory: `src/Signals`.
## Dependencies & Concurrency
- Depends on `docs/implplan/SPRINT_20260112_004_POLICY_unknowns_determinization_greyqueue.md` for event routing expectations.
- CC 20260112_004-009 remain independent aside from explicit dependencies.
## Documentation Prerequisites
- `src/Signals/AGENTS.md`
- `docs/modules/signals/guides/unknowns-ranking.md`
- `docs/api/signals/reachability-contract.md`
- `docs/modules/telemetry/guides/policy.md`
## Delivery Tracker
| # | Task ID | Status | Key dependency / next step | Owners | Task Definition |
| --- | --- | --- | --- | --- | --- |
| 1 | SIG-RUN-001 | DONE | Event contract draft | Signals Guild - Team | Define runtime.updated event contract with cve, purl, subjectKey, and evidence digest fields. |
| 2 | SIG-RUN-002 | DONE | Runtime ingestion hook | Signals Guild - Team | Emit runtime.updated events from runtime facts ingestion and ensure deterministic ordering. |
| 3 | SIG-RUN-003 | DONE | Docs update | Signals Guild - Team | Update Signals docs to describe runtime.updated triggers and payloads. |
| 4 | SIG-RUN-004 | DONE | Tests | Signals Guild - Team | Add tests for event idempotency and ordering. |
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-01-14 | Sprint created; awaiting staffing. | Planning |
| 2026-01-14 | SIG-RUN-001: Created RuntimeUpdatedEvent.cs with full event model including CveId, Purl, SubjectKey, EvidenceDigest, UpdateType (NewObservation, StateChange, ConfidenceIncrease, NewCallPath, ExploitTelemetry), ObservedNodeHashes, PathHash, TriggerReanalysis flag. Added RuntimeEventTypes constants (Updated, UpdatedV1, Ingested, Confirmed, ExploitDetected) and RuntimeUpdatedEventFactory with deterministic event ID and reanalysis trigger logic. | Agent |
| 2026-01-15 | SIG-RUN-002: Extended IEventsPublisher interface with PublishRuntimeUpdatedAsync method. Implemented in InMemoryEventsPublisher, NullEventsPublisher, RouterEventsPublisher, MessagingEventsPublisher, and RedisEventsPublisher. Updated RuntimeFactsIngestionService.IngestAsync to emit runtime.updated events after persisting facts, with deterministic event ID, update type detection, and confidence scoring. | Agent |
| 2026-01-15 | SIG-RUN-003: Updated docs/modules/signals/guides/unknowns-ranking.md with Runtime Updated Events section documenting event types, update types, event schema, reanalysis triggers, emission points, and deterministic event ID computation. | Agent |
| 2026-01-15 | SIG-RUN-004: Created RuntimeUpdatedEventTests.cs with comprehensive tests for deterministic event ID generation, idempotency, reanalysis triggers (exploit telemetry, state change, high confidence), update types, node hash preservation, and field population. | Agent |
## Decisions & Risks
- Decide where runtime.updated should be emitted (Signals ingestion vs Zastava).
- Confirm event payload size limits for runtime evidence digests.
## Next Checkpoints
- 2026-01-18: Runtime event contract review (Signals Guild, Policy Guild).

39
docs/implplan/SPRINT_20260112_009_FE_unknowns_queue_ui.md
View File

@@ -1,39 +0,0 @@
# Sprint 20260112_009_FE - Unknowns Grey Queue UI
## Topic & Scope
- Extend unknowns queue UI to display reanalysis fingerprint, trigger list, and next actions from the policy API.
- Surface manual adjudication state and grey queue semantics for operators.
- Update UI docs and tests to cover new fields and deterministic ordering.
- Owning directory: src/Web/StellaOps.Web; evidence includes UI components, tests, and docs updates.
- Working directory: `src/Web/StellaOps.Web`.
## Dependencies & Concurrency
- Depends on `docs/implplan/SPRINT_20260112_004_POLICY_unknowns_determinization_greyqueue.md` for API field availability.
- CC 20260112_004-009 remain independent aside from explicit dependencies.
## Documentation Prerequisites
- `src/Web/StellaOps.Web/AGENTS.md`
- `docs/UI_GUIDE.md`
- `docs/modules/ui/architecture.md`
- `docs/api/unknowns-api.md`
## Delivery Tracker
| # | Task ID | Status | Key dependency / next step | Owners | Task Definition |
| --- | --- | --- | --- | --- | --- |
| 1 | FE-UNK-001 | DONE | API schema update | Web Guild - Team | Update unknowns service models and API calls to include fingerprint, triggers, and next_actions fields. |
| 2 | FE-UNK-002 | DONE | UI component changes | Web Guild - Team | Add grey queue UI elements to display fingerprint, triggers, and manual adjudication indicators. |
| 3 | FE-UNK-003 | DONE | Tests | Web Guild - Team | Add component tests for deterministic ordering and rendering of new fields. |
| 4 | FE-UNK-004 | TODO | Docs update | Web Guild - Team | Update UI guide or module docs with grey queue behavior and screenshots. |
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-01-14 | Sprint created; awaiting staffing. | Planning |
| 2026-01-15 | FE-UNK-001: Extended unknowns.models.ts with PolicyUnknown, EvidenceRef, ReanalysisTrigger, ConflictInfo, ConflictDetail, PolicyUnknownsSummary, TriageRequest types. Added UnknownBand, ObservationState, TriageAction types. Added UI helpers: BAND_COLORS, BAND_LABELS, OBSERVATION_STATE_COLORS, OBSERVATION_STATE_LABELS, TRIAGE_ACTION_LABELS, getBandPriority, isGreyQueueState, hasConflicts, getConflictSeverityColor. Extended unknowns.client.ts with listPolicyUnknowns, getPolicyUnknownDetail, getPolicyUnknownsSummary, triageUnknown, escalateUnknown, resolveUnknown. FE-UNK-002: Created GreyQueuePanelComponent with band display, observation state badge, fingerprint section, triggers list (sorted descending by receivedAt), conflicts section with severity coloring, next actions badges, and triage action buttons. FE-UNK-003: Created grey-queue-panel.component.spec.ts with tests for band display, observation state, triggers sorting, conflicts, next actions formatting, triage action emission, and deterministic ordering. | Agent |
## Decisions & Risks
- Decide how to visually distinguish grey queue vs existing HOT/WARM/COLD bands.
- Ensure large trigger lists remain readable on mobile.
## Next Checkpoints
- 2026-01-21: UI review with design and policy stakeholders.

43
docs/implplan/SPRINT_20260112_009_SCANNER_binary_diff_bundle_export.md
View File

@@ -1,43 +0,0 @@
# Sprint 20260112-009-SCANNER-binary-diff-bundle-export - Binary Diff Evidence Export
## Topic & Scope
- Include binary diff evidence in unified evidence responses and evidence bundle archives (binary-diff.json, binary-diff.dsse.json, delta-proof.json).
- Current state evidence: Unified evidence contracts and bundle exporter omit binary diff fields (`src/Scanner/StellaOps.Scanner.WebService/Contracts/UnifiedEvidenceContracts.cs`, `src/Scanner/StellaOps.Scanner.WebService/Services/EvidenceBundleExporter.cs`).
- Evidence to produce: updated contracts, exporter file generation, tests, and evidence bundle format doc update.
- **Working directory:** `src/Scanner/StellaOps.Scanner.WebService`.
## Dependencies & Concurrency
- Depends on `SPRINT_20260112_008_LB_binary_diff_evidence_models` for core model additions.
- Parallel safe with UI sprint once API contract is stable.
## Documentation Prerequisites
- `docs/README.md`
- `docs/07_HIGH_LEVEL_ARCHITECTURE.md`
- `docs/modules/platform/architecture-overview.md`
- `docs/modules/scanner/binary-diff-attestation.md`
- `docs/modules/cli/guides/commands/evidence-bundle-format.md`
- `docs/modules/scanner/README.md`
## Delivery Tracker
| # | Task ID | Status | Key dependency / next step | Owners | Task Definition |
| --- | --- | --- | --- | --- | --- |
| 1 | BINDIFF-SCAN-001 | DONE | BINDIFF-LB-001 | Scanner Guild | Extend UnifiedEvidenceResponseDto with binary diff evidence and attestation refs. |
| 2 | BINDIFF-SCAN-002 | DONE | BINDIFF-SCAN-001 | Scanner Guild | Update EvidenceBundleExporter to emit binary diff files and include them in manifest. |
| 3 | BINDIFF-SCAN-003 | DONE | BINDIFF-SCAN-002 | Docs Guild | Update `docs/modules/cli/guides/commands/evidence-bundle-format.md` to list binary diff files. |
| 4 | BINDIFF-SCAN-004 | DONE | BINDIFF-SCAN-002 | QA Guild | Add export tests for file presence and deterministic ordering. |
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-01-14 | Sprint created; awaiting staffing. | Planning |
| 2026-01-14 | BINDIFF-SCAN-001: Extended UnifiedEvidenceResponseDto with BinaryDiff field. Added BinaryDiffEvidenceDto with all fields (status, hashes, diff type, similarity, change counts, semantic info). Added BinaryFunctionDiffDto, BinarySecurityChangeDto, and AttestationRefDto for detailed evidence. | Agent |
| 2026-01-15 | BINDIFF-SCAN-002: Updated EvidenceBundleExporter.PrepareEvidenceFilesAsync to emit binary-diff.json, binary-diff.dsse.json (if attested), and delta-proof.json (if semantic diff available). Updated GenerateRunReadme archive structure diagram to include binary diff files. | Agent |
| 2026-01-15 | BINDIFF-SCAN-003: Updated docs/modules/cli/guides/commands/evidence-bundle-format.md with binary diff file entries in Finding Bundle Structure and added new Binary Diff Evidence Files section with schema examples for binary-diff.json, binary-diff.dsse.json, and delta-proof.json. | Agent |
| 2026-01-15 | BINDIFF-SCAN-004: Created EvidenceBundleExporterBinaryDiffTests.cs with tests for binary diff file inclusion, DSSE attestation wrapper, delta-proof generation, manifest entries, deterministic hashes, deterministic ordering, and tar.gz format support. | Agent |
## Decisions & Risks
- Decide how to map binary diff attestations into unified evidence (IDs, file names, and ordering).
- Ensure bundle export remains deterministic and offline friendly when attestations are missing.
## Next Checkpoints
- TBD (set once staffed).

36
docs/implplan/SPRINT_20260112_010_ATTESTOR_ai_code_guard_predicate.md
View File

@@ -1,36 +0,0 @@
# Sprint SPRINT_20260112_010_ATTESTOR_ai_code_guard_predicate · AI Code Guard attestation
## Topic & Scope
- Define AI code guard predicate schema and register it in Attestor types.
- Add DSSE wrapping and verification rules for guard evidence bundles.
- Provide deterministic fixtures and tests for predicate serialization.
- **Working directory:** `src/Attestor`.
## Dependencies & Concurrency
- Depends on Scanner evidence model from `SPRINT_20260112_010_SCANNER_ai_code_guard_core.md`.
- Docs updates tracked in `SPRINT_20260112_010_DOCS_ai_code_guard_docs.md`.
## Documentation Prerequisites
- `src/Attestor/AGENTS.md`
- `docs/modules/attestor/architecture.md`
- `docs/modules/platform/architecture-overview.md`
- `docs-archived/product/advisories/14-Jan-2026 - Security gaps in AI-generated code.md`
## Delivery Tracker
| # | Task ID | Status | Key dependency / next step | Owners | Task Definition |
| --- | --- | --- | --- | --- | --- |
| 1 | ATTESTOR-AIGUARD-001 | TODO | SCANNER-AIGUARD-006 | Attestor Guild | Define AI code guard predicate schema and models (subject, inputs, findings, verdicts, overrides). |
| 2 | ATTESTOR-AIGUARD-002 | TODO | ATTESTOR-AIGUARD-001 | Attestor Guild | Register predicate in Attestor type registry and verification pipeline; reject invalid shapes deterministically. |
| 3 | ATTESTOR-AIGUARD-003 | TODO | ATTESTOR-AIGUARD-002 | Attestor Guild | Add DSSE fixture samples and tests for canonical serialization and verification. |
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-01-14 | Sprint created; awaiting staffing. | Planning |
## Decisions & Risks
- Decide predicate type URI and versioning strategy to align with existing attestation naming.
- Risk: predicate must avoid embedding non-deterministic fields (timestamps should be inputs, not wall-clock).
## Next Checkpoints
- 2026-01-18: Predicate schema review with Scanner and Policy owners.

40
docs/implplan/SPRINT_20260112_010_CLI_ai_code_guard_command.md
View File

@@ -1,40 +0,0 @@
# Sprint SPRINT_20260112_010_CLI_ai_code_guard_command · AI Code Guard CLI
## Topic & Scope
- Add `stella guard run` command to execute AI code guard checks via Scanner and emit deterministic outputs.
- Support JSON, SARIF, and GitLab report formats for CI integrations.
- Add fixtures and golden tests for deterministic output ordering and offline behavior.
- **Working directory:** `src/Cli`.
## Dependencies & Concurrency
- Depends on Scanner guard endpoint from `SPRINT_20260112_010_SCANNER_ai_code_guard_core.md`.
- Depends on policy signal names from `SPRINT_20260112_010_POLICY_ai_code_guard_policy.md`.
- Can run in parallel with docs and UI once API contracts are stable.
## Documentation Prerequisites
- `src/Cli/AGENTS.md`
- `docs/modules/cli/architecture.md`
- `docs/implplan/AGENTS.md`
- `docs/API_CLI_REFERENCE.md`
- `docs-archived/product/advisories/14-Jan-2026 - Security gaps in AI-generated code.md`
## Delivery Tracker
| # | Task ID | Status | Key dependency / next step | Owners | Task Definition |
| --- | --- | --- | --- | --- | --- |
| 1 | CLI-AIGUARD-001 | TODO | SCANNER-AIGUARD-006 | CLI Guild | Add `guard run` command with policy file input, base/head refs, and sealed mode flags; wire to Scanner endpoint. |
| 2 | CLI-AIGUARD-002 | TODO | CLI-AIGUARD-001 | CLI Guild | Implement deterministic output renderers for JSON, SARIF, and GitLab formats. |
| 3 | CLI-AIGUARD-003 | TODO | CLI-AIGUARD-002 | CLI Guild | Add golden fixtures and tests for guard outputs; validate ordering, timestamps, and ASCII-only output. |
| 4 | CLI-AIGUARD-004 | TODO | CLI-AIGUARD-002 | CLI Guild | Update CLI help and error codes; sync docs via `SPRINT_20260112_010_DOCS_ai_code_guard_docs.md`. |
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-01-14 | Sprint created; awaiting staffing. | Planning |
## Decisions & Risks
- Decide whether `guard run` is core CLI or a plugin command; impacts packaging and offline kit contents.
- Risk: SARIF schema mapping must align with Integrations GitHub code scanning requirements.
## Next Checkpoints
- 2026-01-19: CLI flag review with Scanner owners.
- 2026-01-24: SARIF format validation with Integrations owners.

42
docs/implplan/SPRINT_20260112_010_CLI_unknowns_grey_queue_cli.md
View File

@@ -1,42 +0,0 @@
# Sprint 20260112_010_CLI - Unknowns Grey Queue CLI Parity
## Topic & Scope
- Close the CLI gap for grey queue outcomes so operators can view fingerprints, triggers, and next actions without the UI.
- Align CLI verbs with the Unknowns runbook (summary/show/proof/export/triage) and keep outputs deterministic.
- Wire CLI to the policy unknowns API and new fields introduced by the grey queue determinization work.
- Owning directory: src/Cli/StellaOps.Cli; evidence includes command handlers, tests, and runbook updates.
- **Working directory:** `src/Cli`.
## Dependencies & Concurrency
- Depends on `docs/implplan/SPRINT_20260112_004_POLICY_unknowns_determinization_greyqueue.md` for unknowns schema fields and policy API updates.
- CC 20260112_010 remains independent of other sprints aside from explicit dependencies.
## Documentation Prerequisites
- `src/Cli/AGENTS.md`
- `docs/modules/cli/architecture.md`
- `docs/operations/unknowns-queue-runbook.md`
- `docs/api/unknowns-api.md`
## Delivery Tracker
| # | Task ID | Status | Key dependency / next step | Owners | Task Definition |
| --- | --- | --- | --- | --- | --- |
| 1 | CLI-UNK-001 | DONE | Policy API fields | CLI Guild - Team | Add `stella unknowns summary` and `stella unknowns show` with fingerprint, triggers, next_actions, and evidence refs. |
| 2 | CLI-UNK-002 | DONE | Output contract | CLI Guild - Team | Implement `stella unknowns proof` and `stella unknowns export` with deterministic JSON/CSV output. |
| 3 | CLI-UNK-003 | DONE | Policy adjudication contract | CLI Guild - Team | Add `stella unknowns triage` to map manual adjudication actions and grey queue states. |
| 4 | CLI-UNK-004 | TODO | Docs sync | CLI Guild - Team | Update `docs/operations/unknowns-queue-runbook.md` and CLI reference to match actual verbs and flags. |
| 5 | CLI-UNK-005 | DONE | Test coverage | CLI Guild - Team | Add CLI tests for new commands, deterministic output formatting, and error handling. |
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-01-14 | Sprint created; awaiting staffing. | Planning |
| 2026-01-15 | CLI-UNK-001: Added `stella unknowns summary` (band counts) and `stella unknowns show` (detail with fingerprint, triggers, next_actions, conflict info). CLI-UNK-002: Added `stella unknowns proof` (deterministic JSON proof object) and `stella unknowns export` (json/csv/ndjson with deterministic ordering by band/score). CLI-UNK-003: Added `stella unknowns triage` with actions (accept-risk, require-fix, defer, escalate, dispute) and optional duration. Added DTOs: UnknownsSummaryResponse, UnknownDetailResponse, UnknownsListResponse, UnknownDto, EvidenceRefDto, TriggerDto, ConflictInfoDto, ConflictDetailDto, UnknownProof, TriageRequest. | Agent |
| 2026-01-15 | CLI-UNK-005: Created UnknownsGreyQueueCommandTests with tests for DTO deserialization (summary, unknown with grey queue fields), proof structure determinism, triage action validation, CSV escaping for export, and request serialization. | Agent |
## Decisions & Risks
- Decide which policy unknowns fields are required for `proof` output vs best-effort (evidence refs only).
- Confirm how `triage` maps to policy states (Disputed vs ManualReviewRequired) and required inputs.
## Next Checkpoints
- 2026-01-16: CLI and Policy contract review (CLI Guild, Policy Guild).
- 2026-01-20: Runbook alignment review with Ops.

47
docs/implplan/SPRINT_20260112_010_DOCS_ai_code_guard_docs.md
View File

@@ -1,47 +0,0 @@
# Sprint SPRINT_20260112_010_DOCS_ai_code_guard_docs · AI Code Guard docs and benchmarks
## Topic & Scope
- Document the AI code guard concept, policy matrix, and override workflow with links to Scanner, Policy, CLI, and Integrations surfaces.
- Add high-level positioning updates in key features and architecture references; include cross-links from the legacy index file.
- Publish deterministic benchmark fixtures (policy YAML and CI snippets) and reference them from the detailed docs.
- Capture evidence expectations and determinism constraints for offline use.
- **Working directory:** `docs`.
## Dependencies & Concurrency
- Can run in parallel with implementation sprints; update links as endpoints stabilize.
- Depends on advisory approval for AI code guard naming and scope.
## Documentation Prerequisites
- `docs/README.md`
- `docs/ARCHITECTURE_OVERVIEW.md`
- `docs/07_HIGH_LEVEL_ARCHITECTURE.md`
- `docs/modules/platform/architecture-overview.md`
- `docs/modules/scanner/architecture.md`
- `docs/modules/policy/architecture.md`
- `docs/modules/cli/architecture.md`
- `docs/modules/ui/architecture.md`
- `docs-archived/product/advisories/14-Jan-2026 - Security gaps in AI-generated code.md`
## Delivery Tracker
| # | Task ID | Status | Key dependency / next step | Owners | Task Definition |
| --- | --- | --- | --- | --- | --- |
| 1 | DOCS-AIGUARD-001 | DONE | - | Docs Guild | Update `docs/key-features.md` and `docs/ARCHITECTURE_OVERVIEW.md` with AI code guard positioning and cross-links to detailed docs. |
| 2 | DOCS-AIGUARD-002 | DONE | DOCS-AIGUARD-001 | Docs Guild | Add detailed docs: `docs/modules/scanner/operations/ai-code-guard.md` and `docs/modules/policy/guides/ai-code-guard-policy.md` (checks, evidence, policy matrix, override rules). |
| 3 | DOCS-AIGUARD-003 | DONE | DOCS-AIGUARD-002 | Docs Guild | Add deterministic fixtures under `docs/benchmarks/ai-code-guard/` for `.stellaops.yml` and CI snippets; link from docs. |
| 4 | DOCS-AIGUARD-004 | DONE | DOCS-AIGUARD-002 | Docs Guild | Update flow and CLI references: `docs/flows/10-cicd-gate-flow.md`, `docs/API_CLI_REFERENCE.md`, `docs/flows/06-export-flow.md`. |
| 5 | DOCS-AIGUARD-005 | DONE | DOCS-AIGUARD-004 | Docs Guild | Archive advisory to `docs-archived/product/advisories/` and add supersedes or extends notes if overlaps found. |
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-01-14 | Sprint created; awaiting staffing. | Planning |
| 2026-01-14 | Completed AI code guard doc sync, fixtures, flow updates, and advisory archive. | Planning |
## Decisions & Risks
- Decide whether "AI code guard" is a Scanner feature name or a Policy gate name; docs must match product naming.
- Confirm license policy matrix defaults (allow/review/block lists) and override roles before publishing docs.
- Risk: endpoints and CLI flags may change during implementation; mark docs as draft until API contracts land.
## Next Checkpoints
- 2026-01-18: Docs outline review with Scanner and Policy owners.
- 2026-01-24: Cross-link validation and fixture review.

44
docs/implplan/SPRINT_20260112_010_DOCS_cli_command_name_sweep.md
View File

@@ -1,44 +0,0 @@
# Sprint SPRINT_20260112_010_DOCS_cli_command_name_sweep · CLI command name sweep analysis
## Topic & Scope
- Confirm the canonical CLI command name is `stella` across product docs, flows, and operator guides.
- Inventory all references to `stellaops` in docs and classify each as: must replace, keep as legacy alias, or ambiguous.
- Produce a deterministic sweep report listing file paths, context, and recommended action.
- Define follow-up tasks for replacements and exception handling without performing implementation in this sprint.
- **Working directory:** `docs`.
## Dependencies & Concurrency
- No runtime dependencies; can run in parallel with other docs sprints.
- Requires coordination with CLI guild to confirm any legacy alias policy.
## Documentation Prerequisites
- `docs/README.md`
- `docs/ARCHITECTURE_OVERVIEW.md`
- `docs/modules/cli/architecture.md`
- `docs/API_CLI_REFERENCE.md`
- `docs/flows/10-cicd-gate-flow.md`
- `docs/flows/06-export-flow.md`
## Delivery Tracker
| # | Task ID | Status | Key dependency / next step | Owners | Task Definition |
| --- | --- | --- | --- | --- | --- |
| 1 | DOCS-CLISWEEP-001 | DONE | - | Docs Guild | Inventory all `stellaops` command references in `docs/**` and capture location, snippet, and context. |
| 2 | DOCS-CLISWEEP-002 | DONE | DOCS-CLISWEEP-001 | Docs Guild | Classify each reference as replace, keep (legacy alias), or ambiguous; note rationale and owners. |
| 3 | DOCS-CLISWEEP-003 | DONE | DOCS-CLISWEEP-002 | Docs Guild | Publish a sweep report under `docs/technical/reviews/cli-command-name-sweep-2026-01-14.md` with deterministic ordering. |
| 4 | DOCS-CLISWEEP-004 | DONE | DOCS-CLISWEEP-003 | Docs Guild | Draft follow-up sprint tasks for replacements and exceptions (no edits performed in this sprint). |
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-01-14 | Sprint created; awaiting staffing. | Planning |
| 2026-01-14 | DOCS-CLISWEEP-001: Inventoried stellaops references. Found 140 CLI command uses vs 984 canonical stella uses. Identified main locations in benchmark docs. | Agent |
| 2026-01-14 | DOCS-CLISWEEP-002: Classified references into 3 categories: Replace (CLI commands ~25), Keep (namespaces/headers ~100+), Ambiguous (domains/product names). | Agent |
| 2026-01-14 | DOCS-CLISWEEP-003: Published sweep report to docs/technical/reviews/cli-command-name-sweep-2026-01-14.md with methodology, findings, and recommendations. | Agent |
| 2026-01-14 | DOCS-CLISWEEP-004: Drafted 4 follow-up tasks in sweep report: CLISWEEP-REPLACE-001, CLISWEEP-ALIAS-002, CLISWEEP-DOC-003, CLISWEEP-VERIFY-004. | Agent |
## Decisions & Risks
- Decision: confirm whether `stellaops` is a supported legacy alias in any documentation or packaging context.
- Risk: replacing command names in examples may diverge from shipped binaries if alias support exists; require CLI owner sign-off.
## Next Checkpoints
- 2026-01-16: CLI command naming alignment review with CLI guild.

38
docs/implplan/SPRINT_20260112_010_FE_ai_code_guard_console.md
View File

@@ -1,38 +0,0 @@
# Sprint SPRINT_20260112_010_FE_ai_code_guard_console · AI Code Guard console UX
## Topic & Scope
- Add UI surfaces for AI code guard status, evidence summaries, and waiver requests.
- Provide inline badge states (Pass/Review/Block) and detail panels with line refs, similarity scores, and license verdicts.
- Ensure offline-friendly rendering and deterministic UI outputs for evidence exports.
- **Working directory:** `src/Web/StellaOps.Web`.
## Dependencies & Concurrency
- Depends on Scanner guard endpoints and payloads from `SPRINT_20260112_010_SCANNER_ai_code_guard_core.md`.
- Depends on Policy override semantics from `SPRINT_20260112_010_POLICY_ai_code_guard_policy.md`.
- Can run in parallel with CLI and Integrations once API shapes are stable.
## Documentation Prerequisites
- `src/Web/StellaOps.Web/AGENTS.md`
- `docs/modules/ui/architecture.md`
- `docs/modules/platform/architecture-overview.md`
- `docs-archived/product/advisories/14-Jan-2026 - Security gaps in AI-generated code.md`
## Delivery Tracker
| # | Task ID | Status | Key dependency / next step | Owners | Task Definition |
| --- | --- | --- | --- | --- | --- |
| 1 | FE-AIGUARD-001 | TODO | SCANNER-AIGUARD-006 | Web Guild | Add AI code guard badge and summary panels for scan/PR views; include counts and status. |
| 2 | FE-AIGUARD-002 | TODO | POLICY-AIGUARD-002 | Web Guild | Implement waiver request flow (issue link, expiry, approver role) with audit preview. |
| 3 | FE-AIGUARD-003 | TODO | FE-AIGUARD-001 | Web Guild | Add detail panel with line refs, similarity evidence, and license verdicts; support export links. |
| 4 | FE-AIGUARD-004 | TODO | FE-AIGUARD-003 | Web Guild | Add unit and e2e tests for AI code guard views and waiver flow. |
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-01-14 | Sprint created; awaiting staffing. | Planning |
## Decisions & Risks
- Decide where AI code guard surfaces live in navigation (scan detail, PR view, or new Guard page).
- Risk: waiver flows require Authority scope mapping; confirm roles before UI wiring.
## Next Checkpoints
- 2026-01-20: UX wireframe review with Docs and Security owners.

38
docs/implplan/SPRINT_20260112_010_FE_binary_diff_explain_panel.md
View File

@@ -1,38 +0,0 @@
# Sprint 20260112-010-FE-binary-diff-explain-panel - Binary Diff Explain Panel
## Topic & Scope
- Add a binary diff explain panel to the triage evidence UI and wire it to evidence bundle data.
- Current state evidence: Evidence panel components and models do not include binary diff tab or fields (`src/Web/StellaOps.Web/src/app/features/triage/components/evidence-panel/index.ts`, `src/Web/StellaOps.Web/src/app/features/triage/models/evidence.model.ts`).
- Evidence to produce: UI component, model updates, mock/test data updates, and UI guide update.
- **Working directory:** `src/Web/StellaOps.Web`.
## Dependencies & Concurrency
- Depends on `SPRINT_20260112_009_SCANNER_binary_diff_bundle_export` for API payloads.
- Parallel safe with evidence-card UI sprint if components remain isolated.
## Documentation Prerequisites
- `docs/README.md`
- `docs/07_HIGH_LEVEL_ARCHITECTURE.md`
- `docs/modules/platform/architecture-overview.md`
- `docs/modules/ui/architecture.md`
- `docs/modules/vuln-explorer/README.md`
## Delivery Tracker
| # | Task ID | Status | Key dependency / next step | Owners | Task Definition |
| --- | --- | --- | --- | --- | --- |
| 1 | BINDIFF-FE-001 | TODO | BINDIFF-SCAN-001 | UI Guild | Add binary diff fields to evidence models and API client. |
| 2 | BINDIFF-FE-002 | TODO | BINDIFF-FE-001 | UI Guild | Implement binary diff explain component and wire into evidence panel tabs. |
| 3 | BINDIFF-FE-003 | TODO | BINDIFF-FE-002 | QA Guild | Add component tests and update mock data for evidence panel. |
| 4 | BINDIFF-FE-004 | TODO | BINDIFF-FE-002 | Docs Guild | Update `docs/UI_GUIDE.md` with binary diff explain panel usage. |
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-01-14 | Sprint created; awaiting staffing. | Planning |
## Decisions & Risks
- Define UX affordances for large binary diffs (pagination, collapse, or download).
- Ensure evidence panel handles missing binary diff data without errors.
## Next Checkpoints
- TBD (set once staffed).

37
docs/implplan/SPRINT_20260112_010_INTEGRATIONS_ai_code_guard_annotations.md
View File

@@ -1,37 +0,0 @@
# Sprint SPRINT_20260112_010_INTEGRATIONS_ai_code_guard_annotations · AI Code Guard annotations
## Topic & Scope
- Extend SCM annotation payloads to carry AI code guard status, counts, and evidence refs.
- Add status checks and inline annotations for GitHub and GitLab integrations.
- Ensure ASCII-only output and deterministic ordering in comments and checks.
- **Working directory:** `src/Integrations`.
## Dependencies & Concurrency
- Depends on Scanner guard evidence from `SPRINT_20260112_010_SCANNER_ai_code_guard_core.md`.
- Depends on base SCM annotation plumbing in `SPRINT_20260112_006_INTEGRATIONS_scm_annotations.md`.
- Can run in parallel with CLI and UI sprints once payload contract is defined.
## Documentation Prerequisites
- `src/Integrations/AGENTS.md`
- `docs/architecture/integrations.md`
- `docs/modules/platform/architecture-overview.md`
- `docs-archived/product/advisories/14-Jan-2026 - Security gaps in AI-generated code.md`
## Delivery Tracker
| # | Task ID | Status | Key dependency / next step | Owners | Task Definition |
| --- | --- | --- | --- | --- | --- |
| 1 | INTEGRATIONS-AIGUARD-001 | TODO | SCANNER-AIGUARD-006 | Integrations Guild | Define annotation payload fields for AI code guard (status, counts, evidence URIs, SARIF link). |
| 2 | INTEGRATIONS-AIGUARD-002 | TODO | INTEGRATIONS-AIGUARD-001 | Integrations Guild | Implement GitHub and GitLab status checks and inline annotations for AI guard findings. |
| 3 | INTEGRATIONS-AIGUARD-003 | TODO | INTEGRATIONS-AIGUARD-002 | Integrations Guild | Add deterministic tests for annotation mapping and error handling. |
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-01-14 | Sprint created; awaiting staffing. | Planning |
## Decisions & Risks
- Decide if annotations should embed SARIF or link to an artifact; impacts SCM payload size limits.
- Risk: SCM rate limits may require batching; align with existing annotation throttling rules.
## Next Checkpoints
- 2026-01-20: Annotation contract review with Scanner owners.

43
docs/implplan/SPRINT_20260112_010_POLICY_ai_code_guard_policy.md
View File

@@ -1,43 +0,0 @@
# Sprint SPRINT_20260112_010_POLICY_ai_code_guard_policy · AI Code Guard policy signals
## Topic & Scope
- Add Policy DSL signals and helpers for AI code guard evidence (secrets, unsafe APIs, similarity, license verdicts, overrides).
- Define policy matrix evaluation for allow/review/block outcomes and ensure deterministic explain traces.
- Provide policy examples and tests that align with Scanner evidence outputs and Attestor predicates.
- **Working directory:** `src/Policy`.
## Dependencies & Concurrency
- Depends on Scanner evidence model from `SPRINT_20260112_010_SCANNER_ai_code_guard_core.md`.
- Docs updates tracked in `SPRINT_20260112_010_DOCS_ai_code_guard_docs.md`.
- Can run in parallel with CLI and UI sprints after signal names stabilize.
## Documentation Prerequisites
- `src/Policy/AGENTS.md`
- `docs/README.md`
- `docs/ARCHITECTURE_OVERVIEW.md`
- `docs/modules/platform/architecture-overview.md`
- `docs/modules/policy/architecture.md`
- `docs/modules/policy/guides/dsl.md`
- `docs-archived/product/advisories/14-Jan-2026 - Security gaps in AI-generated code.md`
## Delivery Tracker
| # | Task ID | Status | Key dependency / next step | Owners | Task Definition |
| --- | --- | --- | --- | --- | --- |
| 1 | POLICY-AIGUARD-001 | TODO | SCANNER-AIGUARD-006 | Policy Guild | Add AI code guard signals to the Policy DSL signal context (guard status, counts, similarity, license verdicts, override metadata). |
| 2 | POLICY-AIGUARD-002 | TODO | POLICY-AIGUARD-001 | Policy Guild | Implement matrix helpers for allow/review/block mapping and deterministic explain trace annotations. |
| 3 | POLICY-AIGUARD-003 | TODO | POLICY-AIGUARD-001 | Policy Guild | Add policy pack examples and fixtures covering allow/review/block outcomes and override expiry. |
| 4 | POLICY-AIGUARD-004 | TODO | POLICY-AIGUARD-002 | Policy Guild | Add deterministic unit and golden tests for AI code guard signal evaluation. |
| 5 | POLICY-AIGUARD-005 | TODO | POLICY-AIGUARD-002 | Policy Guild | Wire guard evidence into policy explain exports so CLI and UI can surface reasons. |
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-01-14 | Sprint created; awaiting staffing. | Planning |
## Decisions & Risks
- Decide how override roles map to existing Authority scopes and Policy exception flows; document in policy guide.
- Risk: overlap with existing secret or license rules may double-count evidence; align signal naming to avoid collisions.
## Next Checkpoints
- 2026-01-18: Signal naming review with Scanner owners.
- 2026-01-23: Policy matrix review with Security and Docs owners.

47
docs/implplan/SPRINT_20260112_010_SCANNER_ai_code_guard_core.md
View File

@@ -1,47 +0,0 @@
# Sprint SPRINT_20260112_010_SCANNER_ai_code_guard_core · AI Code Guard core pipeline
## Topic & Scope
- Implement the AI code guard pipeline in Scanner to evaluate changed hunks for secrets, unsafe API use, snippet similarity, and license diffs.
- Produce deterministic evidence artifacts with hunk hashes, finding summaries, and rule versions for Policy and Attestor.
- Package allowlist and denylist corpora for offline use; enforce stable ordering and deterministic thresholds.
- Expose guard execution via Scanner WebService endpoints and SARIF-ready outputs for downstream CLI/SCM integrations.
- **Working directory:** `src/Scanner`.
## Dependencies & Concurrency
- Depends on Policy signals (`SPRINT_20260112_010_POLICY_ai_code_guard_policy.md`) and Attestor predicate registration (`SPRINT_20260112_010_ATTESTOR_ai_code_guard_predicate.md`).
- Integrations annotation delivery depends on `SPRINT_20260112_006_INTEGRATIONS_scm_annotations.md`.
- Can run in parallel with CLI and UI sprints once endpoint contracts are agreed.
## Documentation Prerequisites
- `src/Scanner/AGENTS.md`
- `docs/README.md`
- `docs/ARCHITECTURE_OVERVIEW.md`
- `docs/modules/platform/architecture-overview.md`
- `docs/modules/scanner/architecture.md`
- `docs/modules/policy/architecture.md`
- `docs-archived/product/advisories/14-Jan-2026 - Security gaps in AI-generated code.md`
## Delivery Tracker
| # | Task ID | Status | Key dependency / next step | Owners | Task Definition |
| --- | --- | --- | --- | --- | --- |
| 1 | SCANNER-AIGUARD-001 | TODO | - | Scanner Guild | Define AI code guard options (thresholds, license matrix, corpora paths) and validate config with deterministic defaults. |
| 2 | SCANNER-AIGUARD-002 | TODO | SCANNER-AIGUARD-001 | Scanner Guild | Implement diff and hunk hashing pipeline to classify new vs pre-existing findings; emit stable hunk IDs. |
| 3 | SCANNER-AIGUARD-003 | TODO | SCANNER-AIGUARD-001 | Scanner Guild | Implement unsafe API scan for changed hunks using existing capability scanners; produce file, line, and snippet evidence. |
| 4 | SCANNER-AIGUARD-004 | TODO | SCANNER-AIGUARD-001 | Scanner Guild | Implement snippet similarity checker with allowlist and denylist corpora; enforce deterministic similarity scoring and threshold outputs. |
| 5 | SCANNER-AIGUARD-005 | TODO | SCANNER-AIGUARD-001 | Scanner Guild | Implement license hygiene check using SBOM diff; map license evidence to allow/review/block verdicts. |
| 6 | SCANNER-AIGUARD-006 | TODO | SCANNER-AIGUARD-002 | Scanner Guild | Emit AI code guard evidence payloads (JSON + DSSE-ready) and include SARIF output adapters for CLI/SCM. |
| 7 | SCANNER-AIGUARD-007 | TODO | SCANNER-AIGUARD-006 | Scanner Guild | Add deterministic tests and fixtures for hunk hashing, similarity scoring, and license verdicts. |
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-01-14 | Sprint created; awaiting staffing. | Planning |
## Decisions & Risks
- Decide on similarity algorithm (MinHash/SimHash/Jaccard) and corpus packaging format; lock before fixtures are published.
- Risk: scanning source hunks may require language-specific normalizers; define normalization rules to keep hashes stable.
- Risk: license matrix enforcement may conflict with existing Policy packs; align with Policy owners before enabling blocking defaults.
## Next Checkpoints
- 2026-01-18: Guard evidence model review with Policy and Attestor owners.
- 2026-01-24: Similarity corpus packaging review with Offline Kit owners.

48
docs/implplan/SPRINT_20260112_011_CLI_evidence_card_remediate_cli.md
View File

@@ -1,48 +0,0 @@
# Sprint 20260112-011-CLI-evidence-card-remediate-cli - Evidence Card and Remediation CLI
## Topic & Scope
- Add CLI support for exporting and verifying the single-file evidence card so operators can fetch deterministic receipts without the UI.
- Add CLI remediation action to request PR or ticket creation and print the returned link and metadata.
- Current state evidence: evidence CLI only exports and verifies bundles (`src/Cli/StellaOps.Cli/Commands/EvidenceCommandGroup.cs`); `remediate` only returns guidance (`src/Cli/StellaOps.Cli/Commands/CommandFactory.cs`).
- Evidence to produce: new CLI commands, JSON output schema, and tests for command parsing and output.
- **Working directory:** `src/Cli/StellaOps.Cli`.
## Dependencies & Concurrency
- Depends on evidence card format and API (`docs/implplan/SPRINT_20260112_004_LB_evidence_card_core.md`, `docs/implplan/SPRINT_20260112_005_BE_evidence_card_api.md`).
- Depends on remediation PR generator API (`docs/implplan/SPRINT_20260112_007_BE_remediation_pr_generator.md`).
- Parallel safe with UI sprints; no shared DB migrations.
## Documentation Prerequisites
- `docs/README.md`
- `docs/07_HIGH_LEVEL_ARCHITECTURE.md`
- `docs/modules/platform/architecture-overview.md`
- `docs/modules/cli/architecture.md`
- `docs/modules/advisory-ai/architecture.md`
- `docs/modules/cli/guides/commands/evidence-bundle-format.md`
## Delivery Tracker
| # | Task ID | Status | Key dependency / next step | Owners | Task Definition |
| --- | --- | --- | --- | --- | --- |
| 1 | EVPCARD-CLI-001 | DONE | SPRINT_20260112_005_BE_evidence_card_api.md | CLI Guild | Add `stella evidence card export` to fetch and write evidence-card files with deterministic naming and content type handling. |
| 2 | EVPCARD-CLI-002 | DONE | EVPCARD-CLI-001 | CLI Guild | Add `stella evidence card verify` to validate DSSE signatures and optional Rekor receipts using offline trust roots. |
| 3 | REMPR-CLI-001 | DONE | SPRINT_20260112_007_BE_remediation_pr_generator.md | CLI Guild | Add `stella remediate open-pr` to call the remediation PR endpoint with repo/branch options and emit PR URL, branch, and status. |
| 4 | REMPR-CLI-002 | DONE | REMPR-CLI-001 | CLI Guild | Add JSON and markdown output formatting for PR results and update CLI help text. |
| 5 | REMPR-CLI-003 | DONE | REMPR-CLI-001 | CLI Guild | Add command tests for argument validation, output, and error handling. |
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-01-14 | Sprint created; awaiting staffing. | Planning |
| 2026-01-14 | EVPCARD-CLI-001: Added `stella evidence card export` command with --compact, --output, --format options. Implemented HandleCardExportAsync with progress spinner, response header parsing (X-Content-Digest, X-Evidence-Card-Version, X-Rekor-Log-Index), file writing, and summary table output. | Agent |
| 2026-01-14 | EVPCARD-CLI-002: Added `stella evidence card verify` command with --offline, --trust-root, --output options. Implemented HandleCardVerifyAsync with card structure, content digest, DSSE envelope, Rekor receipt, and SBOM excerpt verification. Added CardVerificationResult record and helper methods. | Agent |
| 2026-01-14 | REMPR-CLI-001: Added `stella advise open-pr` command. Calls POST /v1/advisory-ai/remediation/apply with plan-id and scm-type. Supports table/json/markdown output formats. Shows PR URL, branch, status, and PR body. Uses Spectre.Console for formatting. | Agent |
| 2026-01-15 | REMPR-CLI-003: Verified OpenPrCommandTests.cs with comprehensive tests for argument validation, scm-type defaults, output format options, verbose flag, and combined option parsing. All tests pass. | Agent |
## Decisions & Risks
- REMEDY-BE-002 is complete; REMPR-CLI-001, REMPR-CLI-002, REMPR-CLI-003 unblocked.
- Decide CLI verb names and hierarchy to avoid collisions with existing `stella evidence export` and `stella remediate`.
- Define required inputs for PR creation (integration id vs explicit repo URL) and how CLI resolves defaults.
- Confirm offline verification behavior when Rekor receipts are absent or optional.
## Next Checkpoints
- TBD (set once staffed).

43
docs/implplan/SPRINT_20260112_011_FE_policy_unknowns_queue_integration.md
View File

@@ -1,43 +0,0 @@
# Sprint 20260112_011_FE - Policy Unknowns Grey Queue UI Integration
## Topic & Scope
- Point the Unknowns UI to the policy unknowns API so grey queue results are visible with fingerprints, triggers, and next actions.
- Add UI affordances for manual adjudication and disputed evidence while keeping ordering deterministic.
- Provide navigation from the Unknowns queue to determinization review context for grey queue items.
- Owning directory: src/Web/StellaOps.Web; evidence includes API client updates, UI components, tests, and docs updates.
- **Working directory:** `src/Web/StellaOps.Web`.
## Dependencies & Concurrency
- Depends on `docs/implplan/SPRINT_20260112_004_POLICY_unknowns_determinization_greyqueue.md` for API fields and unknowns schema updates.
- CC 20260112_011 remains independent aside from explicit dependencies.
## Documentation Prerequisites
- `src/Web/StellaOps.Web/AGENTS.md`
- `docs/modules/ui/architecture.md`
- `docs/api/unknowns-api.md`
- `docs/modules/policy/determinization-api.md`
- `docs/operations/unknowns-queue-runbook.md`
## Delivery Tracker
| # | Task ID | Status | Key dependency / next step | Owners | Task Definition |
| --- | --- | --- | --- | --- | --- |
| 1 | FE-UNK-005 | DONE | Policy API contract | Web Guild - Team | Add policy unknowns API client/models (fingerprint, triggers, next_actions, manual adjudication fields) and migrate the queue view to the policy endpoints. |
| 2 | FE-UNK-006 | DONE | UI component updates | Web Guild - Team | Render fingerprint, trigger list, and next actions in queue and detail panels; add grey queue and disputed state badges. |
| 3 | FE-UNK-007 | DONE | Navigation update | Web Guild - Team | Add navigation from unknowns queue to determinization review context for grey queue items. |
| 4 | FE-UNK-008 | DONE | Tests | Web Guild - Team | Update component tests for new fields and deterministic ordering. |
| 5 | FE-UNK-009 | TODO | Docs update | Web Guild - Team | Update UI guide or module docs with grey queue behavior and examples. |
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-01-14 | Sprint created; awaiting staffing. | Planning |
| 2026-01-15 | FE-UNK-005, FE-UNK-006: Covered by SPRINT_20260112_009_FE_unknowns_queue_ui - unknowns.models.ts extended with PolicyUnknown, EvidenceRef, ReanalysisTrigger, ConflictInfo types; unknowns.client.ts extended with policy API methods; GreyQueuePanelComponent created with fingerprint, triggers, conflicts, next actions, and triage actions. | Agent |
| 2026-01-15 | FE-UNK-007: Extended unknowns.routes.ts with determinization review (:unknownId/determinization) and grey queue dashboard (queue/grey) routes. Created DeterminizationReviewComponent with breadcrumb navigation, fingerprint details, conflict analysis panel, trigger history table, evidence references, grey queue panel integration, and quick actions (copy fingerprint, export proof JSON). Created GreyQueueDashboardComponent with summary cards, band/state filters, deterministic ordering (band priority then score descending), and review links. | Agent |
| 2026-01-15 | FE-UNK-008: Created grey-queue-dashboard.component.spec.ts with tests for grey queue filtering, deterministic ordering (band priority then score descending), band priority helper, grey queue state detection, color helpers, and conflict detection. Created determinization-review.component.spec.ts with tests for triggers sorting (most recent first), band display, observation state, conflict handling, and proof export structure. Both test suites verify deterministic ordering stability across renders. | Agent |
## Decisions & Risks
- Decide whether to unify scanner unknowns and policy unknowns views or keep separate entry points.
- Confirm UX for manual adjudication actions and the minimal detail panel fields.
## Next Checkpoints
- 2026-01-21: UI review with policy stakeholders.

43
docs/implplan/SPRINT_20260112_012_FE_remediation_pr_ui_wiring.md
View File

@@ -1,43 +0,0 @@
# Sprint 20260112-012-FE-remediation-pr-ui-wiring - Remediation PR UI Wiring
## Topic & Scope
- Extend the AI Remediate panel to open PRs or tickets and show results (PR URL, branch, status) alongside existing guidance.
- Add UI gating and configuration for SCM connections and remediation PR enablement, linking to Integrations Hub when not configured.
- Current state evidence: AI Remediate panel only exports guidance (`src/Web/StellaOps.Web/src/app/features/vex-hub/ai-remediate-panel.component.ts`); AI preferences include PR comments but no PR creation toggle (`src/Web/StellaOps.Web/src/app/features/settings/ai-preferences.component.ts`); Integrations wizard lists SCM providers without remediation wiring (`src/Web/StellaOps.Web/src/app/features/integrations/integration-wizard.component.ts`).
- Evidence to produce: UI actions, API client models, settings wiring, and component tests.
- **Working directory:** `src/Web/StellaOps.Web`.
## Dependencies & Concurrency
- Depends on remediation PR backend API and models (`docs/implplan/SPRINT_20260112_007_BE_remediation_pr_generator.md`).
- Depends on evidence card API for attachments (`docs/implplan/SPRINT_20260112_005_BE_evidence_card_api.md`).
- Parallel safe with evidence-card UI and binary-diff UI sprints if components remain isolated.
## Documentation Prerequisites
- `docs/README.md`
- `docs/07_HIGH_LEVEL_ARCHITECTURE.md`
- `docs/modules/platform/architecture-overview.md`
- `docs/modules/ui/architecture.md`
- `docs/modules/advisory-ai/architecture.md`
## Delivery Tracker
| # | Task ID | Status | Key dependency / next step | Owners | Task Definition |
| --- | --- | --- | --- | --- | --- |
| 1 | REMPR-FE-001 | DONE | SPRINT_20260112_007_BE_remediation_pr_generator.md | UI Guild | Extend Advisory AI API client and models with PR creation request/response fields (PR URL, branch, status, evidence card id). |
| 2 | REMPR-FE-002 | TODO | REMPR-FE-001 | UI Guild | Add "Open PR" action to AI Remediate panel with progress, success, and error states plus link/copy affordances. |
| 3 | REMPR-FE-003 | TODO | REMPR-FE-001 | UI Guild | Add SCM connection selector and gating message with link to Integrations Hub when no SCM connection is available. |
| 4 | REMPR-FE-004 | TODO | REMPR-FE-003 | UI Guild | Add settings toggles for remediation PR enablement and evidence-card attachment or PR comment behavior. |
| 5 | REMPR-FE-005 | TODO | REMPR-FE-002 | UI Guild | Add component tests for PR actions and update `docs/UI_GUIDE.md` with remediation PR flow. |
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-01-14 | Sprint created; awaiting staffing. | Planning |
| 2026-01-15 | REMPR-FE-001: Extended advisory-ai.models.ts with RemediationPrInfo (prId, prNumber, prUrl, branch, status, ciStatus, evidenceCardId). Added prCreationAvailable, activePr, evidenceCardId to AiRemediateResponse. Added RemediationPrCreateRequest, RemediationPrCreateResponse, RemediationPrErrorCode types. Added ScmConnectionInfo with ScmCapabilities. Added RemediationPrSettings interface. Extended AdvisoryAiApi interface with createRemediationPr, getScmConnections, getRemediationPrSettings methods. Implemented in AdvisoryAiApiHttpClient and MockAdvisoryAiClient. | Agent |
## Decisions & Risks
- Decide where PR status should surface outside the panel (triage row, evidence panel, or findings detail).
- Ensure UI respects offline mode and hides PR actions when SCM is not configured or disabled.
- Align evidence-card attachment behavior with backend defaults to avoid mismatched settings.
## Next Checkpoints
- TBD (set once staffed).

44
docs/implplan/SPRINT_20260112_012_POLICY_determinization_reanalysis_config.md
View File

@@ -1,44 +0,0 @@
# Sprint 20260112_012_POLICY - Determinization Reanalysis Configuration
## Topic & Scope
- Introduce persisted determinization config for grey queue reanalysis triggers, conflict handling, and per-environment thresholds; remove hard-coded defaults in code.
- Expose effective config via read endpoint and policy-admin write endpoint with audit trail.
- Encode best-in-class defaults (EPSS delta >= 0.2, threshold crossing, Rekor/OpenVEX/telemetry/patch-proof/DSSE changes) and add tests for binding and determinism.
- Owning directory: src/Policy; evidence includes options models, policy evaluation updates, tests, endpoints, and docs changes.
- **Working directory:** `src/Policy`.
## Dependencies & Concurrency
- Depends on `docs/implplan/SPRINT_20260112_004_POLICY_unknowns_determinization_greyqueue.md` for unknowns outcome mapping and API output fields.
- CC 20260112_012 remains independent aside from explicit dependencies.
## Documentation Prerequisites
- `src/Policy/AGENTS.md`
- `docs/modules/policy/architecture.md`
- `docs/modules/policy/determinization-api.md`
- `docs/api/unknowns-api.md`
- `docs/operations/unknowns-queue-runbook.md`
## Delivery Tracker
| # | Task ID | Status | Key dependency / next step | Owners | Task Definition |
| --- | --- | --- | --- | --- | --- |
| 1 | POLICY-CONFIG-001 | DONE | Config schema | Policy Guild - Team | Extend `DeterminizationOptions` with reanalysis triggers, conflict policy, and default values (EPSS delta >= 0.2, threshold crossing, Rekor/OpenVEX/telemetry/patch-proof/DSSE changes; tool-version trigger disabled by default). |
| 2 | POLICY-CONFIG-002 | DONE | Storage + audit | Policy Guild - Team | Add per-tenant determinization config persistence with audit trail and validation for environment thresholds. |
| 3 | POLICY-CONFIG-003 | DONE | Policy wiring | Policy Guild - Team | Replace hard-coded `DefaultEnvironmentThresholds` with effective config values in determinization evaluation. |
| 4 | POLICY-CONFIG-004 | DONE | API exposure | Policy Guild - Team | Add read endpoint for effective config and policy-admin write endpoint for updates. |
| 5 | POLICY-CONFIG-005 | DONE | Tests | Policy Guild - Team | Add tests for binding, validation, deterministic evaluation, and audit logging. |
| 6 | POLICY-CONFIG-006 | TODO | Docs update | Policy Guild - Team | Update determinization and unknowns docs with configuration schema and defaults. |
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-01-14 | Sprint created; awaiting staffing. | Planning |
| 2026-01-15 | POLICY-CONFIG-001: Extended DeterminizationOptions with ReanalysisTriggerConfig (EpssDeltaThreshold=0.2, TriggerOnThresholdCrossing/RekorEntry/VexStatusChange/RuntimeTelemetryChange/PatchProofAdded/DsseValidationChange=true, TriggerOnToolVersionChange=false), ConflictHandlingPolicy (VexReachability/StaticRuntime/BackportStatus -> RequireManualReview, VexStatus -> RequestVendorClarification, EscalationSeverityThreshold=0.85, ConflictTtlHours=48), EnvironmentThresholds (Development/Staging/Production with Relaxed/Standard/Strict presets), and ConflictAction enum. | Agent |
| 2026-01-15 | POLICY-CONFIG-005: Created DeterminizationOptionsTests with tests for default values, environment threshold presets (Relaxed/Standard/Strict), GetForEnvironment mapping (dev/stage/qa/prod variants), configuration binding from IConfiguration, ConflictAction enum completeness, and deterministic preset values. | Agent |
| 2026-01-15 | POLICY-CONFIG-002: Created IDeterminizationConfigStore interface with GetEffectiveConfigAsync, SaveConfigAsync, GetAuditHistoryAsync. Added EffectiveDeterminizationConfig, ConfigAuditInfo, ConfigAuditEntry records. Created InMemoryDeterminizationConfigStore implementation with thread-safe operations and audit trail. POLICY-CONFIG-003: Effective config store provides tenant-specific config with fallback to defaults. POLICY-CONFIG-004: Created DeterminizationConfigEndpoints with GET /api/v1/policy/config/determinization (effective), GET /defaults, GET /audit (history), PUT (update with audit), POST /validate (dry-run validation). Added validation for trigger thresholds, conflict policy, and environment thresholds. | Agent |
## Decisions & Risks
- Defaults: EPSS delta >= 0.2, trigger on threshold crossings, Rekor entry new, OpenVEX status change, runtime telemetry exploit/reachability change, binary patch proof added, DSSE validation state change; tool-version trigger available but disabled by default.
- Config exposure: read for policy viewers; write restricted to policy admin; audit trail required for all changes.
## Next Checkpoints
- 2026-01-16: Policy configuration review (Policy Guild, Platform).

40
docs/implplan/SPRINT_20260112_013_FE_determinization_config_pane.md
View File

@@ -1,40 +0,0 @@
# Sprint 20260112_013_FE - Determinization Config Pane
## Topic & Scope
- Wire the Configuration Pane to determinization config endpoints so operators can view and edit grey queue settings from the UI.
- Provide admin-gated editing of per-environment thresholds and reanalysis triggers with deterministic display and validation feedback.
- Document the UI workflow and update component tests for the new configuration section.
- Owning directory: src/Web/StellaOps.Web; evidence includes UI components, API wiring, tests, and docs updates.
- **Working directory:** `src/Web/StellaOps.Web`.
## Dependencies & Concurrency
- Depends on `docs/implplan/SPRINT_20260112_012_POLICY_determinization_reanalysis_config.md` for config read/write endpoints and defaults.
- CC 20260112_013 remains independent aside from explicit dependencies.
## Documentation Prerequisites
- `src/Web/StellaOps.Web/AGENTS.md`
- `docs/modules/ui/architecture.md`
- `docs/modules/policy/determinization-api.md`
- `docs/api/policy.md`
## Delivery Tracker
| # | Task ID | Status | Key dependency / next step | Owners | Task Definition |
| --- | --- | --- | --- | --- | --- |
| 1 | FE-CONFIG-001 | DONE | Policy config API | Web Guild - Team | Add API client/models for determinization config (effective config read + admin update). |
| 2 | FE-CONFIG-002 | DONE | UI section | Web Guild - Team | Add a Configuration Pane section for determinization thresholds and reanalysis triggers, with read-only view for non-admins. |
| 3 | FE-CONFIG-003 | DONE | Validation feedback | Web Guild - Team | Surface server-side validation errors and show effective vs overridden values per environment. |
| 4 | FE-CONFIG-004 | DONE | Tests | Web Guild - Team | Add component and service tests for config load/save and deterministic rendering. |
| 5 | FE-CONFIG-005 | TODO | Docs update | Web Guild - Team | Update UI guide or module docs with configuration workflow and screenshots. |
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-01-14 | Sprint created; awaiting staffing. | Planning |
| 2026-01-15 | FE-CONFIG-001: Created determinization-config.client.ts with ReanalysisTriggerConfig, ConflictHandlingPolicy, EnvironmentThreshold, EnvironmentThresholds, DeterminizationConfig, EffectiveConfigResponse, UpdateConfigRequest, ValidationResponse, AuditEntry, AuditHistoryResponse models. Added DeterminizationConfigClient with getEffectiveConfig, getDefaultConfig, updateConfig, validateConfig, getAuditHistory methods. Added CONFLICT_ACTION_LABELS, ENVIRONMENT_LABELS, DEFAULT_TRIGGER_CONFIG constants. FE-CONFIG-002, FE-CONFIG-003: Created DeterminizationConfigPaneComponent with reanalysis triggers section (EPSS delta threshold, toggle triggers), conflict handling policy section (conflict actions per type, escalation threshold, TTL), environment thresholds table (development/staging/production), edit mode with deep clone, validation error/warning display, save with reason requirement, metadata display (last updated, version). FE-CONFIG-004: Created determinization-config-pane.component.spec.ts with tests for config display, edit mode toggling, deep clone on edit, admin-only edit button, conflict action labels, environment labels, validation state, deterministic rendering order, and metadata display. | Agent |
## Decisions & Risks
- UI write access must align with policy admin scope; read access follows policy viewer.
- Ensure config pane changes do not conflict with offline-first deployment posture.
## Next Checkpoints
- 2026-01-21: UI and Policy config review.

45
docs/implplan/SPRINT_20260112_013_FE_witness_ui_wiring.md
View File

@@ -1,45 +0,0 @@
# Sprint 20260112_013_FE · Witness UI Wiring
## Topic & Scope
- Wire Console UI witness surfaces to real APIs (no mocks), including list, detail, verify, and export actions.
- Surface path-witness nodeHash/pathHash and runtime evidence pointers in the witness modal and vulnerability explorer.
- Add UI affordances for DSSE signature and Rekor verification status with offline-safe messaging.
- **Working directory:** `src/Web/StellaOps.Web`. Evidence: updated API client, UI components, and tests.
## Dependencies & Concurrency
- Depends on Scanner witness endpoints and payload fields from `SPRINT_20260112_004_SCANNER_path_witness_nodehash.md`.
- Depends on predicate type alignment from `SPRINT_20260112_006_ATTESTOR_path_witness_predicate.md` and contracts from `SPRINT_20260112_008_DOCS_path_witness_contracts.md`.
- UI download/export actions depend on backend endpoints for `/download` and `/export/sarif` (currently missing).
## Documentation Prerequisites
- docs/README.md
- docs/ARCHITECTURE_OVERVIEW.md
- docs/modules/platform/architecture-overview.md
- docs/modules/ui/README.md
- docs/modules/ui/architecture.md
- docs/modules/ui/implementation_plan.md
- docs/contracts/witness-v1.md
- docs/modules/vuln-explorer/architecture.md
- docs/technical/cicd/sarif-integration.md
## Delivery Tracker
| # | Task ID | Status | Key dependency / next step | Owners | Task Definition |
| --- | --- | --- | --- | --- | --- |
| 1 | FE-WIT-001 | TODO | Scanner witness endpoints | Guild - UI | Replace `WitnessMockClient` usage with real `WitnessHttpClient` wiring; align base paths and query parameters with Scanner endpoints; add error handling and unit tests. |
| 2 | FE-WIT-002 | DONE | PW-DOC-001 | Guild - UI | Extend `witness.models.ts` and view models to include `node_hashes`, `path_hash`, evidence URIs, and runtime evidence metadata; keep deterministic ordering in rendering and tests. |
| 3 | FE-WIT-003 | TODO | FE-WIT-001, FE-WIT-002 | Guild - UI | Update witness modal and vulnerability explorer views to render node hash and path hash details, evidence links, and runtime join status; update component tests. |
| 4 | FE-WIT-004 | TODO | Scanner verify endpoint | Guild - UI | Wire verify action to `/witnesses/{id}/verify`, display DSSE signature status and error details, and add unit tests. |
| 5 | FE-WIT-005 | TODO | Backend download/export endpoints | Guild - UI | Add UI actions for witness JSON download and SARIF export; show disabled states until endpoints exist; add tests and help text. |
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-01-14 | Sprint created; awaiting staffing. | Planning |
| 2026-01-15 | FE-WIT-002: Extended witness.models.ts with path witness fields: nodeHashes (array of algorithm-prefixed hashes), pathHash (blake3/sha256 prefixed), runtimeEvidence (RuntimeEvidenceMetadata with available, source, lastObservedAt, invocationCount, confirmsStatic, traceUri). Extended WitnessEvidence with evidence URIs: dsseUri, rekorUri, sbomUri, callGraphUri, attestationUri for linking to external artifacts. All fields are optional for backward compatibility. | Agent |
## Decisions & Risks
- `docs/modules/ui/implementation_plan.md` is listed as required reading but is missing; restore or update the prerequisites before work starts.
- Download/export UI depends on backend endpoints not yet present; coordinate with Scanner owners or defer FE-WIT-005.
## Next Checkpoints
- TBD: UI and API shape review with Scanner and Attestor owners.

87
docs/implplan/SPRINT_20260112_014_CLI_config_viewer.md
View File

@@ -1,87 +0,0 @@
# Sprint 20260112_014_CLI - Config Viewer (All Modules)
## Topic & Scope
- Provide unified CLI config inspection across all StellaOps modules using `stella config <path> show` (example: `stella config policy.determinization show`).
- Support `stella config list` to enumerate all supported config paths and aliases; output is deterministic and secrets are redacted.
- Cover every config SectionName defined in code plus setup/integration config prefixes used by the setup wizard.
- Owning directory: src/Cli/StellaOps.Cli; evidence includes command handlers, tests, and docs updates.
- **Working directory:** `src/Cli`.
## Dependencies & Concurrency
- Depends on `docs/implplan/SPRINT_20260112_012_POLICY_determinization_reanalysis_config.md` for policy config read endpoints.
- CC 20260112_014 remains independent aside from explicit dependencies.
## Documentation Prerequisites
- `src/Cli/AGENTS.md`
- `docs/modules/cli/architecture.md`
- `docs/api/overview.md`
- `docs/api/policy.md`
## Delivery Tracker
| # | Task ID | Status | Key dependency / next step | Owners | Task Definition |
| --- | --- | --- | --- | --- | --- |
| 1 | CLI-CONFIG-010 | DONE | Config catalog | Build a config catalog from SectionName constants and setup prefixes; define canonical CLI paths and aliases (case-insensitive, `:` and `.` interchangeable). |
| 2 | CLI-CONFIG-011 | DONE | Command surface | Add `stella config list` and `stella config <path> show` (example: `stella config policy.determinization show`). |
| 3 | CLI-CONFIG-012 | DONE | Data sources | Implement config readers for effective config (policy endpoint where available; local config file fallback). |
| 4 | CLI-CONFIG-013 | DONE | Output and redaction | Deterministic table/json output with stable ordering and redaction of secret keys. |
| 5 | CLI-CONFIG-014 | DONE | Tests | Add CLI tests for list/show behavior, alias matching, and deterministic output. |
| 6 | CLI-CONFIG-015 | TODO | Docs update | Update CLI reference docs with config list/show usage and examples. |
## Config Inventory (SectionName keys by module)
- __Libraries: Eventing, HybridLogicalClock, IssuerDirectory:Client, LazyFetchHttp, Provcache
- AdvisoryAI: AdvisoryAI:Chat, AdvisoryAI:Inference:Offline, AdvisoryAI:LlmProviders, AdvisoryAI:RateLimits
- AirGap: AirGap:BundleSigning, AirGap:Quarantine
- Attestor: Attestor:BinaryDiff, Attestor:GraphRoot, Attestor:Rekor
- BinaryIndex: BinaryIndex:Builders, BinaryIndex:FunctionExtraction, BinaryIndex:GoldenSet, BSim, Disassembly, Ghidra, Ghidriff, HybridDisassembly, Resolution, ResolutionCache, VexBridge
- Concelier: Concelier:Cache, Concelier:Epss, Concelier:Interest, Federation
- Doctor: Doctor
- EvidenceLocker: EvidenceLocker
- Excititor: AutoVex:Downgrade, Excititor:Airgap, Excititor:Evidence:Linking, Excititor:Mirror, VexSignatureVerification
- ExportCenter: ExportCenter, ExportCenter:Adapters:Trivy, ExportCenter:Distribution:Oci, ExportCenter:Encryption, Provcache:Oci
- Findings: findings:ledger, findings:ledger:airgap, findings:ledger:incident, Scoring
- Gateway: Gateway
- IssuerDirectory: IssuerDirectory
- Notifier: ChannelAdapters, InAppChannel, Notifier:AckBridge, Notifier:Correlation, Notifier:Digest, Notifier:DigestSchedule, Notifier:DigestScheduler, Notifier:Fallback, Notifier:IncidentManager, Notifier:Integrations:OpsGenie, Notifier:Integrations:PagerDuty, Notifier:Localization, Notifier:Observability:Chaos, Notifier:Observability:DeadLetter, Notifier:Observability:Metrics, Notifier:Observability:Retention, Notifier:Observability:Tracing, Notifier:OperatorOverride, Notifier:QuietHours, Notifier:Security:HtmlSanitizer, Notifier:Security:Signing, Notifier:Security:TenantIsolation, Notifier:Security:Webhook, Notifier:Simulation, Notifier:StormBreaker, Notifier:SuppressionAudit, Notifier:Tenancy:Channels, Notifier:Tenancy:Enrichment, Notifier:Tenancy:Middleware, Notifier:Tenancy:Rls, Notifier:Tenant, Notifier:Throttler, TemplateRenderer
- Notify: notify
- Orchestrator: FirstSignal, Orchestrator, Orchestrator:IncidentMode, Orchestrator:Stream
- Platform: Platform
- Plugin: PluginRegistry, Plugins
- Policy: ConfidenceWeights, Determinization, Policy:ExceptionApproval, Policy:Exceptions:Approval, Policy:Exceptions:Expiry, Policy:GateBypassAudit, PolicyDecisionAttestation, PolicyEngine, PolicyEngine:EvidenceWeightedScore, PolicyEngine:Tenancy, PolicyGates, PolicyGateway, RateLimiting, ReachabilitySignals, SmartDiff:Gates, ToolLattice, UnknownBudgets, VexSigning
- Registry: RegistryTokenService
- Replay: Replay
- Router: Gateway, GatewayNode, Router:Authority, Router:Health, Router:Node, Router:OpenApi, Router:Routing
- SbomService: RegistryHttp, RegistrySources, ScannerHttp
- Scanner: DriftAttestation, Epss, Epss:Enrichment, Epss:Ingest, Epss:Signal, scanner, Scanner:Analyzers:EntryTrace, Scanner:Analyzers:Native, Scanner:Analyzers:Secrets, scanner:concelier, Scanner:EntryTrace:Semantic, Scanner:EpssEnrichment, Scanner:FuncProof:Dsse, Scanner:FuncProof:Generation, Scanner:FuncProof:Oci, Scanner:FuncProof:Transparency, Scanner:Idempotency, Scanner:OfflineKit, scanner:proofSpine:dsse, Scanner:Reachability:PrGate, Scanner:ReachabilitySubgraph, Scanner:ReachabilityWitness, Scanner:Worker, Scanner:Worker:NativeAnalyzers, ValidationGate, VexGate
- Scheduler: Scheduler:HlcOrdering
- Signals: EvidenceNormalization, EvidenceWeightedScore, Signals, Signals:Retention, Signals:UnknownsDecay, Signals:UnknownsRescan, Signals:UnknownsScoring
- Signer: Signer:Keyless, Sigstore
- TaskRunner: TaskRunner:ApiDeprecation, TaskRunner:Client
- Telemetry: Telemetry:Incident, Telemetry:Sealed
- VexHub: VexHub
- VexLens: VexLens, VexLens:NoiseGate
- Zastava: zastava:agent, zastava:observer, zastava:runtime, zastava:webhook
## Setup/Integration Config Prefixes (from CLI setup wizard)
- authority.* (plus Authority:Plugins.* and Authority:PasswordPolicy.*)
- cache.*
- database.*
- llm.* (plus AdvisoryAI:Enabled and AdvisoryAI:LlmProviders.*)
- notify.* (plus Notify:Channels.* and Notify:Rules.*)
- registry.*
- settingsstore.*
- telemetry.*
- users.*
- vault.*
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-01-14 | Sprint created; expanded to cover all config sections and CLI path aliases. | Planning |
| 2026-01-15 | CLI-CONFIG-010/011/012/013: Created ConfigCatalog with 90+ entries covering Policy, Scanner, Notifier, Concelier, Attestor, BinaryIndex, Signals, Signer, AdvisoryAI, AirGap, Excititor, ExportCenter, Orchestrator, Scheduler, VexLens, Zastava, Platform, Authority, and Setup modules. Created ConfigCommandGroup with list/show commands. Created CommandHandlers.Config with deterministic table/json/yaml output, secret redaction, and category filtering. | Agent |
## Decisions & Risks
- Canonical path normalization: lower-case, `:` and `.` treated as separators, module prefix added when SectionName has no prefix (example: `policy.determinization`).
- Data source precedence: explicit `--config` file path, then service endpoints where available.
## Next Checkpoints
- 2026-01-20: CLI + Policy endpoint alignment review.

45
docs/implplan/SPRINT_20260112_014_CLI_witness_commands.md
View File

@@ -1,45 +0,0 @@
# Sprint 20260112_014_CLI · Witness Commands
## Topic & Scope
- Replace placeholder witness CLI handlers with real API-backed implementations for list, show, verify, and export.
- Enforce ASCII-only output and deterministic ordering for witness results.
- Provide offline-friendly verification options where possible.
- **Working directory:** `src/Cli/StellaOps.Cli`. Evidence: updated handlers, backend client, and tests.
## Dependencies & Concurrency
- Depends on Scanner witness endpoints and payload fields from `SPRINT_20260112_004_SCANNER_path_witness_nodehash.md`.
- Depends on predicate type alignment from `SPRINT_20260112_006_ATTESTOR_path_witness_predicate.md`.
- Export/download commands depend on backend endpoints for witness JSON download and SARIF export.
## Documentation Prerequisites
- docs/README.md
- docs/ARCHITECTURE_OVERVIEW.md
- docs/modules/platform/architecture-overview.md
- docs/modules/cli/README.md
- docs/modules/cli/architecture.md
- docs/modules/cli/implementation_plan.md
- docs/contracts/witness-v1.md
- docs/technical/cicd/sarif-integration.md
- docs/operations/proof-verification-runbook.md
## Delivery Tracker
| # | Task ID | Status | Key dependency / next step | Owners | Task Definition |
| --- | --- | --- | --- | --- | --- |
| 1 | CLI-WIT-001 | DONE | Scanner endpoints | Guild - CLI | Implement witness API calls in `IBackendOperationsClient` and `BackendOperationsClient` for list/get/verify; add unit tests. |
| 2 | CLI-WIT-002 | DONE | CLI-WIT-001 | Guild - CLI | Replace placeholders in `CommandHandlers.Witness.cs` with real API calls; enforce ASCII-only output and deterministic ordering; update CLI tests. |
| 3 | CLI-WIT-003 | DONE | Backend export endpoints | Guild - CLI | Implement `witness export` to download JSON/SARIF when endpoints are available; add safe fallback messaging and tests. |
| 4 | CLI-WIT-004 | DONE | CLI-WIT-001 | Guild - CLI | Implement `witness verify` to call `/witnesses/{id}/verify` and report DSSE status; add tests for error paths and offline mode behavior. |
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-01-14 | Sprint created; awaiting staffing. | Planning |
| 2026-01-14 | Added `docs/modules/cli/implementation_plan.md` to satisfy CLI charter prerequisites. | Planning |
| 2026-01-15 | CLI-WIT-001: Created WitnessModels.cs with WitnessListRequest/Response, WitnessSummary, WitnessDetailResponse (with path_hash, node_hashes, evidence_uris, predicate_type), WitnessVerifyResponse, WitnessExportFormat enum. Extended IBackendOperationsClient with ListWitnessesAsync, GetWitnessAsync, VerifyWitnessAsync, DownloadWitnessAsync. Implemented all methods in BackendOperationsClient. | Agent |
| 2026-01-15 | CLI-WIT-002/003/004: Replaced placeholder handlers in CommandHandlers.Witness.cs with real API calls. HandleWitnessShowAsync now calls GetWitnessAsync; HandleWitnessListAsync calls ListWitnessesAsync with deterministic ordering (sorted by CVE then WitnessId); HandleWitnessVerifyAsync calls VerifyWitnessAsync with ASCII-only output ([OK]/[FAIL]); HandleWitnessExportAsync calls DownloadWitnessAsync with format selection. Added ConvertToWitnessDto, ExtractPackageName, ExtractPackageVersion helpers. | Agent |
## Decisions & Risks
- Export/download depends on backend endpoints that do not yet exist; coordinate with Scanner owners or defer CLI-WIT-003.
## Next Checkpoints
- TBD: CLI and API shape review with Scanner and Attestor owners.

43
docs/implplan/SPRINT_20260112_015_SIGNER_path_witness_predicate.md
View File

@@ -1,43 +0,0 @@
# Sprint 20260112_015_SIGNER · Path Witness Predicate Registry
## Topic & Scope
- Register canonical path-witness predicate type `https://stella.ops/predicates/path-witness/v1` in Signer allowlists.
- Add alias support for `stella.ops/pathWitness@v1` and `https://stella.ops/pathWitness/v1` without breaking existing workflows.
- Extend Signer predicate classification helpers and tests for the new predicate types.
- **Working directory:** `src/Signer/StellaOps.Signer`. Evidence: updated predicate registry and tests.
## Dependencies & Concurrency
- Predicate type locked to `https://stella.ops/predicates/path-witness/v1` with aliases `stella.ops/pathWitness@v1` and `https://stella.ops/pathWitness/v1`.
- Parallel execution is safe with Attestor and Scanner once predicate naming is stable.
## Documentation Prerequisites
- docs/README.md
- docs/ARCHITECTURE_OVERVIEW.md
- docs/modules/platform/architecture-overview.md
- docs/modules/signer/README.md
- docs/modules/signer/architecture.md
- docs/modules/signer/implementation_plan.md
- docs/contracts/witness-v1.md
## Delivery Tracker
| # | Task ID | Status | Key dependency / next step | Owners | Task Definition |
| --- | --- | --- | --- | --- | --- |
| 1 | SIGNER-PW-001 | DONE | Predicate type locked | Guild - Signer | Add predicate constants for canonical and alias URIs in `PredicateTypes.cs`; update `GetAllowedPredicateTypes`, `IsReachabilityRelatedType`, and `IsAllowedPredicateType`. |
| 2 | SIGNER-PW-002 | DONE | SIGNER-PW-001 | Guild - Signer | Add or update Signer tests to validate allowed predicate lists and reachability classification for the new predicate types. |
| 3 | SIGNER-PW-003 | DONE | SIGNER-PW-001 | Guild - Signer | Update `PredicateTypes.IsStellaOpsType` and `SignerStatementBuilder.GetRecommendedStatementType` to recognize `https://stella.ops/` and `https://stella-ops.org/` URIs as StellaOps types; add Keyless signer tests for Statement v1 selection. |
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-01-14 | Sprint created; awaiting staffing. | Planning |
| 2026-01-14 | Added `docs/modules/signer/implementation_plan.md` to satisfy Signer charter prerequisites. | Planning |
| 2026-01-14 | Added task to ensure Statement type selection treats `https://stella.ops/` predicate URIs as StellaOps types. | Planning |
| 2026-01-14 | SIGNER-PW-001: Added PathWitnessCanonical, PathWitnessAlias1, PathWitnessAlias2 constants. Added IsPathWitnessType() helper. Updated IsReachabilityRelatedType() and GetAllowedPredicateTypes() to include all path witness types. | Agent |
| 2026-01-14 | SIGNER-PW-003: Updated IsStellaOpsType to recognize https://stella.ops/ and https://stella-ops.org/ URI prefixes as StellaOps types. | Agent |
| 2026-01-15 | SIGNER-PW-002: Created PredicateTypesTests.cs with comprehensive tests for IsPathWitnessType, IsReachabilityRelatedType, GetAllowedPredicateTypes, IsAllowedPredicateType, IsStellaOpsType, constant values, backward compatibility (Alias1 = StellaOpsPathWitness), no duplicates, and deterministic ordering. | Agent |
## Decisions & Risks
- Predicate allowlist changes can affect downstream verification policies; coordinate with Attestor and Policy owners.
## Next Checkpoints
- TBD: Signer predicate registry review with Attestor owners.

69
docs/implplan/SPRINT_20260112_016_CLI_attest_verify_offline.md
View File

@@ -1,69 +0,0 @@
# Sprint 20260112-016-CLI-attest-verify-offline - Offline Attestation Verification CLI
## Topic & Scope
- Implement `stella attest verify --offline` CLI command for air-gapped attestation verification.
- Current state evidence: `RekorOfflineReceiptVerifier` exists in AirGap module but no CLI exposure (`src/AirGap/StellaOps.AirGap.Importer/Validation/RekorOfflineReceiptVerifier.cs`).
- Evidence to produce: CLI command implementation, bundled verification script generation, and golden test fixtures.
- **Working directory:** `src/Cli`.
- **Compliance item:** Item 1 - Attestation caching (offline).
## Dependencies & Concurrency
- Depends on existing `RekorOfflineReceiptVerifier` and `OfflineVerifier` services.
- Parallel safe with other CLI sprints; no shared DB migrations.
## Documentation Prerequisites
- `docs/README.md`
- `docs/modules/attestor/architecture.md`
- `docs/modules/airgap/guides/portable-evidence-bundle-verification.md`
- `docs/modules/cli/guides/commands/attest.md`
## Delivery Tracker
| # | Task ID | Status | Key dependency / next step | Owners | Task Definition |
| --- | --- | --- | --- | --- | --- |
| 1 | ATTEST-CLI-001 | TODO | None | CLI Guild | Add `AttestCommandGroup.cs` with `verify` subcommand skeleton. |
| 2 | ATTEST-CLI-002 | TODO | ATTEST-CLI-001 | CLI Guild | Implement `--offline` flag with bundle path input, checkpoint path, and trust root options. |
| 3 | ATTEST-CLI-003 | TODO | ATTEST-CLI-002 | CLI Guild | Wire `RekorOfflineReceiptVerifier` for Merkle proof validation without network. |
| 4 | ATTEST-CLI-004 | TODO | ATTEST-CLI-002 | CLI Guild | Wire `OfflineVerifier` for DSSE envelope and org signature validation. |
| 5 | ATTEST-CLI-005 | TODO | ATTEST-CLI-003 | CLI Guild | Add JSON/text output formatters for verification results (pass/fail + details). |
| 6 | ATTEST-CLI-006 | TODO | ATTEST-CLI-004 | CLI Guild | Generate `VERIFY.md` script in exported bundles with sha256 + signature chain report. |
| 7 | ATTEST-CLI-007 | TODO | ATTEST-CLI-005 | Testing Guild | Create golden test fixtures for cross-platform bundle verification. |
| 8 | ATTEST-CLI-008 | TODO | ATTEST-CLI-007 | Testing Guild | Add determinism tests verifying identical results across Windows/Linux/macOS. |
| 9 | ATTEST-CLI-009 | TODO | ATTEST-CLI-006 | Docs Guild | Update `docs/modules/cli/guides/commands/attest.md` with verify subcommand documentation. |
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-01-15 | Sprint created for compliance readiness gap: offline attestation verification CLI. | Planning |
## Decisions & Risks
- Decide on trust root bundling format (PEM directory vs single bundle file).
- Checkpoint signature verification requires bundled public keys; document sourcing procedure.
- Cross-platform hash determinism must be validated (UTF-8 BOM handling, line endings).
## Acceptance Criteria
```bash
# Demo: Verify attestation bundle offline (Wi-Fi off)
stella attest verify --offline \
--bundle evidence.tar.gz \
--checkpoint checkpoint.sig \
--trust-root /path/to/roots/
# Expected output:
# Attestation Verification Report
# ================================
# Bundle: evidence.tar.gz
# Status: VERIFIED
#
# Checks:
# [PASS] DSSE envelope signature valid
# [PASS] Merkle inclusion proof verified (log index: 12345)
# [PASS] Checkpoint signature valid (origin: rekor.sigstore.dev)
# [PASS] Content hash matches manifest
#
# Artifact: sha256:abc123...
# Signed by: identity@example.com
# Timestamp: 2026-01-14T10:30:00Z
```
## Next Checkpoints
- TBD (set once staffed).

73
docs/implplan/SPRINT_20260112_016_CLI_sbom_verify_offline.md
View File

@@ -1,73 +0,0 @@
# Sprint 20260112-016-CLI-sbom-verify-offline - Offline SBOM Verification CLI
## Topic & Scope
- Implement `stella sbom verify` CLI command for offline signed SBOM archive verification.
- Current state evidence: SBOM export exists (`SbomExportService.cs`) but no verification CLI; signing exists in Signer module.
- Evidence to produce: CLI command, offline verification workflow, and integration with signed SBOM archive format.
- **Working directory:** `src/Cli`.
- **Compliance item:** Item 3 - Signed SBOM archives (immutable).
## Dependencies & Concurrency
- Depends on `SPRINT_20260112_016_SCANNER_signed_sbom_archive_spec` for archive format.
- Parallel safe with attestation verify sprint.
## Documentation Prerequisites
- `docs/README.md`
- `docs/modules/sbom-service/architecture.md`
- `docs/modules/signer/architecture.md`
- `docs/modules/cli/guides/commands/sbom.md`
## Delivery Tracker
| # | Task ID | Status | Key dependency / next step | Owners | Task Definition |
| --- | --- | --- | --- | --- | --- |
| 1 | SBOM-CLI-001 | TODO | None | CLI Guild | Add `SbomCommandGroup.cs` with `verify` subcommand skeleton. |
| 2 | SBOM-CLI-002 | TODO | SBOM-CLI-001 | CLI Guild | Implement `--offline` flag with archive path, trust root, and output format options. |
| 3 | SBOM-CLI-003 | TODO | SBOM-CLI-002 | CLI Guild | Implement archive extraction and manifest hash validation. |
| 4 | SBOM-CLI-004 | TODO | SBOM-CLI-003 | CLI Guild | Wire DSSE envelope verification for SBOM payload signature. |
| 5 | SBOM-CLI-005 | TODO | SBOM-CLI-004 | CLI Guild | Validate SBOM schema (SPDX/CycloneDX) against bundled JSON schemas. |
| 6 | SBOM-CLI-006 | TODO | SBOM-CLI-005 | CLI Guild | Verify tool version metadata matches expected format. |
| 7 | SBOM-CLI-007 | TODO | SBOM-CLI-006 | CLI Guild | Add JSON/HTML verification report output with pass/fail status. |
| 8 | SBOM-CLI-008 | TODO | SBOM-CLI-007 | Testing Guild | Create unit tests for archive parsing, hash validation, and signature verification. |
| 9 | SBOM-CLI-009 | TODO | SBOM-CLI-008 | Testing Guild | Create integration tests with sample signed SBOM archives. |
| 10 | SBOM-CLI-010 | TODO | SBOM-CLI-009 | Docs Guild | Update `docs/modules/cli/guides/commands/sbom.md` with verify documentation. |
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-01-15 | Sprint created for compliance readiness gap: offline SBOM verification CLI. | Planning |
## Decisions & Risks
- Archive format must align with `SPRINT_20260112_016_SCANNER_signed_sbom_archive_spec`.
- Need to bundle JSON schemas for SPDX 2.3/3.0.1 and CycloneDX 1.4-1.7 for offline validation.
- Consider Fulcio root bundling for keyless signature verification in offline mode.
## Acceptance Criteria
```bash
# Demo: Verify signed SBOM archive offline
stella sbom verify \
--archive signed-sbom-sha256-abc123-20260115.tar.gz \
--offline \
--trust-root /path/to/roots/
# Expected output:
# SBOM Verification Report
# ========================
# Archive: signed-sbom-sha256-abc123-20260115.tar.gz
# Status: VERIFIED
#
# Checks:
# [PASS] Archive integrity (all hashes match manifest)
# [PASS] DSSE envelope signature valid
# [PASS] SBOM schema valid (SPDX 2.3)
# [PASS] Tool version present (StellaOps Scanner v2027.Q1)
# [PASS] Timestamp within validity window
#
# SBOM Details:
# Format: SPDX 2.3
# Components: 142
# Artifact: sha256:abc123...
# Generated: 2026-01-14T10:30:00Z
```
## Next Checkpoints
- TBD (set once staffed).

53
docs/implplan/SPRINT_20260112_016_DOCS_blue_green_deployment.md
View File

@@ -1,53 +0,0 @@
# Sprint 20260112-016-DOCS-blue-green-deployment - Blue/Green Deployment Documentation
## Topic & Scope
- Create comprehensive blue/green deployment documentation for platform-level upgrades with evidence continuity.
- Current state evidence: Multi-tenant policy rollout exists (`docs/flows/14-multi-tenant-policy-rollout-flow.md`) but no platform-level deployment guide.
- Evidence to produce: Deployment guide, upgrade runbook, and evidence continuity procedures.
- **Working directory:** `docs/operations`.
- **Compliance item:** Item 7 - Upgrade & evidence-migration paths.
## Dependencies & Concurrency
- Depends on understanding of existing backup/restore procedures (`docs/modules/authority/operations/backup-restore.md`).
- Parallel safe with all other sprints.
## Documentation Prerequisites
- `docs/README.md`
- `docs/db/MIGRATION_STRATEGY.md`
- `docs/releases/VERSIONING.md`
- `docs/flows/13-evidence-bundle-export-flow.md`
## Delivery Tracker
| # | Task ID | Status | Key dependency / next step | Owners | Task Definition |
| --- | --- | --- | --- | --- | --- |
| 1 | BG-DOC-001 | TODO | None | Docs Guild | Create `docs/operations/blue-green-deployment.md` skeleton. |
| 2 | BG-DOC-002 | TODO | BG-DOC-001 | Docs Guild | Document blue/green environment setup (namespaces, DNS, load balancer). |
| 3 | BG-DOC-003 | TODO | BG-DOC-002 | Docs Guild | Document pre-deployment checklist (backup, evidence export, health checks). |
| 4 | BG-DOC-004 | TODO | BG-DOC-003 | Docs Guild | Document deployment sequence (deploy green, validate, switch traffic). |
| 5 | BG-DOC-005 | TODO | BG-DOC-004 | Docs Guild | Document health check timing and validation procedures. |
| 6 | BG-DOC-006 | TODO | BG-DOC-005 | Docs Guild | Document traffic switching procedure (gradual vs instant). |
| 7 | BG-DOC-007 | TODO | BG-DOC-006 | Docs Guild | Document rollback procedure with evidence preservation. |
| 8 | BG-DOC-008 | TODO | BG-DOC-007 | Docs Guild | Document evidence bundle continuity during cutover. |
| 9 | BG-DOC-009 | TODO | BG-DOC-008 | Docs Guild | Create `docs/operations/upgrade-runbook.md` with step-by-step procedures. |
| 10 | BG-DOC-010 | TODO | BG-DOC-009 | Docs Guild | Document evidence locker health checks and integrity validation. |
| 11 | BG-DOC-011 | TODO | BG-DOC-010 | Docs Guild | Document post-upgrade verification report generation. |
| 12 | BG-DOC-012 | TODO | BG-DOC-011 | DevOps Guild | Create Helm values examples for blue/green deployment. |
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-01-15 | Sprint created for compliance readiness gap: blue/green deployment documentation. | Planning |
## Decisions & Risks
- Blue/green requires double infrastructure; document cost implications.
- Database migrations must be backward-compatible (N-1 version) for safe rollback.
- Evidence bundles created during cutover may reference both environments.
## Acceptance Criteria
- Complete blue/green deployment guide with diagrams.
- Step-by-step upgrade runbook with evidence continuity focus.
- Rollback procedure that preserves all evidence integrity.
- Health check procedures specific to evidence services.
## Next Checkpoints
- TBD (set once staffed).

90
docs/implplan/SPRINT_20260112_016_SCANNER_signed_sbom_archive_spec.md
View File

@@ -1,90 +0,0 @@
# Sprint 20260112-016-SCANNER-signed-sbom-archive-spec - Signed SBOM Archive Format Specification
## Topic & Scope
- Define and implement unified signed SBOM archive format combining SBOM, signatures, metadata, and verification materials.
- Current state evidence: Evidence bundles exist (`EvidenceBundleExporter.cs`) but no SBOM-specific signed archive format.
- Evidence to produce: Format specification, exporter implementation, and documentation.
- **Working directory:** `src/Scanner`.
- **Compliance item:** Item 3 - Signed SBOM archives (immutable).
## Dependencies & Concurrency
- Depends on existing `SbomExportService` and `SignerPipeline`.
- Blocks `SPRINT_20260112_016_CLI_sbom_verify_offline`.
## Documentation Prerequisites
- `docs/README.md`
- `docs/modules/sbom-service/architecture.md`
- `docs/modules/signer/architecture.md`
- `docs/modules/attestor/bundle-format.md`
## Delivery Tracker
| # | Task ID | Status | Key dependency / next step | Owners | Task Definition |
| --- | --- | --- | --- | --- | --- |
| 1 | SBOM-SPEC-001 | TODO | None | Scanner Guild | Create `docs/modules/scanner/signed-sbom-archive-spec.md` with format specification. |
| 2 | SBOM-SPEC-002 | TODO | SBOM-SPEC-001 | Scanner Guild | Define archive structure: sbom.{spdx,cdx}.json, sbom.dsse.json, manifest.json, metadata.json, certs/, schemas/. |
| 3 | SBOM-SPEC-003 | TODO | SBOM-SPEC-002 | Scanner Guild | Implement `SignedSbomArchiveBuilder` service in Scanner module. |
| 4 | SBOM-SPEC-004 | TODO | SBOM-SPEC-003 | Scanner Guild | Capture tool versions in metadata.json (stellaOpsVersion, scannerVersion, signerVersion). |
| 5 | SBOM-SPEC-005 | TODO | SBOM-SPEC-004 | Scanner Guild | Capture source container digest (Scanner image digest) in metadata. |
| 6 | SBOM-SPEC-006 | TODO | SBOM-SPEC-005 | Scanner Guild | Add manifest.json with file inventory and SHA-256 hashes. |
| 7 | SBOM-SPEC-007 | TODO | SBOM-SPEC-006 | Signer Guild | Sign manifest as separate DSSE envelope OR include in SBOM predicate. |
| 8 | SBOM-SPEC-008 | TODO | SBOM-SPEC-007 | Scanner Guild | Bundle Fulcio root + Rekor public log for offline verification. |
| 9 | SBOM-SPEC-009 | TODO | SBOM-SPEC-008 | Scanner Guild | Generate VERIFY.md with one-click verification instructions. |
| 10 | SBOM-SPEC-010 | TODO | SBOM-SPEC-009 | Scanner Guild | Add API endpoint `GET /scans/{scanId}/exports/signed-sbom-archive`. |
| 11 | SBOM-SPEC-011 | TODO | SBOM-SPEC-010 | Testing Guild | Create unit tests for archive structure and content. |
| 12 | SBOM-SPEC-012 | TODO | SBOM-SPEC-011 | Docs Guild | Update OpenAPI spec with new export endpoint. |
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-01-15 | Sprint created for compliance readiness gap: signed SBOM archive specification. | Planning |
## Archive Format Specification
```
signed-sbom-{artifact_digest_short}-{timestamp}.tar.gz
|
+-- sbom.spdx.json # OR sbom.cdx.json (CycloneDX)
+-- sbom.dsse.json # DSSE envelope with signature
+-- manifest.json # File inventory with SHA-256 hashes
+-- metadata.json # Tool versions, timestamps, generation info
+-- certs/
| +-- signing-cert.pem # Certificate chain from signer
| +-- fulcio-root.pem # Fulcio root CA (for offline keyless verify)
+-- rekor-proof/ # Optional transparency log proof
| +-- inclusion-proof.json
| +-- checkpoint.sig
+-- schemas/ # Bundled JSON schemas for offline validation
| +-- spdx-2.3-schema.json
| +-- cyclonedx-1.7-schema.json
+-- VERIFY.md # One-click verification instructions
```
### metadata.json Schema
```json
{
"schemaVersion": "1.0.0",
"stellaOpsVersion": "2027.Q1",
"scannerVersion": "1.2.3",
"scannerDigest": "sha256:abc123...",
"signerVersion": "1.0.0",
"sbomServiceVersion": "1.1.0",
"generatedAt": "2026-01-15T12:34:56Z",
"generatedAtHlc": "...",
"input": {
"imageRef": "myregistry/app:1.0",
"imageDigest": "sha256:def456..."
},
"reproducibility": {
"deterministic": true,
"expectedDigest": "sha256:..."
}
}
```
## Decisions & Risks
- Choose between signing manifest separately vs including manifest hash in SBOM predicate.
- RFC 3161 TSA integration deferred to Phase 3 (medium-term).
- Decide compression format: tar.gz vs tar.zst (zstd preferred for smaller size).
## Next Checkpoints
- TBD (set once staffed).

89
docs/implplan/SPRINT_20260112_017_ATTESTOR_checkpoint_divergence_detection.md
View File

@@ -1,89 +0,0 @@
# Sprint 20260112-017-ATTESTOR-checkpoint-divergence-detection - Checkpoint Divergence Detection
## Topic & Scope
- Implement root hash divergence detection and mismatch alarms for Rekor checkpoints.
- Current state evidence: Checkpoint verification exists but no active monitoring for conflicting checkpoints.
- Evidence to produce: Divergence detector, monotonicity checks, and alerting integration.
- **Working directory:** `src/Attestor`.
- **Compliance item:** Item 5 - Local Rekor (transparency) mirrors.
## Dependencies & Concurrency
- Depends on `SPRINT_20260112_017_ATTESTOR_periodic_rekor_sync` for checkpoint storage.
- Parallel safe with other Attestor sprints after checkpoint store is available.
## Documentation Prerequisites
- `docs/README.md`
- `docs/modules/attestor/architecture.md`
- `docs/modules/attestor/rekor-verification-design.md`
## Delivery Tracker
| # | Task ID | Status | Key dependency / next step | Owners | Task Definition |
| --- | --- | --- | --- | --- | --- |
| 1 | DIVERGE-001 | TODO | REKOR-SYNC-002 | Attestor Guild | Create `ICheckpointDivergenceDetector` interface. |
| 2 | DIVERGE-002 | TODO | DIVERGE-001 | Attestor Guild | Implement root hash comparison at same tree size. |
| 3 | DIVERGE-003 | TODO | DIVERGE-002 | Attestor Guild | Implement monotonicity check (tree size only increases). |
| 4 | DIVERGE-004 | TODO | DIVERGE-003 | Attestor Guild | Detect rollback attempts (tree size regression). |
| 5 | DIVERGE-005 | TODO | DIVERGE-004 | Attestor Guild | Implement cross-log consistency check (primary vs mirror). |
| 6 | DIVERGE-006 | TODO | DIVERGE-005 | Attestor Guild | Add metric: `attestor.rekor_checkpoint_mismatch_total{backend,origin}`. |
| 7 | DIVERGE-007 | TODO | DIVERGE-006 | Attestor Guild | Add metric: `attestor.rekor_checkpoint_rollback_detected_total`. |
| 8 | DIVERGE-008 | TODO | DIVERGE-007 | Notify Guild | Integrate with Notify service for alert dispatch. |
| 9 | DIVERGE-009 | TODO | DIVERGE-008 | Attestor Guild | Create `CheckpointDivergenceEvent` for audit trail. |
| 10 | DIVERGE-010 | TODO | DIVERGE-009 | Testing Guild | Create unit tests for divergence detection scenarios. |
| 11 | DIVERGE-011 | TODO | DIVERGE-010 | Testing Guild | Create integration tests simulating Byzantine scenarios. |
| 12 | DIVERGE-012 | TODO | DIVERGE-011 | Docs Guild | Document divergence detection and incident response procedures. |
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-01-15 | Sprint created for compliance readiness gap: checkpoint divergence detection. | Planning |
## Technical Specification
### Divergence Detection Rules
| Check | Condition | Severity | Action |
|-------|-----------|----------|--------|
| Root mismatch | Same tree_size, different root_hash | CRITICAL | Alert + quarantine |
| Monotonicity violation | New tree_size < stored tree_size | CRITICAL | Alert + reject |
| Cross-log divergence | Primary root != mirror root at same size | WARNING | Alert + investigate |
| Stale checkpoint | Checkpoint age > threshold | WARNING | Alert |
### Alert Payload
```json
{
"eventType": "rekor.checkpoint.divergence",
"severity": "critical",
"origin": "rekor.sigstore.dev",
"treeSize": 12345678,
"expectedRootHash": "sha256:abc123...",
"actualRootHash": "sha256:def456...",
"detectedAt": "2026-01-15T12:34:56Z",
"backend": "sigstore-prod",
"description": "Checkpoint root hash mismatch detected. Possible split-view attack."
}
```
### Metrics
```
# Counter: total checkpoint mismatches
attestor_rekor_checkpoint_mismatch_total{backend="sigstore-prod",origin="rekor.sigstore.dev"} 0
# Counter: rollback attempts detected
attestor_rekor_checkpoint_rollback_detected_total{backend="sigstore-prod"} 0
# Gauge: seconds since last valid checkpoint
attestor_rekor_checkpoint_age_seconds{backend="sigstore-prod"} 120
```
## Decisions & Risks
- Define response to detected divergence: quarantine all proofs or alert-only.
- Cross-log divergence may indicate network partition vs attack.
- False positive handling for transient network issues.
## Acceptance Criteria
- Alert triggered within 1 minute of divergence detection.
- Metrics visible in Grafana dashboard.
- Audit trail for all divergence events.
- Runbook for incident response to checkpoint divergence.
## Next Checkpoints
- TBD (set once staffed).

101
docs/implplan/SPRINT_20260112_017_ATTESTOR_periodic_rekor_sync.md
View File

@@ -1,101 +0,0 @@
# Sprint 20260112-017-ATTESTOR-periodic-rekor-sync - Periodic Rekor Checkpoint Sync
## Topic & Scope
- Implement background service for periodic Rekor checkpoint and tile synchronization.
- Current state evidence: `HttpRekorTileClient` exists for on-demand fetching but no periodic sync service.
- Evidence to produce: Background sync service, local checkpoint storage, and tile caching.
- **Working directory:** `src/Attestor`.
- **Compliance item:** Item 5 - Local Rekor (transparency) mirrors.
## Dependencies & Concurrency
- Depends on existing `IRekorTileClient` implementation.
- Parallel safe with checkpoint divergence detection sprint.
## Documentation Prerequisites
- `docs/README.md`
- `docs/modules/attestor/architecture.md`
- `docs/modules/attestor/rekor-verification-design.md`
- `docs/modules/attestor/transparency.md`
## Delivery Tracker
| # | Task ID | Status | Key dependency / next step | Owners | Task Definition |
| --- | --- | --- | --- | --- | --- |
| 1 | REKOR-SYNC-001 | TODO | None | Attestor Guild | Create `IRekorCheckpointStore` interface for local checkpoint persistence. |
| 2 | REKOR-SYNC-002 | TODO | REKOR-SYNC-001 | Attestor Guild | Implement `PostgresRekorCheckpointStore` for checkpoint storage. |
| 3 | REKOR-SYNC-003 | TODO | REKOR-SYNC-002 | Attestor Guild | Create `IRekorTileCache` interface for tile storage. |
| 4 | REKOR-SYNC-004 | TODO | REKOR-SYNC-003 | Attestor Guild | Implement `FileSystemRekorTileCache` for air-gapped tile storage. |
| 5 | REKOR-SYNC-005 | TODO | REKOR-SYNC-004 | Attestor Guild | Create `RekorSyncBackgroundService` as IHostedService. |
| 6 | REKOR-SYNC-006 | TODO | REKOR-SYNC-005 | Attestor Guild | Implement periodic checkpoint fetching (configurable interval, default 5 min). |
| 7 | REKOR-SYNC-007 | TODO | REKOR-SYNC-006 | Attestor Guild | Implement incremental tile sync (only new entries since last sync). |
| 8 | REKOR-SYNC-008 | TODO | REKOR-SYNC-007 | Attestor Guild | Add checkpoint signature verification during sync. |
| 9 | REKOR-SYNC-009 | TODO | REKOR-SYNC-008 | Attestor Guild | Add metrics: `attestor.rekor_sync_checkpoint_age_seconds`, `attestor.rekor_sync_tiles_cached`. |
| 10 | REKOR-SYNC-010 | TODO | REKOR-SYNC-009 | Testing Guild | Create unit tests for sync service and stores. |
| 11 | REKOR-SYNC-011 | TODO | REKOR-SYNC-010 | Testing Guild | Create integration tests with mock Rekor server. |
| 12 | REKOR-SYNC-012 | TODO | REKOR-SYNC-011 | Docs Guild | Document sync configuration options and operational procedures. |
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-01-15 | Sprint created for compliance readiness gap: periodic Rekor checkpoint sync. | Planning |
## Technical Specification
### Checkpoint Store Schema
```sql
CREATE TABLE attestor.rekor_checkpoints (
checkpoint_id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
origin TEXT NOT NULL,
tree_size BIGINT NOT NULL,
root_hash BYTEA NOT NULL,
signature BYTEA NOT NULL,
fetched_at TIMESTAMPTZ NOT NULL DEFAULT NOW(),
verified BOOLEAN NOT NULL DEFAULT FALSE,
UNIQUE(origin, tree_size)
);
CREATE INDEX idx_rekor_checkpoints_origin_tree_size
ON attestor.rekor_checkpoints(origin, tree_size DESC);
```
### Tile Cache Structure
```
/var/lib/stellaops/rekor-cache/
+-- {origin}/
+-- checkpoints/
| +-- checkpoint-{tree_size}.sig
+-- tiles/
+-- level-0/
| +-- tile-{index}.bin
+-- level-1/
+-- tile-{index}.bin
```
### Configuration
```yaml
attestor:
rekor:
sync:
enabled: true
intervalMinutes: 5
maxCheckpointAgeDays: 30
tileCachePath: "/var/lib/stellaops/rekor-cache"
tileCacheSizeMb: 1024
backends:
- name: "sigstore-prod"
url: "https://rekor.sigstore.dev"
publicKeyPath: "/etc/stellaops/rekor-sigstore-prod.pub"
```
## Decisions & Risks
- Tile cache size management: LRU eviction vs time-based.
- Multiple Rekor backend support for redundancy.
- Network failure handling: exponential backoff with jitter.
## Acceptance Criteria
- Background service syncing checkpoints every 5 minutes.
- Offline verification using cached tiles (no network).
- Metrics dashboard showing cache health and sync lag.
## Next Checkpoints
- TBD (set once staffed).

82
docs/implplan/SPRINT_20260112_017_CRYPTO_pkcs11_hsm_implementation.md
View File

@@ -1,82 +0,0 @@
# Sprint 20260112-017-CRYPTO-pkcs11-hsm-implementation - PKCS#11 HSM Implementation
## Topic & Scope
- Complete PKCS#11 HSM integration using Net.Pkcs11Interop library.
- Current state evidence: `HsmPlugin` exists with stub implementation (`src/Cryptography/StellaOps.Cryptography.Plugin.Hsm/HsmPlugin.cs`), `Pkcs11HsmClient` throws `NotImplementedException`.
- Evidence to produce: Working PKCS#11 client, HSM connectivity validation, and operational runbook.
- **Working directory:** `src/Cryptography`.
- **Compliance item:** Item 4 - HSM / key escrow patterns.
## Dependencies & Concurrency
- Depends on Net.Pkcs11Interop NuGet package addition.
- Parallel safe with Rekor sync sprint.
## Documentation Prerequisites
- `docs/README.md`
- `docs/modules/signer/architecture.md`
- `docs/operations/key-rotation-runbook.md`
- `docs/modules/authority/operations/key-rotation.md`
## Delivery Tracker
| # | Task ID | Status | Key dependency / next step | Owners | Task Definition |
| --- | --- | --- | --- | --- | --- |
| 1 | HSM-001 | TODO | None | Crypto Guild | Add Net.Pkcs11Interop NuGet package to `src/Directory.Packages.props`. |
| 2 | HSM-002 | TODO | HSM-001 | Crypto Guild | Implement `Pkcs11HsmClient.SignAsync()` with PKCS#11 session management. |
| 3 | HSM-003 | TODO | HSM-002 | Crypto Guild | Implement `Pkcs11HsmClient.VerifyAsync()` for signature verification. |
| 4 | HSM-004 | TODO | HSM-003 | Crypto Guild | Add session pooling and reconnection logic for HSM connection stability. |
| 5 | HSM-005 | TODO | HSM-004 | Crypto Guild | Implement multi-slot failover support. |
| 6 | HSM-006 | TODO | HSM-005 | Crypto Guild | Add key attribute enforcement (CKA_PRIVATE, CKA_EXTRACTABLE policy). |
| 7 | HSM-007 | TODO | HSM-006 | Crypto Guild | Implement `GetMetadataAsync()` for key versioning info. |
| 8 | HSM-008 | TODO | HSM-007 | Testing Guild | Create SoftHSM2 test fixtures for integration testing. |
| 9 | HSM-009 | TODO | HSM-008 | Testing Guild | Add unit tests for session management, signing, and verification. |
| 10 | HSM-010 | TODO | HSM-009 | Doctor Guild | Update `HsmConnectivityCheck` to validate actual PKCS#11 operations. |
| 11 | HSM-011 | TODO | HSM-010 | Docs Guild | Create `docs/operations/hsm-setup-runbook.md` with configuration guide. |
| 12 | HSM-012 | TODO | HSM-011 | Docs Guild | Document SoftHSM2 test environment setup for development. |
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-01-15 | Sprint created for compliance readiness gap: PKCS#11 HSM implementation. | Planning |
## Technical Specification
### Supported Mechanisms
| Algorithm | PKCS#11 Mechanism | Status |
|-----------|------------------|--------|
| RSA-SHA256 | CKM_SHA256_RSA_PKCS | TODO |
| RSA-SHA384 | CKM_SHA384_RSA_PKCS | TODO |
| RSA-SHA512 | CKM_SHA512_RSA_PKCS | TODO |
| RSA-PSS | CKM_SHA256_RSA_PKCS_PSS | TODO |
| ECDSA-P256 | CKM_ECDSA_SHA256 | TODO |
| ECDSA-P384 | CKM_ECDSA_SHA384 | TODO |
| AES-GCM-128 | CKM_AES_GCM | TODO |
| AES-GCM-256 | CKM_AES_GCM | TODO |
### Configuration
```yaml
signing:
provider: "hsm"
hsm:
type: "pkcs11"
libraryPath: "/opt/hsm/libpkcs11.so"
slotId: 0
pin: "${HSM_PIN}"
tokenLabel: "StellaOps"
connectionTimeoutSeconds: 30
maxSessions: 10
sessionIdleTimeoutSeconds: 300
```
## Decisions & Risks
- SoftHSM2 for testing vs real HSM for production validation.
- PIN management via environment variable or secrets manager.
- Session exhaustion recovery strategy.
## Acceptance Criteria
- Working signing and verification with SoftHSM2.
- Key rotation demonstration with attestation continuity.
- Doctor check validating HSM connectivity.
- Runbook with step-by-step HSM configuration.
## Next Checkpoints
- TBD (set once staffed).

109
docs/implplan/SPRINT_20260112_017_POLICY_cvss_threshold_gate.md
View File

@@ -1,109 +0,0 @@
# Sprint 20260112-017-POLICY-cvss-threshold-gate - CVSS Threshold Policy Gate
## Topic & Scope
- Implement dedicated `CvssThresholdGate` for static CVSS score enforcement.
- Current state evidence: EPSS quarantine rules exist (priority 20) but no explicit CVSS threshold gate class.
- Evidence to produce: Gate implementation, configuration, and documentation.
- **Working directory:** `src/Policy`.
- **Compliance item:** Item 6 - Offline policy engine (OPA/Conftest-class).
## Dependencies & Concurrency
- Depends on existing `IPolicyGate` interface.
- Parallel safe with SBOM presence gate sprint.
## Documentation Prerequisites
- `docs/README.md`
- `docs/modules/policy/architecture.md`
- `docs/modules/policy/determinization-api.md`
## Delivery Tracker
| # | Task ID | Status | Key dependency / next step | Owners | Task Definition |
| --- | --- | --- | --- | --- | --- |
| 1 | CVSS-GATE-001 | DONE | None | Policy Guild | Create `CvssThresholdGate` class implementing `IPolicyGate`. |
| 2 | CVSS-GATE-002 | DONE | CVSS-GATE-001 | Policy Guild | Support CVSS v3.1 base score threshold configuration. |
| 3 | CVSS-GATE-003 | DONE | CVSS-GATE-002 | Policy Guild | Support CVSS v4.0 base score threshold configuration. |
| 4 | CVSS-GATE-004 | DONE | CVSS-GATE-003 | Policy Guild | Add per-environment threshold overrides (prod: 7.0, staging: 8.0, dev: 9.0). |
| 5 | CVSS-GATE-005 | DONE | CVSS-GATE-004 | Policy Guild | Add CVE allowlist/denylist support for exceptions. |
| 6 | CVSS-GATE-006 | DONE | CVSS-GATE-005 | Policy Guild | Implement offline operation (no external lookups). |
| 7 | CVSS-GATE-007 | DONE | CVSS-GATE-006 | Policy Guild | Register gate in `PolicyGateRegistry` with configurable priority. |
| 8 | CVSS-GATE-008 | DONE | CVSS-GATE-007 | Testing Guild | Create unit tests for threshold enforcement. |
| 9 | CVSS-GATE-009 | DONE | CVSS-GATE-008 | Testing Guild | Create tests for environment-specific overrides. |
| 10 | CVSS-GATE-010 | TODO | CVSS-GATE-009 | Docs Guild | Update policy architecture docs with CVSS gate. |
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-01-15 | Sprint created for compliance readiness gap: CVSS threshold policy gate. | Planning |
| 2026-01-15 | CVSS-GATE-001 to 007: Created CvssThresholdGate implementing IPolicyGate with full feature set. Options: Enabled, Priority, DefaultThreshold, per-environment Thresholds (prod/staging/dev), CvssVersionPreference (v3.1/v4.0/highest), Allowlist, Denylist, FailOnMissingCvss, RequireAllVersionsPass. Gate evaluates CVSS v3.1 and v4.0 scores, supports offline operation via injectable lookup or context metadata. Created CvssThresholdGateExtensions for DI registration and PolicyGateRegistry integration. CVSS-GATE-008/009: Created CvssThresholdGateTests with 20+ test cases covering: disabled gate, denylist/allowlist, missing CVSS handling, threshold enforcement at various score levels, environment-specific thresholds (staging/dev), version preference (v3.1/v4.0/highest), RequireAllVersionsPass mode, metadata fallback, case-insensitive CVE matching, and complete details in result. | Agent |
## Technical Specification
### Gate Configuration
```yaml
policy:
gates:
cvssThreshold:
enabled: true
priority: 15
defaultThreshold: 7.0
thresholds:
production: 7.0
staging: 8.0
development: 9.0
cvssVersionPreference: "v4.0" # v3.1, v4.0, or highest
allowlist:
- "CVE-2024-12345" # Known false positive
denylist:
- "CVE-2024-99999" # Always block
```
### Gate Interface
```csharp
public sealed class CvssThresholdGate : IPolicyGate
{
public string Name => "CvssThreshold";
public int Priority => _options.Priority;
public Task<GateResult> EvaluateAsync(
GateContext context,
CancellationToken ct)
{
var finding = context.Finding;
var environment = context.Environment;
// Get CVSS score (prefer v4.0 if available)
var cvssScore = GetCvssScore(finding, _options.CvssVersionPreference);
// Check denylist first
if (_options.Denylist.Contains(finding.CveId))
return Task.FromResult(GateResult.Blocked($"CVE {finding.CveId} is denylisted"));
// Check allowlist
if (_options.Allowlist.Contains(finding.CveId))
return Task.FromResult(GateResult.Passed("CVE is allowlisted"));
// Get environment-specific threshold
var threshold = GetThreshold(environment);
if (cvssScore >= threshold)
return Task.FromResult(GateResult.Blocked(
$"CVSS {cvssScore:F1} exceeds threshold {threshold:F1} for {environment}"));
return Task.FromResult(GateResult.Passed());
}
}
```
## Decisions & Risks
- CVSS v4.0 adoption is emerging; fallback to v3.1 required.
- Denylist takes precedence over allowlist.
- Offline operation means CVSS scores must be pre-populated in findings.
## Acceptance Criteria
- Gate blocks CVEs exceeding configured threshold.
- Environment-specific thresholds enforced correctly.
- Allowlist/denylist exceptions work as expected.
- Gate operates without network (offline determinism).
## Next Checkpoints
- TBD (set once staffed).

128
docs/implplan/SPRINT_20260112_017_POLICY_sbom_presence_gate.md
View File

@@ -1,128 +0,0 @@
# Sprint 20260112-017-POLICY-sbom-presence-gate - SBOM Presence Policy Gate
## Topic & Scope
- Implement dedicated `SbomPresenceGate` for SBOM inventory validation.
- Current state evidence: `SbomLineageEvidence` mentioned in config but no dedicated presence gate.
- Evidence to produce: Gate implementation, schema validation, and configuration.
- **Working directory:** `src/Policy`.
- **Compliance item:** Item 6 - Offline policy engine (OPA/Conftest-class).
## Dependencies & Concurrency
- Depends on existing `IPolicyGate` interface.
- Parallel safe with CVSS threshold gate sprint.
## Documentation Prerequisites
- `docs/README.md`
- `docs/modules/policy/architecture.md`
- `docs/modules/sbom-service/architecture.md`
## Delivery Tracker
| # | Task ID | Status | Key dependency / next step | Owners | Task Definition |
| --- | --- | --- | --- | --- | --- |
| 1 | SBOM-GATE-001 | DONE | None | Policy Guild | Create `SbomPresenceGate` class implementing `IPolicyGate`. |
| 2 | SBOM-GATE-002 | DONE | SBOM-GATE-001 | Policy Guild | Require SBOM presence for release artifacts. |
| 3 | SBOM-GATE-003 | DONE | SBOM-GATE-002 | Policy Guild | Validate SBOM format (SPDX 2.3/3.0.1, CycloneDX 1.4-1.7). |
| 4 | SBOM-GATE-004 | DONE | SBOM-GATE-003 | Policy Guild | Validate SBOM schema against bundled JSON schemas. |
| 5 | SBOM-GATE-005 | DONE | SBOM-GATE-004 | Policy Guild | Check minimum component inventory (configurable threshold). |
| 6 | SBOM-GATE-006 | DONE | SBOM-GATE-005 | Policy Guild | Add per-environment enforcement levels (prod: required, dev: optional). |
| 7 | SBOM-GATE-007 | DONE | SBOM-GATE-006 | Policy Guild | Add SBOM signature verification requirement option. |
| 8 | SBOM-GATE-008 | DONE | SBOM-GATE-007 | Policy Guild | Register gate in `PolicyGateRegistry`. |
| 9 | SBOM-GATE-009 | DONE | SBOM-GATE-008 | Testing Guild | Create unit tests for presence and schema validation. |
| 10 | SBOM-GATE-010 | TODO | SBOM-GATE-009 | Docs Guild | Update policy architecture docs with SBOM gate. |
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-01-15 | Sprint created for compliance readiness gap: SBOM presence policy gate. | Planning |
| 2026-01-15 | SBOM-GATE-001 to 008: Created SbomPresenceGate implementing IPolicyGate. Options: Enabled, Priority, per-environment Enforcement (Required/Recommended/Optional), AcceptedFormats (spdx-2.2/2.3/3.0.1, cyclonedx-1.4-1.7), MinimumComponents, RequireSignature, SchemaValidation, RequirePrimaryComponent. Gate validates SBOM presence, format normalization (handles case variations, cdx alias), component count, schema validity, signature requirement, and primary component. Created SbomPresenceGateExtensions for DI and registry integration. SbomInfo record captures all SBOM metadata. SBOM-GATE-009: Created SbomPresenceGateTests with 25+ test cases covering: disabled gate, enforcement levels (optional/recommended/required), missing SBOM handling, valid SBOM, accepted formats, invalid formats, insufficient components, schema validation, signature requirements (missing/invalid/valid), primary component requirement, environment-specific enforcement, default enforcement fallback, metadata parsing, format normalization variations, and optional metadata inclusion. | Agent |
## Technical Specification
### Gate Configuration
```yaml
policy:
gates:
sbomPresence:
enabled: true
priority: 5
enforcement:
production: required
staging: required
development: optional
formats:
- "spdx-2.3"
- "spdx-3.0.1"
- "cyclonedx-1.4"
- "cyclonedx-1.5"
- "cyclonedx-1.6"
- "cyclonedx-1.7"
minimumComponents: 1
requireSignature: false
schemaValidation: true
```
### Gate Interface
```csharp
public sealed class SbomPresenceGate : IPolicyGate
{
public string Name => "SbomPresence";
public int Priority => _options.Priority;
public Task<GateResult> EvaluateAsync(
GateContext context,
CancellationToken ct)
{
var artifact = context.Artifact;
var environment = context.Environment;
// Get enforcement level for environment
var enforcement = GetEnforcementLevel(environment);
if (enforcement == EnforcementLevel.Optional)
return Task.FromResult(GateResult.Passed("SBOM optional for environment"));
// Check SBOM presence
var sbom = context.Evidence.GetSbom(artifact.Digest);
if (sbom is null)
return Task.FromResult(GateResult.Blocked("SBOM not found for artifact"));
// Validate format
if (!_options.Formats.Contains(sbom.Format))
return Task.FromResult(GateResult.Blocked(
$"SBOM format '{sbom.Format}' not in allowed list"));
// Validate schema
if (_options.SchemaValidation)
{
var schemaResult = ValidateSchema(sbom);
if (!schemaResult.IsValid)
return Task.FromResult(GateResult.Blocked(
$"SBOM schema validation failed: {schemaResult.Error}"));
}
// Check minimum components
if (sbom.ComponentCount < _options.MinimumComponents)
return Task.FromResult(GateResult.Blocked(
$"SBOM has {sbom.ComponentCount} components, minimum is {_options.MinimumComponents}"));
// Check signature if required
if (_options.RequireSignature && !sbom.IsSigned)
return Task.FromResult(GateResult.Blocked("SBOM signature required but not present"));
return Task.FromResult(GateResult.Passed());
}
}
```
## Decisions & Risks
- Schema validation requires bundling JSON schemas for offline operation.
- Minimum component threshold prevents empty SBOMs.
- Signature requirement may be too strict for some environments.
## Acceptance Criteria
- Gate blocks artifacts without SBOM in production.
- Schema validation works offline with bundled schemas.
- Environment-specific enforcement works correctly.
- Signature verification optional but functional.
## Next Checkpoints
- TBD (set once staffed).

150
docs/implplan/SPRINT_20260112_017_POLICY_signature_required_gate.md
View File

@@ -1,150 +0,0 @@
# Sprint 20260112-017-POLICY-signature-required-gate - Signature Required Policy Gate
## Topic & Scope
- Implement standalone `SignatureRequiredGate` for generic payload signature enforcement.
- Current state evidence: `VexProofGate` has `RequireSignedStatements` but no standalone signature gate.
- Evidence to produce: Generic gate implementation for any evidence type.
- **Working directory:** `src/Policy`.
- **Compliance item:** Item 6 - Offline policy engine (OPA/Conftest-class).
## Dependencies & Concurrency
- Depends on existing `IPolicyGate` interface.
- Parallel safe with other policy gate sprints.
## Documentation Prerequisites
- `docs/README.md`
- `docs/modules/policy/architecture.md`
- `docs/modules/signer/architecture.md`
## Delivery Tracker
| # | Task ID | Status | Key dependency / next step | Owners | Task Definition |
| --- | --- | --- | --- | --- | --- |
| 1 | SIG-GATE-001 | DONE | None | Policy Guild | Create `SignatureRequiredGate` class implementing `IPolicyGate`. |
| 2 | SIG-GATE-002 | DONE | SIG-GATE-001 | Policy Guild | Configure required signatures per evidence type (SBOM, VEX, attestation). |
| 3 | SIG-GATE-003 | DONE | SIG-GATE-002 | Policy Guild | Validate DSSE envelope structure. |
| 4 | SIG-GATE-004 | DONE | SIG-GATE-003 | Policy Guild | Verify signature against trusted key set. |
| 5 | SIG-GATE-005 | DONE | SIG-GATE-004 | Policy Guild | Support keyless (Fulcio) signature verification with bundled roots. |
| 6 | SIG-GATE-006 | DONE | SIG-GATE-005 | Policy Guild | Add per-environment signature requirements. |
| 7 | SIG-GATE-007 | DONE | SIG-GATE-006 | Policy Guild | Add issuer/identity constraints (e.g., only accept signatures from specific emails). |
| 8 | SIG-GATE-008 | DONE | SIG-GATE-007 | Policy Guild | Register gate in `PolicyGateRegistry`. |
| 9 | SIG-GATE-009 | DONE | SIG-GATE-008 | Testing Guild | Create unit tests for signature validation scenarios. |
| 10 | SIG-GATE-010 | TODO | SIG-GATE-009 | Docs Guild | Update policy architecture docs with signature gate. |
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-01-15 | Sprint created for compliance readiness gap: signature required policy gate. | Planning |
| 2026-01-15 | SIG-GATE-001 to 008: Created SignatureRequiredGate implementing IPolicyGate. Options: Enabled, Priority, EvidenceTypes (per-type config with Required, TrustedIssuers with wildcard support, TrustedKeyIds, AcceptedAlgorithms), Environments (RequiredOverride, AdditionalIssuers, SkipEvidenceTypes), EnableKeylessVerification, FulcioRoots, RekorUrl, RequireTransparencyLogInclusion. SignatureInfo record captures EvidenceType, HasSignature, SignatureValid, Algorithm, SignerIdentity, KeyId, IsKeyless, HasTransparencyLogInclusion, CertificateChainValid, VerificationErrors. Gate validates per-evidence-type signatures with issuer wildcard matching (*@domain.com), algorithm enforcement (ES256/RS256/EdDSA), key ID constraints, keyless (Fulcio) verification with transparency log requirement, certificate chain validation, and environment-specific overrides. Created SignatureRequiredGateExtensions for DI and registry integration. SIG-GATE-009: Created SignatureRequiredGateTests with 18+ test cases covering: disabled gate, missing/invalid signatures, issuer validation with wildcards, algorithm enforcement, key ID constraints, keyless signatures with/without transparency log, keyless disabled, environment overrides (skip types, additional issuers), certificate chain validation, and subdomain wildcard matching. | Agent |
## Technical Specification
### Gate Configuration
```yaml
policy:
gates:
signatureRequired:
enabled: true
priority: 3
evidenceTypes:
sbom:
required: true
trustedIssuers:
- "build@company.com"
- "release@company.com"
vex:
required: true
trustedIssuers:
- "security@company.com"
attestation:
required: true
trustedIssuers:
- "*@company.com" # Wildcard support
keylessVerification:
enabled: true
fulcioRootPath: "/etc/stellaops/fulcio-root.pem"
rekorPublicKeyPath: "/etc/stellaops/rekor.pub"
enforcement:
production: required
staging: required
development: optional
```
### Gate Interface
```csharp
public sealed class SignatureRequiredGate : IPolicyGate
{
public string Name => "SignatureRequired";
public int Priority => _options.Priority;
public Task<GateResult> EvaluateAsync(
GateContext context,
CancellationToken ct)
{
var environment = context.Environment;
var enforcement = GetEnforcementLevel(environment);
if (enforcement == EnforcementLevel.Optional)
return Task.FromResult(GateResult.Passed("Signatures optional"));
var failures = new List<string>();
foreach (var evidence in context.Evidence.All)
{
var config = GetEvidenceConfig(evidence.Type);
if (!config.Required) continue;
// Check signature presence
if (evidence.Signature is null)
{
failures.Add($"{evidence.Type}: No signature present");
continue;
}
// Validate DSSE envelope
var dsseResult = ValidateDsseEnvelope(evidence.Signature);
if (!dsseResult.IsValid)
{
failures.Add($"{evidence.Type}: Invalid DSSE - {dsseResult.Error}");
continue;
}
// Verify signature
var verifyResult = await VerifySignatureAsync(
evidence.Signature,
config.TrustedIssuers,
ct);
if (!verifyResult.IsValid)
{
failures.Add($"{evidence.Type}: Signature invalid - {verifyResult.Error}");
continue;
}
// Check issuer constraints
if (!MatchesIssuerConstraints(verifyResult.Issuer, config.TrustedIssuers))
{
failures.Add($"{evidence.Type}: Issuer '{verifyResult.Issuer}' not trusted");
}
}
if (failures.Count > 0)
return Task.FromResult(GateResult.Blocked(string.Join("; ", failures)));
return Task.FromResult(GateResult.Passed());
}
}
```
## Decisions & Risks
- Wildcard issuer matching syntax (e.g., `*@company.com`).
- Keyless verification requires bundled Fulcio root for offline.
- Performance impact of signature verification on every evaluation.
## Acceptance Criteria
- Gate blocks unsigned evidence when required.
- Issuer constraints enforced correctly.
- Keyless verification works offline with bundled roots.
- Environment-specific enforcement works correctly.
## Next Checkpoints
- TBD (set once staffed).

157
docs/implplan/SPRINT_20260112_018_AUTH_local_rbac_fallback.md
View File

@@ -1,157 +0,0 @@
# Sprint 20260112-018-AUTH-local-rbac-fallback - Local RBAC Policy Fallback
## Topic & Scope
- Implement local file-based RBAC policy fallback for offline/air-gapped Authority operation.
- Current state evidence: Authority is PostgreSQL-only; no local policy fallback exists.
- Evidence to produce: File-based policy store, fallback mechanism, and break-glass account.
- **Working directory:** `src/Authority`.
- **Compliance item:** Item 2 - Offline RBAC & break-glass.
## Dependencies & Concurrency
- Depends on existing Authority architecture understanding.
- Parallel safe with other Authority sprints.
## Documentation Prerequisites
- `docs/README.md`
- `docs/modules/authority/architecture.md`
- `docs/modules/authority/AUTHORITY.md`
## Delivery Tracker
| # | Task ID | Status | Key dependency / next step | Owners | Task Definition |
| --- | --- | --- | --- | --- | --- |
| 1 | RBAC-001 | DONE | None | Authority Guild | Create `ILocalPolicyStore` interface. |
| 2 | RBAC-002 | DONE | RBAC-001 | Authority Guild | Implement `FileBasedPolicyStore` with YAML/JSON policy files. |
| 3 | RBAC-003 | DONE | RBAC-002 | Authority Guild | Define local policy file schema (roles, scopes, subjects). |
| 4 | RBAC-004 | DONE | RBAC-003 | Authority Guild | Implement policy file hot-reload with inotify/FileSystemWatcher. |
| 5 | RBAC-005 | DONE | RBAC-004 | Authority Guild | Create fallback mechanism when PostgreSQL is unavailable. |
| 6 | RBAC-006 | DONE | RBAC-005 | Authority Guild | Implement break-glass account with bootstrap credentials. |
| 7 | RBAC-007 | DONE | RBAC-006 | Authority Guild | Add break-glass usage audit logging (mandatory reason codes). |
| 8 | RBAC-008 | DONE | RBAC-007 | Authority Guild | Implement automatic break-glass session timeout (configurable, default 15 min). |
| 9 | RBAC-009 | DONE | RBAC-008 | Authority Guild | Add break-glass session extension with re-authentication. |
| 10 | RBAC-010 | TODO | RBAC-009 | AirGap Guild | Include local policy in Offline Kit bundles. |
| 11 | RBAC-011 | DONE | RBAC-010 | Testing Guild | Create unit tests for local policy store. |
| 12 | RBAC-012 | TODO | RBAC-011 | Testing Guild | Create integration tests for fallback scenarios. |
| 13 | RBAC-013 | TODO | RBAC-012 | Docs Guild | Create break-glass account runbook. |
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-01-15 | Sprint created for compliance readiness gap: local RBAC policy fallback. | Planning |
| 2026-01-15 | RBAC-001: Created ILocalPolicyStore interface with GetPolicyAsync, GetSubjectRolesAsync, GetRoleScopesAsync, HasScopeAsync, GetSubjectScopesAsync, ValidateBreakGlassCredentialAsync, IsAvailableAsync, ReloadAsync, and PolicyReloaded event. RBAC-002/003/004: Created FileBasedPolicyStore implementing ILocalPolicyStore with YAML/JSON loading via YamlDotNet, FileSystemWatcher hot-reload with debouncing, role inheritance resolution, subject index with tenant/expiration checks, schema version validation. Created LocalPolicyModels with LocalPolicy, LocalRole, LocalSubject, BreakGlassConfig, BreakGlassAccount, BreakGlassSession records. Created LocalPolicyStoreOptions with PolicyFilePath, EnableHotReload, RequireSignature, FallbackBehavior, SupportedSchemaVersions. RBAC-005: Created FallbackPolicyStore with IPrimaryPolicyStoreHealthCheck integration, PolicyStoreMode enum (Primary/Fallback/Degraded), automatic failover after FailureThreshold consecutive failures, recovery with MinFallbackDurationMs cooldown, ModeChanged event. RBAC-006/007/008/009: Created BreakGlassSessionManager with IBreakGlassSessionManager interface, session creation with credential validation (bcrypt), mandatory reason codes from AllowedReasonCodes, configurable SessionTimeoutMinutes (default 15), MaxExtensions with re-authentication, automatic expired session cleanup, IBreakGlassAuditLogger with BreakGlassAuditEvent (SessionCreated/Extended/Terminated/Expired/AuthenticationFailed/InvalidReasonCode/MaxExtensionsReached). RBAC-011: Created FileBasedPolicyStoreTests with 15+ unit tests covering policy serialization, role inheritance, subject enable/expiration, break-glass config, session validity, options defaults, mode change events. | Agent |
## Technical Specification
### Local Policy File Schema
```yaml
# /etc/stellaops/authority/local-policy.yaml
schemaVersion: "1.0.0"
lastUpdated: "2026-01-15T12:00:00Z"
signatureRequired: true
signature: "base64-encoded-dsse-signature"
roles:
- name: "admin"
scopes:
- "authority:read"
- "authority:write"
- "platform:admin"
- name: "operator"
scopes:
- "orch:operate"
- "orch:view"
- name: "auditor"
scopes:
- "audit:read"
- "obs:incident"
subjects:
- id: "user@company.com"
roles: ["admin"]
tenant: "default"
- id: "ops@company.com"
roles: ["operator"]
tenant: "default"
breakGlass:
enabled: true
accounts:
- id: "break-glass-admin"
passwordHash: "$argon2id$v=19$m=65536,t=3,p=4$..."
roles: ["admin"]
sessionTimeoutMinutes: 15
maxExtensions: 2
requireReasonCode: true
allowedReasonCodes:
- "emergency-incident"
- "database-outage"
- "security-event"
- "scheduled-maintenance"
```
### Break-Glass Audit Event
```json
{
"eventType": "authority.break_glass.activated",
"severity": "warning",
"accountId": "break-glass-admin",
"reasonCode": "database-outage",
"reasonDetails": "PostgreSQL cluster unreachable",
"activatedAt": "2026-01-15T12:34:56Z",
"sessionId": "bg-session-abc123",
"expiresAt": "2026-01-15T12:49:56Z",
"clientIp": "10.0.0.5",
"userAgent": "StellaOps-CLI/2027.Q1"
}
```
### Configuration
```yaml
authority:
localPolicy:
enabled: true
policyPath: "/etc/stellaops/authority/local-policy.yaml"
fallbackMode: "on_db_unavailable" # on_db_unavailable, always_local, hybrid
reloadIntervalSeconds: 30
requireSignature: true
signaturePublicKeyPath: "/etc/stellaops/authority/policy-signing.pub"
breakGlass:
enabled: true
maxSessionMinutes: 60
alertOnActivation: true
alertChannels: ["email", "slack", "pagerduty"]
```
### Fallback Logic
```csharp
public async Task<AuthorizationResult> AuthorizeAsync(
AuthorizationRequest request,
CancellationToken ct)
{
// Try PostgreSQL first
if (await _postgresStore.IsAvailableAsync(ct))
{
return await _postgresStore.AuthorizeAsync(request, ct);
}
// Fallback to local policy
_logger.LogWarning("PostgreSQL unavailable, using local policy fallback");
_metrics.IncrementFallbackActivations();
return await _localPolicyStore.AuthorizeAsync(request, ct);
}
```
## Decisions & Risks
- Local policy must be signed to prevent tampering.
- Break-glass password storage: Argon2id hash in file.
- Alert-on-activation to notify security team.
- Policy sync between PostgreSQL and local file.
## Acceptance Criteria
- Local policy fallback activates when PostgreSQL unavailable.
- Break-glass account authenticates with reason code.
- Session timeout enforced with audit trail.
- Alert dispatched on break-glass activation.
## Next Checkpoints
- TBD (set once staffed).

143
docs/implplan/SPRINT_20260112_018_CRYPTO_key_escrow_shamir.md
View File

@@ -1,143 +0,0 @@
# Sprint 20260112-018-CRYPTO-key-escrow-shamir - Key Escrow with Shamir Secret Sharing
## Topic & Scope
- Implement key escrow mechanisms using Shamir's Secret Sharing for key recovery.
- Current state evidence: No key recovery or escrow mechanisms exist.
- Evidence to produce: Shamir splitting, escrow storage, and recovery procedures.
- **Working directory:** `src/Cryptography`.
- **Compliance item:** Item 4 - HSM / key escrow patterns.
## Dependencies & Concurrency
- Depends on `SPRINT_20260112_018_SIGNER_dual_control_ceremonies` for recovery ceremony.
- Parallel safe with other crypto sprints.
## Documentation Prerequisites
- `docs/README.md`
- `docs/modules/signer/architecture.md`
- `docs/operations/key-rotation-runbook.md`
## Delivery Tracker
| # | Task ID | Status | Key dependency / next step | Owners | Task Definition |
| --- | --- | --- | --- | --- | --- |
| 1 | ESCROW-001 | TODO | None | Crypto Guild | Implement `ShamirSecretSharing` class with split/combine operations. |
| 2 | ESCROW-002 | TODO | ESCROW-001 | Crypto Guild | Use GF(2^8) for byte-level secret sharing. |
| 3 | ESCROW-003 | TODO | ESCROW-002 | Crypto Guild | Create `IKeyEscrowService` interface. |
| 4 | ESCROW-004 | TODO | ESCROW-003 | Crypto Guild | Implement key splitting with configurable M-of-N threshold. |
| 5 | ESCROW-005 | TODO | ESCROW-004 | Crypto Guild | Create `KeyShare` record with share index, data, and metadata. |
| 6 | ESCROW-006 | TODO | ESCROW-005 | Crypto Guild | Implement encrypted share storage (shares encrypted at rest). |
| 7 | ESCROW-007 | TODO | ESCROW-006 | Crypto Guild | Create `IEscrowAgentStore` interface for share custody. |
| 8 | ESCROW-008 | TODO | ESCROW-007 | Crypto Guild | Implement share distribution to escrow agents. |
| 9 | ESCROW-009 | TODO | ESCROW-008 | Crypto Guild | Create key recovery workflow with share collection. |
| 10 | ESCROW-010 | TODO | ESCROW-009 | Crypto Guild | Integrate with dual-control ceremonies for recovery authorization. |
| 11 | ESCROW-011 | TODO | ESCROW-010 | Testing Guild | Create unit tests for Shamir splitting/combining. |
| 12 | ESCROW-012 | TODO | ESCROW-011 | Testing Guild | Create integration tests for recovery workflow. |
| 13 | ESCROW-013 | TODO | ESCROW-012 | Docs Guild | Create key escrow and recovery runbook. |
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-01-15 | Sprint created for compliance readiness gap: key escrow with Shamir secret sharing. | Planning |
## Technical Specification
### Shamir Secret Sharing
```csharp
public sealed class ShamirSecretSharing
{
/// <summary>
/// Split a secret into N shares where any M shares can reconstruct.
/// Uses GF(2^8) arithmetic for byte-level operations.
/// </summary>
public IReadOnlyList<KeyShare> Split(
byte[] secret,
int threshold, // M - minimum shares needed
int totalShares, // N - total shares created
IGuidGenerator guidGenerator,
TimeProvider timeProvider)
{
// Validate: 2 <= M <= N <= 255
// For each byte of secret:
// 1. Generate random polynomial of degree M-1 with secret as constant term
// 2. Evaluate polynomial at points 1..N
// 3. Store evaluation results as share data
}
/// <summary>
/// Reconstruct secret from M or more shares using Lagrange interpolation.
/// </summary>
public byte[] Combine(IReadOnlyList<KeyShare> shares)
{
// Validate: shares.Count >= threshold
// Use Lagrange interpolation at x=0 to recover constant term (secret)
}
}
```
### Key Share Model
```csharp
public sealed record KeyShare
{
public required Guid ShareId { get; init; }
public required int Index { get; init; } // 1..N
public required byte[] EncryptedData { get; init; }
public required string KeyId { get; init; }
public required int Threshold { get; init; }
public required int TotalShares { get; init; }
public required DateTimeOffset CreatedAt { get; init; }
public required DateTimeOffset ExpiresAt { get; init; }
public required string CustodianId { get; init; }
public required string ChecksumHex { get; init; } // SHA-256 of unencrypted share
}
```
### Escrow Agent Configuration
```yaml
cryptography:
escrow:
enabled: true
defaultThreshold: 3
defaultTotalShares: 5
shareEncryptionKeyPath: "/etc/stellaops/escrow-encryption.key"
agents:
- id: "escrow-agent-1"
name: "Primary Security Officer"
email: "cso@company.com"
publicKeyPath: "/etc/stellaops/escrow-agents/agent1.pub"
- id: "escrow-agent-2"
name: "Backup Security Officer"
email: "backup-cso@company.com"
publicKeyPath: "/etc/stellaops/escrow-agents/agent2.pub"
- id: "escrow-agent-3"
name: "External Custodian"
email: "custodian@escrow-service.com"
publicKeyPath: "/etc/stellaops/escrow-agents/agent3.pub"
shareRetentionDays: 365
autoDeleteOnRecovery: false
```
### Recovery Workflow
```
1. Recovery request initiated (requires dual-control ceremony)
2. Notify escrow agents of recovery request
3. Each agent authenticates and submits their share
4. System collects shares until threshold reached
5. Secret reconstructed using Lagrange interpolation
6. Key imported/restored to target HSM or keystore
7. Recovery audit event logged
8. (Optional) Shares re-generated with new random polynomial
```
## Decisions & Risks
- Share storage security: encrypt shares at rest with separate key.
- Agent identity verification during recovery.
- Re-escrow after recovery to prevent share replay.
- External escrow agent integration complexity.
## Acceptance Criteria
- 3-of-5 Shamir splitting demonstrated.
- Key recovery from 3 shares successful.
- Escrow agent notification workflow functional.
- Recovery audit trail complete.
## Next Checkpoints
- TBD (set once staffed).

131
docs/implplan/SPRINT_20260112_018_DOCS_upgrade_runbook_evidence_continuity.md
View File

@@ -1,131 +0,0 @@
# Sprint 20260112-018-DOCS-upgrade-runbook-evidence-continuity - Upgrade Runbook with Evidence Continuity
## Topic & Scope
- Create comprehensive upgrade runbook with evidence continuity procedures.
- Current state evidence: DB migrations documented but no evidence-focused upgrade guide.
- Evidence to produce: Step-by-step runbook, pre-flight checklists, and validation procedures.
- **Working directory:** `docs/operations`.
- **Compliance item:** Item 7 - Upgrade & evidence-migration paths.
## Dependencies & Concurrency
- Depends on `SPRINT_20260112_016_DOCS_blue_green_deployment` for deployment procedures.
- Depends on `SPRINT_20260112_018_EVIDENCE_reindex_tooling` for CLI commands.
- Parallel safe with implementation sprints.
## Documentation Prerequisites
- `docs/README.md`
- `docs/db/MIGRATION_STRATEGY.md`
- `docs/releases/VERSIONING.md`
- `docs/flows/13-evidence-bundle-export-flow.md`
## Delivery Tracker
| # | Task ID | Status | Key dependency / next step | Owners | Task Definition |
| --- | --- | --- | --- | --- | --- |
| 1 | RUNBOOK-001 | TODO | None | Docs Guild | Create `docs/operations/upgrade-runbook.md` structure. |
| 2 | RUNBOOK-002 | TODO | RUNBOOK-001 | Docs Guild | Document pre-upgrade checklist (backup, health checks, evidence export). |
| 3 | RUNBOOK-003 | TODO | RUNBOOK-002 | Docs Guild | Document evidence integrity pre-flight validation. |
| 4 | RUNBOOK-004 | TODO | RUNBOOK-003 | Docs Guild | Document database backup procedures with evidence focus. |
| 5 | RUNBOOK-005 | TODO | RUNBOOK-004 | Docs Guild | Document step-by-step upgrade sequence. |
| 6 | RUNBOOK-006 | TODO | RUNBOOK-005 | Docs Guild | Document evidence reindex procedures (reference CLI sprint). |
| 7 | RUNBOOK-007 | TODO | RUNBOOK-006 | Docs Guild | Document chain-of-custody verification steps. |
| 8 | RUNBOOK-008 | TODO | RUNBOOK-007 | Docs Guild | Document post-upgrade validation checklist. |
| 9 | RUNBOOK-009 | TODO | RUNBOOK-008 | Docs Guild | Document rollback procedures with evidence considerations. |
| 10 | RUNBOOK-010 | TODO | RUNBOOK-009 | Docs Guild | Document breaking changes matrix per version. |
| 11 | RUNBOOK-011 | TODO | RUNBOOK-010 | Docs Guild | Create `docs/operations/evidence-migration.md` for detailed procedures. |
| 12 | RUNBOOK-012 | TODO | RUNBOOK-011 | Docs Guild | Document air-gap upgrade path with evidence handling. |
| 13 | RUNBOOK-013 | TODO | RUNBOOK-012 | Docs Guild | Create troubleshooting section for common upgrade issues. |
| 14 | RUNBOOK-014 | TODO | RUNBOOK-013 | Docs Guild | Add version-specific migration notes template. |
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-01-15 | Sprint created for compliance readiness gap: upgrade runbook with evidence continuity. | Planning |
## Runbook Outline
### 1. Pre-Upgrade Phase
```markdown
## Pre-Upgrade Checklist
### 1.1 Environment Assessment
- [ ] Current version identified
- [ ] Target version confirmed compatible (see compatibility matrix)
- [ ] Resource requirements verified (CPU, memory, storage)
- [ ] Maintenance window scheduled
### 1.2 Backup Procedures
- [ ] PostgreSQL full backup completed
- [ ] Evidence Locker export completed (all tenants)
- [ ] Attestation bundles archived
- [ ] Configuration files backed up
- [ ] Backup integrity verified
### 1.3 Evidence Integrity Pre-Flight
- [ ] Run `stella evidence verify-all --output pre-upgrade-report.json`
- [ ] Verify all Merkle roots valid
- [ ] Export root cross-reference baseline
- [ ] Document current evidence count by type
### 1.4 Health Checks
- [ ] All services healthy (green status)
- [ ] No pending migrations
- [ ] Queue depths at zero
- [ ] Recent scan/attestation successful
```
### 2. Upgrade Phase
```markdown
## Upgrade Sequence
### 2.1 Blue/Green Preparation
- [ ] Deploy green environment with new version
- [ ] Apply database migrations (Category A: startup)
- [ ] Verify green environment health
### 2.2 Evidence Migration
- [ ] Run `stella evidence migrate --dry-run` on green
- [ ] Review migration impact report
- [ ] Execute evidence migration if needed
- [ ] Verify evidence integrity post-migration
### 2.3 Traffic Cutover
- [ ] Switch traffic to green (gradual or instant)
- [ ] Monitor error rates and latency
- [ ] Verify all services responding correctly
```
### 3. Post-Upgrade Phase
```markdown
## Post-Upgrade Validation
### 3.1 Evidence Continuity Verification
- [ ] Run `stella evidence verify-continuity --pre pre-upgrade-report.json`
- [ ] Confirm chain-of-custody preserved
- [ ] Verify artifact digests unchanged
- [ ] Generate continuity report for audit
### 3.2 Functional Validation
- [ ] Execute smoke test suite
- [ ] Verify scan capability
- [ ] Verify attestation generation
- [ ] Verify policy evaluation
### 3.3 Cleanup
- [ ] Decommission blue environment (after observation period)
- [ ] Archive upgrade artifacts
- [ ] Update documentation with version
```
## Decisions & Risks
- Minimum observation period before blue decommission (recommend 72 hours).
- Evidence export timing (before or during maintenance window).
- Rollback trigger criteria definition.
## Acceptance Criteria
- Complete runbook with all checklists.
- Evidence-focused procedures clearly documented.
- Rollback procedures tested and validated.
- Troubleshooting section covers common issues.
## Next Checkpoints
- TBD (set once staffed).

157
docs/implplan/SPRINT_20260112_018_EVIDENCE_reindex_tooling.md
View File

@@ -1,157 +0,0 @@
# Sprint 20260112-018-EVIDENCE-reindex-tooling - Evidence Re-Index Tooling
## Topic & Scope
- Implement CLI tooling for evidence re-indexing and chain-of-custody verification after upgrades.
- Current state evidence: Evidence bundles exist but no re-indexing or migration tooling.
- Evidence to produce: CLI commands, migration scripts, and verification reports.
- **Working directory:** `src/Cli`, `src/EvidenceLocker`.
- **Compliance item:** Item 7 - Upgrade & evidence-migration paths.
## Dependencies & Concurrency
- Depends on `SPRINT_20260112_016_DOCS_blue_green_deployment` for upgrade procedures.
- Parallel safe with other Evidence sprints.
## Documentation Prerequisites
- `docs/README.md`
- `docs/flows/13-evidence-bundle-export-flow.md`
- `docs/db/MIGRATION_STRATEGY.md`
## Delivery Tracker
| # | Task ID | Status | Key dependency / next step | Owners | Task Definition |
| --- | --- | --- | --- | --- | --- |
| 1 | REINDEX-001 | TODO | None | CLI Guild | Add `stella evidence reindex` command skeleton. |
| 2 | REINDEX-002 | TODO | REINDEX-001 | CLI Guild | Implement `--dry-run` mode for impact assessment. |
| 3 | REINDEX-003 | TODO | REINDEX-002 | Evidence Guild | Create `IEvidenceReindexService` interface. |
| 4 | REINDEX-004 | TODO | REINDEX-003 | Evidence Guild | Implement Merkle root recomputation from existing evidence. |
| 5 | REINDEX-005 | TODO | REINDEX-004 | Evidence Guild | Create old/new root cross-reference mapping. |
| 6 | REINDEX-006 | TODO | REINDEX-005 | Evidence Guild | Implement chain-of-custody verification (old proofs still valid). |
| 7 | REINDEX-007 | TODO | REINDEX-006 | Evidence Guild | Add `stella evidence verify-continuity` command. |
| 8 | REINDEX-008 | TODO | REINDEX-007 | Evidence Guild | Generate verification report (JSON, HTML formats). |
| 9 | REINDEX-009 | TODO | REINDEX-008 | CLI Guild | Add `stella evidence migrate` command for schema migrations. |
| 10 | REINDEX-010 | TODO | REINDEX-009 | Evidence Guild | Implement batch processing with progress reporting. |
| 11 | REINDEX-011 | TODO | REINDEX-010 | Evidence Guild | Add rollback capability for failed migrations. |
| 12 | REINDEX-012 | TODO | REINDEX-011 | Testing Guild | Create unit tests for reindex operations. |
| 13 | REINDEX-013 | TODO | REINDEX-012 | Testing Guild | Create integration tests with sample evidence bundles. |
| 14 | REINDEX-014 | TODO | REINDEX-013 | Docs Guild | Document evidence migration procedures in upgrade runbook. |
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-01-15 | Sprint created for compliance readiness gap: evidence re-index tooling. | Planning |
## Technical Specification
### CLI Commands
```bash
# Dry-run reindex to assess impact
stella evidence reindex --dry-run --since 2026-01-01
# Execute reindex with progress
stella evidence reindex --since 2026-01-01 --batch-size 100
# Verify chain-of-custody after upgrade
stella evidence verify-continuity \
--old-root sha256:abc123... \
--new-root sha256:def456... \
--output report.html
# Migrate evidence schema
stella evidence migrate \
--from-version 1.0 \
--to-version 2.0 \
--dry-run
# Generate upgrade readiness report
stella evidence upgrade-check --target-version 2027.Q2
```
### Reindex Service Interface
```csharp
public interface IEvidenceReindexService
{
/// <summary>
/// Recompute Merkle roots for evidence bundles.
/// </summary>
Task<ReindexResult> ReindexAsync(
ReindexOptions options,
IProgress<ReindexProgress> progress,
CancellationToken ct);
/// <summary>
/// Verify chain-of-custody between old and new roots.
/// </summary>
Task<ContinuityVerificationResult> VerifyContinuityAsync(
string oldRoot,
string newRoot,
CancellationToken ct);
/// <summary>
/// Generate cross-reference mapping between old and new roots.
/// </summary>
Task<RootCrossReferenceMap> GenerateCrossReferenceAsync(
DateTimeOffset since,
CancellationToken ct);
}
```
### Cross-Reference Map
```json
{
"schemaVersion": "1.0.0",
"generatedAt": "2026-01-15T12:34:56Z",
"fromVersion": "2027.Q1",
"toVersion": "2027.Q2",
"entries": [
{
"bundleId": "bundle-abc123",
"oldRoot": "sha256:old123...",
"newRoot": "sha256:new456...",
"evidenceCount": 15,
"verified": true,
"digestsPreserved": true
}
],
"summary": {
"totalBundles": 1500,
"successfulMigrations": 1498,
"failedMigrations": 2,
"digestsPreserved": 1500
}
}
```
### Verification Report
```html
<!DOCTYPE html>
<html>
<head>
<title>Evidence Continuity Report - 2027.Q1 to 2027.Q2</title>
</head>
<body>
<h1>Evidence Continuity Verification Report</h1>
<h2>Summary</h2>
<ul>
<li>Upgrade: 2027.Q1 -> 2027.Q2</li>
<li>Bundles Verified: 1500</li>
<li>Chain-of-Custody: PRESERVED</li>
<li>Artifact Digests: UNCHANGED</li>
</ul>
<h2>Details</h2>
<!-- Bundle-by-bundle verification results -->
</body>
</html>
```
## Decisions & Risks
- Batch size tuning for large evidence stores.
- Rollback strategy for partial failures.
- Digest preservation guarantee documentation.
## Acceptance Criteria
- Dry-run mode shows accurate impact assessment.
- Reindex completes with progress reporting.
- Continuity verification confirms chain-of-custody.
- HTML report suitable for auditor review.
## Next Checkpoints
- TBD (set once staffed).

143
docs/implplan/SPRINT_20260112_018_SIGNER_dual_control_ceremonies.md
View File

@@ -1,143 +0,0 @@
# Sprint 20260112-018-SIGNER-dual-control-ceremonies - Dual-Control Signing Ceremonies
## Topic & Scope
- Implement M-of-N threshold signing ceremonies for high-assurance key operations.
- Current state evidence: Key rotation service exists but no dual-control or threshold signing.
- Evidence to produce: Ceremony protocol, approval workflow, and audit trail.
- **Working directory:** `src/Signer`.
- **Compliance item:** Item 4 - HSM / key escrow patterns.
## Dependencies & Concurrency
- Depends on `SPRINT_20260112_017_CRYPTO_pkcs11_hsm_implementation` for HSM integration.
- Parallel safe with key escrow sprint.
## Documentation Prerequisites
- `docs/README.md`
- `docs/modules/signer/architecture.md`
- `docs/operations/key-rotation-runbook.md`
## Delivery Tracker
| # | Task ID | Status | Key dependency / next step | Owners | Task Definition |
| --- | --- | --- | --- | --- | --- |
| 1 | DUAL-001 | DONE | None | Signer Guild | Design M-of-N ceremony protocol specification. |
| 2 | DUAL-002 | DONE | DUAL-001 | Signer Guild | Create `ICeremonyOrchestrator` interface. |
| 3 | DUAL-003 | DONE | DUAL-002 | Signer Guild | Implement ceremony state machine (Pending, PartiallyApproved, Approved, Executed, Expired). |
| 4 | DUAL-004 | DONE | DUAL-003 | Signer Guild | Create `CeremonyApproval` record with approver identity, timestamp, and signature. |
| 5 | DUAL-005 | DONE | DUAL-004 | Signer Guild | Implement approval collection with threshold checking. |
| 6 | DUAL-006 | DONE | DUAL-005 | Signer Guild | Add ceremony timeout and expiration handling. |
| 7 | DUAL-007 | DONE | DUAL-006 | Signer Guild | Integrate with Authority for approver identity verification. |
| 8 | DUAL-008 | DONE | DUAL-007 | Signer Guild | Create ceremony audit event (`signer.ceremony.initiated`, `.approved`, `.executed`). |
| 9 | DUAL-009 | DONE | DUAL-008 | DB Guild | Create `signer.ceremonies` PostgreSQL table for state persistence. |
| 10 | DUAL-010 | TODO | DUAL-009 | API Guild | Add ceremony API endpoints (`POST /ceremonies`, `POST /ceremonies/{id}/approve`). |
| 11 | DUAL-011 | DONE | DUAL-010 | Testing Guild | Create unit tests for ceremony state machine. |
| 12 | DUAL-012 | TODO | DUAL-011 | Testing Guild | Create integration tests for multi-approver workflows. |
| 13 | DUAL-013 | TODO | DUAL-012 | Docs Guild | Create dual-control ceremony runbook. |
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-01-15 | Sprint created for compliance readiness gap: dual-control signing ceremonies. | Planning |
| 2026-01-15 | DUAL-001: Protocol specification embedded in sprint. DUAL-002: Created ICeremonyOrchestrator interface with CreateCeremonyAsync, ApproveCeremonyAsync, GetCeremonyAsync, ListCeremoniesAsync, ExecuteCeremonyAsync, CancelCeremonyAsync, ProcessExpiredCeremoniesAsync methods. Added CeremonyFilter for list queries. DUAL-003: Created CeremonyStateMachine with IsValidTransition, ComputeStateAfterApproval, CanAcceptApproval, CanExecute, CanCancel, IsTerminalState, GetStateDescription methods. DUAL-004: Created CeremonyApproval record with ApprovalId, CeremonyId, ApproverIdentity, ApprovedAt, ApprovalSignature, ApprovalReason, SigningKeyId, SignatureAlgorithm. DUAL-005/006: Implemented CeremonyOrchestrator with threshold checking, expiration handling via ProcessExpiredCeremoniesAsync. DUAL-007: Created ICeremonyApproverValidator interface and ApproverValidationResult for Authority integration. DUAL-008: Created CeremonyAuditEvents constants and event records (CeremonyInitiatedEvent, CeremonyApprovedEvent, CeremonyExecutedEvent, CeremonyExpiredEvent, CeremonyCancelledEvent, CeremonyApprovalRejectedEvent). DUAL-009: Created ICeremonyRepository interface. DUAL-011: Created CeremonyStateMachineTests with 50+ test cases for state transitions, approval computation, and state queries. | Agent |
## Technical Specification
### Ceremony Protocol
```
1. Initiator creates ceremony request with operation details
2. System notifies required approvers
3. Each approver authenticates and provides approval + signature
4. System collects approvals until M-of-N threshold reached
5. Operation executes with audit trail
6. Ceremony marked complete with all approvals recorded
```
### Ceremony State Machine
```
+----------------+
| Pending |
+-------+--------+
|
(approval received)
v
+----------------------+
| PartiallyApproved |
+----------+-----------+
|
(threshold reached OR timeout)
|
+---------+---------+
v v
+-----------+ +-----------+
| Approved | | Expired |
+-----+-----+ +-----------+
|
(execution)
v
+-----------+
| Executed |
+-----------+
```
### Database Schema
```sql
CREATE TABLE signer.ceremonies (
ceremony_id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
operation_type TEXT NOT NULL, -- key_generation, key_rotation, key_revocation
operation_payload JSONB NOT NULL,
threshold_required INT NOT NULL,
threshold_reached INT NOT NULL DEFAULT 0,
state TEXT NOT NULL DEFAULT 'pending',
initiated_by TEXT NOT NULL,
initiated_at TIMESTAMPTZ NOT NULL DEFAULT NOW(),
expires_at TIMESTAMPTZ NOT NULL,
executed_at TIMESTAMPTZ,
CONSTRAINT valid_state CHECK (state IN ('pending', 'partially_approved', 'approved', 'executed', 'expired'))
);
CREATE TABLE signer.ceremony_approvals (
approval_id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
ceremony_id UUID NOT NULL REFERENCES signer.ceremonies(ceremony_id),
approver_identity TEXT NOT NULL,
approved_at TIMESTAMPTZ NOT NULL DEFAULT NOW(),
approval_signature BYTEA NOT NULL,
approval_reason TEXT,
UNIQUE(ceremony_id, approver_identity)
);
```
### Configuration
```yaml
signer:
ceremonies:
enabled: true
defaultThreshold: 2
expirationMinutes: 60
operations:
key_generation:
threshold: 3
requiredRoles: ["crypto-custodian"]
key_rotation:
threshold: 2
requiredRoles: ["crypto-custodian", "security-admin"]
key_revocation:
threshold: 2
requiredRoles: ["crypto-custodian"]
notifications:
channels: ["email", "slack"]
```
## Decisions & Risks
- Threshold signing vs approval collection (approval is simpler, threshold signing is cryptographically stronger).
- Ceremony timeout to prevent indefinite pending operations.
- Approver identity must be verified via Authority.
## Acceptance Criteria
- 2-of-3 ceremony workflow demonstrated.
- Audit trail captures all approvals with signatures.
- Expired ceremonies handled gracefully.
- Runbook with step-by-step ceremony instructions.
## Next Checkpoints
- TBD (set once staffed).