LaunchRepo.

Glossary term

Product context file

One structured file with the facts and copy about your product — product.json in LaunchRepo — that the agent reads for every submission.

Definition

A product context file is a single structured document describing one product for machines and people: name, URL, one-line and long descriptions, category, audience, real features, pricing and trial facts, launch stage, screenshots and logo paths, and constraints such as the earliest launch date. Companion files hold approved copy variants and the identity facts that may be published.

Its defining rule is that unknowns stay empty. A field the owner has not confirmed is blank, not guessed.

Example

A founder in Brighton creates a project for her booking app with new-product.py. The onboarding interview fills product.json: name, website, audience, three verified features, a dated pricing summary and the earliest launch date. She is not sure the free plan will stay free, so free_forever_verified stays false instead of turning into a claim.

Weeks later a directory form asks whether the product is free forever. The agent reads the file, finds no verified yes and does not tick the box. The twentieth form gets exactly the facts the first one got. An excerpt of the file is below.

{
  "schema_version": 1,
  "name": "Example Booking",
  "website": "https://yourproduct.example/",
  "audience": ["independent physiotherapists"],
  "verified_features": ["online booking", "SMS reminders", "calendar sync"],
  "pricing_summary": "Free plan for one calendar, paid plans from 9 EUR a month",
  "pricing_checked_at": "2026-09-30",
  "free_forever_verified": false,
  "earliest_launch_date": "2026-11-03",
  "unknown_required_facts": ["founding year"],
  "approved_asset_paths": ["assets/logo.png", "assets/screenshot-1.png"],
  "spend_limit": 0
}

Why it matters for a directory launch

Every directory asks for the same facts in a different shape — a 60-character tagline here, an 80-character one there. Pasting by hand drifts; letting an agent improvise invents features. One source of truth, filled once and reviewed, is what makes the twentieth form as accurate as the first and the next product a copy-and-edit job.

How LaunchRepo handles it

new-product.py creates projects/<slug>/product.json from the template; the onboarding interviews you or reads your codebase to fill it, and COPY-WORKSHOP.md produces copy.md with approved variants. The local dashboard edits the same files. The agent may not derive capabilities from a competitor or turn planned features into available ones; record.py reads earliest_launch_date from the same file.

Go deeper

Your first session: onboarding led by the agent

The seven phases of the first session, including the product brief, the launch date and the permissions agreed once per product.

See the term in the repository

LaunchRepo is 299 directory playbooks, a product context file and a submission tracker your own agent runs. Pay €119.00 once; use it for every product you own.

See pricing