Federal grant discovery, tracking, and submission platform for the three AITCH family foundations: Today's Child Foundation (TCF), Ifoma Foundation (IFM), and AITCH Conservation Foundation (ACF). The platform automatically scans Grants.gov for mission-aligned opportunities using foundation-specific keywords and guardrails, generates AI-powered application drafts using Claude, tracks opportunities through the full application lifecycle, and sends automated email alerts when new matching grants are posted.
Features
- Dashboard with financial summaries and upcoming deadlines
- Automated opportunity scanner with relevance scoring
- Manual search with keyword, agency, ALN, and category filters
- Application tracker with status pipeline (Identified through Awarded)
- AI-powered submission draft generator (8 narrative sections)
- Grant finances tracker with awarded and pipeline totals
- Configurable email alert filters with scheduled delivery
- Foundation manager with per-entity keywords and categories
- CSV/JSON export for all data views
Foundation Scope
- TCF — Adoption advocacy, family support, youth development
- IFM — Vision care, eyewear assistance, eye health education
- ACF — Wetlands preservation, wildlife habitat, environmental education
How to Use
- Sign in with your email and password. Access is scoped by foundation role.
- Use the foundation filter in the top bar to view data for a specific foundation or all three.
- Click Run Full Opportunity Scan on the Dashboard to search Grants.gov for new matches.
- Review scan results and click Track to save opportunities to the Application Tracker.
- In the Tracker, update each opportunity's status as it progresses. Click Draft to generate an AI-powered application.
- Review and edit drafts in the Submissions view. Use Preview for a print-ready formatted document.
- Set up Email Filters to receive automated alerts when new grants match your criteria.
Expired opportunities are automatically labeled. Mission guardrails prevent cross-foundation contamination.
Launch Grants S2S →Investment portfolio rebalancing tool for 52nd Street Capital Group, anchored to the Howell Legacy Group three-tier capital architecture (Operational / Strategic / Legacy). Calculates precise buy orders across six brokerage accounts based on target allocation percentages and real-time market prices, with both ETF (whole-share) and mutual fund (dollar-based) order calculations. Includes IPS-anchored presets, AI-powered market recommendation with explicit flagging when a recommendation deviates from the governing IPS target, tier-aware drift analysis, and a Capital Stack dashboard that rolls positions up by tier and entity.
Features
- Live market prices via Yahoo Finance (auto-refreshed)
- New Investment mode with buy order calculations
- Portfolio Rebalancer with tier-aware drift thresholds and sell/buy orders
- AI Market Recommendation with real-time reasoning, anchored to the tier IPS target
- IPS deviation flag with Current / IPS / AI side-by-side and explicit acknowledgment
- AI Rebalance Analysis with tax-aware and tier-aware strategy
- Strategy presets: Aggressive, Moderate, Conservative, S&P 500
- IPS-anchored presets: Strategic Balanced, Legacy Growth, IPS Auto
- Capital Stack dashboard — three-tier household rollup with entity subgrouping and liquidity ladder
- Copy to clipboard and print-friendly output
Accounts & Capital Tiers
- Howell Holdings LLC (Schwab) — Strategic / Strategic Capital Reserve
- Schwab Solo 401(k) — Strategic / Retirement
- Fidelity Trust — Legacy / Trust corpus
- Fidelity Roth IRA — Strategic / Retirement
- Wells Fargo Roth IRA — Strategic / Retirement
- Fannie Mae 401(k) — Strategic / Retirement (pending rollover)
How to Use
- Sign in with your email and password.
- Choose New Investment to calculate buy orders for new cash, or Rebalance Portfolio to analyze drift on existing holdings.
- Select a brokerage account and enter amounts or current holdings.
- Set allocation manually, choose a preset, or click AI Market Recommendation.
- Review orders and click Copy or Print.
Tax-advantaged accounts get full rebalance recommendations; taxable accounts prefer contribution-based correction. The IPS governs and the AI advises: Strategic and Legacy tiers carry their own drift thresholds, and Legacy smallcap + emerging-markets exposure is capped at 25% combined absent an explicit Managing Member determination.
Launch Rebalancing Calculator →Management services agreement reporting system for 52nd Street Capital Group. Generates structured invoice receipts and financial reports (monthly, quarterly, annual) with revenue, COGS, operating expenses, payroll, and auto-calculated trial balances. Supports file uploads for supporting documentation and email distribution to configured recipients.
Features
- Dashboard with receipt, report, and file counts
- Invoice receipt creation with auto-numbering and line items
- Monthly, quarterly, and annual report generation
- Revenue, COGS, operating expenses, and distribution tables
- Payroll tracking (W-2 count and processor)
- Auto-calculated trial balance with imbalance warnings
- Document upload with drag-and-drop
- HTML preview and print-ready output
- Email distribution to configured recipient list
- AI report generation from uploaded source documents (P&L workbooks, statements, PDFs) via Claude synthesis, run as a background worker
- Config-driven GL classification: entity-aware member-distribution vs owner-draw, from msa_entities + msa_gl_classifications
- Cross-report business view: revenue, gross profit and margin trended across every published monthly report
- Scheduled automation: bi-weekly invoice receipts (15th + last day, $5,000 base management fee) and monthly report drafts
- Rendered PDF attached on every send path, plus a test-send mode that leaves delivery state untouched
Report Types
- Invoice receipts (1st-15th and 16th-End periods)
- Monthly MSA reports
- Quarterly MSA reports
- Annual MSA reports
How to Use
- Sign in with your email and password.
- Use Create Receipt to generate a new invoice. Select the period, add line items, and save.
- Use Create Report to build a financial report. The trial balance calculates automatically.
- Upload supporting documents in the Files tab using drag-and-drop.
- Use Preview to review formatting before finalizing.
- Configure email recipients in Settings, then mark reports as Sent to distribute.
Trial balance must be balanced before a report can be finalized. Status flow: Draft → Sent → Archived.
Launch MSA Reporting →Comprehensive bookkeeping and tax preparation system covering every HLG entity plus the Howell family's personal household. An AI-powered document processing pipeline analyzes uploaded financial documents, extracts transactions, generates financial statements, and maintains balanced books. Runs daily or on-demand. Each entity is configured with its tax form (Form 1065, 1120-S, 1041, 990-PF, or 1040), entity type, EIN, address, and bank accounts.
Features
- AI document processing pipeline (daily automated or on-demand)
- Multi-entity management across all 21 active entities — operating LLCs, sub-holdings, trusts, foundations, and the Howell Family personal household (Form 1040 MFJ)
- Drag-and-drop document upload with auto-categorization
- Automated transaction extraction from bank statements and invoices
- Auto-generated income statements, balance sheets, and trial balances
- Tax preparation workbook with year selector and per-entity tax-form routing (1065, 1120-S, 1041, 990-PF, 1040)
- Trial balance with auto-calculation and balance warnings
- PDF export and multi-entity ZIP download
- Nightly bridge to HLG Cash Flow Pipeline — finalized AI-confirmed transactions (status=filed, confidence high/medium) mirror into
cf_ledgerevery day at 06:30 UTC; edits and reversals post immutable correction rows (FR-5.6) - Brokerage statement bucket consumed by Master Banking (account-number scans) and Wealth Management (holdings extraction)
- Per-account reconciliation of multi-account statements — each account balanced independently, identical lines no longer collapsed across accounts
- Extractions verified against the statement's own printed totals before transactions are booked
- Document period derived from the statement's printed statement period, not inferred from transaction dates
- Re-filing a document moves the existing record rather than creating a duplicate
- Daily EMS entity sync (05:30 UTC) creates, updates and retires entities, propagating EMS dissolutions into bk_entities
Supported Entities
- The Howell Legacy Group (Statutory Trust · 1041)
- Howell Holdings LLC (Corporate Trustee · 1065)
- AITCH Holdings LLC (Operational Holding · 1065)
- AITCH Enterprises LLC (Primary Operating · 1065)
- AITCH Technologies LLC · AITCH IP Holdings LLC · AITCH Land Group LLC
- 52nd Street Capital Group LLC · 52nd Street Capital Retirement Trust
- H&L Venture Group LLC · Welannee Blvd Family Estate LLC · Haleyberry Ave Property LLC · Johnson Ct Property LLC
- Nevada Investment Holdings · Nevada IP Licensing · Nevada Venture Capital (dissolved 2026-08-13)
- 360 World Music LLC · Global Music Group L.L.C.
- Today's Child Foundation · Ifoma Foundation · AITCH Conservation Foundation (501(c)(3) · 990-PF)
- Howell Family Personal household (Form 1040 MFJ)
How to Use
- Sign in with your email and password.
- Upload bank statements, invoices, and receipts via the Upload tab.
- Click Process Documents on the Dashboard to run AI analysis, or wait for the daily 6 AM automated run.
- Review extracted transactions and auto-generated financial statements.
- Navigate to Tax Prep to review the auto-populated workbook for each entity.
- Verify the Trial Balance is balanced, then export the workbook as PDF.
The AI pipeline processes up to 20 documents per daily run. Documents are archived after processing.
Launch Enterprise Bookkeeping →Full lifecycle patent management for AITCH Technologies' portfolio of sustainable-technology patents. The platform tracks every application from idea through grant, captures every USPTO correspondence as it lands, and produces complete, USPTO-compliant submission packages — both responses to incoming Office Actions and Notices, and new patent applications drafted from a plain-English invention description. Every package self-validates against the same checks USPTO would run (37 CFR 1.71-1.77 sections, 1.72(b) abstract, 1.75 claim form, 1.84 drawings, 35 USC §112(a) written description) and never ships unless every fatal check passes; failed artifacts are auto-regenerated. Forms are pulled live from uspto.gov so you file with the latest revision. The inventor is the final reviewer — content only (do the claims read on the invention, do the drawings show the invention) — never compliance.
Features
- AI-Drafted New Filing wizard — paste a paragraph of invention description, get back a complete utility application: specification (Field, Background, Summary, BDD, Detailed Description), 1-3 independent + 12-20 dependent claims, abstract, USPTO-compliant drawings, and every required form pre-filled (AIA/15, AIA/01, SB/17, SB/15A) — bundled as a single ZIP for Patent Center upload
- USPTO compliance gate — every bundle (Reply or New Filing) runs through
lib/uspto-validator.jsbefore it ships. Validates 37 CFR 1.71-1.77 sections + paragraph numbering, 1.72(b) abstract length / single-paragraph rule, 1.75 claim balance and dependency targets, 1.84 drawing sheet headers + reference-numeral placement, and 35 USC §112(a) written-description support. Failed drawings auto-regenerate up to two times; if the gate still fails, the package refuses to ship rather than handing the inventor a non-compliant ZIP. - AI-Powered Reply Drafter — Claude reads any USPTO Office Action or Notice (text or scanned PDF), identifies every rejection / objection / cure with severity and statute, drafts the MPEP-compliant response, and produces the same kind of submission ZIP with the response document plus every required form pre-filled (AIA/22 extension, SB/17 fee, SB/15A, etc.)
- Filing History — every document from every prior filing (356 PDFs across all 7 active applications) is in the portal's storage and listed on each patent's detail panel by date, with one-click signed-URL downloads
- USPTO-compliant drawings (Rev 4 build spec) — five-scenario taxonomy backed by the aitch-prosecution-tools Python toolkit (reportlab + Pillow + pdftoppm). Scenario 1 (original drafting):
build_original.pyassembles figures from a per-application inventory. Scenario 2 (extract-and-overlay): extracts originally-deposited drawings from the Patent Center bundle at 200 DPI and overlays the universal §9 header, preserving line work pixel-for-pixel. Scenario 3 (late-deposit generation): Claude Opus 4.7 authors a per-figurebuild_fig_<app>_<N>.pywith a mandatory source-attribution docstring; nothing executes until a reviewer approves it (recorded inprosecution_drawing_reviews). Scenario 4 (late-deposit existing): reformats an existing drawing to USPTO §1.84 spec viabuild_drawings.py. Scenario 5 (continuation drafting): combines Scenarios 1-3 for continuation/divisional applications. The TerraGrid 19/306,897 response (Apr 28, 2026) is the validated reference case — Scenario 2 + Scenario 3 under Option II election — with a regression test pinning the 10-sheet replacement-drawing PDF byte-for-byte. - Live form pre-fill — the platform fetches each USPTO form from its stable URL, caches with 24h TTL + If-Modified-Since revalidation, and uses pdf-lib to fill AcroForm fields with applicant data from
applicant_profiles(Customer Number, inventor, residence/mailing address, micro entity status, signature block) - IMAP poller reads
patents@aitchtechnologies.comevery 15 minutes for USPTO Patent Center courtesy emails and creates pending correspondence rows automatically with computed statutory + extension deadlines - Plain-language guidance per USPTO event code (NT.INC.REPLY, CTNF, CTFR, N561, ABN, MN/=., etc.) — what the notice means, what's at stake, the cure period
- Patent Center deep links from every correspondence row, upcoming-deadline widget, and IFW history view
- Sector breakdown (Construction, Agriculture, Energy) and pre-filing through grant pipeline
- Daily auto-sync against USPTO Open Data Portal once each application crosses its 18-month publication date
- USPTO Filing Audit Gate registry — 49 machine-readable gates (categories A–S), every gate fatal with no operator override, run against every artifact in a bundle; gate S1 re-verifies the encoded requirements against live 37 CFR via eCFR each build and refuses to certify on drift
- Self-improving audit loop — each defect extracted from an Office Action / Notice maps to an enforced gate, or, where none exists, synthesizes a proposed fatal gate and a failing test fixture so the coverage gap stays visible in CI until implemented
- Entity-status derivation — small / micro / undiscounted status is always derived from the documentation of record (Patent Center sync, a 37 CFR 1.27/1.29 statement, the paid fee-code prefix, Notice language), never hand-set; a silent or conflicting record hard-fails to manual review
- Final-artifact certification — the assembled package is rendered and OCR'd, reconciling every replacement drawing sheet against source; a stale “Sheet N of M” legend or blank sheet fails the build, and validation runs on the final rendered artifact rather than the source text layer
- Certification versioning — each package is stamped with the standard in force when it was built; when a new control raises the bar, older packages drop out of filing-ready rather than staying selectable
Submission Package Contents
- New Filing: SPEC.pdf · CLM.pdf · ABST.pdf · DRW.pdf (Scenario 1: per-figure Claude-authored build_fig scripts run via the prosecution-tools toolkit and assembled by build_original.py) · AIA/15 · AIA/01 · SB/17 · SB/15A · README
- Reply: response.pdf · AIA/22 (if past statutory date) · SB/17 fee · SB/15A micro-entity certification (only when a fresh 1.29 certification is required — a new filing or continuation/divisional/CIP/CPA/reissue; a reply in the same pending application needs none) · replacement DRW.pdf via the prosecution-tools pipeline (extract-and-overlay or hybrid late-deposit per the OA scenario) · §1.182 petition + Statement of No New Matter when a generated figure is filed · README
- Bundled as ZIP, named by attorney docket + date, ready to drop into Patent Center
- Manifest carries a
uspto_validationrecord with every check that ran, every warning, and the timestamp the gate passed. The README inside the ZIP enumerates what the platform verified (not what the inventor must check).
Status Pipeline
- Pre-Filing · Filed · Preexam · Docketed · Examination · Allowed · Granted
How to Use
- Sign in with your email and password.
- The Dashboard shows portfolio summary, pending actions, and upcoming deadlines (driven by the Correspondence table).
- Filing a new application: go to Submissions → click ✨ AI-Drafted Filing → pick a pre-filing entity from the dropdown → choose application type (Utility / Provisional / Design) → paste your invention description (500-2000 chars is the sweet spot) → optional Claim 1 concept and drawing notes → Draft Application with Claude. Wait 3-5 min while the system drafts the spec, generates compliant drawings, validates the package against every USPTO rule, and pre-fills every USPTO form → Download ZIP. Your job is content review only — confirm the claims read on the invention, the drawings depict the geometry correctly, and the Detailed Description tells the truth about how it works. Leave per-artifact comments and the tool regenerates the affected pieces. Sign AIA/01 in Patent Center on filing day.
- Responding to a USPTO Notice or Office Action: the IMAP poller logs the courtesy email automatically; open the Correspondence tab, find the pending row, click ✍ Draft Reply → pick the source PDF (it's already on file from the historical import) → Analyze with Claude. The wizard returns a structured item list, MPEP-format response draft, and the full submission ZIP with response + all required forms pre-filled — every artifact passes the compliance gate before the ZIP exists. Confirm the response addresses each rejection, sign, file.
- Use ✓ Resolve on a correspondence row once the response has been filed in Patent Center; the row moves out of Pending Actions automatically.
- Browse the Patent Portfolio, click any patent for full metadata + Filing History (every document on file with one-click download).
- Click Sync with USPTO on the Dashboard to refresh examiner / art unit / event log from the public ODP API for any application past its 18-month publication date.
Pending Actions and Upcoming Deadlines are driven by the Correspondence table, which combines IMAP-ingested USPTO emails, manual entries, and the daily ODP sync — deduped on (application, event code, mailroom date). Forms are fetched live from uspto.gov/sites/default/files/documents with 24h cache so you always file the latest revision USPTO has published. Every package passes the USPTO compliance gate before it ships; the inventor is the final reviewer for content accuracy only.
Operationalizes the Howell Legacy Group cash flow model across every active and pending entity in the cascade. Automates the 30/40/20/10 allocation framework at AITCH Holdings, models the 52SC fixed-retainer MSA waterfall, tracks intercompany loan receivables, and enforces the active Business Rules from PRD v2 (including the Kenneth Lynch 33% exclusion and the Welannee Boulevard capex exclusion). The distribution ledger is live and is now populated nightly from the Enterprise Bookkeeping platform.
Features
- Dashboard with 52SC waterfall and AITCH Holdings allocation
- Entity registry with cascade tiers and pipeline-inclusion flags
- Versioned configuration with effective dates (MSA fee, W-2, allocation %)
- 30/40/20/10 compliance check with 1% tolerance (BR-01)
- 52SC shortfall detector with minimum-MSA-to-breakeven (BR-06)
- Intercompany loan receivable tracker with AFR interest accrual
- Bookkeeping bridge — finalized
bk_transactionsmirror intocf_ledgernightly at 06:30 UTC with provenance columns (source,source_bk_txn_id) and immutable correction rows on edits/reversals - Distribution ledger with K-1, MSA, rental, DSCR, and operating income/expense kinds — feeds Wealth Management's 12-month forecast
- Daily alert scan at 07:00 UTC consumes freshly-bridged data; daily backup at 08:00 UTC
- Immutable audit log on every data change (NFR-03)
Business Rules Enforced
- BR-01 30/40/20/10 split at AITCH Holdings
- BR-02 Kenneth Lynch 33% excluded from all calculations
- BR-03 52SC fixed-retainer MSA ($10k/month, no AUM/performance/transaction fees — retired 2026-04-24)
- BR-04 W-2 + employer FICA waterfall
- BR-05 Cascade flow sequence
- BR-08 Welannee Blvd excluded from pipeline
- BR-13 Foundations excluded until revenue confirmed
- BR-14 IRC §706(c) 2026 period split
How to Use
- Sign in with your email and password.
- Review the Dashboard for the live 52SC waterfall and 30/40/20/10 allocation.
- Use the Configuration tab to update MSA fee, H&L annual net, and any allocation parameters. Changes are saved with effective dates.
- The Entities tab lists the full registry with tier, bank, income type, status, and pipeline-inclusion.
- Active warnings (shortfalls, DSCR gaps, allocation drift) appear on the Dashboard and in the Alert Center.
Distribution ledger and Bookkeeping bridge are live. Audit history is queryable at /api/bk-bridge?status=1&days=8. Validated entity-rename fixes can be submitted via /api/bk-bridge-fix.
Authoritative source of truth for all HLG entities. Upload legal documents (CP-575 EIN letters, Delaware formation certificates, operating agreements, board resolutions, good standing certificates, 501(c)(3) determinations, SAM.gov registrations, banking resolutions, amendments, trust agreements) and Claude AI extracts structured data with field-level confidence scores. Low-confidence extractions route to a human review queue; confirmed data populates the entity registry, compliance calendar, and document vault with a full audit trail.
Operator Features
- Dashboard with entity count, doc completeness, review queue, and 30-day deadlines
- Entity registry with EIN masking, completeness score, compliance status
- Live four-tier cascade org chart with BR-09 charity independence
- Drag-and-drop upload with in-browser PDF/DOCX text extraction
- Claude Sonnet 4.6 extraction for 12 document types with confidence scoring
- Two-panel extraction review (original document + extracted fields)
- Human review queue for fields < 0.85 confidence (BR-04)
- Compliance calendar with DE franchise tax + Form 990 auto-seeding
- Document vault with search, type filter, and versioning (BR-03)
- Immutable audit log on every write (NFR-04)
- CSV and printable PDF reports (entity summary · doc inventory · compliance deadlines · audit log)
EMS v1.1 Canonical Layer (Spec §16.1 – §16.3)
- 101 documents ingested with SHA-256 verification across 16 canonical classes (GOV-TRUST, GOV-OA, GOV-OA-AMEND, MSA, IP-LICENSE, REGISTRY, etc.)
- em_entities_v1 published interface (Estate Data Contract HLG-PLT-2026-002): a versioned, banking-free view downstream platforms read instead of copying entity data — current consumers include ILIP and the Music Rights Platform
- Entity provenance fields separating a company's origin from its Delaware registration (original_formation_date, original_jurisdiction, original_legal_name, domesticated_on, name_changed_on) and the registered DBA as structured data — e.g. GMG organized in Virginia 2014-07-28, re-registered as a Delaware LLC 2025-04-17, EIN 45-1675784 retained, DBA “GMG”
- 968 signatory rows extracted from canonical OA + Trust v12 lineage
- 26 ILIP Source Registry bindings (25 ACTIVE; 1 deprecated rollup) — source_id resolves to current EMS document/snapshot
- Amendment lineage: Trust v12 four-document chain (initial → DocuSign re-baseline → Amendment No.1 → Amendment No.2) with point-in-time resolution
- HLG-BANKING-REGISTRY LIVE-INTEGRATION (Plaid-class) across Fidelity / Schwab / Wells Fargo Commercial / Truist / US Bank
- SAM.gov LIVE-INTEGRATION: daily sync (06:15 UTC) against the SAM.gov Entity Management API keeps each entity's UEI / CAGE / registration status / expiration current and seeds a sam_registration compliance item; alerts 60 days out and on any status drop or recorded exclusion
- 96-entry tamper-evident hash chain (Spec §6.1); per-document verify endpoint
- 180 compliance obligations across 9 categories projecting 24 months forward (annual reports, BOI/CTA, tax returns, Form 990, MSA renewals, registered-agent renewals, foundation distribution + board attestation)
- Music-industry identifiers held alongside the legal/tax IDs for publisher/label entities: IPI/CAE, BMI publisher account and PRO affiliation (360 World Music — IPI 00782057821, BMI 1666683; GMG BMI-affiliated)
- Cancellation tracked as a distinct pending state — eight Delaware entities' cancellations filed 2026-08-13 stay live until the state confirms — with a separate dissolution lifecycle (date, evidence, state filing, final federal-return / franchise-tax status) and a gaps queue for dissolved entities missing either
- 90/60/30/7-day alert tiers; Group COO manual override workflow
- Litigation Hold workflow: scope-defined holds lock matching documents; counsel-only release; chain-of-custody log
- Evidentiary Output Package: signed URL + amendment lineage + custody log + hash anchor + Sponsor certificate
- Authority Cascade trigger emits to ILIP webhook on amendment ingest (Spec §4.4)
Business Rules Enforced
- BR-01 Source of truth (CP-575 for EIN, DE cert for file#) — conflicts require resolution
- BR-02 No fabrication — missing fields return null + 0.0 confidence
- BR-03 Immutable documents with version history
- BR-04 <0.85 confidence routes to human review queue
- BR-05 Cascade hierarchy enforcement (Trust → Trustee → Holding → Ops)
- BR-06 Compliance deadline tracking per entity
- BR-07 Completeness scoring across required documents
- BR-08 Sensitive data (EIN, account) masked in UI
- BR-09 Foundations shown as independent charities
- BR-10 Audit trail on every write
Source Registry Resolution API
GET /api/ems-resolve?source_id=<id>— current operative document or live snapshot?as_of=YYYY-MM-DD— point-in-time resolution (audit reproducibility Spec §23 / §45)?op=chain— full amendment lineage?op=fetch&id=<doc_id>— 60-second signed URL?op=verify&id=<doc_id>— recompute + compare SHA-256POST {op:'refresh_live', source_id}— trigger live-integration snapshotGET /api/ems-compliance?op=calendar|alerts|obligations— Phase 2 compliance readsPOST /api/ems-compliance {op:'hold_create'|'hold_release'}— counsel-only litigation holdsGET /api/ems-compliance?op=evidentiary_package&document_id=<id>— discovery-ready bundle- Outbound webhook: ILIP receives SOURCE_REGISTRY_DOCUMENT_CHANGED + AUTHORITY_CASCADE events via HMAC-SHA256 signed POST
How to Use
- Sign in with your email and password.
- Browse the Entities tab to see the full HLG registry seeded from the Cash Flow Pipeline canon.
- Go to Upload, pick the entity and document type, then drop the PDF / DOCX / image. Text is extracted in your browser, Claude extracts structured fields, and the review pane opens automatically.
- Correct any fields flagged amber or red, then click Confirm & Apply to Entity to write the extracted values back to the entity record.
- Use the Compliance tab to mark filings complete — next due dates auto-calculate for recurring items.
- Low-confidence items gather in the Review Queue. Items older than 48h trigger a dashboard alert.
EMS is the system of record for all entity legal names (CP-575 source) — every other platform reads the published em_entities_v1 interface (Estate Data Contract HLG-PLT-2026-002), which deliberately omits banking columns. Currently tracking 30 active entities across the four-tier cascade (Trust → Corporate Trustee → Operational Holding → Operating Subsidiaries / Sub-Holdings / Foundations). The EMS v1.1 canonical layer (schema ems, 13 tables) is the document repository ILIP reads from; the two systems are co-equal subsystems per Spec §2.1.
Deterministic 9-layer compliance audit engine for governance documents, transaction packets, and lending packages. Every audit cites pinned source_versions + rule_versions + EMS document IDs so any run can be replayed years later with byte-identical findings. Built as the structural fix for stale-citation audit failures (Howell Detailing SBA Microloan, April 2026, ORC 1706.07 vs 1706.09). Co-equal subsystem to EMS — ILIP renders compliance judgments, EMS supplies the documents.
Audit Engine
- 9-layer hard-gated audit per Spec §2.1 (Source-of-Truth → Statute → Filing → Enforceability → Reconciliation → Underwriting → Governance → Formatting → Tone)
- 50 sources + 78 active rules (23 deprecated) in the canonical registry, each rule pinned to a versioned source
- Registry scoped to the entity footprint (Delaware, Nevada, Florida, Virginia): 22 out-of-footprint rules for Ohio, California, New York and Texas retired; their sources retained as dormant and verified yearly rather than cascading daily
- 6 deterministic evaluators (NUMERIC_RANGE, PRESENCE, ABSENCE, CITATION, ATTESTATION, CROSS_DOC) + NUMERIC_CALC for DSCR/leverage
- Layer-2 DISQUALIFYING blocks higher-layer rule execution (Spec §2.2 hard-gate)
- Document upload + classification (TXT/PDF/DOCX up to 5MB) auto-fires audit when document_class inferred
- Audit packages (up to 25 docs) with cross-document reconciliation (loan amount / guarantor / collateral / banking / insurance)
- Reference case: Howell Detailing SBA Microloan passes 9/9 acceptance with reproducible manifest_hash
EMS Integration (Spec §14, §33)
- Every HLG-* source_id in the rule corpus resolves at audit time via EMS Resolution API — no static fallback
ems_resolution_audit_linkstable joins every audit to the exact EMS document_id + SHA-256 it cited- Inbound webhook
POST /api/ems-events-ingestverifies HMAC-SHA256 (EMS_WEBHOOK_SECRET) - Entity sync mirrors EMS music identifiers (IPI, BMI publisher ID, PRO) into
ilip.entities— 360 World Music carries IPI 00782057821 + BMI 1666683; Global Music Group BMI-affiliated - Owns the HLG-PLT-2026-002 Estate Data Contract: publishes tenant-gated views
royalty_streams_v1+royalty_periods_v1, consumed by the Music Rights Platform for income reconciliation - Royalty registry seeded from authoritative catalog exports: 45 earning-rights streams (34 SoundExchange master under Global Music Group, 11 BMI publishing under 360 World Music); 42 of 45 tie to the music catalog by ISRC/ISWC
- AUTHORITY_CASCADE / SOURCE_REGISTRY_DOCUMENT_CHANGED events automatically invalidate cached resolutions
- Per-audit_id resolution cache ensures deterministic resolution across all rule evaluations within a run
- REQUIRE_EMS env var available for fail-closed deployments (default: best-effort with error logging)
Constitutional Controls (Spec §30)
- Append-only audit trail with DB-trigger-enforced immutability (no policy bypass)
- Stale-law quarantine: rules citing quarantined sources SKIP with constitutional reason
- Source refresh worker (ecfr.gov verified end-to-end) — polite HTTP, SHA-256 over response body
- No LLM in the deterministic path — Claude Opus 4.7 only in the conversational layer (chat-first UI)
- Grounded Response Contract per UI Spec §3.2 (mode pill, citation block, tool trace, confidence, verification badge)
- Litigation hold workflow (Subsystem L): counsel-only create/modify/release; chain-of-custody log; held docs cannot be archived
- Escalation engine (Subsystem K): human-review-required findings route to Sponsor + Counsel with SLA
Document Generation & Certificates
- 5 Phase-1 templates (OA Amendment, MSA Commercial, Board Resolution, MI Assignment, Foundation Grant Agreement)
- Pre-delivery audit gate: DISQUALIFYING blocks generation; MATERIAL requires explicit acknowledgement
- Institutional-grade DOCX output (Times New Roman 11pt body / 14pt headings, 1in margins, auto-appended audit-trail page)
- 5 certificate types (COMPLIANCE / RELEASE_CLEARANCE / FILING_READINESS / LENDER_READINESS / GOVERNANCE_INTEGRITY) with per-type preconditions
- Cryptographic chain on certificate issuance (chain_seq + chain_prev_hash + payload_hash)
- Bearer-token API at
ilip-platform-api.netlify.app:/api/audit,/api/audit-package,/api/certificates,/api/generate,/api/chat,/api/holds,/api/escalations,/api/ems-resolutions,/api/royalty-streams
How to Use
- Open the platform — the chat-first UI is the default landing per UI Spec v1.0.
- Submit a document, paste text, or attach a PDF/DOCX. The agent classifies, calls the audit engine, and returns findings layered by severity.
- For multi-document packets (lender packages, governance refresh bundles), use Submit Package — cross-doc reconciliation rules fire automatically.
- Review the citation block under each finding: every rule names its authority_source_ids; EMS-bound sources show the resolved document_id + SHA-256.
- For evidentiary preservation, hit
/api/holdsto create a counsel-issued litigation hold scoped by document_class / entity / date range. - Switch to Operator UI (/operator.html) for power-user views: Submit Audit, Submit Package, Recent Audits, Entity Registry.
ILIP is co-canonical with EMS. Neither operates without the other — ILIP audit runs halt with SOURCE_UNAVAILABLE if EMS is unreachable; EMS continues to ingest and buffer events until ILIP recovers (Spec §14.3 failure isolation). All audits since 2026-05-11 cite live EMS document state via ems_resolution_audit_links — point-in-time replay returns byte-identical findings.
Board-member operator console for The Howell Legacy Group. Surfaces resolutions, meetings, initiatives, financials, grants, patents, compliance calendar, governing documents, and audit findings — all entity-scoped and role-gated. The compliance and documents views pull live from EMS (canonical governing-doc repository) and ILIP (deterministic audit findings); board members can review the underlying OAs/amendments/501(c)(3) packages inline and complete reviews without leaving the calendar.
Pages
- Dashboard — pending votes, recent resolutions, upcoming meetings, compliance summary, financial snapshot
- Resolutions — board votes with quorum + outcome tracking
- Meetings — schedule, attendance, minutes, agenda items
- Initiatives — active board initiatives with status + due date
- Documents — Governing documents (EMS v1.1) + Board working documents (Confluence) per entity
- Financials — HLG rollup + per-foundation lines
- Grants — foundation grant pipeline + award tracking
- Patents — AITCH Technologies patent maintenance + USPTO status
- Compliance — Form 990, Delaware annual report, SAM.gov renewal, board-meeting and governance obligations, MSA renewals + live ILIP findings
- Directory — board members + trustees by entity
- Admin — seeding tools (admins only)
EMS + ILIP integration
/api/documents?entity=…mergesgoverning_documents(EMS v1.1 canonical) withboard_documents(Confluence working docs)/api/documents/ems/:doc_id/urlreturns a short-lived signed URL via the EMS Resolution API/api/compliancemerges seeded board obligations with live ILIP escalations (DISQUALIFYING + MATERIAL); ILIP findings sort first within urgency bucket- Inline "Review documents" expander on each compliance row loads the entity's current OAs / amendments / foundation packages / MSAs and opens each via signed URL — board members complete reviews without leaving the calendar
Access Control
- Supabase Auth (email + password, magic-link option)
board_members+board_entity_rolestables drive RLS — every fetch is scoped to the caller's entities- 4-hour inactivity timeout; JWT auto-refresh in-session
- PLATFORM-manager and HLG-trustee roles see all entities; other roles are entity-scoped
Notifications
- compliance-alert-check.js — daily 06:00 UTC scan; honours each obligation's own
alert_window_daysas both floor and ceiling, escalating across 180/90/60/30-day tiers, and flips upcoming→overdue when a due date passes - meeting-reminder-check.js — pre-meeting attendance reminders
- voting-deadline-check.js — alerts when a resolution's voting deadline is approaching without quorum
Board is a co-equal consumer of EMS + ILIP. Both upstream platforms must be reachable for full functionality; the Board UI falls back gracefully (shows Confluence-only documents and seeded-only compliance) when an upstream is degraded.
Launch Board Platform →Authoritative banking registry for all HLG entities — full account numbers and ABA routing numbers across Fidelity, Charles Schwab, Wells Fargo Commercial, Truist, and US Bank. Sensitive fields are masked by default (last-4 only) and a Reveal action requires a written reason that is logged to an immutable audit trail with IP and user agent. Account numbers are populated by scanning the bank-statement PDFs already stored in the Enterprise Bookkeeping platform with Claude Sonnet 4.6 — proposals are reviewed and confirmed, never silently written.
Features
- Institution summary dashboard with per-bank account counts
- Full account registry seeded from the canonical PRD — masked by default, reveal-on-demand
- Masked account & routing numbers by default (last-4)
- 30-second timed reveal with reason + actor + IP audit log
- Claude statement scan against bookkeeping-docs bucket
- Side-by-side proposal review before writing to the registry
- CSV and printable PDF exports (masked by default)
- Gated FULL-number export requiring reason + actor
- Reveal log and audit log viewers
Institutions Covered
- Fidelity Investments — Trust custody
- Charles Schwab — Corporate trustee + Solo 401(k)
- Wells Fargo Commercial — Primary operating + real estate
- Truist Bank — 52SC, H&L operations, GMG
- US Bank — all three 501(c)(3) public charities
How to Use
- Sign in with your email and password.
- Browse the Accounts tab — all numbers are masked by default.
- To see a full account or routing number, click Reveal and supply a written reason. The reveal lasts 30 seconds and is logged.
- Go to the Scan Statements tab, pick an entity, and run the scan. The system pulls its latest bank-statement PDFs from the bookkeeping bucket, Claude extracts full account + routing details, and proposals appear for you to confirm before writing.
- Check the Reveal & Audit Log for a complete, immutable history of every sensitive access.
Classified: Do not transmit via unencrypted channels. Full-number exports require an explicit reason written into the audit log.
Launch Master Banking →The family office wealth platform. Bookkeeping is the canonical source of truth: every brokerage and bank statement that lands in the Enterprise Bookkeeping platform is parsed by Claude into structured holdings and cash balances, and an hourly wealth-sync projects those into the dashboard so investments, cash on hand, and per-entity NAV stay current automatically — no manual entry. Real-estate values refresh through the hlg-property-valuation tool: an inline Claude web-search synthesis that reads same-street comps, recent sales, Redfin/Zillow estimates, and county records, then applies registry-tracked encumbrance discounts (conservation easements, code-enforcement liens, etc.) before writing audit rows to hlg_property_valuations. A persistent data-freshness banner at the top of every page reports when each pipeline last ran and surfaces any account where bookkeeping is missing a statement upload or extraction. Claude Opus 4.7 drives what-if scenarios against the full current state, including the active Business Rules from the Cash Flow Pipeline.
Features
- Data freshness banner — pinned below the topbar; one colour-coded pill per data source (bookkeeping sync, latest statement processed, NAV snapshot, live prices, property values), plus a red pill listing any confirmed bank account missing a statement; auto-refreshes every 60s and exposes a one-click "Refresh now" button that fires every pipeline in parallel
- Bookkeeping → wealth sync (hourly) — pulls
investment_holdingand closing-balance rows from the latest processed bk_document for every entity and projects them intowm_holdings+wm_valuations; uses filename role-suffix matching ((OPS), (PR), Checking, Savings) so each fi_account is paired to its own statement - Cash on Hand dashboard tile — total liquid cash across every confirmed bank account at every entity (operating LLCs, foundations, retirement trust, personal); per-account breakdown rolls up by entity through the wealth map
- Property auto-valuation — Claude reads the agent's own web_search results across each subject's same-street Redfin/Zestimate comps, recent sale prices, county records, and listings, then synthesizes a point estimate with 0.7-power sqft scaling against the closest comp. Registry-tracked encumbrances (conservation easement, code-enforcement lien, mortgage) discount the pre-encumbrance value. Every refresh writes a verbatim audit row (sources, snippets, synthesis notes) to
hlg_property_valuations; the latest row per property projects intowm_valuationsfor the dashboard. Run inline on demand; weekly cron is a best-effort fallback. - Global Wealth Map — cascade tree with rolled-up NAV per entity; BR-02 applies 67% on H&L upstream
- Portfolio Overview — asset-class allocation bars + top positions with gain/loss
- Live market-price ticker (every 15 minutes) for public-ticker positions on top of the daily statement-driven base
- Managers — roster + performance snapshots (YTD/1Y/3Y + fees)
- Cash Flow Forecast — 12-month projection from cf_config + cf_ledger (MSA, AUM, salary, FICA, K-1 distributions, 30/40/20/10 split)
- What-If Scenarios — Claude analyzes any proposed action against NAV, liquidity, allocation drift, tax, and BR compliance
- Rebalancer deep-link — hand the current top-10 positions straight to the Rebalancing Calculator
Integrations
em_entities— entity registryfi_accounts— banking accounts from Master Banking (read by wealth-sync to identify which accounts to look up)bk_documents.ai_analysis— bookkeeping's AI extractions are the canonical source for holdings and cash balancescf_config/cf_ledger— Cash Flow Pipeline (ledger now populated nightly from the Enterprise Bookkeeping bridge)cf_intercompany_loans— AITCH Land Group receivableswm_sync_runs— singleton-per-pipeline ledger; powers the freshness banner- Anthropic API (Claude Opus 4.7 + web_search) — drives property valuation refresh and what-if scenarios
- Portfolio Rebalancer — deep-link with holdings query param
How to Use
- Sign in with your email and password.
- The freshness banner at the top of every page tells you at a glance when each data source last refreshed. Green = fresh; amber = aging; red = stale or attention needed (e.g., a confirmed bank account whose statement hasn't been uploaded to bookkeeping yet).
- The Dashboard shows Total Family NAV broken into Market Assets, Cash on Hand, Non-Market Assets, and 12-mo Projected Net.
- Open Holdings to see per-account positions; quantities + prices come from the most recent bookkeeping statement, refreshed hourly.
- Click Refresh now in the freshness banner to immediately re-run all three pipelines (bookkeeping sync, market-price tick, property revaluation) — useful right after uploading a new statement to bookkeeping.
- Check the Global Wealth Map for the entity cascade roll-up, and Portfolio Overview for allocation + top holdings.
- Review the Cash Flow Forecast — it pulls directly from the Cash Flow Pipeline's config.
- Use What-If Scenarios to test decisions before you make them. Describe the move in plain English (e.g., "Should we proceed with a $750k DE property acquisition?"); Claude returns a verdict plus NAV/liquidity/allocation/tax/risk analysis against your actual current state.
All data flows from bookkeeping. When a number looks wrong, the bookkeeping platform is where to fix it — uploading the missing statement (or correcting a prior one) cascades to wealth on the next sync. The red attention-needed pill in the freshness banner names the exact account and statement gap.
Launch Wealth Management →The controlling register for every musical composition and master recording under Group control, and the system of record for whether each asset is actually registered on every platform that pays it. Built in response to HLG-MUS-AUD-2026-001, which found eleven compositions and thirty-four masters exploited without the registrations needed to collect on them — two empty mechanical catalogs, six works with no publisher interest of record, twenty-nine masters with no underlying composition registered anywhere, and no recorded chain of title to any Group entity. Every one of those failures was invisible for years because nothing in the environment could detect an absence. This platform makes absence visible, blocks exploitation before the registration perimeter is complete, and makes an uncited financial figure impossible to store.
Features
- Registration perimeter engine — computes, per asset, its status across every platform of record: BMI, The MLC, Harry Fox, SoundExchange (Rights Owner and Featured Artist), AFM & SAG-AFTRA Fund, U.S. Copyright Office, PPL, sub-publishing, CMRRA, ISWC and ISRC. Every gap routes directly to the payload generator that closes it.
- Absence detection — the reconciliation engine asserts, for every asset and platform and period where activity is expected, that a statement line exists. A missing statement raises a CRITICAL variance unprompted. An empty publisher catalog produces no statement, and no statement previously produced no alarm; this is the control that ends that.
- Gate enforcement (SOP Gates 0–8) — gate order is enforced by database trigger, not by the interface. Gate 7 release authorisation is reserved to the CEO role by RLS policy and refuses to sign while the perimeter is incomplete or chain of title is unrecorded. Nothing without Gate 7 can appear in any export, registration payload or repertoire delivery pack.
- Citation constraint — a reported financial figure carries a NOT NULL foreign key to the royalty statement line it came from. There is no field in the schema in which an uncited number can be stored, and therefore no source from which one can be exported into a board memorandum, valuation or award submission. Statement lines are immutable once written; corrections supersede rather than edit.
- Import pipeline — parses BMI catalog exports, SoundExchange rights-owner catalogs, Harry Fox mechanical catalogs and Copyright Office records against their real formats. A header-only HFA export is recorded as an observation of zero registered works, not discarded as an empty file.
- Source-pluggable auto-reconciliation (Sync) — the registration findings derive from the platform of record, never toggled by hand. Upload a fresh BMI/Songview, SoundExchange or The MLC export and every registration-linked finding recomputes from a per-source snapshot — newly-assigned ISWCs and MLC song codes are captured automatically, and each finding closes itself as the work is registered. F‑12 (missing ISWC), F‑13 (Pending Society Review), F‑03 (MANUSCRIPT publisher), F‑05 (masters with no composition), F‑02 (MLC registration) and others all track live off the source data. The snapshot swap is atomic and refuses a replace that would lose more than half a populated snapshot: an empty snapshot reads as “nothing outstanding” and would close every finding derived from it, so a failed upload can no longer present itself as a clean audit.
- Self-service exports (Export) — the HFA eSong bulk-upload workbook (.xlsx), the HFA CWR 2.1 registration file (.V21), and a filterable catalog report (by artist, registration-ready, 360-published) generated on demand and downloaded in the browser. The eSong file is written into HFA’s own template rather than a workbook built from scratch — HFA rejects a file whose formatting has been altered — and the template is treated as the authority on column order, so a reordered template fails the export instead of putting values in the wrong columns.
- Registration files that refuse to be wrong — a split is a percentage of the writer’s share converted against each work’s own share basis (BMI account 945278 runs on 200 points, everything else on 100), so the same stored number cannot mean two things in two formats. HFA’s mandatory publisher number is always populated; titles beginning with a number are held back for manual registration because HFA will not take them in bulk; and a work whose writer shares do not total 100% is excluded with its reason stated rather than shipped. The CWR file is built to CWR11‑1494: ownership totals 100% per right per work within the specified .06% tolerance, publisher PR 50 / MR 100 and writers PR 50 / MR 0 per the manual’s worked example, and the generator refuses to emit a file that does not balance rather than transmitting a registration of record that does not add up.
- Split sheet generation (Split sheets) — the 360 World Music song split sheet pre-filled from the register: the work and its identifiers, the publisher block, and every writer with their PRO, IPI/CAE and percentage. Outstanding sheets are listed with the reason each is outstanding — no writer shares recorded, shares that do not total 100%, or documents that state conflicting splits — and can be produced singly or as a zip. A split sheet is a task attached to a work, not a gate on registering it: 360 publishes the catalogue structurally, so a missing sheet never withholds a work from its own publisher registration. Where the shares on record fall short of 100% the sheet prints them exactly as held, names the shortfall, and never adjusts them to close — that gap is why the sheet is going out.
- Interest provenance — every writer and publisher interest records how it is evidenced:
registered(it appears in the source-of-record export),contract(granted by an executed instrument),asserted(the Group’s position, not yet reflected at the source) orderived, with a required note on anything that is not registered. A drift view compares registered interests against the platform snapshot they claim to come from, so a finding closing at the source says something about whether the rights table actually agrees with it. Balance is computed on registered rows only, so an asserted position can neither make a work look balanced nor make one look broken. - Deezer ISRC enrichment — fills any missing recording ISRC from Deezer’s public catalog using conservative exact title-and-artist matching, so a same-named track by another artist is never stored.
- Party registry — one identity per party with a uniqueness constraint on issued identifiers. John Howell III (Dr. Jae) correctly holds both of his BMI writer name-numbers — IPI 00463346355 and 00463346551 — on a single party, so the same-person credit on DRUMLINE resolves to one writer rather than two unrelated people.
- Chain of title and §203 termination register — assignment instruments, §204(a) signed-writing evidence, §205 recordation numbers, and the termination calendar projected to the trust horizon with statutory heir position identified.
- Obligation watch — affirmative agreement obligations (Mood Media §7(d) repertoire delivery and equivalents) extracted by Claude, calendared, and raised as CRITICAL when a due date passes undischarged.
- Payload generators — HFA registration CSV in exact column order, MLC work registration, BMI publisher claim packs for unrepresented interests, repertoire delivery packs with covering notice and manifest, Copyright Office filing schedules with the §412 three-month window flagged.
- Findings tracker — the audit findings and the Phase 0–4 remediation roadmap, tracked to closure with evidence; the registration-linked findings recompute automatically from the per-source snapshots on every Sync refresh, so status reflects the platforms of record rather than a manual edit.
Scope
- 360 World Music LLC — BMI publisher IPI 00782057821, HFA P769TR
- Global Music Group L.L.C. — HFA P0987K, SoundExchange Payee 2177650133
- 29 works on the register, 11 of them registered compositions across BMI accounts 1666683 and 945278
- 35 master recordings
- 5 U.S. Copyright Office registrations
Platforms of Record
- Composition: BMI · ASCAP affiliate · The MLC · Harry Fox · Music Reports · CMRRA · sub-publishing network
- Recording: SoundExchange (RO + FA) · AFM & SAG-AFTRA IP Fund · PPL · neighbouring rights administrator · ISRC registrant
- Statutory: U.S. Copyright Office · ISWC via CISAC · ISNI / IPI
Gate Pipeline
- G0 Engagement · G1 Split confirmation · G2 Chain of title · G3 Identifiers · G4 Composition registration · G5 Recording registration · G6 International · G7 Release authorisation · G8 Post-release verification
How to Use
- Sign in with your email and password.
- The Dashboard shows perimeter completeness across the portfolio, open variances by severity, assets blocked at each gate, obligations due, and registration decay warnings.
- Adding a work: go to Compositions → New, or ingest from a platform export under Imports. Work the asset through Gates 0–6, attaching evidence at each sign-off. The gate queue shows exactly what is outstanding.
- Closing a perimeter gap: open Perimeter, filter to gaps, and click any cell. The platform generates the registration payload for that platform — HFA CSV, MLC registration, BMI publisher claim — ready to submit. Record the platform reference and evidence on return.
- Authorising release: only the CEO role sees Gate 7. It will refuse to sign while any required registration is outstanding or chain of title is unrecorded. Until it is signed, the work appears in no export of any kind.
- Loading statements: go to Statements → upload the royalty statement → the platform matches lines to assets by identifier and retains anything unmatched. Every figure you will ever quote is created here, and carries its citation forward automatically.
- Keeping registration status current: under Sync, upload a fresh export from BMI/Songview, SoundExchange or The MLC after registering works. The findings recompute themselves from the new data — newly-assigned ISWCs and MLC song codes are captured and the outstanding-issue counts update with no manual editing. Run the Deezer ISRC enrichment from the same tab to fill any missing recording ISRC.
- Producing registration & catalog files: under Export, download the HFA eSong bulk workbook, the HFA CWR (.V21) registration file, or a filterable catalog report to submit or circulate. Anything held back is named in the response with the reason, so you know what did not go and why.
- Papering the writer splits: under Split sheets, review what is outstanding and why, then generate a pre-filled sheet for one work or a zip of them all. Circulate for signature and record the signed sheet against the work. Registration is not waiting on this — the publishing position is already settled — but a share carried into a PRO or HFA registration is not evidenced until the sheet is signed.
- Quarterly reconciliation: runs on schedule. Review variances under Reconciliation, clear or escalate each, and generate the board pack. The pack cannot render a financial figure that lacks a statement citation.
- Discharging a delivery obligation: under Perimeter → Repertoire delivery, generate the pack for the counterparty, issue the covering notice, and record the delivery evidence.
Gate 2 has no exception path: a work whose chain of title is not recorded under 17 U.S.C. §205 may not be exploited under any circumstances, because an intervening transfer recorded first takes priority and no later diligence recovers it. Claude services are advisory only — they may propose values traceable to a supplied document, always with the source passage, and are required to return an explicit gap rather than a plausible value when the document does not support one. No AI service may originate a financial figure, share, identifier or registration status.
Launch Music Rights →