feat: Add guild charters and task boards for various components
Some checks failed
Docs CI / lint-and-preview (push) Has been cancelled
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:
@@ -1,38 +1,49 @@
|
||||
# AGENTS
|
||||
## Role
|
||||
Implement the CERT/CC (Carnegie Mellon CERT Coordination Center) advisory connector so Concelier can ingest US CERT coordination bulletins.
|
||||
|
||||
## Scope
|
||||
- Identify CERT/CC advisory publication format (VU#, blog, RSS, JSON) and define fetch cadence/windowing.
|
||||
- Implement fetch, parse, and mapping jobs with cursor persistence and dedupe.
|
||||
- Normalise advisory content (summary, impacted vendors, products, recommended mitigations, CVEs).
|
||||
- Produce canonical `Advisory` objects including aliases, references, affected packages, and range primitive metadata.
|
||||
- Supply fixtures and deterministic regression tests.
|
||||
|
||||
## Participants
|
||||
- `Source.Common` (HTTP/fetch utilities, DTO storage).
|
||||
- `Storage.Mongo` (raw/document/DTO/advisory stores and state).
|
||||
- `Concelier.Models` (canonical structures).
|
||||
- `Concelier.Testing` (integration tests and snapshots).
|
||||
|
||||
## Interfaces & Contracts
|
||||
- Job kinds: `certcc:fetch`, `certcc:parse`, `certcc:map`.
|
||||
- Persist upstream caching metadata (ETag/Last-Modified) when available.
|
||||
- Aliases should capture CERT/CC VU IDs and referenced CVEs.
|
||||
|
||||
## In/Out of scope
|
||||
In scope:
|
||||
- End-to-end connector with range primitive instrumentation and telemetry.
|
||||
|
||||
Out of scope:
|
||||
- ICS-CERT alerts (handled by dedicated connector) or blog posts unrelated to advisories.
|
||||
|
||||
## Observability & Security Expectations
|
||||
- Log fetch and mapping statistics; surface failures with backoff.
|
||||
- Sanitise HTML sources before persistence.
|
||||
- Respect upstream throttling via retry/backoff.
|
||||
|
||||
## Tests
|
||||
- Add `StellaOps.Concelier.Connector.CertCc.Tests` to cover fetch/parse/map with canned fixtures.
|
||||
- Snapshot canonical advisories and support UPDATE flag for regeneration.
|
||||
- Ensure deterministic ordering and timestamp normalisation.
|
||||
# AGENTS
|
||||
## Role
|
||||
Implement the CERT/CC (Carnegie Mellon CERT Coordination Center) advisory connector so Concelier can ingest US CERT coordination bulletins.
|
||||
|
||||
## Scope
|
||||
- Identify CERT/CC advisory publication format (VU#, blog, RSS, JSON) and define fetch cadence/windowing.
|
||||
- Implement fetch, parse, and mapping jobs with cursor persistence and dedupe.
|
||||
- Normalise advisory content (summary, impacted vendors, products, recommended mitigations, CVEs).
|
||||
- Produce canonical `Advisory` objects including aliases, references, affected packages, and range primitive metadata.
|
||||
- Supply fixtures and deterministic regression tests.
|
||||
|
||||
## Participants
|
||||
- `Source.Common` (HTTP/fetch utilities, DTO storage).
|
||||
- `Storage.Mongo` (raw/document/DTO/advisory stores and state).
|
||||
- `Concelier.Models` (canonical structures).
|
||||
- `Concelier.Testing` (integration tests and snapshots).
|
||||
|
||||
## Interfaces & Contracts
|
||||
- Job kinds: `certcc:fetch`, `certcc:parse`, `certcc:map`.
|
||||
- Persist upstream caching metadata (ETag/Last-Modified) when available.
|
||||
- Aliases should capture CERT/CC VU IDs and referenced CVEs.
|
||||
|
||||
## In/Out of scope
|
||||
In scope:
|
||||
- End-to-end connector with range primitive instrumentation and telemetry.
|
||||
|
||||
Out of scope:
|
||||
- ICS-CERT alerts (handled by dedicated connector) or blog posts unrelated to advisories.
|
||||
|
||||
## Observability & Security Expectations
|
||||
- Log fetch and mapping statistics; surface failures with backoff.
|
||||
- Sanitise HTML sources before persistence.
|
||||
- Respect upstream throttling via retry/backoff.
|
||||
|
||||
## Tests
|
||||
- Add `StellaOps.Concelier.Connector.CertCc.Tests` to cover fetch/parse/map with canned fixtures.
|
||||
- Snapshot canonical advisories and support UPDATE flag for regeneration.
|
||||
- Ensure deterministic ordering and timestamp normalisation.
|
||||
|
||||
## Required Reading
|
||||
- `docs/modules/concelier/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.
|
||||
|
||||
Reference in New Issue
Block a user