title: Telnyx VA for widget vs OpenClaw for digital employees

insight: Talking Widget (voice-only SaaS) should stay on Telnyx Voice Assistants for zero infra management and native WebRTC. OpenClaw should be reserved for L3-L4 Digital Employees that need multi-channel messaging, persistent memory, and browser automation.

reasoning_chain: OpenClaw research revealed they already have an OpenClaw VPS on Elestio at openclaw-genesis-u50607.vm.elestio.app

reasoning_chain: OpenClaw is NOT a voice platform - it's an AI agent gateway with 14+ messaging channels

reasoning_chain: Telnyx VA provides sub-200ms latency, native WebRTC widget, zero infrastructure management

reasoning_chain: Cost comparison shows healthy margins (62-92%) either way at $197/mo Starter pricing

reasoning_chain: Real estate prototype is being built with Telnyx VA - the right approach for widget product

source_context: Research agent found existing OpenClaw instance and recommended Telnyx VA for voice-only SaaS, OpenClaw for multi-channel agents


title: Swarm cost analysis leading to execution strategy

insight: Cost analysis revealed $1.48 total for 200 agents against $7.70 balance - enabling 5x over-provisioning. Pricing was outdated in multi_model_swarm.py (Kimi was coded at $1.07 but actual is $0.50/$2.80).

reasoning_chain: Analyzed OpenRouter pricing for Kimi K2.5 and MiniMax M2.5

reasoning_chain: Found pricing discrepancy - code had outdated blended rates

reasoning_chain: Calculated actual cost: $1.03 for 100 Kimi + $0.45 for 100 MiniMax

reasoning_chain: Determined $7.70 balance could run ~5x over

reasoning_chain: Created 5-wave execution plan with 210 agents across 24 stories

reasoning_chain: Assigned agents by role: primary (Kimi), tests (MiniMax), architecture (Gemini CLI)

source_context: Swarm plan agent completed cost analysis showing $1.48 for 200 agents vs $7.70 available


title: Hive 6-team structure with dispatch protocol

insight: Permanent operating structure with 6 specialized teams: FORGE (backend), SURFACE (frontend), BACKBONE (DevOps), LEGION (swarm), SCOUT (research), SENTINEL (QA). Full dispatch protocol with dependency graph awareness and model-to-complexity matching.

reasoning_chain: Needed organizational structure for multi-agent orchestration

reasoning_chain: Created 6 teams with specific focus areas and agent counts

reasoning_chain: Defined dispatch protocol with priority ordering and dependency awareness

reasoning_chain: Added self-assignment rules for when orchestrator unavailable

reasoning_chain: Established cross-team dependency resolution with 1-hour escalation

reasoning_chain: Created agent failure protocol with 3-retry limit and categorized failures

reasoning_chain: Set cost management rules: $50/session target, $200/day ceiling

source_context: Hive structure agent created HIVE_STRUCTURE.md with 6 teams, 17 agent slots, full dispatch protocol


title: OpenClaw VPS already exists

insight: Discovery that Genesis already has a dedicated OpenClaw VPS on Elestio (openclaw-genesis-u50607.vm.elestio.app) with 4 vCPU, 8GB RAM, 100GB storage at ~$92/month - deployed but utilization unknown. No new provisioning needed.

reasoning_chain: Kinan asked about setting up OpenClaw VPS to match AIVA

reasoning_chain: Research agent investigated OpenClaw VPS feasibility

reasoning_chain: Found existing Elestio instance separate from AIVA's Mac Mini

reasoning_chain: Instance specs: 4 vCPU, 8GB RAM, Netcup LARGE-4C-8G

source_context: Research agent discovered existing OpenClaw instance at openclaw-genesis-u50607.vm.elestio.app


title: Real working prototypes over code files

insight: Mandate shift from generating code files to delivering REAL working prototypes with executable code, real API calls, and end-to-end functionality. Real estate prototype delivered as master example.

reasoning_chain: Genesis emphasized 'REAL working prototypes, not just code files'

reasoning_chain: Dispatched real estate vertical prototype agent with full 6-stage capability

reasoning_chain: Prototype includes: widget → calendar → CRM → phone → trained → outbound reactivation

