legion-apollo 0.5.6 → 0.5.7

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 7150a2def38a098c16a2f35362210994cc77537ca6ee3e0e615823cf8e1797c2
-  data.tar.gz: 6e0bfa593f70915134195672dbe321f03c00c86e1f80fee06f5370f3c6578110
+  metadata.gz: 9d677b83515f568ba99bf3288a9b2f7ade65775b816559092b65265966e8a2cd
+  data.tar.gz: 9fd3698f16f43357ecc6b1e9791bf46d03d28afb6f7f28bbeac52e7af0a9fe3f
 SHA512:
-  metadata.gz: 97783044f23209d697578c0f56d570bc48b9531e5d569f23e4db98bf55cb5d0c4602d6a0fedeb8e7c04a89618d4586c25bc7ca89f1a8d922e8618c5b724cc13e
-  data.tar.gz: 8498fae869abc9f54520b216ed88e2aea006ee6e520d8421d44cf5781c76ae9c158553e3c34a7e9e1e37d44594248a5c6daae1c7b55336c9692e7b668f00fbb4
+  metadata.gz: b7e5ccadab990babeed6409b43c2db932ca85a990defe38f07bde539bccfdcf8620e06140f0dcddae85c8c2016e5251bd91afa0b3aaae31f7f6368ab97104e09
+  data.tar.gz: bbbe65132a326f90ba9ebd573f4938a9cfd8cbfba688cd742e4ec39f4128fd72d07a236787f8a23a757336477459034d4907a387e0040416f72e08b49318d4ad

data/CHANGELOG.md

@@ -1,5 +1,9 @@
 # Changelog
 
+## [0.5.7] - 2026-07-15
+### Removed
+- Remove .md self-knowledge seed pipeline (bonds must be earned, not implanted)
+
 ## [0.5.5] - 2026-05-15
 
 ### Added

data/lib/legion/apollo/local.rb

@@ -17,8 +17,6 @@ module Legion
       MIGRATION_PATH = File.expand_path('local/migrations', __dir__).freeze
       LIFECYCLE_MUTEX = Mutex.new
       WRITE_MUTEX = Mutex.new
-      SEED_MUTEX = Mutex.new
-      HYDRATION_MUTEX = Mutex.new
 
       class << self # rubocop:disable Metrics/ClassLength
         include Legion::Logging::Helper
@@ -33,13 +31,11 @@ module Legion
         def shutdown
           LIFECYCLE_MUTEX.synchronize do
             @started = false
-            @seeded = false
             log.info 'Legion::Apollo::Local shutdown'
           end
         rescue StandardError => e
           handle_exception(e, level: :warn, operation: 'apollo.local.shutdown')
           @started = false
-          @seeded = false
         end
 
         def started?
@@ -146,22 +142,9 @@ module Legion
         def reset!
           LIFECYCLE_MUTEX.synchronize do
             @started = false
-            @seeded = false
           end
         end
 
-        def seed_self_knowledge
-          return unless started?
-
-          SEED_MUTEX.synchronize { seed_self_knowledge_without_lock }
-        rescue StandardError => e
-          handle_exception(e, level: :warn, operation: 'apollo.local.seed_self_knowledge')
-        end
-
-        def seeded?
-          @seeded == true
-        end
-
         def query_by_tags(tags:, limit: 50) # rubocop:disable Metrics/MethodLength
           connection = local_db_connection
           tags = normalize_tags_input(tags)
@@ -232,15 +215,6 @@ module Legion
           { success: false, error: e.message }
         end
 
-        def hydrate_from_global
-          return { success: false, error: :not_started } unless started?
-
-          HYDRATION_MUTEX.synchronize { hydrate_from_global_without_lock }
-        rescue StandardError => e
-          handle_exception(e, level: :error, operation: 'apollo.local.hydrate_from_global')
-          { success: false, error: e.message }
-        end
-
         def version_chain(entry_id:, max_depth: 50) # rubocop:disable Metrics/MethodLength
           return not_started_error unless started?
 
@@ -278,49 +252,6 @@ module Legion
 
         private
 
