mindforge-cc 11.3.0 → 11.3.1

package/.claude/commands/mindforge/iot.md

@@ -0,0 +1,31 @@
+---
+name: mindforge:iot
+description: "Design IoT platform architecture. Usage: /mindforge:iot [component] [--protocol mqtt|coap|http] [--scale devices]"
+argument-hint: "[component] [--protocol mqtt|coap|http] [--scale devices]"
+allowed-tools:
+  - list_dir
+  - view_file
+---
+
+<objective>
+Designs IoT platform architectures for device connectivity, telemetry ingestion, command/control, and edge computing. Produces designs for MQTT/CoAP brokers, device management, time-series data storage, real-time analytics, and firmware update systems with support for millions of concurrent devices.
+</objective>
+
+<execution_context>
+@.mindforge/skills/iot-platform/SKILL.md
+</execution_context>
+
+<context>
+Skills Directory: `.mindforge/skills/iot-platform/`
+State: Evaluates IoT use case, device scale, protocol requirements, and produces architecture with device provisioning, telemetry pipelines, edge processing, and device twin patterns for industrial, consumer, and smart city applications.
+</context>
+
+<process>
+1. **Use Case Analysis**: Identify IoT domain (industrial monitoring, smart home, connected vehicles, agriculture) and classify device types (sensors, actuators, gateways), communication patterns (telemetry streaming, command/response, firmware updates), and scale (thousands to millions of devices).
+2. **Protocol Architecture**: Select communication protocols based on device constraints (MQTT for reliable messaging, CoAP for constrained devices, HTTP/REST for simple integrations), design pub/sub topic hierarchies, and implement protocol gateways for multi-protocol support with TLS encryption.
+3. **Device Management**: Design device lifecycle management with secure provisioning (X.509 certificates, token-based auth), device registry with metadata/tags, health monitoring with heartbeat tracking, and bulk operations for fleet management (configuration updates, diagnostics).
+4. **Telemetry Ingestion**: Architect high-throughput data ingestion pipeline with MQTT broker clustering (EMQX, HiveMQ), message queuing (Kafka, Pulsar) for decoupling, and time-series database (InfluxDB, TimescaleDB) for sensor data storage with downsampling and retention policies.
+5. **Edge Computing**: Implement edge processing with local data filtering/aggregation to reduce bandwidth, edge analytics for real-time anomaly detection, offline operation with store-and-forward capabilities, and edge AI model deployment for predictive maintenance.
+6. **Command and Control**: Design bidirectional communication for remote device control with command queuing, acknowledgment patterns, timeout handling, and desired state management using device twin/shadow patterns for eventually consistent configuration.
+7. **Analytics and Visualization**: Build real-time dashboards for device status monitoring, streaming analytics for alerting on threshold violations, historical trend analysis, and integration with ML pipelines for predictive analytics using telemetry data.
+</process>

package/.claude/commands/mindforge/knowledge-graph.md

@@ -0,0 +1,37 @@
+---
+name: mindforge:knowledge-graph
+description: "Design knowledge graph architecture. Usage: /mindforge:knowledge-graph [domain] [--db neo4j|neptune|dgraph] [--scale nodes]"
+argument-hint: "[domain] [--db neo4j|neptune|dgraph] [--scale nodes]"
+allowed-tools:
+  - list_dir
+  - view_file
+---
+
+<objective>
+Design a scalable knowledge graph system for relationship-rich data modeling, entity resolution, and semantic querying. This command creates graph database architecture with schema design, query optimization strategies, entity linking pipelines, and reasoning capabilities for complex relationship traversals and inference.
+</objective>
+
+<execution_context>
+@.mindforge/skills/knowledge-graphs/SKILL.md
+</execution_context>
+
+<context>
+Skills Directory: `.mindforge/skills/knowledge-graphs/`
+State: Analyzes domain entity relationships, query patterns, scale requirements, and reasoning needs to design graph schema, database selection, ingestion pipelines, and query optimization strategies.
+</context>
+
+<process>
+1. **Domain and Schema Modeling**: Identify core entities and relationship types, design ontology with classes, properties, and constraints, model multi-hop relationships and temporal dimensions, and define cardinality rules and validation logic.
+
+2. **Graph Database Selection**: Compare options (Neo4j for ACID/Cypher, Neptune for AWS integration, Dgraph for distributed scale), evaluate trade-offs (consistency vs availability, query expressiveness vs performance), and specify deployment topology (single-node, cluster, multi-region).
+
+3. **Data Ingestion and ETL**: Design entity extraction pipelines from structured/unstructured sources, implement entity resolution and deduplication with fuzzy matching, create relationship inference rules from co-occurrence patterns, and build incremental update mechanisms for real-time graphs.
+
+4. **Query Optimization**: Implement indexing strategies for high-cardinality properties, design query patterns for common traversals (shortest path, neighborhood expansion, pattern matching), optimize for specific workloads (OLTP vs OLAP graph queries), and create materialized views for frequent aggregations.
+
+5. **Entity Linking and Enrichment**: Design entity disambiguation with contextual embeddings, implement cross-source entity alignment, create knowledge base augmentation from external graphs (Wikidata, DBpedia), and build confidence scoring for inferred relationships.
+
+6. **Graph Reasoning and Inference**: Implement rule-based inference (transitive closure, property inheritance), design probabilistic reasoning with uncertainty quantification, create graph neural network embeddings for link prediction, and specify reasoning depth limits for query performance.
+
+7. **Monitoring and Maintenance**: Define graph quality metrics (completeness, consistency, freshness), implement anomaly detection for suspicious relationships, design archival and pruning strategies for temporal graphs, and create versioning mechanisms for schema evolution.
+</process>

