--- 0.2
+++ 0.3
@@ -138,6 +138,13 @@
* **FG-TIDA/themes#27 and PR #28 (verifier-side requirements in regulated workflows).** Of the change-event record it
proposes, its drafter wrote that the record-side requirements in themes#1 "define where this record belongs; this
item specifies what the verifier must be able to read from it" (@zhaoxinghua09-cell, PR #28, 15 October 2026).
+* **Verifier-side interface to the record requirements (linked contribution record).** Four clauses, VR1 to VR4, on
+ the report a verifier makes: each check as a pair of who performed it and against what; the moment evaluated against;
+ what a pass claims and within what boundary; and the report as a claim the next party assesses. The record "adds
+ nothing to R1–R8 and alters nothing in them", and it stands beside this document, under its author's name
+ (@zhaoxinghua09-cell, PR #46, 16 November 2026):
+ https://github.com/LGD-Eval/evaluation-protocol/blob/f66c4658fd1c99b1e6fef99b99eed3865dc8e45f/FG-TIDA-AAR-VERIFIER-SIDE-INTERFACE.md.
+ Whether the four clauses move into this work item is for the group to decide.
* **WG0, Use Cases and Terminology.** Use cases #7 (@syedofc) and #12 (@danyka-icam) supply the cases for D2.
* **Format work.** Encodings and profiles for carried claims belong to the bodies that specify formats. The thread
named the Internet Engineering Task Force (IETF) Remote Attestation Procedures (RATS) architecture and the Entity
@@ -286,6 +293,11 @@
- —
- TIDA
- Incubation (proposed)
+ * - 0.3
+ - Two co-authors and a contributor added; a linked contribution record listed
+ - —
+ - TIDA
+ - Incubation (proposed)
To access this Document as a PDF, open the published documentation site in your web
browser and click the PDF download link, or navigate directly to
@@ -307,11 +319,20 @@
* - Syed Amir Hamza
- Forkit AI
- GitHub @syedofc
+ * - Nika Novak
+ - ICAM Research Programme
+ - GitHub @danyka-icam
+ * - Xinghua Zhao
+ - Independent expert
+ - GitHub @zhaoxinghua09-cell
Contributors. The requirements come from the open thread on FG-TIDA/themes#1. Its originating proposer is Oleh
Vasylenko (@OlehVasylenko2000), Management Company Elixir LLC (Ukraine), who takes part as proposer and reviewer.
-@danyka-icam co-drafted the lineage requirements and cases. Co-author Syed Amir Hamza (@syedofc) co-drafted the
-identity and state continuity requirements (R8) and contributed use case #7. Every clause in
+Co-author Nika Novak (@danyka-icam) co-drafted the lineage requirements and cases and contributed use case #12.
+Co-author Syed Amir Hamza (@syedofc) co-drafted the identity and state continuity requirements (R8) and contributed use
+case #7. Co-author Xinghua Zhao (@zhaoxinghua09-cell) is named for the null-case refinement on R5 and for the linked
+contribution record on the verifier side (:ref:`chapter-relation`). @Abracadabrastartup (DEUSPROOF) raised the point
+recorded under open question 12, an asserted or witnessed moment (a possible R7.2a). Every clause in
:ref:`chapter-requirements` names its author.
Keywords
@@ -355,9 +376,9 @@
Note
----
-This document is a proposal for a new work item, to be submitted to FG-TIDA Incubation by 22 November 2026 as an
-input to the first FG-TIDA meeting (Paris, 30 November – 1 December 2026). It is not yet registered, and it is not
-adopted Focus Group text. The requirement text it summarises
+This document is a proposal for a new work item, submitted to FG-TIDA Incubation on 15 November 2026 as an input to
+the first FG-TIDA meeting (Paris, 30 November – 1 December 2026). The TIDA DataTracker records it as contribution
+FG-TIDA-INCUBATION-003, state Submitted. It is not adopted Focus Group text. The requirement text it summarises
stands in the posted comments listed in :ref:`chapter-annexes`.
.. Intellectual Property Rights — section commented out. To restore it, remove the