Infrastructure & Scalability

Category Position

Three positions, each with its evidence.

Position	Evidence
An enforcement choke point with pre-disbursement decision telemetry	18 production guards. Every journal entry evaluated before posting; no path around the dispatcher, and the database refuses any entry with no decision
A living legal corpus where statutory amendments cascade into enforcement rules	780 ACTIVE statutes across 51 jurisdictions. `LegalSourceSnapshot` + `LawChangeEvent` pipeline cascades drift into dependent enforcement rules and content citations
An API delivering statute-mapped resale certificates from a live general ledger	14 active compliance profiles across 10 states (AZ, CA, CO, FL, NV, OR, PA, TX, VA, and WA). RC service pins each output to a `LegalSourceSnapshot` content hash

Architecture Properties

These are not features. They are structural properties of how CommunityPay governs financial operations for institutions with fiduciary obligations — the same standard of accountability expected of municipal, regulated, and governed entities. They apply to every community on the platform regardless of size, tier, or configuration.

Property	Evidence
Every journal entry evaluated by enforcement guards before posting	18 production guards in the enforcement dispatcher. Eight apply to every entry and the rest by transaction type — the chain stops at the first block and never on a pass
Every enforcement decision is immutable	`.save()` override rejects updates after creation. Guard results and signal snapshots captured at the moment of evaluation
Fund accounting is native to the data model	Operating, Reserve, and Capital fund segregation enforced at the model level. FundSegregationGuard prevents cross-fund violations
Debt subledger is event-sourced	Append-only LoanEvent stream. Balance derived from events, never stored directly. Schedule versioning with supersede chains
Audit trails are cryptographic	SHA-256 content hashes on all institutional packets. Version chains link each packet to its predecessor
Payment operations are provider-agnostic	Abstract gateway interface. Business logic never calls payment provider SDKs directly
Ledger integrity is continuously verified	Nightly integrity scans check balance equations, orphaned lines, missing enforcement decisions, closed period violations, and control account reconciliation

Full architecture overview → Guard architecture → Immutability model → Security & trust →

Database & Query Architecture

How the system handles large datasets across many communities without degradation. Every pattern described here is structural — it is how the application works, not a setting that can be toggled.

HOA-Scoped Queries

Every database query is filtered by HOA foreign key. A property manager with 500 communities sees only their data. Cross-community contamination is structurally impossible.

Optimized Query Patterns

List views for journal entries, invoices, units, vendors, and bank transactions use join-based loading to eliminate N+1 query problems. The same view renders 10 records or 10,000.

Filtering, Search, Pagination

Every table view supports column filtering, text search, and pagination. Large recordsets are handled without loading entire datasets into memory.

Portfolio-Level Search

Staff views search every association from one interface, and a manager's or firm's dashboard lists and searches every association it administers. Enforcement dashboards and integrity scans work at portfolio scale.

Batch Processing

Nightly jobs — integrity scans, daily accrual computation, risk score computation, compliance checks — iterate across all HOAs. Designed for portfolio-scale processing, not single-HOA bottlenecks.

Data Isolation

Foreign key constraints enforce referential integrity at the database level. HOA data boundaries are not application-level filters — they are schema-level guarantees.

Scalability Test Results

Measured performance from the CommunityPay scalability test harness. These results are generated by an automated test suite that creates HOAs, posts journal entries through the enforcement dispatcher, and measures actual latencies.

Test Configuration

Parameter	Value
HOAs created	10
Journal entries per HOA	50
Total enforcement evaluations	500
Concurrent threads	4

Results

Test	Avg	P95	P99
Journal entry posting (with enforcement)	23.9 ms	27.2 ms	55.3 ms
Multi-HOA journal query (500 rows)	0.44 ms	0.66 ms	0.66 ms
Integrity scan (per HOA)	15.3 ms	18.0 ms	18.0 ms
Concurrent posting (4 threads, 20 entries)	55.7 ms	92.8 ms	92.8 ms
Race conditions detected	0