package/.claude/commands/mindforge/lakehouse.md

@@ -0,0 +1,31 @@
+---
+name: mindforge:lakehouse
+description: "Design data lakehouse architecture. Usage: /mindforge:lakehouse [domain] [--format delta|iceberg|hudi] [--layer bronze|silver|gold]"
+argument-hint: "[domain] [--format delta|iceberg|hudi] [--layer bronze|silver|gold]"
+allowed-tools:
+  - list_dir
+  - view_file
+---
+
+<objective>
+Design comprehensive lakehouse system architecture with best practices and production-ready patterns.
+</objective>
+
+<execution_context>
+@.mindforge/skills/data-lakehouse/SKILL.md
+</execution_context>
+
+<context>
+Skills Directory: `.mindforge/skills/data-lakehouse/`
+State: Analyzes requirements, constraints, and scale to generate optimized lakehouse architecture.
+</context>
+
+<process>
+1. **Requirement Analysis**: Analyze domain-specific requirements, performance constraints, and scalability needs.
+2. **Architecture Design**: Design system architecture with component interaction patterns and data flow.
+3. **Technology Selection**: Evaluate and select appropriate technologies, tools, and frameworks.
+4. **Integration Strategy**: Define integration patterns with existing systems and external dependencies.
+5. **Optimization Approach**: Implement performance, cost, and resource optimization strategies.
+6. **Monitoring Framework**: Design observability, alerting, and debugging mechanisms.
+7. **Deployment Planning**: Create deployment strategy with rollback procedures and disaster recovery.
+</process>

package/.claude/commands/mindforge/lead.md

@@ -0,0 +1,31 @@
+---
+name: mindforge:lead
+description: "Technical leadership guidance and decision framework. Usage: /mindforge:lead [situation] [--context team|org|technical]"
+argument-hint: "[situation] [--context team|org|technical]"
+allowed-tools:
+  - list_dir
+  - view_file
+---
+
+<objective>
+Provides technical leadership guidance for decision-making, team management, and organizational influence. Produces frameworks for handling complex situations including technical direction, conflict resolution, career development, and strategic planning for engineering leaders at all levels.
+</objective>
+
+<execution_context>
+@.mindforge/skills/technical-leadership/SKILL.md
+</execution_context>
+
+<context>
+Skills Directory: `.mindforge/skills/technical-leadership/`
+State: Evaluates leadership challenges, organizational context, and produces actionable frameworks with decision matrices, communication strategies, and stakeholder management approaches for technical leaders.
+</context>
+
+<process>
+1. **Situation Analysis**: Identify leadership challenge category (technical decision-making, people management, cross-functional collaboration, organizational change) and assess scope of impact (team, department, organization), urgency (immediate, short-term, strategic), and stakeholder complexity.
+2. **Context Mapping**: Map organizational context including reporting structure, decision-making authority, team dynamics, cultural norms, and political landscape to understand constraints and leverage points for effective leadership.
+3. **Decision Framework**: Apply appropriate decision-making framework (RACI for ownership clarity, trade-off analysis for technical choices, stakeholder mapping for buy-in, forcing functions for priority decisions) based on situational characteristics.
+4. **Communication Strategy**: Design multi-level communication plan with tailored messaging for different audiences (executives, peers, direct reports, cross-functional partners) considering timing, medium (written, verbal, visual), and feedback mechanisms.
+5. **People Development**: Address team growth needs with career development frameworks, delegation strategies matching skill levels, mentorship approaches, performance feedback models, and creating psychological safety for innovation and healthy conflict.
+6. **Influence Patterns**: Implement influence strategies including building coalitions, leveraging data and prototypes for technical persuasion, managing up with executive-friendly communication, and navigating organizational politics with integrity.
+7. **Action Plan**: Generate specific action plan with timelines, success metrics, contingency options, and reflection checkpoints to adapt approach based on outcomes and new information emerging from implementation.
+</process>