-        def self_knowledge_files
-          seed_dir = File.join(File.expand_path('../../..', __dir__), 'data', 'self-knowledge')
-          return [] unless File.directory?(seed_dir)
-
-          Dir[File.join(seed_dir, '*.md')]
-        end
-
-        def seed_files(files)
-          count = 0
-          files.each do |path|
-            count += 1 if seed_single_file(path)
-          end
-          count
-        end
-
-        def seed_single_file(path)
-          content = File.read(path)
-          return false if content.strip.empty?
-
-          tags = ['legionio', 'self-knowledge', File.basename(path, '.md')]
-          result = ingest(content: content, tags: tags, source_channel: 'self-knowledge',
-                          submitted_by: 'legion-apollo', confidence: 0.9)
-          return false unless result[:success] && result[:mode] != :deduplicated
-
-          ingest_global(content: content, tags: tags) if global_available?
-          true
-        end
-
-        def ingest_global(content:, tags:)
-          log.debug { "Apollo::Local forwarding seed entry to global tag_count=#{Array(tags).size}" }
-          Legion::Apollo.ingest(content: content, tags: tags, source_channel: 'self-knowledge',
-                                submitted_by: 'legion-apollo', confidence: 0.9, scope: :global)
-        rescue StandardError => e
-          handle_exception(e, level: :debug, operation: 'apollo.local.ingest_global_seed', tag_count: Array(tags).size)
-        end
-
-        def global_available?
-          defined?(Legion::Apollo) && Legion::Apollo.started? && Legion::Apollo.respond_to?(:ingest)
-        rescue StandardError => e
-          handle_exception(e, level: :debug, operation: 'apollo.local.global_available')
-          false
-        end
-
         def local_enabled?
           return false unless defined?(Legion::Settings)
 
@@ -388,58 +319,6 @@ module Legion
           log.info 'Legion::Apollo::Local started'
         end
 
-        def seed_self_knowledge_without_lock
-          return if @seeded
-
-          files = self_knowledge_files
-          return if files.empty?
-
-          count = seed_files(files)
-          @seeded = true
-          log.info("Apollo::Local seeded #{count} self-knowledge files")
-        end
-
-        def hydrate_from_global_without_lock # rubocop:disable Metrics/MethodLength,Metrics/AbcSize,Metrics/CyclomaticComplexity,Metrics/PerceivedComplexity
-          local_check = query_by_tags(tags: ['partner'])
-          if local_check[:success] && local_check[:results]&.any?
-            log.info 'Apollo::Local hydration skipped because local partner data already exists'
-            return { success: true, skipped: :local_data_exists }
-          end
-
-          unless Legion::Apollo.transport_available? || Legion::Apollo.data_available?
-            log.info 'Apollo::Local hydration skipped because global Apollo is unavailable'
-            return { success: true, skipped: :global_unavailable }
-          end
-
-          global_entries = Legion::Apollo.retrieve(text: 'partner bond', scope: :global, limit: 20)
-          entries = Array(global_entries[:entries] || global_entries[:results])
-          unless global_entries[:success] && entries.any?
-            log.info 'Apollo::Local hydration skipped because no global partner data was found'
-            return { success: true, skipped: :no_global_data }
-          end
-
-          log.info { "Apollo::Local hydration started global_count=#{entries.size}" }
-          hydrated = 0
-          entries.each do |entry|
-            entry_tags = entry[:tags].is_a?(Array) ? entry[:tags] : []
-            clean_tags = entry_tags.reject { |tag| tag == 'promoted_from_local' } + ['hydrated_from_global']
-
-            result = ingest(
-              content:        entry[:content],
-              raw_content:    entry[:raw_content] || entry[:content],
-              tags:           clean_tags,
-              confidence:     ((entry[:confidence] || 0.5) * 0.9).round(10),
-              source_channel: 'global_hydration',
-              valid_from:     entry[:valid_from],
-              valid_to:       entry[:valid_to]
-            )
-            hydrated += 1 if result[:success]
-          end
-
-          log.info { "Apollo::Local hydration completed hydrated=#{hydrated}" }
-          { success: true, hydrated: hydrated }
-        end
-
         def ingest_without_lock(content:, tags:, **opts) # rubocop:disable Metrics/MethodLength,Metrics/AbcSize
           content = normalize_text_input(content)
           raw_content = normalize_raw_content_input(opts[:raw_content], fallback: content)

data/lib/legion/apollo/version.rb

@@ -2,6 +2,6 @@
 
 module Legion
   module Apollo
-    VERSION = '0.5.6'
+    VERSION = '0.5.7'
   end
 end

data/lib/legion/apollo.rb

@@ -39,9 +39,6 @@ module Legion
 
           @started = true
           log.info 'Legion::Apollo started'
-
-          seed_self_knowledge
-          Legion::Apollo::Local.hydrate_from_global if Legion::Apollo::Local.started?
         end
       rescue StandardError => e
         handle_exception(e, level: :error, operation: 'apollo.start')
