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

69
src/Scanner/__Libraries/StellaOps.Scanner.Analyzers.Lang.Rust/AGENTS.md
View File

@@ -1,29 +1,40 @@
# StellaOps.Scanner.Analyzers.Lang.Rust — Agent Charter
## Role
Develop the Rust analyzer plug-in that resolves crates from metadata (`.fingerprint`, Cargo.lock, embedded markers) and provides deterministic fallbacks for stripped binaries.
## Scope
- Locate Cargo metadata in container layers (registry cache, target fingerprints, embedded Git info).
- Parse symbol tables / section data to heuristically identify crates when metadata missing, tagging provenance appropriately.
- Integrate binary hash fallback with quiet provenance classification.
- Package plug-in manifest, determinism fixtures, and performance/coverage benchmarks.
## Out of Scope
- Native linker analysis beyond crate attribution.
- Fetching Cargo registry metadata from the network.
- Policy decisions or UI surfacing.
## Expectations
- Accurate crate attribution (≥85 % on curated fixtures) with explicit heuristic labeling.
- Analyzer runtime <1 s over 500 binary corpus; minimal allocations through pooling.
- Offline-first; rely on local Cargo data.
- Telemetry capturing heuristic vs verified evidence ratios.
## Dependencies
- Shared language analyzer infrastructure; Worker dispatcher; optionally EntryTrace hints for runtime coverage.
## Testing & Artifacts
- Fixtures for cargo workspaces, release builds, stripped binaries, vendor caches.
- Determinism + benchmark artifacts comparing to competitor scanners.
- ADR documenting heuristic boundaries + risk mitigations.
# StellaOps.Scanner.Analyzers.Lang.Rust — Agent Charter
## Role
Develop the Rust analyzer plug-in that resolves crates from metadata (`.fingerprint`, Cargo.lock, embedded markers) and provides deterministic fallbacks for stripped binaries.
## Scope
- Locate Cargo metadata in container layers (registry cache, target fingerprints, embedded Git info).
- Parse symbol tables / section data to heuristically identify crates when metadata missing, tagging provenance appropriately.
- Integrate binary hash fallback with quiet provenance classification.
- Package plug-in manifest, determinism fixtures, and performance/coverage benchmarks.
## Out of Scope
- Native linker analysis beyond crate attribution.
- Fetching Cargo registry metadata from the network.
- Policy decisions or UI surfacing.
## Expectations
- Accurate crate attribution (≥85 % on curated fixtures) with explicit heuristic labeling.
- Analyzer runtime <1 s over 500 binary corpus; minimal allocations through pooling.
- Offline-first; rely on local Cargo data.
- Telemetry capturing heuristic vs verified evidence ratios.
## Dependencies
- Shared language analyzer infrastructure; Worker dispatcher; optionally EntryTrace hints for runtime coverage.
## Testing & Artifacts
- Fixtures for cargo workspaces, release builds, stripped binaries, vendor caches.
- Determinism + benchmark artifacts comparing to competitor scanners.
- ADR documenting heuristic boundaries + risk mitigations.
## 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.