package/.claude/commands/mindforge/learn-instinct.md

@@ -0,0 +1,58 @@
+---
+description: Manually capture a learned behavior as an instinct with initial confidence scoring. Usage - /mindforge:learn-instinct [observation] [--behavior "what to do"] [--confidence 0.7] [--tags tag1,tag2]
+---
+
+<objective>
+Create a new instinct entry manually, capturing a behavioral pattern the agent
+should remember and apply in future sessions.
+</objective>
+
+<execution_context>
+@.mindforge/engine/instincts/instinct-schema.md
+@.mindforge/engine/instincts/capture-engine.md
+@.mindforge/skills/continuous-learning/SKILL.md
+</execution_context>
+
+<context>
+$ARGUMENTS
+</context>
+
+<process>
+1. Parse arguments:
+   - observation: what pattern was observed (required)
+   - --behavior: what to do when pattern detected (required)
+   - --confidence: initial confidence (default: 0.7 for manual capture)
+   - --tags: classification tags (optional, auto-derived if not provided)
+2. **Deduplication check:**
+   - Read `.mindforge/engine/instincts/instinct-store.jsonl`
+   - Compare observation against all active instincts (same project)
+   - If >80% word overlap: warn "Similar instinct exists" and show it
+   - Ask user: reinforce existing or create new?
+3. **Capacity check:**
+   - Count active instincts for current project
+   - If at 100: identify lowest-confidence instinct for pruning
+   - Inform user: "At capacity. Will prune: [lowest instinct] (confidence: X)"
+4. **Create instinct entry:**
+   ```json
+   {
+     "id": "inst-[generate-uuid]",
+     "created_at": "[current timestamp]",
+     "updated_at": "[current timestamp]",
+     "observation": "[from args]",
+     "behavior": "[from args]",
+     "confidence": [from args or 0.7],
+     "times_applied": 0,
+     "times_succeeded": 0,
+     "times_failed": 0,
+     "project": "[current project name]",
+     "tags": [from args or auto-derived],
+     "status": "active",
+     "promoted_to_skill": null,
+     "last_applied_at": null,
+     "source_sessions": ["[current session id]"]
+   }
+   ```
+5. Append entry to `instinct-store.jsonl`.
+6. Report: "Instinct captured. Active: [count]/100. Confidence: [X]."
+7. Log in AUDIT: instinct_created event.
+</process>

package/.claude/commands/mindforge/learn.md

