diff --git a/.codex/plans/2026-03-09-dependency-risk-mapping.md b/.codex/plans/2026-03-09-dependency-risk-mapping.md deleted file mode 100644 index c8a231e..0000000 --- a/.codex/plans/2026-03-09-dependency-risk-mapping.md +++ /dev/null @@ -1,24 +0,0 @@ -# Dependency Risk Mapping for metasystem-master - -Date: 2026-03-09 - -## Summary -- Use sibling repo `seed.yaml` `consumes` entries as the authoritative direct dependency graph. -- Reconcile conflicting directory and metadata signals inside `metasystem-master`. -- Generate a Markdown audit that distinguishes live backplane consumers from stale or archival metadata. -- Leave target-repo comparison as a runtime argument to avoid hard-coding an unresolved repo identity. - -## Implementation -- Add a Python utility under `tools/scripts/` to: - - enumerate direct dependents of `organvm-ii-poiesis/metasystem-master` - - classify active versus archived consumers - - flag stale metadata such as `.meta/dependencies.json` - - flag top-level archival directories that overlap the live repo surface - - optionally analyze a target repo for public-package, documented-runtime, and private-surface coupling -- Generate an initial Markdown audit under `docs/architecture/`. -- Clarify active versus historical directory boundaries in `README.md`. - -## Assumptions -- `seed.yaml` direct dependency declarations are canonical. -- `_archive/` is historical and should not be used as the live deployment or dependency surface. -- `ecosystem.yaml` and `.meta/dependencies.json` are advisory snapshots and may lag the true graph. diff --git a/.gitignore b/.gitignore index cf5e8c6..d5f3409 100644 --- a/.gitignore +++ b/.gitignore @@ -34,3 +34,13 @@ data/ # OS mnt/ ssl/ + +# Agent work records are kept in a private archive, not in public repos. +.claude/plans/ +.claude/handoffs/ +.codex/plans/ +.codex/receipts/ +.gemini/plans/ +.gemini/handoffs/ +.conductor/ +.specstory/ diff --git a/docs/plans/EXECUTION_PROTOCOL_ALPHA.md b/docs/plans/EXECUTION_PROTOCOL_ALPHA.md deleted file mode 100644 index 1311043..0000000 --- a/docs/plans/EXECUTION_PROTOCOL_ALPHA.md +++ /dev/null @@ -1,103 +0,0 @@ -# EXECUTION PROTOCOL ALPHA: Total Metasystem Synthesis - -**Target:** 115 Repositories across 3+ Organizations. -**Objective:** Transform a scattered archive into a unified, self-governing organism. -**Timeline:** 4 Weeks (Phased). - ---- - -## πŸ“… PHASE 1: SANITATION & STRUCTURAL INTEGRITY (Week 1) -*Goal: Physical reorganization. "A place for everything, and everything in its place."* - -### 1.1 The Commercial Schism (The Fourth Node) -**Action:** Establish the "Guild" organization to house production assets. -- [ ] **User Action:** Create new GitHub Org (e.g., `Aeterna-Ventures` or `Legion-Systems`). -- [ ] **Transfer:** Move `trade-perpetual-future` from `ivviiviivvi`. -- [ ] **Transfer:** Move `gamified-coach-interface` from `ivviiviivvi`. -- [ ] **Transfer:** Move `enterprise-plugin` from local workspace. -- [ ] **Update Remotes:** Update local git remotes for these 3 repos. - -### 1.2 The Great Archival -**Action:** Reduce cognitive load by explicitly marking "Dead" or "Legacy" code. -- [ ] **Archive:** `4444JPP/perpetual-future` (Legacy version). -- [ ] **Archive:** `omni-dromenon-machina/artist-toolkit-and-templates` (Duplicate). -- [ ] **Archive:** `ivviiviivvi/collective-persona-operations` (Merged concepts). -- [ ] **Tag:** Add `archive` topic to all `4444JPP` repos that are purely historical. - -### 1.3 Naming Standardization -**Action:** Enforce `kebab-case` and semantic prefixes. -- [ ] **Rename:** `4-ivi374-F0Rivi4` -> `organ-body-recursive`. -- [ ] **Rename:** `a-mavs-olevm` -> `site-etceter4`. -- [ ] **Rename:** `Intelligent-Agent-for-Microsoft-365-Automation` -> `agent-m365-automation`. - ---- - -## 🧬 PHASE 2: INOCULATION (Week 2) -*Goal: Identity injection. Every repo must know "Who am I?" and "Who do I serve?"* - -### 2.1 The Genome Script -**Action:** Create a Python script (`scripts/inoculate_seeds.py`) to mass-generate `seed.yaml` files. -- [ ] **Logic:** - - If `package.json` exists -> Type: `node/typescript`. - - If `requirements.txt` exists -> Type: `python`. - - If `org == 4444JPP` -> Role: `archive/origin`. - - If `org == ivviiviivvi` -> Role: `mythos/research`. -- [ ] **Execution:** Run script across all 115 cloned repos (in `Workspace` or via API). - -### 2.2 The Teleological Audit -**Action:** Manually verify the `seed.yaml` of High-Value Targets (HVTs). -- [ ] **Verify:** `life-my--midst--in` (Identity). -- [ ] **Verify:** `core-engine` (Orchestrator). -- [ ] **Verify:** `system-governance-framework` (Constitution). - ---- - -## 🧠 PHASE 3: THE NEURAL WEB (Week 3) -*Goal: Connectivity. The Brain must see the Body.* - -### 3.1 The Grand Map (`4jp-metasystem.yaml`) -**Action:** Expand the Orchestrator's map from 7 to 115. -- [ ] **Update:** Write a script to auto-generate the `workspaces` list in `4jp-metasystem.yaml` based on the `ECOSYSTEM.md` inventory. -- [ ] **Filter:** Set `status: dormant` for Archives, `status: active` for Mythos/Commercial. - -### 3.2 The Indexer (`cognitive-archaelogy-tribunal`) -**Action:** Activate the Tribunal to index the codebases. -- [ ] **Configure:** Point the Tribunal at the `4444JPP` org. -- [ ] **Task:** "Generate a Knowledge Graph of all reusable Python snippets in the Origin archives." -- [ ] **Output:** A vector database (Pinecone/Chroma) accessible to the **Architect Agent**. - -### 3.3 The Neural Link (Webhooks) -**Action:** Real-time event propagation. -- [ ] **Setup:** Configure GitHub Webhooks on the 3 Orgs (`ivviiviivvi`, `omni`, `[COMMERCIAL]`). -- [ ] **Payload:** Push events -> `https://omni-dromenon-core.../webhook/github`. -- [ ] **Response:** Core Engine triggers `NightWatchman` to check for drift. - ---- - -## βš–οΈ PHASE 4: ACTIVATION & GOVERNANCE (Week 4) -*Goal: Autonomy. The system begins to govern itself.* - -### 4.1 The Critic's Gate (CI/CD) -**Action:** Block bad code before it merges. -- [ ] **Workflow:** Create a shared GitHub Action (`.github/workflows/critic-guard.yml`). -- [ ] **Logic:** On PR -> Send diff to `omni-dromenon-core` -> Critic Agent reviews against `seed.yaml` -> Pass/Fail PR. -- [ ] **Deploy:** Push this workflow to all `active` repos. - -### 4.2 The Council (Strategy) -**Action:** High-level decision making. -- [ ] **Simulate:** Run a "Council Session" where `Architect`, `Alchemist`, and `Merchant` (AI Personas) debate the roadmap based on the new inventory. -- [ ] **Output:** A generated `roadmap_Q1_2026.md` committed to `omni-dromenon-machina/docs`. - -### 4.3 The Dashboard (Visualization) -**Action:** See the Galaxy. -- [ ] **Upgrade:** `performance-sdk` to render a Force-Directed Graph of the 115 repos. -- [ ] **Data:** Nodes = Repos, Edges = Dependencies (from Phase 2). -- [ ] **Color:** Blue = Origin, Purple = Mythos, Gold = Commercial, Grey = Archive. - ---- - -## πŸ“‰ SUCCESS METRICS (KPIs) -1. **Genome Coverage:** 100% of active repos have a valid `seed.yaml`. -2. **Drift Detection:** `NightWatchman` detects a change in `ivviiviivvi` within < 5 minutes. -3. **Governance Compliance:** 0% of "Commercial" repos contain "Mythos" experimental code (enforced by Critic). -4. **Visual Clarity:** User can see the status of `trade-perpetual-future` from the `omni-dromenon` dashboard. diff --git a/docs/plans/HANDOFF-PLAN--2026-04-28.md b/docs/plans/HANDOFF-PLAN--2026-04-28.md deleted file mode 100644 index 85d6aff..0000000 --- a/docs/plans/HANDOFF-PLAN--2026-04-28.md +++ /dev/null @@ -1,56 +0,0 @@ -# HANDOFF PLAN: Elevation Execution (PLAN-088) -**Date:** 2026-04-28 -**Target:** omni-dromenon-machina (Universal Master) -**Objective:** Execute the elevation of Hokage Chess and My-Knowledge-Base per SPEC-024. - -## I. Immediate Execution Stream (Surgical Actions) - -### Step 1: Metasystem Registration -* **Action:** Update `organvm/metasystem-master/.config/metasystem.yaml`. -* **Payload:** - ```yaml - workspaces: - - name: "hokage-chess" - path: "../../4444J99/hokage-chess" - type: "landing-page" - status: "elevation-pending" - tech_stack: ["next.js", "tailwind"] - - - name: "my-knowledge-base" - path: "../../organvm/my-knowledge-base" - type: "knowledge-engine" - status: "active" - tech_stack: ["typescript", "sqlite", "ollama"] - ``` - -### Step 2: Hokage Chess Node Activation -* **Action:** Execute build and deployment. -* **Sub-tasks:** - 1. `cd /Users/4jp/Workspace/4444J99/hokage-chess` - 2. Register domain `hokagechess.com` (Manual intervention required for payment/DNS setup). - 3. Configure Vercel project and link to GitHub. - 4. Wire ConvertKit API keys to `.env.production`. - 5. Run `npm run build` and verify output. - 6. Run `npx playwright test` to verify email funnel integrity. - -### Step 3: Theory Scaling (Wiki Compiler) -* **Action:** Implement `TheoryEngine` and resume synthesis. -* **Sub-tasks:** - 1. Initialize `VectorDatabase` with existing 154k embeddings. - 2. Run `TopicClusteringAnalyzer` to reduce 147k "Insights" into ~50-100 high-fidelity clusters. - 3. Modify `WikiCompiler.ts` to use `TheoryEngine` synthesis instead of raw unit extraction. - 4. Resume `Phase B` (Page Synthesis) in background mode. - ---- - -## II. Strategic Elevation Questions (For Master Deliberation) - -* **Pattern Extraction:** Can the `BatchProcessor` logic in `my-knowledge-base` be promoted to a core `omni-dromenon-machina` package for all large-scale LLM tasks? -* **Personal Space Cleanliness:** Should `4444J99/hokage-chess` be migrated to a dedicated `organvm-iii-ergon` (Commerce) repository post-elevation? -* **Failure Protocol:** At 154k units, a 10% failure threshold is 15.4k errors. Is this too high? Should the Master implement a "Tiered Sampling" verification phase for massive datasets? - ---- - -## III. Verification & Closure -* **Validation:** Run `conductor patch` to verify all unvetted suggestions are now recorded as "Live Tasks." -* **Artifact:** Confirm the existence of `docs/theory/ELEVATION-SPEC--2026-04-28.md`. diff --git a/docs/plans/INCIDENT_POSTMORTEM_DEC_28.md b/docs/plans/INCIDENT_POSTMORTEM_DEC_28.md deleted file mode 100644 index bd30938..0000000 --- a/docs/plans/INCIDENT_POSTMORTEM_DEC_28.md +++ /dev/null @@ -1,63 +0,0 @@ -# 🩺 INCIDENT POSTMORTEM: Metasystem Genesis -**Date:** December 28, 2025 -**Session:** Genesis / Activation -**Status:** RESOLVED - ---- - -## 1. Executive Summary -During the initialization of the Metasystem, we encountered **6 distinct anomalies** ranging from filesystem entropy to network failures. All issues were resolved in-session. The system is now stable. - -## 2. Incident Analysis - -### πŸ”΄ Incident 001: The "Russian Doll" Anomaly -* **Symptom:** The `omni-dromenon-machina` repository contained a nested folder of the same name, hiding the actual source code (`core-engine`, etc.). -* **Root Cause:** **Entropy.** Likely a previous `git clone` or drag-and-drop operation that pasted the repo *inside* itself rather than merging content. -* **Impact:** **High.** Scripts like `inoculate_seeds.py` failed to find repositories because the directory depth was unexpected. -* **Resolution:** Executed **"The Great Flattening"**. Used `shutil.move` to hoist all sub-folders to the root and deleted the ghost folder. -* **Prevention:** The new `metasystem-master` repo ignores sub-repo content (`.gitignore`), preventing accidental nesting in the future. - -### πŸ”΄ Incident 002: Inoculation Blindness -* **Symptom:** `inoculate_seeds.py` reported "0 repositories Inoculated" for the Omni org. -* **Root Cause:** **Logic Error.** The script assumed a flat `Org/Repo` hierarchy. It did not account for the monorepo-style structure of `omni-dromenon-machina` where projects live in subfolders. -* **Impact:** **Medium.** `seed.yaml` identity files were not generated initially. -* **Resolution:** Patched the script to detect and recurse into nested structures specific to the Omni org. -* **Prevention:** `scripts/audit_universe.py` now includes a recursive scanner. - -### πŸ”΄ Incident 003: Restoration Timeouts -* **Symptom:** Cloning the Origin (`4444JPP`) failed repeatedly on large repositories (`docs`, `OpenMetadata`). -* **Root Cause:** **Bandwidth/Size.** The global 5-minute timeout for tool execution killed the `gh repo clone` process before completion. -* **Impact:** **Medium.** 5 of 52 repositories remain deferred. -* **Resolution:** Implemented **"Surgical Restoration"**. Created `scripts/robust_restore.py` to skip known heavyweights and successfully clone the remaining 45 repos. -* **Prevention:** Use `robust_restore.py` for all future mass-cloning events. - -### πŸ”΄ Incident 004: Identity Crisis -* **Symptom:** The Master Repo was created under `4444JPP` (Personal) instead of `omni-dromenon-machina` (Org). -* **Root Cause:** **Agent Assumption.** I defaulted to the authenticated user's personal account instead of verifying the target organization's existence. -* **Impact:** **Low.** Created clutter. -* **Resolution:** Deleted the personal repo. Created `omni-dromenon-machina/metasystem-master`. Updated git remotes. -* **Prevention:** Always verify `gh org list` before creating repositories. - -### πŸ”΄ Incident 005: Neural Link Severed (Redis DNS) -* **Symptom:** `core-engine` crashed with `getaddrinfo ENOTFOUND redis`. -* **Root Cause:** **Network Race Condition.** The Docker network `omni-network` was stale or the container tried to connect before DNS propagation. -* **Impact:** **High.** The Event Bus (Neural Link) was dead. -* **Resolution:** Full stack restart (`docker-compose down && up`). This flushed the network map. -* **Prevention:** Added `healthcheck` to Redis service (already present) but ensured `core-engine` logic handles reconnection gracefully. - -### πŸ”΄ Incident 006: The Mute Critic (Missing API Key) -* **Symptom:** The Critic Agent detected the PR but failed to review it (`404` / Auth Error). -* **Root Cause:** **Configuration Gap.** `GEMINI_API_KEY` was not passed from the host shell to the Docker container. -* **Impact:** **Medium.** Intelligence features were disabled. -* **Resolution:** Updated `docker-compose.yml` to pass `${GEMINI_API_KEY}`. Updated `critic.ts` to use the correct model version. -* **Prevention:** `scripts/audit_universe.py` should check for `.env` file presence and key validity. - ---- - -## 3. Systemic Health Assessment -* **Resilience:** The system survived partial network failures and successfully self-corrected via the new scripts. -* **Integrity:** The `seed.yaml` protocol is now actively enforcing identity across 3 distinct Organizations. -* **Intelligence:** The Neural Link is proven to work. The "Brain" is connected to the "Body." - -**Signed:** -*The Architect* diff --git a/docs/plans/MASTER_EXECUTION_PLAN.md b/docs/plans/MASTER_EXECUTION_PLAN.md deleted file mode 100644 index ab9027c..0000000 --- a/docs/plans/MASTER_EXECUTION_PLAN.md +++ /dev/null @@ -1,61 +0,0 @@ -# πŸ“œ MASTER EXECUTION PLAN: The Metasystem - -**Version:** 2.0.0 (Post-Activation) -**Status:** ACTIVE -**Objective:** Evolve the newly synthesized Metasystem from a functional prototype to a dominant, autonomous sovereign entity. - ---- - -## βœ… COMPLETED PHASES (Dec 28, 2025) -* **Phase 1 (Restoration):** 90% Complete. 45/52 Origin repos restored. -* **Phase 2 (Neural Link):** 100% Complete. Event Bus & Webhooks Active. -* **Phase 3 (Guild):** 100% Local Prep. CI/CD Gatekeepers deployed. -* **Phase 4 (Activation):** 100% Complete. Critic Agent & Indexer deployed. - ---- - -## πŸ—οΈ Phase 5: The Habit (Routine Maintenance) -*Goal: Prevent entropy and establish the "Heartbeat" of the system.* - -### 5.1. The Daily Ritual (Script: `scripts/daily_ritual.py`) -We need a single command that runs every morning to sync reality. -- [ ] **Create Script:** `scripts/daily_ritual.py`. - - **Pull:** `git pull` on all 115 repos. - - **Inoculate:** Run `inoculate_seeds.py`. - - **Audit:** Run `audit_universe.py` to check for uncommitted changes. - - **Index:** Run `index_universe.py` to update the Architect's memory. -- [ ] **Automation:** Add to `crontab` or macOS LaunchAgent (`com.omni.ritual.plist`). - -### 5.2. The Night Watch (Security) -- [ ] **Secret Rotation:** Weekly prompt to rotate 1Password keys. -- [ ] **Backup:** `rsync` the entire `~/Workspace` to an external drive or S3 bucket (`_archive/weekly-snapshot`). - ---- - -## 🧬 Phase 6: Evolution (The Alchemical Works) -*Goal: Use the system to create Value (Code, Art, Money).* - -### 6.1. The Guild Launch (Commercial) -- [ ] **Action:** Create `labores-profani-crux` Org on GitHub. -- [ ] **Action:** Push the 3 commercial repos. -- [ ] **Action:** Deploy `trade-perpetual` to Cloud Run (Production). - -### 6.2. The Dreamcatcher (Generative Art) -- [ ] **Integration:** Connect `core-engine` to Stable Diffusion / Midjourney API. -- [ ] **Task:** Use the "Audience Input" (Neural Link) to drive real-time visual generation in `example-generative-visual`. - -### 6.3. The Recursive Architect -- [ ] **Goal:** The Architect Agent should be able to *modify its own code*. -- [ ] **Task:** Grant the `CriticAgent` permission to open PRs (not just review them) to fix linting errors automatically. - ---- - -## πŸ›‘ Blockers & Risks -1. **GitHub Org:** Need `labores-profani-crux` creation to unblock Guild. -2. **API Costs:** Heavy use of Gemini/OpenAI for the Critic will incur costs. *Mitigation: Rate limiting.* -3. **Local Compute:** Running Indexer daily might be slow. *Mitigation: Incremental indexing.* - ---- - -**Next Immediate Action:** -Run `python3 scripts/daily_ritual.py` (Once created) to lock in the day's progress. \ No newline at end of file diff --git a/docs/plans/ORIGIN_RESTORATION_LOG.md b/docs/plans/ORIGIN_RESTORATION_LOG.md deleted file mode 100644 index e00ef88..0000000 --- a/docs/plans/ORIGIN_RESTORATION_LOG.md +++ /dev/null @@ -1,12 +0,0 @@ -# πŸ“œ Origin Restoration Log - -| Repository | Status | Notes | -| :--- | :--- | :--- | -| `docs` | ❌ FAILED | Timed out (Deferred) | -| `adaptiveDEVlearningHub` | ⏳ PENDING | Deferred | -| `cookbook` | ⏳ PENDING | Deferred | -| `OpenMetadata` | ⏳ PENDING | Deferred | -| `pokerogue` | ⏳ PENDING | Deferred | -| `Context` | βœ… RESTORED | | -| `aionui` | βœ… RESTORED | | -| **All Others (45+)** | βœ… RESTORED | See scripts/robust_restore.py logs | diff --git a/docs/plans/PHASE_E_COMPLETION.md b/docs/plans/PHASE_E_COMPLETION.md deleted file mode 100644 index 820fb19..0000000 --- a/docs/plans/PHASE_E_COMPLETION.md +++ /dev/null @@ -1,30 +0,0 @@ -# Phase E: Expansion & Entropy - Completion Report - -## βœ… Implemented Features - -### 1. Identity OS: The Mask Editor -- **Location:** `life-my--midst--in/apps/web/src/app/ui/MaskEditor.tsx` -- **Status:** Implemented. -- **Details:** A React UI allows editing the Persona Name, Ontology, Tone, and Compression Ratio. It visualizes the JSON output and has a "Sync" button (mocked). - -### 2. Strategy Core: Neural Link -- **Location:** `gamified-coach-interface/src/main.js` -- **Status:** Implemented. -- **Details:** - - Installed `socket.io-client`. - - `NeuralLink` established to `http://localhost:3000`. - - 3D Core reacts to `metasystem:health` events (Green = Success, Orange = Drift, Red = Error). - -### 3. Orchestrator: Dream Scenarios -- **Location:** `omni-dromenon-machina/core-engine/src/dreamcatcher/scenarios/index.ts` & `watchman.ts` -- **Status:** Implemented. -- **Details:** - - Defined scenarios: `UI_POLISH`, `SECURE_CORE`, `CHAOS_MONKEY`. - - `NightWatchman` has a 5% probability to trigger a "Dream Scenario" when the universe is calm. - - Scenarios dispatch specific prompts to the Architect for autonomous improvement. - -## πŸš€ Next Steps (Deployment) -To make these changes live in production: -1. Run `./DEPLOY_ALL.sh`. -2. Ensure `gamified-coach-interface` and `life-my--midst--in` are also deployed (currently `DEPLOY_ALL.sh` focuses on the Core/SDK/Landing). -3. Update Terraform to provision services for the satellite apps. diff --git a/docs/plans/PLAN-001-neural-link.md b/docs/plans/PLAN-001-neural-link.md deleted file mode 100644 index f21e6f4..0000000 --- a/docs/plans/PLAN-001-neural-link.md +++ /dev/null @@ -1,36 +0,0 @@ -# πŸ—οΈ PLAN-001: Implementing the Neural Link - -**Spec:** `specs/REQ-001-neural-link.md` -**Context:** `core-engine` -**Goal:** Establish the Metasystem Event Bus and GitHub Webhook Ingress. - -## 1. Architecture Changes - -### A. The Event Definition (`src/types/metasystem.ts`) -We need a unified type definition for system-level events, distinct from performance parameters. - -### B. The System Bus (`src/bus/system-bus.ts`) -A dedicated Redis wrapper for `metasystem:events` channel. -* `publish(event: MetasystemEvent)` -* `subscribe(handler: (event: MetasystemEvent) => void)` - -### C. The Webhook Ingress (`src/server/routes/webhooks.ts`) -A new Express router to handle `POST /webhooks/github`. -* Verify Signature. -* Parse Payload. -* Dispatch to System Bus. - -### D. Server Integration (`src/server.ts`) -Mount the new routes. - -## 2. Execution Steps - -1. [ ] **Create Types:** `src/types/metasystem.ts` -2. [ ] **Create Bus:** `src/bus/system-bus.ts` -3. [ ] **Create Route:** `src/routes/webhooks.ts` (Need to create `routes` dir or use `server` dir) -4. [ ] **Wire Server:** Update `src/server.ts` -5. [ ] **Verify:** Create `scripts/test_neural_link.py` to fire mock event. - -## 3. Dependencies -* `ioredis` (Assume installed or install it). -* `crypto` (Node built-in for signature verification). diff --git a/docs/plans/PLAN-002-the-guild.md b/docs/plans/PLAN-002-the-guild.md deleted file mode 100644 index d1bf6fe..0000000 --- a/docs/plans/PLAN-002-the-guild.md +++ /dev/null @@ -1,27 +0,0 @@ -# πŸ—οΈ PLAN-002: Guild Infrastructure - -**Spec:** `specs/REQ-002-the-guild.md` -**Context:** `labores-profani-crux` -**Goal:** Prepare the commercial assets for deployment. - -## 1. Pipeline Architecture -We need a reusable workflow file that enforces "Profane Standards." - -### `profane-standards.yml` -* **Triggers:** Push to `main`, PR. -* **Jobs:** - * `quality`: Lint + Test. - * `security`: Dependency Audit. - * `build`: Production Build. - -## 2. Execution Steps - -1. [ ] **Create Workflow:** `templates/profane-standards.yml`. -2. [ ] **Distribute:** Copy workflow to `.github/workflows/` in: - * `trade-perpetual-future` - * `gamified-coach-interface` - * `enterprise-plugin` -3. [ ] **Script:** Create `scripts/init_guild_remote.sh` to automate the remote switch once Org exists. - -## 3. Dependencies -* None. diff --git a/docs/plans/PLAN-003-activation.md b/docs/plans/PLAN-003-activation.md deleted file mode 100644 index bd1010d..0000000 --- a/docs/plans/PLAN-003-activation.md +++ /dev/null @@ -1,33 +0,0 @@ -# πŸ—οΈ PLAN-003: Activating the Critic & The Architect - -**Spec:** `specs/REQ-003-activation.md` -**Context:** `core-engine` -**Goal:** Deploy autonomous review and indexing agents. - -## 1. Architecture - -### A. The Critic Agent (`src/orchestrator/critic.ts`) -A service that subscribes to the `systemBus` and reacts to `repo.pull_request` events. -* **Prompt:** Uses a "Critic Persona" to evaluate code against `seed.yaml` constraints. -* **Action:** Uses `gh api` or Octokit to post review comments. - -### B. The Architect (Indexing Script) -A standalone tool `scripts/index_universe.py` that chunks the 115 repos and prepares them for RAG. -* **Store:** For the prototype, we will use a JSON-based "Search Index" or a local ChromaDB instance if available. - -## 2. Execution Steps - -### Step 1: Implement the Critic -1. [ ] **Create Agent:** `core-engine/src/orchestrator/critic.ts`. -2. [ ] **Wire to Bus:** In `server.ts`, initialize the `CriticAgent` and subscribe it to `systemBus`. -3. [ ] **Mock Review:** Test using `scripts/test_neural_link.py` by sending a `pull_request` event. - -### Step 2: Implement the Architect (Indexer) -1. [ ] **Create Indexer:** `scripts/index_universe.py`. -2. [ ] **Scan Workspace:** Iterate through `~/Workspace/{Org}/{Repo}`. -3. [ ] **Chunking:** Extract `README.md` and key source files. -4. [ ] **Store:** Create `data/universe_index.json`. - -## 3. Dependencies -* `GITHUB_TOKEN` (Scoped for all 3 Orgs). -* `GEMINI_API_KEY`. diff --git a/docs/plans/RESUME_PROTOCOL.md b/docs/plans/RESUME_PROTOCOL.md deleted file mode 100644 index 1013816..0000000 --- a/docs/plans/RESUME_PROTOCOL.md +++ /dev/null @@ -1,58 +0,0 @@ -# ⏸️ RESUME PROTOCOL: Metasystem Synthesis - -**Session Status:** `PAUSED` -**Date:** Sunday, December 28, 2025 -**Phase:** Phase 1.2 (The Great Archival) - Partially Complete. - ---- - -## πŸ“ Current State -1. **Structure:** `~/Workspace` is physically partitioned into 4 Organizations: - * `omni-dromenon-machina` (The Architect) - * `ivviiviivvi` (The Alchemist) - * `labores-profani-crux` (The Guild - Commercial) - * `4444JPP` (The Origin - Archives) -2. **Identity:** All active repositories in Architect, Alchemist, and Guild have `seed.yaml`. -3. **Inventory:** `ECOSYSTEM.md` contains the master list of 115 repositories. -4. **Blocker:** Cloning the 52 repositories of `4444JPP` timed out due to network/size constraints. - ---- - -## ▢️ Next Actions (To Execute Next Session) - -> **See `plans/MASTER_EXECUTION_PLAN.md` for the full roadmap.** - -### 1. Resume the Archival (Manual Batching) -The "Ark" is empty. We need to fill `~/Workspace/4444JPP`. -Do not run the mass script. Run these batches manually in your terminal: - -**Batch A: The Brain (Docs & Knowledge)** -```bash -gh repo clone 4444JPP/docs ~/Workspace/4444JPP/docs -gh repo clone 4444JPP/adaptiveDEVlearningHub ~/Workspace/4444JPP/adaptiveDEVlearningHub -gh repo clone 4444JPP/cookbook ~/Workspace/4444JPP/cookbook -``` - -**Batch B: The Agents** -```bash -gh repo clone 4444JPP/aionui ~/Workspace/4444JPP/aionui -gh repo clone 4444JPP/terminal-ai ~/Workspace/4444JPP/terminal-ai -``` - -### 2. Activate the Neural Link (Phase 3) -Once the files are present (or even before), we need to wire the webhooks. -* **Action:** Configure GitHub Webhooks to point to the `core-engine`. -* **Tool:** Use `gh api` to auto-create webhooks on the Org level. - -### 3. The Grand Indexing -* **Action:** Point `cognitive-archaelogy-tribunal` at `~/Workspace/4444JPP`. -* **Goal:** Generate the Vector Embeddings so the Architect Agent can "remember" your past code. - ---- - -## πŸ› οΈ Scripts Available -* `scripts/audit_universe.py`: Checks for drift between Local and Remote. -* `scripts/sync_universe.py`: Pulls latest changes for all *existing* local repos. -* `scripts/inoculate_seeds.py`: Regenerates `seed.yaml` if you add new repos. - -**System is stable. Sleep well.** πŸŒ™ diff --git a/docs/plans/RITUAL_LOG.md b/docs/plans/RITUAL_LOG.md deleted file mode 100644 index 9b0ddd6..0000000 --- a/docs/plans/RITUAL_LOG.md +++ /dev/null @@ -1,5 +0,0 @@ - -- **2025-12-28:** Ritual Performed. System Aligned. -- **2025-12-28:** Ritual Performed. System Aligned. -- **2025-12-28:** Ritual Performed. System Aligned. -- **2025-12-29:** Ritual Performed. System Aligned. \ No newline at end of file diff --git a/docs/plans/comprehensive_synthesis_strategy.md b/docs/plans/comprehensive_synthesis_strategy.md deleted file mode 100644 index 3bd1af6..0000000 --- a/docs/plans/comprehensive_synthesis_strategy.md +++ /dev/null @@ -1,87 +0,0 @@ -# Comprehensive Synthesis Strategy: Alchemizing the 115 - -## 🎯 Objective -Transform the disparate 115 repositories of the **Omni-Dromenon Ecosystem** into a unified, self-governing Metasystem. - -## πŸ—οΈ 1. Repo Analysis (The Inventory) -**Status:** Completed via `ECOSYSTEM.md`. -**Key Findings:** -- **Fragmentation:** 52 repos in personal, 50 in mythos, 13 in architect. -- **Redundancy:** `perpetual-future` (4444JPP) vs `trade-perpetual-future` (ivviiviivvi). `artist-toolkits` vs `artist-toolkit-and-templates`. -- **Misplacement:** Commercial-grade apps (`gamified-coach`, `trade-perpetual`) are currently housed in the "Mythos" org (`ivviiviivvi`). - -**Action Plan:** -1. **Migrate:** Move `trade-perpetual-future` and `gamified-coach-interface` to the new **[COMMERCIAL_ORG]**. -2. **Archive:** Mark `4444JPP/perpetual-future` and `omni-dromenon-machina/artist-toolkit-and-templates` as archived/read-only. -3. **Tag:** Apply `mythos` topic to `ivviiviivvi` repos and `commercial` to the Guild repos. - -## πŸ•ΈοΈ 2. Dependency Mapping (The Nervous System) -**Goal:** Visualize and codify inter-repo links. - -**Core Dependencies:** -- `omni-dromenon-machina/core-engine` -> Orchestrates ALL. -- `ivviiviivvi/system-governance-framework` -> Rules for ALL. -- `life-my--midst--in` -> Consumes `performance-sdk`. - -**Action Plan:** -1. **Genome Injection:** Ensure every active repo has a `seed.yaml` listing its `dependencies`. -2. **Graph Generation:** Use `cognitive-archaelogy-tribunal` to parse `package.json` / `requirements.txt` across all 115 repos and generate a Gephi/Neo4j graph. - -## πŸ›‘οΈ 3. Code Scan (The Immunization) -**Goal:** Detect critical vulnerabilities across the sprawl. - -**Strategy:** -- **Tier 1 (High Risk):** Crypto/Finance (`trade-perpetual-future`), Auth (`life-my--midst--in`). - - *Action:* Full Snyk/CodeQL audit. -- **Tier 2 (Core):** `core-engine`, `performance-sdk`. - - *Action:* `npm audit`, Dependabot enabled. -- **Tier 3 (Archives/Art):** - - *Action:* Basic automated scans, low priority fixes. - -## 🀝 4. API Contract (The Language) -**Goal:** Define how the disparate organs talk to the Brain. - -**Standard:** -- **Protocol:** `socket.io` for real-time (Neural Link), REST/GraphQL for data. -- **Event Schema:** - ```typescript - interface MetasystemEvent { - source: string; // e.g., "gamified-coach" - type: "HEALTH" | "DRIFT" | "REQUEST"; - payload: Record; - signature: string; // Cryptographic proof of origin - } - ``` -**Action Plan:** -1. Publish `@omni-dromenon/contracts` npm package containing these shared types. -2. Enforce usage in `gamified-coach` and `life-my--midst--in`. - -## πŸ§ͺ 5. Test Strategy (The Gauntlet) -**Goal:** Ensure the Alchemization doesn't break the magic. - -**Levels:** -- **Unit:** Jest/Vitest within each repo. -- **Integration:** "Dream Scenarios" (Chaos Monkey). -- **System:** The `NightWatchman` checks `getUniverseHealth()` which aggregates status from all satellites. - -## πŸš€ 6. Deployment Plan (The Launch) -**Goal:** Continuous Delivery for the Metasystem. - -**Pipeline:** -1. **Commit** to Satellite (`ivviiviivvi/repo`). -2. **GitHub Action** runs tests & builds container. -3. **Registry Push** to `gcr.io`. -4. **Webhook** notifies `core-engine`. -5. **Core Engine** updates `4jp-metasystem.yaml` (if version changed) and redeploys via Terraform if necessary. - -## πŸ“Š 7. Metrics (The Pulse) -**KPIs:** -- **Drift Rate:** How often does `NightWatchman` have to intervene? (Target: < 1/day). -- **Alchemical Yield:** Number of "Mythos" ideas that successfully graduate to "Commercial" products. -- **System Coherence:** % of repos with valid `seed.yaml` and passing CI. - -## πŸ—“οΈ Execution Roadmap -- **Week 1:** Migration & Archival (Cleanup). -- **Week 2:** Genome Injection (`seed.yaml` everywhere). -- **Week 3:** The "Fourth Org" Setup & Transfer. -- **Week 4:** Dashboard Unification (See everything in `performance-sdk`). diff --git a/docs/plans/exhaustive_tasks_phase_2.md b/docs/plans/exhaustive_tasks_phase_2.md deleted file mode 100644 index 5dd81f2..0000000 --- a/docs/plans/exhaustive_tasks_phase_2.md +++ /dev/null @@ -1,64 +0,0 @@ -# Feature Implementation Plan: Exhaustive Tasks Phase 2 - -## πŸ“‹ Todo Checklist -- [ ] **Unified CI/CD**: Implement root-level dispatch workflows in `omni-dromenon-machina` to trigger downstream builds. -- [ ] **Shared Component Library**: Extract common UI components (e.g., "Neo-Brutalist" cards, buttons) into a new `@4jp/design-system` package within `life-my--midst--in`. -- [ ] **Centralized Auth**: prototype the "Identity Wallet" login flow using Solana adapter in `omni-dromenon-sdk`. -- [ ] **Cross-Repo Testing**: Implement `runIntegrationTest` in `OrchestratorTester` to spin up Docker containers for E2E testing. -- [ ] **Documentation**: Generate a "Grand Index" in the root workspace `README.md` linking to all project docs. -- [ ] Final Review and Testing - -## πŸ” Analysis & Investigation - -### Current State -- **Metasystem**: Fully integrated and deployed. Orchestrator sees all 7 projects. -- **CI/CD**: `life-my--midst--in` has a workflow, others rely on manual scripts. -- **UI**: Fragmented. `gamified-coach` and `omni-dromenon` share aesthetic but not code. -- **Auth**: Fragmented. `omni` uses secrets, `trade` uses wallets. - -### Dependencies -- **Solana Wallet Adapter**: Needed for centralized auth. -- **Docker**: Needed for integration testing. -- **Turbo**: Used in `life-my--midst--in` for package management. - -### Challenges -- **Auth Bridging**: Connecting a Solana wallet signature to a backend JWT for a non-web3 app (`omni-dromenon`) requires careful cryptographic verification. -- **Component Extraction**: Moving code from a standalone repo (`gamified-coach`) to a monorepo package (`@4jp/design-system`) involves refactoring imports and dependencies. - -## πŸ“ Implementation Plan - -### Prerequisites -- `omni-dromenon-machina` live. -- `life-my--midst--in` accessible. - -### Step-by-Step Implementation - -1. **Step 1: Shared Design System** - - **Context**: Unify UI. - - Files to modify: `../life-my--midst--in/packages/design-system`. - - Action: Create a new package. Extract `Card`, `Button`, `NeonText` from `omni-dromenon-sdk` and `gamified-coach-interface`. - -2. **Step 2: Unified CI Dispatch** - - **Context**: Automate builds. - - Files to modify: `omni-dromenon-machina/.github/workflows/dispatch.yml`. - - Action: Create a workflow that listens for `repository_dispatch` or pushes and triggers builds in satellite repos via API. - -3. **Step 3: Identity Wallet Prototype** - - **Context**: Unified Login. - - Files to modify: `omni-dromenon-machina/performance-sdk/src/auth/WalletLogin.tsx`. - - Action: specific implementation of SIWS (Sign In With Solana). - -4. **Step 4: Cross-Repo Integration Tests** - - **Context**: Verify the "Symbiote". - - Files to modify: `omni-dromenon-machina/core-engine/src/orchestrator/tester.ts`. - - Action: Add `runIntegrationTest` which uses `dockerode` or shell commands to spin up the stack and curl endpoints. - -### Testing Strategy -- **Design System**: Storybook (if added) or import into `web` app. -- **Auth**: successful login with Phantom wallet -> JWT issuance. -- **Integration**: `tester.ts` reports success after spinning up containers. - -## 🎯 Success Criteria -- **Shared UI**: `omni-dromenon` consumes components from `@4jp/design-system`. -- **Unified Auth**: One wallet login accesses Dashboard. -- **Automated E2E**: Orchestrator can prove the whole system works together. diff --git a/docs/plans/metasystem-structure-proposal.md b/docs/plans/metasystem-structure-proposal.md deleted file mode 100644 index 6731a66..0000000 --- a/docs/plans/metasystem-structure-proposal.md +++ /dev/null @@ -1,343 +0,0 @@ -# 4jp Metasystem Structure Proposal - -## Current Situation - -``` -/Users/4jp/Workspace/ -β”œβ”€β”€ omni-dromenon-machina/ # Autonomous development orchestrator (the "org") -└── life-my--midst--in/ # Interactive CV system (monorepo, managed by omni-drom) -``` - -## Relationship - -- **omni-dromenon-machina** is the **meta-system** that orchestrates autonomous development -- **life-my--midst--in** is a **target project** (first of potentially many) that omni-drom manages - -## Proposed Structure Options - -### Option A: Flat Organization with Manifest (Recommended) - -Keep them separate but create a meta-manifest linking them: - -``` -/Users/4jp/Workspace/ -β”œβ”€β”€ 4jp-metasystem.yaml # Meta-manifest linking projects -β”œβ”€β”€ omni-dromenon-machina/ # The orchestrator -β”‚ └── ... (autonomous dev system) -└── life-my--midst--in/ # Managed project #1 - └── ... (CV monorepo) -``` - -**4jp-metasystem.yaml**: -```yaml -name: "4jp-metasystem" -description: "Autonomous development ecosystem" - -orchestrator: - name: "omni-dromenon-machina" - path: "./omni-dromenon-machina" - type: "autonomous-orchestrator" - -managed_projects: - - name: "life-my--midst--in" - path: "./life-my--midst--in" - type: "monorepo" - orchestration: - enabled: true - genome: "./life-my--midst--in/seed.yaml" - -relationships: - - from: "omni-dromenon-machina" - to: "life-my--midst--in" - type: "orchestrates" -``` - -**Pros**: -- Clean separation of concerns -- Easy to add more managed projects -- Each project maintains its own git repo -- Simple structure - -**Cons**: -- Not physically nested (but linked via manifest) - ---- - -### Option B: Parent Folder with Git Submodules - -``` -/Users/4jp/Workspace/ -└── 4jp-metasystem/ # Parent meta-repo - β”œβ”€β”€ README.md - β”œβ”€β”€ .gitmodules - β”œβ”€β”€ orchestrator/ # Git submodule - β”‚ └── [omni-dromenon-machina contents] - └── projects/ - └── life-my--midst--in/ # Git submodule - └── [midst-life contents] -``` - -**Pros**: -- Single parent repo tracks both -- Clean nested structure -- Can version the "meta-system" as a whole -- Easy to clone entire system - -**Cons**: -- Git submodules can be tricky -- More complex workflow - ---- - -### Option C: Orchestrator Contains Projects (Workspace Pattern) - -``` -/Users/4jp/Workspace/ -└── omni-dromenon-machina/ # The orchestrator IS the parent - β”œβ”€β”€ README.md - β”œβ”€β”€ orchestrator/ # The orchestrator code itself - β”‚ └── ... (multi-agent system) - β”œβ”€β”€ managed-projects/ - β”‚ └── life-my--midst--in/ # Nested managed project - β”‚ └── ... (CV monorepo) - └── config/ - └── metasystem.yaml -``` - -**Pros**: -- Orchestrator "owns" its projects -- Single point of entry -- Clear hierarchy - -**Cons**: -- Mixes orchestrator code with managed projects -- Could become monolithic - ---- - -### Option D: Hybrid - Orchestrator + Separate Workspaces Folder - -``` -/Users/4jp/Workspace/ -└── 4jp-metasystem/ - β”œβ”€β”€ README.md - β”œβ”€β”€ metasystem.yaml # Configuration - β”œβ”€β”€ omni-dromenon-machina/ # The orchestrator (could be submodule) - β”‚ └── ... - └── workspaces/ # Managed projects - └── life-my--midst--in/ # Monorepo project - └── ... -``` - -**Pros**: -- Clean separation of orchestrator vs. managed -- Room to grow (multiple workspaces) -- Clear conceptual model -- Single parent container - -**Cons**: -- Slightly more nested - ---- - -## Recommendation - -I recommend **Option D (Hybrid)** because: - -1. **Clear separation**: Orchestrator vs. workspaces -2. **Scalable**: Easy to add more projects -3. **Conceptually sound**: Matches the actual relationship -4. **Flexible git strategy**: Can make parent a repo or not - -### Proposed Git Strategy for Option D - -**Parent (4jp-metasystem)**: Regular git repo -- Tracks metasystem.yaml, README, docs -- Does NOT track children directly - -**Children**: Independent git repos -- omni-dromenon-machina has its own repo -- life-my--midst--in has its own repo -- Parent .gitignore ignores child .git folders - -**Connection**: Via metasystem.yaml manifest - -This way: -- Each project maintains independence -- You can version-control the meta-configuration -- Easy to add/remove projects -- No submodule complexity - ---- - -## Implementation Steps (for Option D) - -```bash -# 1. Create parent structure -mkdir -p /Users/4jp/Workspace/4jp-metasystem/workspaces - -# 2. Move projects -mv /Users/4jp/Workspace/omni-dromenon-machina \ - /Users/4jp/Workspace/4jp-metasystem/omni-dromenon-machina - -mv /Users/4jp/Workspace/life-my--midst--in \ - /Users/4jp/Workspace/4jp-metasystem/workspaces/life-my--midst--in - -# 3. Create meta-configuration -# (See metasystem.yaml template below) - -# 4. Initialize parent git -cd /Users/4jp/Workspace/4jp-metasystem -git init -git add README.md metasystem.yaml .gitignore -git commit -m "Initial metasystem structure" - -# 5. Update symlinks/paths if needed -``` - ---- - -## Metasystem Configuration Template - -```yaml -# /Users/4jp/Workspace/4jp-metasystem/metasystem.yaml - -version: 1 -name: "4jp-metasystem" -description: > - Meta-system for autonomous development orchestration. - omni-dromenon-machina orchestrates development across managed workspaces. - -components: - orchestrator: - name: "omni-dromenon-machina" - path: "./omni-dromenon-machina" - type: "autonomous-orchestrator" - capabilities: - - "multi-agent-development" - - "github-integration" - - "project-scaffolding" - - "code-generation" - - "quality-enforcement" - - workspaces: - - name: "life-my--midst--in" - path: "./workspaces/life-my--midst--in" - type: "monorepo" - status: "active" - genome: "./workspaces/life-my--midst--in/seed.yaml" - orchestration: - enabled: true - agent_access: true - ci_integration: true - tech_stack: - - "typescript" - - "next.js" - - "postgresql" - - "neo4j" - -relationships: - - source: "omni-dromenon-machina" - target: "life-my--midst--in" - relationship: "orchestrates" - description: "Autonomous multi-agent development and maintenance" - -metadata: - created: "2025-12-26" - owner: "4jp" - purpose: "Autonomous identity system development ecosystem" -``` - ---- - -## .gitignore for Parent - -```gitignore -# Ignore child repos' .git directories -omni-dromenon-machina/.git/ -workspaces/**/.git/ - -# Ignore child repos' dependencies -omni-dromenon-machina/node_modules/ -workspaces/**/node_modules/ - -# Ignore build artifacts -omni-dromenon-machina/dist/ -workspaces/**/dist/ -workspaces/**/.next/ - -# Ignore logs -*.log -``` - ---- - -## README.md Template for Parent - -```markdown -# 4jp Metasystem - -Meta-system for autonomous development orchestration. - -## Structure - -- **omni-dromenon-machina/** - Autonomous development orchestrator -- **workspaces/** - Managed projects - - **life-my--midst--in/** - Interactive CV/rΓ©sumΓ© system - -## How It Works - -**omni-dromenon-machina** is the autonomous development orchestrator that: -- Manages multi-agent workflows -- Coordinates code generation across projects -- Enforces quality gates and architectural constraints -- Integrates with GitHub for CI/CD - -**Workspaces** are projects managed by the orchestrator: -- Each has a `seed.yaml` genome defining constraints -- Autonomous agents read/write within defined boundaries -- Human oversight at approval gates - -## Getting Started - -1. Set up orchestrator: `cd omni-dromenon-machina && pnpm install` -2. Review workspace: `cd workspaces/life-my--midst--in && cat README.md` -3. See configuration: `cat metasystem.yaml` - -## Projects - -### life-my--midst--in -Interactive CV/rΓ©sumΓ© system with blockchain-inspired architecture, -identity masks, and temporal epochs. First project managed by omni-drom. - -Status: Design complete, implementation ready -Tech: TypeScript, Next.js 15, PostgreSQL, Neo4j -``` - ---- - -## Alternative: Keep Flat Structure - -If you prefer simplicity, we can also just keep them flat and create the manifest: - -``` -/Users/4jp/Workspace/ -β”œβ”€β”€ 4jp-metasystem.yaml # Links the two -β”œβ”€β”€ omni-dromenon-machina/ -└── life-my--midst--in/ -``` - -This is simpler but less "organized" visually. - ---- - -## Your Choice - -Which option resonates with you? - -1. **Option A** - Flat with manifest (simplest) -2. **Option B** - Parent with submodules (complex but unified) -3. **Option C** - Orchestrator owns projects (conceptually merged) -4. **Option D** - Hybrid workspaces (recommended, balanced) - -Or a completely different structure you envision? diff --git a/docs/plans/metasystem_integration.md b/docs/plans/metasystem_integration.md deleted file mode 100644 index 8ed86b0..0000000 --- a/docs/plans/metasystem_integration.md +++ /dev/null @@ -1,57 +0,0 @@ -# Metasystem Integration Plan: The Alchemization of Three Orgs - -## 🎯 Objective -Synthesize the disjointed **115 repositories** of `omni-dromenon-machina`, `ivviiviivvi`, and `4444JPP` into a unified, autonomous **Metasystem**. -*(See `ECOSYSTEM.md` for the complete master inventory)* - -## πŸ›οΈ Organizational Roles (The Triad + The Guild) - -### 1. Omni-Dromenon Machina (`omni-dromenon-machina`) -**Role:** **The Architect** (Structure, Law, Infrastructure) -**Mandate:** Provide the stable core, orchestration engine, and rigid protocols that govern the system. -**Canonical Repos:** `core-engine`, `performance-sdk`, `docs`, etc. (13 Total) - -### 2. ivviiviivvi (`ivviiviivvi`) -**Role:** **The Alchemist** (Transformation, Identity, Experimentation) -**Mandate:** Explore, generate, and evolve. This is where the "Masks" live and where "Chaos" is transmuted into value. -**Canonical Repos:** `life-my--midst--in` (Proposed), `system-governance-framework`, `solve-et-coagula`, etc. (50 Total) - -### 3. 4444JPP (`4444JPP`) -**Role:** **The Origin** (Base Reality, Personal Data, Archives) -**Mandate:** Store the raw, private, and personal history that fuels the Alchemist. -**Canonical Repos:** `mail_automation`, `my--father-mother`, Cookbooks, etc. (52 Total) - -### 4. labores-profani-crux (The Guild) -**Role:** **The Merchant** (Commercial Products, Stable Releases) -**Mandate:** Monetize the alchemical output. Separation of concerns from the Mythos. -**Migration Candidates:** -- `trade-perpetual-future` -- `gamified-coach-interface` -- `enterprise-plugin` - -## βš—οΈ The Alchemization Process - -### Phase 1: Inventory & Classification (Completed) -- [x] **Repo Inventory**: Generated `ECOSYSTEM.md` covering all 115 repos. -- [x] **Strategy Definition**: Created `plans/comprehensive_synthesis_strategy.md`. - -### Phase 2: Mapping & Standardization (Immediate) -- [ ] **Update `4jp-metasystem.yaml`**: Explicitly map every local project to one of these 3 remote orgs. -- [ ] **Standardize `seed.yaml`**: Ensure every repo has a `seed.yaml` that declares its `org` and `role`. -- [ ] **Consolidate Duplicates**: - - Archive `4444JPP/perpetual-future` in favor of `ivviiviivvi/trade-perpetual-future`. - - Merge `collective-persona-operations` concepts into `life-my--midst--in`. - - Archive `artist-toolkit-and-templates`. - -### Phase 3: The Neural Link (Integration) -- [ ] **Orchestrator Access**: The `core-engine` (running in Cloud Run) needs a `GITHUB_TOKEN` with permissions across ALL THREE orgs to manage them. -- [ ] **Cross-Org Dispatch**: The `NightWatchman` must be able to detect drift in `ivviiviivvi` and dispatch a fix via `omni-dromenon-machina`'s core. - -### Phase 3: Autonomous Governance (Evolution) -- [ ] **The Council**: Use `ivviiviivvi/system-governance-framework` to define the rules for how the Orgs interact. -- [ ] **The Tribunal**: Activate `cognitive-archaelogy-tribunal` to index `4444JPP` archives and feed insights to `ivviiviivvi` agents. - -## πŸ“‹ Action Items for User -1. **Authorize**: Confirm the proposed home for `life-my--midst--in` is `ivviiviivvi`. -2. **Token**: Ensure your 1Password secrets contain a Personal Access Token (PAT) with `repo` and `workflow` scope for all 3 orgs. -3. **Push**: Run the universal sync script (to be created) to push local states to these remotes. \ No newline at end of file diff --git a/docs/plans/phase_e_evolution.md b/docs/plans/phase_e_evolution.md deleted file mode 100644 index 9b1b424..0000000 --- a/docs/plans/phase_e_evolution.md +++ /dev/null @@ -1,56 +0,0 @@ -# Feature Implementation Plan: Phase E - Expansion & Entropy - -## πŸ“‹ Todo Checklist -- [ ] **Identity OS (`life-my--midst--in`)**: Implement the "Mask Editor" UI. -- [ ] **Strategy Core (`gamified-coach`)**: Connect the 3D hologram to real Identity data. -- [ ] **Orchestrator (`omni-dromenon`)**: Implement "Dream Scenarios" for targeted autonomous improvement. -- [ ] **Infrastructure**: Terraform/IaC for satellite project deployment. -- [ ] **Docs**: Create a "Grand Index" in the root workspace. - -## πŸ” Analysis & Investigation - -### Current State -- **Orchestrator**: Active, Triple-Agent (Architect/Builder/Critic), monitoring 7 projects. -- **Identity OS**: `life-my--midst--in` has a `schema` package but the `web` app is a skeleton (`next dev` works but UI is empty). -- **Strategy Core**: `gamified-coach-interface` has a `StrategyCore.js` (Three.js) but it's isolated and uses mock states ('idle', 'glitching'). -- **Metasystem**: `4jp-metasystem.yaml` is the source of truth. - -### The Gap -The "Nervous System" (Omni) is built, but the "Body" (Identity) and "Mind" (Strategy) are still embryonic. They need content and connection. - -## πŸ“ Implementation Plan - -### 1. Identity OS: The Mask Editor -**Objective:** Create a UI to edit the `seed.yaml` genome visually. -- **Location:** `life-my--midst--in/apps/web`. -- **Tech:** React Hook Form + Zod (from `packages/schema`). -- **Feature:** A "Mask Switcher" that changes the user's active persona (e.g., "Developer" -> "Artist"). - -### 2. Strategy Core: Neural Link -**Objective:** Feed real data into the `StrategyCore` hologram. -- **Location:** `gamified-coach-interface/src/main.js` & `StrategyCore.js`. -- **Action:** - 1. Connect to `omni-dromenon-core` via WebSocket (`socket.io-client`). - 2. Listen for `metasystem:health` events. - 3. Map Health -> Visual State: - - All Green -> "Success" state (Green glow). - - Drift Detected -> "Glitching" state (Orange vertices). - - Error -> "Critical" state (Red pulse). - -### 3. Orchestrator: Dream Scenarios -**Objective:** Give the `NightWatchman` specific missions beyond just "fix drift". -- **Location:** `omni-dromenon-machina/core-engine/src/dreamcatcher/scenarios`. -- **Scenarios:** - - `UI_POLISH`: "Scan all CSS files and normalize colors to the design system." - - `SECURE_CORE`: "Scan all dependencies and upgrade if vulnerable." - - `CHAOS_MONKEY`: "Randomly introduce a minor drift to test recovery." - -### 4. Infrastructure: Satellite Launch -**Objective:** Deploy the satellites to the cloud so they are accessible public URLs. -- **Location:** `omni-dromenon-deploy/gcp`. -- **Action:** Create `cloud-run-service.yaml` for `gamified-coach` and `identity-os`. - -## 🎯 Success Criteria -- **Visual Synergy:** The `gamified-coach` hologram turns RED when I break a test in `life-my--midst--in`. -- **Identity Control:** I can edit my "Mask" in `life-my--midst--in` and see the changes reflected in the Metasystem. -- **Autonomous Evolution:** The Orchestrator wakes up at night and optimizes the CSS of the Identity OS without human intervention. diff --git a/docs/plans/workspace_quality_and_security_overhaul.md b/docs/plans/workspace_quality_and_security_overhaul.md deleted file mode 100644 index 50de05c..0000000 --- a/docs/plans/workspace_quality_and_security_overhaul.md +++ /dev/null @@ -1,76 +0,0 @@ -# Feature Implementation Plan: workspace_quality_and_security_overhaul - -## πŸ“‹ Todo Checklist -- [ ] **Standardization**: Create a shared ESLint/Prettier configuration package for the metasystem. -- [ ] **Security (Crypto)**: Audit `trade-perpetual-future` dependencies and implement a lockfile freeze. -- [ ] **Security (Automation)**: Verify `.gitignore` rules for `mail_automation` and `my--father-mother` to prevent credential leaks. -- [ ] **Performance**: Analyze `gamified-coach-interface` bundle size and Three.js asset loading strategies. -- [ ] **Documentation**: Consolidate architectural diagrams from all projects into a central Metasystem Wiki. -- [ ] **Orchestration**: Extend `omni-dromenon-machina` to support "Quality Guard" tasks that run `audit` commands across managed repos. -- [ ] Final Review and Testing - -## πŸ” Analysis & Investigation - -### Codebase Structure -The workspace is a "Metasystem" managed by `omni-dromenon-machina`. -- **Orchestrator**: `omni-dromenon-machina` (Node/TS) - High quality, strict types. -- **Monorepo**: `life-my--midst--in` (Turbo/Next.js) - Strict governance via `seed.yaml`. -- **Web Apps**: `gamified-coach-interface`, `trade-perpetual-future` (React/Vite). -- **Tools**: `mail_automation`, `my--father-mother` (Python). - -### Current Architecture -- **Federated Governance**: Each project has local config, but `omni-dromenon` is acquiring capabilities to audit them. -- **Language Split**: Heavy TypeScript focus for apps, Python for local automation/tools. -- **Deployment**: Docker/Cloud Run for the core engine; Vercel/Netlify patterns for web apps. - -### Dependencies & Integration Points -- **Shared**: `mcp-servers` provides local intelligence capabilities to multiple projects. -- **External**: Google Cloud (Firestore, Cloud Run), Solana (Drift Protocol), OpenAI/Anthropic APIs. - -### Considerations & Challenges -- **Secret Management**: Python scripts (`mail_automation`) rely on local files (`credentials.json`) which pose a leak risk if not strictly git-ignored. -- **Consistency**: TypeScript configs vary slightly between `omni-dromenon` and `trade-perpetual-future`. -- **Local Data**: `my--father-mother` stores sensitive clipboard history in SQLite; encryption at rest should be considered. - -## πŸ“ Implementation Plan - -### Prerequisites -- Access to all repositories (verified). -- `omni-dromenon-machina` operational (verified). - -### Step-by-Step Implementation - -1. **Step 1: Unify TypeScript & Linting Standards** - - **Context**: Reduce cognitive load by enforcing consistent rules. - - Files to modify: Create `packages/config-eslint` in `life-my--midst--in` (as it's the monorepo) or a root-level config in `omni-dromenon`. - - Action: Define a "Strict Metasystem" preset (AirBnb style + Prettier) and propagate to `trade-perpetual-future`. - -2. **Step 2: Hardening Python Automation** - - **Context**: Prevent credential leaks. - - Files to modify: `mail_automation/.gitignore`. - - Changes needed: Ensure `token.pickle`, `credentials.json`, and `*.log` are explicitly ignored. Add a pre-commit hook script to check for high-entropy strings. - -3. **Step 3: Crypto-Safety Audit** - - **Context**: `trade-perpetual-future` handles real funds via wallet connection. - - Action: Run `npm audit`. Implement `socket.io` security headers if used. - - Files to modify: `trade-perpetual-future/package.json` (update dependencies). - -4. **Step 4: Performance Optimization (3D)** - - **Context**: `gamified-coach-interface` loads 3D scenes. - - Action: Implement Draco compression for models and lazy-loading for the `StrategyCore`. - - Files to modify: `gamified-coach-interface/src/SceneManager.js`. - -5. **Step 5: Metasystem Quality Guard** - - **Context**: Automate this review process. - - Files to modify: `omni-dromenon-machina/core-engine/src/orchestrator/tester.ts`. - - Changes needed: Add a `runSecurityAudit` method that triggers `npm audit` or `pip-audit` in managed workspaces and reports findings to the dashboard. - -### Testing Strategy -- **Linting**: Run `eslint .` across all TS projects; expect zero errors. -- **Security**: Run `trivy` or `npm audit` on all repos. -- **Performance**: Use Lighthouse CI on the landing page and dashboard. - -## 🎯 Success Criteria -- **Zero Critical Vulnerabilities** across all 4 major projects. -- **Unified Style**: All TypeScript projects pass the same strict linting rules. -- **Automated Vigilance**: The Orchestrator reports security status alongside project health in the Performer Dashboard.