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.

The Project Forge web compiler is a guided browser surface for filling the artifact surfaces that make up a target-project opening package. It exists to make the compilation step more structured and legible for operators who want a dedicated interface — particularly for reviewing what is required, what is optional, and what has not been filled yet. It is one of the support surfaces of the system, not part of the canonical core. Its role is to help you work faster and more clearly; authority over what the system requires, what counts as valid, and what is ready to emit stays with the canonicals.

Open the Web Compiler

Browser-based surface for guided artifact compilation

​
What the Web Compiler Is For

The compiler exists to help operators complete the steps that require filling structured surfaces — specifically the opening artifact fields that are easy to skip, mis-scope, or partially fill without a dedicated interface. It is designed to:

Structured Artifact Filling

Guide the operator through filling brief and initial SSOT fields in a structured, field-by-field way rather than through free-form editing.

Required vs. Optional Surfaces

Keep required and optional artifact surfaces visible so nothing required is silently skipped and nothing optional is mistakenly treated as mandatory.

Import and Review

Support import of source content for review before it affects the draft — so candidate material and official basis remain distinct.

Export a Clean Package

Export the compiled opening package in one place once the required surfaces have been filled and reviewed.

​
What the Web Compiler Is Not

Do not treat the compiler as authority. The canonicals still govern the system.
The compiler is a support surface. It is not a fifth canonical, not an artifact class, and not a decision-maker. Specifically, it does not:
  • Hold canonical authority over what the system requires or allows
  • Belong to any of the four baseline artifact classes (TARGET_PROJECT_BRIEF_ARTIFACT, INITIAL_SSOT_ARTIFACT, HANDOFF_ARTIFACT, SOURCE_OR_MATERIAL_TRANSFER_ARTIFACT)
  • Substitute for source validation, readiness evaluation, or operator judgment
  • Decide when an artifact is required — those decisions remain in the canonicals
  • Create promotion eligibility for any material you fill into it
  • Override any immutable field or redefine any canonical rule
If the compiler’s interface and a canonical rule appear to conflict, the canonical wins. The compiler is downstream of the canonicals in all things.

​
Relationship to the Canonicals

The web compiler is a support surface, not a fifth canonical. Its position in the authority hierarchy is the same as that of the operator guides, AI_START.md, and the smoke test materials: it helps operators enter and use the system correctly, but it does not govern the system. The same logic that applies to artifact templates applies to the compiler. Templates help you instantiate the artifact surfaces faster and more completely. The compiler helps you fill those surfaces in a guided, browser-based interface. Neither creates authority. Neither validates content. Neither decides when an artifact is required. Those decisions are made upstream, in 01_RULES.md and 02_PROTOCOL.md.
The compiler helps structure the package. It does not replace the canonicals.

​
When to Use the Web Compiler

Prefer the web compiler when any of the following apply:
  • You want a cleaner, dedicated operator-facing surface for the compilation step rather than editing raw files
  • You want to review imported source content before it affects the draft, keeping candidate material visibly separate from official basis
  • You want a single export point for the full opening package once all required surfaces are filled
  • The operator working on the package benefits from explicit field-by-field guidance rather than open-ended template editing

​
When to Use Manual Templates Instead

The artifact_templates/ directory contains the same artifact surfaces in raw file form. Prefer the manual templates when:
  • The project is small and the target, scope, and basis are already clear before you start filling
  • You want maximum control over every field and do not need a guided interface
  • You are working in an agent context where a browser UI is not accessible
  • You are compiling the package programmatically or from a file-based agent workflow
The templates and the compiler produce the same artifact surfaces. Choosing between them is an operator workflow preference, not a system requirement. Neither path changes what the canonicals require of the output.

​
Summary: The Compiler’s Role in One Sentence

The compiler is a surface that helps instantiate and fill the opening artifacts faster; it does not create authority, validate content, or substitute for operator judgment — and it does not change what the canonicals require.

Build docs developers (and LLMs) love

Get started for freeTalk to us