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.

ENTRY_POINT.md is the startup entry point for the target-project package. It is not one of the four artifact classes defined in 03_ARTIFACTS.md — it is the package startup surface itself. Its job is structural: tell the target project how to read the package before any project work begins. It defines read order, inference limits, conflict rules, and stop conditions. It does not contain a single word about what the project is supposed to do.
ENTRY_POINT.md says HOW to read the package. The brief says WHAT the project is. The SSOT says WHAT counts as official basis. These three surfaces answer three different questions and must never be collapsed into one.

​
What ENTRY_POINT.md Is For

The target project needs one package-level reading surface before it encounters any project-specific content. Without it, there is no guarantee that the project will interpret the package in the right order, apply the right authority hierarchy, or stop when required information is missing. ENTRY_POINT.md closes exactly those gaps:
  • How the package must be read
  • What each package surface is for
  • What counts as official basis and what does not
  • What must not be inferred from absence or proximity
  • When the target project must stop and ask before proceeding

​
Package Interpretation Authority Order

Inside the package, authority for package interpretation closes in this order:
1

ENTRY_POINT.md

Highest authority on package interpretation, startup routing, inference limits, startup stop conditions, and package-local conflict handling.
2

TARGET_PROJECT_BRIEF_ARTIFACT.md

Highest authority on project frame and project-specific operational direction.
3

INITIAL_SSOT_ARTIFACT.md

Highest authority on what counts as approved startup basis.
4

HANDOFF_ARTIFACT.md (if present)

Temporary and subordinate only. Provides operational continuity; cannot redefine frame or basis.
5

SOURCE_OR_MATERIAL_TRANSFER_ARTIFACT.md (if present)

Subordinate and non-normative. Candidate materials only — not official basis until explicitly promoted.
6

Attached or linked source materials (if present)

Reference only. No authority by default. Cannot become official basis without explicit approval.
7

Runtime operator input in current session

Local and current-session only. May clarify or constrain; may not override brief or SSOT by default.
A lower surface may add detail within its own role. It may not redefine a higher surface. If a lower surface conflicts with a higher one, the lower surface does not authorize that point.

​
What ENTRY_POINT.md May Contain

ENTRY_POINT.md is authorized to define the following:
  • Package interpretation — how the full package must be read as a bounded startup unit
  • Read order — the sequence in which package surfaces must be consumed
  • Inference limits — what the target project must not infer from silence, proximity, or tone
  • Startup stop conditions — when the target project must halt before beginning work
  • Package-local conflict handling — which surface wins when two surfaces appear to disagree
  • The official basis rule — that official startup basis is limited to the INITIAL_SSOT and what it explicitly names
  • The reference-only rule — that transfer material, source materials, and unconfirmed runtime remarks are reference-only unless explicitly promoted

​
What ENTRY_POINT.md Must NOT Contain

Contamination test. If a line in ENTRY_POINT.md answers any of the following six questions, it does not belong there. Move it to the correct artifact surface.
  1. What is this specific project?
  2. What is in scope for this specific project?
  3. What outputs are required for this specific project?
  4. What sources are approved for this specific project?
  5. What counts as official basis for this specific project?
  6. What changed in this specific run?
ENTRY_POINT.md must never contain:
  • Project-specific objective
  • Project-specific scope boundaries
  • Project-specific required outputs
  • Approved sources or official materials
  • Run-specific continuity or decisions
  • Project-specific rationale or exceptions
Those belong in TARGET_PROJECT_BRIEF_ARTIFACT, INITIAL_SSOT_ARTIFACT, or HANDOFF_ARTIFACT respectively. Placing them in ENTRY_POINT.md is contamination — it turns the package-reading surface into a hidden brief or a hidden SSOT.

​
The Startup Move

After the target project reads the full package, it must close six checks before beginning any project work:
1

Close what project this package opens

Confirm which target project this package is for.
2

Close what the project must produce

Confirm the required outputs from the brief.
3

