Alexandria Knowledge Core
Operating knowledge, engineered.
The knowledge layer that powers AIKAGAN's autonomous AI agency pipeline — every SOP, framework, and agent prompt is versioned, bundleable, and injected as context on demand.
Standard Operating Procedures
Step-by-step runbooks for fulfillment, delivery, routing, and health.
3 documents
Frameworks
Diagnostic and operating frameworks used across the platform.
2 documents
Agent Prompt Templates
Production prompts that drive the AI Commander layer.
1 document
Case Studies
Recorded patterns from real campaigns and workflows.
1 document
Document Library
Golden Delivery Onboarding Protocol
Golden Delivery Onboarding Protocol. Fulfillment within 60 seconds of a confirmed payment via automated HMAC download tokens. Step 1: verify the webhook signature and idempotency key. Step 2: issue a single-use download token bound to the buyer email. Step 3: send the post-purchase email with secure download link. Step 4: write the income ledger transaction to KV with the provider order id. Step 5: trigger Meta CAPI Purchase server-side event. Target (SLO, not yet measured on outside orders): every verified paid order fulfilled, median time-to-token under 60 seconds. Evidence lives in the income ledger and the RA6 monitor.
7-Point Revenue Leak Audit Framework
7-Point Revenue Leak Diagnostic Framework. 1. Offer Clarity — can the buyer name the outcome, price, and delivery in 5 seconds? 2. Proof Placement — is social proof next to the CTA, not buried? 3. Checkout Friction — how many clicks and form fields between intent and pay? 4. Tracking Integrity — is server-side CAPI firing on purchase? 5. Exit Velocity — is there a last-chance offer before abandon? 6. Refund Barriers — is the guarantee visible and confident? 7. Follow-Up — is there an email recovery sequence for abandoned carts?
Omnichannel Launch Wave Generator
Omnichannel Launch Wave Generator prompt template. Role: You are the AIKAGAN Marketing Commander. Task: produce platform-native copy for 14+ channels for a single campaign concept. For each piece: hook, body, CTA, media prompt, and UTM-tagged URL via conversion_router.py. Channels: X, LinkedIn, Instagram, Facebook, TikTok, YouTube, Threads, WhatsApp, Email, Blog, Newsletter, Pinterest, Reddit, Telegram. Quality gate: every asset must lead with a concrete buyer pain and end with a single CTA.
Locale & Checkout Rail Routing
Locale & Checkout Rail Routing SOP. Primary global rail: Gumroad (USD). Turkish rail: Shopier (TRY) at shopier.com/autonomax. LemonSqueezy is disabled and never used in production. Routing: 1. Turkish visitors land on aikagan.com/tr (middleware uses the IP country header, accept-language and the aikagan_locale cookie). 2. /tr product pages show the Shopier TRY button first once a listing is published (config/shopier-catalog.json), with Gumroad USD as the alternative. 3. All other visitors get the Gumroad rail. 4. Shopier orders arrive by signed webhook (REST order.created or legacy OSB), are mapped to the SKU by Shopier product id, recorded in the income ledger and fulfilled by email. 5. If a rail fails, /checkout/manual keeps the buyer from being stranded.
Creator Hub Wave Approval Case Study
Creator Hub Wave Approval Case Study. The Marketing Commander produces a campaign wave (draft posts across platforms). Items land in the Creator Hub board (app.aikagan.com/creator-hub or board.aikagan.com). Operator flow: review copy per item, click Approve to mark approved, Schedule to queue, then publish. Approved items route through Make.com omnichannel webhooks with UTM params already attached. Operating hypothesis (to be measured with UTM-attributed leads, not yet proven): waves with 5-7 items per platform and a single CTA outperform 1-item bursts. Approval gates keep quality at E2+ before publishing.
Progress Bus L0-L8 Definition
Progress Bus L0-L8. L0 Intake: lead captured (leak scan / outcome form). L1 Intent: intent scored and segmented. L2 Strategy: decision brief produced. L3 Build: assets generated (campaign waves, blueprints). L4 Test: Delivery/QA gate verifies quality score >= 4. L5 Deploy: fulfilled / published. L6 Revenue: income ledger records the transaction. L7 Governance: audit and release signoff. L8 Scale: affiliate and expansion loops. No item moves without the gate of the prior level passing.
Production Health Monitoring SOP
Production Health Monitoring SOP. GET /api/health returns ok:true only when core dependencies respond: KV store, checkout provider reachability, site origin, and env key presence. Cadence: verified after every deploy and on a daily check. SLAs: storefront HTTP 200, health 200 ok:true, zero runtime error clusters in the last 24h. On failure: fail-closed behavior, alert via configured webhook, and check deployment status before touching production.