Let a Local Clock Gate the Free Server

Description and use

A script decides whether to use a free remote server or a local model by evaluating latency, offline drill markers, and secret patterns.

Problem

Decide whether to use a free remote server or a local model based on latency, offline status, and secret safety.

Outcome

The gate script enables teams to use a local model when it meets latency budgets and security checks, otherwise falling back to the free remote server, reducing unnecessary network traffic and trust overhead.

Workflow

• Set assist and batch latency budgets (400 ms and 8000 ms).
• Run 7 local samples to estimate p50 and p95 latency.
• Scan payload for secret patterns using a regex.
• Check for an offline drill marker file.
• Determine if the network is up.
• Apply decision logic: block if secrets found; stay local if offline drill missing or local p95 within budget; otherwise use free server if budget missed and network up; otherwise stay local.
• Output the chosen path and reason.

Evidence

Set two budgets before you send any prompt. An assist hop should return in under 400 milliseconds. A batch review may spend up to eight seconds.

Source

Stay local when the local p95 fits the budget. Stay local when the offline drill was never recorded. Block the send when a key-like pattern remains.

Source

The secret scan is a rough net, not a proof. It flags common key labels and a private-key banner.

Source