pin_constraint

com.getfreedomos/freedom-mcp · Verify this server

Pin, re-pin, or release this company's binding revenue constraint as a DATED, FALSIFIABLE claim. Operator-only: live chat or a card a person approved — never an unattended run. A claim names the constraint, what you believe (8–280 chars), by_date (7–180 days out), and the registered demand number + threshold that would DISCONFIRM it — a number this company can measure today; the daily sweep measures it for free, and every door (get_okrs, goals in every worker prompt, the dashboard header) reads HOLDING / DISCONFIRMED / EXPIRED from the same row. Re-pin = call again (restarts the clock; confirm-still-binds is a re-pin). release:true deletes the pin. Use when the operator says which constraint binds and until when. Routing: Operator pins / re-pins / releases the binding constraint claim → use this [sensitive-tier — EVERY call needs a manager's approval (per-send human rail): each request queues its own approval card and sends exactly once on approve. There is no standing grant for this tool.]