stop syncing with TASKS.md
This commit is contained in:
@@ -17,7 +17,7 @@ Provide key management abstractions and drivers (file, cloud KMS, HSM, FIDO2) fo
|
||||
- `docs/modules/platform/architecture-overview.md`
|
||||
|
||||
## Working Agreement
|
||||
- 1. Update task status to `DOING`/`DONE` in both correspoding sprint file `/docs/implplan/SPRINT_*.md` and the local `TASKS.md` when you start or finish work.
|
||||
- 1. Update task status to `DOING`/`DONE` in both correspoding sprint file `/docs/implplan/SPRINT_*.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.
|
||||
|
||||
@@ -1,6 +0,0 @@
|
||||
# CryptoPro Plugin Tasks
|
||||
|
||||
- [ ] SEC-CRYPTO-90-019: Run fork test suite on Windows runner with CryptoPro CSP; capture results.
|
||||
- [ ] SEC-CRYPTO-90-020: Run plugin smoke (sign/verify) on Windows runner with CSP; capture results.
|
||||
- [ ] Add platform gating in CI: ensure `cryptopro-optin` workflow wired to Windows runner that has CSP installed.
|
||||
- [ ] Publish runbook updates after tests pass (link to docs/security/rootpack_ru_crypto_fork.md).
|
||||
@@ -7,7 +7,7 @@ Team 8 owns the end-to-end security posture for StellaOps Authority and its cons
|
||||
## Operational Boundaries
|
||||
|
||||
- Primary workspace: `src/__Libraries/StellaOps.Cryptography`, `src/Authority/StellaOps.Authority/StellaOps.Authority.Plugin.Standard`, `src/Authority/StellaOps.Authority/StellaOps.Authority.Storage.Postgres`, and Authority host (`src/Authority/StellaOps.Authority/StellaOps.Authority`).
|
||||
- Coordinate cross-module changes via TASKS.md updates and PR descriptions.
|
||||
- Coordinate cross-module changes via docs/implplan/SPRINT*.md files updates and PR descriptions.
|
||||
- Never bypass deterministic behaviour (sorted keys, stable timestamps).
|
||||
- Tests live alongside owning projects (`*.Tests`). Extend goldens instead of rewriting.
|
||||
|
||||
@@ -25,7 +25,7 @@ Team 8 owns the end-to-end security posture for StellaOps Authority and its cons
|
||||
- `docs/modules/platform/architecture-overview.md`
|
||||
|
||||
## Working Agreement
|
||||
- 1. Update task status to `DOING`/`DONE` in both correspoding sprint file `/docs/implplan/SPRINT_*.md` and the local `TASKS.md` when you start or finish work.
|
||||
- 1. Update task status to `DOING`/`DONE` in both correspoding sprint file `/docs/implplan/SPRINT_*.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.
|
||||
|
||||
@@ -17,7 +17,7 @@ Maintain the shared plugin infrastructure used across StellaOps services (Scanne
|
||||
- `docs/modules/excititor/architecture.md`
|
||||
|
||||
## Working Agreement
|
||||
1. **Status sync**: update task state to `DOING`/`DONE` in corresponding sprint file `docs/implplan/SPRINT_*.md` and local `TASKS.md` whenever work begins/ends.
|
||||
1. **Status sync**: update task state to `DOING`/`DONE` in corresponding sprint file `docs/implplan/SPRINT_*.md` whenever work begins/ends.
|
||||
2. **Deterministic loading**: maintain ordered, reproducible plugin discovery; enforce hash verification/whitelists as documented.
|
||||
3. **Security**: validate manifests, restrict assembly loading paths, and expose capability checks to hosts; document hardening guidance.
|
||||
4. **Compatibility**: version public APIs carefully; provide migration guides when breaking changes occur.
|
||||
|
||||
@@ -13,7 +13,6 @@ Own shared replay domain types, canonicalisation helpers, bundle hashing utiliti
|
||||
1. Maintain deterministic behaviour (lexicographic ordering, canonical JSON, fixed encodings).
|
||||
2. Keep APIs offline-friendly; no network dependencies.
|
||||
3. Coordinate schema and bundle changes with Scanner, Evidence Locker, CLI, and Docs guilds.
|
||||
4. Update module `TASKS.md` statuses alongside `docs/implplan/SPRINT_0185_0001_0001_shared_replay_primitives.md`.
|
||||
|
||||
## Contacts
|
||||
- BE-Base Platform Guild (primary)
|
||||
|
||||
@@ -1,17 +0,0 @@
|
||||
# StellaOps.Replay.Core task board
|
||||
|
||||
Keep this table in sync with `docs/implplan/SPRINT_0185_0001_0001_shared_replay_primitives.md`.
|
||||
|
||||
| Task ID | Status | Owners | Notes |
|
||||
| --- | --- | --- | --- |
|
||||
| REPLAY-CORE-185-001 | DONE (2025-11-25) | BE-Base Platform Guild | Library scaffolding: manifest schema types, canonical JSON rules, Merkle utilities, DSSE payload builders. |
|
||||
| REPLAY-CORE-185-002 | DONE (2025-11-25) | Platform Guild | Deterministic bundle writer (tar.zst, CAS naming) and hashing abstractions; update platform architecture doc with “Replay CAS” subsection. |
|
||||
| REPLAY-CORE-185-003 | DONE (2025-11-25) | Platform Data Guild | Mongo collections (`replay_runs`, `replay_bundles`, `replay_subjects`) and indices aligned with schema doc. |
|
||||
| DOCS-REPLAY-185-003 | DONE (2025-11-25) | Docs Guild · Platform Data Guild | `docs/data/replay_schema.md` detailing collections, index guidance, offline sync strategy. |
|
||||
| DOCS-REPLAY-185-004 | DONE (2025-11-25) | Docs Guild | Expand `docs/replay/DEVS_GUIDE_REPLAY.md` with integration guidance and deterministic replay checklist. |
|
||||
| POLICY-GAPS-185-006 | DONE (2025-12-03) | Policy Guild · Platform Guild | Policy simulation gaps PS1–PS10 remediated: inputs lock schema/sample + DSSE-ready verifier, shadow isolation validator, offline CLI verifier script. |
|
||||
|
||||
## Status rules
|
||||
- Use TODO → DOING → DONE/BLOCKED and mirror every change in the sprint Delivery Tracker.
|
||||
- Note dates in parentheses when flipping to DOING/DONE for traceability.
|
||||
- Capture contract or runbook changes in the relevant docs under `docs/replay` or `docs/data`.
|
||||
Reference in New Issue
Block a user