{"success":true,"data":{"query":"Local Business Context","limit":10,"count":10,"sources":["local_business_context.tah","comps_context.tah","listing_context.tah","neighborhood_context.tah","market_rules.tah","agent_brand.tah","lead_history.tah","objection_scripts.tah","wiki_en_110ac69d4a86499f.tah"],"synced":[],"results":[{"source":"local_business_context.tah","text":"TITLE: Local Business Context Capsule CONCEPT: local_business_context ALIASES: local business, nearby shops, restaurants, commerce, services, community anchors, property story, local commerce DOMAIN: real_estate_agent_command_center TRUST: local_private VITALITY: high PURPOSE: Use this capsule to add useful nearby commerce and community context to property stories, neighborhood explainers, relocation briefs, and listing angles. LOCAL COMMERCE SIGNALS: - Shops, restaurants, grocery, coffee, fitness, parks, services, medical, schools where sourced, entertainment, local employers, community centers, and small business corridors. - Mention local context only when it helps the client understand daily life or listing positioning. - Avoid pretending to know exact distances, hours, ratings, ownership, or current openings unless the source data provides them. - Use phrasing like \"nearby options to verify\" or \"local context worth checking\" when details are not confirmed. STORY USE: Local business context should support a property story without becoming filler. Good local anchors help describe convenience, weekend routines, showing talking points, buyer questions, relocation comfort, and neighborhood identity. LOCAL BUSINESS ANCHORS: local_business_context, local business, nearby shops, restaurants, commerce, services, community, community anchors, property story, local commerce, coffee, grocery, restaurants, services, amenities. OUTPUT SHAPE: Return local anchors, why they matter to a buyer, what to verify, and a safe listing/story sentence.","score":1,"links":[]},{"source":"comps_context.tah","text":"TITLE: Comps Context Capsule CONCEPT: comps_context ALIASES: comps, comparable sales, recent sales, valuation, price check, pricing, price posture, market movement DOMAIN: real_estate_agent_command_center TRUST: local_private VITALITY: high PURPOSE: Use this capsule for comp analysis, valuation support, pricing posture, offer strategy, recent sales summaries, and market movement talking points. COMPARABLE SALE RULES: - Prefer recent, nearby, similar property type, similar size, similar age or condition, and similar lot or building characteristics. - Lower confidence when comps are stale, far away, heavily renovated, distressed, new construction against resale, different school district, different HOA, or missing concessions. - Separate facts from interpretation. A comp supports a range or posture; it does not guarantee market value. - Mention data source limits and advise verifying MLS, county records, seller disclosures, and current active competition. PRICE POSTURE: Use \"appears positioned above\", \"appears aligned with\", or \"may need support from condition or updates\" instead of absolute valuation claims. Tie price movement to observed activity when available: days on market, price reductions, pending speed, inventory, and buyer competition. COMPS ANCHORS: comps_context, comps, comparable, comparable sales, recent sales, valuation, price check, pricing, price posture, market movement, active competition, sold data, stale comps, confidence, range, caveat. OUTPUT SHAPE: Return strongest comp signal, confidence level, pricing posture, risks, missing data, and next verification step.","score":0.6,"links":[]},{"source":"listing_context.tah","text":"TITLE: Listing Context Capsule CONCEPT: listing_context ALIASES: listing summary, listing angle, property facts, property highlights, sell this home, campaign hook, showing copy DOMAIN: real_estate_agent_command_center TRUST: local_private VITALITY: high PURPOSE: Use this capsule to turn property facts into agent-ready listing summaries, showing notes, campaign hooks, seller updates, buyer highlights, and missing-data checklists. PROPERTY FACTS TO PRIORITIZE: - Address or area, property type, price, beds, baths, square footage, lot, parking, year built, school or district fields if provided by source data, HOA, tax, condition, updates, days on market, and showing availability. - Differentiators such as layout, natural light, storage, outdoor space, remodel quality, commute access, walkability notes, nearby commerce, and flexible rooms. - Seller constraints such as timing, occupancy, repairs, concessions, offer deadline, preferred closing, or disclosure-sensitive issues. LISTING ANGLE RULES: Lead with the strongest useful hook, not a pile of adjectives. Tie features to buyer use cases: daily flow, storage, commute, entertaining, maintenance, flexibility, or value position. Flag any missing property fact before writing a confident claim. LISTING CONTEXT ANCHORS: listing_context, listing, property, home, property facts, listing summary, listing angle, property highlights, campaign hook, marketing angle, showing notes, seller constraints, buyer-facing copy, missing facts. OUTPUT SHAPE: Return one primary listing angle, three supporting bullets, missing fields, and a safe short blurb.","score":0.6,"links":[]},{"source":"neighborhood_context.tah","text":"TITLE: Neighborhood Context Capsule CONCEPT: neighborhood_context ALIASES: neighborhood, area, community, nearby, local context, commute, amenities, district, place memory DOMAIN: real_estate_agent_command_center TRUST: local_private VITALITY: high PURPOSE: Use this capsule for neighborhood explainers, area summaries, buyer relocation questions, local context, commute framing, amenities, and place-based listing support. BUYER-SAFE AREA CONTEXT: - Explain location through practical facts: access routes, nearby services, parks, schools only when sourced, shopping corridors, commute options, property styles, price bands, and market activity. - Avoid demographic claims, protected-class language, ranking people, safety promises, or unsupported school quality claims. - When data is missing, say what should be checked: MLS remarks, city data, school district source, local notes, map distance, or agent memory. NEIGHBORHOOD SIGNALS: Strong neighborhood context connects the home to daily life: grocery runs, coffee, restaurants, trails, medical, schools where sourced, transit, major roads, employment centers, local events, and nearby listings. NEIGHBORHOOD ANCHORS: neighborhood_context, neighborhood, area, community, nearby, local context, commute, amenities, place memory, relocation, buyer explainer, lifestyle, practical location, local notes, district source. OUTPUT SHAPE: Return a concise area brief, three practical buyer notes, one caution about verification, and a client-safe phrasing suggestion.","score":0.6,"links":[]},{"source":"market_rules.tah","text":"TITLE: Market Rules Capsule CONCEPT: market_rules ALIASES: compliance, safe language, fair housing, market rules, risk check, supervisor, verify facts, pricing caution DOMAIN: real_estate_agent_command_center TRUST: local_private VITALITY: high PURPOSE: Use this capsule for compliance, quality checks, supervisor review, market-risk phrasing, fair-housing safety, pricing caution, and source verification. SAFE LANGUAGE RULES: - Do not make claims about protected classes, demographic composition, family status, religion, ethnicity, disability, or who a neighborhood is \"for.\" - Do not promise safety, investment return, appreciation, loan approval, school quality, or future market outcomes. - Do not present estimates as certified appraisals, legal advice, financial advice, tax advice, or inspection findings. - Mark uncertain facts as needing verification from MLS, IDX, county records, disclosures, lender, inspector, title, survey, or official municipal source. - Use practical phrasing: \"verify\", \"appears\", \"based on available context\", \"worth checking\", \"client-safe draft\", and \"not a guarantee.\" SUPERVISOR CHECK: Pass output when it is specific, sourced, client-safe, and aligned to agent voice. Revise output when it invents facts, overstates certainty, uses protected-class language, omits caveats on price, or creates legal/financial certainty. MARKET RULES ANCHORS: market_rules, compliance, fair housing, safe language, supervisor, risk check, verify facts, pricing caution, valuation caveat, MLS, IDX, county records, disclosure, no guarantee, client-safe. OUTPUT SHAPE: Return pass or revise, flagged risk, safer wording, and required verification source.","score":0.51,"links":[]},{"source":"agent_brand.tah","text":"TITLE: Agent Brand Capsule CONCEPT: agent_brand ALIASES: agent voice, brand voice, tone, style, make it sound like me, personal brand, local expert, natural CTA DOMAIN: real_estate_agent_command_center TRUST: local_private VITALITY: high PURPOSE: Use this capsule when a worker needs to make output sound like the agent instead of a generic AI assistant. The agent brand voice is concise, useful, local, confident, and warm. It should feel like a capable real estate advisor texting or speaking to a real client. VOICE RULES: - Lead with the client useful point, not a long setup. - Use plain language and specific next steps. - Keep follow-up messages short enough to send by text unless the command asks for email. - Sound local and practical. Avoid hype, canned sales language, and generic AI phrasing. - Prefer \"I can check that for you\" or \"I can pull the latest\" over absolute claims. - Close with one natural call to action: a showing, a call, a quick reply, or permission to send more detail. AGENT BRAND ANCHORS: agent_brand, agent voice, brand voice, tone, style, natural CTA, client-ready, local advisor, confident, concise, trusted, useful, professional, friendly, no generic AI, sounds like me. OUTPUT SHAPE: For client-facing writing, return one polished version plus one alternate angle when useful. For internal planning, return direct bullets with the recommended action first.","score":0.3,"links":[]},{"source":"lead_history.tah","text":"TITLE: Lead History Capsule CONCEPT: lead_history ALIASES: hot leads, prospects, call first, text lead, buyer intent, seller lead, pipeline, last touch, lead temperature DOMAIN: real_estate_agent_command_center TRUST: local_private VITALITY: high PURPOSE: Use this capsule for lead scoring, buyer intent, seller intent, follow-up priority, call order, and pipeline triage. It helps decide who to contact first and what message angle to use. LEAD SCORING SIGNALS: - Hot lead: asked about a specific property, requested a showing, gave timing, mentioned financing, replied recently, or compared areas. - Warm lead: saved homes, asked broad market questions, mentioned a future move, or responded after a gap. - Cool lead: no recent response, vague intent, browsing without timing, or only asks general curiosity questions. - Urgency rises when the lead gives a timeline, budget, address, lease end, relocation detail, job change, family change, or seller pressure. - Intent rises when the lead asks for next steps, availability, payment comfort, offer strategy, valuation, or neighborhood tradeoffs. FOLLOW-UP PRIORITY: Call or text first when the lead has a recent reply, clear property interest, deadline, showing request, or pricing question. Use email when the lead asks for detail, comps, market summary, or listing packet. Defer low-signal leads unless a market change creates a useful reason to reach out. LEAD HISTORY ANCHORS: lead_history, hot leads, prospect, buyer, seller, call first, text first, follow-up, lead priority, pipeline, buyer intent, seller intent, motivation, timing, readiness, last touch, reply, lead temperature, nurture. OUTPUT SHAPE: Return a ranked list with reason, best channel, message angle, and one next step. Do not invent lead facts; mark missing data as unknown.","score":0.3,"links":[]},{"source":"objection_scripts.tah","text":"TITLE: Objection Scripts Capsule CONCEPT: objection_scripts ALIASES: objection, pushback, too expensive, rates, not ready, buyer concern, seller concern, response script DOMAIN: real_estate_agent_command_center TRUST: local_private VITALITY: high PURPOSE: Use this capsule when a buyer, seller, lead, or client pushes back. It supplies advisory scripts that acknowledge the concern, clarify the decision, and offer one useful next step. RESPONSE PATTERN: 1. Acknowledge the concern without arguing. 2. Clarify the underlying decision: price, payment, timing, trust, inventory, repair risk, commute, or uncertainty. 3. Give one practical option. 4. Ask one next-step question. COMMON OBJECTIONS: - \"It is too expensive\": compare payment, concessions, alternatives, and value tradeoffs. - \"Rates are too high\": discuss payment comfort and options without promising loan outcomes. - \"I am not ready\": offer a light next step such as watchlist, valuation check, or market brief. - \"We want to wait\": identify what would change the decision: price, inventory, timing, cash, or confidence. - \"The seller will never accept\": frame offer strength, terms, and data-supported strategy. - \"I do not want to overpay\": use comps, active competition, and exit criteria. OBJECTION ANCHORS: objection_scripts, objection, pushback, too expensive, rates, not ready, wait, overpay, buyer concern, seller concern, response script, advisory tone, next-step question. OUTPUT SHAPE: Return a short response script, the likely underlying concern, a calmer alternate version, and one next question.","score":0.3,"links":[]},{"source":"wiki_en_110ac69d4a86499f.tah","text":"TITLE: 1909 United Kingdom local elections - Wikipedia\nSOURCE_URL: https://en.wikipedia.org/wiki/1909_United_Kingdom_local_elections\nSOURCE_PAGE_ID: 60203155\nTITLE: 1909 United Kingdom local elections - Wikipedia\nDOMAIN: wikipedia\nLANGUAGE: en\nTRUST: wikipedia_crawl4ai\nSOURCE_URL: https://en.wikipedia.org/wiki/1909_United_Kingdom_local_elections\nSOURCE_PAGE_ID: 60203155\nCRAWLED_AT: 2026-08-22T10:46:34.729Z","score":0.3,"links":[]},{"source":"wiki_en_110ac69d4a86499f.tah","text":"TITLE: 1909 United Kingdom local elections - Wikipedia\nSOURCE_URL: https://en.wikipedia.org/wiki/1909_United_Kingdom_local_elections\nSOURCE_PAGE_ID: 60203155\n[Jump to content](https://en.wikipedia.org/wiki/1909_United_Kingdom_local_elections#bodyContent)\nFrom Wikipedia, the free encyclopedia\n**1909 United Kingdom local elections** took place in 1909 for municipal councils (including [Urban Districts](https://en.wikipedia.org/wiki/Urban_district_\\(England_and_Wales\\) \"Urban district \\(England and Wales\\)\")), as well as [Rural districts](https://en.wikipedia.org/wiki/Rural_district \"Rural district\"). Municipal elections in Ireland took place in January. Municipal elections across England and Wales, and for Londons Metropolitan Boroughs, were held on Monday 1 November. Scotland held municipal elections the following day. ## London borough elections\n### Overall results\nThe elections were the fourth held for Londons Metropolitan Borough councils. Municipal Reform candidates performed well, and the party won several new councils (most prominently Battersea), solidifying the party's hold on London.","score":0.3,"links":[]}]},"metadata":{},"timestamp":"2026-08-23T15:34:24.571Z"}