docs: point the carrier block's limits at their argument #157
No reviewers
Labels
No labels
priority/P0
priority/P1
priority/P2
release/v0.1.0
status/blocked
status/planned
type/bug
type/design
type/test-gap
type/tracker
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
natsukium/felis!157
Loading…
Reference in a new issue
No description provided.
Delete branch "docs/frly-carrier-caps-139"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Fixes #139.
The reference's FRLY carrier block listed the frozen caps and the degrade
contract but gave no way into the argument behind them. It now points at the
explanation twin, so a contributor reading the limit table finds why the block
drops rather than fails, why the payload is not chunked, and when either
decision should be revisited — instead of rediscovering the rejected shapes.
Doc cascade:
docs/reference/ipc.mdonly; the argument already lives in itsexplanation twin and needed no edit.
Verified: just check green (fmt, clippy, nextest, deny, proto-compat); reviewed by pi luna + pi sol; docs proofread by Gemini gemini-3.8-flash-high
Deferred
Pull request closed