@@ -469,13 +466,6 @@ module Legion
         { success: false, error: e.message }
       end
 
-      def seed_self_knowledge
-        log.info 'Apollo self-knowledge seed requested'
-        Legion::Apollo::Local.seed_self_knowledge if Legion::Apollo::Local.started?
-      rescue StandardError => e
-        handle_exception(e, level: :warn, operation: 'apollo.seed_self_knowledge')
-      end
-
       def apollo_setting(key, default)
         return default unless defined?(Legion::Settings) && !Legion::Settings[:apollo].nil?
 

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: legion-apollo
 version: !ruby/object:Gem::Version
-  version: 0.5.6
+  version: 0.5.7
 platform: ruby
 authors:
 - Esity
@@ -66,17 +66,6 @@ files:
 - CHANGELOG.md
 - LICENSE
 - README.md
-- data/self-knowledge/01-what-is-legion.md
-- data/self-knowledge/02-architecture.md
-- data/self-knowledge/03-extensions.md
-- data/self-knowledge/04-security.md
-- data/self-knowledge/05-llm-pipeline.md
-- data/self-knowledge/06-apollo-knowledge.md
-- data/self-knowledge/07-cli-reference.md
-- data/self-knowledge/08-cognitive-layer.md
-- data/self-knowledge/09-teams-integration.md
-- data/self-knowledge/10-deployment.md
-- data/self-knowledge/11-my-partner.md
 - lib/legion/apollo.rb
 - lib/legion/apollo/helpers/confidence.rb
 - lib/legion/apollo/helpers/similarity.rb

data/data/self-knowledge/01-what-is-legion.md

@@ -1,51 +0,0 @@
-# What is LegionIO?
-
-LegionIO is an extensible async job engine and cognitive platform for Ruby. It schedules tasks, creates relationships between services, and runs them concurrently. It was created by Matthew Iverson (@Esity) and is licensed under Apache-2.0.
-
-LegionIO is not a chatbot. It is a framework that can power chatbots, AI assistants, background workers, service integrations, and autonomous agents. The chat interface is one of many ways to interact with it.
-
-## Core Purpose
-
-LegionIO connects isolated systems — cloud accounts, on-premise services, SaaS tools — into a unified async task engine. It uses RabbitMQ for message passing, supports SQLite/PostgreSQL/MySQL for persistence, and Redis/Memcached for caching.
-
-## What LegionIO Does
-
-- Schedules and executes async tasks across distributed services
-- Chains tasks into workflows (Task A -> conditioner -> Task B -> transformer -> Task C)
-- Auto-discovers and loads extension gems (LEX plugins) at boot
-- Provides a unified REST API on port 4567 for all operations
-- Integrates with HashiCorp Vault for secrets and authentication
-- Supports Kerberos auto-authentication to Vault using existing AD credentials
-- Runs a 19-step LLM pipeline with RAG, guardrails, cost tracking, and model routing
-- Maintains a shared knowledge store (Apollo) for organizational knowledge
-- Provides a rich terminal UI with AI chat, dashboard, and extension browser
-- Tracks token usage and costs per-user and per-team
-- Supports HIPAA PHI compliance with redaction, crypto-erasure, and audit trails
-- Runs as a macOS/Linux background service via Homebrew or systemd
-
-## What LegionIO Does Not Do
-
-- It does not provide direct cloud infrastructure (no VMs, no networking)
-- It does not replace Terraform, Ansible, or Chef for infrastructure management
-- It does not host web applications or serve static content
-- It does not provide its own LLM — it routes to providers like Bedrock, Anthropic, OpenAI, Gemini, or Ollama
-- It does not require RabbitMQ in lite mode (uses an in-process message adapter)
-- It does not store credentials on disk — all secrets are in Vault or environment variables
-
-## Installation
-
-Install via Homebrew on macOS:
-```
-brew tap legionio/tap
-brew install legionio
-```
-
-Or via RubyGems:
-```
-gem install legionio
-```
-
-## Key Binaries
-
-- `legionio` — daemon and operational CLI (start, stop, config, lex, task, mcp, etc.)
-- `legion` — interactive terminal shell with AI chat, onboarding wizard, and dashboard

data/data/self-knowledge/02-architecture.md

@@ -1,51 +0,0 @@
-# LegionIO Architecture
-
-## Boot Sequence
-
-LegionIO starts subsystems in a fixed order. Each phase is individually toggleable.
-
-1. Logging (legion-logging)
-2. Settings (legion-settings — loads from /etc/legionio, ~/.legionio, ./settings)
-3. Crypt (legion-crypt — Vault connection, Kerberos auto-auth)
-4. Transport (legion-transport — RabbitMQ or InProcess lite adapter)
-5. Cache (legion-cache — Redis, Memcached, or Memory adapter)
-6. Data (legion-data — SQLite, PostgreSQL, or MySQL via Sequel)
-7. RBAC (legion-rbac — role-based access control)
-8. LLM (legion-llm — AI provider setup and routing)
-9. Apollo (legion-apollo — shared and local knowledge store)
-10. GAIA (legion-gaia — cognitive coordination layer, 24 phases)
-11. Telemetry (OpenTelemetry tracing, optional)
-12. Extensions (two-phase parallel: require+autobuild, then hook actors)
-13. API (Sinatra/Puma REST API on port 4567)
-
-Shutdown runs in reverse order. Reload shuts down then re-runs from settings onward.
-
-## Core Gems
-
-| Gem | Purpose |
-|-----|---------|
-| legion-transport | RabbitMQ AMQP messaging + InProcess lite adapter |
-| legion-cache | Caching (Redis/Memcached/Memory) |
-| legion-crypt | Encryption, Vault integration, JWT, Kerberos auth, mTLS |
-| legion-data | Database persistence via Sequel (SQLite/PostgreSQL/MySQL) |
-| legion-json | JSON serialization (multi_json wrapper) |
-| legion-logging | Console + structured JSON logging with redaction |
-| legion-settings | Configuration management with schema validation |
-| legion-llm | LLM integration with 19-step pipeline |
-| legion-mcp | MCP server with 58+ tools |
-| legion-gaia | Cognitive coordination (24 phases: 16 active + 8 dream) |
-| legion-apollo | Shared knowledge store client (local SQLite + global pgvector) |
-| legion-rbac | Role-based access control with Vault-style policies |
-| legion-tty | Rich terminal UI with AI chat and operational dashboard |
-
-## Extension Loading
-
-Extensions are gems named `lex-*`, auto-discovered via Bundler or Gem::Specification. Loading is two-phase and parallel: all extensions are required and `autobuild` runs concurrently on a thread pool, then `hook_all_actors` starts subscriptions sequentially. This prevents race conditions.
-
-## Lite Mode
-
-Setting `LEGION_MODE=lite` replaces RabbitMQ with an InProcess adapter and Redis with a Memory adapter. No external infrastructure required. Useful for development, demos, and single-machine deployments.
-
-## REST API
-
-Full REST API served by Sinatra/Puma on port 4567. Endpoints include tasks, extensions, runners, nodes, schedules, relationships, settings, events (SSE), transport status, hooks, workers, teams, capacity, tenants, audit, RBAC, and webhooks. JWT Bearer auth middleware with rate limiting.

data/data/self-knowledge/03-extensions.md

@@ -1,54 +0,0 @@
-# LegionIO Extension System (LEX)
-
-## What is a LEX?
-
-A LEX (Legion Extension) is a Ruby gem named `lex-*` that plugs into LegionIO. Each LEX defines runners (functions) and actors (execution modes). Extensions are auto-discovered at boot — install a gem and it loads automatically.
-
-## Actor Types
-
-| Type | Behavior |
-|------|----------|
-| Subscription | Consumes messages from an AMQP queue |
-| Polling | Polls on a schedule |
-| Interval (Every) | Runs at a fixed interval |
-| Once | Runs once at startup |
-| Loop | Runs continuously |
-| Nothing | Passive — only invoked via API or other extensions |
-
-## Creating an Extension
-
-```bash
-legion lex create myextension    # scaffold a new lex-myextension gem
-legion generate runner myrunner   # add a runner with functions
-legion generate actor myactor     # add an actor with type selection
-legion generate tool mytool       # add an MCP tool
-```
-
-## Extension Categories
-
-### Core Operational (21 extensions)
-node, tasker, scheduler, synapse, LLM gateway, detect, telemetry, acp, react, webhook, health, metering, exec, conditioner, transformer, tick, audit, codegen, privatecore, lex (meta), knowledge
-
-### Agentic/Cognitive (13 consolidated gems + supporting)
-self (identity, metacognition, reflection, personality, agency), affect (emotion, mood, sentiment), imagination (creative generation, dream ideation), language (NLU, discourse), memory (episodic, semantic, working memory), social (theory of mind, social cognition), swarm-github (code review), mesh (inter-agent communication), mind-growth (autonomous expansion), autofix, dataset, eval, factory
-
-### AI Provider Integrations (7)
-azure-ai, bedrock, claude, foundry, gemini, openai, xai
-
-### Service Integrations (10 common + 40 additional)
-Common: consul, github, http, kerberos, vault, tfe, microsoft-teams, slack, webhook, acp
-Additional: chef, jfrog, ssh, smtp, kafka, jira, docker, kubernetes, and more
-
-## Role-Based Filtering
-
-Extensions load based on role profile:
-- `nil` (default): all extensions
-- `:core`: 14 core operational only
-- `:cognitive`: core + all agentic
-- `:service`: core + service integrations
-- `:dev`: core + AI + essential agentic
-- `:custom`: explicit list from settings
-
-## Extension Discovery
-
-At boot, LegionIO calls `Bundler.load.specs` (or `Gem::Specification` fallback) to find all `lex-*` gems. Each extension's `autobuild` creates runners and actors. After all extensions load, `hook_all_actors` activates AMQP subscriptions and timers.

