Skip to content

Voice guide's live policy check burns ~6 consent rounds — cap the attempts, then degrade honestly #102

Description

@wine-fall

What it is

The live policy check in the voice-endpoint guide (spec 03-03 §7.2, decision (d): no hardcoded dates, verify free-tier status at setup time) works, but expensively: in the 2026-08-01 real-SDK acceptance run it took ~6 consented WebFetch rounds to land one fact, because fish.audio's docs/pricing pages are unfriendly to fetchers (404s, JS-rendered pages) and the model kept trying alternate URLs. Each round is a consent prompt — the noisiest stretch of an otherwise smooth conversation.

Suspected, NOT verified: a prompt-level cap is enough; no code change needed.

Spec

specs/spec03/03-03-guide-harness.md §7.2 (the live-check rule).

Done when

The voice guide prompt bounds the live check — try the known-good URLs (the model-list doc page succeeded) at most twice, then degrade honestly ("couldn't verify current pricing — check fish.audio/pricing yourself") and move on. The §7.2 rule gains the cap in one sentence. Verified by the next real-SDK setup run taking ≤2 consent rounds for the policy check (or degrading gracefully).

Metadata

Metadata

Assignees

No one assigned

    Labels

    engEngineering work: a measured defect or a performance targetenhancementNew feature or request

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions