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,39 +1,50 @@
|
||||
# AGENTS
|
||||
## Role
|
||||
Implement the CISA ICS advisory connector to ingest US CISA Industrial Control Systems advisories (distinct from the general CERT feed).
|
||||
|
||||
## Scope
|
||||
- Locate the official CISA ICS advisory feed/API (currently HTML/RSS) and define fetch cadence/windowing.
|
||||
- Build fetch/cursor pipeline with retry/backoff and raw document storage.
|
||||
- Parse advisory content for summary, impacted vendors/products, mitigation, CVEs.
|
||||
- Map advisories into canonical `Advisory` records with aliases, references, affected ICS packages, and range primitives.
|
||||
- Provide deterministic fixtures and automated regression tests.
|
||||
|
||||
## Participants
|
||||
- `Source.Common` (HTTP/fetch utilities, DTO storage).
|
||||
- `Storage.Mongo` (raw/document/DTO/advisory stores + source state).
|
||||
- `Concelier.Models` (canonical advisory structures).
|
||||
- `Concelier.Testing` (integration fixtures and snapshots).
|
||||
|
||||
## Interfaces & Contracts
|
||||
- Job kinds: `ics-cisa:fetch`, `ics-cisa:parse`, `ics-cisa:map`.
|
||||
- Persist upstream caching metadata (ETag/Last-Modified) when available.
|
||||
- Alias set should include CISA ICS advisory IDs and referenced CVE IDs.
|
||||
|
||||
## In/Out of scope
|
||||
In scope:
|
||||
- ICS-specific advisories from CISA.
|
||||
- Range primitives capturing vendor/equipment metadata.
|
||||
|
||||
Out of scope:
|
||||
- General CISA alerts (covered elsewhere).
|
||||
|
||||
## Observability & Security Expectations
|
||||
- Log fetch attempts, advisory counts, and mapping results.
|
||||
- Sanitize HTML, removing scripts/styles before persistence.
|
||||
- Honour upstream rate limits with exponential backoff.
|
||||
|
||||
## Tests
|
||||
- Add `StellaOps.Concelier.Connector.Ics.Cisa.Tests` to cover fetch/parse/map with canned fixtures.
|
||||
- Snapshot canonical advisories; support fixture regeneration via env flag.
|
||||
- Ensure deterministic ordering/time normalisation.
|
||||
# AGENTS
|
||||
## Role
|
||||
Implement the CISA ICS advisory connector to ingest US CISA Industrial Control Systems advisories (distinct from the general CERT feed).
|
||||
|
||||
## Scope
|
||||
- Locate the official CISA ICS advisory feed/API (currently HTML/RSS) and define fetch cadence/windowing.
|
||||
- Build fetch/cursor pipeline with retry/backoff and raw document storage.
|
||||
- Parse advisory content for summary, impacted vendors/products, mitigation, CVEs.
|
||||
- Map advisories into canonical `Advisory` records with aliases, references, affected ICS packages, and range primitives.
|
||||
- Provide deterministic fixtures and automated regression tests.
|
||||
|
||||
## Participants
|
||||
- `Source.Common` (HTTP/fetch utilities, DTO storage).
|
||||
- `Storage.Mongo` (raw/document/DTO/advisory stores + source state).
|
||||
- `Concelier.Models` (canonical advisory structures).
|
||||
- `Concelier.Testing` (integration fixtures and snapshots).
|
||||
|
||||
## Interfaces & Contracts
|
||||
- Job kinds: `ics-cisa:fetch`, `ics-cisa:parse`, `ics-cisa:map`.
|
||||
- Persist upstream caching metadata (ETag/Last-Modified) when available.
|
||||
- Alias set should include CISA ICS advisory IDs and referenced CVE IDs.
|
||||
|
||||
## In/Out of scope
|
||||
In scope:
|
||||
- ICS-specific advisories from CISA.
|
||||
- Range primitives capturing vendor/equipment metadata.
|
||||
|
||||
Out of scope:
|
||||
- General CISA alerts (covered elsewhere).
|
||||
|
||||
## Observability & Security Expectations
|
||||
- Log fetch attempts, advisory counts, and mapping results.
|
||||
- Sanitize HTML, removing scripts/styles before persistence.
|
||||
- Honour upstream rate limits with exponential backoff.
|
||||
|
||||
## Tests
|
||||
- Add `StellaOps.Concelier.Connector.Ics.Cisa.Tests` to cover fetch/parse/map with canned fixtures.
|
||||
- Snapshot canonical advisories; support fixture regeneration via env flag.
|
||||
- Ensure deterministic ordering/time 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