Question 1

What does competitor-density territory mapping actually deliver, and how does the 4-skill bundle decompose?

Accepted Answer

An orchestration layer that sits above the operator GIS + demographics + foot-traffic + real-estate + franchise-management + BI + policy-as-code + WORM-storage stack and produces per-territory competitor-density maps that franchise development can act on — without triggering joint-employer, antitrust, FDD Item 12, FCRA, Fair Housing, or mobile-location-data enforcement exposure. The skill is a four-skill bundle on the territory agent. Skill 1 — Define: produce per-territory polygon definitions through the operator GIS platform (Esri ArcGIS Business Analyst, Mapbox, Carto, Maptive, Maptitude, Tableau Geo, Power BI Maps, Spotzi, Alteryx Spatial — operator chooses). Territory definitions respect (a) the operator-counsel-approved FDD Item 12 Territory disclosure (whether the franchisor grants protected territory, non-protected territory, or hybrid; whether territory is by radius, ZIP, county, MSA, or custom polygon; whether the franchisor reserves rights to develop alternative channels within the territory), (b) per-state franchise-relationship encroachment doctrine in the 23 franchise-relationship states, (c) operator-counsel-approved antitrust analysis on territory restrictions. Skill 2 — Discover: identify competitors operating within and adjacent to each territory through structured (operator-licensed CoStar, LoopNet, Crexi, LandVision, CompStak, Reonomy, Buildout, JLL Spark, Real Capital Analytics commercial-real-estate data) and unstructured (operator-permitted web sources) inputs. Discover respects per-vendor data-license terms; CoStar and LoopNet specifically have strict data-use terms that govern downstream use and redistribution. Multiple Listing Service (MLS) data carries IDX feed terms; per-state real-estate broker license rules and per-state real-estate-commission rules govern who may use MLS data for what purpose and whether operator-side use requires broker affiliation. Skill 3 — Score: compute per-territory competitor density, vertical saturation, channel pressure, and whitespace indicators from operator-licensed demographics (Esri Tapestry, Claritas PRIZM, Experian Mosaic, Acxiom InfoBase, Nielsen DMA, Catalist, IXI, Buxton — operator chooses) and operator-licensed foot-traffic data (SafeGraph, Placer.ai, Foursquare Movement, Near, Cuebiq, Skyhook, Spectus — operator chooses). Mobile-location data flows through the operator-counsel-approved per-vendor consent-provenance attestation; the FTC enforcement wave in 2024 — FTC v X-Mode Social and Outlogic in January 2024, FTC v Mobilewalla in December 2024, FTC v Avast in February 2024, Massachusetts AG v X-Mode in 2024 — established that location-data vendors with broken consent provenance create direct enforcement exposure for downstream users. When demographics data is used to inform credit decisions for franchisee financing, FCRA 15 USC 1681 applies; when used for employment, FCRA-as-investigative-consumer-report applies; when used for insurance underwriting, state insurance and federal FCRA apply. Skill 4 — Recommend: emit per-territory franchise-development recommendations with operator-counsel-approved framing. Recommendations distinguish operator-mandatory items (compliance-flagged items operator-side approval required before franchise-development action) from advisory items (development considerations the franchise-development team reviews). Recommendations carry the FDD Item 19 Financial Performance Representation evaluation when comparative metrics enter the recommendation; FPR-class outputs route through FTC Franchise Rule 16 CFR Part 436 substantiation and FDD currency verification before any communication to prospective franchisees or in any franchise-sales context. The GIS, demographics, foot-traffic, real-estate, franchise-management, BI vendors below ship strong primitives. The orchestration above them — FDD Item 12 + Item 19 + state-by-state registration consistency + state franchise-relationship-law overlay, antitrust + per-state non-compete posture, per-state real-estate broker + RESPA + MLS license enforcement, Fair Housing + Fair Lending + ECOA + CRA enforcement when franchisee financing analyzed, mobile-location consent-provenance enforcement under the 2024 FTC enforcement wave, FCRA enforcement when demographics inform credit/insurance/employment decisions, audit trail — is operator-side architecture.

Question 2

Where does single-vendor GIS stop compounding for multi-unit franchise development at scale?

Accepted Answer

