---
title: "Clear this alignment layer"
method: DELETE
path: "/alignment/team/{team_id}"
tags: ["Alignment"]
---

# Clear this alignment layer

`DELETE /alignment/team/{team_id}`

## Request

- Base URL: `https://api.mnemom.ai/v1`
- URL: `https://api.mnemom.ai/v1/alignment/team/{team_id}`
- Auth: one of:
  - HTTP bearer
  - API key in header `X-Mnemom-Api-Key`
  - API key in cookie `mnemom_session`

Removes the team-scope alignment authoring; downstream scopes fall through to the next layer up in the cascade. Authorization: `team_id` is resolved to its owning organization from the DB and the caller must be an owner/admin of that org or hold an active team_admin grant on this team. A team in an org the caller does not belong to returns the same 404 as a nonexistent team; a member without that role or grant receives 403. No other tenant's manifest can be changed.

## Path parameters

- `team_id` string, required

## Response `200`

Cleared. Returns the deletion confirmation (`deleted: true`, `template: null`) and the count of agents flagged for recompose; the next read returns the composed view without this layer. (The handler returns this 200-with-body, not 204.)

- object
  - `team_id` string, uuid
  - `org_id` string, uuid
  - `template` unknown
  - `enabled` boolean
  - `deleted` boolean: Always `true`.
  - `agents_flagged_for_recompose` integer: Number of active member agents queued for re-composition.
  - `agents_recomposed` integer: Team scope only: active members whose canonical cards were recomposed in this request, so their served card already reflects the write.
  - `agents_recompose_pending` integer: Team scope only: active members still waiting on the recompose sweep (past the per-request cap, or a compose failed). Their served card updates within the sweep cadence.

## Other responses

- `400`: Bad request
- `401`: Authentication required
- `403`: Forbidden
- `404`: Resource not found
- `429`: Rate-limit exceeded. The global per-IP limiter (100 requests/minute, applied to every `/v1/*` route) rejected this request. Back off until the window resets — `Retry-After` carries the cooldown in seconds and `X-RateLimit-Reset` the absolute reset time.
- `500`: Server error — request was well-formed but the server failed to fulfill it. Typically a downstream dependency (DB / RPC / external API) returned an unexpected error.

---

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