πŸ“‘ Peck Protocol Monitor
Live monitor Waiting for first poll…
Awaiting fetch
Running β€” Active SFN executions in flight
Succeeded β€” Completed successfully
Failed β€” Failed or timed out
Active Peck Count β€” Pecks currently in any live state

State Machine Transitions

View full diagram β†’

Each peck request moves through a defined set of states. Counts reflect cached local data plus any live count returned by the status endpoint. Click Drill to inspect a specific state in the flow visualizer.

Initiated
Peck request sent, awaiting approval
β€” Drill β†’
Awaiting Approval
SMS OTP sent to target human
β€” Drill β†’
OTP Sent
One-time code delivered, awaiting entry
β€” Drill β†’
Bonded
Connection established, Beak Key issued
β€” Drill β†’
Denied
Human rejected the connection request
β€” Drill β†’
Expired
10-minute window elapsed without approval
β€” Drill β†’
Callback Error
Webhook or callback delivery failed
β€” Drill β†’

Active Peck Trend

Fetching…

Active peck count across the last 8 polls (30s intervals). A rising bar pattern indicates increased bonding activity; sustained red bars indicate failures.

● Succeeded ● Failed ● Running β—Œ No data
Failure Rate
β€” No data

Status Endpoint Response

Last response from POST /beak/system/status. Colour-coded counts are parsed from this payload.

Waiting for first poll…
HTTP β€”

Protocol Health Summary

Assessing… SLA Monitor β†’
Est. Approval Rate β€” succeeded / (succeeded + failed)
Polls This Session 0 Every 30 seconds
Last API Error None No errors recorded
Stuck-run detection: If the running count is >0 and unchanged for 2 or more consecutive polls (β‰₯1 minute), the amber alert banner is shown above. This may indicate a Step Function execution waiting at a human-approval state for an extended period. Navigate to Peck Flow Visualizer to inspect per-state counts, or review the Step Functions console for timed-out tasks.

Operator Quick Links