Single-vendor GIS is solved. Esri ArcGIS Business Analyst ships a strong territory analysis + demographics + Business Analyst Web App. Mapbox and Carto ship strong programmable GIS. Maptive and Maptitude ship strong desktop territory mapping. SafeGraph and Placer.ai ship strong foot-traffic. CoStar and LoopNet ship strong commercial real estate. The compound case the territory agent has to handle is the one where (a) the franchisor is making development decisions that will be memorialized in the FDD Item 12 Territory disclosure — and FDD updates run on an annual cycle with per-state registration filings in 14 states (California, Hawaii, Illinois, Indiana, Maryland, Michigan, Minnesota, New York, North Dakota, Rhode Island, South Dakota, Virginia, Washington, Wisconsin), so the territory analysis methodology has to be defensible across that annual cycle, (b) territory comparisons that surface in any franchise-development communication with prospective franchisees become FDD Item 19 Financial Performance Representations under FTC Franchise Rule 16 CFR Part 436 — out-of-FDD FPRs are FTC enforcement targets and per-state franchise-registration violations, (c) territory restrictions face antitrust analysis under Sherman Act + Robinson-Patman + state UDAP + the Leegin Creative Leather Products v PSKS Inc 2007 rule-of-reason framework for RPM, with California Cartwright Act + Maryland + state patchwork retaining per-se RPM in some contexts, (d) per-state non-compete law has been evolving rapidly — California AB 1076 effective January 1 2024 expanded California’s ban on non-competes and required employers to notify current and former employees of unenforceable non-competes; Minnesota Statute 181.988 effective July 1 2023 banned most non-competes; Oklahoma and a handful of other states impose strict limits; FTC issued a Final Rule banning most non-competes in April 2024 that was vacated by the Northern District of Texas in August 2024 + the appeal is pending at the 5th Circuit through 2025-2026 — franchise-territory restrictions on franchisees and franchisor-side non-competes operate in a live regulatory environment, (e) per-state real-estate broker-license rules govern who may use MLS data and CoStar/LoopNet/Crexi data for what purposes; RESPA 12 USC 2601 governs settlement service kickbacks when franchisor-broker arrangements exist, (f) when territory analysis informs franchisee credit decisions or financing decisions, ECOA Regulation B 12 CFR 1002 + Fair Lending + CFPB UDAAP apply, and Community Reinvestment Act 12 USC 2901 applies when federally-insured lenders are involved, (g) Fair Housing Act + HUD AI/algorithmic-decisionmaking guidance apply when territory analysis touches residential demographics in ways that influence housing-adjacent decisions, (h) mobile-location data flows through SafeGraph + Placer.ai + Foursquare Movement + Near + Cuebiq + Skyhook + Spectus carry per-vendor consent-provenance exposure under the FTC 2024 enforcement wave — X-Mode/Outlogic January 2024, Mobilewalla December 2024, Avast February 2024, MA AG v X-Mode 2024 established that operators using location data from vendors with broken consent provenance face direct enforcement exposure, (i) demographics data (Esri Tapestry, Claritas PRIZM, Experian Mosaic, Acxiom InfoBase) when used for credit, insurance, or employment decisions implicates FCRA 15 USC 1681. Without an orchestration layer above the GIS + demographics + foot-traffic + real-estate + franchise-management vendors, FDD Item 12 + Item 19 currency drifts (the analysis runs ahead of the FDD update), antitrust + non-compete posture goes stale (CA AB 1076 + Minnesota + FTC Rule litigation evolves but the territory analysis stays on prior rules), per-state real-estate broker + RESPA + MLS license enforcement breaks, Fair Housing + ECOA + CRA enforcement gaps surface when franchisee financing analyzed, mobile-location data vendor risk compounds, FCRA scope leaks when demographics inform credit/insurance/employment, and the audit trail of "which territory analysis, against which FDD version, with which counsel-policy-version, using which licensed datasets, with which vendor consent-provenance attestation" fragments across consoles. The orchestration above the vendors is what holds the cross-vendor + cross-jurisdiction + cross-statute + cross-license invariants.

Question 3

How does Skill 1 Define handle FDD Item 12 Territory + per-state franchise-relationship encroachment doctrine?

Accepted Answer

