<aside> <img src="notion://custom_emoji/a9e82583-b24a-4a1a-acd2-b871fcb71bd8/30835fe7-dd4a-80c8-a244-007ad12a35e5" alt="notion://custom_emoji/a9e82583-b24a-4a1a-acd2-b871fcb71bd8/30835fe7-dd4a-80c8-a244-007ad12a35e5" width="40px" />

Status: Draft.

Purpose: Set the behavioural and governance rules for participation in development and implementation of Digital Public Transparency Infrastructure (DPTI) work.

Digital Transparency Code of Conduct

This Code of Conduct is paired with:

• ‣

• ‣ </aside>

• pinciple note - operational transparency logic is the order of information objects according to what is intuitively human usable in context

1. Scope

This Code of Conduct applies to all 0PN Lab activities that produce, review, publish, or operate DPTI artefacts.

2. Core conduct rules

• Treat Digital Transparency Infrastructure as regulatory capacity infrastructure, not a compliance marketing asset.
• Default to evidence-grade statements. If something is not yet adopted or verified, label it clearly.
• Do not frame surveillance-enabling patterns as “digital consent.”
• Respect rights and licensing rules for all contributions.

3. Evidence discipline (Transparency by Default)

• When discussing “digital consent,” always state the evidence stage target (A self-stamped receipt, B + notice event log, C bilateral receipt).
• Do not claim that bilateral receipt implies a notice event log unless explicitly stated.

4. Contribution and rights discipline (Contribution Hub)

• Contributions must be logged with Rights basis and Rights notes.
• Normative specifications default to OPN-RF-RAND (spec/IPR) unless explicitly stated otherwise.

5. Canonical specification reference

The current internal draft reference for ISO/IEC 27560-1 Universal Notice Receipt Profile v1.01 is:

• ISO/IEC 27560:2023-1 Notice & Consent Receipt information structure
• GitHub-ready rendering: ‣

6. Enforcement (v0.1)