Skip to content

README.md

Latest commit

 

History

History
86 lines (63 loc) · 3.86 KB

README.md

File metadata and controls

86 lines (63 loc) · 3.86 KB
Raw

Architecture decision records

WE BUILD maintains a lightweight architecture decision record (ADR) for each software-related decision affecting interoperability.

Propose new ADRs using the template. Announce them to the Architecture group in the Portal to get feedback to understand the consortium’s opinion.

ADR overview

  1. Publish consortium trusted lists
  2. Baseline protocols
  3. Specify PID and eAA formats
  4. Provide EBWOID as a stable minimal basis
  5. Wallet Unit Attestation and Lifecycle Management (For European Business Wallet)
  6. Replace LPID with EBWOID
  7. Deliver business wallet data using QERDS
  8. Attestation Revocation Mechanism
  9. Separate QERDS registry from relay
  10. Structure the European Digital Directory as identification, discovery, and connection
  11. Separate attestations, documents, and data in EBW
  12. Acceptance of Self-Issued Attributes
  13. Atomic Granularity for Mandate-Related Attestations
  14. EAA Extension for the EDD
  15. EBW EAA Exchange Automation
  16. Role-Based vs Service-Based Authorization
  17. Support for Sole Trader Representation
  18. QEAA Attestations and QERDS Documents
  19. Credential Offer Endpoint Registry and Lookup Service
  20. Business Wallet Unit Attestation based on TS3
  21. Pre-flight CS
  22. Pseudonyms for User Accounts

Supporting analysis

ADR process for WE BUILD

ADRs are handled through a timeboxed process to avoid proposals remaining open indefinitely.

1. Intake – next Architecture Group (AG) meeting (max. 14 days)

  • checks that the ADR is ready for review;
  • identifies required stakeholders/reviewers; and
  • identifies whether additional approval is required for high-risk decisions.

2. Review – max. 12 days

Required stakeholders are requested as reviewers in GitHub.

Feedback should identify any blocking issues. No response by the deadline is treated as no blocking objection.

3. Decision – next AG meeting

The AG decides to:

  • Approve – no unresolved blocking issues → merge.
  • Iterate – blocking issues remain → one iteration allowed.
  • Reject – insufficient support, maturity or relevance → close.

Additional stakeholder engagement may exceptionally be requested if a required stakeholder has not had a reasonable opportunity to respond.

After one iteration, the ADR is approved or rejected.

stateDiagram-v2
    [*] --> Intake: PR opened by any consortium member
    Intake --> Review: Ready for review
    Intake --> Rejected: Not ready / out of scope

    Review --> Decision: Max. 12 days

    Decision --> Approved: No blocking issues
    Decision --> Iteration: Blocking issues
    Decision --> Rejected: Insufficient support

    Iteration --> Approved: Issues resolved
    Iteration --> Rejected: Issues remain

    Approved --> [*]
    Rejected --> [*]
Loading