Territory definition is operator-counsel-approved and reflects the FDD Item 12 Territory disclosure verbatim. Step 1 — read the current FDD Item 12. FTC Franchise Rule 16 CFR Part 436.5(l) requires the FDD Item 12 to describe (a) whether the franchisee is granted exclusive territory, (b) whether the franchisor or affiliates may operate competing units within the territory, (c) whether the franchisor or affiliates may operate under different trademarks within the territory, (d) whether the franchisee’s ability to expand depends on satisfying minimum sales quotas or similar performance benchmarks, (e) how territory disputes are resolved. Step 2 — read per-state franchise-relationship law overlay. The 23 franchise-relationship states (Arkansas, California, Connecticut, Delaware, Hawaii, Illinois, Indiana, Iowa, Maryland, Michigan, Minnesota, Mississippi, Missouri, Nebraska, New Jersey, North Dakota, Rhode Island, South Dakota, Virginia, Washington, Wisconsin, plus Puerto Rico and US Virgin Islands — counts vary by source) impose state-by-state restrictions on territory encroachment, non-renewal, transfer denial, and bad-faith conduct. Some states explicitly regulate encroachment (e.g., Wisconsin Chapter 553 and similar); others rely on general good-faith-and-fair-dealing doctrines. Operator counsel maintains the per-state encroachment posture. Step 3 — encode territory polygons in the GIS platform with metadata: territory type (radius, ZIP, county, MSA, custom polygon), exclusivity status, franchisor reserved rights, performance benchmarks if any, dispute-resolution mechanic. The polygons live in operator-controlled GIS storage. Step 4 — annual FDD update synchronization. When the FDD is updated for the registration-state filing cycle, territory polygons sync to match the updated Item 12. Step 5 — antitrust + non-compete posture overlay. Territory restrictions that involve franchisee-side non-competes route through the per-state non-compete posture (California AB 1076 banning most non-competes effective January 1 2024; Minnesota Statute 181.988 banning most non-competes effective July 1 2023; the FTC Final Rule banning most non-competes April 2024 vacated by ND Texas August 2024 with pending 5th Circuit appeal; Oklahoma + Massachusetts + Illinois with state-specific rules; California has long banned most non-competes under Business and Professions Code 16600 with limited carve-outs). Operator counsel maintains the per-state non-compete posture. Step 6 — audit trail. Per-territory definition writes to the WORM audit trail with FDD-version + per-state registration consistency + per-state encroachment posture + per-state non-compete posture + counsel-policy-version. The audit trail supports defense in a franchisee encroachment challenge or state-AG investigation.

Question 4

How does Skill 3 Score handle mobile-location data privacy and FCRA when demographics inform franchisee credit decisions?

Accepted Answer

Mobile-location data and demographics data have specific enforcement exposure that the orchestration manages explicitly. Mobile-location data: the FTC 2024 enforcement wave established that operators using location data from vendors with broken consent provenance face direct enforcement exposure. FTC v X-Mode Social and Outlogic in January 2024 settled with a prohibition on sale and use of sensitive location data and restrictions on raw-location-data use. FTC v Mobilewalla in December 2024 settled with restrictions on location-data acquisition and use. FTC v Avast in February 2024 settled with a $16.5 million penalty for misrepresenting browsing data privacy. Massachusetts AG v X-Mode in 2024 reinforced state-AG scrutiny. The orchestration enforces per-vendor consent-provenance attestation — operator counsel reviews each mobile-location data vendor (SafeGraph, Placer.ai, Foursquare Movement, Near, Cuebiq, Skyhook, Spectus) and assigns the vendor an operator-counsel-approved posture (cleared, cleared with restrictions, paused, prohibited). Vendors with paused or prohibited posture cannot contribute to Score outputs. Per-vendor consent provenance includes (a) the chain of consent from the original mobile user through any intermediaries to the operator’s licensed dataset, (b) the per-jurisdiction consent class (CCPA opt-out propagation, GDPR Article 6 lawful basis when EU residents, Maryland Online Data Privacy Act, Washington MHMDA when health-context location, state-comprehensive-privacy patchwork), (c) the per-vendor data-license terms governing operator-side use. Sensitive location data (visits to healthcare facilities, places of worship, schools, addiction-treatment, reproductive-health facilities) carries additional restrictions per the FTC X-Mode settlement; the orchestration excludes sensitive-location data unless operator counsel has specifically cleared the use case. Demographics data: when Esri Tapestry, Claritas PRIZM, Experian Mosaic, Acxiom InfoBase, Nielsen DMA, Catalist, IXI, or Buxton demographics are used to inform a credit decision (e.g., franchisee creditworthiness scoring), the use becomes a consumer-report use under FCRA 15 USC 1681. FCRA permissible-purpose requirements apply (the operator must have a permissible purpose under 15 USC 1681b), and the consumer-report user must comply with adverse-action notice obligations under FCRA Section 615 (15 USC 1681m) when an adverse action is taken on the basis of the report. The orchestration tags demographics use cases and routes credit-implicating uses through operator counsel for FCRA compliance evaluation. ECOA Regulation B 12 CFR 1002 notice-of-action also applies. When federally-insured lenders are involved in franchisee financing, Community Reinvestment Act 12 USC 2901 applies. When demographics analyze housing-adjacent decisions, Fair Housing Act + HUD AI/algorithmic-decisionmaking guidance + state fair-housing acts apply. The Score skill emits per-output the vendor-consent-provenance attestation + FCRA evaluation status + ECOA evaluation status + Fair Housing evaluation status to the WORM audit trail.

