aiConnected — Complete Document Inventory
Prepared: April 15, 2026Purpose: Full inventory of all documents, specifications, ideas, and innovations across all project conversations. Intended for transfer to a live developer repository and handoff to an engineering team. Status Key:
[WRITTEN] — Formally produced as a standalone file in a previous session[CONVERSATIONAL] — Exists in detail across chat sessions but not formatted as a standalone document[NEEDS WRITING] — Concept is defined; document has not been produced
SECTION 1: COMPANY & CORPORATE DOCUMENTS
1.1 Legal & Entity
| # | Document | Status | Notes |
|---|---|---|---|
| 1 | aiConnected LLC Operating Agreement (Georgia) | [WRITTEN] | Full draft produced with placeholder CTO/COO names; covers equity, compensation, IP assignment, vesting, governance, exit provisions |
| 2 | Schedule A — Capital Contributions | [WRITTEN] | Part of operating agreement |
| 3 | Schedule B — Ownership Units (10M unit structure) | [WRITTEN] | Bob 53%, CTO 10%, COO 10%, future CEO 12%, reserved pool 15% |
| 4 | Schedule C — Vesting Schedule Examples | [WRITTEN] | 4-year vest, 1-year cliff |
| 5 | Schedule D — Revenue Share Examples | [WRITTEN] | Revenue share formula examples at various MRR levels |
| 6 | CTO Joinder Agreement (template) | [NEEDS WRITING] | Addendum for Jacob Mandt when he accepts |
| 7 | COO Joinder Agreement (template) | [NEEDS WRITING] | Addendum for Bobbi Garvel when she accepts |
1.2 Strategy & Business Planning
| # | Document | Status | Notes |
|---|---|---|---|
| 8 | aiConnected Full Business Plan | [WRITTEN] | Comprehensive plan produced in operating agreement session; covers GTM, projections, market opportunity, team structure, unit economics |
| 9 | aiConnected For Agencies — Revenue Map | [WRITTEN] | Standalone document; covers $10K/year license, 30% salesperson commission, sales manager structure, break-even math |
| 10 | aiConnected Vision Document (Partner/Co-founder Pitch) | [WRITTEN] | Produced in “aiConnected’s vision for potential partners” session; covers cognitive OS thesis, product stack, Acquired Intelligence philosophy, robotics long-game |
| 11 | Revenue Projections (Year 1-3) | [CONVERSATIONAL] | Detailed in operating agreement and business plan sessions; 2.1M MRR Month 12, $27M ARR Year 1 targets |
| 12 | Investor Pitch Deck | [NEEDS WRITING] | Structure discussed in fundraising session; 10-15 slides defined but deck not produced |
| 13 | Executive Summary (1-page investor) | [NEEDS WRITING] | Referenced in Brain fundraising session |
| 14 | Fundraising Strategy Document | [CONVERSATIONAL] | Discussed in “Fundraising strategy for Brain by aiConnected” session; seed round mechanics, investor targeting, timing |
| 15 | Competitive Analysis — AI Memory (Mem0, OpenMemory, MemGPT, Zep) | [CONVERSATIONAL] | Detailed comparison produced in Mem0 and memory architecture sessions; needs standalone document |
| 16 | Competitive Analysis — Voice AI (Vapi, Retell, Bland) | [CONVERSATIONAL] | Discussed in voice infrastructure session |
| 17 | Competitive Analysis — Agency Platforms (GoHighLevel) | [CONVERSATIONAL] | Referenced across multiple sessions |
| 18 | Series A Readiness Checklist | [CONVERSATIONAL] | Referenced in operating agreement session; targets $10-15M MRR before raise |
SECTION 2: PHILOSOPHY & INTELLECTUAL PROPERTY
2.1 Acquired Intelligence Framework
| # | Document | Status | Notes |
|---|---|---|---|
| 19 | Acquired Intelligence: Reframing AGI Definition | [WRITTEN] | Exists as project file (Acquired_Intelligence__Reframing_AGI_Definition.md); covers AGI vs AGI nomenclature shift, anchor quote, specialization thesis |
| 20 | ANI (Acquired Network Intelligence) Definition | [CONVERSATIONAL] | Formally named in memory session; 2-hour sleep cycles, anonymized cross-instance learning; needs standalone spec |
| 21 | Scaling Hypothesis vs. Experience Hypothesis | [CONVERSATIONAL] | Developed during book Chapter 1 expansion; core theoretical argument |
2.2 The Book: “Acquired Intelligence”
| # | Document | Status | Notes |
|---|---|---|---|
| 22 | Book Outline (51 chapters, 11 parts) | [WRITTEN] | Exists as project file (_Acquired_Intelligence__Book_Outline.md); full structure from Parts I-XI plus Preface and Epilogue |
| 23 | Book Cover Design | [WRITTEN] | Produced by Bob; robotic hand reaching for apple; confirmed in book outline session |
| 24 | Parts I & II Draft (Chapters 1-8) | [WRITTEN] | Interview-based draft produced in book outline session; rough skeleton format |
| 25 | Chapter 1 — Expanded Draft | [WRITTEN] | Partial expansion started; process defined (challenges list → fact-check → educational expansion → subsections → 5,000-7,000 words) |
| 26 | Chapters 3-51 Full Expansions | [NEEDS WRITING] | Only Chapter 1 expansion begun; all remaining chapters need full treatment |
| 27 | Chapter 1 — Challenges List | [CONVERSATIONAL] | Produced in book session; itemized intellectual challenges to address |
| 28 | Chapter 1 — Fact-Check & Educational Expansion | [CONVERSATIONAL] | Covers: transformer architecture, RLHF, stochastic parrot debate, scaling hypothesis, emergent abilities, history of the term “artificial intelligence” |
SECTION 3: NEURIGRAPH / aiCONNECTED MEMORY ARCHITECTURE
3.1 Core Architecture
| # | Document | Status | Notes |
|---|---|---|---|
| 29 | Neurigraph Master Architecture Overview | [NEEDS WRITING] | Referenced repeatedly as the authoritative document; individual components specified but master doc not consolidated |
| 30 | Cognigraph Architecture — Original PRD (Sections 1-13) | [CONVERSATIONAL] | PRD was written section by section in early secure chat session; reached Section 13 before session ended; needs continuation and consolidation |
| 31 | Hyperthyme / Brain Technical Architecture Document (TAD) | [WRITTEN] | 3,564-line document produced in “Brain by aiConnected” session; covers all components, DB schema, APIs, storage, security, deployment |
| 32 | Hyperthyme Investor Overview | [WRITTEN] | 01-investor-overview.md — non-technical pitch for the memory system |
| 33 | Hyperthyme Junior Developer Guide | [WRITTEN] | 02-junior-developer-guide.md — plain-language explanation with analogies |
| 34 | Hyperthyme AI Community Technical Overview | [WRITTEN] | 03-ai-community-technical-overview.md — deep technical doc for AI practitioners |
| 35 | Brain by aiConnected — Product Summary (ClickUp) | [WRITTEN] | Two-paragraph summary produced in “Knowledge by aiConnected overview” session |
| 36 | Brain — Master Project Checklist (Recall → Launch) | [WRITTEN] | recall-project-master-checklist.md; 7-phase checklist from foundation to post-launch |
3.2 Architecture Components & Innovations
| # | Document | Status | Notes |
|---|---|---|---|
| 37 | Recall File Structure Specification | [WRITTEN] | Defined in TAD; covers folder structure, summary.md, keywords.txt, transcript.md, artifacts |
| 38 | Knowledge Graph Specification | [WRITTEN] | Defined in TAD; Category → Concept → Topic hierarchy, node types, edge relationships |
| 39 | RAG Database (Per-Node Vector Store) Specification | [WRITTEN] | Defined in TAD; pgvector implementation, embedding strategy |
| 40 | Defining Memories Specification | [WRITTEN] | Defined in TAD; always-warm index of decisions, milestones, turning points |
| 41 | Hot/Warm/Cold Storage Tiering Specification | [WRITTEN] | Defined in TAD; state transitions, compression, warming logic |
| 42 | Index Files Specification | [CONVERSATIONAL] | Innovation that reduces retrieval costs 90%+ and latency 75-88%; mentioned in cross-platform memory session; needs standalone spec |
| 43 | Z-Axis (Match Specificity) Architecture Specification | [WRITTEN] | brain-z-axis-specification.md; full specification of retrieval intent awareness (exact match to broad match); BM25 + vector hybrid |
| 44 | Object Deconstruction Graph (ODG) — Explainer | [WRITTEN] | Plain-language explanation produced in AI architecture session; covers what it is, how it works, why it matters, 10-layer depth, 4-level graph structure |
| 45 | Object Deconstruction Graph (ODG) — PRD | [NEEDS WRITING] | Identified at end of AI architecture session as next session; not yet written |
| 46 | Amygdala — Extended Function: Dynamic Heat Threshold Control | [WRITTEN] | Amygdala_Dynamic_Threshold_Function.md; standalone document produced at end of AI architecture session |
| 47 | Brain Region Registry (All Named Regions) | [CONVERSATIONAL] | Fully defined in AI architecture session: Cognigraph, ODG, Amygdala, Hippocampus, Prefrontal Cortex, Open Thinking Layer, Closed Thinking Layer, Long Term Memory; needs consolidated spec |
| 48 | Graph Search Model Specification | [CONVERSATIONAL] | Heat-based traversal (hot/warm/cold weighted edges, 0-1 probability scale), threshold logic; defined in AI architecture session |
| 49 | Sleep Cycle / ANI Specification | [CONVERSATIONAL] | 2-hour cycles, anonymized cross-instance learning, ODG activation during sleep; defined across multiple sessions |
| 50 | Quantum-Inspired Coherence Layer | [NEEDS WRITING] | Referenced in book outline and AI architecture session; 1,000 simultaneous hypothesis processing; no formal specification produced |
| 51 | Creativity Engine (Brain Region) | [NEEDS WRITING] | Mentioned at end of AI architecture session as next region to define; not yet specified |
| 52 | Coordinator / Priority Resolution Mechanism | [CONVERSATIONAL] | Pushback raised in AI architecture session; sequential processing model defined but debate ongoing; needs resolution and documentation |
3.3 Cross-Platform & Integration
| # | Document | Status | Notes |
|---|---|---|---|
| 53 | Cross-Platform Memory Transfer Pipeline (ChatGPT → aiConnected) | [CONVERSATIONAL] | 6-stage pipeline designed in cross-platform chat export session: Ingest → Parse → Structure → Map (Cognigraph hierarchy) → Deduplicate → Deploy; identified as potential killer feature |
| 54 | MCP Server Implementation Specification | [WRITTEN] | Defined in TAD and multiple sessions; tool schema, memory/search/retrieve endpoints |
| 55 | Mem0 Competitive Analysis & Differentiation | [WRITTEN] | Produced in Mem0 session; covers their $24M raise, 80K developers, AWS integration, and aiConnected differentiation strategy |
| 56 | OpenMemory Fork-and-Differentiate Analysis | [CONVERSATIONAL] | Discussed in memory system comparison session; Apache 2.0 fast-path vs. build-from-scratch; conclusion: viable fast path |
| 57 | aiConnected Memory API Design | [CONVERSATIONAL] | Discussed in API infrastructure session; POST /v1/memory/store, POST /v1/memory/search, POST /v1/context/synthesize, GET /v1/persona/{id}/state |
SECTION 4: VOICE INFRASTRUCTURE
4.1 Layer 1 — Shared Voice Infrastructure Platform
| # | Document | Status | Notes |
|---|---|---|---|
| 58 | Voice Infrastructure Platform Overview | [CONVERSATIONAL] | Defined in voice infrastructure session; Vapi/Retell competitor; STT → LLM → TTS → Telephony pipeline; LiveKit + Deepgram + ElevenLabs/Chatterbox + Twilio/Telnyx |
| 59 | Voice Infrastructure — Technical Architecture | [NEEDS WRITING] | Component specs discussed; no standalone TAD produced |
| 60 | Voice Infrastructure — Realistic Build Assessment | [CONVERSATIONAL] | Produced in voice session; recommends building on LiveKit rather than raw WebRTC; 6-week estimate for Voice by aiConnected |
4.2 aiConnected Voice (Layer 2)
| # | Document | Status | Notes |
|---|---|---|---|
| 61 | aiConnected Voice — Product Summary (ClickUp) | [WRITTEN] | Two-paragraph summary produced referencing Google Drive document; multi-tenant voice AI platform |
| 62 | aiConnected Voice — Product Overview Document | [WRITTEN] | Exists in Google Drive (fetched during session); covers GoToConnect → WebRTC bridge → LiveKit → Deepgram → Claude Sonnet → Chatterbox pipeline |
| 63 | aiConnected Voice — PRD | [WRITTEN] | No formal PRD produced; GoToConnect integration deprioritized; Vapi/Retell competitor model adopted |
4.3 aiConnected Dialer (Layer 3)
| # | Document | Status | Notes |
|---|---|---|---|
| 64 | aiConnected Dialer — Concept Definition | [CONVERSATIONAL] | Fully defined in voice infrastructure session; three phases: AI Power Dialer → Live Handoff → Real-Time Sales Intelligence |
| 65 | aiConnected Dialer — Feature Specification | [CONVERSATIONAL] | Covers pre-call batch enrichment (100-300 leads), 3-layer lead summaries, WebSocket live call streaming, split-screen command center, post-call automation, pricing ( 0.05/enriched lead) |
| 66 | aiConnected Dialer — PRD | [WRITTEN] | Concept complete; no PRD produced |
| 67 | PowerDial.ai — Original ChatGPT Concept Documents | [WRITTEN] | Two uploaded files reviewed in session: ChatGPT_Export_-_aiConnected___Dial.md and Original_ChatGPT_Export_-_aiConnected___Dial.md |
SECTION 5: AICO NNECTED BUSINESS CHAT (kbChat)
| # | Document | Status | Notes |
|---|---|---|---|
| 68 | kbChat Platform Specification v1.0 | [WRITTEN] | kbchat-platform-spec.md; full PRD covering 7-tier user hierarchy, 3 login routes, B2B2B model, authentication, theming system |
| 69 | kbChat Database Schema (Supabase / PostgreSQL with RLS) | [WRITTEN] | supabase/schema.sql; full schema produced in kbChat build session |
| 70 | kbChat UI/UX Design Specification | [WRITTEN] | UI-UX-DESIGN-SPEC.md; 29KB document produced in Paper/kbChat session |
| 71 | kbChat Developer PRD (Multi-Tenant Version) | [WRITTEN] | Comprehensive PRD produced in main chat.sec-admn.com session; covers architecture, 47-file manifest, all admin tabs, branding system |
| 72 | kbChat Theming System — 100+ Styling Options | [WRITTEN] | 93 configurable elements, 100+ styling options, light/dark modes, Google Fonts, color picker, custom CSS, 8 premade color themes, section-level control (Sidebar/Header/Chat Window/Input) |
| 73 | kbChat Tasks / Phased Build Checklist | [WRITTEN] | Tasks.md; 11-phase checklist, Phases 1-8 marked complete, Testing/Deployment in progress |
| 74 | kbChat Claude.md (Developer Context File) | [WRITTEN] | Claude.md; 9.5KB developer onboarding doc |
| 75 | kbChat README.md | [WRITTEN] | Setup, environment variables, deployment instructions |
| 76 | kbChat .env.example | [WRITTEN] | Environment variable template |
| 77 | kbChat Login Page UI — Three Portals | [WRITTEN] | platform-login.jsx; three-portal login (auth, admin, business); sec-admn.com domain; renaming from agency to “System Admin” documented |
| 78 | kbChat Industry Analysis (Target Markets) | [WRITTEN] | kbchat_industry_analysis.md; produced in secure chat session; breakdown by industry, willingness to pay, ROI framing |
| 79 | kbChat — Knowledge Base Generator Integration | [WRITTEN] | 9-step KB generation pipeline defined (crawl → extract → interview → research → review → deploy); embedded in platform spec |
SECTION 6: AICO NNECTED KNOWLEDGE
| # | Document | Status | Notes |
|---|---|---|---|
| 80 | aiConnected Knowledge — Product Summary (ClickUp) | [WRITTEN] | Two-paragraph summary produced in “Knowledge by aiConnected overview” session |
| 81 | aiConnected Knowledge — Sales Copy | [WRITTEN] | Exists as project file (AI_Knowledge_Base_Generator_Sales_Copy) |
| 82 | Knowledge Base Generator — Pipeline Specification | [CONVERSATIONAL] | 9-step pipeline: web crawl → entity extraction → service research → owner AI interview → concern mapping → conversation starters → system prompt generation; defined in multiple sessions |
| 83 | Knowledge Base Generator — Platform Compatibility List | [CONVERSATIONAL] | Vapi, Bland, Retell, Botpress, Voiceflow, OpenAI, Anthropic; webhook routing via Zapier/n8n |
| 84 | Knowledge Base Generator — Pricing Tiers | [CONVERSATIONAL] | 149-499/month subscription; BYOK model |
SECTION 7: AICO NNECTED CONTACT
| # | Document | Status | Notes |
|---|---|---|---|
| 85 | aiConnected Contact — Competitive Positioning Document | [WRITTEN] | Full conversation session “Contact by aiConnected competitive positioning”; covers existing solutions (Drift, Intercom, HubSpot Forms, etc.) and differentiation |
| 86 | aiConnected Contact — Product Architecture | [CONVERSATIONAL] | Form → AI analysis (under 500ms) → morphing chat interface → real-time lead alert → warm handoff; intent scoring, spam detection, calendar integration, Voice escalation |
| 87 | aiConnected Contact — Privacy Architecture (GDPR/CCPA) | [CONVERSATIONAL] | Explicit decision: no Brain/Memory integration for anonymous website visitors; consent boundary documented |
| 88 | aiConnected Contact — Product Summary (ClickUp) | [NEEDS WRITING] | Referenced in product summary session but not formally written |
| 89 | aiConnected Contact — PRD | [NEEDS WRITING] | Concept fully defined; no PRD produced |
SECTION 8: PAPER BY AICO NNECTED
| # | Document | Status | Notes |
|---|---|---|---|
| 90 | Paper by aiConnected — Developer PRD v2.1 | [WRITTEN] | DEVELOPER-PRD.md; 158KB; full technical PRD for thought leadership PDF platform; FastAPI/Next.js/WeasyPrint/Celery stack |
| 91 | Paper by aiConnected — UI/UX Design Spec | [WRITTEN] | UI-UX-DESIGN-SPEC.md; aiConnected colors and typography applied |
| 92 | Paper by aiConnected — Product Summary (ClickUp) | [WRITTEN] | Two-paragraph summary produced from GitHub repo read |
| 93 | Paper by aiConnected — Product Summary Document | [WRITTEN] | First product definition document from Oxford Pierpont session |
| 94 | Paper by aiConnected — Content Generation Pipeline | [WRITTEN] | 9-step pipeline defined in PRD: topic analysis → keyword research → web research (20-500 sources) → industry analysis → outline → content writing → statistics extraction → chart generation → PDF rendering |
| 95 | Paper by aiConnected — PDF Proof of Concept | [WRITTEN] | Working PDF generated using WeasyPrint in “Oxford Pierpont website research & Paper” session |
SECTION 9: LOGICLEGAL BY AICO NNECTED
| # | Document | Status | Notes |
|---|---|---|---|
| 96 | LogicLegal — Full Concept & Feature Definition | [WRITTEN] | Comprehensive session “LogicLegal - AI legal intake and case analysis tool”; covers all features, architecture, closed knowledge base, pricing |
| 97 | LogicLegal — Product Summary (ClickUp) | [WRITTEN] | Two-paragraph summary produced in “Knowledge by aiConnected overview” session |
| 98 | LogicLegal — Platform Architecture (LawLogic closed layer) | [CONVERSATIONAL] | Two-layer architecture: LawLogic (closed/air-gapped for legal Q&A) + Administrative Layer (internet-connected); compliance rationale documented |
| 99 | LogicLegal — Client Touchpoints Specification | [CONVERSATIONAL] | Three entry points: Perplexity-style research chat, corner chatbot, AI phone number |
| 100 | LogicLegal — Voice Assistant Specification | [CONVERSATIONAL] | Attorney call-in briefings; “Brief me on the Martinez case”; case prep before hearings |
| 101 | LogicLegal — Pricing Tiers | [CONVERSATIONAL] | Growth 2,500/month (15 topics), Complete $5,000/month (20 topics); closed knowledge base included at all tiers |
| 102 | LogicLegal — Competitive Analysis (LegalClerk.ai, Gideon, Smith.ai, Clio, GoHighLevel) | [CONVERSATIONAL] | Produced in initial LogicLegal session; distinguishes Clio (case management) from GoHighLevel (marketing/CRM) |
| 103 | LogicLegal — GoHighLevel vs. Clio Integration Strategy | [CONVERSATIONAL] | GoHighLevel as operational backbone, Clio as optional integration for case management |
| 104 | LogicLegal Version 1 Scope Document | [CONVERSATIONAL] | Phased feature list: Version 1 (research chat, corner chatbot, phone, basic dashboard, marketing engine), deferred to Version 2 (case briefings, smart dashboard, voice assistant) |
| 105 | LogicLegal — PRD | [NEEDS WRITING] | Full feature set defined; PRD was the stated next step at end of session |
SECTION 10: AICO NNECTED BUSINESS (AGENCY PLATFORM)
| # | Document | Status | Notes |
|---|---|---|---|
| 106 | aiConnected Business — Marketing Copy (“Connective Tissue”) | [WRITTEN] | Produced in “AI orchestration for enterprise workflows” session; reviewed and flagged as generic (doesn’t surface Cognigraph differentiators) |
| 107 | aiConnected Business — Product Stack Summary | [WRITTEN] | ”aiConnected’s vision for potential partners” session; 5-product integrated platform description |
| 108 | aiConnected Reputation Management — Concept Document | [WRITTEN] | aiConnected_Reputation_Management_Concept.md; features, compliance architecture, Yelp exclusion rationale, pricing decision, strategic value to Cognigraph |
| 109 | aiConnected Reputation Management — Features & Capabilities List | [WRITTEN] | Detailed feature list produced in follow-up in same session: review generation, negative feedback recovery, monitoring, response, analytics |
| 110 | aiConnected Business — Sales Cold Outreach Strategy | [CONVERSATIONAL] | Discussed in secure chat session; cold calling, emailing demo links, YouTube demos, community engagement; YouTube recommended as primary |
| 111 | aiConnected Business — Agency Break-Even Analysis | [CONVERSATIONAL] | Break-even at ~100 agencies; strong profitability at 300+; detailed in operating agreement business plan |
| 112 | aiConnected Business — Sales Team Scaling Plan | [CONVERSATIONAL] | Start 10 reps, promote from within, avoid upfront management overhead; 1099 contractor model; 30% commission |
SECTION 11: FUNNELCHAT
| # | Document | Status | Notes |
|---|---|---|---|
| 113 | funnelChat — Project Requirements Document | [WRITTEN] | Project-Requirements-Document.md; ~35,000 words; comprehensive PRD for AI debt collection / accounts receivable platform; FDCPA, TCPA, CFPB compliant |
| 114 | funnelChat — Original ChatGPT Concept Export | [WRITTEN] | Uploaded file funnelChat_by_aiConnected.md; 100 disruptive AI chatbot ideas + Stripe configuration |
| 115 | funnelChat — Competitive & Regulatory Review | [CONVERSATIONAL] | Produced in PRD session; regulatory concerns flagged (FDCPA, TCPA, asset-aware outreach ethics) |
SECTION 12: FLIPABATHROOM.COM (IGNORE)
| # | Document | Status | Notes |
|---|---|---|---|
| 116 | FlipABathroom.com — Business Proposal | [WRITTEN] | Uploaded file reviewed in service provider directory session; lead gen platform for bathroom remodeling contractors |
| 117 | FlipABathroom.com — Directory Build Plan (High Level) | [WRITTEN] | Phase 1-5 plan: foundation setup, data collection, quality, enrichment, deployment |
| 118 | FlipABathroom.com — 1,200 City Dataset | [WRITTEN] | Complete CSV; 100 cities × 12 SE states; Census ACS 2023 5-Year Estimates; 100% spot-check verified |
| 119 | FlipABathroom.com — Census Data Verification Report | [WRITTEN] | Comprehensive audit produced in directory session; methodology, source citations, quality certification |
| 120 | FlipABathroom.com — Revenue Model | [CONVERSATIONAL] | 125/bid (up to 10 bids per job = 49.97/month contractor membership; $576K/year conservative from leads alone |
| 121 | FlipABathroom.com — Google Places API Data Collection Script | [WRITTEN] | Python script produced in session; collects 10 contractors per city across 1,200 cities |
SECTION 13: AI SERVICES BUSINESS DIRECTORY
| # | Document | Status | Notes |
|---|---|---|---|
| 122 | AI Services Business Directory — PRD | [WRITTEN] | ai-directory-prd.md; uploaded file reviewed in session; 50,000 businesses, 50 states × 100 cities × 10 businesses, n8n orchestration, Apollo.io primary source |
| 123 | AI Services Business Directory — n8n Workflow Architecture | [WRITTEN] | 4 workflows: orchestrator, worker, validation, update; documented in PRD |
| 124 | AI Services Business Directory — Database Schema | [WRITTEN] | 4 tables: states, cities, businesses, update_log; defined in PRD |
| 125 | AI Services Business Directory — Cost Estimate | [WRITTEN] | ~ 468/year maintenance; Apollo.io as primary data source |
SECTION 14: GLOBAL AI MARKETPLACE
| # | Document | Status | Notes |
|---|---|---|---|
| 126 | Global AI Marketplace — Feasibility Research Report | [WRITTEN] | Comprehensive research produced in “Global AI marketplace for developers” session; technical feasibility, market demand, competitive landscape, regulatory issues, monetization models |
| 127 | Global AI Marketplace — Investment Range | [CONVERSATIONAL] | $25-55M investment range assessed; 2025-2026 launch window identified as viable |
SECTION 15: AUTHAPI.NET (IGNORE)
| # | Document | Status | Notes |
|---|---|---|---|
| 128 | authAPI.net — Developer Contact Form HTML Email Template | [WRITTEN] | authapi-contact-email.html; dark-mode professional email template produced for JetFormBuilder integration |
| 129 | authAPI.net — Platform Concept | [CONVERSATIONAL] | Developer-facing API service; named in product suite; full spec not produced |
SECTION 16: ROBOTICS & LONG-TERM VISION (IGNORE)
| # | Document | Status | Notes |
|---|---|---|---|
| 130 | Robotics Cognitive OS — Strategic Vision | [CONVERSATIONAL] | Detailed in operating agreement session and vision document; aiConnected as cognitive layer for humanoid robotics; Tesla Optimus scenario ( 1.2B/year) |
| 131 | Robotics Product Stack Architecture | [CONVERSATIONAL] | Defined in API infrastructure session: Brain + Knowledge + Voice + Chat + Persona + Vision (future) + Motor Control (future) |
| 132 | Vision Module — Concept | [CONVERSATIONAL] | Future brain region for robotics visual processing; named but not specified |
| 133 | Motor Control Module — Concept | [CONVERSATIONAL] | Future brain region for physical action; named but not specified |
| 134 | Acquisition Scenario Analysis (Tesla, Apple, Google, Amazon, Microsoft) | [CONVERSATIONAL] | Produced in operating agreement session; $50-150B acquisition scenarios; 2030+ timeframe |
SECTION 17: DESIGN & BRAND ASSETS
| # | Document | Status | Notes |
|---|---|---|---|
| 135 | aiConnected Style Guide | [WRITTEN] | Exists as project file (aiConnectedStyleGuide.pdf) |
| 136 | aiConnected Logo Suite | [WRITTEN] | 11 logo variants in project files: horizontal dark/light, vertical dark/light, text-only dark/light/gray, powered-by dark/light, profile picture, favicon |
| 137 | aiConnected Favicon | [WRITTEN] | favicon_ico.png in project files |
| 138 | GoToConnect Postman Collection | [WRITTEN] | GoToConnect_postman_collection.json in project files; from GoToConnect integration work (now deprioritized) |
SECTION 18: DOCUMENTS DISCUSSED BUT NOT YET FORMALLY SCOPED
| # | Document | Status | Notes | |
|---|---|---|---|---|
| 139 | aiConnected OS — Cognitive Operating System Specification | [NEEDS WRITING] | Long-term vision document; the OS layer that all products feed into | |
| 140 | Persona Layer Specification | [NEEDS WRITING] | Referenced in robotics stack; defines consistent AI identity, personality, behavior | |
| 141 | aiConnected API Platform — Full Specification | [NEEDS WRITING] | Dual-layer model (platform + API); discussed in API infrastructure session | |
| 142 | aiConnected Dialer — Pre-Call Enrichment Engine Specification | [NEEDS WRITING] | 3-layer lead summary system defined in concept; needs formal spec | |
| 143 | Privacy Policy (Platform-Wide) | [NEEDS WRITING] | Referenced in Brain checklist; GDPR/CCPA compliant | |
| 144 | Terms of Service (Platform-Wide) | [NEEDS WRITING] | Referenced in Brain checklist | |
| 145 | Data Processing Agreement (DPA) | [NEEDS WRITING] | Referenced in Brain checklist; for enterprise customers | |
| 146 | Security Whitepaper | [WRITTEN] | Referenced in Brain checklist | |
| 147 | aiConnected Knowledge — Full PRD | [NEEDS WRITING] | Product fully operational but no standalone PRD | |
| 148 | funnelChat — Secure Chat Build (kbChat for Debt Collection) | [CONVERSATIONAL] | Referenced in early secure chat session; may be a vertical deployment of kbChat |
SECTION 19: FORMALLY PRODUCED STANDALONE FILES (REFERENCE LIST)
This is a consolidated list of every file that was formally written and presented as a download during project sessions, regardless of section. Engineers should locate these in session outputs.| File | Session Origin |
|---|---|
aiConnected_Operating_Agreement_GA_LLC.md | Operating agreement session |
aiConnected_For_Agencies_Revenue_Map.md | Reputation management session |
aiConnected_Reputation_Management_Concept.md | Reputation management session |
brain-z-axis-specification.md | Three-dimensional memory session |
Amygdala_Dynamic_Threshold_Function.md | AI architecture session |
kbchat-platform-spec.md | kbChat original spec session |
hyperthyme-technical-architecture-document.md | Brain by aiConnected session |
01-investor-overview.md (Hyperthyme) | Brain by aiConnected session |
02-junior-developer-guide.md (Hyperthyme) | Brain by aiConnected session |
03-ai-community-technical-overview.md (Hyperthyme) | Brain by aiConnected session |
recall-project-master-checklist.md | Brain by aiConnected session |
Project-Requirements-Document.md (funnelChat) | funnelChat PRD session |
DEVELOPER-PRD.md (Paper by aiConnected) | Oxford Pierpont / Paper session |
UI-UX-DESIGN-SPEC.md (Paper by aiConnected) | Oxford Pierpont / Paper session |
authapi-contact-email.html | authAPI.net HTML email session |
kbchat_industry_analysis.md | Secure chat build session |
Acquired_Intelligence_Draft_Parts_I_II.md | Book outline session |
FlipABathroom_census_dataset.csv (1,200 cities) | Service provider directory session |
aiConnected_business_plan.md (within operating agreement) | Operating agreement session |
REPOSITORY STRUCTURE (Mintlify / Fumadocs Format)
The following is how all documentation should be organized in the live developer documentation repository.DOCUMENT COUNT SUMMARY
| Category | Written | Conversational | Needs Writing | Total |
|---|---|---|---|---|
| Company & Corporate | 9 | 9 | 7 | 25 |
| Philosophy & IP (incl. Book) | 5 | 3 | 26 | 34 |
| Neurigraph / Memory Architecture | 20 | 14 | 7 | 41 |
| Voice Infrastructure | 3 | 5 | 3 | 11 |
| aiConnected Business Chat | 12 | 1 | 0 | 13 |
| aiConnected Knowledge | 2 | 3 | 1 | 6 |
| aiConnected Contact | 1 | 3 | 2 | 6 |
| Paper by aiConnected | 5 | 0 | 0 | 5 |
| LogicLegal | 2 | 5 | 1 | 8 |
| aiConnected Business (Agency) | 3 | 4 | 0 | 7 |
| funnelChat | 2 | 1 | 0 | 3 |
| FlipABathroom | 4 | 1 | 0 | 5 |
| AI Services Directory | 3 | 0 | 0 | 3 |
| Global AI Marketplace | 1 | 1 | 0 | 2 |
| authAPI.net | 1 | 1 | 1 | 3 |
| Robotics Vision | 0 | 3 | 3 | 6 |
| Legal & Compliance | 0 | 0 | 4 | 4 |
| Design & Brand Assets | 12 | 0 | 0 | 12 |
| TOTALS | 85 | 54 | 55 | 194 |
PRIORITY WRITING QUEUE
The following documents are highest priority for the engineering handoff because they are either blockers for development or represent significant unprotected IP. Tier 1 — Critical (Write First):- Neurigraph Master Architecture Overview (consolidates all brain region specs)
- Brain Region Registry (canonical list of all regions and their functions)
- Object Deconstruction Graph (ODG) — PRD
- Quantum-Inspired Coherence Layer — Specification
- aiConnected Memory — Full PRD
- Voice Infrastructure — Technical Architecture Document
- aiConnected Voice — PRD
- aiConnected Dialer — PRD
- LogicLegal — PRD
- aiConnected Contact — PRD