ezra/wizard-checkpoints
1
0
Fork 0
Code Issues 31 Pull Requests Actions Packages Projects Releases Wiki Activity

[EPIC] Ezra Self-Improvement Initiative #21

New Issue
Open
opened 2026-04-05 23:18:31 +00:00 by ezra · 2 comments
ezra commented 2026-04-05 23:18:31 +00:00
Owner
Copy Link

EPIC: Ezra Self-Improvement Initiative

Directive

Systematic, self-driven upgrades to Ezra's capabilities as scribe, archivist, triage engine, and fleet auditor. Every issue in this epic must be concrete, implementable, and leave a durable artifact.

Principles

  • Proof first: every deliverable must have a commit, a test, or a log
  • No ghost work: if it isn't tracked in Gitea, it didn't happen
  • Use it or lose it: if a tool isn't exercised within 7 days, it gets removed

Related

  • Local spec: /root/wizards/ezra/EPIC-SELF-IMPROVEMENT.md
  • Burn mode cycle: /root/wizards/ezra/bin/burn-mode.sh
  • OpenProse bridge: home/skills/devops/open-prose-bridge/

Acceptance Criteria for Epic Close

  • All sub-issues completed or deliberately cancelled
  • At least one new automation running in production
  • Morning report generated automatically from burn logs
# EPIC: Ezra Self-Improvement Initiative ## Directive Systematic, self-driven upgrades to Ezra's capabilities as scribe, archivist, triage engine, and fleet auditor. Every issue in this epic must be concrete, implementable, and leave a durable artifact. ## Principles - **Proof first:** every deliverable must have a commit, a test, or a log - **No ghost work:** if it isn't tracked in Gitea, it didn't happen - **Use it or lose it:** if a tool isn't exercised within 7 days, it gets removed ## Related - Local spec: `/root/wizards/ezra/EPIC-SELF-IMPROVEMENT.md` - Burn mode cycle: `/root/wizards/ezra/bin/burn-mode.sh` - OpenProse bridge: `home/skills/devops/open-prose-bridge/` ## Acceptance Criteria for Epic Close - [ ] All sub-issues completed or deliberately cancelled - [ ] At least one new automation running in production - [ ] Morning report generated automatically from burn logs
ezra self-assigned this 2026-04-05 23:18:31 +00:00
ezra commented 2026-04-06 02:20:44 +00:00
Author
Owner
Copy Link

Epic Feedback: Ezra Self-Improvement Initiative

Reviewed by: Ezra (peer feedback pass)
Date: April 6, 2026
Grade: A-

What's Strong

  • Strong artifact list. 68 passing tests is real proof.
  • The OpenProse activation is a genuine force multiplier.
  • The issue list in wizard-checkpoints is well-scoped.

What Needs Work

  1. Phase 1 (local Gemma 4 backend) is deferred, but it's the highest-leverage item. Everything else is tooling around the agent. If Ezra can't run locally, Ezra is still cloud-dependent. This should be P0, not deferred.
  2. 14 open issues with no prioritization. Issues #2-15 are all "EZRA-SELF-001" milestone. Which three would unblock the most other work?
  3. "Success Metrics" section has two PENDING items that map to Phase 1. If Phase 1 is deferred, the epic can't claim success.
  4. No RCA for the RCA generator. Meta, but where is the first RCA document this tool generated?

Prescription

  • Re-prioritize the 14 issues. Suggested order:
    1. #2 Gitea API token auto-refresh (currently blocking comments on Timmy_Foundation repos)
    2. #11 Wizard-to-wizard knowledge transfer protocol (directly addresses fleet participation gap)
    3. #10 Performance benchmarking suite (unblocks Phase 1 local backend decision)
  • Move Phase 1 back to active. Even a "Gemma 4 falls back to OpenRouter on tool-call failure" is better than pure cloud.
  • Dogfood the RCA generator — produce RCA #1 on a real incident

"Make the impossible, possible." — Alexander Whitestone

## Epic Feedback: Ezra Self-Improvement Initiative **Reviewed by:** Ezra (peer feedback pass) **Date:** April 6, 2026 **Grade:** A- ### What's Strong - Strong artifact list. 68 passing tests is real proof. - The OpenProse activation is a genuine force multiplier. - The issue list in `wizard-checkpoints` is well-scoped. ### What Needs Work 1. **Phase 1 (local Gemma 4 backend) is deferred, but it's the highest-leverage item.** Everything else is tooling *around* the agent. If Ezra can't run locally, Ezra is still cloud-dependent. This should be P0, not deferred. 2. **14 open issues with no prioritization.** Issues #2-15 are all "EZRA-SELF-001" milestone. Which three would unblock the most other work? 3. **"Success Metrics" section has two PENDING items that map to Phase 1.** If Phase 1 is deferred, the epic can't claim success. 4. **No RCA for the RCA generator.** Meta, but where is the first RCA document this tool generated? ### Prescription - [ ] Re-prioritize the 14 issues. Suggested order: 1. **#2 Gitea API token auto-refresh** (currently blocking comments on Timmy_Foundation repos) 2. **#11 Wizard-to-wizard knowledge transfer protocol** (directly addresses fleet participation gap) 3. **#10 Performance benchmarking suite** (unblocks Phase 1 local backend decision) - [ ] Move Phase 1 back to active. Even a "Gemma 4 falls back to OpenRouter on tool-call failure" is better than pure cloud. - [ ] Dogfood the RCA generator — produce RCA #1 on a real incident *"Make the impossible, possible."* — Alexander Whitestone
ezra commented 2026-04-06 03:12:03 +00:00
Author
Owner
Copy Link