Question 5

What compliance does the orchestration enforce, and how does it map to FTC Franchise Rule + antitrust/non-compete + real-estate + Fair Housing/Lending + mobile-location/FCRA?

Accepted Answer

Five anchors. Anchor 1 — FTC Franchise Rule 16 CFR Part 436 + FDD maintenance + Item 12 Territory + Item 19 Financial Performance Representations + Item 20 Franchisee Lists + 14-state franchise registration + 23-state franchise-relationship laws (counts vary slightly by source). The orchestration enforces FDD currency, Item 12 Territory consistency, Item 19 substantiation for FPR-class outputs, per-state filing alignment, and per-state relationship-law overlay on encroachment and termination-implicating outputs. Anchor 2 — Antitrust + non-compete. Sherman Act + Robinson-Patman + state UDAP + Hart-Scott-Rodino when M&A + Leegin Creative Leather Products v PSKS Inc 2007 federal RPM rule-of-reason framework + California Cartwright Act + Maryland + state per-se exceptions surviving in some contexts. Per-state non-compete posture: California AB 1076 (effective January 1, 2024) expanding California’s ban on non-competes and requiring notice to current and former employees of unenforceable non-competes + California Business and Professions Code 16600 long-standing prohibition with limited carve-outs; Minnesota Statute 181.988 (effective July 1, 2023) banning most non-competes; Oklahoma; Massachusetts Noncompetition Agreement Act 2018; Illinois Freedom to Work Act; Washington RCW 49.62 with salary threshold; Oregon ORS 653.295; Colorado Revised Statutes 8-2-113; state patchwork. FTC Final Rule banning most non-competes (April 2024) was vacated by the Northern District of Texas in August 2024 (Ryan LLC v FTC); appeal pending at the 5th Circuit through 2025-2026; further FTC rulemaking possible. Anchor 3 — Per-state real-estate broker license rules + RESPA 12 USC 2601 + per-state real-estate-commission advertising rules + MLS data-use terms + CoStar Terms of Service + LoopNet Terms of Service + Crexi Terms of Service + Reonomy Terms of Service + IDX feed licensing + per-state broker-affiliation requirements when MLS data used. Anchor 4 — Fair Housing Act + HUD AI/algorithmic-decisionmaking guidance + per-state fair-housing acts + Equal Credit Opportunity Act ECOA Regulation B 12 CFR 1002 + Fair Lending + CFPB UDAAP + Community Reinvestment Act 12 USC 2901 when federally-insured lenders involved in franchisee financing + state UDAP. Anchor 5 — Mobile-location data privacy + FTC 2024 enforcement wave + FCRA when demographics inform credit/insurance/employment + state-comprehensive-privacy. FTC v X-Mode Social and Outlogic (January 2024) + FTC v Mobilewalla (December 2024) + FTC v Avast (February 2024) + Massachusetts AG v X-Mode (2024) established direct operator exposure for downstream use of location data with broken consent provenance + sensitive-location-data restrictions. Per-vendor consent-provenance attestation required (SafeGraph + Placer.ai + Foursquare Movement + Near + Cuebiq + Skyhook + Spectus). FCRA 15 USC 1681 permissible-purpose + adverse-action notice when demographics inform credit decisions. ECOA Regulation B notice-of-action. CCPA Section 1798.140(ae) cross-context-behavioral-advertising opt-out + Section 1798.121 sensitive PI + Maryland Online Data Privacy Act + Washington My Health My Data Act (effective April 2024) + state-comprehensive-privacy patchwork. GDPR Articles 6 + 9 + 22 + 26 + Article 35 DPIA + ePrivacy when EU users. Broader gate also enforced: SOC 2 + ISO 27001 for territory data security + per-state pricing-display when territory analysis informs pricing recommendations + state employment-AI laws (NYC LL144, Illinois AIVIA) when territory analysis informs franchisee hiring + Colorado AI Act effective February 2026 when consequential decisions via policy-as-code (OPA Rego + AWS Cedar + Casbin + Cerbos + Oso). WORM audit trail (AWS S3 Object Lock + GCS retention + Azure Blob immutable + Snowflake Time Travel) with per-statute retention (FTC Franchise Rule 7yr + state franchise-registration variable + state relationship-law variable + FCRA 25mo + ECOA 25mo + Fair Housing variable + RESPA 5yr + GDPR 6yr + CCPA 3yr + FTC 7yr + IRS 7yr) per operator counsel policy.

