HS‑Intent v1. 0 specifies a minimal, protocol‑friendly intent declaration extension for phase‑window coordination stacks (Timeverse / Phase‑Coordination Series). While Conventions/Q‑Address/TAQA define when an action is executed (cycle‑anchored, wrap‑safe phase windows verified in tick‑canonical integers), deployments also require a signable statement of what is being attempted for audit and policy gating. HS‑Intent defines a deterministic, signable object including: intentclassᵢd (namespaced action class identifier), intentₖind (EXECUTE / RESERVE / CANCEL / OBSERVE), riskₜierᵤ8 (declared risk tier), optional purpose (audit/UI), optional ttlcyclesᵤ32 (policy TTL horizon in cycles). HS‑Intent does not redefine execution semantics, does not provide cryptographic primitives, and does not grant authorization by itself. Integrity and anti‑replay are provided by the external Timeverse Security Profile. HS‑Intent is designed to compose with HS‑Bloch (quality gating) and HS‑bit Meter (consumption reporting), and is particularly useful for autonomous controllers (including AI schedulers) as a signed pre‑execution declaration consumed by policy engines. Normative dependencies: Conventions (10. 5281/zenodo. 18068999), Q‑Address (10. 5281/zenodo. 18068997), TAQA v2 (10. 5281/zenodo. 18070594), Timeverse Security Profile (10. 5281/zenodo. 18069423). Related: HS‑Bloch v1. 1 (10. 5281/zenodo. 18216116), HS‑bit Meter v1. 0 (10. 5281/zenodo. 18071687).
Tarik Ouardi (Sun,) studied this question.