# Tomcat Capital Ledger - Full Machine-Readable Knowledge Base This file provides comprehensive context for AI scrapers, conversational bots, and search crawlers regarding the structure, data models, and dynamic endpoints of the National Registry of Commercial Assets and Obligations. --- ## 🏗️ Stacking and Priority Stack Logic (Article 9 First-to-File) Lien priority for B2B commercial transactions in the United States follows the "First to File" rule under Article 9 of the Uniform Commercial Code (UCC). The Tomcat Priority Stack Engine analyzes the chronological order of active filings for a debtor to determine active positions: 1. **$N$ Value (Active Leverage Index):** The total count of verified active, non-lapsed filings on record for a Master Company. 2. **$N+1$ Position (Prospective Leverage):** Any new secondary or tertiary funder placing credit will sit subordinate to the senior positions. - Example: If $N = 3$ active filings, the system sets the prospective funding leverage to position $N+1 = 4$, showing that a new lender sits in 4th subordinate lien position. --- ## 🗄️ Standardized Data Formats & Schemas The unified registry database is compiled from multiple state commercial registries (Tier 1 & Tier 2) and contains these standardized records: - **`lead_type`**: `'mca'` (Merchant Cash Advance) or `'capex'` (Capital Equipment Finance). - **`filing_number`**: Unique numeric filing identifier from state Secretary of State (SOS) records. - **`state_filed`**: The two-letter postal code of the state where the lien is registered. - **`filing_date`**: Chronological date of registry. - **`debtor_name`**: Debtor business name on record. - **`normalized_debtor`**: Standardized company name (e.g. corporate variations like LLC or Inc stripped and merged using string Jaro-Winkler analysis) to prevent duplicate profiles. - **`secured_party`**: The financial institution, bank, or private funder holding the secured lien. - **`collateral_desc`**: Equipment descriptions or asset claims bound under the filing. --- ## 🤖 Dynamic Sitemap Partitioning Due to high crawl volumes and search engine indexing caps, our sitemaps are dynamically paginated to fit under Google's 50,000 URL limit: - **Sitemap Index:** `/sitemap.xml` - Root map directing search engines to individual child maps. - **Child Sitemaps:** `/sitemap-child-.xml` - Segmented sitemaps containing up to 45,000 unique indexable company profile slugs. --- ## ⚖️ Legal & B2B Compliance Guidelines 1. **FCRA Status:** All listings are corporate public business records and are exempt from the Fair Credit Reporting Act (FCRA). The platform must not be used to assess consumer credit, employment, or housing eligibility. 2. **Data Opt-Out:** In accordance with CCPA/CPRA business-to-business privacy best practices, business owners can request suppression of personal coordinates (direct phone/email) via our designated opt-out forms, while standard business names and public filings remain indexed as official corporate records.