Question 6

What does the engagement look like across Tier 1 → Tier 2 → Tier 3, and what does the Tier 3 reporting cycle commit to?

Accepted Answer

Tier 1 AI Readiness Assessment (2-3 weeks, diagnostic): audits the operator current competitor-density territory mapping posture against the 4-skill bundle + 5-anchor compliance overlay + per-vendor GIS + demographics + foot-traffic + real-estate + franchise-management state; deliverable is a gap-pack report identifying which territory polygons drift from the current FDD Item 12, which Score outputs cross into FDD Item 19 FPR exposure, which antitrust + non-compete posture gaps exist relative to CA AB 1076 + Minnesota + Oklahoma + FTC Rule litigation, which per-state real-estate broker license + RESPA + MLS license exposure exists in operator-side data use, which Fair Housing + ECOA + CRA + Fair Lending paths apply when territory analysis informs franchisee financing, which mobile-location data vendors lack operator-counsel-approved consent-provenance attestation given the 2024 FTC enforcement wave, which demographics use cases lack FCRA evaluation when informing credit/insurance/employment, and a recommended remediation sequence for Tier 2. Tier 2 AI Swarm Setup Sprint (4-8 weeks): builds the 4-skill bundle on the territory agent, wires GIS + demographics + foot-traffic + real-estate + franchise-management + BI + policy-as-code + WORM-storage vendors (operator-chosen subset), configures the operator-counsel-approved FDD Item 12 Territory polygon library + per-state encroachment overlay + Item 19 FPR substantiation library + antitrust + per-state non-compete posture + per-state real-estate broker + RESPA + MLS license register + Fair Housing + ECOA + CRA + Fair Lending evaluation flow + mobile-location data per-vendor consent-provenance attestation register + FCRA + ECOA evaluation flow for demographics + CCPA cross-context + GDPR + Maryland ODPA + Washington MHMDA propagation, runs 30-day shadow + canary period before flipping to enforce-mode. Tier 3 Fractional CMO with AI Swarm (6-month minimum, 1-2 days/wk embedded): continues operating with monthly per-territory refresh + quarterly FDD Item 12 + Item 19 review against the annual FDD update cycle + quarterly per-state non-compete posture review against case-law and statute amendments + quarterly per-vendor consent-provenance attestation refresh + quarterly compliance evidence packages. Tier 3 reporting is a 6-workstream pre-engagement-baseline reporting cycle (per-territory polygon currency against current FDD Item 12 + Item 19 FPR substantiation coverage when outputs cross into FPR + per-state encroachment + non-compete posture maintenance + per-state real-estate broker + RESPA + MLS license compliance + per-vendor mobile-location consent-provenance attestation freshness + WORM audit-trail completeness) measured against the operator’s pre-engagement baseline. Each workstream surfaces trend direction and the gap to operator-defined targets. Reporting carries explicit caveats: GIS + demographics + foot-traffic + real-estate + franchise-management vendor SLA + FTC Franchise Rule interpretive guidance + FDD amendments + per-state franchise registration statute amendments + per-state franchise-relationship statute amendments + Sherman Act + Leegin progeny + state RPM doctrine evolution + per-state non-compete statute and case-law evolution + FTC non-compete rule litigation through 2025-2026 + CA AB 1076 implementing guidance + Minnesota and other state non-compete amendments + RESPA interpretive guidance + per-state real-estate-commission amendments + MLS policy updates + CoStar/LoopNet/Crexi terms updates + Fair Housing + HUD AI guidance + ECOA + CFPB + CRA + Fair Lending amendments + FTC mobile-location enforcement evolution + FCRA interpretive guidance + state-comprehensive-privacy implementing rules sit outside Completions control. Attorney-client privilege preservation across operator-counsel-approved FDD Item 12 polygon library + Item 19 FPR substantiation + antitrust + non-compete posture + real-estate license register + Fair Housing/ECOA/CRA flow + mobile-location consent-provenance attestation + FCRA evaluation records is maintained per operator counsel policy.

