ANCR Consensus Policy for Personal Data Control, is a policy used to cover the data governance of authentication and authorisation with directed consent, and consent by default, technical policy, pracitce and security measures.

The Consensus Policy refers to the legal and standards based framework, the ANCR WG specification are contributing too. Is a comprehensive and mature data governance framework, applicable to all stakeholders.

In Particular Convention 108, and 108+, (Ratified when legal jurisdictions, implement enforceable privacy law, like in Quebec)

There are always exceptions to the rule, the international framework, provides 6 legal justifications, along with exceptions and how to log data processing activities.

In terms of the Common’s Regulated Digital Public Infrastructure, these rules much like the Magna Carta, are the international adequacy baseline, which all data governance policy and practices can be measured against. Applicable to all parties. And like the Forrest Charter 1217, which followed the Magna Carta 1215, the Consensus policy is the Community / Commons policy, which is co-created in this governed data commons mediated space referred to as data governance consensus.

The ANCR (Anchored Notice and Consent Receipt) is a legal notice record and receipt format, and log specifcaton, which generated by providing an open notice. Binding the notice, and the interaction into a record, which is linked to a receipt, consiting of specified meta-data which is required by Commonwealth Treaty in Convention 108+. for legal proof of notice, and the use of consent as a legal authority, for an individual to self-identify, and manage the control, access, mobility and aggregation of micro-data. (referring, to attributes and identifiers) in so much as a consent token can then be the mechanism which controls the aggregation and use of micro-data.

This framework of rules is referenced here is free to access, authoritative law and standard, developed for an International Digital Commonwealth, represted in a multi-country Treaty, from the Council of Europe 108+. This Treaty, which mirrors the GDPR, is coming into force in 2025 as privacy laws are legislated by participating countries.
In the ANCR WG we work with the ISO/IEC 29100, security and privacy techniques, 29184 Online privacy notice and consent standard 2020, setting a sample framework of controls for

the data control governance policy framework core set of data governance laws, standards, rules and practices that are used to frame data governance and security and create a consensus policy to enable distributed and decentralised governance.

Protocol Outline Notes

this Protocol is defined by law, in particular

• Convention 108+, (Art 14, 31, 80) international baseline, and the consent policy is further informed by the national, regional and personal consent.

• the records and receipts use ISO/iEC 29100 Framework as core technical standard, with whcih the ANCR WG Specs has been written for.

• Utilise the 29184 and 27560 and reference documents for record structures and controls

• Conv 108+ (Mirror of GDPR) as the baseline ruleset to measure compliance against

  • Specifically Article 12, 30, 80

  • Assured, Mirror Records of Processing Activies (to digitally twin proof of notice and evidence of consent for digital identity management protocols.

• Providing the Consensus protocol as a process and practice methodology to engineer consent with consensus.

ANCR Practice

1. ANCR WG Policy and WG Call Practice

   1. To start each call

      1. Walk through the overview of the ANCR Consensus Protocol spec.

      2. Link this to an overview of the ANCR WG, ANCR WG Specs, Common Law, Standards framework, and Goals.

      3. Actions

         1. Add the consensus protocol to the Charter as a way for operating the group.

         2. Write an ANCR WG Consensus Protocol Agreement (like the Kantara GPA) for agreeing to operate using this protocol and ettiquette, that is co-decided,

         3. Run the consensus protocol in practice in ANCR WG meetings - running a formal meeting process for ANCR WG

         4. Actions for Next 0PN Consensus Protocol Call

            1. Add Policy for operating Consensus Protocol:

            2. Resetting, renewing, or restarting consensus once it's broken.

            3. Ethics of operating the Consensus Protocol.

            4. Process for setting purpose, scope, roles, and activities.

            5. Meeting process for entering contributions.

2. in ANCR CP Policy Document:

   1. Assign Role - editor of - ANCR Consensus Protocol Policy. (Mark To Start WIth)

      1. editor role,

         1. mandate, practice for making and maintaing policy and policy discussion

         2. Start/Maintain ANCR WG - Contribution Ledger.

      2. Consensus Ceremony - With consensus protocol - onboard new and existing workgroup members, and contributions in call

3. Roles and Etiquette:

   1. Editor Role

      1. Like secretary - documents policy, its purpose, its reference, the ettiquet for respectng the policy and also the notice, notification or disclosure clauses for this role

         1. add - aditional tasks of the role and reference existing etiquette in the WG practice to develop and maintain these documents.

4. Specification, Guide for Use, and CPF Contributions:

   1. Aim is to create framework documentation, in addition to making framework components, with limited scope of the ANCR WG - as case study

   2. Develop a guide/support/contributions process for projects and organizations that want to use and implement the ANCR Consensus Protocol Specification.

5. sing consensus protocol - onboard new and existing workgroup members, and contributions in call

Appendix Example ANCR Policy (see ANCR Consensus Policy )

• Policy, description, ANCR WG Etiquette, and then notice, notifications, disclosure and policy clause, legal reference - and process.

•