Skip to content

The design pages say what a call to the endpoint survives - #758

Merged
WaylandYang merged 1 commit into
devfrom
docs/what-a-call-to-the-endpoint-survives
Sep 18, 2026
Merged

WaylandYang merged 1 commit into
devfrom
docs/what-a-call-to-the-endpoint-survives

Conversation

@WaylandYang

Copy link
Copy Markdown
Contributor

Design pages for #757, which landed the behaviour without writing it down.

extraction.md gains a paragraph on what a call survives: the four failures that fix themselves (rate limited, 408/502/503/504, a request that never arrived, a stream that stops mid-answer), the two that do not (a 500, a read timeout, with the reason for each), why the call is streamed, and that a passage which still cannot be extracted leaves a drop row.

chat-and-mcp.md had "the out-of-credit against rate-limit classification"; there are four classes now.

ontology.md notes that a burst of ontology edits debounces into one alignment run.

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Signed-off-by: WaylandYang <wayland0916@gmail.com>
@WaylandYang
WaylandYang merged commit ca46780 into dev Sep 18, 2026
4 checks passed
@WaylandYang
WaylandYang deleted the docs/what-a-call-to-the-endpoint-survives branch September 18, 2026 13:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant