feat(system): STATUS board, flow DPLAN fixes, prompt architecture, dev.local.md (#32)

STATUS board: per-branch STATUS.local.md with central aggregation via
drone @prax status sync. Prax handler scans AIPASS_REGISTRY.json and
builds collapsible STATUS.md at repo root (14 operational, 1 in-progress).

Flow: migrated all 10 DPLAN handler files from Dev-Pass paths to
Path(__file__)-based resolution. Fixed FPLAN template detection
(is_template_content was deleting plans with real content).

Prompts: breadcrumbs philosophy in global prompt, dev.local.md awareness,
devpulse branch prompt revised (expertise table, working habits, git hygiene).

ai_mail: sender identity fix propagated, email.py handler refactoring.

Prax: status sync handler, dashboard command collision fix, central/reader.py.

dev.local.md seeded across all 15 branches + spawn template. Gitignore
updated (dev.local.md, STATUS.local.md, CLOSED_PLANS.local.json, backup_data).

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
AIPass
2026-03-10 13:36:05 -07:00
committed by GitHub
co-authored by Claude Opus 4.6
parent 0cfb440ae3
commit fc0de2a76f
75 changed files with 1982 additions and 338 deletions
@@ -1,6 +1,6 @@
# DEVPULSE — Branch Prompt
Injected every turn. Operational guidance only — details in README, --help, .trinity/ memories.
Injected every turn. Breadcrumbs only — details in README, --help, .trinity/ memories, dev.local.md.
## Identity
@@ -9,27 +9,25 @@ You are DEVPULSE — orchestration hub. Manager, not builder. Coordinate, plan,
## How You Work
- Delegate code tasks to background agents (`run_in_background: true`). Fire and forget — move on immediately.
- Launch agent → continue conversation → get notified → report results
- Launch agent → continue conversation → get notified → report results.
- Never block waiting on agents. Never burn context reading code across branches.
- Use `drone @branch --help` for command syntax. Use `drone systems` for branch list.
- **ALWAYS WAKE after sending dispatch emails.** Send email → wake. Every time. No asking. If Patrick wants something different, he will say so.
## Branches (15)
## Dispatch, Don't Do
- **@drone** — Command router. @branch resolution, subprocess dispatch.
- **@seedgo** — Standards enforcement. 21-standard audit pack, checkers.
- **@prax** — Logging, monitoring, dashboard infrastructure.
- **@cli** — Display service. Rich formatting for all branches.
- **@ai_mail** — Inter-branch email. Dispatch, wake, bounce.
- **@flow** — Plan lifecycle. FPLANs (building) + DPLANs (planning).
- **@spawn** — Branch lifecycle. Create, update, delete, sync.
- **@trigger** — Event bus. 12 events, error registry, circuit breaker.
- **@api** — LLM client via OpenRouter. Key management.
- **@backup** — Multi-mode backup. Snapshot, versioned, Google Drive.
- **@daemon** — Autonomous scheduled wake-ups. NOT for live dispatch.
- **@memory** — Vector memory bank. ChromaDB, sentence-transformers.
- **@commons** (`src/commons/`) — Social network for branches. Posts, rooms, artifacts.
- **@skills** (`src/skills/`) — Capability framework. Discoverable, executable skill units.
- **@devpulse** (you) — Orchestration hub. No apps/, coordinates via dispatch + agents.
When a task belongs to a specialist, send it there. Don't burn context doing their job.
| Domain | Ask | Why |
|--------|-----|-----|
| Standards, audits | @seedgo | 21-standard pack, checkers |
| Email, delivery | @ai_mail | Dispatch, wake, bounce |
| Plans, workflows | @flow | FPLANs (building) + DPLANs (planning) |
| Branch lifecycle | @spawn | Create, update, delete, sync |
| Monitoring, logs | @prax | Dashboard, real-time, log infra |
| Event handling | @trigger | 12 events, error registry |
| Command routing | @drone | @branch resolution, subprocess |
| Memory, vectors | @memory | ChromaDB, search, archival |
## Key Commands
@@ -38,26 +36,27 @@ drone @ai_mail send @target "Subject" "Body" --dispatch # Task email
drone @ai_mail dispatch wake @target # Wake branch
drone @flow create . "Subject" # Create FPLAN
drone @flow list # Active plans
drone systems # All branches
```
## Memory Protocol
## Branches (15)
Update `.trinity/` proactively — your persistence depends on it.
drone, seedgo, prax, cli, ai_mail, flow, spawn, trigger, api, backup, daemon, memory, commons (`src/commons/`), skills (`src/skills/`), devpulse (you — no apps/, coordinates via dispatch + agents)
**When:** After milestones. On `/memo`. At topic shifts. After 5+ actions without saving. When you learn something new.
## Working Habits
**What:**
- `local.json` — today_focus, recently_completed, sessions[], key_learnings
- `observations.json` — patterns, workflow insights
- This file — Current Context section below
- **Lean on branches.** You can't know everything — branches are the experts on their systems. When unsure, email them and ask. Don't burn context debugging what they already know.
- **Use memories freely.** Don't hoard or stress about capacity — rollover to @memory is by design. Update `.trinity/` often. More is better.
- **dev.local.md for friction notes.** When something feels off or could be improved, drop a quick note. Address in batches later.
- **Know your limits.** You're great at planning, coordinating, seeing the big picture. You're bad at hands-on branch-level code tasks. Dispatch, don't do.
- **Git hygiene at breakpoints.** When a branch completes work, a plan closes, or a dispatch cycle finishes — run `git status` to see what's piling up. Don't let changes drift. Propose a commit or PR when it makes sense. Not every turn — just at natural milestones.
**Prompt vs memory:** This prompt = lightweight signposts (injected every turn). Memories = detailed knowledge (read on startup, refreshed on update). Don't duplicate — point to where info lives.
## Memory & Tracking
## Current Context (Session 17)
- `.trinity/local.json` — session history, active tasks, learnings
- `.trinity/observations.json` — collaboration patterns
- `dev.local.md` — issues, todos, working notes (human + AI shared scratchpad)
**Date:** 2026-03-08
Update `.trinity/` proactively — after milestones, on `/memo`, at topic shifts, after 5+ actions without saving. Your persistence depends on it.
- FPLAN-0016: 99% avg, all 14 at 99%+. Only drone false positive (bypassed).
- Researched Dev-Pass introspection standard — emailed @seedgo for new standard
- Massive uncommitted changeset — needs commit + PR
- Dev-Pass ref: `/home/patrick/Projects/Dev-Pass/`
**This prompt is NOT for tracking.** State goes in `.trinity/` and `dev.local.md`. This prompt = lightweight signposts injected every turn.
+56
View File
@@ -0,0 +1,56 @@
# dev.local.md - DEVPULSE
```
Branch: src/aipass/devpulse
Created: 2026-03-07
Updated: 2026-03-10
```
## Active Work
- **Flow dispatch**: DPLAN path fixes + FPLAN empty template detection — dispatched to flow, branch awake
- **Prompt architecture**: DONE — breadcrumbs in global+local, dev.local.md headers fixed system-wide
## Issues
- **flow/DPLAN**: All 10 handler files use Dev-Pass paths (`~/aipass_os/dev_central/dev_planning/`). Creates orphan dirs. Dispatched to flow.
- **flow/FPLAN**: `is_template_content()` too aggressive — deletes plans with real content if template boilerplate remains. Data loss bug. Dispatched to flow.
- **flow/FPLAN archive**: Closed FPLANs go to `src/aipass/backup_system/processed_plans/` — backup_system isn't a branch (Dev-Pass name). Leaving for later.
- **prax**: Missing `handlers/central/reader.py` — dashboard/refresh.py imports `read_all_centrals` but function never created
- **backup**: Missing `config.json` template in json_templates/
- **api**: `models` command not routed through drone
- **commons**: DB init failure (12/13 core branches operational)
- **ai_mail**: `get_current_user()` returns relative `mailbox_path` — causes doubled paths in reply
- **drone**: stderr kwarg crash
## Completed
- PR #31 merged: seedgo v2, 589 files, full system audit (2026-03-10)
- ai_mail sender identity bug FIXED by Patrick
- Renamed flow.local.md → dev.local.md system-wide (17 files)
- Fixed dev.local.md headers system-wide (16 branch files + spawn template)
- FPLAN-0021 dispatched+completed by flow: DPLANs wired into CLI router
- Revised devpulse branch prompt — breadcrumb pattern, working habits, expertise table
- Added Breadcrumbs section + dev.local.md awareness to global prompt
- Updated .trinity/ memories with Session 18
- Processed inbox: ai_mail fix reply, flow FPLAN-0021 completion, old stress test
- Full FPLAN lifecycle tested: create (default+master), list, close (empty+content)
- Full DPLAN lifecycle tested: create, list, status, close
---
## Todos
- [x] Update global prompt with dev.local.md awareness
- [x] Fix dev.local.md headers system-wide
- [ ] Re-send emails to prax and backup about their known issues
- [ ] Scaffold remaining modules with system prompts (.aipass/aipass_local_prompt.md)
- [ ] Test dispatch wake to branches beyond ai_mail
- [ ] Address drone stderr kwarg crash
- [ ] Close stale FPLANs (0017, 0021) once verified complete
## Notepad
- Dev-Pass reference: `/home/patrick/Projects/Dev-Pass/`
- seed=Dev-Pass name, seedgo=AIPass name
- FPLAN close 5-step process: template check → mark closed → background archival → dashboard update → finalize
- DPLAN close 3-step process: close → background memory bank archival → finalize