A production-grade engineering reference for automating corporate entity compliance across all 50 U.S. jurisdictions.
👉 Read it live at www.annual-filing.org
Manual annual-filing tracking breaks the moment a portfolio grows past a handful of entities: due dates drift, state portals change without warning, and a single missed report can trigger penalties or administrative dissolution months later. This site treats the whole problem as a deterministic software system instead of a spreadsheet — and shows you, end to end, how to build it.
Every page is a hands-on field guide written for the people who actually ship this tooling: corporate legal-ops and entity-management teams, compliance officers, and the Python automation engineers who support them. Each one pairs a real architectural decision with runnable, type-annotated Python, a hand-drawn diagram, and jurisdiction-specific detail for Delaware, California, New York, and Texas.
The reference is organized into three connected disciplines:
| Area | What it covers |
|---|---|
| 🏛️ Core Architecture & Regulatory Mapping | Treat statutes as versioned configuration — entity taxonomy and classification, schema-driven obligation contracts, filing-deadline calendars, and secure, auditable data boundaries. |
| 📡 Secretary of State Portal & API Ingestion | API-first sync with headless fallbacks, async polling and rate-limiting, pagination, error categorization, and good-standing certificate monitoring across fragile state portals. |
| ⏱️ Deadline Tracking & Routing Engines | Rules-as-code deadline calendars, penalty and grace-period mapping, registered-agent routing, priority scoring, multi-entity batch orchestration, and alerting pipelines. |
Highlights include worked, multi-jurisdiction examples — benchmarking priority-scoring strategies, calculating multi-state grace and cure windows, driving the California BizFile and New York DOS portals, bulk good-standing polling with status diffing, and orchestrating resumable filing batches without duplicate submissions.
- Deterministic, not eyeballed. Statutory rules modeled as data, pure functions for date math, and idempotent pipelines you can re-run safely.
- Audit-ready by design. Structured logging, provenance hashing, and reproducible decisions your counsel can defend.
- Built for scale. Bounded concurrency, per-jurisdiction pacing, and failure-budget thinking that keep hundreds of entities in good standing.
- Genuinely practical. No placeholder pseudo-code — every module is complete, type-annotated Python 3.10+.
This is an engineering reference, not legal advice or a legal reference. Statutory citations, deadlines, grace periods, and penalties are illustrative and can change; verify every obligation against the primary source and qualified counsel before relying on it.
This repository holds the source for the site — content in Markdown, built into a fast, accessible, offline-capable static site with Eleventy and deployed on Cloudflare Pages.
npm install # install dependencies
npm run serve # local preview at http://localhost:8080
npm run build # build the static site into _site/
npm run deploy # build and publish to productioncontent/— the guides, as Markdownsrc/— layouts, styles, data, icons, and the service worker.eleventy.js— build configuration
- 🌐 Website: www.annual-filing.org
- 💻 Source: github.com/annual-filing/annual-filing