titan/atlas-iac
3
0
Fork 0
Code Issues Pull Requests 9 Actions Packages Projects Releases Wiki Activity

docs(hux): record enforcement rollback and re-enable checklist

Browse Source 
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BvMSXH8VH2tMWXanb8SJdf
This commit is contained in:
jenkins 2026-08-24 10:56:26 -03:00
parent 1793903f5e
commit eebc5e6de6
1 changed files with 18 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
docs/hux/HANDOFF.md
View File

@ -465,3 +465,21 @@ Remaining, deliberately gated:
cross-surface continuity is NOT claimed.
- Real-traffic approvals-UX feedback from the operator; rollback = one
revert of 5fc3e870 (re-partition) and/or HUX_TOOL_ENFORCEMENT=0.
## Enforcement rolled back to observe-only (2026-08-24 ~13:3x UTC, 1793903f)
Live traffic on the enforced fleet showed the first defaults blocking core
assistant faculties (skills listing and the sandboxed Python fell into the
unknown->external_side_effect always-ask bucket, browsing was deny-by-
default, and no approval prompt surfaced in the chat flow). Fleet rolled to
HUX_TOOL_ENFORCEMENT=0 with a corrected capability map (python_sandbox =
internal shell; skills/todo/clarify/vision = reads; browser/web = network
medium; image_gen = artifact_write via the trusted broker; unknown tools
stay fail-closed). Verified live: all tenants 5/5, enf=0 everywhere.
Re-enforcement checklist (in order):
1. Approvals UX must surface prompts inline in the chat/voice flow.
2. Default grants reviewed against the corrected capability map (network
under safe autonomy should ask, not deny, for the chat surface).
3. Canary re-enable on one ordinal first (partition), then fleet.