Access Enforcement & Breach

Findings

Catalogue-native findings must describe the information grouped by each layer. This legacy version does not declare them separately.

Questions & artifacts

Questions, artifact requirements and serial naming rules are required by Vercy vNext; they remain unassigned in this reference version.

Dimension & namespace

• REFERENCE `world.accessContract` (S2): the violated instrument, its scope and its obligations define what counts as a breach.
• REFERENCE `world.accessAudit` (S4): the append-only log is the primary evidence source; signals cite entries and proofs of inclusion.
• REFERENCE `world.ownership` (S1): the harmed party is resolved through ownership records, including guardians acting for wards.
• REFERENCE `world.privacyAggregation` (S5): public enforcement statistics are released only at cohort grain under its floors.
• REFERENCE `world.disputeResolution` (A19): contested cases are decided by the courts model; this model records referrals and receives outcomes.
• imports: odrl (ALIGN): duty, prohibition and remedy vocabulary mapped onto obligations, sanctions and redress.
• imports: iso-29100 (ALIGN): privacy principles, including redress, that remedy kinds trace to.

Canon, patches & standards

• REFERENCE `world.accessContract` (S2): the violated instrument, its scope and its obligations define what counts as a breach.
• REFERENCE `world.accessAudit` (S4): the append-only log is the primary evidence source; signals cite entries and proofs of inclusion.
• REFERENCE `world.ownership` (S1): the harmed party is resolved through ownership records, including guardians acting for wards.
• REFERENCE `world.privacyAggregation` (S5): public enforcement statistics are released only at cohort grain under its floors.
• REFERENCE `world.disputeResolution` (A19): contested cases are decided by the courts model; this model records referrals and receives outcomes.
• imports: odrl (ALIGN): duty, prohibition and remedy vocabulary mapped onto obligations, sanctions and redress.
• imports: iso-29100 (ALIGN): privacy principles, including redress, that remedy kinds trace to.

Artifact formats & serial data

Format-independent core. Concrete artifact formats and naming prefixes are not declared in this legacy version.

Policies & accepted processes

• `breachNotification`: the harmed owner is informed of an established breach touching their objects, with the case evidence they are entitled to.
• `courtReferral`: the evidence package and case record are transmitted to the adjudication model under chain-of-custody terms.
• `standingCheck`: a prospective grantor queries a grantee's current standing before entering a new grant; detail beyond the standing class is not returned.

Read / add / edit / delete

CRUD procedures and interface bindings are not declared in this legacy version.

Ownership, roles & access

An enforcement registrar archetype keeps cases, sanctions and standing, acting alongside the courts (A19) that decide contested matters. It owns process records only: evidence stays anchored in S4, the harmed owner's rights stay theirs, and reads of enforcement data follow S1/S2 like everything else.

Objects

• `violationSignal`: a raw indication of possible violation; key attributes: source (audit anomaly, owner report, self-report), time, referenced entries.
• `enforcementCase`: an opened proceeding; key attributes: parties, evidence references, state, referral state.
• `breach`: an established violation of an access contract or of catalogue rules; key attributes: contract reference, kind (out-of-scope read, onward sharing, retention breach, post-revocation use), severity, established by.
• `sanction`: an imposed consequence; key attributes: kind (contract suspension, grant ineligibility, penalty under applicable law), duration, imposing body.
• `remedy`: redress delivered to the harmed party; key attributes: kind (notification, erasure confirmation, correction, restitution), delivered time, evidence.
• `complianceStanding`: a grantee's current status; key attributes: standing class, active sanctions, since.
• `reinstatementRecord`: the restoration of standing; key attributes: conditions met, verified by, effective time.

Relationships

• `violationSignal` -> triggers -> `enforcementCase` (0..1): signals may be dismissed on triage or may open a case.
• `enforcementCase` -> establishes -> `breach` (0..1): a case ends in an established breach or a dismissal, never both.
• `breach` -> violates -> `accessContract` (1..1): every breach names the S2 instrument, or the catalogue rule, it broke.
• `sanction` -> imposedFor -> `breach` (*..1): consequences attach to established breaches, not to accusations.
• `remedy` -> redresses -> `breach` (*..1): the harmed owner's redress is tracked to completion per breach.
• `complianceStanding` -> summarizes -> `sanction` (0..*): standing is the live rollup of a grantee's active sanctions.
• `reinstatementRecord` -> restores -> `complianceStanding` (1..1): reinstatement is itself an evidenced act, not a decay.

Events

• `signalRaised`: an anomaly or report suggested a violation.
• `caseOpened`: triage found the signal credible and a proceeding began.
• `caseReferred`: a contested or grave case was handed to the courts with its evidence package.
• `breachEstablished`: a violation was found proven, by the enforcing body or by a court.
• `sanctionImposed`: a consequence took effect against the violator.
• `remedyDelivered`: the harmed party received their redress and it was evidenced.
• `caseDismissed`: a case closed without an established breach.
• `standingReinstated`: a violator returned to good standing after fulfilling conditions.

Projections

• `ownerCaseView`: all signals, cases and outcomes touching my objects; omits every other owner's matters.
• `standingBadge`: a grantee's current standing class only; omits case detail and history.
• `enforcementStatistics`: cohort-grain counts of breaches, sanctions and remedies via the S5 machinery; omits all parties.