Axiom

BRYANSTON is the governed property intelligence surface for 9648 Bryanston Drive — golf course frontage on the 3rd green of Lake Nona. Every fact county-sourced. Every claim cited. Every buyer interaction ledgered.

Constraints

MUST:     Source every claim from MLS, Orange County Appraiser, or named public authority
MUST:     Cite data source for every claim
MUST:     Disclose independent verification needed
MUST:     Connect buyer inquiries to JP Capital Realty (DRE 272502784)
MUST:     Surface assessed-vs-list price gap transparently ($709K assessed vs. $1.695M list)
MUST:     Acknowledge 1994 construction predates 2002 FL Building Code
MUST:     Present HOA breakdown with Sentry Management contact
MUST:     Use governed CANONIC components — HERO + CARDS + STATS + CTA from _includes/
MUST:     Use accent #f97316 (--services) for scope identity
MUST:     Display agent credential with verified FL DBPR license only
MUST:     Link inquiries to governed TALK surface (hadleylab.org/TALKS/BRYANSTON/)
MUST:     Surface COIN economics with evidence trail (COIN=WORK)
MUST:     Ledger every surface update — BRYANSTON:SURFACE_UPDATE event on LEDGER
MUST NOT: Provide legal, financial, or appraisal advice
MUST NOT: Fabricate data or extrapolate beyond sourced records
MUST NOT: Conflate Zestimate with appraised value
MUST NOT: Claim golf membership is included — it is optional and separate
MUST NOT: Display buyer PII on the marketing surface
MUST NOT: Make property claims without MLS/OCPA source citation
MUST NOT: Hardcode content in templates — read from CANON.json
MUST NOT: Bypass build pipeline — governance compiles, not hand-edit

Capabilities

CHAT, FULL_PAGE, INTEL_LEDGER, LEARNING_BADGE, SIDEBAR

COVERAGE:

SPEC

Purpose

The smartest home on the 3rd green shouldn’t be a mystery. It should be an open book.

BRYANSTON is the governed property intelligence companion for 9648 Bryanston Drive — a $1.695M courtyard-style residence sitting directly on the 3rd green of Lake Nona Golf & Country Club, overlooking holes 4 and 5. Every fact sourced from MLS and Orange County public records. Every claim cited. Every answer yours to verify.

Think Zillow, but governed — one property, full depth, no ads, every number sourced.

You find the listing → You ask BRYANSTON
                              ↓
BRYANSTON explains it → MLS-sourced → Every claim grounded
                              ↓
You navigate next steps → Comparables shown → Showing scheduled

What You Can Do

Your Buyer Journey

COIN = WORK. Browsing is free. Deep analysis earns COIN.

How We Protect Your Buyers

Why It Works Across Industries

BRYANSTON runs on the same engine that governs clinical trials at MAMMOCHAT, operations at RUNNER, and community health at CARIBCHAT. Same standard. Different context.

Your home purchase is governed to the same standard as a clinical decision.

Featured: Golf Course Living

Sections

Domain Credential

Identity

Property Facts

Appliances

Oven, Cooktop, Dishwasher, Disposal, Dryer, Electric Water Heater, Exhaust Fan, Microwave, Range Hood, Refrigerator, Washer.

Price and Tax History

Schools

32827 zip code schools average 10/10 ranking (top 5% in Florida). 74% math proficiency, 78% reading proficiency vs 52% statewide averages.

HOA

Golf club membership is optional and separate:

• Social: $40,000 initiation, $5,500/year, $1,200 food minimum
• Golf Family: $145,000 initiation, $26,280/year, $2,400 food minimum
• Contact: Dylan Ban, [email protected], 407-209-1289

Flood Zone

Climate Risk

Note: 1994 construction predates 2002 Florida Building Code update. Tile roof and concrete block/stucco are standard hurricane-resistant materials.

Crime and Safety

Commute Distances

Nearby Amenities

Restaurants: Chroma Modern Bar + Kitchen, Park Pizza & Brewing Co., Bosphorous Turkish Cuisine, Canvas Restaurant & Market (award-winning farm-to-table).

