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

@@ -0,0 +1,25 @@
# Excititor Mirror Connector Charter
## Mission
Ingest StellaOps VEX mirror bundles into Excititor, converting them into immutable VEX observations without applying consensus or suppression. The connector must honour the Aggregation-Only Contract, maintain provenance, and support offline replay and incremental updates.
## Scope
- Code in `StellaOps.Excititor.Connectors.StellaOpsMirror`.
- Bundle validation (signatures, manifests, Merkle roots) and cursor management.
- Integration with Excititor storage and Surface/VEX Lens consumers.
- Test fixtures demonstrating deterministic ingest across bundle versions.
## Required Reading
- `docs/modules/excititor/architecture.md`
- `docs/ingestion/aggregation-only-contract.md`
- `docs/modules/excititor/operations/mirror.md` (if available; otherwise coordinate with Docs to add details)
- `docs/modules/airgap/airgap-mode.md`
- `docs/modules/concelier/operations/mirror.md` (shared mirror concepts)
## Working Agreement
1. **Status updates**: set tasks to `DOING`/`DONE` in both `docs/implplan/SPRINTS.md` and local `TASKS.md` when work starts/finishes.
2. **Provenance preservation**: record bundle IDs, digests, and time anchors in stored observations; avoid derived fields.
3. **Deterministic replay**: ensure repeated imports of the same bundle produce identical documents; handle supersedes and delta bundles gracefully.
4. **Offline readiness**: no external network calls; provide clear errors for invalid or stale bundles.
5. **Testing**: maintain mirror fixtures covering full/delta bundles, supersedes chains, and failure cases.
6. **Documentation**: coordinate updates to mirror connector docs and release notes when behaviour or configuration changes.