@@ -0,0 +1,147 @@
+---
+description: Convert any knowledge source into a reusable, validated, committed MindForge SKILL.md.
+---
+
+# MindForge v2 — Learn Command
+# Usage: /mindforge:learn [url|path|--session|npm:package] [--name skill-name] [--tier project|org|core]
+# Version: v2.0.0-alpha.6
+
+## Purpose
+Convert any knowledge source into a reusable, validated, committed MindForge SKILL.md.
+Feed Claude your documentation and it writes down what it learned — for every future session.
+
+## The insight
+Every developer on your team already knows how Prisma works, how your internal API
+conventions are structured, how your CI pipeline behaves. That knowledge lives in their
+heads and in documentation. `/mindforge:learn` captures it permanently as skills that
+load automatically whenever relevant work begins.
+
+## Usage examples
+
+### Learn from external documentation
+```
+/mindforge:learn https://docs.prisma.io/concepts/components/prisma-schema
+/mindforge:learn https://stripe.com/docs/webhooks
+/mindforge:learn https://docs.aws.amazon.com/lambda/latest/dg/nodejs-handler.html
+```
+→ Fetches the page (with SSRF protection)
+→ Uses Gemini 2.5 Pro (1M context) for large docs, claude-sonnet-4-6 for smaller ones
+→ Extracts 10 patterns + 15-25 trigger keywords
+→ Writes SKILL.md + scores it + presents for approval
+
+### Learn from local documentation
+```
+/mindforge:learn ./docs/api-conventions.md
+/mindforge:learn ./docs/internal/
+/mindforge:learn ./CONTRIBUTING.md
+```
+→ Reads local files directly (no model call for reading, only for analysis)
+→ Perfect for: internal API docs, team conventions, onboarding guides
+
+### Learn from npm package docs
+```
+/mindforge:learn npm:zod
+/mindforge:learn context7:zod
+/mindforge:learn npm:drizzle-orm
+/mindforge:learn context7:drizzle-orm
+```
+→ Fetches README from npm registry or real-time docs from Context7
+→ Extracts patterns from the package documentation
+
+### Learn from current session
+```
+/mindforge:learn --session
+```
+→ Analyses SUMMARY files from the most recent phase
+→ Finds patterns that appeared across 2+ tasks
+→ Generates up to 3 skills from what was learned (focused: quality over quantity)
+→ Does NOT repeat patterns already in the knowledge base
+
+## Flags
+
+### --name [skill-name]
+Override the auto-generated skill name (kebab-case).
+Default: inferred from the URL domain/path or file name.
+Example: `/mindforge:learn ./docs/prisma-patterns.md --name prisma-advanced`
+
+### --tier [project|org|core]
+Where to install the skill (default: project).
+- project: only loads in this project (T3)
+- org: loads in all projects using this org config (T2)
+- core: loads everywhere (T1 — use sparingly)
+
+### --model [model-id]
+Override the model used for analysis.
+Default: RESEARCH_MODEL for large content (>50K chars), EXECUTOR_MODEL for small.
+
+## Output format
+
+```
+📚 Learning from: https://docs.prisma.io/...
+
+  🔍 Fetching content...            done (148K chars)
+  🧠 Extracting patterns (gemini-2.5-pro)...
+  Step 1/3 — Extracting patterns... done (10 patterns)
+  Step 2/3 — Generating triggers... done (22 triggers)
+  Step 3/3 — Writing SKILL.md...    done
+
+📊 Skill Quality Score: 84/100 (Good — can register + publish)
+  trigger_coverage   : 26/30   ✅
+  mandatory_actions  : 21/25   ✅
+  code_examples      : 17/20   ✅
+  self_check         : 12/15   ✅
+  injection_safe     : 10/10   ✅
+  no_placeholders    : 9/10    ✅
+  version_history    : 8/10    ⚠️
+
+Preview (top 3 patterns):
+  1. [CRITICAL] Always define explicit cascade behaviour
+     "Set onDelete on every @relation — never rely on database defaults"
+  2. [HIGH] Use compound indexes for cursor pagination
+     "Always index (createdAt, id) together for reliable cursor pagination"
+  3. [HIGH] Never use String for UUID fields in Prisma schema
+     "Use @id @default(uuid()) with the String type — Prisma handles this"
+
+Triggers (22): prisma schema, schema.prisma, @relation, prisma migrate,
+               @id @default, prisma.findMany, prisma generate, model definition...
+
+Skill file: .mindforge/skills/prisma-schema/SKILL.md
+
+[ y ] Register in project tier and commit
+[ n ] Discard
+[ e ] Edit SKILL.md before registering
+[ p ] Register AND publish to community marketplace (score ≥ 80 ✅)
+```
+
+## After registration
+
+```
+✅ Skill registered: prisma-schema (T3 Project)
+
+  Will auto-load when tasks contain:
+    "prisma schema", "schema.prisma", "@relation", "prisma migrate"...
+
+  Committed: feat(skills): learn prisma-schema from docs.prisma.io
+
+  Next: /mindforge:skills info prisma-schema
+```
+
+## Integration with auto-capture
+When `AUTO_CAPTURE_SKILLS=true` in MINDFORGE.md:
+`/mindforge:learn --session` is called automatically after each phase completion.
+The prompt is shown; if no patterns found, it exits silently (no noise).
+
+## AUDIT entry
+```json
+{
+  "event": "skill_learned",
+  "source_type": "url|local|session|npm",
+  "source": "[url or path]",
+  "skill_name": "prisma-schema",
+  "quality_score": 84,
+  "pattern_count": 10,
+  "trigger_count": 22,
+  "tier": "project",
+  "cost_usd": 0.31
+}
+```

