stella-ops.org/git.stella-ops.org
1
0
Fork 0
Code Issues Pull Requests Actions 12 Releases Wiki Activity
Files
d9077297782de5a90a6aab929d99abaae632cd7d
git.stella-ops.org/docs/modules/platform/implementation_plan.md
StellaOps Bot 71e9a56cfd
Some checks failed
Docs CI / lint-and-preview (push) Has been cancelled
Details
Airgap Sealed CI Smoke / sealed-smoke (push) Has been cancelled
Details
Export Center CI / export-ci (push) Has been cancelled
Details
Signals CI & Image / signals-ci (push) Has been cancelled
Details
feat: Add Scanner CI runner and related artifacts 
- Implemented `run-scanner-ci.sh` to build and run tests for the Scanner solution with a warmed NuGet cache.
- Created `excititor-vex-traces.json` dashboard for monitoring Excititor VEX observations.
- Added Docker Compose configuration for the OTLP span sink in `docker-compose.spansink.yml`.
- Configured OpenTelemetry collector in `otel-spansink.yaml` to receive and process traces.
- Developed `run-spansink.sh` script to run the OTLP span sink for Excititor traces.
- Introduced `FileSystemRiskBundleObjectStore` for storing risk bundle artifacts in the filesystem.
- Built `RiskBundleBuilder` for creating risk bundles with associated metadata and providers.
- Established `RiskBundleJob` to execute the risk bundle creation and storage process.
- Defined models for risk bundle inputs, entries, and manifests in `RiskBundleModels.cs`.
- Implemented signing functionality for risk bundle manifests with `HmacRiskBundleManifestSigner`.
- Created unit tests for `RiskBundleBuilder`, `RiskBundleJob`, and signing functionality to ensure correctness.
- Added filesystem artifact reader tests to validate manifest parsing and artifact listing.
- Included test manifests for egress scenarios in the task runner tests.
- Developed timeline query service tests to verify tenant and event ID handling.
2025-11-30 19:12:35 +02:00

1.7 KiB
Raw Blame History

Implementation plan — Platform

Current objectives

  • Maintain deterministic behaviour and offline parity across releases.
  • Keep documentation, telemetry, and runbooks aligned with the latest sprint outcomes.

Workstreams

  • Backlog grooming: reconcile open stories in ../../TASKS.md with this module's roadmap.
  • Implementation: collaborate with service owners to land feature work defined in SPRINTS/EPIC docs.
  • Validation: extend tests/fixtures to preserve determinism and provenance requirements.

Epic milestones

  • Epic 1 – AOC enforcement: maintain authoritative guardrail docs, schemas, and verifier checklists.
  • Epics 2 & 4 – Policy Engine/Studio: coordinate platform-wide governance, approvals, and tenancy scopes.
  • Epic 5 – SBOM Graph Explorer: define shared contracts for graph indexing and overlays.
  • Epics 6–11: ensure cross-cutting contracts (Explorer, Lens, AI, Orchestrator, Notifications) stay aligned.
  • Track additional platform updates in ../../TASKS.md and docs/implplan/SPRINTS.md.

Coordination

  • Review ./AGENTS.md before picking up new work.
  • Sync with cross-cutting teams noted in /docs/implplan/SPRINT_*.md.
  • Update this plan whenever scope, dependencies, or guardrails change.

Sprint alignment (2025-11-30)

  • Docs sprint: docs/implplan/SPRINT_0324_0001_0001_docs_modules_platform.md; statuses mirrored in docs/modules/platform/TASKS.md.
  • Keep links to architecture-overview.md and ../../07_HIGH_LEVEL_ARCHITECTURE.md current; update both sprint and TASKS if platform guardrails change.
  • Platform is docs-only; ensure Offline Kit and AOC references remain discoverable from README/architecture.