---
title: "Unpin Evaluation From Constitution"
method: POST
path: "/api/mind/v2/evaluations/{evaluation_id}/constitution-unpin"
tags: ["mind-v2"]
---

# Unpin Evaluation From Constitution

`POST /api/mind/v2/evaluations/{evaluation_id}/constitution-unpin`

## Request

- Base URL: `https://app.thinqos.com` (the document declares no server; this is the origin it was published from)
- URL: `https://app.thinqos.com/api/mind/v2/evaluations/{evaluation_id}/constitution-unpin`
- Auth: none declared

Remove a belief from the Constitution (TOS-1412).

Unpinning never touches ``confirmed`` or ``protection_level`` - the belief
stays held-true and keeps competing through the attention package; it just
stops being always-on. Locked (constitutional-seed) rows are Constitution
members via ``protection_level='locked'``, not via the pin, so unpinning
cannot remove them - by design (they are the non-negotiable core).

TOS-1982 Phase 2: a real True->False transition also emits an ELEVATE
``constitution_unpin`` event, regardless of whether the pin being removed
was applied by a human or by the constitution-candidacy auto-pin sweep.
This is a durable veto - see ``constitution_candidacy.
was_constitution_unpinned`` - so a LATER consolidation pass never
silently re-pins this SAME evaluation even if it still satisfies every
auto-pin criterion. The user retains the ordinary manual pin route to
re-add it at any time; only the AUTOMATIC sweep is vetoed.

## Path parameters

- `evaluation_id` string, uuid, required

## Headers

- `x-impersonate-identity-id` string, nullable

## Response `204`

Successful Response

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/thinqos/apis/thinqos-api.md) · [All operations](https://skmtc.dev/thinqos/apis/thinqos-api/llms.txt) · [OpenAPI document](https://skmtc.dev/thinqos/apis/thinqos-api/revisions/5387b4ded614?raw)