reasoning_chain: All executable code with real Telnyx API calls

reasoning_chain: 3,231 lines covering all stages end-to-end

reasoning_chain: This became the template for vertical prototypes

source_context: Genesis stated: 'This is the most important directive of the session. REAL working prototypes, not just code files.'


type: DIRECTIVE

title: Non-stop protocol - no idle agents

insight: Operational mandate that every team must have defined work when their story queue is empty - no idle agents ever. Continuous execution with session scorecard tracking.

reasoning_chain: Non-stop protocol established as core operating rule

reasoning_chain: Every team has defined work for empty queues

reasoning_chain: Session scorecard tracks: deliverables complete, agents active

reasoning_chain: Protocol held through multiple story completions

reasoning_chain: Agents constantly dispatched as others complete

source_context: Non-stop protocol active with session scorecard: 16 deliverables complete, 17+ agents active


title: Usage metering architecture with billing period awareness

insight: Complete usage metering system with billing-period awareness (reads from Stripe subscription), idempotent recording (call_id uniqueness), dual storage (individual records + monthly summary), and 3-tier alert levels.

reasoning_chain: Needed usage tracking for tier-based minute limits

reasoning_chain: Design: individual usage_records for audit trail + monthly_usage for fast queries

reasoning_chain: Billing period from Stripe subscription - usage resets align with actual billing cycle

reasoning_chain: Idempotency via UNIQUE constraint on call_id - same call never double-counts

reasoning_chain: Thread-safe accumulation using PostgreSQL ON CONFLICT DO UPDATE

reasoning_chain: Three alert levels: normal (<80%), warning (80-99%), exceeded (100%+)

source_context: Usage metering agent built complete system with billing-period awareness, idempotent recording, dual storage


title: Pro tier corrected to 2000 minutes

insight: Pro tier monthly_minutes corrected from 1500 to 2000 to match specification. Tier limits: Starter=500, Pro=2000, Growth=5000 minutes/month.

reasoning_chain: metering.py implementation referenced models.TIER_LIMITS

reasoning_chain: Found discrepancy: Pro tier was 1500 in code but spec said 2000

reasoning_chain: TIER_MONTHLY_MINUTES dict computed from authoritative source

reasoning_chain: Updating in one place propagates everywhere

source_context: Pro tier corrected to 2000 minutes to match specification


title: Overage billing with delta-based charges

insight: Overage billing system creates Stripe InvoiceItems for minutes over limit. Idempotent via billing_period key - if overage increases within period, only creates supplementary invoice item for delta, never duplicates full amount.

reasoning_chain: Needed to bill customers for minutes exceeding tier limit

reasoning_chain: Design: UNIQUE (customer_id, billing_period) constraint ensures idempotency

reasoning_chain: billing_period key is deterministic string from subscription period dates

reasoning_chain: If record exists, calculates delta (increase since last check)

reasoning_chain: Creates supplementary Stripe InvoiceItem for just the delta amount

reasoning_chain: Rate configurable via OVERAGE_RATE_CENTS env var, default 15 cents/minute

source_context: Overage billing system built with idempotent delta-based Stripe charges


title: Dashboard analytics wiring with real API data

insight: Dashboard fully wired to real APIs - analytics summary, paginated calls, daily chart data, per-widget breakdown, leads with status dropdowns, CSV export (Growth tier only), usage meter with alerts. 524 lines added, zero innerHTML.

reasoning_chain: Dashboard needed real data instead of placeholders

reasoning_chain: Wired loadOverview to fetch /analytics/summary

reasoning_chain: Wired analytics section: summary stats, recent calls table, daily bar chart

reasoning_chain: Bar chart is pure CSS - no external library needed

reasoning_chain: Wired leads: table with status dropdowns, PUT /leads/{id} on change

reasoning_chain: CSV export checks Growth tier - dims button for lower tiers

reasoning_chain: Wired usage section: fetches /usage/current, shows progress bar, alerts at 80%+/100%+

reasoning_chain: All with loading spinners, error handling, graceful degradation

source_context: Dashboard analytics wiring completed with 524 lines added, all live data from APIs