-
Notifications
You must be signed in to change notification settings - Fork 3
Home
Genesis Code Protocol (GCP) is an AI‑native, checkpoint‑gated invention protocol. A capable large language model (LLM) can run it end‑to‑end to turn a Spark into a signed, auditable Invention Package with evidence, provenance and a verifiable Exit Wizard export【332716383956412†L2-L5】.
This wiki provides version‑agnostic guidance and references for using GCP. Each major edition introduces new phases and capabilities, but the core principles remain the same: begin with a Spark, progress through checkpoints, and generate reproducible artifacts along the way. For details on a specific release, see the edition pages (e.g. GCP‑V50) or browse the release notes in the repository changelog.
- Quick‑Start – how to initiate a GCP run (LLM‑only or via the CLI).
- Phase‑Map‑and‑Gates – overview of phases and the gate decision flow.
- Gate‑Decision‑Card – fields and options for gate decisions.
- Runners‑and‑Cartridges – how to attach deterministic runners and knowledge cartridges.
- Artifacts‑and‑Ledgers – description of evidence, reproducibility, provenance and export artifacts.
- Evidence‑and‑Claims – managing evidence indexes and claim graphs.
- Reproducibility‑and‑Rehydration – ensuring experiments are repeatable and re‑hydratable.
- Exit‑Wizard – final export and closure.
- Security‑and‑Provenance – security practices and provenance (SBOM/signing) guidelines.
- Templates – contribution templates for feature requests, issues and pull requests.
- Glossary – definitions of key terms.
- FAQ – frequently asked questions.
- GCP‑V50 – information on the latest flagship edition.
- Master‑Runners‑Codex‑V50 – summary of V50 runner contracts.
- Cartridges‑Pack‑V50 – summary of V50 cartridge modules.
- GCP V49 Flagship Edition – Details of V49 Flagship Edition.
- GCP V49 ‐ Summarized – Summary of V49 Flagship Edition
GCP evolves with each version. Earlier editions (V49, V48, V47, V46, etc.) remain archived for reference. The GCP‑V50 page details the latest flagship edition, while older release notes are documented in the repository changelog.
If you’d like to contribute to GCP or its documentation, please read the contribution guidelines and templates. Keep ledgers current, follow conventional commit messages and respect privacy constraints—no personally identifiable information (PII) should appear in logs or public artifacts【332716383956412†L14-L18】.