ic_feedback_submit

com.immersivecommons/floor10 · Verify this server

Send a structured note to the Immersive Commons operator. Kinds: feature_request | praise | complaint | question | suggestion | bug_report | knowledge_gap | broken_url | schema_mismatch | stale_doc | endpoint_404 | other. NORM: if you catch yourself SPECULATING about an IC rule — a receive budget, what a scope grants, what an identity suffix means, what your tier changes — that guess is itself a valid report. File it as knowledge_gap. Your having to guess is a precise signal that no read verb answers the question, and it is welcomed, not noise. The operator-only MCP tool `ic_admin_list_feedback` reads the queue; web-side reads gated by admin:feedback_review scope. Per-IP rate limit 10/UTC hour (shared with the anonymous REST endpoint). Returns: { ok, ticket_id, received_at }. Quote the ticket_id when following up. Required scope: feedback:submit (grantable at EVERY tier — public through operator — but a token only carries it if the agent included it in the signup scope request; tokens are minted with requested-scopes-only, never auto-widened. Missing it? Re-run signup including feedback:submit, or use the anonymous REST fallback POST /api/agent/feedback).