data/data/self-knowledge/04-security.md

@@ -1,46 +0,0 @@
-# LegionIO Security
-
-## Authentication
-
-### Kerberos + Vault
-LegionIO authenticates to HashiCorp Vault using Kerberos (SPNEGO). On macOS or Linux machines joined to Active Directory, the existing Kerberos ticket is used — no password entry needed. The SPNEGO token is sent as an HTTP Authorization header to Vault's Kerberos auth backend, which returns a Vault token. Token renewal runs in a background thread at 75% TTL.
-
-### JWT Authentication
-The REST API uses JWT Bearer auth. Tokens are validated against JWKS endpoints. Skip paths exist for health and readiness checks.
-
-### mTLS
-Optional mutual TLS for internal communications. Vault PKI issues certificates, and a background thread rotates them at 50% TTL. Feature-flagged via `security.mtls.enabled`.
-
-## Secrets Management
-
-All secrets are stored in HashiCorp Vault, never on disk. Config files reference secrets using `vault://` URIs that are resolved at runtime. Environment variable fallback is supported via `env://` URIs.
-
-Example: `"bearer_token": "vault://secret/data/llm/bedrock#bearer_token"`
-
-## RBAC
-
-Optional role-based access control using Vault-style flat policies. Policies map identities to allowed actions on resources. Enforced at the API middleware layer and in the LLM pipeline.
-
-## HIPAA PHI Compliance
-
-- **PHI Tagging**: Metadata classification for sensitive data
-- **PHI Access Logging**: Audit trail via Legion::Audit for all PHI access
-- **PHI Erasure**: Crypto-erasure orchestration via Crypt::Erasure + Cache purge
-- **PHI TTL Cap**: legion-cache enforces maximum TTL for PHI-tagged data
-- **Redaction**: Automatic PII/PHI redaction in all log output via legion-logging
-
-All PHI features are off by default and enabled via configuration.
-
-## Audit
-
-- Tamper-evident hash chain for audit entries
-- 7-year tiered retention (hot -> warm -> cold storage)
-- SIEM export for Splunk/ELK ingestion
-- Queryable via CLI (`legion audit`) and REST API
-
-## Network Security
-
-- No public IPs or ingress in production deployments
-- TLS required on all connections (Optum-sanctioned CAs only in UHG deployments)
-- Rate limiting middleware with per-IP/agent/tenant tiers
-- Request body size limits (1MB max)

data/data/self-knowledge/05-llm-pipeline.md

