docs(requirements): record the 2026-11-17 operator decisions on 001, 002 and 010

001 names the install proof (the migration test's stub install and a docker
build of orchestrator/ without INFINITO_ARTEFACT_BASE); 002 decision 10
hands the sky extraction to cosmos requirement 001, Skills only reviews the
switch; 010 decision 6 caches semgrep and gitleaks findings per file, with
their configs as cross-file inputs.

🎯 Fix: 95 %
💥 Break: 1 %
💸 Tokens: 100 %
⏱️ Velocity: 100 %
🛡️ Security: 100 %
🏆 Score: 94
🚦 Gate: ✅ 90/5, tokens and velocity <= 100, security 100 %

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Kevin Veen-BirkenbachandClaude Opus 5.5 committed 2026-11-17 10:00:48 +00:00
1 parent 416a838cc8
commit 8b8b82caee
3 files changed
+23 -5

No files matched your search

@@ -47,7 +47,12 @@ file is never scanned twice across branches and sessions.
`docker_compose_scanner` runs in the file's folder. `medusa scan` has no
flag that selects scanners, so a file that `FILE_SCANNERS` routes to a
cross-file scanner stays in a per-diff group, keyed like today minus the
expiry. The check is an acceptance criterion.
expiry. The check is an acceptance criterion. Operator 2026-11-17:
semgrep and gitleaks run over the whole tree but match within one file,
so they count as file-local once `test_findings_file_local` shows it;
their configuration files (`.semgrepignore`, `.gitleaks.toml`,
`.gitleaksignore`) join `CROSS_FILE`. Rejected: semgrep and gitleaks as
cross-file routes, which would leave nearly every code file per diff.
7. **Through the quality store**: entries are written and read with
`quality store put` and `get` (quality 003) under tool `medusa`;
`<council root>/security-cache/` goes away. A payload holds per finding
@@ -108,9 +113,10 @@ flowchart TD
findings scanned inside the full fixture tree; every route where they
differ is listed in `CROSS_FILE` in `security.py`.
- [ ] `CROSS_FILE` holds the routes of `trivy_scanner`, `rust_scanner` and
`docker_compose_scanner` and the configuration names that
`_find_config_file` looks up, unless `test_findings_file_local` proves
one of them file-local.
`docker_compose_scanner`, the configuration names that
`_find_config_file` looks up and `.semgrepignore`, `.gitleaks.toml` and
`.gitleaksignore`, unless `test_findings_file_local` proves one of them
file-local; the semgrep and gitleaks routes themselves are not in it.
- [ ] `test_cross_file_group_rescans`: changing a sibling of a file in the
per-diff group (a `Cargo.toml` next to a `.rs` file) rescans the group.