wiki/projects/semantic-collapse-theory/loop-series/pdsp-and-sovereignty

PDSP and Sovereignty

wiki/projects/semantic-collapse-theory/loop-series/pdsp-and-sovereignty/index.md

Rendered from markdown source. Open raw source on GitHub.

PDSP and Sovereignty

Parent lineage: Semantic Collapse Theory / Loop Series

This cluster covers the personal data sovereignty protocol, its LoopLink-based variant, the integration bundles, and the evolving PDSP-lite specifications.

Current Shape

  • 7 PDSP and sovereignty documents.
  • 3 nested lineage pages organize those documents.

Nested Lineage Pages

Representative Files

Working Read

This branch now separates into the core sovereignty protocol, the integration bundles, and the PDSP-lite spec line. The split follows the document titles closely and keeps the implementation path visible.

It is the sovereignty branch of the loop series. The documents here hold the protocol core, the bundle-level application layer, and the lighter spec line that makes the branch easier to carry forward.

The broader semantic role of this branch is to treat PDSP as a sovereignty attractor rather than a single spec family. It is the place where personal data, trust, and subjective auditability are organized into a loop-based trust model.

Because PDSP depends on LoopLink transport and touches the governance logic of SCT, it is one of the main bridges between the loop stack and the origin/governance material. The core manuscript pair now has markdown source copies in artifacts/standard-named/, so this branch can prefer markdown for the main protocol reading while leaving the remaining spec and bundle line items in archive form for now. The PDSP-lite specs and integration bundles now have markdown source copies as well, which makes the branch fully indexed across the core, transport, and implementation layers.

Semantic Role

This branch is the source of the protocol family as a whole. It separates the sovereignty substrate, the packet-level spec, and the integration bundles while keeping them tied to the same trust problem.

The important move is not just versioning. It is that the documents show the same sovereignty idea at three scales: protocol core, minimal interoperability surface, and integration packaging.

Core Claims

  • Trust should be auditable without becoming centralized.
  • Loop-scoped identity is more useful here than persistent global identity.
  • Packet-level interoperability is only meaningful if the trust loop remains legible.
  • The core and the implementation layers are different expressions of the same sovereignty model.

Mechanism Stack

  • PDSP Core names the subjective trust graph and the sovereignty substrate.
  • PDSP-lite Specs define the minimal packet and validation surface.
  • Integration Bundles translate the protocol into application-facing dialogue and bridge context.
  • LoopLink provides the transport and presence layer beneath the rest of the branch.

Implications

  • Readers can move from theory to implementation without changing the trust vocabulary.
  • The branch can support both protocol exploration and concrete system design.
  • Civic, medical, and AI-human use cases all remain downstream of the same sovereignty pattern.

Dependencies

Open Questions

  • How do protocol variants preserve coherence across the shared trust vocabulary?
  • What revocation or decay semantics should be surfaced centrally?
  • How much witness structure belongs in the substrate versus the bundle layer?
  • Can loop states be migrated without weakening provenance?

Related Concepts

Related Links

Next Actions

  1. Keep the three nested lineage pages stable.
  2. Split again only if one of the three tracks develops another durable seam.