package/.claude/commands/mindforge/learning.md

@@ -0,0 +1,20 @@
+---
+description: Consult or initialize the project agentic learning memory - AGENTS_LEARNING.md
+---
+
+# /mindforge:learning [init]
+
+Consult the project's persistent engineering memory to avoid past mistakes and follow established best practices.
+
+## Usage
+
+- `/mindforge:learning`: Displays the current learning status and path to the learning file.
+- `/mindforge:learning init`: Initializes a new `AGENTS_LEARNING.md` in the project root if it doesn't already exist.
+
+## Why use this?
+Before starting any significant implementation or refactor, you MUST consult the learning memory. It contains project-specific "Anti-Patterns" to avoid and "Best Practices" that have been proven in this specific system.
+
+## Example
+1. Run `/mindforge:learning` to find where the learning file is.
+2. Read the file to understand recent architectural shifts or discovered failure scenarios.
+3. If the project is new, run `/mindforge:learning init` to scaffold the memory.

package/.claude/commands/mindforge/llm-route.md

@@ -0,0 +1,37 @@
+---
+name: mindforge:llm-route
+description: "Design LLM orchestration and routing. Usage: /mindforge:llm-route [system] [--strategy cascade|parallel|router] [--budget tokens]"
+argument-hint: "[system] [--strategy cascade|parallel|router] [--budget tokens]"
+allowed-tools:
+  - list_dir
+  - view_file
+---
+
+<objective>
+Design intelligent LLM orchestration systems that route requests across multiple models based on complexity, cost, and latency requirements. This command creates routing strategies (cascade, parallel, learned routing), fallback mechanisms, and optimization patterns that balance quality, speed, and cost across heterogeneous LLM deployments.
+</objective>
+
+<execution_context>
+@.mindforge/skills/llm-orchestration/SKILL.md
+</execution_context>
+
+<context>
+Skills Directory: `.mindforge/skills/llm-orchestration/`
+State: Analyzes request patterns, model capabilities, cost constraints, and quality thresholds to design routing logic, caching strategies, and orchestration workflows that optimize for throughput and accuracy.
+</context>
+
+<process>
+1. **Request Classification**: Design intent classification to route queries by type (factual lookup, creative generation, reasoning), implement complexity scoring using heuristics or learned classifiers, and create routing decision trees based on input characteristics.
+
+2. **Cascade Routing Strategy**: Implement cheapest-first cascade (Haiku → Sonnet → Opus) with confidence thresholding, design validation checks to determine if escalation is needed, and specify retry logic with context preservation across models.
+
+3. **Parallel Routing with Fusion**: Design parallel execution across multiple models for critical queries, implement response fusion strategies (voting, averaging, judge model selection), and optimize for latency with timeout and early-exit conditions.
+
+4. **Learned Routing Models**: Train routing classifiers on historical query/outcome data, implement feature extraction (query length, domain, user tier), and design online learning loops to adapt routing decisions based on performance feedback.
+
+5. **Caching and Deduplication**: Implement semantic caching with embedding similarity thresholds, design cache invalidation strategies for dynamic content, and create prompt canonicalization to maximize cache hit rates.
+
+6. **Cost and Performance Optimization**: Track cost per query across models with token usage accounting, implement budget constraints and throttling per user/tenant, and design cost-aware routing that prioritizes cheaper models when quality thresholds permit.
+
+7. **Fallback and Resilience**: Design graceful degradation when primary models are unavailable, implement retry logic with exponential backoff across providers, and create circuit breakers to isolate failing models without impacting overall system availability.
+</process>

package/.claude/commands/mindforge/load-test.md

