Audit vocabulary for a change to the compliance boundary itself

Featurekamo-shared-library
Shipped
August 4, 2026 at 3:55 AM UTC
Author
Kamo
Commit
4d5b119

Adds PhiResourceType.ORGANIZATION and PhiAccessKind.CONFIGURE so that turning Organization.handlesPhi on or off can be recorded as what it is. Every existing resource type names a person's record. Filing a change of the tenant's compliance posture under one of them would put a lie in the §164.528 accounting of disclosures, and "when did this tenant become a covered entity's business associate" is the question the rest of the trail is scoped against — it needs its own row shape, not a borrowed one. CONFIGURE fails closed for a different reason from the bulk kinds: nothing is disclosed, so refusing costs the operator a retry, while a boundary that moved with no record of when is the state a §164.402 assessment cannot reconstruct. No schema implication. phi_access_log.RESOURCE_TYPE and ACCESS_KIND are plain VARCHARs created by PhiAccessLogTableMigration with no enum whitelist CHECK, so neither constant needs a KamoInitializer run before it can be inserted, and no entity or @Column is touched. Verified no exhaustive switch over either enum exists in any service.

All changes

Like what you see shipping?

Every one of these updates lands in your workspace automatically. Start free and watch it grow week after week.

Start Free ForeverView Pricing