HIL NOTE: So I had Gemini generate this article to summarize the state of our core modules existing so far on the ContractorLocal platform. Here's what the model had to say:
We are excited to share a developer update on the state of the core modules existing within the ContractorLocal workspace. The platform continues to evolve around its core tenets: offline-first local hosting, zero-knowledge encryption, and a filesystem-driven CSV data model.
Here is a summary of the active modules currently available on the platform:
1. CRM Module (CRM)
Purpose: Payer, Vendor, and Contractor identity manager.
Details: Maintains legal names, contact numbers, email addresses, mailing addresses, default billing rates, and tax identification numbers (SSN/EIN). Serves as the single source of truth for recipient identity metadata.
2. Billing Center (billing-center)
Purpose: Document explorer and atomic transaction manager.
Details: Implements the Scrape-to-CSV architecture. Converts custom forms into
standardized 4-column CSV files. Features a dynamic schema editor that parses CSV inputs directly to prevent
layout drift, alongside an automatic .bak backup manager and minor-version increment loop on
file updates.
3. 1099s Preparer (1099s)
Purpose: Fast payment consolidation tool.
Details: Built as a simplex compiler. Queries contractor parameters in the CRM sector, executes rapid SQL aggregations on indexing payment columns inside the central registry database, and compiles selected transactions into a consolidated 1099-NEC CSV layout for tax exports. Note: Does not directly file or validate IRS forms.
4. Copy-Center (copy-center)
Purpose: Filesystem-routed form builder and template manager.
Details: Decouples document styles from state. Hydrates blank HTML form templates using lightweight JSON states and automatically routes static PDF attachments to native browser drawers.
5. Help Center (help-center)
Purpose: Integrated manual and learning guide.
Details: Built with subroute memory persistence. Leverages sessionStorage with
a 30-minute auto-expiry filter to maintain category navigation states when switching modules.
6. Sync-Hub (sync-hub)
Purpose: Headless cross-boundary table broker.
Details: Coordinates database junction mappings across sandboxes. Protects CRM entity
directories using table deletion filters (isClientsTable), forcing client table lists to remain
immutable from public API requests.
7. Time-Tracker (time-tracker)
Purpose: Hourly labor compiler.
Details: Stages raw billable hour periods and logs description cards in the operations database for visual mapping imports.
8. Activity-Logger (activity-logger)
Purpose: Task reconciliation logger.
Details: Logs operational project checklists and activity sheets to maintain high-density proof of performance.