@@ -0,0 +1,30 @@
+---
+description: Design load test scenario with profiles. Usage - /mindforge:load-test [endpoint] [--profile ramp|spike|soak] [--target-rps N]
+---
+
+<objective>
+Design and implement a load testing strategy with configurable profiles that
+validates system behavior under stress. Identifies breaking points, latency
+degradation curves, and resource exhaustion thresholds.
+</objective>
+
+<execution_context>
+@.mindforge/skills/load-testing/SKILL.md
+</execution_context>
+
+<context>
+$ARGUMENTS
+</context>
+
+<process>
+1. Define SLAs and performance objectives — target p50/p95/p99 latencies, maximum error rate, throughput requirements, and resource utilization ceilings.
+2. Select test type based on --profile flag: ramp (gradual increase to find ceiling), spike (sudden burst to test elasticity), or soak (sustained load to find memory leaks and connection exhaustion).
+3. Design the load profile with specific stages — VU ramp-up duration, hold duration, ramp-down. For spike: define burst magnitude and recovery window.
+4. Write the test script using k6 or Locust. Include realistic user flows, proper think times, data parameterization, and correlation of dynamic values.
+5. Configure thresholds that define pass/fail criteria — e.g., http_req_duration p95 < 500ms, http_req_failed < 1%, checks > 99%.
+6. Run the load test against staging environment. Ensure staging mirrors production topology (same instance types, connection pool sizes, rate limits).
+7. Analyze results: identify bottleneck (CPU, memory, DB connections, external dependency), find the inflection point where latency degrades non-linearly.
+8. Document findings with charts: latency vs throughput curve, error rate vs load, resource utilization timeline. Include specific recommendations for capacity planning.
+9. Create a repeatable test suite that can run in CI on a schedule (nightly) or before releases. Configure baseline comparison to detect regressions.
+10. Log load-test invocation in AUDIT with: endpoint, profile, target RPS, peak RPS achieved, p95 latency at peak.
+</process>

package/.claude/commands/mindforge/logistics.md

@@ -0,0 +1,31 @@
+---
+name: mindforge:logistics
+description: "Design logistics optimization system. Usage: /mindforge:logistics [component] [--type routing|warehouse|delivery]"
+argument-hint: "[component] [--type routing|warehouse|delivery]"
+allowed-tools:
+  - list_dir
+  - view_file
+---
+
+<objective>
+Designs logistics and supply chain optimization systems for route planning, warehouse management, and last-mile delivery. Produces architectures for vehicle routing algorithms, inventory optimization, real-time tracking, and delivery orchestration with cost and time efficiency goals.
+</objective>
+
+<execution_context>
+@.mindforge/skills/logistics-optimization/SKILL.md
+</execution_context>
+
+<context>
+Skills Directory: `.mindforge/skills/logistics-optimization/`
+State: Evaluates logistics optimization requirements, operational constraints, and produces architecture with route planning algorithms, warehouse automation integration, real-time tracking, and dynamic dispatch systems.
+</context>
+
+<process>
+1. **Domain Analysis**: Identify logistics scope (last-mile delivery, long-haul trucking, warehouse fulfillment, multi-modal shipping) and define optimization objectives (minimize cost, delivery time, carbon footprint), constraints (vehicle capacity, driver hours, time windows), and scale (orders/day, fleet size).
+2. **Route Optimization**: Design vehicle routing system with constraint satisfaction algorithms (VRP, CVRP with time windows), real-time route recalculation for dynamic orders, traffic-aware routing with ETA prediction, and multi-stop optimization considering driver shifts and vehicle capacity.
+3. **Warehouse Management Integration**: Architect WMS integration for order allocation to warehouses based on inventory availability and proximity, pick-pack-ship workflow orchestration, barcode/RFID tracking for package movement, and automated sorting system coordination.
+4. **Real-Time Tracking**: Implement GPS tracking for delivery vehicles with position updates, geofencing for delivery zone entry/exit events, mobile app for driver navigation and proof-of-delivery (signature, photo), and customer notification system with live tracking links.
+5. **Dynamic Dispatch**: Build dispatch system with load balancing across drivers, real-time order insertion into existing routes, driver assignment optimization based on location and capacity, and exception handling for failed deliveries with automatic rescheduling.
+6. **Inventory Optimization**: Design inventory forecasting with demand prediction, safety stock calculations, reorder point automation, and multi-warehouse inventory balancing to reduce stockouts while minimizing holding costs with ABC analysis for prioritization.
+7. **Analytics and Reporting**: Create operational dashboards with delivery performance metrics (on-time rate, cost per delivery, vehicle utilization), route efficiency analysis, driver performance tracking, and predictive analytics for demand forecasting and capacity planning.
+</process>