- Created `StellaOps.TestKit.Tests` project for unit tests related to determinism. - Implemented `DeterminismManifestTests` to validate deterministic output for canonical bytes and strings, file read/write operations, and error handling for invalid schema versions. - Added `SbomDeterminismTests` to ensure identical inputs produce consistent SBOMs across SPDX 3.0.1 and CycloneDX 1.6/1.7 formats, including parallel execution tests. - Updated project references in `StellaOps.Integration.Determinism` to include the new determinism testing library.
Platform Architecture & Module Dossiers
Use this index to locate architecture narratives, boundaries, and implementation plans for every Stella Ops component.
Core Views
- ../high-level-architecture.md – 10-minute overview of the end-to-end flow.
- ../07_HIGH_LEVEL_ARCHITECTURE.md – exhaustive reference (data flows, trust boundaries, operational traits).
- ../40_ARCHITECTURE_OVERVIEW.md – design principles applied across modules.
- ../scanner-core-contracts.md – canonical DTOs shared by Scanner services and consumers.
- Legacy service dossier: ../11_AUTHORITY.md – Authority overview before module split.
- UI documentation set: ../../ui/ (navigation, policies, findings, runs, tours).
- Component map: component-map.md – quick descriptions of every
src/module and how they interact.
Module Catalogue
Each module directory bundles an ownership charter (AGENTS.md), current work (TASKS.md), architecture dossier, and implementation plan. Operations guides live under operations/ where applicable.
Tip: Every module directory also exposes
README.md,AGENTS.md, andTASKS.mdfor roles, current backlog, and ownership responsibilities.