Compliance Profile Registry

CommunityPay generates resale certificates under jurisdiction-specific statutory requirements. The compliance profile registry is the system that maps those requirements to the data sections, mandatory disclosures, and constraints that govern each certificate. This page describes how the registry is structured, what it contains, and how it supports multi-jurisdiction expansion.

Why Profiles, Not States

A compliance profile is not keyed by state. It is keyed by the specific statutory regime that governs the certificate. This distinction matters because a single state can have multiple concurrent regimes.

Washington State is the clearest example. Two statutes govern condominium and common interest community resale certificates:

All Washington communities will transition to WUCIOA (RCW 64.90) by January 1, 2028. Until then, both regimes are active. A resale certificate generated for a 1995 condominium must comply with RCW 64.34.425. A certificate generated for a 2020 planned community must comply with RCW 64.90.640.

If the registry were keyed by state, it would have to guess which regime applies — or require the caller to specify. By keying on the compliance regime itself, the registry eliminates ambiguity. The caller selects the profile; the profile determines the requirements.

Profile Structure

Each compliance profile contains five categories of information:

1. Statutory Identity

2. Operational Constraints

These constraints are from the statutes, not from CommunityPay policy. They are read from the verified legal-threshold corpus, with the profile's own value as the fallback, so a verified change reaches every certificate without a code change. The fee cap is written into the certificate's certification block and shown when the fee is collected.

3. Required Items

Each required disclosure item is a structured entry with:

The code is stable across versions. If the statute is amended and the item changes, the profile is versioned — the code itself does not change, preventing downstream breakage in reporting and analytics.

4. Mandatory Disclosures

Verbatim text blocks that must appear on the certificate. These are statutory requirements, not CommunityPay editorial.

Washington Condominium Act (RCW 64.34.425):

Washington WUCIOA (RCW 64.90.640):

WUCIOA requires the conspicuous notice in addition to the cancellation rights disclosure. This is a substantive difference between the two regimes — the newer statute requires buyers to be explicitly warned about assessment obligations and foreclosure risk.

These text blocks are embedded in the profile definition. They cannot be edited, paraphrased, or omitted during certificate generation. The generator includes them verbatim from the profile.

5. Profile Status

Fourteen profiles are defined in code and serve as the fallback. Six more profiles are defined in the legal data files and loaded as active records at each release: Alabama, Minnesota, Missouri, Tennessee, and Wisconsin condominium or common-interest regimes, and a non-statutory estoppel certificate. A profile is available for certificate generation when its record is active.

Active profiles have fully mapped required items and mandatory disclosures. A stub profile declares the jurisdiction and statute reference without claiming completeness, and the system will not generate a certificate under it. No stub exists today.

Each resale statute is re-verified against its official text on a 90-day cycle. A statute whose verification has lapsed fails the release, so a covered profile cannot ship resting on an unverified source. The release check covers thirteen of the fourteen code-defined profiles. Arizona and the six data-file profiles are not in it, so a lapsed statute behind one of those does not stop a release.

Active Profiles

The code defines 14 profiles across 10 states. The table lists those; the six data-file profiles are not in it.

The two Washington profiles are described in full below. The state pages carry the statutory references and current fee and deadline figures for the others.

Washington Condominium Act (wa_condo_64_34)

20 required disclosure items covering:

• Alienability restraints — right of first refusal or free alienability restrictions (a)
• Financial status — assessments, delinquency, special assessments (b)
• Association past-due obligations (c), (d)
• Other fees payable by unit owners (e)
• Anticipated repairs exceeding 5% of annual budget (f)
• Reserve fund amounts and designations (g)
• Annual financial statement and audit report (h)
• Balance sheet within 120 days on accrual basis (i)
• Current operating budget (j)
• Judgments and pending litigation (k)
• Insurance coverage description (l)
• Unit violations (m), declarant units (n), code violations (o)
• Leasehold terms (p)
• Governing documents (q)
• Warranty coverage (r)
• EV charging requirements (s)
• Reserve study absence disclosure (t)

Washington WUCIOA (wa_wucioa_64_90)

26 required disclosure items. Includes all items from the Condominium Act profile plus:

• Sale proceeds restrictions (q) — declaration restrictions on sale proceeds
• Cooperative tax deductibility (r) — cooperative-specific tax statement
• Common element sale or encumbrance (s) — pending sale of common elements
• Use, occupancy, and rental restrictions (t)
• Governing documents, board policies, and board and association meeting minutes from the last 12 months (u)
• Age-related occupancy restrictions (w)
• Conspicuous notice regarding community membership obligations (z)

The WUCIOA profile reflects the broader scope of the newer statute — it covers areas (cooperative provisions, use restrictions, meeting minutes, age restrictions) that the older Condominium Act does not require in the resale certificate.

Actual-Cost and Reasonable-Cost Fee Profiles

Five profiles use an actual-cost or reasonable-cost fee model instead of a statutory dollar cap:

These profiles resolve prep_fee_cap and update_fee_cap to None — the fee is the association's actual or reasonable cost of preparation, not a statutory ceiling.

California Notes

California's Davis-Stirling Act uses an "actual cost" model for certificate preparation fees rather than a statutory cap, and requires the association to provide a written fee estimate before doing the work (Cal. Civ. Code §4530(b)(2)).

Oregon Notes

Oregon's Planned Community Act (ORS 94.670) governs resale certificates for planned communities. The delivery deadline is 10 business days — a different unit of measure than Washington's 10 calendar days.

How Profiles Drive Generation

When a resale certificate is generated:

1. Profile selection: The caller specifies the compliance profile key (e.g., wa_condo_64_34). The registry returns the full profile definition.

2. Item enumeration: The generator iterates over the profile's required items. For each item, it uses the data_key to look up the corresponding data section builder.

3. Section assembly: Each data section builder queries production models (AR invoices, fund balances, insurance policies, etc.) and returns a structured data payload — or an "unknown" payload if the data is not available in the system.

4. Mandatory disclosure insertion: The profile's mandatory disclosure text blocks are included verbatim in the evidence snapshot.

5. Compliance check: After assembly, the generator computes coverage — how many required items have live data versus "unknown" payloads. The gap list identifies specific statute subsections with missing data.

6. Content hash: The complete evidence snapshot (including all data sections, mandatory disclosures, and compliance check results) is hashed with SHA-256.

The profile, not the generator, carries the jurisdiction-specific requirements. The same generator produces certificates under any profile, current or future.

Adding a New Jurisdiction

Activating a new compliance profile requires:

1. Statutory research: Map each required disclosure item from the statute to a code, statute reference, label, and data key
2. Data key mapping: Ensure each data key corresponds to a section builder that can produce the required data from CommunityPay's models
3. Fee and deadline parameters: Define preparation fee caps, update fee caps, delivery deadlines, and buyer review periods from the statute
4. Mandatory disclosures: Extract verbatim text blocks that the statute requires on the certificate
5. Profile activation: Define the profile in the legal data and mark its record active. It is then loaded into the database at the next release

The generation engine, snapshot assembly, compliance check computation, and hashing take the jurisdiction from the profile.

Helper Functions

The registry provides utility functions for common operations:

These functions filter out stub profiles by default. Forms and pages that display available profiles show only active profiles with fully mapped requirements.

This describes production controls as of October 2026. Controls evolve; request a current posture packet for diligence.