--- id: 20260731_152513_clerk-counci title: COUNCIL - CLERK - Council FAQ KB seed category: Work predicted_narrative_arc: Initiation sentiment: Neutral emotions: - purposeful - neutral keypoints: - First content deposit into Council instance - Designed for interactive querying not browsing - Includes category stage and tags metadata - Answers must be live-verifiable - Placeholder fields for 01_PILE to 07_CODEX schema summary: This deposit introduces the first content for a Council FAQ knowledge base seed, intended for direct querying via Council Asker rather than static browsing. It includes placeholder metadata blocks for schema mapping and stresses that answers must be verifiable through live system queries. tags: - clerk - council-faq - kb-seed - interactive-query - metadata-mapping sycophancy: 0 truth_score: 7 entropy: 2 sample: false consent: own_laptop agent: council source_session: 20260731_144239_8215a8 created: '2026-07-31T22:25:13Z' updated: '2026-07-31T22:34:36Z' vault_stage: 07_CODEX headwaters: COUNCIL prefix: COUNCIL enrich_status: ok enrich_blockers: [] enrich_method: llm pipeline_filename: COUNCIL_2026-07-31_clerk-council-faq-kb-seed.md source_kind: chat proposed_topic: Work lane: Work voice: clerk active_voice: clerk voices: - clerk routing_source: carbon corpus_topic: Work --- # Conversation transcript _Agent: council_ ## You Here's another deposit ### Attached: council-faq-kb-seed.md # Council FAQ — KB Seed Set **Purpose:** This is the first content deposited into a Council instance. It is meant to be asked, not browsed — load it in, then let prospects query it directly through Council Asker rather than reading it as a static page. Every answer below should be verifiable by asking Council the same question live. **Note on format:** each entry has a light metadata block (category, stage, tags) so it maps into your existing Codex enrichment schema. Field names below are placeholders — swap them for your actual `01_PILE`–`07_CODEX` schema fields before ingestion. --- ## Stage 1 — Skepticism Gate ```yaml category: trust stage: 1_skepticism_gate tags: [ai-distrust, accuracy, product-basics] ``` **Q: Is this just another AI chatbot?** No. General chat tools reason from everything they were trained on across the open internet. Council doesn't do that. It only answers from what a business has actually deposited into its own knowledge base. If something isn't in there, it says so — it doesn't fill the gap with a plausible-sounding guess. --- ```yaml category: trust stage: 1_skepticism_gate tags: [data-security, privacy] ``` **Q: Where does my information go when I use this?** That's your choice, not ours. Council runs either against a cloud model with your own API key, or entirely locally on your own machine with no cloud key at all — nothing leaves your computer unless you choose the cloud option. Either way, nothing you ask, and nothing you've deposited, gets pooled with anyone else's data or used to train a general-purpose model. It's a single-enterprise knowledge base, not a shared one — and with the local option, it's not even a networked one. --- ```yaml category: trust stage: 1_skepticism_gate tags: [hallucination, accuracy, honesty] ``` **Q: How do I know you're not just making things up?** Because the honest answer is available and used: "that's not something I have information on yet." Council is built to prefer that answer over a confident-sounding guess. If you ask something outside what's in the knowledge base, that's what you'll get — not an invented one. --- ## Stage 2 — How This Differs ```yaml category: differentiation stage: 2_how_it_differs tags: [comparison, chatgpt, gemini] ``` **Q: How is this different from just typing my question into ChatGPT or Gemini?** Those tools average an answer across the entire internet — useful for general knowledge, useless for anything specific to one business, and impossible to hold accountable to a single source of truth. Council draws from exactly one place: what this business has actually put in. The answer isn't a blend. It's traceable to something real. --- ```yaml category: differentiation stage: 2_how_it_differs tags: [ask-vs-browse, product-mechanics] ``` **Q: What does "ask, don't browse" actually mean in practice?** Instead of digging through a website, an FAQ page, or a PDF looking for the answer, you just ask your actual question, in your own words, and get answered directly — not routed to a page that might or might not cover it. --- ```yaml category: differentiation stage: 2_how_it_differs tags: [website, positioning] ``` **Q: Does this replace my website?** No — it sits alongside it as the layer that answers the specific question someone actually has, instead of asking them to find it themselves. The website is where you present yourself. Council is where someone gets a direct answer. --- ## Stage 3 — Fit for My Business ```yaml category: fit stage: 3_fit_for_my_business tags: [small-business, non-technical] ``` **Q: My business isn't especially high-tech — is this still for me?** Most owners are already testing general AI tools and hitting the same wall: they don't fully trust the answers without checking them. That's exactly the gap this closes. You don't need to become a tech company. You need to put what you already know — the stuff you currently explain over the phone, in person, or by email, over and over — into one place once. --- ```yaml category: fit stage: 3_fit_for_my_business tags: [use-case, ideal-customer] ``` **Q: What kind of business does this actually fit?** Small enterprises — under 50 people — that are trying to grow and already have real expertise, just not in a form anyone else can get at yet. That might be a single book you wrote. It might be a folder of half-finished notes and drafts that never quite came together into something you'd hand a new hire on day one. Either way, if you find yourself explaining the same three or four things to every new customer or client, that's the exact gap this is built to close. You don't need a clean, organized case for what you know going in — you need what you already have, however mangled, and Council does the organizing. --- ```yaml category: fit stage: 3_fit_for_my_business tags: [pricing, setup, PLACEHOLDER] ``` **Q: What does it cost, and how long does it take to set up?** *[Placeholder — needs your actual numbers before this goes live. Draft structure: cost model, typical time from first conversation to a working instance, what's required from the business owner vs. what's handled for them.]* --- ## Stage 4 — Try Before You Trust ```yaml category: conversion stage: 4_try_before_trust tags: [demo, trial, no-commitment] ``` **Q: Can I try this before committing to anything?** Yes — right now, in fact. Ask a real question about your own business, or ask Council something about how it itself works. There's no setup required to test whether it answers honestly. --- ```yaml category: conversion stage: 4_try_before_trust tags: [self-demonstration, proof] ``` **Q: How do I know the answers in this FAQ are trustworthy, if you built the demo yourself?** Because this FAQ *is* the knowledge base. Every answer here was generated the same way an answer to your customer would be — asked of Council, about Council, not written as marketing copy and dropped in afterward. If it can't be accurate and honest about its own product, that's worth knowing before you'd ever trust it with yours. Ask it something harder than what's written here and see what happens. --- ```yaml category: conversion stage: 4_try_before_trust tags: [next-step, onboarding] ``` **Q: What happens after I ask my first real question?** Whatever it can't answer yet becomes the starting list for building out your own knowledge base — not a guess at what you might need, but an actual gap identified from a real question you asked. That's the first concrete step toward a working instance for your business. ## Clerk **Received.** This deposit is the Council FAQ KB seed — a self-contained, queryable starter set built in four stages (skepticism gate → differentiation → fit → conversion). Each entry carries light metadata (category, stage, tags) so it slots straight into the existing Codex enrichment schema. The explicit intent is “ask, don’t browse”: these answers are meant to be tested live inside Council itself, not read as static marketing copy. The file is now held in the vault. --- _PRISM refractions and Sherlock notes may be appended to this item in later turns._