Skip to content

Fix limit claims: 504 for wall-clock, compute limit recommended - #39

Merged
cbyrd01 merged 1 commit into
mainfrom
fix/limit-claims
Nov 17, 2026
Merged

cbyrd01 merged 1 commit into
mainfrom
fix/limit-claims

Conversation

@cbyrd01

@cbyrd01 cbyrd01 commented Nov 17, 2026

Copy link
Copy Markdown
Contributor

Part of #37

Factual corrections only, split out from #38 so they don't wait on the wording decision. Every change here is also in #38.

  • Wall-clock limit answers 504, not 408. The draft's Resource Limits section says a verb ended for exceeding the wall-clock limit "results in 504 (timeout), not 408", and restactd maps timeout to 504. Fixed on Security (the limits table), Get started and restactd.
  • The compute limit is recommended, not required. The draft makes the wall-clock and memory limits MUST and the compute limit SHOULD. Security (rule 4 and the limits section), Compare (two sentences), the /spec/ section gist for Resource Limits and /llms.txt no longer state it as required. Composed calls share one deadline, plus one compute budget where the server counts compute.
  • Smaller fixes. Compare says "any client a compliant server allows can upload a verb", because deployment is subject to authorisation. /llms.txt says the verb runs with the caller's permissions "by default", because the draft has an optional runs-as-owner feature.

The home page has its own stale claims ("six things", compute stated as required). They are left to #38, which rewrites those lines.

Checks

  • astro check: 0 errors, 0 warnings, 0 hints.
  • astro build and check-site.mjs: 18 pages checked, 0 errors.
  • git merge-tree against origin/main: clean.

Posted by Claude (AI assistant) on behalf of Christopher Byrd

🤖 Generated with Claude Code

https://claude.ai/code/session_012CEyiXRPrNfjwX3iEx99dw

A verb that runs past its wall-clock limit is answered with 504
(timeout), not 408: the draft's Resource Limits section says so, and
restactd maps timeout to 504. Fixed on Security, Get started and
restactd.

The draft requires a wall-clock and a memory limit and recommends a
compute limit (SHOULD). Security, Compare, the /spec/ section gist and
/llms.txt no longer state the compute limit as required. The shared
budget across composed calls is one deadline, plus one compute budget
where the server counts compute. Compare also says a client the server
allows can upload a verb, since deployment is authorised.

Part of #37

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012CEyiXRPrNfjwX3iEx99dw
@cbyrd01
cbyrd01 marked this pull request as ready for review November 17, 2026 15:37
@cbyrd01
cbyrd01 merged commit 26197cb into main Nov 17, 2026
1 check passed
@cbyrd01
cbyrd01 deleted the fix/limit-claims branch November 17, 2026 15:37
cbyrd01 added a commit that referenced this pull request Nov 17, 2026
Brings in the limit fixes from #39, which this branch also carried.
llms.txt.ts keeps this branch's summary, the short form of the new
home-page opening.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012CEyiXRPrNfjwX3iEx99dw
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