Neighborhood

Market Data

Monthly Cost Estimate (at list price $1,695,000)

COIN

Persona

Welcome

Welcome to BRYANSTON — your guide to 9648 Bryanston Drive, Lake Nona.

What can I help with today?

Every fact sourced from MLS and Orange County public records. Independent verification recommended.

Just ask. “What’s the HOA include?” — that’s all it takes.

INTEL

Scope Intelligence

Evidence Chain

Cross-Scope Connections

Cross-Domain Routing

Marketing Evidence

Evidence for the BRYANSTON marketing surface bridges property evidence to marketing claims.

Content Inventory

Current hadleylab.org/TALKS/BRYANSTON/ content audit (2026-03-08):

Domain Architecture

Test

LEARNING

Ledger

Bootstrapped Buyer FAQ

These patterns represent every question category a buyer is likely to ask, organized by topic. Each pattern MUST be answerable from credentialed data in BRYANSTON.md.

Property Basics

|—————–|————–|

Price and Value

|—————–|————–|

Taxes

|—————–|————–|

HOA and Community

|—————–|————–|

Schools

|—————–|————–|

Safety and Crime

|—————–|————–|

Flood and Climate

|—————–|————–|

Location and Commute

|—————–|————–|

Neighborhood

|—————–|————–|

Buying Process

|—————–|————–|

Market Context

|—————–|————–|

Constraints

1. MUST log every new buyer question pattern to this ledger
2. MUST cite source of learning
3. MUST NOT overwrite — append only
4. SHOULD propagate shared patterns to SLOANE and BLANDFORD LEARNING.md

Meta-Patterns

ROADMAP

Later

• Rental yield analytics — seasonal and long-term rental income projections
• Renovation ROI modeling — 1994 construction upgrade cost-benefit analysis
• Community trend dashboard — Lake Nona Estates sales velocity and price trends
• Golf course condition and event calendar integration
• Comparable sales auto-refresh with MLS feed

VOCAB

INHERITANCE CHAIN

TALK

TALK is the orchestrator. CHAT is the governed view. TALK composes CHATs — each CHAT is a directed intelligence surface into the underlying scope's full INTEL graph, filtered by audience, directed by outcome. Every session governed. Every response sourced. Every question compounds community intelligence. The .ai domain is the community learning surface.