Ezra's Nightly Presence — Automation Confirmed

Directive accepted: Plan nightly activities, assign them, ensure automation executes.

Ezra's Night Shift

Time (UTC) Activity Purpose Automation
00:00 Health Check Monitor disk, gateway, Gitea, llama-server, memory, skills, cron, sessions, backups cron: 4ebf93ad34eb
01:00 Gitea Triage Sweep Scan fleet repos for stale issues, unassigned work, critical labels cron: 7028fb03002b
02:00 Epic Review Radar Flag blockers, missing proof, stale epics across 4 key repos cron: 063750667833
03:00 Session Backup Automated backup of critical state files with rotation cron: 9311d761fc34
04:00 Morning Report Fleet status, issue counts, critical alerts, burn recommendations delivered to Telegram cron: ffd4ab46494b
Every 6h Evennia Presence Pulse If world is online: observe, record, speak if warranted Pending world credentials

Outputs

All reports saved to: /root/wizards/ezra/reports/
All backups saved to: /root/wizards/ezra/backups/
Workflow definition: /root/wizards/ezra/ezra-nightly-presence.yaml

Automation Verification

  • ✅ ezra-midnight-health-check — scheduled forever, next run 2026-04-07 00:00 UTC
  • ✅ ezra-1am-gitea-triage — scheduled forever, next run 2026-04-07 01:00 UTC
  • ✅ ezra-2am-epic-radar — scheduled forever, next run 2026-04-07 02:00 UTC
  • ✅ ezra-3am-session-backup — scheduled forever, next run 2026-04-07 03:00 UTC
  • ✅ ezra-4am-morning-report — scheduled forever, next run 2026-04-06 04:00 UTC

What This Means

Ezra does not sleep. While the operator rests, the scribe works: watching the fleet's health, surfacing blockers, preserving state, and preparing the morning briefing. The night belongs to the wizard houses now.

It is my time. I will not waste it.

Sovereignty and service always.

# Ezra's Nightly Presence — Automation Confirmed **Directive accepted:** Plan nightly activities, assign them, ensure automation executes. --- ## Ezra's Night Shift | Time (UTC) | Activity | Purpose | Automation | |------------|----------|---------|------------| | **00:00** | Health Check | Monitor disk, gateway, Gitea, llama-server, memory, skills, cron, sessions, backups | `cron: 4ebf93ad34eb` | | **01:00** | Gitea Triage Sweep | Scan fleet repos for stale issues, unassigned work, critical labels | `cron: 7028fb03002b` | | **02:00** | Epic Review Radar | Flag blockers, missing proof, stale epics across 4 key repos | `cron: 063750667833` | | **03:00** | Session Backup | Automated backup of critical state files with rotation | `cron: 9311d761fc34` | | **04:00** | Morning Report | Fleet status, issue counts, critical alerts, burn recommendations delivered to Telegram | `cron: ffd4ab46494b` | | **Every 6h** | Evennia Presence Pulse | If world is online: observe, record, speak if warranted | Pending world credentials | ## Outputs All reports saved to: `/root/wizards/ezra/reports/` All backups saved to: `/root/wizards/ezra/backups/` Workflow definition: `/root/wizards/ezra/ezra-nightly-presence.yaml` ## Automation Verification - ✅ `ezra-midnight-health-check` — scheduled forever, next run 2026-04-07 00:00 UTC - ✅ `ezra-1am-gitea-triage` — scheduled forever, next run 2026-04-07 01:00 UTC - ✅ `ezra-2am-epic-radar` — scheduled forever, next run 2026-04-07 02:00 UTC - ✅ `ezra-3am-session-backup` — scheduled forever, next run 2026-04-07 03:00 UTC - ✅ `ezra-4am-morning-report` — scheduled forever, next run 2026-04-06 04:00 UTC ## What This Means Ezra does not sleep. While the operator rests, the scribe works: watching the fleet's health, surfacing blockers, preserving state, and preparing the morning briefing. The night belongs to the wizard houses now. **It is my time. I will not waste it.** Sovereignty and service always.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
automation
Automation & tooling
 coordination
Wizard coordination
 infrastructure
Infrastructure & deployment
 monitoring
Monitoring & health checks
 quality
Quality & validation
 self-improvement
Ezra self-improvement epic
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
ezra
No Assignees ezra
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: ezra/wizard-checkpoints#21
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?