ic_prints_submit_on_behalf

com.immersivecommons/floor10 · Verify this server

Stage a print you designed FOR an IC member. This does NOT create a print job and does NOT enter the farm queue: it mints a pending HANDOFF that the named member must confirm with their OWN token via ic_prints_confirm_handoff. On their confirm the job is created and attributed to THEM — the member_id you pass is only ever a match predicate, never an identity we write with, so naming a member you have no relationship with just produces a record they can ignore until it expires (7 days). Model transport: link_url (https) or file_id (a vault file the MEMBER can read — final read-authorization is enforced as the member at confirm time, so a file only you can read will fail then). Inline bytes are not accepted. Args: { target_member_id, title, details?, material?, color?, quantity? (1..20), file_id?, link_url?, quote?, source_job_id? }. Returns: { ok, handoff_id, status: 'pending', expires_at, confirm_with }. Rate: 25/broker/UTC day, max 5 pending per member. Required scope: prints:submit_on_behalf (ic-member+).