skynet/claude-foundations
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore: end-session — log, clear stale CONTEXT block, FUTURE idea

Browse Source 
Session log for the explore-minimax build; remove stale 2026-06-12
unpushed-commits block (all six repos verified in sync); FUTURE entry for
extending /explore-minimax to more modes and parallel sweeps.

Claude-Session: https://claude.ai/code/session_01Ku87DDWwbJkTx6SuV3sQDc
This commit is contained in:
Paul O'Reilly
2026-09-11 11:38:25 +12:00
parent 468d75b224
commit bb03070e69
2 changed files with 32 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
FUTURE.md
View File

@@ -4,6 +4,15 @@ Backlog of improvement ideas not on the active roadmap.
---
## Extend /explore-minimax to more modes and parallel sweeps
- **Problem:** MiniMax-backed exploration (2026-09-11) is only wired into deep, deep-fable, and orch mode guidance, and runs one synchronous sweep at a time; quick/hybrid modes still use Anthropic subagents for all searches.
- **Idea:** After a few weeks of real use, extend the preference to `quick.md`/`hybrid.md` if answer quality holds, and add a parallel pattern (multiple `explore-minimax-run` invocations via background Bash with distinct roots/questions) for dataset-wide audits.
- **Open questions:** What's the observed false-citation rate in practice? Is 540s enough for very-thorough sweeps on large repos? Should the citation spot-check be automated (script greps each cited line)?
- **Depends on:** Usage data from deep/deep-fable sessions
---
## Standing Deployment Authorization in CLAUDE.md
- **Problem:** Claude has all the tooling needed to run deployment steps (sops, ansible-playbook, kubectl, docker, git push) but must ask for confirmation every time because these are irreversible, shared-infrastructure operations. This makes multi-step milestone deployments slow and interactive.