Close what counts as official basis at startup

Confirm the approved materials and sources from the SSOT.
4

Identify optional surfaces that are present

Note whether HANDOFF_ARTIFACT and SOURCE_OR_MATERIAL_TRANSFER_ARTIFACT are present and what they contain.
5

Identify missing required information

If any critical field is missing, mark it explicitly as missing — do not infer or fill it.
6

Determine whether work can start safely

Apply the stop conditions. If any stop condition is met, halt and ask before proceeding.
These six checks establish startup readiness only. They are not project work. Do not skip them.

​
Stop Conditions

The target project must stop before proceeding if any of the following are true:
  • TARGET_PROJECT_BRIEF_ARTIFACT.md is missing
  • INITIAL_SSOT_ARTIFACT.md is missing
  • The brief is incomplete in a way that changes scope or output
  • The SSOT is incomplete in a way that changes official basis
  • Package surfaces conflict on a material point
  • Only reference-only material exists for a point that requires official basis
  • Attached sources exist but approval state is not closed where approval is required
  • The package attempts to rely on missing artifacts as if they existed
Stop conditions are not an inconvenience. In a conversational AI system, many errors come from unearned forward motion. The stop condition is the structural brake.

​
Template Structure

This is the canonical ENTRY_POINT.md template. Use it as the startup surface of every target-project package. 
# ENTRY_POINT

## Role
This file is the startup entry point for the target project package.

Use it to interpret the package correctly before doing any project work.

This file is not the project brief.
This file is not the official basis.
This file does not replace the content of the package surfaces it points to.

Its job is to:
- define how the package must be read
- define what each package surface is for
- define what counts as official basis
- define what does not count as official basis
- define what must not be inferred
- define when to stop and ask

## Package Scope
This package exists to open one target project from explicit materials.

The package must be read as a bounded startup package.
Do not treat it as a full project archive, a notebook, or a general knowledge dump.

## Package Interpretation Authority
Package interpretation authority closes in this order:
1. `ENTRY_POINT.md`
2. `TARGET_PROJECT_BRIEF_ARTIFACT.md`
3. `INITIAL_SSOT_ARTIFACT.md`
4. `HANDOFF_ARTIFACT.md`, if present
5. `SOURCE_OR_MATERIAL_TRANSFER_ARTIFACT.md`, if present
6. attached or linked source materials, if present
7. runtime operator input explicitly provided in the current session

Lower package surfaces may add detail within their role.
Lower package surfaces may not redefine a higher package surface.

## Read Order
Read the package in this order:
1. `ENTRY_POINT.md`
2. `TARGET_PROJECT_BRIEF_ARTIFACT.md`
3. `INITIAL_SSOT_ARTIFACT.md`
4. `HANDOFF_ARTIFACT.md`, if present
5. `SOURCE_OR_MATERIAL_TRANSFER_ARTIFACT.md`, if present
6. attached or linked source materials, if present

## Inference Limits
Do not infer any of the following unless explicitly present:
- missing objective
- missing scope boundaries
- missing required outputs
- missing official basis
- missing source approval
- missing artifact existence
- missing runtime decisions

## Stop Conditions
Stop before proceeding if:
- `TARGET_PROJECT_BRIEF_ARTIFACT.md` is missing
- `INITIAL_SSOT_ARTIFACT.md` is missing
- the brief is incomplete in a way that changes scope or output
- the SSOT is incomplete in a way that changes official basis
- package surfaces conflict on a material point
- only reference-only material exists for a point that requires official basis
- attached sources exist but approval state is not closed where approval is required
- the package tries to rely on missing artifacts as if they existed

## Startup Move
After reading the package:
1. close what project this package opens
2. close what the project must produce
3. close what counts as official basis at startup
4. identify optional surfaces that are present
5. identify missing required information
6. determine whether work can start safely

## Final Rule
Read the package before extending the package.
Do not replace missing structure with inference.

Build docs developers (and LLMs) love

Get started for freeTalk to us