EX-ST-01-UI-TRANSLATION-SPEC.md

Status: DRAFT — NON-AUTHORITATIVE Location: docs/governance/

1. Purpose of UI Translation Specification

• The UI MUST strictly reflect governance states as defined in EX-ST-01-STRUCTURAL-SKELETON.md, EX-ST-01-FORMS-PLACEHOLDERS.md, and STEP-06-STATE-MACHINE-EX-ST-01.md.
• The UI MUST NOT redefine, shortcut, or imply completion, approval, or correctness of settlement.

2. State-to-Visibility Rules

• For each settlement state, the following role-based visibility rules apply:
  • Payer Authority: MAY see all settlement records relevant to their initiated transactions. MUST NOT see verifier notes for unrelated settlements.
  • Payee: MAY see settlement status and confirmation of their own payments. MUST NOT see other payees' records or internal verification notes.
  • Financial Verifier: MAY see all submitted evidence and verification records. MUST NOT see or alter settlement confirmation without proper authority.
  • Governance / Audit Oversight: MAY see all records in a read-only, logged manner. MUST NOT alter or annotate records post-settlement.
• Confidentiality for financial evidence and verifier notes MUST be preserved at all times.

3. Action Constraints

• Actions shown in the UI MUST map directly to governance transitions only.
• No implicit or automatic actions are permitted.
• All actions MUST be role-gated and state-gated according to governance artefacts.

4. Terminology Constraints

• Allowed labels: "Settlement Initiated", "Evidence Submitted", "Under Verification", "Anchoring Proof Available", "Settled"
• Prohibited labels: "Approved Payment", "Auto-confirmed", "Winner", "Success Guaranteed", "Completed Automatically"
• All UI copy MUST use governance and blockchain terminology only: Settlement, Anchoring, Anchoring Proof.

5. Verification vs Confirmation Safeguards

• The UI MUST clearly separate:
  • Evidence submission
  • Verification decision record
  • Settlement confirmation record
• Approval ≠ verification ≠ settlement. UI MUST NOT conflate these concepts.

6. Anchoring Presentation Rules

• Anchoring Proof MUST be presented as cryptographic proof only.
• Anchoring MUST NOT be presented as approval, correctness, or completion.
• Anchoring MAY be unavailable without blocking governance decisions (UNDEFINED if policy requires).

7. GDPR / ISO 27001 Overlays

• Role-based visibility and confidentiality principles MUST be maintained for:
  • Personal data
  • Financial evidence
  • Verifier reasoning
• Audit access MUST be read-only and logged (conceptual, not technical).

8. Validation Checklist for UI Developers

• UI MUST:
  • Apply ISO 27001 confidentiality for all sensitive data
  • Ensure ISO 9001 traceability for all settlement records
  • Respect independence and segregation of duties
  • Use only allowed terminology
  • Never imply approval, correctness, or automatic completion
  • Apply role-based and state-based visibility

9. UNDEFINED Items

• Policy for anchoring availability in case of incomplete settlement: UNDEFINED — GOVERNANCE DECISION REQUIRED
• Any additional role-based visibility exceptions: UNDEFINED — GOVERNANCE DECISION REQUIRED