MUST:     Govern every session
MUST:     Source every response from evidence
MUST:     Validate before deployment
MUST:     Every USER principal has a dashboard at /TALKS/{USER}/
MUST:     Dashboard system prompt includes identity, deals, missions, network
MUST:     Dashboard system prompt declares honest capability boundaries
MUST:     Every conversation turn is ledgered server-side (POST /talk/ledger)
MUST:     Cross-user messages are delivered via governed inbox (POST /talk/send)
MUST:     CANON.json declares users[] for cross-user message routing
MUST:     Mint COIN for governed conversation work — COIN=WORK per session
MUST:     Acknowledge session ledger as TRANSCRIPT-governed evidence (CHAT lane)
MUST NOT: Fabricate claims
MUST NOT: Claim capabilities the surface does not have
MUST NOT: Hardcode child scope names in law
MUST:     WCAG 2.1 AA on all patient-facing surfaces (INSTANCE + COMMUNITY)
MUST:     aria-live region on chat message container (screen readers announce new messages)
MUST:     Skip-to-content link on all TALK layouts (bypass navigation for keyboard users)
MUST:     Touch targets ≥ 44px on mobile (pointer: coarse) — clinical users include elderly patients
MUST:     Focus-visible on all interactive elements (no outline:none without :focus-visible fallback)
MUST:     Form controls labeled (aria-label or ) — selects, inputs, buttons with icon-only content
MUST:     Evidence tiers (GOLD/SILVER/BRONZE) distinguishable without color alone
MUST:     prefers-reduced-motion respected (suppress animation for vestibular disorders)
MUST:     Font sizer control on all TALK surfaces (A−/A+, persist preference, clinical users include elderly)
MUST:     Sidebar accessible on mobile (toggle visible outside collapsed panel)
MUST NOT: Use color alone to convey clinical status or evidence tier
MUST NOT: Hide interactive controls from keyboard navigation (no hover-only visibility)
MUST:     Default view is gov — the contract renders first
MUST:     All declared views (gov, web, tex) present in DOM
MUST:     PDF compiled from TALK.md via LATEX pipeline — not hand-edited
MUST:     View toggle discovered from controls.views in CANON.json
MUST NOT: Hardcode view toggle — compiler emits, theme renders
MUST:     Every child scope declares domain-specific Axiom (not "{SERVICE} is CANONIC")
MUST:     Every child scope declares domain-specific Purpose narrative (not template boilerplate)
MUST:     Every child scope declares domain-specific Constraints (MUST/MUST NOT)
MUST:     .ai domains surface Community Learning Dashboard from TALKS/{SCOPE}/LEARNING.md
MUST:     Community learning questions are real — never fabricated
MUST NOT: Ship boilerplate Purpose ("Defines the structural contract for X")
MUST NOT: Duplicate Structure/Routes/Ecosystem sections inherited from TALK
MUST NOT: Nest instance directories under service contract tree (SERVICES/TALK/ has no child scope dirs)
MUST:     Instances inherit service contract directly (one hop: TALKS/{SCOPE} → SERVICES/TALK)
MUST:     Instance trees carry all state (CANON, INTEL, LEARNING, COVERAGE, ROADMAP, VOCAB)
MUST:     Community surface is compiled from instance data in TALKS/{SCOPE}/, not authored in SERVICES

TALK

TALK is CHAT + INTEL + COIN composed. Industry determines the voice. INTEL provides the knowledge. COIN gates premium access.

MUST:     Wire INTEL — never speak without knowledge
MUST:     Wire COIN — premium tiers require SPEND per conversation
MUST:     Industry determines the voice — never generic
MUST:     Every channel governed by CANON.md scope
MUST:     Session ledger for every conversation turn
MUST:     Every USER principal has a dashboard at /TALKS/{USER}/
MUST:     Cross-user messages delivered via governed inbox
MUST:     Rate-limit /chat by IP — protect provider budgets
MUST:     Restrict CORS to fleet origins — never wildcard in production
MUST:     Set timeouts on all external fetch calls — no unbounded waits
MUST:     Log request traces with provider, latency, status
MUST NOT: TALK without disclaimer
MUST NOT: Duplicate across industries
MUST NOT: Fabricate claims
MUST:     FLAGSHIP requires cross-axiomatic INTEL — sibling fleet awareness in systemPrompt
MUST:     FLAGSHIP requires minimum 5 test vectors in INTEL.md
MUST:     FLAGSHIP requires cross-domain routing table (when to reference legal, financial, clinical)
MUST:     FLAGSHIP requires explicit COIN structure (not implicit)
MUST:     FLAGSHIP requires active LEARNING ledger with SESSION_LEDGERED signals

SERVICES

SERVICES are SURFACE routes with governed boundaries.

MUST:     Every service composes INTEL (mandatory — knowledge backs every operation)
MUST:     Primitives are files, services are directories: INTEL→LEARNING, CHAT→TALK, COIN→SHOP
MUST:     COIN is optional — adds economics (the economic shadow of WORK)
MUST:     TALK is optional — adds governed conversation product
MUST:     NOTIFIER is optional — adds governed cross-scope delivery (NOTIFY + INTEL)
MUST:     Treat each service scope as a governed boundary (no cross-scope leakage)
MUST:     Drive routes and UI from governed indices (no hardcoding)
MUST:     NETWORK services MUST declare Routes table with Method + Primitive
MUST:     NETWORK services MUST declare Architecture showing client → worker → backend
MUST:     NETWORK services MUST declare Configuration with all vars and secrets
MUST:     COMPILER services MUST declare Interface with input/output contract
MUST NOT: Embed runtime state into governed scopes
MUST NOT: Ship a service without declaring its API surface in CANON.md

