HS‑Core Profile v1.0 — Deterministic Policy Combination of Intent, Quality, and Cost for Phase‑Window Actions (Timeverse / Phase‑Coordination Series)

HS‑Core Profile v1.0 specifies a minimal, deterministic policy evaluation layer for the Timeverse / Phase‑Coordination stack. While Conventions/Q‑Address/TAQA define when actions may execute (cycle‑anchored, wrap‑safe phase windows verified in tick‑canonical integers) and the Timeverse Security Profile defines integrity, canonical encoding, and anti‑replay, deployments still require a normative decision layer that determines whether an action should proceed. HS‑Core combines three independent signals: HS‑Intent — what is being attempted (intent class + kind) and declared risk tier, HS‑Bloch — quality/coherence gating (including optional vector policy and tick‑freshness), HS‑bit — alignment cost signal for budgets and rate limits (consumed via a fixed‑point integer encoding). This profile defines: a signable HS‑Core policy profile object (risk‑tier rules, optional allow/deny lists, quality floors, cost budgets), a signable HS‑Core verdict object bound to an action context (scope, cycle index, optional action hash), fixed‑point cost encoding (milli‑HS‑bits) to avoid floating‑point enforcement, a deterministic evaluation algorithm producing one of: ALLOW / DENY / DELAY / DEGRADE (DEGRADE requires an explicit degrade_mode_id). HS‑Core does not redefine execution semantics, does not define cryptographic primitives, and does not provide scheduling algorithms. It is designed to be embedded in signed contexts under the active security_profile_id and evaluated alongside TAQA execution gating. Normative dependencies: HS‑Intent v1.0 (10.5281/zenodo.18216336), HS‑Bloch v1.1 (10.5281/zenodo.18216116), HS‑bit Meter v1.0 (10.5281/zenodo.18071687), Conventions (10.5281/zenodo.18068999), Q‑Address (10.5281/zenodo.18068997), TAQA v2 (10.5281/zenodo.18070594), Timeverse Security Profile (10.5281/zenodo.18069423).