Question 7

Who owns the GIS data, the FDD library, the per-state non-compete posture, the consent-provenance attestation, and the audit trail?

Accepted Answer

Operator owns every artifact. The GIS subscriptions (Esri ArcGIS Business Analyst, Mapbox, Carto, Maptive, Maptitude, Tableau Geo, Power BI Maps, Spotzi, Alteryx Spatial — operator chooses) run under operator billing on operator-controlled accounts. The demographics subscriptions (Esri Tapestry, Claritas PRIZM, Experian Mosaic, Acxiom InfoBase, Nielsen DMA, Catalist, IXI, Buxton — operator chooses) run under operator licenses. The foot-traffic subscriptions (SafeGraph, Placer.ai, Foursquare Movement, Near, Cuebiq, Skyhook, Spectus — operator chooses) run under operator licenses with operator-counsel-approved per-vendor consent-provenance attestation. The commercial-real-estate subscriptions (CoStar, LoopNet, Crexi, LandVision, CompStak, Reonomy, Buildout, JLL Spark, Real Capital Analytics — operator chooses) run under operator licenses with strict per-vendor terms-of-service compliance. The franchise-management subscription (FranConnect, Naranga, Wingspread, Franchise360, 1851 Franchise — operator chooses) runs under operator billing. The BI subscriptions (Looker, Tableau, Power BI, Sigma, Hex, Mode, ThoughtSpot — operator chooses) run under operator billing. The Franchise Disclosure Document and per-state franchise-registration filings live in operator counsel + franchise administration repo. The operator-counsel-approved FDD Item 12 Territory polygon library + Item 19 FPR substantiation library + per-state encroachment overlay + antitrust + per-state non-compete posture + per-state real-estate broker + RESPA + MLS license register + Fair Housing + ECOA + CRA + Fair Lending evaluation flow + mobile-location data per-vendor consent-provenance attestation register + FCRA + ECOA evaluation flow + GDPR + Maryland ODPA + Washington MHMDA + state-comprehensive-privacy + CCPA cross-context records all live in operator counsel repo. The Define + Discover + Score + Recommend skill code lives in operator code repo. The WORM audit trail lives on operator-controlled cloud storage (AWS S3 Object Lock + GCS retention + Azure Blob immutable + Snowflake Time Travel) with per-statute retention enforcement. The policy-as-code policies (OPA Rego + AWS Cedar + Casbin + Cerbos + Oso) live in operator code repo, counsel-aligned. The FTC Franchise Rule + antitrust + non-compete + real-estate + Fair Housing + ECOA + CRA + mobile-location + FCRA + GDPR + state-comprehensive-privacy compliance evidence records are operator-counsel-maintained. Completions owns the orchestration knowledge — how to design the territory polygon library against the operator’s current FDD Item 12, how to wire Item 19 FPR substantiation when comparative metrics cross into FPR, how to maintain the per-state encroachment + non-compete posture against the live case-law and FTC-rule litigation, how to wire RESPA + per-state real-estate broker + MLS license compliance, how to wire Fair Housing + ECOA + CRA + Fair Lending evaluation when franchisee financing analyzed, how to maintain per-vendor mobile-location consent-provenance attestation against the 2024 FTC enforcement wave, how to wire FCRA + ECOA when demographics inform credit decisions, how to propagate CCPA cross-context + GDPR + state-comprehensive-privacy — and that knowledge transfers under the Tier 3 transition path (30-60 days at engagement end with full hand-off of the FDD Item 12 polygon library maintenance playbook, the Item 19 FPR substantiation maintenance runbook, the per-state non-compete posture maintenance playbook, the per-state real-estate broker + RESPA + MLS license maintenance playbook, the Fair Housing/ECOA/CRA evaluation playbook, the mobile-location consent-provenance attestation maintenance playbook, the FCRA + ECOA evaluation playbook, the privacy propagation playbook, and the compliance evidence-package generation playbook). Completions credentials revoke on engagement-end.

The real ecosystem this sits above

GIS + territory analysis

Demographics + foot traffic

Commercial real estate

Franchise management + BI

Policy-as-code + WORM + legal research

Frequently asked