V1 readiness
3 of 10 items pass
Still open: both co-editor seats filled, integrated changes published as a numbered ml-draft revision, chapter checked against neighbouring dps for terms, overlaps and conflicts, every must and should is testable or rephrased as guidance, all contributors acknowledged, no release blockers open from the readiness review, v1 candidate revision published before the freeze
Cross-Layer Resilience and Compromise Containment
Participants can visit any page, including a hostile one, without that page speaking for them, reading their communities, or redirecting their agents.
Overview
The Meta-Layer should preserve the integrity of identity, authority, interactions, and governance even when the websites, browsers, devices, networks, services, overlays, or AI systems it depends on are compromised – within explicitly declared trust boundaries and threat assumptions.
Why It Matters
DP24 defines how the Meta-Layer’s guarantees for identity, authority, and governance survive when a neighboring layer – a website, browser, device, network, overlay, or AI system – turns hostile.
Key Elements
Authority independent of content origin
A page, script, or document is a source of content, never of authority: compromise of a lower layer must not confer control over identity, communities, or agents.
Isolation and containment
Credentials and privileged operations stay isolated from host pages and sibling overlays; when one component is compromised, the damage is contained, evidence is preserved, and recovery begins.
Shared surfaces and anchor integrity
Several Meta-Layer clients share the same page through one participant-arranged launcher, and annotations stay attached to what their authors meant – or say so – when the page beneath them changes.
Current Draft
Workgroup
Join the active workgroup stewarding this property and participate in its evolution.