The Approval Gate Worked. Its Alarm Didn't.

Description and use

A single observation channel caused silent failures in approval and email sending. Adding three independent detectors and measuring UI coordinates resolved the issues.

Problem

A single observation channel caused critical approvals and actions to fail silently, exposing the need for redundant detection mechanisms.

Outcome

Redundant detection channels and precise measurement of UI actions eliminated silent failures, ensuring that approvals and email sends are reliably monitored and logged.

Workflow

• 1. Watcher checks API pending flag for approval card.
• 2. Watcher locates approval prompt on owner-facing UI.
• 3. Watcher performs OCR on screen to confirm card presence.
• 4. If any detector flags a pending card, human is notified.
• 5. Operator measures toolbar coordinates for Send and paperclip buttons.
• 6. Operator records exact pixel positions in operating notes.
• 7. Operator performs click using measured coordinates.
• 8. System logs action and any errors for audit.

Evidence

The watcher trusted one signal about the gate. I trusted one estimate about the interface.

Source

Three independent detectors, any one of which can raise the alarm: The API pending flag — the original signal. A locator for the owner-facing approval prompt itself — the thing the human would see, searched for directly. OCR of the screen — the dumbest channel, reading the rendered pixels the way a person glancing at the monitor would.

Source

Measured, not remembered, for anything irreversible. Coordinates, thresholds, counts — if an action can't be undone, its inputs get read from the source in the same session, grounded to the pixel or the byte.

Source