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

feat: Add guild charters and task boards for various components
Some checks failed
Docs CI / lint-and-preview (push) Has been cancelled
Details

Browse Source 
- Introduced guild charters for Scanner Deno, PHP, Ruby, Native, WebService, Java, Surface.Env, Surface.FS, Surface.Secrets, Surface.Validation, UI, Zastava Observer, Zastava Webhook, Zastava Core, and Plugin Platform.
- Each charter outlines the mission, scope, required reading, and working agreements for the respective guilds.
- Created task boards for Surface.Env, Surface.FS, Surface.Secrets, Surface.Validation, and Zastava components to track progress and dependencies.
- Ensured all documents emphasize determinism, offline readiness, security, and integration with shared Surface libraries.
This commit is contained in:
master
2025-11-01 02:21:46 +02:00
parent e5629454cf
commit 66cb6c4b8a
227 changed files with 9913 additions and 6210 deletions
Download Patch File Download Diff File Expand all files Collapse all files

41
src/Scanner/__Libraries/StellaOps.Scanner.Cache/AGENTS.md
View File

@@ -1,15 +1,26 @@
# StellaOps.Scanner.Cache — Agent Charter
## Mission
Provide deterministic, offline-friendly caching primitives for scanner layers and file content so warm scans complete in <5 s and cache reuse remains reproducible across deployments.
## Responsibilities
- Implement layer cache keyed by layer digest, retaining analyzer metadata and provenance per architecture §3.3.
- Deliver file content-addressable storage (CAS) with deduplication, TTL enforcement, and offline import/export hooks.
- Expose structured metrics, health probes, and configuration toggles for cache sizing, eviction, and warm/cold thresholds.
- Coordinate invalidation workflows (layer purge, TTL expiry, diff invalidation) while keeping deterministic logs and telemetry.
## Interfaces & Dependencies
- Relies on `StackExchange.Redis` via `StellaOps.DependencyInjection` bindings for cache state.
- Coordinates with `StellaOps.Scanner.Storage` object store when persisting immutable artifacts.
- Targets `net10.0` preview SDK and follows scanner coding standards from `docs/18_CODING_STANDARDS.md`.
# StellaOps.Scanner.Cache — Agent Charter
## Mission
Provide deterministic, offline-friendly caching primitives for scanner layers and file content so warm scans complete in <5 s and cache reuse remains reproducible across deployments.
## Responsibilities
- Implement layer cache keyed by layer digest, retaining analyzer metadata and provenance per architecture §3.3.
- Deliver file content-addressable storage (CAS) with deduplication, TTL enforcement, and offline import/export hooks.
- Expose structured metrics, health probes, and configuration toggles for cache sizing, eviction, and warm/cold thresholds.
- Coordinate invalidation workflows (layer purge, TTL expiry, diff invalidation) while keeping deterministic logs and telemetry.
## Interfaces & Dependencies
- Relies on `StackExchange.Redis` via `StellaOps.DependencyInjection` bindings for cache state.
- Coordinates with `StellaOps.Scanner.Storage` object store when persisting immutable artifacts.
- Targets `net10.0` preview SDK and follows scanner coding standards from `docs/18_CODING_STANDARDS.md`.
## Required Reading
- `docs/modules/scanner/architecture.md`
- `docs/modules/platform/architecture-overview.md`
## Working Agreement
- 1. Update task status to `DOING`/`DONE` in both `docs/implplan/SPRINTS.md` and the local `TASKS.md` when you start or finish work.
- 2. Review this charter and the Required Reading documents before coding; confirm prerequisites are met.
- 3. Keep changes deterministic (stable ordering, timestamps, hashes) and align with offline/air-gap expectations.
- 4. Coordinate doc updates, tests, and cross-guild communication whenever contracts or workflows change.
- 5. Revert to `TODO` if you pause the task without shipping changes; leave notes in commit/PR descriptions for context.