Skip to content

[arm 2, items 56-65] latency makes certification refuse navigation clicks (business-side effect not proven) #1378

Open

Description

@abrichr

Arm 2 (compile_agent), silent-saves fault set 1.1.0 on MockMed, items 56-65 (the latency block).

Under MockMed's slow change, every screen change waits 2 s. Every recording in the block compiled, but the standard run gate refused its canary at certification:

[REFUSE] Certification: bundle is NOT certified under 'clinical-write': 2 policy violation(s)
(e.g. require_reviewed_action_risk: write-shaped action risk has no current, bound operator
classification ... (navigation occurred but its business-side effect is not proven))
steps: step_000, step_001

step_000 and step_001 are the "Open" and "New Encounter" clicks. They navigate and write nothing. Recordings of the same task without the delay certified and were admitted (the admission records at items 2, 27, 37, 67, 77 and 87, for the recordings at items 1, 26, 36, 66, 76 and 86). No program was admitted in the block, so the agent recorded every one of items 56-65.

Evidence (branch bench/silent-saves-change, stacked on #1352):

Expected: a delayed screen change after a navigation click is classified as navigation, as it is without the delay, so it needs no reviewed risk override.

🤖 Generated with Claude Code

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions