Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/xxyoudeadpunkxx/gpt-pf-chat-gpt-project-forge/llms.txt

Use this file to discover all available pages before exploring further.

Readiness in Project Forge is not a judgment call or a vibe — it is a gate. Before a target project can open, the system must evaluate the current preparation package against a defined set of conditions and assign one of four states. Each state carries a mandatory output minimum: a set of fields that must be produced regardless of how the session went. The state determines what happens next. Understanding each state, what triggers it, and what it requires is essential to operating Project Forge correctly.
NOT_READY is a normal operating state. Do not be afraid of it. It means the frame and procedure are coherent but material is still incomplete — which is useful, honest information. It is far preferable to a falsely confident READY that papers over missing data.

​
The Four States

READY

All required gate conditions for the current opening decision are satisfied. The project can proceed. Output minimum must name what authorized the decision and what comes next.

NOT_READY

The frame and procedure are coherent, but required material is missing or weak. Normal operating state. Output minimum must name exactly what is missing and what the next move is.

BLOCKED

A structural condition is missing, invalid, or unavailable. The flow cannot safely continue. Output minimum must identify the blocking cause and who owns the unblock.

CONFLICT

Two or more surfaces produce incompatible claims that cannot be closed at the current authority level. No automatic resolution. Output minimum must name the conflicting sources and suspend the open point.

​
State Definitions and Output Minimums

​
READY

READY means all required gate conditions for the current opening decision are satisfied. This does not mean all uncertainty has been eliminated or all possible questions have been answered — it means the specific gate for this opening decision is closed.
Every READY state must produce all four of these fields:
  • readiness_basis — the specific conditions that were satisfied to reach this state; names the gate, not just the conclusion
  • authorized_next_move — the explicitly authorized action that follows from this readiness determination
  • artifacts_to_read — which artifacts the target project must read at opening, in order
  • artifacts_to_emit — which artifacts are to be emitted as part of the opening package

​
NOT_READY

NOT_READY means the frame is still coherent and procedure is still running, but the required material is incomplete, weak, or missing. The system has not broken down — it has accurately identified a gap.
Every NOT_READY state must produce all four of these fields:
  • missing_items — explicit list of what is absent; must not be vague
  • weak_items — material that exists but is not strong enough to pass the gate; must name what makes it weak
  • blocking_or_non_blocking — whether the missing or weak material prevents forward motion entirely or allows partial progress
  • minimum_next_move — the smallest concrete action that would close the most critical gap

​
BLOCKED

BLOCKED means a structural condition is missing, invalid, or unavailable, and the flow cannot safely continue. Typical blocked cases include: a forbidden stability-to-residence combination is the only apparent path, a required artifact class is not defined, or measurable observability has not been closed.
Every BLOCKED state must produce all three of these fields:
  • blocking_cause — the precise structural condition that is missing or invalid; must be specific enough to act on
  • governing_owner — which surface, rule, or authority owns the blocking condition
  • minimum_unblock_move — the specific action required to remove the block and allow the flow to resume

​
CONFLICT

CONFLICT means two or more surfaces produce incompatible claims on the same point and no automatic resolution mechanism is available at the current authority level. This state is especially important in conversational AI systems, which tend to smooth over conflict rather than hold it open.
Every CONFLICT state must produce all five of these fields:
  • conflicting_sources — the specific surfaces or artifacts that diverge; must name both sides
  • resolution_rule_applied — which resolution rule was consulted (even if it could not close the conflict)
  • suspended_point — the exact question or claim that remains unresolved
  • minimum_unblock_move — the specific action needed to close the conflict (typically higher-surface validation or explicit revalidation)
  • peer_authority_status — whether the conflict involves peer-authority surfaces or higher-vs-lower surfaces, since these require different handling

​
Documentary Readiness

Documentary readiness is the base gate for any opening. It asks: is the opening package closed enough on paper? Documentary readiness requires all seven critical fields to be present and none of them to be marked MISSING:
  1. objective — defined and singular
  2. scope_in — explicitly defined
  3. scope_out — explicitly defined
  4. required_outputs — named
  5. canonical_read_order — defined
  6. stop_conditions — defined
  7. project_opening_required_artifacts — named, including TARGET_PROJECT_BRIEF_ARTIFACT, INITIAL_SSOT_ARTIFACT, and artifact read order
If the frame is coherent but any critical field is absent, the minimum state is NOT_READY. Documentary readiness is necessary but not always sufficient — some openings also require measurable readiness.

​
Measurable Readiness

Measurable readiness is activated only when the target project depends on technical variables, measurable configurations, comparable states, or checks that are not purely documentary. It is not always required. When the measurable readiness trigger is active, the system applies two layers of tests in order:
1

Observability Completeness Tests

These tests close whether the measurement surface is even well-defined:
  • required_measurable_variables_defined — required technical variables are explicitly named
  • measure_units_or_reference_method_defined — a unit or reference method exists to make measures comparable
  • missing_measurements_explicit — any missing measure affecting the gate is explicitly marked as missing
If observability completeness is not closed, the minimum state is BLOCKED. Measuring an undefined surface is not possible.
2

Measurable Gate Pass Tests

These tests close whether the defined measurements are actually sufficient:
  • required_gate_measures_present — all gate-required measures are present
  • state_comparable — the captured state is comparable to other states, setups, or runs in the same domain
If observability is closed but gate-required measures are missing, the minimum state is NOT_READY. Well-documented absence is honest — but it does not pass the gate.
The split between observability completeness and gate pass matters: “can we describe the measurable state honestly?” is a different question from “is the measurable state sufficient?” Treating well-documented absence as readiness is a subtle but serious error.

​
The Peer Authority Conflict Rule

Between peer-authority surfaces — two artifacts at the same authority level, or two peer-authority validated sources — no automatic precedence exists. If two such surfaces diverge on the same point, the minimum outcome is CONFLICT until one of the following closes the point:
  • higher-surface validation from a canonical
  • explicit revalidation that names and resolves the divergence
This rule is conservative by design. It prevents the system from pretending that order, recency, or file proximity creates authority when they do not.

Build docs developers (and LLMs) love

Get started for freeTalk to us