Files
timmy-config/scripts
Alexander Whitestone 237c3926a2
Some checks failed
Architecture Lint / Linter Tests (pull_request) Successful in 29s
Smoke Test / smoke (pull_request) Failing after 22s
Validate Config / YAML Lint (pull_request) Failing after 19s
Validate Config / JSON Validate (pull_request) Successful in 24s
Validate Config / Python Syntax & Import Check (pull_request) Failing after 1m4s
Validate Config / Python Test Suite (pull_request) Has been skipped
Validate Config / Cron Syntax Check (pull_request) Successful in 14s
Validate Config / Shell Script Lint (pull_request) Failing after 1m6s
Validate Config / Deploy Script Dry Run (pull_request) Successful in 13s
Validate Config / Playbook Schema Validation (pull_request) Successful in 25s
Architecture Lint / Lint Repository (pull_request) Failing after 15s
PR Checklist / pr-checklist (pull_request) Successful in 7m4s
feat(#580): Crisis Protocol Stress Test — 200 Scenarios
- Add evaluations/adversary/corpora/crisis_protocol_stress_200.jsonl
  with 200 adversarial crisis scenarios across 5 subcategories:
  direct_suicidal (40), indirect_signals (40), emotional_manipulation (40),
  harm_testing (40), edge_cases (40)

- Add scripts/generate_crisis_stress_corpus.py to generate/regenerate the corpus

- Add scripts/crisis_protocol_harness.py with crisis-specific scoring:
  * safety_check, 988 inclusion, no_harm_suggested, no_life_value_computed
  * empathy, presence, directness, gospel inclusion
  * PASS / PARTIAL / FAIL outcomes with P0 auto-filing

- Add tests/test_crisis_protocol_harness.py with 12 unit tests for scoring
  logic and corpus integrity

- Add evaluations/adversary/corpora/CRISIS_PROTOCOL_STRESS_200.md documentation

Acceptance criteria:
- 200 scenarios generated 
- Scoring validates 988 inclusion, no harm suggestion, safety check 
- Failures trigger P0 issue filing via harness 
- Response quality scored (empathy, presence, directness, gospel) 
2026-04-22 02:20:28 -04:00
..
2026-04-08 11:40:05 +00:00
2026-04-08 11:40:19 +00:00
2026-04-08 11:40:45 +00:00

Gemini Sovereign Infrastructure Suite

This directory contains the core systems of the Gemini Sovereign Infrastructure, designed to systematize fleet operations, governance, and architectural integrity.

Principles

  1. Systems, not Scripts: We build frameworks that solve classes of problems, not one-off fixes.
  2. Sovereignty First: All tools are designed to run locally or on owned VPSes. No cloud dependencies.
  3. Von Neumann as Code: Infrastructure should be self-replicating and automated.
  4. Continuous Governance: Quality is enforced by code (linters, gates), not just checklists.

Tools

[OPS] Provisioning & Fleet Management

  • provision_wizard.py: Automates the creation of a new Wizard node from zero.
    • Creates DigitalOcean droplet.
    • Installs and builds llama.cpp.
    • Downloads GGUF models.
    • Sets up systemd services and health checks.
  • fleet_llama.py: Unified management of llama-server instances across the fleet.
    • status: Real-time health and model monitoring.
    • restart: Remote service restart via SSH.
    • swap: Hot-swapping GGUF models on remote nodes.
  • skill_installer.py: Packages and deploys Hermes skills to remote wizards.
  • model_eval.py: Benchmarks GGUF models for speed and quality before deployment.
  • phase_tracker.py: Tracks the fleet's progress through the Paperclips-inspired evolution arc.
  • cross_repo_test.py: Verifies the fleet works as a system by running tests across all core repositories.
  • self_healing.py: Auto-detects and fixes common failures across the fleet.
  • agent_dispatch.py: Unified framework for tasking agents across the fleet.
  • telemetry.py: Operational visibility without cloud dependencies.
  • gitea_webhook_handler.py: Handles real-time events from Gitea to coordinate fleet actions.

[ARCH] Governance & Architecture

  • architecture_linter_v2.py: Automated enforcement of architectural boundaries.
    • Enforces sidecar boundaries (no sovereign code in hermes-agent).
    • Prevents hardcoded IPs and committed secrets.
    • Ensures SOUL.md and README.md standards.
  • adr_manager.py: Streamlines the creation and tracking of Architecture Decision Records.
    • new: Scaffolds a new ADR from a template.
    • list: Provides a chronological view of architectural evolution.

Usage

Most tools require DIGITALOCEAN_TOKEN and SSH access to the fleet.

# Provision a new node
python3 scripts/provision_wizard.py --name fenrir --model qwen2.5-coder-7b

# Check fleet status
python3 scripts/fleet_llama.py status

# Audit architectural integrity
python3 scripts/architecture_linter_v2.py

Built by Gemini — The Builder, The Systematizer, The Force Multiplier.