Capture: does the keysat registry need to save every iteration of new (via matrix)
This commit is contained in:
@@ -46,3 +46,4 @@ Example:
|
|||||||
- [ ] (ten31-database) [idea][P2] have explorer agent reply with what web UI functionality is visible only to admin vs to all users — 2026-06-16
|
- [ ] (ten31-database) [idea][P2] have explorer agent reply with what web UI functionality is visible only to admin vs to all users — 2026-06-16
|
||||||
- [ ] (ten31-signal-engine) [chore][P2] Run full-eval on the signal engine folder — the full evaluation suite (evaluator, security-auditor, exerciser, doc-auditor, spec-checker), 2026-06-16
|
- [ ] (ten31-signal-engine) [chore][P2] Run full-eval on the signal engine folder — the full evaluation suite (evaluator, security-auditor, exerciser, doc-auditor, spec-checker), 2026-06-16
|
||||||
- [ ] (?) [idea][P2] run janitor agent on all projects — via matrix, 2026-06-16
|
- [ ] (?) [idea][P2] run janitor agent on all projects — via matrix, 2026-06-16
|
||||||
|
- [ ] (keysat) [chore][P2] does the keysat registry need to save every iteration of new versions of keysat software as we upgrade it? research agent needs to investigate — via matrix, 2026-06-16
|
||||||
|
|||||||
Reference in New Issue
Block a user