{
  "metadata": {
    "name": "Darthom Intlligence Developer Knowledge Database",
    "base_url": "https://darthom-intel.netlify.app",
    "description": "Queryable static knowledge database for website architecture, landing pages, AI-assisted web development, Netlify deployment, local brain routing, content operations, accessibility, performance, SEO, and proof-first web systems.",
    "mode": "static local retrieval and indexed synthesis; no external LLM call required",
    "chunk_count": 27,
    "all_site_chunk_count": 251,
    "brains": 8,
    "updated": "2026-05-22"
  },
  "query_surfaces": [
    {
      "label": "Brain Room",
      "url": "/brain/",
      "purpose": "general operator brain switching and local knowledge chat"
    },
    {
      "label": "Dev Brain Database",
      "url": "/dev-brain/",
      "purpose": "developer/web architecture focused knowledge chat"
    },
    {
      "label": "Knowledge Browser",
      "url": "/knowledge/",
      "purpose": "browse all indexed knowledge chunks"
    },
    {
      "label": "AI site map",
      "url": "/AI-SITEMAP.md",
      "purpose": "machine-readable site routes, content, and usage guide"
    }
  ],
  "chunks": [
    {
      "id": "dev-knowledge-db-01",
      "title": "Website operating model vs landing page funnel",
      "owner": "Skyes Over London / Gray Skyes",
      "summary": "A website carries the operating model of the company; a landing page compresses one offer into one conversion path.",
      "questions": [
        "What is the difference between a real website and a landing page?",
        "When is a landing page enough?",
        "What should a company website know?"
      ],
      "keywords": [
        "operating model",
        "conversion path",
        "visitor questions",
        "proof routes",
        "website",
        "landing page",
        "ai web development",
        "interactive database",
        "knowledge base",
        "site architecture",
        "developer brain"
      ]
    },
    {
      "id": "dev-knowledge-db-02",
      "title": "Information architecture as a data model",
      "owner": "Darius Hartwell",
      "summary": "Information architecture is a data model for public understanding: questions, entities, pages, tags, evidence, owners, and actions.",
      "questions": [
        "How should a website be structured as a database?",
        "What is information architecture?",
        "How do tags and pages help search?"
      ],
      "keywords": [
        "information architecture",
        "taxonomy",
        "entities",
        "semantic search",
        "website",
        "landing page",
        "ai web development",
        "interactive database",
        "knowledge base",
        "site architecture",
        "developer brain"
      ]
    },
    {
      "id": "dev-knowledge-db-03",
      "title": "AI-generated pages require human architecture review",
      "owner": "Talia Monroe",
      "summary": "AI can draft interface copy and code, but a human operator has to review workflow logic, source quality, risk, and user intent.",
      "questions": [
        "How should AI be used in web development?",
        "Can AI replace product thinking?",
        "How do we review AI generated pages?"
      ],
      "keywords": [
        "ai drafting",
        "human review",
        "workflow logic",
        "model output",
        "website",
        "landing page",
        "ai web development",
        "interactive database",
        "knowledge base",
        "site architecture",
        "developer brain"
      ]
    },
    {
      "id": "dev-knowledge-db-04",
      "title": "Component architecture for sites that need to grow",
      "owner": "Roman Ellis",
      "summary": "A serious website needs reusable components, routes, data files, content patterns, and predictable styling so it can expand without breaking.",
      "questions": [
        "How should a static Netlify site be built?",
        "What makes a website maintainable?",
        "Why do components matter?"
      ],
      "keywords": [
        "component architecture",
        "routes",
        "static site",
        "maintainability",
        "website",
        "landing page",
        "ai web development",
        "interactive database",
        "knowledge base",
        "site architecture",
        "developer brain"
      ]
    },
    {
      "id": "dev-knowledge-db-05",
      "title": "Content operations are part of engineering",
      "owner": "Nyla Voss",
      "summary": "Longform content, FAQs, sources, tags, and author profiles become operational data when they are structured and queryable.",
      "questions": [
        "How should blogs become a knowledge base?",
        "Why does content need metadata?",
        "How do we make articles queryable?"
      ],
      "keywords": [
        "content operations",
        "metadata",
        "author profiles",
        "queryable content",
        "website",
        "landing page",
        "ai web development",
        "interactive database",
        "knowledge base",
        "site architecture",
        "developer brain"
      ]
    },
    {
      "id": "dev-knowledge-db-06",
      "title": "Deployment hygiene for Netlify drops",
      "owner": "Kendrick Vale",
      "summary": "Drop-ready means the root is flat, the paths resolve, scripts parse, assets load, redirects work, and there is a repeatable verification check.",
      "questions": [
        "What makes a Netlify ZIP drop-ready?",
        "Why do static sites 404 on Netlify?",
        "How do we test a deployment package?"
      ],
      "keywords": [
        "netlify",
        "deployment",
        "qa",
        "root zip",
        "website",
        "landing page",
        "ai web development",
        "interactive database",
        "knowledge base",
        "site architecture",
        "developer brain"
      ]
    },
    {
      "id": "dev-knowledge-db-07",
      "title": "Product surfaces must answer buyer objections",
      "owner": "Amara Stone",
      "summary": "A website becomes a product surface when it shows what the buyer can do, learn, compare, trust, and request without needing a call first.",
      "questions": [
        "How does a website support product strategy?",
        "What should a service website prove?",
        "How do pages answer buyer objections?"
      ],
      "keywords": [
        "product surface",
        "buyer objections",
        "offer clarity",
        "proof artifact",
        "website",
        "landing page",
        "ai web development",
        "interactive database",
        "knowledge base",
        "site architecture",
        "developer brain"
      ]
    },
    {
      "id": "dev-knowledge-db-08",
      "title": "Commercial trust signals without fake hype",
      "owner": "Jalen Cross",
      "summary": "The site should make a buyer feel that serious operators are behind the screen by showing proof, process, specificity, and clear boundaries.",
      "questions": [
        "How does a website build trust?",
        "Why do buyers feel the difference between real sites and pitch pages?",
        "What makes AI claims credible?"
      ],
      "keywords": [
        "trust signals",
        "technical sales",
        "buyer confidence",
        "proof",
        "website",
        "landing page",
        "ai web development",
        "interactive database",
        "knowledge base",
        "site architecture",
        "developer brain"
      ]
    },
    {
      "id": "dev-knowledge-db-09",
      "title": "Interactive database as a public knowledge surface",
      "owner": "Skyes Over London / Gray Skyes",
      "summary": "The Brain Room should feel like a queryable intelligence desk, not a gimmick: the user asks, the system retrieves, the operator explains, and the sources remain visible.",
      "questions": [
        "Is the Brain Room like ChatGPT?",
        "How does local brain chat work?",
        "Can users query the knowledge base?"
      ],
      "keywords": [
        "interactive database",
        "brain room",
        "local retrieval",
        "chat surface",
        "website",
        "landing page",
        "ai web development",
        "interactive database",
        "knowledge base",
        "site architecture",
        "developer brain"
      ]
    },
    {
      "id": "dev-knowledge-db-10",
      "title": "Developer knowledge retrieval should privilege architecture terms",
      "owner": "Darius Hartwell",
      "summary": "A developer brain needs weighted retrieval around architecture, routes, state, content, accessibility, performance, source quality, and maintenance.",
      "questions": [
        "How should a local knowledge index work?",
        "How do query terms map to site knowledge?",
        "How do we avoid generic answers?"
      ],
      "keywords": [
        "weighted retrieval",
        "developer knowledge",
        "terms",
        "search index",
        "website",
        "landing page",
        "ai web development",
        "interactive database",
        "knowledge base",
        "site architecture",
        "developer brain"
      ]
    },
    {
      "id": "dev-knowledge-db-11",
      "title": "UI states separate real apps from page mockups",
      "owner": "Roman Ellis",
      "summary": "A site that includes interactive databases, forms, chats, filters, and knowledge browsers needs empty states, loading states, error states, and recovery paths.",
      "questions": [
        "What UI states should a real website have?",
        "How do interactive pages fail gracefully?",
        "Why do demos break after launch?"
      ],
      "keywords": [
        "ui states",
        "loading",
        "empty state",
        "error handling",
        "frontend",
        "website",
        "landing page",
        "ai web development",
        "interactive database",
        "knowledge base",
        "site architecture",
        "developer brain"
      ]
    },
    {
      "id": "dev-knowledge-db-12",
      "title": "AI chat without a backend must be honest",
      "owner": "Talia Monroe",
      "summary": "A static local brain can retrieve and synthesize from site data, but it should not pretend to be a full generative model with memory and external reasoning.",
      "questions": [
        "Is this really AI?",
        "Can a static site act like ChatGPT?",
        "When do we need a backend LLM?"
      ],
      "keywords": [
        "static chat",
        "local mode",
        "llm upgrade",
        "backend honesty",
        "website",
        "landing page",
        "ai web development",
        "interactive database",
        "knowledge base",
        "site architecture",
        "developer brain"
      ]
    },
    {
      "id": "dev-knowledge-db-13",
      "title": "Accessibility is architecture, not polish",
      "owner": "Kendrick Vale",
      "summary": "Accessibility belongs in the architecture because navigation, headings, form labels, contrast, focus, and semantics determine who can use the site.",
      "questions": [
        "How do we make the site accessible?",
        "Why is accessibility part of engineering?",
        "What should we test before launch?"
      ],
      "keywords": [
        "accessibility",
        "semantics",
        "keyboard",
        "focus states",
        "website",
        "landing page",
        "ai web development",
        "interactive database",
        "knowledge base",
        "site architecture",
        "developer brain"
      ]
    },
    {
      "id": "dev-knowledge-db-14",
      "title": "Performance is a trust signal",
      "owner": "Kendrick Vale",
      "summary": "Heavy pages, blocking scripts, unoptimized media, and layout shift make a company feel careless even when the visuals are strong.",
      "questions": [
        "Why does page speed matter?",
        "How do motion backgrounds affect trust?",
        "What performance checks matter?"
      ],
      "keywords": [
        "performance",
        "core web vitals",
        "media",
        "caching",
        "website",
        "landing page",
        "ai web development",
        "interactive database",
        "knowledge base",
        "site architecture",
        "developer brain"
      ]
    },
    {
      "id": "dev-knowledge-db-15",
      "title": "A full website should contain multiple decision paths",
      "owner": "Amara Stone",
      "summary": "Different visitors need different paths: proof, services, process, team, research, FAQs, chat, contact, and downloadable assets.",
      "questions": [
        "What pages should a real company website have?",
        "How do visitor paths work?",
        "Why is one CTA not enough?"
      ],
      "keywords": [
        "decision paths",
        "visitor journey",
        "faq",
        "downloads",
        "website",
        "landing page",
        "ai web development",
        "interactive database",
        "knowledge base",
        "site architecture",
        "developer brain"
      ]
    },
    {
      "id": "dev-knowledge-db-16",
      "title": "Proof artifacts make service claims testable",
      "owner": "Jalen Cross",
      "summary": "A web page should connect claims to artifacts: dashboards, portals, briefs, reports, automations, QA logs, case-style examples, or working interfaces.",
      "questions": [
        "How do we prove AI development claims?",
        "What should a service site show?",
        "How do buyers evaluate proof?"
      ],
      "keywords": [
        "proof artifacts",
        "claims",
        "sales enablement",
        "outcomes",
        "website",
        "landing page",
        "ai web development",
        "interactive database",
        "knowledge base",
        "site architecture",
        "developer brain"
      ]
    },
    {
      "id": "dev-knowledge-db-17",
      "title": "FAQs are a retrieval system",
      "owner": "Nyla Voss",
      "summary": "FAQs are not filler content. They are structured answers to actual objections, evaluation questions, risk concerns, and buyer language.",
      "questions": [
        "How do FAQs help a website?",
        "Why are visitor questions important?",
        "How should FAQs be organized?"
      ],
      "keywords": [
        "faq",
        "question database",
        "buyer intent",
        "retrieval",
        "website",
        "landing page",
        "ai web development",
        "interactive database",
        "knowledge base",
        "site architecture",
        "developer brain"
      ]
    },
    {
      "id": "dev-knowledge-db-18",
      "title": "A knowledge base needs source discipline",
      "owner": "Darius Hartwell",
      "summary": "A knowledge base is only useful if its chunks have owners, source IDs, freshness notes, and clear routing logic.",
      "questions": [
        "How should a knowledge base be chunked?",
        "What metadata should knowledge chunks have?",
        "How do we keep sources valid?"
      ],
      "keywords": [
        "source discipline",
        "freshness",
        "chunk owner",
        "routing",
        "website",
        "landing page",
        "ai web development",
        "interactive database",
        "knowledge base",
        "site architecture",
        "developer brain"
      ]
    },
    {
      "id": "dev-knowledge-db-19",
      "title": "Generated content still needs editorial personality",
      "owner": "Nyla Voss",
      "summary": "AI-assisted content becomes forgettable when every article sounds like a neutral brand voice with no operator perspective.",
      "questions": [
        "How do we make AI assisted blogs sound human?",
        "Why do authors need profiles?",
        "How do specialist voices help trust?"
      ],
      "keywords": [
        "editorial personality",
        "author voice",
        "specialist writing",
        "human prose",
        "website",
        "landing page",
        "ai web development",
        "interactive database",
        "knowledge base",
        "site architecture",
        "developer brain"
      ]
    },
    {
      "id": "dev-knowledge-db-20",
      "title": "Client portals are websites with operating memory",
      "owner": "Roman Ellis",
      "summary": "A portal differs from a brochure because it can remember users, expose status, route documents, show dashboards, and support repeated actions.",
      "questions": [
        "When does a website need a portal?",
        "What is a client portal?",
        "How do public and private surfaces differ?"
      ],
      "keywords": [
        "client portal",
        "auth",
        "private workflow",
        "status",
        "website",
        "landing page",
        "ai web development",
        "interactive database",
        "knowledge base",
        "site architecture",
        "developer brain"
      ]
    },
    {
      "id": "dev-knowledge-db-21",
      "title": "AI-era SEO depends on answer quality and structure",
      "owner": "Darius Hartwell",
      "summary": "Search and AI retrieval both need clear pages, helpful answers, structured topics, source-aware language, and content that adds value beyond generic summaries.",
      "questions": [
        "What should AI crawlers understand about the site?",
        "Why add llms.txt?",
        "How do we make content useful for AI search?"
      ],
      "keywords": [
        "seo",
        "ai search",
        "llms.txt",
        "structured content",
        "website",
        "landing page",
        "ai web development",
        "interactive database",
        "knowledge base",
        "site architecture",
        "developer brain"
      ]
    },
    {
      "id": "dev-knowledge-db-22",
      "title": "Lead capture should respect user context",
      "owner": "Jalen Cross",
      "summary": "A serious contact path gives visitors enough context to explain what they need without turning the form into a trap.",
      "questions": [
        "What should a contact form ask?",
        "How do we qualify leads?",
        "How should site inquiries route?"
      ],
      "keywords": [
        "lead capture",
        "contact form",
        "qualification",
        "routing",
        "website",
        "landing page",
        "ai web development",
        "interactive database",
        "knowledge base",
        "site architecture",
        "developer brain"
      ]
    },
    {
      "id": "dev-knowledge-db-23",
      "title": "Motion backgrounds must not overpower the system",
      "owner": "Amara Stone",
      "summary": "Cinematic motion can support brand feeling, but it must sit behind readability, navigation, interaction, and performance.",
      "questions": [
        "How do we use video backgrounds without ruining usability?",
        "Should cards be transparent?",
        "How much motion is too much?"
      ],
      "keywords": [
        "motion background",
        "readability",
        "brand system",
        "ux",
        "website",
        "landing page",
        "ai web development",
        "interactive database",
        "knowledge base",
        "site architecture",
        "developer brain"
      ]
    },
    {
      "id": "dev-knowledge-db-24",
      "title": "Security boundaries for public knowledge chat",
      "owner": "Kendrick Vale",
      "summary": "A public local brain should never expose private client data, secrets, credentials, hidden operations, or unreviewed internal records.",
      "questions": [
        "What data can live in a static knowledge base?",
        "Is local chat secure?",
        "What should not go into public JSON?"
      ],
      "keywords": [
        "public chat",
        "secrets",
        "client side data",
        "security boundary",
        "website",
        "landing page",
        "ai web development",
        "interactive database",
        "knowledge base",
        "site architecture",
        "developer brain"
      ]
    },
    {
      "id": "dev-knowledge-db-25",
      "title": "Admin orchestration is a routing pattern",
      "owner": "Skyes Over London / Gray Skyes",
      "summary": "Gray as admin means the site can answer broad questions by routing across specialists instead of pretending one brain owns every domain.",
      "questions": [
        "How should Gray orchestrate the brains?",
        "Who owns a cross-domain question?",
        "How does the Brain Room route work?"
      ],
      "keywords": [
        "admin orchestrator",
        "routing pattern",
        "specialist brains",
        "gray",
        "website",
        "landing page",
        "ai web development",
        "interactive database",
        "knowledge base",
        "site architecture",
        "developer brain"
      ]
    },
    {
      "id": "dev-knowledge-db-26",
      "title": "Static now, backend later",
      "owner": "Talia Monroe",
      "summary": "A static Brain Room can be valuable immediately, but the upgrade path should be explicit: API function, embeddings, vector store, conversation logs, auth, and admin ingestion.",
      "questions": [
        "What is the next step after local chat?",
        "How do we turn this into a real AI backend?",
        "What does RAG need?"
      ],
      "keywords": [
        "rag",
        "vector store",
        "netlify functions",
        "upgrade path",
        "website",
        "landing page",
        "ai web development",
        "interactive database",
        "knowledge base",
        "site architecture",
        "developer brain"
      ]
    },
    {
      "id": "dev-knowledge-db-27",
      "title": "Maintenance is part of the product",
      "owner": "Roman Ellis",
      "summary": "A website with blogs, brains, knowledge files, motion layers, and data indexes needs a maintenance rhythm, not just a launch date.",
      "questions": [
        "How do we maintain this website?",
        "What should be checked after changing knowledge files?",
        "How do we avoid breaking Netlify deploys?"
      ],
      "keywords": [
        "maintenance",
        "documentation",
        "qa script",
        "content updates",
        "website",
        "landing page",
        "ai web development",
        "interactive database",
        "knowledge base",
        "site architecture",
        "developer brain"
      ]
    }
  ]
}