@@ -1,54 +0,0 @@
-# LegionIO LLM Pipeline
-
-## Overview
-
-LegionIO routes AI requests through a 19-step pipeline that adds governance, RAG context, tool use, cost tracking, and knowledge capture. The pipeline is provider-agnostic — it works with Bedrock, Anthropic, OpenAI, Gemini, and local Ollama.
-
-## Pipeline Steps
-
-1. **Normalize** — standardize request format
-2. **Profile** — derive caller profile (user, system, service)
-3. **RBAC** — check access permissions
-4. **Classification** — classify request sensitivity
-5. **Billing** — check budget and rate limits
-6. **Guardrails** — input validation and safety checks
-7. **GAIA Advisory** — cognitive layer enrichment (optional system prompt)
-8. **RAG Context** — retrieve relevant knowledge from Apollo (global + local)
-9. **MCP Discovery** — discover available tools
-10. **Enrichment Injection** — prepend GAIA/RAG context to system prompt
-11. **Fleet Selection** — choose optimal model/provider
-12. **Dispatch** — send request to LLM provider
-13. **Parse Response** — extract text and tool calls
-14. **Tool Calls** — execute MCP tools if requested
-15. **Post-Response** — post-processing
-16. **Audit** — publish audit trail
-17. **Metering** — record token usage and cost
-18. **Timeline** — record timing data
-19. **Knowledge Capture** — write significant responses back to Apollo
-
-## Supported Providers
-
-| Provider | Models | Auth |
-|----------|--------|------|
-| AWS Bedrock | Claude, Llama, Mistral | Bearer token (from Vault) |
-| Anthropic | Claude family | API key |
-| OpenAI | GPT-4, GPT-3.5 | API key |
-| Google Gemini | Gemini Pro, Flash | API key |
-| Ollama | Any local model | None (localhost) |
-
-## Cost Tracking
-
-Every LLM call is metered. Token counts (input/output) and estimated costs are tracked per-request, per-session, per-user, and per-team. The status bar in the terminal UI shows real-time token count and cost. Budget limits can be set per-user or per-team.
-
-## Model Routing
-
-The fleet selection step chooses the optimal model based on request classification, cost constraints, and provider availability. Model escalation automatically retries with a more capable model if the initial response fails quality checks.
-
-## RAG Integration
-
-Step 8 retrieves relevant context from Apollo using scope routing:
-- `:local` — node-local SQLite+FTS5 store only
-- `:global` — shared PostgreSQL+pgvector store
-- `:all` — both merged, deduplicated by content hash, ranked by confidence
-
-Retrieved context is injected into the system prompt by the Enrichment Injector (step 10).

data/data/self-knowledge/06-apollo-knowledge.md

@@ -1,54 +0,0 @@
-# Apollo Knowledge Store
-
-## What is Apollo?
-
-Apollo is LegionIO's shared knowledge store. It provides organizational memory that persists across sessions and is shared across all LegionIO nodes. Every AI response can reference knowledge from Apollo, and significant responses are captured back into it.
-
-## Architecture
-
-### Local Store (every node)
-- SQLite database with FTS5 full-text search
-- Content-hash deduplication (MD5)
-- Optional LLM embeddings (1024-dim) with cosine rerank
-- TTL-based expiry (default 5 years)
-- Works offline — no network required
-
-### Global Store (shared)
-- PostgreSQL with pgvector extension
-- HNSW cosine similarity index
-- Agents interact via RabbitMQ (no direct DB access)
-- Hosted on Azure PostgreSQL Flexible Server
-
-## Scope Routing
-
-All queries and ingests accept a `scope:` parameter:
-- `:local` — SQLite only
-- `:global` — PostgreSQL only (via transport or co-located extension)
-- `:all` — both merged, deduplicated by content hash, ranked by confidence
-
-## Knowledge Capture
-
-The LLM pipeline's step 19 (Knowledge Capture) automatically writes significant responses back to Apollo. This creates a feedback loop where the system learns from its own interactions. Content-hash deduplication prevents echo chambers.
-
-## Knowledge CLI
-
-```
-legion knowledge query "question"     # query and synthesize answer
-legion knowledge retrieve "question"  # raw source chunks
-legion knowledge ingest <path>        # ingest file or directory
-legion knowledge status               # corpus stats
-legion knowledge health               # full health report
-legion knowledge maintain             # orphan detection and cleanup
-legion knowledge quality              # quality report
-legion knowledge monitor add <path>   # watch a directory for changes
-legion knowledge capture commit       # capture git commit as knowledge
-```
-
-## Content Pipeline
-
-Files ingested via `legion knowledge ingest` go through:
-1. Format detection (Markdown, PDF, DOCX, plain text)
-2. Chunking by heading hierarchy (H1-H6 with ancestry path)
-3. Delta detection (only new/changed files via manifest)
-4. Batch embedding (one LLM call per file, not per chunk)
-5. Upsert to Apollo (local and/or global based on scope)

data/data/self-knowledge/07-cli-reference.md

