- 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).
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. Submitted (Advice Gathering)
Once submitted, the proposal enters an active review phase.- Notification: Corgtex automatically notifies the relevant members of the affected circle.
- 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?”