Decision-OS V5 Revised (SiriusA2): A Zero-Knowledge Confirmation Layer for Trajectory-Aware Human–AI Decision Safety

Decision-OS V5 Revised (SiriusA2) addresses a practical AI safety problem: how human oversight can prevent irreversible decisions from being executed under pressure, confusion, coercion, or panic. It is designed for safety-critical, non-medical decision support settings where a user may be authenticated, yet the execution path may still be unsafe. The framework proposes a human-in-the-loop confirmation layer for irreversible risk. Instead of allowing a valid user action to move directly into execution, SiriusA2 routes protected actions through auditable confirmation states such as Request, Observe, Hold, Approve, Reject, Stop Candidate, Execute, and Revoke. The core mechanism is a trajectory-aware duressₛcore. This score is not an intent classifier, diagnosis, truthfulness score, or autonomous veto. It is an operational control-routing signal used to detect when a valid execution path deviates from an ordinary decision trajectory and approaches irreversible harm. SiriusA2 preserves human final consent through two-step confirmation, an explicit revoke path, optional family multisig, and a Zero-Knowledge approval layer (310/320) that verifies authorization without exposing personally identifiable information. The duressₛcore does not replace ZK approval or multisig; it routes actions into the confirmation path, while ZK qualification and multisig provide independent authorization conditions before irreversible execution. The revised manuscript integrates the SiriusA Adoption Gate into the main paper. The gate provides a Hold-first confirmation path for irreversible, externally pressured, unusually urgent, or high-stake actions: Request → Observe/Hold → Approve/Reject → Execute/Revoke. A score-based Stop Candidate does not automatically become Stop or Freeze. Stop or Freeze requires an independent non-score condition, such as verified revoke input, ZK-qualified m-of-k approval, policy-defined guardian confirmation, or an emergency protocol condition. If no such condition is available, SiriusA intentionally prefers continued Hold and evidence preservation over an AI-only execution veto. This release also clarifies cold-start behavior, causal bridge support, baseline maturity, corrected event terms, disclosure boundaries for calibration-sensitive parameters, and non-PII audit requirements. Safety is operationalized through auditable state transitions, non-PII KPIs, five-line gate outputs, evidence packaging (ZIP + SHA256), and explicit prohibitions on automatic transmission, payment, or reporting. A minimal proof-of-concept gate exists as a public runtime artifact, demonstrating PASS / DELAY / BLOCK routing, conservative severity merging, evidence union, pre-execution checking, and auditable JSON outputs. Deployment-level validation, calibration, and domain-specific robustness remain future work. Gateway / series index: https: //github. com/shin4141/decision-os-paper Recommended read order: V5 Revised (SiriusA2) → V6 (PIC) → V8 (v2) Optional: V7 (AGI definition) Related repositories: - V5 Policy Pack / specification and adoption materials: https: //github. com/shin4141/paper-public- Gate engine / MMAR-L0: https: //github. com/shin4141/mmar-l0-core- SiriusA core runtime: https: //github. com/shin4141/siriusA-core SSOT: GitHub repository “decision-os-paper”. This PDF corresponds to the revised SiriusA2 release candidate committed to the SSOT repository. Release note: This revised release integrates the trajectory-aware duressₛcore definition, SiriusA Adoption Gate, ZK qualification layer, family multisig, independent non-score Stop conditions, non-PII audit structure, V4-compatible escalation interface, and proof-of-concept gate positioning into the main paper. Transparency / Author’s Note: https: //github. com/shin4141/decision-os-paper/blob/main/AUTHORSNOTE. md