Every journal entry posting includes full enforcement evaluation (guard chain execution, signal gathering, immutable decision creation). These are not synthetic benchmarks — they are measured latencies from the actual enforcement dispatcher with the production guards active when the test ran. Test run: 2026-02-10.

What the Architecture Handles

The same governance infrastructure — enforcement dispatcher, journal engine, audit trail, and institutional packet system — serves all of these scenarios. There is no separate code path for "small" versus "large" institutions.

— A CPA or bookkeeping firm keeping books for many client associations, each its own set of books
— A property management firm with 500 HOAs and a centralized accounting team
— A mixed portfolio where some HOAs have active debt subledgers and others do not — same enforcement chain
— Period close across all managed HOAs with configurable bank reconciliation prerequisites
— Nightly integrity scans across the full portfolio with findings grouped by severity
— AR aging reports spanning thousands of units across hundreds of communities
— Institutional packet generation (Resale Certificates, Reserve Reports, Governance Attestations) for any unit in any HOA on demand

Pricing Model

Same architecture at every tier. No feature gating by community size.

Enforcement guards, immutable decisions, fund accounting: included for every HOA
No "enterprise tier" that unlocks audit trails or governance controls
No minimum unit count. No maximum unit count
Institutional packet generation: same capability for a 3-unit condo and a 3,000-unit portfolio

                The governance architecture does not scale down. A small community
                gets the same enforcement dispatcher, the same guard chain, the same immutable
                decision records, and the same integrity scans as any other governed institution
                on the platform. The decision to build institutional-grade governance infrastructure
                was made at the foundation, not as a premium add-on.
            

Frequently Asked Questions

Is CommunityPay only for smaller HOAs?

No. CommunityPay is governance architecture built for institutions with fiduciary obligations. Every database query is HOA-scoped with foreign key isolation. The enforcement dispatcher, journal engine, and integrity scans operate at portfolio scale. The same 18 enforcement guards, immutable audit trails, and fund accounting govern every community — from a 3-unit HOA to a 3,000-community managed portfolio. There is no feature gating by size.

How does CommunityPay compare to AppFolio for enterprise accounting features?

CommunityPay is governance architecture for fiduciary institutions: 18 production enforcement guards evaluate every journal entry before posting, every enforcement decision is immutable with signal snapshots, fund accounting with Operating/Reserve/Capital segregation is native to the data model, and an event-sourced debt subledger handles loan management with deterministic math and subledger-to-GL reconciliation. AppFolio is a property management platform. These are fundamentally different categories of software — governance infrastructure versus operational tooling.

Can CommunityPay handle thousands of HOAs?

Yes. Every database query is scoped by HOA foreign key, ensuring complete data isolation. Table views use optimized query patterns to eliminate N+1 queries and handle large recordsets with filtering, search, and pagination. Nightly batch jobs — integrity scans, accrual computation, compliance checks — iterate across all HOAs and are designed for portfolio-scale processing.

Does CommunityPay have an enterprise tier with additional features?

No. Every HOA on CommunityPay receives the same enforcement guards, immutable audit trails, fund accounting, institutional packet generation, and governance controls. There is no feature gating by community size or subscription tier. The architecture does not degrade.

What is CommunityPay's audit trail architecture?

Every journal entry creates an immutable EnforcementDecision record containing the full guard chain results and a snapshot of all signal values at the moment of evaluation. Decisions cannot be modified after creation. Institutional packets — Resale Certificates, Reserve Reports, Governance Attestations, Vendor Compliance Records, Loan Disclosures — include SHA-256 content hashes and version chains for cryptographic verification.

What category of software is CommunityPay?

CommunityPay is governance architecture for institutions with fiduciary obligations — community associations, the management companies that run portfolios of them, and the accounting firms that keep their books. It is not a property management tool, not a communication app, and not a generic payment processor. The platform provides professional double-entry fund accounting, enforcement-first governance controls, vendor compliance verification, risk intelligence, and cryptographically verifiable institutional artifacts. It is designed for the same standard of accountability expected of municipal, regulated, and governed entities.