src/media_gate.rs:323-324 publishes inline_max_bytes: 1 MiB and whole_read_max_bytes: WHOLE_READ_CAP. The write door (src/drive.rs:~728, write_file) refuses only over WHOLE_READ_CAP; inline_max_bytes is a storage fact (inline vs blob), not a refusal threshold. A client reading the policy can't tell which number gates an upload, and gating on the smaller one would refuse files the node would take.
Ask: name the write gate explicitly in the policy (e.g. upload_max_bytes, or a gates: {write: "whole_read_max_bytes"} map), and document inline_max_bytes as storage placement. CIRISClient (CSD-007) gates on whole_read_max_bytes today and says so.
Found by CIRISClient's Files 0.5.217 pass, read against origin/main.
🤖 Generated with Claude Code
src/media_gate.rs:323-324publishesinline_max_bytes: 1 MiBandwhole_read_max_bytes: WHOLE_READ_CAP. The write door (src/drive.rs:~728,write_file) refuses only overWHOLE_READ_CAP;inline_max_bytesis a storage fact (inline vs blob), not a refusal threshold. A client reading the policy can't tell which number gates an upload, and gating on the smaller one would refuse files the node would take.Ask: name the write gate explicitly in the policy (e.g.
upload_max_bytes, or agates: {write: "whole_read_max_bytes"}map), and documentinline_max_bytesas storage placement. CIRISClient (CSD-007) gates onwhole_read_max_bytestoday and says so.Found by CIRISClient's Files 0.5.217 pass, read against origin/main.
🤖 Generated with Claude Code