> ## Documentation Index
> Fetch the complete documentation index at: https://docs.corgtex.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Proposals

> Propose changes to your organization through an asynchronous, consent-based process.

When a [Tension](/decide/tensions) requires changing the structure or rules of your organization, you submit a **Proposal**.

Proposals are the mechanism for evolving your company organically. You use proposals to:

* Create, modify, or delete a Role or Circle.
* Change an accountability or domain.
* Enact a new organization-wide or circle-specific policy.
* Request financial budget ([Spend Requests](/see/spend-requests)).

## The Proposal Lifecycle

Corgtex handles proposals entirely asynchronously, eliminating the need for synchronous governance meetings. The standard lifecycle follows these states:

### 1. Draft

You draft the proposal, outlining the "Why" (the tension driving it) and the "What" (the specific structural or policy changes proposed). You can collaborate with others on the draft before submitting.

### 2. Open (Advice Gathering)

Once opened, the proposal enters an active review phase and becomes visible across the workspace.

* **Notification:** Corgtex automatically notifies relevant workspace members.
* **AI Routing:** Based on the proposal's content, the AI may proactively route it to specific domain experts for their advice.
* **Reactions:** Team members can review the proposal, ask clarifying questions in the discussion thread, and leave reactions (e.g., `AGREE`, `ABSTAIN`).

### 3. Resolution

The proposal is resolved based on the Circle's configured **Approval Flow** (typically Consent).

If no paramount objections are raised within the time limit, the proposal is **APPROVED** and the structural changes are immediately enacted in the Corgtex database. If valid objections cannot be integrated, the proposal may be **REJECTED** or **WITHDRAWN** for a rewrite.

## Consent vs Consensus

By default, Corgtex encourages **Consent-based decision making** for proposals.

* **Consensus** asks: *"Does everyone agree this is the best possible idea?"* (This is slow and encourages mediocrity).
* **Consent** asks: *"Does anyone have a reasoned, paramount objection that this will cause harm to the organization or move us backward?"*

If the answer is no, the proposal passes. It is safe to try. Corgtex's asynchronous flows are specifically optimized for Consent, allowing organizations to move with incredible velocity while maintaining strict safety guardrails.