Status: DRAFT — NON-AUTHORITATIVE Date: 2026-02-09

1. Purpose of UI Translation Specification

• The UI MUST reflect governance states as defined in STEP-06-STATE-MACHINE-EX-TN-01.md.
• The UI MUST NOT redefine, shortcut, or bypass governance logic.
• This document provides guardrails for UI representation only; it is not a UI design or workflow specification.

2. State-to-Visibility Rules

For each governance state, the following visibility rules apply:

| State | Role | MAY See | MUST NOT See | |----------------------|---------------------|-----------------------------------------------|----------------------------------------------| | DRAFT | Tender Creator | Draft details | Other bids, evaluation notes | | | Other Bidders | NOTHING | Draft details, other bids | | PUBLISHED | All Bidders | Tender notice, eligibility criteria | Other bids, evaluation notes | | BIDDING_OPEN | All Bidders | Own bid submission status | Other bids, evaluation notes | | | Tender Committee | List of bidders (no content) | Bid content before opening | | BIDDING_CLOSED | Tender Committee | All bid submissions (content) | Bidder identities (if anonymized) | | | Bidders | Own bid status | Other bids, evaluation notes | | UNDER_EVALUATION | Evaluation Committee| All bid content, evaluation forms | Bidder access, non-committee access | | | Bidders | Notification of evaluation phase | Evaluation content, other bids | | SELECTION_PROPOSED | Approver | Evaluation summary, selection proposal | Evaluation details to non-approvers | | | Bidders | Notification of selection proposal | Evaluation content, other bids | | APPROVED | All Bidders | Award notice, closure summary | Evaluation details, non-public records | | REJECTED | All Bidders | Rejection notice, closure summary | Evaluation details, non-public records | | CLOSED | All Bidders | Public closure record | Confidential/restricted records |

• Bid content MUST NOT be visible to any party before formal opening.
• No cross-bid visibility for bidders at any stage.

3. Action Constraints

• Actions MAY be exposed only if they map to explicit governance state transitions.
• UI MUST NOT suggest, imply, or enable outcomes or decisions not present in governance.
• Request, evaluation, and approval actions MUST be separated by role and state.

4. Terminology Constraints

• Allowed: "Tender published", "Bid submitted", "Evaluation in progress", "Selection proposed", "Awarded", "Anchoring proof available", "Settlement reference".
• Prohibited: Terms that imply system-made decisions, automatic outcomes, or real-world action taking.

5. Evaluation & Selection Safeguards

• No implicit or visual ranking of bids in UI.
• No early disclosure of evaluation results.
• Approval MUST be clearly separated from evaluation.
• UI MUST NOT imply single-person decision authority.

6. Anchoring & Settlement Presentation Rules

• Anchoring MAY be shown as cryptographic proof only (e.g., "Anchoring proof available").
• Anchoring MUST NOT be presented as approval, selection, or decision.
• Settlement references MUST be informational only.

7. GDPR & ISO 27001 Overlays

• Bid confidentiality MUST be preserved at all times.
• Role-based visibility MUST be implemented for all sensitive data.
• Data minimization and access control principles SHALL apply to all UI displays.

8. UI Validation Checklist

• UI MUST reflect only governance states and transitions.
• UI MUST NOT use prohibited terminology.
• UI MUST NOT expose confidential or restricted records to unauthorized roles.
• UI MUST NOT imply outcomes, rankings, or decisions not present in governance.
• UI MUST pass review for GDPR and ISO 27001 compliance.

9. UNDEFINED Items

• Public disclosure policy for closed tenders: UNDEFINED
• Handling of anonymized vs. identified bids: UNDEFINED
• Policy for post-closure access to evaluation records: UNDEFINED
• Any additional UI patterns not explicitly covered: UNDEFINED