Timmy_Foundation/timmy-config
15
0
Fork 0
Code Issues 114 Pull Requests 10 Actions Packages Projects Releases Wiki Activity

[EPIC] Harden Gemini Sovereign Infrastructure Suite after merge #418 #432

New Issue
Open
opened 2026-04-09 14:32:35 +00:00 by Timmy · 0 comments
Timmy commented 2026-04-09 14:32:35 +00:00
Owner
Copy Link

Context

  • PR #418 merged the Gemini Sovereign Infrastructure Suite that closed epic #398.
  • The suite is directionally strong, but the merged code still contains trust shortcuts that need post-merge hardening.
  • This epic tracks the work needed to keep the systematization while removing unsafe operational posture.

Merged-code evidence that motivated this backlog

  • scripts/agent_dispatch.py: hard-coded host IPs, StrictHostKeyChecking=no, and user task text interpolated into a remote command string.
  • scripts/fleet_llama.py, scripts/self_healing.py, scripts/telemetry.py, and scripts/provision_wizard.py: disabled SSH host verification and/or shell-string execution patterns.
  • scripts/self_healing.py: main() runs a healing cycle unconditionally, so --help is not side-effect safe.
  • scripts/architecture_linter_v2.py: rule logic depends on repo basename and currently diverges from the suite it ships with.

Desired outcome

  • The Gemini suite remains in timmy-config as sovereign infrastructure.
  • Fleet topology, trust policy, and execution contracts move out of ad-hoc script literals and into explicit configuration + tested interfaces.
  • Unsafe defaults are removed before more autonomous behavior is layered on top.

Child issues

  • #433 [GEMINI-HARDEN-01] Replace hard-coded fleet inventory with repo-native config
  • #434 [GEMINI-HARDEN-02] Enforce verified SSH trust and safe remote execution in scripts/
  • #435 [GEMINI-HARDEN-03] Make self_healing.py safe-by-default, dry-run-first, and --help-safe
  • #436 [GEMINI-HARDEN-04] Build an authenticated webhook runner instead of a print-only payload parser
  • #437 [GEMINI-HARDEN-05] Make architecture_linter_v2 repo-aware, test-backed, and CI-enforced
  • #438 [GEMINI-HARDEN-06] Add a common CLI safety/test harness for the scripts/ suite

Related existing work

  • #238 source-controlled cron/deadman hardening
  • #288 Gitea webhook setup across org repos
  • #290 verified admin SSH access for Allegro
  • #356 agent dispatcher capability
  • #423 dead man switch fallback implementation
  • PR #430 fleet behaviour hardening / guardrails

Recommended order

  1. #433 inventory/path centralization
  2. #434 SSH trust + remote execution safety
  3. #435 self-healing safety contract
  4. #436 authenticated webhook runner
  5. #437 linter correctness + CI enforcement
  6. #438 suite-wide CLI/test harness
Context - PR #418 merged the Gemini Sovereign Infrastructure Suite that closed epic #398. - The suite is directionally strong, but the merged code still contains trust shortcuts that need post-merge hardening. - This epic tracks the work needed to keep the systematization while removing unsafe operational posture. Merged-code evidence that motivated this backlog - `scripts/agent_dispatch.py`: hard-coded host IPs, `StrictHostKeyChecking=no`, and user task text interpolated into a remote command string. - `scripts/fleet_llama.py`, `scripts/self_healing.py`, `scripts/telemetry.py`, and `scripts/provision_wizard.py`: disabled SSH host verification and/or shell-string execution patterns. - `scripts/self_healing.py`: `main()` runs a healing cycle unconditionally, so `--help` is not side-effect safe. - `scripts/architecture_linter_v2.py`: rule logic depends on repo basename and currently diverges from the suite it ships with. Desired outcome - The Gemini suite remains in `timmy-config` as sovereign infrastructure. - Fleet topology, trust policy, and execution contracts move out of ad-hoc script literals and into explicit configuration + tested interfaces. - Unsafe defaults are removed before more autonomous behavior is layered on top. Child issues - [ ] #433 [GEMINI-HARDEN-01] Replace hard-coded fleet inventory with repo-native config - [ ] #434 [GEMINI-HARDEN-02] Enforce verified SSH trust and safe remote execution in scripts/ - [ ] #435 [GEMINI-HARDEN-03] Make self_healing.py safe-by-default, dry-run-first, and --help-safe - [ ] #436 [GEMINI-HARDEN-04] Build an authenticated webhook runner instead of a print-only payload parser - [ ] #437 [GEMINI-HARDEN-05] Make architecture_linter_v2 repo-aware, test-backed, and CI-enforced - [ ] #438 [GEMINI-HARDEN-06] Add a common CLI safety/test harness for the scripts/ suite Related existing work - #238 source-controlled cron/deadman hardening - #288 Gitea webhook setup across org repos - #290 verified admin SSH access for Allegro - #356 agent dispatcher capability - #423 dead man switch fallback implementation - PR #430 fleet behaviour hardening / guardrails Recommended order 1. #433 inventory/path centralization 2. #434 SSH trust + remote execution safety 3. #435 self-healing safety contract 4. #436 authenticated webhook runner 5. #437 linter correctness + CI enforcement 6. #438 suite-wide CLI/test harness
Timmy added the enhancementepic labels 2026-04-09 14:32:35 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
assigned-claw-code
Queued for Code Claw (qwen/openrouter)
 assigned-kimi
Dispatched to Kimi via OpenClaw
 assigned-sonnet
claw-code-done
Code Claw completed this task
 claw-code-in-progress
Code Claw is actively working
 enhancement
epic
kimi-done
Kimi completed this task
 kimi-in-progress
Kimi is actively working on this
 lazzyPit
Lazarus Pit automated recovery system
 research
sonnet-ready
velocity-engine
Auto-generated by velocity engine
No Label enhancement epic
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
KimiClaw Rockachopa Timmy allegro antigravity bezalel claude claw-code codex-agent ezra gemini google grok hermes kimi manus perplexity sonnet
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Timmy_Foundation/timmy-config#432
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?