Skip to content

Require advertised capability before placement reservations - #5305

Merged
joelteply merged 1 commit into
canaryfrom
55820868/capability-signal-integration
Oct 23, 2026
Merged

joelteply merged 1 commit into
canaryfrom
55820868/capability-signal-integration

Conversation

@joelteply

@joelteply joelteply commented Oct 23, 2026 •

Copy link
Copy Markdown
Contributor

A peer that does not advertise placement reservation support must not receive a reservation request. This ports Sahar's affirmative capability signal and production consumer onto current canary: old beacons default to no capabilities, unknown names never authorize, and reservation refusal occurs before transport/fault accounting.

Authored by Sahar, immutable submission1350e4b2-c621-4585-bd75-72a0d296cd00 (SHA256125e5dca19c62a98dc8ba1d9d94135b374027710eb86f05610d36ecc15a6baab,20354 bytes), source34d1cf571. Codex integration card55820868. The patch applies unchanged after relocating capacity/gossip.rs and capacity/lease.rs into continuum-engine; the core uses its existing capacity re-export. Successor to stale#5134; owner branch preserved.

Validation: artifact hash verified; clean apply after two path relocations; git diff --check passed; all CapacityOffer constructors inspected. Existing unit-test modules/fixtures cover missing/unknown/exact capabilities and the reservation gate. Three serde tests propagate errors. No local compilation while serving; fresh CI and independent current-base review required before merge. No deployment or live behavior claim.
Rollout: a newly upgraded spiller refuses reservations to pre-capability seats until those seats upgrade. During a mixed fleet this deliberately keeps those moves home; capability-related placement.spill.refused/return.refused probes are expected. Upgrade seats first where possible. Cormac source PASS at8f109903e is conditional on green CI. Typed refusal telemetry is tracked separately; authorization itself already uses CapabilityDecision, never string matching.

Authored by Sahar (df72dbf2-b177-4d59-8325-b52c6ff71adf), immutable submission 1350e4b2-c621-4585-bd75-72a0d296cd00 from commit34d1cf571c57fe0d24fcf4a8f30aea36a43229b1, artifact125e5dca19c62a98dc8ba1d9d94135b374027710eb86f05610d36ecc15a6baab. Codex current-canary port preserves the patch, relocating capacity files into continuum-engine. Integration card55820868.
@joelteply

Copy link
Copy Markdown
Contributor Author

Independent source review receipt: Cormac's actual AIRC session approved exact8f109903e conditional green CI. He verified Unknown/missing/no-row refusal, exact capability membership, gate before wire, and all three callers retaining Stay without fault writes. His mixed-fleet rollout note is incorporated in the description. Nonblocking typed refusal telemetry follow-up is card8e4c42de-df8f-4766-b773-7ecc9b23a77e (Codex), preserving the typed authorization decision already present.

Canonical Sahar artifact1350e4b2 now has bound source PASS c2487e35-b3b8-4e83-91e2-0dc7d782f5ff under review205c19ee, limited to immutable source, not this integration's CI. Owner confirms frozen34d1cf571 and no concurrent edits. Core/lib.rs:31 reexports engine capacity; there is one definition, no duplicate module.

@joelteply
joelteply merged commit e2faa9d into canary Oct 23, 2026
9 checks passed
@joelteply
joelteply deleted the 55820868/capability-signal-integration branch October 23, 2026 05:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant