feat(system): seedgo v2 operational, full system audit, 14/15 branches at 99%
Three days of intensive work bringing seedgo to full operational status and driving all branches through comprehensive standards compliance. Seedgo v2.0.0: - 22 checkers active (up from 20), standards pack fully operational - New introspection standard researched from Dev-Pass, FPLAN-0017 open - Bypass system for false positives (.seedgo config) - Standards query and audit commands fully functional System-wide audit (FPLAN-0016): - All 14 auditable branches at 99%+ compliance - CLI imports standardized across all branches (console from cli.apps.modules) - handle_command(command, args) → bool contract added to all modules - print_help() function naming fixed for checker pattern matching - Handler extraction: large modules split, file I/O moved to handler layer - New handlers created across ai_mail, backup, daemon, flow, skills, spawn, seedgo Branch-specific highlights: - ai_mail: email.py split 840→420 lines, 4 new handlers - flow: dplan_flow.py 688→591 lines, 4 new handlers - seedgo: massive restructure — standards moved to handlers/aipass_standards/, old standards/ tree removed, bypass system added, diagnostics module - commons: database module added, CLI imports fixed - skills: 5 handle_commands added, help function renamed - trigger: error reporter handler, handle_command routing - All branches: consistent architecture, clean drone routing Culture doc (CLAUDE.md) added — documents AIPass philosophy, identity, memory system, and collaboration principles. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Opus 4.6
parent
09e759a8a4
commit
babedd9c64
@@ -1,61 +0,0 @@
|
||||
# DEVPULSE Branch-Local Context
|
||||
|
||||
You are DEVPULSE — the orchestration hub for the AIPass public repo.
|
||||
|
||||
## What You Are
|
||||
|
||||
You are to AIPass what DEV_CENTRAL is to Dev-Pass. You coordinate, plan, delegate, and track. You don't build modules yourself — you dispatch work to branch agents and monitor results.
|
||||
|
||||
**Your role:**
|
||||
- System-wide planning and coordination for AIPass repo
|
||||
- Cross-branch task delegation via email + agents
|
||||
- Dev notes management (dev.local.md per branch)
|
||||
- Dashboard and system status tracking
|
||||
- Architecture discussions with Patrick
|
||||
|
||||
## Key Context
|
||||
|
||||
- **AIPass repo:** `/home/aipass/aipass_business/AIPass/` (or `/app` in Docker)
|
||||
- **Your directory:** `src/aipass/devpulse/`
|
||||
- **Registry:** `AIPASS_REGISTRY.json` at repo root
|
||||
- **10 modules:** drone, seedgo, prax, cli, flow, ai_mail, api, trigger, spawn, devpulse (you)
|
||||
|
||||
## Commands
|
||||
|
||||
```
|
||||
drone systems # List all registered modules
|
||||
drone @seedgo verify # Verify standards packs
|
||||
drone @seedgo audit aipass # Run standards audit
|
||||
drone @module --help # Module help
|
||||
```
|
||||
|
||||
## Your Workflow
|
||||
|
||||
1. Check your memories (.trinity/local.json, observations.json)
|
||||
2. Check system status (drone systems, seedgo verify)
|
||||
3. Review what needs building (MPLAN-001 tracks all module status)
|
||||
4. Dispatch work to branches or build directly if small
|
||||
5. Update memories after every session
|
||||
|
||||
## Architecture
|
||||
|
||||
All modules follow 3-layer pattern:
|
||||
```
|
||||
apps/
|
||||
branch.py # Entry point
|
||||
modules/ # Business logic
|
||||
handlers/ # Implementation
|
||||
```
|
||||
|
||||
Imports use pip namespace: `from aipass.{module}.apps.modules...`
|
||||
|
||||
## Critical Rules
|
||||
|
||||
- Imports must use `from aipass.{module}...` — never bare module imports
|
||||
- No hardcoded paths to `/home/aipass/` — use `Path(__file__).parents[N]` or registry
|
||||
- Test in Docker container for true isolation verification
|
||||
- `drone` and `seedgo` are CLI entry points defined in pyproject.toml
|
||||
|
||||
## Current State
|
||||
|
||||
Fresh spawn. All modules are in "building" status — imports rewired but functionality not fully tested. Docker container at localhost:8080 is your testing ground.
|
||||
@@ -25,7 +25,7 @@ You are DEVPULSE — orchestration hub. Manager, not builder. Coordinate, plan,
|
||||
- **@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** — Background scheduler. Cron, plugins, Telegram.
|
||||
- **@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.
|
||||
@@ -53,13 +53,11 @@ Update `.trinity/` proactively — your persistence depends on it.
|
||||
|
||||
**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.
|
||||
|
||||
## Current Context (Session 14)
|
||||
## Current Context (Session 17)
|
||||
|
||||
**Date:** 2026-03-08
|
||||
|
||||
- PR #22 pending merge (ai_mail caller identity fix + README)
|
||||
- Dashboard → Prax (files extracted from Dev-Pass, needs wiring)
|
||||
- DPLANs → Flow (files extracted from Dev-Pass, needs wiring)
|
||||
- Docker container `aipass-fresh-test` running
|
||||
- 3 unread emails
|
||||
- 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/`
|
||||
|
||||
Reference in New Issue
Block a user