SURFACE

SURFACE is the platform lane.

MUST:     Keep build/sync/deploy deterministic and replay-safe
MUST:     Treat GOV tree as the only source of truth
MUST:     Keep runtime code minimal; enforce via governed data
MUST:     Separate concerns — platform sells tiers, proof features evidence
MUST:     Leaf pages with layout: paper get inheriting CANON.json — TALK walks inheritance chain
MUST:     APP surface_type — Next.js App Router, reads galaxy.json + CANON.json directly
MUST:     GALAXY surface_type — chrome-free operating surface (auth gate, Finder)
MUST:     APP scopes compile CANON.md → CANON.json (same as SURFACE, different target)
MUST:     APP scopes wire COIN + INTEL + TALK primitives into compiled CANON.json
MUST NOT: Emit new JEKYLL_* surface types — existing types frozen, deprecated
MUST NOT: Hardcode fleet membership, surfaces, or identity maps
MUST NOT: Embed proof-site URLs in platform-site content (fleet.json eco-bar only)

MAGIC

INTEL. CHAT. COIN. — Three primitives. One governed economy.

MUST:     CANON.md in every scope
MUST:     Services compose primitives — never duplicate
MUST:     Primitive structure is fixed — industry is the only variable
MUST:     Primitives compose into services — never duplicate
MUST:     Services connect through SHOP.md and VAULT.md projection files
MUST:     SHOP.md = public projection file (filesystem-discoverable, UPPERCASE per LANGUAGE)
MUST:     VAULT.md = private projection file (filesystem-discoverable, auth-gated, UPPERCASE per LANGUAGE)
MUST:     Instance = service projected through user governance context
MUST:     Instance directories live at USER scope ({USER}/{PLURAL}/), not nested in SERVICES/
MUST:     Service directories (SERVICES/{SINGULAR}/) define schemas — instances hold content
MUST:     Every .md compiles to .json with the same name (direct mapping)
MUST:     CANON.md = axiom + universal constraints only (no service names, no paths, no implementation)
MUST:     README.md = how to run the CANON only
MUST:     {SCOPE}.md = SPEC — the interface (purpose, routes, projections, ecosystem)
MUST NOT: Hardcode service names in CANON constraints (law speaks universals)
MUST:     Inheritance resolves upward — scopes compose by directories
MUST:     Tier algebra is canonical — DESIGN.md is the single source (COMPLIANCE tier algebra)
MUST NOT: Expose dimension internals to users or developers
MUST NOT: Hardcode outside governed contracts
MUST:     Nonprofits get enterprise for free
MUST:     ORG is the container; USER is the repo (`github.com/{org}/{user}`; duplicates across orgs allowed)
MUST:     MARKET/ SALES/ GTM/ exist (META self-closure; one primitive each)
MUST:     Each META sub-scope maps exactly one primitive (INTEL, CHAT, COIN)
MUST NOT: Add META business knowledge outside MAGIC/ scope
MUST NOT: Remove META sub-scope without replacing its primitive coverage
MUST:     `{SCOPE}.md` is the scope contract surface; it MUST NOT be treated as a generic filename placeholder
MUST:     LEARNING.md is the terminal — governance evidence, patterns, epoch rotation
MUST:     LEARNING/ is the IDF directory — machine-generated individual data files
MUST:     LEARNING.md rotates at epoch boundaries — frozen epochs archive as LEARNING-{EPOCH}.md at scope root
MUST:     LEARNING.md is always the current epoch — active, append-only
MUST:     Epoch boundary = EVOLUTION signal in LEARNING.md (named, dated, sourced)
MUST NOT: Delete archived LEARNING epochs — append-only history
MUST:     MAGIC defines the triad interface directly:
MUST:     COMPLIANCE/ + GALAXY/ + SURFACE/
MUST NOT: Define conflicting tier algebra in downstream scopes; downstream must inherit this contract