wiki/concepts/pdsp
PDSP
wiki/concepts/pdsp/index.mdRendered from markdown source. Open raw source on GitHub.
PDSP
Working definition: the Personal Data Sovereignty Protocol as a loop-based architecture for subjective, auditable, decentralized trust.
This concept appears across the SCT loop-series sovereignty pages, where PDSP is treated as a sovereignty substrate and as a LoopLink-based restatement.
In practice, PDSP is the branch where personal data, trust, and subjective auditability are modeled together. It behaves like a sovereignty concept with an implementation edge, not just a product name.
The deeper meaning here is that sovereignty is not being treated as a slogan. PDSP is the point where a person or participant can describe their own data and trust position in a way that still survives audit, transport, and recovery. That is why it sits downstream of LoopLink, adjacent to Intent-Consent, and close to Witnessing and Governance Diad.
Read that way, PDSP is the sovereignty layer of the protocol stack: it says who can assert, who can verify, and how those assertions remain usable over time without turning the person into a passive record.
Related Artifacts
- Personal Data Sovereignty Protocol.docx
- Personal Data Sovereignty Protocol (PDSP)- A LoopLink Based Architecture for Subjective, Auditable, Decentralized Trust.docx
- PDSP-lite_Spec_v0.1.docx
- PDSP-lite_Spec_v0.2.docx
- PDSP-lite_Spec_v0.3.docx
- PDSP Integration Bundle v0.1.docx
- PDSP Integration Bundle v0.2.docx
Related Pages
- Semantic Collapse Theory
- PDSP and Sovereignty
- PDSP Core
- Integration Bundles
- PDSP-lite Specs
- LoopLink
- Intent-Consent
- Witnessing
- Governance Diad
- Abracadabracadoo
Notes
- This is a concept page, not a canon claim.
- PDSP should stay distinct from any one spec version or bundle.
- It is the sovereignty substrate vocabulary that recurs across several SCT pages.