Keeps the books and prepares the tax figures for every company in the group, and for the family household.
Go here to
- Upload a receipt, invoice or bank statement
- Check what an entity earned or spent
- Pull the numbers a tax return needs
What it does
- Document intake with AI extraction — uploaded statements, invoices and receipts are read by Claude into structured transactions, as a background worker and again on a schedule so nothing depends on one request finishing.
- An upload that can always be undone — if the record will not go in, the bytes come back out. A stored file with no row is the shape of a document that exists and cannot be found.
- Entity financials from the register — the entity roster is read from the estate register rather than written into this platform, and re-synced on a schedule.
- Monthly statement generation and tax workbooks — the figures a return needs, produced from the recorded transactions rather than re-keyed.
- Payroll sync from Gusto — scheduled, so payroll figures are current without anyone exporting them.
- Storage reconciliation — finds statements that are in storage and in no query, which is how a document goes missing without anything reporting an error.
- Large responses stream — a request too big to answer in one piece streams rather than failing.
Background
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.
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 Boulevard 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.
Note
The AI pipeline processes up to 20 documents per daily run. Documents are archived after processing.
The official record of every company in the group — what it is, where it is registered, and the documents that prove it.
Go here to
- Look up an EIN, state file number or formation date
- Upload a legal document so it is on file
- Check whether an entity's paperwork is complete
- Clear the review queue
What it does
- The register other platforms read — entities, their identifiers and their offices are held here and published as views the rest of the estate derives from, so no other platform states a legal fact of its own.
- The document decides its own fields — extraction reads what a document actually states rather than filling in a template's expectations, so an instrument with unusual fields is not silently flattened into the ones a form anticipated.
- A document belongs to an entity, enforced rather than intended — the constraint is in the database, not in the uploader's habits.
- A document can belong to a person — the subject is derived from what the document names, matched against the register. There is deliberately no person selector: asking someone to pick from a list is asking them to retype a fact the page already states, and four people here share a name, so an exact match or nothing is the only safe rule.
- Extraction sweeps, not just triggers — a scheduled sweep asks only whether a document has been read, never how it arrived.
- Review queue with reasons — a refusal states what it refused on, so an unresolved document says why rather than simply waiting.
- SAM.gov sync and a scheduled registry audit — external registrations are checked against the register rather than assumed to still hold.
- Storage adoption — files that reached storage but never reached a row are found and adopted.
Background
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.
EMS v1.1 Canonical Layer (Spec §16.1 – §16.3)
- — documents ingested with SHA-256 verification across — 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.
Note
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.
Finds federal grants the three foundations can apply for, and follows each application through to submission.
Go here to
- See which grants are open and worth applying for
- Check where an application has got to
- Assemble what a submission needs
What it does
- Scheduled discovery — federal opportunities are scanned on a schedule for Today's Child, Ifoma and AITCH Conservation, rather than found by someone checking.
- Filtered to what each foundation can actually win — opportunities are matched against the foundation's own purpose and eligibility, so the list is short enough to act on.
- Proactive drafting — a background worker drafts against an opportunity before anyone opens it.
- Grounding statistics — the platform reports how well its drafts are grounded in the source material, so a confident draft with nothing behind it is visible as such.
- Submission tracking — each application is followed to submission, with an email log of what went out.
- Bulk operations and export — work a list rather than an item at a time.
Background
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.
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.
Note
Expired opportunities are automatically labeled. Mission guardrails prevent cross-foundation contamination.
The board's own view of the group: meetings, resolutions, finances and anything waiting on a decision.
Go here to
- Prepare for, or follow up, a board meeting
- Read a resolution or governing document
- See which action items are still open
What it does
- One console per board concern — resolutions, meetings, initiatives, financials, grants, patents, compliance and documents, each entity-scoped and role-gated so a member sees the entities they actually serve.
- Action items carried between meetings — an item raised in one meeting stays visible until it is completed, rather than living in the minutes of the meeting that raised it.
- Deadlines that check themselves — voting deadlines, meeting reminders and compliance alerts are checked on a schedule and notified, rather than depending on someone noticing a date.
- Exports — board material produced as a pack rather than assembled by hand.
- Entities and members from the register — who sits on which board, and which entities exist, are read from the estate register.
Background
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
Note
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.
Shows how money moves between the companies and what each one is due to receive.
Go here to
- Check an entity's cash position
- See how a month's income was split
- Model a change before committing to it
What it does
- The allocation model, run rather than described — the 30/40/20/10 framework at AITCH Holdings and the 52SC fixed-retainer MSA waterfall are computed by the cash-flow engine across every active and pending entity in the cascade.
- Scenarios — model a change and see it flow through the cascade, run as a background worker so a long projection is not bounded by one request.
- Bridges to the platforms that hold the source figures — bookkeeping and MSA reporting feed this on a schedule, so the ledger reflects what those systems actually recorded rather than a re-keyed copy.
- Entities and documents from the register — the roster and its documents sync from the estate register on a schedule; nothing about an entity is written here by hand.
- Loans and ledger — obligations tracked alongside the cash they consume.
- Alerts with a scan behind them — conditions are scanned rather than raised by whoever noticed, and synced so an alert nobody cleared stays visible.
- A backup of the whole database — gzipped, because the database does not fit in one object, and of everything rather than the seven tables someone once listed.
Background
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.
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 Boulevard 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.
Note
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.
The family's home page, and the sign-in that every other platform in this list uses.
Go here to
- Reach the other platforms
- Sign in, or fix a sign-in problem
- Read family reports and documents
What it does
- The estate's identity instance — every platform's sign-in resolves here. If this breaks, they all break, which is why it is health-checked and watched.
- Roles applied at account creation — signup applies role metadata, and accounts are mirrored into the estate database so authorisation is reasoned about in one place rather than per platform.
- Two audiences, one deploy — the external institutional page and the internal family portal are served from the same site, the internal side behind the identity gate.
- Identifiers resolved at build — EINs and entity names are read from the register when the site is built, and the build FAILS rather than publishing a placeholder that was never resolved.
- Infrastructure, not a product — it makes no Claude calls and is deliberately excluded from AI spend reporting; a permanent "awaiting first event" on a platform that will never call Claude would be a false pending on a dashboard whose point is honest reporting.
Background
The family portal, and the estate's identity master. One deploy serves two audiences: /public is the external institutional page, and every other path falls through to the internal Family Portal behind a Netlify Identity gate. Sign-in for every other platform in the estate resolves through the Identity instance here, and new accounts are mirrored into Supabase so authorisation can be reasoned about in one place rather than per platform.
Why it is listed here
- It is infrastructure, not a product: it makes no Claude calls and never appears on the AI cost grid
- It is health-checked and watched for failures — if sign-in breaks, every platform breaks
- It appears in the system context as the node the other platforms authenticate through
Note
Registered as infrastructure. Excluded from AI spend reporting by design — a permanent “awaiting first event” on a platform that will never call Claude would be a false pending on a dashboard whose purpose is honest reporting.
Checks governance and lending documents against the rules they have to meet, and keeps the result so the same check can be re-run years later.
Go here to
- Run a compliance check on a document
- See exactly why something passed or failed
- Re-open an audit that was run before
- Track a signature through to completion
What it does
- Deterministic audit engine — a nine-layer compliance audit over governance documents, transaction packets and lending packages.
- Every run is replayable — each audit cites pinned source versions, rule versions and register document IDs, so a result reached today can be reproduced years from now against the same inputs rather than against whatever those documents have since become.
- Findings, escalations and resolutions — a finding is carried through to who owns it and how it was closed, rather than reported once.
- Signing, with chain of custody — documents route for signature through DocuSign and the custody chain is recorded, not inferred.
- Compliance calendar — obligations with dates, published as a subscribable calendar and notified on a schedule.
- The estate's holdings of record — ownership, beneficiaries, signatories, bank accounts, real property, IP portfolio and royalty streams, each sourced from the register rather than restated here.
- Quarterly audit on a schedule — the audit runs whether or not anyone asks for it.
- Every drafting run states what it cost — cost and tokens are totalled from every model turn, draft and review alike, and written to the request on each round rather than at the end, so a run that dies mid-flight still reports its spend. There is deliberately no per-run ceiling: the run is bounded by its attempt limit and the spend by the account cap the portal warns ahead of, because a legal review stopped halfway is a false negative for every instrument it never reached.
- A draft whose reason has gone leaves the queue — each day, before more are drafted, an instrument is withdrawn once its obsolescence is established: every finding it cites has left the live set, or every document it was raised against has been superseded, or — for the drafts neither of those can judge — the legal reviewer re-reads the entity's instruments, the register and the statutes as they stand today and finds nothing legally wrong. The re-reading is the part that matters, because a draft is just as often retired by a document arriving elsewhere as by its own being replaced: a Form 8822-B correction waited two weeks after the IRS letter that retired it reached the register, and neither derivable test could see it. Every undecided draft is re-read, with no ceiling on how many. A clean verdict is confirmed before it withdraws anything: the record is read a second time, independently, and two runs twenty minutes apart have been seen to disagree about the same unchanged record — so a disagreement withdraws nothing and goes to a person with both readings on file. The direction matters, because leaving a draft alone is the safe answer and taking an instrument out of the queue is not. A reviewer that cannot decide has not decided, so the draft stays. A verdict is re-derived only when the record it was read from has moved: each reading is kept with a fingerprint of the documents' content hashes, the extracted text's hashes, the register, ownership, the name history and the statutes, and while that fingerprint holds the verdict is reused at no cost. That is not a ceiling and not an expiry — nothing is skipped, and one changed hash anywhere puts the question again. Each withdrawal records what withdrew it and that no person decided against it, the draft stays on file with its audit, and anything still undecided is reported with its age.
- A live defect becomes an instrument without being asked — each day the outstanding failures are grouped by entity and a corrective instrument is queued for signing, marked machine-initiated and citing the findings it cures. Which defects qualify is taken from each rule's own stated remediation, not from a list: a remediation beginning "Correct" means the instrument contradicts a source of truth the register already holds, while "Route to counsel" is a lawyer's judgement and is reported rather than drafted. Every entity with a live curable defect is queued on each run: there is no per-run ceiling, because an entity deferred by a number here is one nobody is working on. Spend is bounded by the account cap the portal warns ahead of, and review by the fact that each request names the findings it cures and can be withdrawn unsigned.
- The compliance audit is visible where health is read — the Status page shows what the rule engine still finds wrong across the current documents, beside the document reader's own issues. Checking is not something anyone starts: every document EMS takes in is audited on arrival and the corpus is reviewed in full, so the Checks page is a reader for those results, not a form.
- What is outstanding is derived, not marked — a failure counts as live only when it comes from the latest audit of its document, that document is still current, and nobody has dispositioned it. Of 4,918 recorded failures, 443 are live; the rest were superseded by later audit runs or cannot name the instrument they were found in. An audit must now say what it read: `document_id` is required, and a scratch check against pasted text must declare itself and is never counted among the estate's findings.
- A formed company's instruments are drafted without being asked for — when a certificate of formation and an EIN notice are both on file, any instrument that every *other* active entity of that type holds is queued for signing, marked machine-initiated and carrying the documents that triggered it. The required set is derived per entity type from the register's own practice, never written down: an LLC's operating agreement is not a foundation's, and a type with too few examples gets no set at all rather than a guess from one case.
- A document with no text is still read — where EMS kept no prose but holds a structured extraction, the arrival is read from that extraction and recorded as evidence, never promoted to operative text. This is how acknowledgements reach the platform: IRS entity-classification and EIN-verification letters, certificates of cancellation, state filing receipts — the documents whose whole purpose is to say a thing is already done, and which were previously discarded as having nothing to read.
Background
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)
- — sources + — active rules (— deprecated) in the canonical registry, each rule pinned to a versioned source
- Registry scoped to the entity footprint (—), derived from where the estate's entities are actually formed — Nevada included because three dissolved Nevada entities still have documents, and a document outlives the entity that signed it: — out-of-footprint rules for — deprecated, their — sources retained as dormant and verified yearly rather than cascading daily. Texas was removed outright rather than kept dormant — the estate has never held a Texas entity, so there was no dormant registry to keep.
- 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. - Open Checks (/checks.html) to read any compliance check and its full result. There is nothing to start there: every document EMS takes in is audited on arrival, and the corpus is reviewed in full.
Note
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.
The list of every bank and brokerage account the group holds. Account numbers stay hidden unless you need them.
Go here to
- Find which bank an entity uses
- Get the details needed to make a payment
- Confirm an account is still open
What it does
- Authoritative account registry — every account across the group's institutions, tied to the entity that holds it, with full account and routing numbers held once rather than copied into spreadsheets.
- Masked by default — sensitive fields show last-four unless deliberately revealed, so the register can be read in a meeting without exposing what is in it.
- Statement scanning on a schedule — accounts are scanned nightly rather than checked by hand. That job silently failed every run for at least five days before anything reported it; it is now watched, because a scheduled job that reports healthy on work it never did is worse than one that does not run.
- Entity roster from the register — institutions are attached to entities read from the estate register, never to names typed in here.
Background
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.
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.
Note
Classified: Do not transmit via unencrypted channels. Full-number exports require an explicit reason written into the audit log.
Produces the reports 52nd Street Capital sends its management-services clients, monthly, quarterly and annually.
Go here to
- Check whether the month is ready to close
- Pull this month's figures in from Power BI
- Generate a client report
- Send or re-send a report
What it does
- Invoice receipts and MSA reports — bi-weekly receipts (1st–15th, 16th–end) and monthly, quarterly and annual reports, with revenue, COGS, operating expenses, payroll and an auto-calculated trial balance that warns when it does not balance.
- AI report generation — builds a report from uploaded source documents (P&L workbooks, statements, PDFs) via Claude, run as a background worker.
- Power BI sync by browser extension — "52SC — Power BI Sync" pulls the month's figures in one click. It is an extension rather than a button because a web page cannot read another site's signed-in session; that is a browser security rule, so no button on the portal could ever have done this.
- A/R ingest on a schedule — the A/R Express workbook lives in Egnyte, which a Netlify function cannot reach, while the service-role key exists only here. A monthly routine reads the workbook and posts its text; this platform parses and writes it. Both ingest endpoints fail closed: with the token unset they refuse every request rather than accepting them.
- "Ready to close" — checks each source's freshness against the period being closed, not against today, and separates what still needs a person from what runs unattended. A September schedule captured on the 13th is complete, self-consistent and wrong; generating against it reconciles the month to a forecast.
- Unread-document sweep — asks only whether a document has no reading yet, never how it arrived. Documents come from the upload form, from automation and from the extension, and a trigger covering the paths someone remembered is the thing that quietly stops covering them.
- Reporting period read from inside the document — a background worker, because reading a 48-page master schedule takes longer than a synchronous function is allowed and a timeout leaves the period null, which reads downstream as "this document states no period".
- 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.
- Distribution — a rendered PDF on every send path, plus a test-send mode that leaves delivery state untouched.
Background
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. Most of a month’s figures now arrive on their own — A/R from the Egnyte workbook on a schedule, Power BI through a one-click browser extension — and the platform states whether the period is actually ready to report before anyone generates against it.
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.
- Once, per person: install the “52SC — Power BI Sync” extension — Chrome →
chrome://extensions→ Developer mode → Load unpacked → choosedist/extension. - Each month, after it has ended: sign in to Power BI, open any report, click the extension icon and press Sync. The Files tab will then show Power BI as current under “Ready to close”.
- Check Ready to close before generating. It names what still needs a person — Power BI and ABS both require an interactive sign-in — and what is already handled on a schedule.
Note
Trial balance must be balanced before a report can be finalized. Status flow: Draft → Sent → Archived.
The register of every song and recording the group owns, and whether each one is properly registered everywhere that pays royalties.
Go here to
- Check whether a song or recording is registered
- Produce a registration file to send to a society
- Find out why an expected royalty statement never arrived
What it does
- Registration perimeter engine — computes, per asset, its status across every platform of record: BMI, The MLC, Harry Fox, SoundExchange, AFM & SAG-AFTRA Fund, the Copyright Office, PPL, sub-publishing, CMRRA, ISWC and ISRC. Every gap routes to the payload that closes it.
- Absence detection — asserts that a statement line exists wherever activity is expected, and raises a variance when one does not. An empty catalog produces no statement, and no statement used to produce no alarm; this is the control that ends that.
- Gate enforcement — gate order is enforced by database trigger rather than by the interface, and release authorisation refuses to sign while the perimeter is incomplete or chain of title is unrecorded.
- Self-service exports — the HFA eSong bulk-upload workbook (.xlsx), the HFA CWR 2.1 registration file (.V21) and a filterable catalog report, generated on demand.
- Source-pluggable reconciliation — findings derive from the platform of record rather than being toggled by hand; a fresh BMI/Songview, SoundExchange or MLC extract updates them.
- Deezer ISRC enrichment — fills a missing recording ISRC from the public catalog on conservative exact title-and-artist matching.
- Citation constraint — a reported financial figure carries a foreign key to the statement line it came from, so an uncited number cannot be stored.
Background
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.
Scope
- 360 World Music LLC — BMI publisher IPI 00782057821, HFA P769TR
- Global Music Group L.L.C. — SoundExchange Copyright Owner account —; HFA relationship is an agency/licensee account — a label obtains mechanical licences rather than registering repertoire — and is unconfirmed pending HFA’s reply (F‑32)
- — works on the register, — of them registered compositions across BMI accounts 1666683 and 945278
- — master recordings
- — U.S. Copyright Office registrations on the music register
- — studio-archive documents inventoried; the executed instruments filed into EMS and linked back to the archive row each came from
- Composition: BMI · ASCAP affiliate · The MLC · Harry Fox · Music Reports · CMRRA · sub-publishing network
- Recording: SoundExchange (Rights Owner) · AFM & SAG-AFTRA IP Fund · PPL · neighbouring rights administrator · ISRC registrant
- Statutory: U.S. Copyright Office · ISWC via CISAC · ISNI / IPI
- 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.
- Finding the paper behind a right: the archive’s executed instruments are in EMS against the owning entity, so an agreement supporting a split, a management commission or a master ownership claim is retrievable from the central register rather than from a drive that has to be plugged in. Anything held back — a blank template, a duplicate, a document naming no entity — is recorded with the reason it was held.
- 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.
Note
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.
Works out what to buy and sell to bring the investment accounts back to their target mix.
Go here to
- See how far the accounts have drifted
- Get the exact buy and sell orders
- Check a change before making it
What it does
- Four-tier capital architecture — holdings are scored against the Operational / Short-Term / Strategic / Legacy structure rather than against a single blended target.
- Precise orders, not percentages — the recommendation is the actual buy and sell amounts across the accounts, so it can be acted on without a second calculation.
- Holdings synced rather than typed — positions come from the platforms that hold them, with prices refreshed before a run.
- Every run recorded — a recommendation is stored with the inputs that produced it, so a decision can be reviewed against what was known at the time.
Background
Investment portfolio rebalancing tool for 52nd Street Capital Group, anchored to the Howell Legacy Group four-tier capital architecture (Operational / Short-Term / Strategic / Legacy). Calculates precise buy orders across eight accounts from target allocations and real-time prices, with ETF (whole-share) and mutual fund (dollar-based) order logic, IPS-anchored presets, AI recommendations that tilt from the tier IPS baseline with a cited driver per asset class, tier-aware drift analysis and a Capital Stack dashboard rolling positions up by tier and entity.It also measures. Every account carries a time-weighted return chained from its statement period reconciliations — so contributions are never reported as performance — benchmarked against its tier IPS target, and every saved recommendation can be scored against what actually happened afterwards.
Accounts & Capital Tiers
- Howell Holdings LLC (Schwab) — Strategic / Strategic Capital Reserve
- Schwab Solo 401(k) — Strategic / Retirement
- Schwab One Personal — Short-Term / Taxable brokerage
- Fidelity Trust — Legacy / Trust corpus
- Fidelity Roth IRA (minor) — Strategic / Retirement
- Wells Fargo Roth IRA — Short-Term / Roth
- Fannie Mae 401(k) — Strategic / Retirement (transitional)
- Truist Trade — external (in-laws); excluded from household totals and IPS governance
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.
Note
Tax-advantaged accounts get full rebalance recommendations; taxable accounts prefer contribution-based correction. The IPS governs and the AI advises: each tier carries its own target, drift threshold and review cadence, AI tilts are capped per class and in aggregate, and Legacy smallcap + emerging-markets exposure is capped at 25% combined absent an explicit Managing Member determination — enforced server-side, not merely requested of the model. Returns are not annualised for windows under a year, and an excess return against the benchmark is reported only when enough of the window is priced to support one.
Values the estate's properties every week and keeps a record of each valuation.
Go here to
- Look up what a property is currently valued at
- See how a valuation has moved over time
What it does
- No web interface, by design — this is a Python pipeline run by GitHub Actions on a weekly schedule. There is no page to open; it writes one audited row per run and the figures are read where they are used.
- One audited row per run — each valuation records the inputs and the method that produced it, so a number can be explained rather than only quoted.
- A stated confidence vocabulary — the pipeline says how confident a valuation is in fixed terms, so "estimate" means the same thing in every row.
- Reference cases in the test suite — known properties with known answers are asserted on every run, so a change to the model that breaks a settled valuation fails rather than ships.
Background
Values every active and pending-acquisition property in the estate’s real-estate portfolio and writes one audited row per run. This platform has no web interface — it is a Python pipeline run by GitHub Actions on a weekly schedule, and it is listed here because it is one of the estate’s platforms, not because there is anything to open. Its output reaches people through the Wealth Management platform, which projects the latest valuation per property into wm_valuations on its hourly sync.
Method
- Search, read the answer block, return the value. No comp math, no square-foot adjustments, no manual anchors, no county adapters, no fallback synthesis. If the search results carry no usable answer block the property comes back unresolved and the query is rephrased — the answer is in the results or it is not.
- A text block qualifies when, within roughly 500 characters, it names 2 or more of Zillow, Zestimate, Redfin, Realtor.com or Trulia and carries 2 or more dollar amounts of 4+ digits. The widest dollar range becomes the low/high; its midpoint is the point estimate.
- Four query forms are tried in order (property value, home value, what is … worth, estimate) before a property is called unresolved.
- The only post-processing is the registry encumbrance discount:
discount_pctis summed across the encumbrances recorded on the property row and applied to the value. — encumbrances are recorded across the — active properties. - Every run stores the query that worked, the raw block text, the parsed value and the platforms cited, so a number can be traced back to what was read rather than re-derived on trust.
Scope & Integration
- Portfolio of — active properties and — disposed, read from
hlg_properties— the registry carries owner entity, EIN, Delaware file number, parcel ID, deed book/page and encumbrances alongside the address. - — valuation rows recorded since —; most recent run —.
- — carried across — properties as of — — read from
wm_valuations, which is the figure Wealth Management actually carries. It is not the sum of the latest runs: a county assessment beats a market estimate unless the estimate is recent (under 90 days) and tight (within 15%), so Hudgins Farm carries its market estimate while the vacant lot and the timber acreage carry county assessments. Deriving a rival total here would put a second copy of a valuation policy in a portal card. - Feeds
wm_valuationsin the Wealth Management platform, which is where these numbers surface for reading. Nothing here is displayed to a user by this platform itself. - Runs under its own Anthropic API key held in the macOS Keychain, so spend attributes to this platform rather than to whatever shell happened to invoke it — the same per-platform attribution the AI Cost dashboard above depends on.
How to Run
- It runs itself. Sundays at 13:00 UTC (09:00 ET) via
.github/workflows/portfolio-valuation.yml— property values move slowly, and weekly is the balance between freshness and API spend. - To run it off-schedule, use the workflow’s
workflow_dispatchtrigger in GitHub Actions and pick a purpose:heloc,tax,insurance,estate(the default) orinformational. The purpose is recorded on every row — a HELOC valuation and an estate valuation are not the same claim. - Locally,
bin/valuate portfolio --purpose estatefor the whole portfolio, orbin/valuate one --key hudgins_farm --purpose helocfor a single property. bin/valuatereads this platform’s Anthropic key from the Keychain and exports it for that command only. Do not setANTHROPIC_API_KEYin your shell: a global export would bill every local process to this platform and make genuine runs indistinguishable from development noise.- Read the results in the Wealth Management platform, not here.
Note
There is no launch button because there is nothing to launch, and adding one that pointed at the repository would misrepresent a scheduled pipeline as an application. The button below is declared like every other card’s and stays hidden on its own: the registry publishes no address for this platform, so nothing reveals it. The absence is now a fact the data states rather than something a person remembered — and if this ever grows an interface, publishing its url is all that is needed. This card exists so the platform is not invisible: it was in the platform registry with no card here, which is why the portal counted 12 platforms while the estate operated 13.
Training for the family and staff: the programmes you are required to take, plus a library of outside courses you can choose from.
Go here to
- Start or continue your own training
- See what is required of you and what is recommended
- Find a course in the external library
What it does
- Programmes, modules and lessons — the internal curriculum, with an admin view for authoring.
- Assignment by office or cohort — a programme is required of you because of the office you hold or the cohort you are in, not because someone enrolled you by hand. A programme may also recommend material without requiring it, and the dashboard shows those separately.
- Progress recorded, figures derived — a row is written for every lesson read and every module finished, and everything the dashboard reports is computed from those rows. Stored running totals were removed because they could disagree with the records they summarised.
- External library — institutional coursework linked rather than copied, filterable by department, with hours and tier taken from the source's own published unit counts.
- The lesson reader — a lesson can be read aloud in the browser, with a language control, and Continue returns to the lesson you stopped on rather than to the start.
- Its own database — `profiles`, `learning_paths`, `modules`, `lessons`, `enrollments`, `quizzes`, `module_completions`, `lesson_completions` and `external_courses` sit in a separate Supabase project, `howell-legacy-training`, which is why this platform declares no table prefixes in the shared register. Reads are made from the browser with a publishable key, so row-level security is the only thing separating one person's record from another's.
Background
The Howell Legacy Successor Training Program. Programmes, modules and lessons for the family's executive training, alongside an external library that links institutional material — MIT OpenCourseWare and others — rather than holding copies of it. Progress is recorded per person for every lesson read, and the figures shown are derived from those records rather than stored beside them. It is served at /training/ inside the Family Portal deploy, so it ships and fails with that site rather than having a deploy of its own.
Where its data lives
- Not in the estate database.
profiles,learning_paths,modules,lessons,enrollments,quizzes,module_completions,lesson_completionsandexternal_coursessit in a separate Supabase project,howell-legacy-training— which is why this platform declares no table prefixes in the shared register. - Reads are made from the browser with a publishable key, so row-level security is the only thing separating one person's record from another's. The view-security watch covers that database as of 2026-09-27; table-level RLS is still to be proven.
- Its migrations live in the repository and prove their own effect before they are accepted, but they are not in the estate's migration ledger, which resolves a single project — so changes there are still not recorded the way the estate's are.
Follows every patent application from first idea to granted patent, and files whatever the patent office sends back.
Go here to
- Check where an application stands
- Find the next deadline
- Read correspondence from the patent office
- Build a filing package before submitting it
What it does
- Full application lifecycle — every application tracked from concept through filing, office actions and resubmission to grant, with the filing package assembled here rather than by hand.
- USPTO correspondence, ingested as it lands — the mailbox is polled on a schedule, each document is captured against its application, and a reply can be drafted from it as a background worker.
- Pre-submission validation — artifacts, DOCX, drawings and claim support are each checked before a package is submitted, because a rejection for a malformed drawing costs a cycle for a reason that is not the invention.
- Fee calculation and deposit-account draw status — what a filing will cost, and whether it was actually drawn.
- Scheduled USPTO sync and forms refresh — application status and the current forms are pulled on a schedule rather than when someone remembers.
- Storage adoption — documents that reached storage but never reached a row are found and adopted, so a file that arrived is never invisible to the platform.
- Succession derived at read time — who holds an application is computed from the register when read, never stored, so a dissolved company cannot go on appearing as the holder of a live filing.
Background
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.
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). - 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.
Note
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.
The family's overall wealth picture — what is held, where it is held, and what it is worth.
Go here to
- See total holdings across every account
- Check a balance, a position or a valuation
- Understand how a figure was arrived at
What it does
- Bookkeeping is the source of truth — every brokerage and bank statement that lands in the bookkeeping platform is parsed into structured holdings and cash balances; this platform reads those rather than holding a second set of numbers.
- NAV history and snapshots — net asset value recorded over time, with each snapshot run as a job so the series is built rather than recalculated on demand.
- Price refresh and valuations — holdings revalued from current prices, with the valuation kept alongside what produced it.
- Forecast, scenarios and cash projection — model what a change does to the picture, run in the background where the projection is long.
- Coverage and data freshness, stated openly — the platform says which accounts it can actually see and how current each source is, so a total is never read as complete when it is partial.
- Scheduled jobs that cannot report healthy on work they did not do — three did exactly that, reporting success on a read they never checked.
Background
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.
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.
Note
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.