@vess-id/ai-identity 0.16.0-alpha.4 → 0.16.0-alpha.5
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/index.d.mts
CHANGED
|
@@ -1158,6 +1158,19 @@ interface VcSchedulingDelegationClaim {
|
|
|
1158
1158
|
* which negotiation the write was for.
|
|
1159
1159
|
*/
|
|
1160
1160
|
itemId?: string;
|
|
1161
|
+
/**
|
|
1162
|
+
* Scheduling Phase 2 §A / Plan A' (Task A6, spec §7 / §8.3) — the id of the
|
|
1163
|
+
* standing booking link this automated calendar write was booked THROUGH. Present
|
|
1164
|
+
* on the pull-type booking confirm path (a visitor 1-clicks a slot from an
|
|
1165
|
+
* owner's booking link); ADDITIVE / OPTIONAL — absent on the push-type
|
|
1166
|
+
* `scheduling.request` / confirm (§7) / hold (§6) contexts, which have no link.
|
|
1167
|
+
*
|
|
1168
|
+
* AUDIT-ONLY, same principle as the rest of this claim: no enforcement gate
|
|
1169
|
+
* reads it. The audit evidence names which booking link the write belonged to
|
|
1170
|
+
* so an auditor can reconstruct the standing pull-type authority; invoke-time
|
|
1171
|
+
* authorization is unaffected (#884 unchanged).
|
|
1172
|
+
*/
|
|
1173
|
+
linkId?: string;
|
|
1161
1174
|
/**
|
|
1162
1175
|
* Scheduling Phase 2 Plan B (Task 3 bakes this) — the Policy Registry id of
|
|
1163
1176
|
* the signed delegation-policy document the auto-issuance relied on. Lets an
|