# State Lifecycle

Every state item progresses through a series of statuses that determine how it participates in governance. The lifecycle ensures that information is only used for action decisions when it has been sufficiently confirmed and is free of conflicts.

## Lifecycle Phases

State items move through three broad phases:

**Formation** - Information has been identified and classified but not yet confirmed for governance use. Items in this phase are visible but do not satisfy action gate requirements.

**Active governance** - Information is confirmed and fully participating in the integrity system. Active items trigger conflict detection, satisfy gate requirements, and are subject to policy enforcement.

**Terminal** - Information is no longer governing. This can happen through replacement by newer information, explicit withdrawal, natural relevance decay, or manual archiving. Terminal items are preserved in the audit trail for traceability.

{% hint style="info" %}
State items are **immutable once created**. When a value changes, the previous item receives a terminal status and a new item is created. This ensures the complete history is always preserved.
{% endhint %}

## Governance Participation

| Phase             | Gate Participation | Conflict Detection | Audit Trail |
| ----------------- | ------------------ | ------------------ | ----------- |
| Formation         | Not yet eligible   | Visible            | Recorded    |
| Active Governance | Full participation | Active             | Recorded    |
| Terminal          | No participation   | No                 | Preserved   |

{% hint style="info" %}
See the [Status Lifecycle Reference](https://github.com/Cogna8/docs/blob/main/glossary/status-lifecycle-reference.md) for the full status model and transition rules.
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://cogna8-io.gitbook.io/docs/core-concepts/state-lifecycle.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.