The Specification (lives @ ANCR-WG Github) and is updated to this page for community comments and review,

...

0PN - acronym for Open x3, Open Specification, for Open ISO/IEC Standard, with Open Commons Software and Licensing - which is required for digital transparency standard to scale.

Protocol Scope Outline

this Protoocl 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 documentstandard, apply with whcih the ANCR WG Specs has been written for.

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

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

  • Specifically Article 12, 30, 80

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

• Follow Providing the Consensus protocol for the operations of the WG and engineering digital consent policy infrastructure

...

• 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.