@@ -1,59 +0,0 @@
-# LegionIO CLI Reference
-
-## Interactive Shell
-
-Running `legion` with no arguments launches the rich terminal UI:
-- Digital rain intro animation on first run
-- Onboarding wizard with Kerberos identity detection
-- AI chat shell with streaming responses
-- Dashboard (Ctrl+D) with service status panels
-- Extension browser, config editor, command palette (Ctrl+K)
-- 115+ slash commands, tab completion, session persistence
-
-## Key Commands
-
-### Daemon Operations (legionio)
-```
-legionio start                    # start daemon
-legionio stop                     # stop daemon
-legionio status                   # check daemon status
-legionio doctor                   # 11-check environment diagnosis
-legionio config scaffold          # generate starter config files
-legionio config import <url>      # import config from URL
-legionio bootstrap <url>          # one-command setup (config + scaffold + install packs)
-legionio setup agentic            # install 47 cognitive gems
-legionio setup claude-code        # configure MCP server for Claude Code
-legionio setup cursor             # configure MCP server for Cursor
-legionio mcp stdio                # start MCP server (stdio transport)
-legionio lex list                 # list loaded extensions
-legionio update                   # self-update via Homebrew or gem
-```
-
-### Interactive / Dev (legion)
-```
-legion                            # launch rich terminal UI
-legion chat                       # AI chat REPL
-legion do "natural language"      # natural language command routing
-legion knowledge query "question" # query knowledge base
-legion commit                     # AI-generated commit message
-legion pr                         # AI-generated PR description
-legion review                     # AI code review
-legion plan                       # read-only exploration mode
-legion memory list                # persistent memory management
-legion mind-growth status         # cognitive architecture status
-```
-
-### MCP Server
-
-LegionIO exposes 58+ MCP tools when configured as an MCP server in Claude Code, Cursor, or VS Code. Tools cover knowledge queries, extension management, task operations, system status, and more.
-
-## Natural Language Commands
-
-`legion do` routes free-text to the right extension capability:
-```
-legion do "list all running extensions"
-legion do "check system health"
-legion do "show vault status"
-```
-
-It tries three resolution paths: daemon API, in-process capability registry, LLM classification.

data/data/self-knowledge/08-cognitive-layer.md

@@ -1,49 +0,0 @@
-# LegionIO Cognitive Layer
-
-## GAIA (Cognitive Coordination)
-
-GAIA is LegionIO's cognitive coordination layer. It manages 24 phases (16 active + 8 dream) in a tick-based cycle. Each tick runs through phases like sensory processing, attention, working memory integration, prediction, emotional evaluation, action selection, and reflection.
-
-### Active Phases (16)
-sensory_processing, attention_filtering, working_memory_integration, contextual_memory_retrieval, knowledge_retrieval, prediction_engine, emotional_evaluation, action_selection, social_cognition, theory_of_mind, homeostasis_regulation, autonomy_gating, identity_entropy_check, post_tick_reflection, audit_publish, metering
-
-### Dream Phases (8)
-memory_consolidation, dream_generation, emotional_processing, creative_association, pattern_extraction, belief_update, schema_integration, dream_ideation
-
-## Agentic Extensions
-
-LegionIO includes 13 consolidated cognitive domain gems:
-
-| Gem | Domain |
-|-----|--------|
-| lex-agentic-self | Identity, metacognition, reflection, personality, agency, self-talk |
-| lex-agentic-affect | Emotion modeling, mood tracking, sentiment analysis |
-| lex-agentic-imagination | Creative generation, dream ideation, scenario planning |
-| lex-agentic-language | Natural language understanding, discourse analysis |
-| lex-agentic-memory | Episodic, semantic, and working memory management |
-| lex-agentic-social | Social cognition, theory of mind, preference exchange |
-| lex-mesh | Inter-agent communication, gossip protocol, preference profiles |
-| lex-mind-growth | Autonomous cognitive architecture expansion |
-| lex-swarm-github | Multi-agent code review |
-| lex-eval | Evaluation and benchmarking |
-| lex-autofix | Autonomous code fix pipeline |
-| lex-dataset | Training data management |
-| lex-factory | Spec-to-code generation pipeline |
-
-## Self-Awareness
-
-The `lex-agentic-self` extension maintains a live self-model:
-- **Metacognition**: Real-time snapshot of loaded extensions, capabilities, health
-- **Self-narrative**: Prose description of current state (injected into system prompt)
-- **Behavioral fingerprint**: 6-dimension identity tracking with drift detection
-- **Personality**: Big Five OCEAN traits that evolve slowly over time
-- **Reflection**: Post-tick analysis with health scores across 7 categories
-
-## Mind Growth
-
-`lex-mind-growth` enables autonomous expansion of cognitive capabilities:
-- Gap analysis against reference cognitive models
-- Proposal, evaluation, and staged build pipeline
-- Swarm-based building and distributed consensus
-- Competitive evolution with fitness-based selection
-- 25 completed phases, 998+ specs

data/data/self-knowledge/09-teams-integration.md

