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

- 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:
2025-11-01 02:21:46 +02:00
parent e5629454cf
commit 66cb6c4b8a
227 changed files with 9913 additions and 6210 deletions

View File

@@ -1,21 +1,32 @@
# StellaOps Telemetry Core Guild Charter
## Mission
Deliver shared observability primitives for every StellaOps service. Provide deterministic logging, metrics, and tracing utilities that enforce the imposed rule: instrumentation patterns adopted here must be propagated wherever applicable.
## Scope
- Structured logging facade with fixed field schema and privacy guards.
- OpenTelemetry SDK bootstrapping helpers for services and workers.
- Sampling, exemplar, and redaction policies enforced in code.
- Context propagation middleware for HTTP, gRPC, message, and job pipelines.
- Validation test harnesses ensuring deterministic output across builds.
## Coordination
- Partner with DevOps Guild on collector/exporter defaults.
- Align with Authority on trace/log scope annotations.
- Collaborate with service guilds to roll out new instrumentation packages per sprint objectives.
## Definition of Done
- All library changes ship unit + integration tests.
- Determinism mode runs (`dotnet test -c Deterministic`) pass locally and in CI.
- Updated changelog fragments stored under `/docs/observability/` as referenced by tasks.
# StellaOps Telemetry Core Guild Charter
## Mission
Deliver shared observability primitives for every StellaOps service. Provide deterministic logging, metrics, and tracing utilities that enforce the imposed rule: instrumentation patterns adopted here must be propagated wherever applicable.
## Scope
- Structured logging facade with fixed field schema and privacy guards.
- OpenTelemetry SDK bootstrapping helpers for services and workers.
- Sampling, exemplar, and redaction policies enforced in code.
- Context propagation middleware for HTTP, gRPC, message, and job pipelines.
- Validation test harnesses ensuring deterministic output across builds.
## Coordination
- Partner with DevOps Guild on collector/exporter defaults.
- Align with Authority on trace/log scope annotations.
- Collaborate with service guilds to roll out new instrumentation packages per sprint objectives.
## Definition of Done
- All library changes ship unit + integration tests.
- Determinism mode runs (`dotnet test -c Deterministic`) pass locally and in CI.
- Updated changelog fragments stored under `/docs/observability/` as referenced by tasks.
## Required Reading
- `docs/modules/telemetry/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.