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.

INITIAL_SSOT_ARTIFACT is the official-basis artifact for the target project. It is read immediately after TARGET_PROJECT_BRIEF_ARTIFACT, and it answers a distinct question from the brief: not what the project must do, but what the project is allowed to treat as official starting ground. The SSOT freezes the initial official basis — locking in which materials are approved, which sources are trusted, what base constraints apply, and what version or date defines the opening state. Without the SSOT, the target project has no clear answer to what counts as fact at startup and what is still candidate material.
Nothing counts as official startup basis by default except what is explicitly named in the INITIAL_SSOT_ARTIFACT. Source proximity is not authority. Being present in the package, the chat, or the session is not the same as being approved as official basis.

​
Artifact Properties

PropertyValue
PurposeFreeze the initial official basis of the target project
AuthorityLocal to the target project; initial reference authority for the target project’s starting basis
SurfaceOfficial-basis artifact
Write TriggerWhen an initial official basis exists and must be frozen
Read TriggerImmediately after TARGET_PROJECT_BRIEF_ARTIFACT
Freshness RuleUpdate only when the initial official basis changes
Promotion ConditionsMay be updated only from material already validated under 01_RULES.md

​
Schema Fields

​
official_materials
list
required
The explicit list of materials that count as official at project startup. Only materials named here have official standing. Materials that are relevant but not named here are reference-only until explicitly promoted. Do not list materials you have not validated — that belongs in SOURCE_OR_MATERIAL_TRANSFER_ARTIFACT.
​
approved_sources
list
required
The sources the target project is authorized to treat as reliable for this project. Validation under 01_RULES.md closes: authority, direct relevance, explicit role, freshness (when time-sensitive), and contradiction status. A source is not approved by default because it is plausible, recent, or frequently referenced.
​
base_constraints
list
required
The baseline constraints that apply to official basis use in this project. These are constraints that stem from the official materials or approved sources themselves — format, version limits, applicability conditions, or known exclusions within the approved set. Do not restate project-scope constraints here; those belong in the brief.
​
version_or_date
string
required
The version identifier or date that defines the official basis. This field closes the temporal and versional scope of the SSOT: which edition of a document, which release of a standard, which dataset cutoff. If the basis is undated or unversioned, record that explicitly rather than leaving the field blank.

​
What “Official Basis” Means

Official basis is the set of materials and sources the target project is authorized to treat as true, authoritative, and complete at startup. It is what the target project can cite without qualification, build from without caveat, and use to close decisions. Everything outside the official basis is either:
  • Candidate material — potentially useful but not yet approved; lives in SOURCE_OR_MATERIAL_TRANSFER_ARTIFACT
  • Reference-only material — may inform reading but must not silently become startup truth
  • Runtime operator input — local and session-only unless explicitly approved as package basis
The SSOT exists because candidate material has a tendency to become de facto authority by proximity. A source that is nearby, plausible, or frequently referenced will be treated as authoritative by default unless the system explicitly draws the line. The SSOT draws that line.

​
Why Freezing the Basis Matters

Freezing the official basis at project opening prevents three specific failure modes:
  1. Candidate material absorption — without an explicit SSOT, the target project will absorb materials that are present but not validated, treating nearness as approval
  2. Basis drift across runs — without a frozen starting point, the official basis can shift invisibly from run to run as new materials appear
  3. Reconstruction ambiguity — if the basis is not written down, the next run must reconstruct it from memory or inference, which is exactly what Project Forge is designed to prevent

​
What the SSOT Must NOT Do

The SSOT has hard limits on its authority:
  • Must not absorb candidate material by proximity — the fact that a source or material is attached, nearby, or plausible does not make it official; it must be explicitly named here
  • Must not override the project brief — the SSOT governs what counts as official basis, not what the project is supposed to accomplish; scope and objective belong in the brief
  • Must not treat transfer material as approved — material in SOURCE_OR_MATERIAL_TRANSFER_ARTIFACT is candidate until it passes validation under 01_RULES.md; the SSOT cannot absorb it automatically

​
Template

Use this template to instantiate INITIAL_SSOT_ARTIFACT. Every field must be closed before the artifact is emitted. A validated source that is not named here is not official basis — it may only be named here after it passes validation. 
# INITIAL_SSOT_ARTIFACT

## official_materials
- TBD

## approved_sources
- TBD

## base_constraints
- TBD

## version_or_date
TBD
The SSOT can only be updated from material that has already been validated under 01_RULES.md. This requirement exists because the SSOT is the official starting ground — if it can absorb unvalidated material, the whole concept of a frozen basis collapses. Validation closes authority, relevance, role, and freshness. Until those closures exist, the material is candidate, not basis. The update restriction is what keeps the SSOT from becoming a pile of accumulated candidate material with an official-sounding label.

Build docs developers (and LLMs) love

Get started for freeTalk to us