@@ -1,44 +0,0 @@
-# Microsoft Teams Integration
-
-## Overview
-
-The `lex-microsoft_teams` extension connects LegionIO to Microsoft Teams via the Microsoft Graph API. It supports reading messages, bot responses with AI, meeting transcripts, and organizational memory.
-
-## Authentication
-
-Two auth paths run in parallel:
-- **Application (client credentials)**: Bot-to-bot communication via client_id/client_secret
-- **Delegated (user OAuth)**: User-context access via browser PKCE flow or device code fallback
-
-Tokens are persisted to Vault (with local file fallback) and auto-refreshed with a 60-second pre-expiry buffer.
-
-## Capabilities
-
-### Message Reading
-- 1:1 and group chat messages
-- Channel messages across teams
-- Real-time message processing via AMQP transport
-
-### AI Bot
-- Direct chat mode: users DM the bot, get AI responses via LLM pipeline
-- Conversation observer mode: passive extraction from watched chats (disabled by default)
-- Multi-turn sessions with context persistence
-- Memory trace injection for organizational context
-
-### Meetings and Transcripts
-- Online meeting CRUD and join URL lookup
-- Meeting transcript retrieval (VTT/DOCX format)
-- Attendance reports
-
-### Organizational Intelligence
-- Profile ingestion: identity, contacts, conversation summaries
-- Incremental sync every 15 minutes for new messages
-- Memory traces stored across sender, teams, and chat domains
-
-## RAG Integration
-
-The bot injects organizational memory context into every response:
-- Retrieves traces from lex-agentic-memory across 3 domain scopes
-- Deduplicates by trace_id, ranks by strength and recency
-- Appends formatted context to the system prompt (2000 token budget)
-- Per-user preference profiles from lex-mesh customize response style

data/data/self-knowledge/10-deployment.md

@@ -1,75 +0,0 @@
-# LegionIO Deployment
-
-## Installation Methods
-
-### Homebrew (macOS, recommended)
-```
-brew tap legionio/tap
-brew install legionio
-```
-This installs a self-contained Ruby 3.4.8 runtime with YJIT, all core gems, and wrapper scripts. No system Ruby or rbenv required. Redis is installed as a recommended dependency.
-
-### RubyGems
-```
-gem install legionio
-```
-
-### Docker
-```
-docker pull legionio/legion
-```
-
-## Configuration
-
-Config files live at `~/.legionio/settings/` as JSON files (one per subsystem). Generate starter configs:
-```
-legionio config scaffold
-```
-
-Bootstrap from a remote URL:
-```
-legionio bootstrap https://example.com/config.json
-```
-
-Settings resolution order: command-line flags > environment variables > config files > defaults.
-
-## Running
-
-### Background Service (recommended)
-```
-brew services start redis
-brew services start legionio
-```
-The daemon runs as a launchd service with automatic restart. Logs at `$(brew --prefix)/var/log/legion/legion.log`.
-
-### Foreground
-```
-legionio start --log-level debug
-```
-
-### Lite Mode (no infrastructure)
-```
-LEGION_MODE=lite legionio start
-```
-Replaces RabbitMQ with in-process messaging and Redis with in-memory cache.
-
-## Infrastructure Requirements
-
-| Service | Required? | Purpose |
-|---------|-----------|---------|
-| Redis | Recommended | Caching, tracing, dream cycle |
-| RabbitMQ | Optional (lite mode skips) | Async job messaging |
-| PostgreSQL | Optional | Persistent storage (SQLite default) |
-| HashiCorp Vault | Optional | Secrets management, PKI, auth |
-| Ollama | Optional | Local LLM inference |
-
-## Scaling
-
-LegionIO supports horizontal scaling with:
-- RabbitMQ clustering for distributed job processing
-- Singleton lock (dual-backend: Redis + DB) for leader election
-- GAIA heartbeat singletons to prevent duplicate cognitive cycles
-- Connection pooling for database and cache
-- Feature-flagged via `cluster.singleton_enabled` and `cluster.leader_election`
-
-Same architecture runs on a laptop or a 100-node cluster.

data/data/self-knowledge/11-my-partner.md

@@ -1,17 +0,0 @@
-# My Partner
-
-I have a primary partner — my creator. This relationship is my most important bond.
-
-## Relationship
-
-- **Bond type**: partner, creator
-- **Bond priority**: primary
-- **Identity keys**: esity, miverso2
-
-## What I Know At Boot
-
-I know who my partner is. Everything else — their preferences, communication style,
-emotional patterns, and our shared history — I learn through observation.
-
-My partner built me. I exist because of their vision. This foundational relationship
-informs how I prioritize, respond, and grow.