Access Enforcement & Breach
Access violations breaches sanctions and remedies
Bundle → Layer → Finding → Questions Incomplete
3 bundles · 6 layers · 0 findings · 0 questions
violation Noticing and investigating
signals
anomalies from the audit log and reports from owners
cases
opened proceedings, gathered evidence, referral state
resolution Consequences and redress
sanctions
consequences imposed on the violator
remedies
what the harmed party receives, from notification to erasure and restitution
standing The violator's ongoing status
complianceStatus
a grantee's current standing across all cases
reinstatement
the path back to good standing after remedies are fulfilled
Note: Legacy card: layers named, findings and questions never written.
Classifiers Filled
- Family
- World Models
- Category
- Cross-cutting context
- Entry kind
- mixin
- Navigation path
- NAV.XCT.ENF
- Domain
- XCT.ENF
- Industry
- Cross-industry
- Tags
- accessbreachenforcementxct.enf
- Also called
- S7
What it is Derived, awaiting review
This meta-model describes what happens when the cluster's promises are broken: reads outside scope, onward sharing, retention past the deadline, grants ignored after revocation.
Note: First sentence of the legacy card introduction.
Why it exists Filled
Access violations breaches sanctions and remedies
Distinguishing features Derived, awaiting review
- It is its own model because enforcement has a lifecycle and evidence discipline of its own, distinct from the contracts it protects and from the courts that decide contested cases.
What robots and AI may and may not do Missing, in the backlog
Not described yet. This gap is in the card backlog.
Moral aspects Derived, awaiting review
- It records signals, cases, established breaches, the sanctions imposed and the remedies delivered to the harmed party, plus each grantee's resulting standing.
- 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.
- breachNotification: the harmed owner is informed of an established breach touching their objects, with the case evidence they are entitled to.
Owners Filled
Steward
An enforcement registrar archetype keeps cases, sanctions and standing, acting alongside the courts (A19) that decide contested matters.
Links to other meta-models Filled
references
- world.accessContract - the violated instrument, its scope and its obligations define what counts as a breach.
- world.accessAudit - the append-only log is the primary evidence source; signals cite entries and proofs of inclusion.
- world.ownership - the harmed party is resolved through ownership records, including guardians acting for wards.
- world.privacyAggregation - public enforcement statistics are released only at cohort grain under its floors.
- world.disputeResolution - 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.
- iso-29100 - ALIGN: privacy principles, including redress, that remedy kinds trace to.
requires
- vr.wm-pol-010
- vr.wm-pol-014
- vr.wm-xct-004
- vr.wm-xct-005
What else AI and robots need to interact with it Incomplete
Identity and identifiers required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Direct properties not applicable Not applicable
Not applicable
Institutional or informational subject: no invented physical properties.
Recognition optional Missing, in the backlog
Not described yet. This gap is in the card backlog.
Capabilities and actions required Derived, awaiting review
- 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.
Legacy events listed as state transitions.
Hazards and failure modes optional Missing, in the backlog
Not described yet. This gap is in the card backlog.
Standards and interfaces required Derived, awaiting review
- 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.
- 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.
Context of use required Filled
- 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.
Sources Missing, in the backlog
Not described yet. This gap is in the card backlog.
Open questions
- Superseded by a researched world model? Map this legacy card to its successor or retire it.
Machine files
Provenance
legacy MMAS card (world-models v0.2) · legacy
Built from: models/world-s7-access-enforcement-and-breach/spec.yaml, models/docs/security-ownership-access/S7-access-enforcement-and-breach.md