# Code companion author decisions Last audited: 2026-08-25 This packet turns every unresolved code-companion publication blocker into an explicit author choice. Recommendations are conservative defaults, not selections. A null selectedOption means that publication remains unauthorized. ## Current state - Packages: 5 - Registered decisions: 15 - Author selections recorded: 0 - Pending author selections: 15 **Recommended launch sequence.** Publish the two high-priority companions only after their package decisions and manual gates are complete. Keep the three medium-priority companions as non-downloadable provenance records until their individual gates pass. ## `categories-gt-archive` — Categories for AGI learning experiments Priority: high ### 1. Choose the public repository boundary and software license. Stable ID: `categories-repository-and-license` · Status: **awaiting author** Audit blocker: Choose the companion repository boundary and license - **A — Conservative default:** Create a dedicated Categories for AGI code companion and license the curated software under Apache-2.0; keep book text, raw corpora, checkpoints, and unsupported artifacts outside that repository. - **B — Alternative:** Publish the curated packet as immutable release assets in the existing Categories repository, with an explicit software license and the same exclusions. - **C — Alternative:** Keep the packet private and label the affected experiment families forthcoming. ### 2. Choose the evidence status of the two Chapter 8 commutator-proxy figures. Stable ID: `categories-chapter-8-evidence` · Status: **awaiting author** Audit blocker: Recover per-step raw logs for the Chapter 8 plots if they still exist; otherwise retain their explicit archived plot-only status - **A — Conservative default:** Publish the exact figures and producer hashes with an explicit archived plot-only boundary unless the original per-step logs are recovered and verified. - **B — Alternative:** Delay this portion of the companion while searching for and auditing the original per-step logs. - **C — Alternative:** Exclude the two figures from the public companion and retain only their manuscript provenance record. ### 3. Choose the public evidence status for the Chapters 13–14 experiments. Stable ID: `categories-chapters-13-14-evidence` · Status: **awaiting author** Audit blocker: Preserve Chapters 13–14 as archived-only evidence unless complete raw run artifacts are found - **A — Conservative default:** Retain the experiments as archived-only evidence with no independent reproduction claim unless complete raw run artifacts are recovered. - **B — Alternative:** Delay public release of these records until complete raw artifacts are recovered and audited. - **C — Alternative:** Omit these records from the code companion and keep only the chapter-level evidence boundary. ## `kan-do-dcdi-archive` — Judo Calculus supplementary experiments Priority: medium ### 1. Choose whether the Judo Calculus packet is merged or independently versioned. Stable ID: `judo-repository-boundary` · Status: **awaiting author** Audit blocker: Decide whether the packet belongs in Causal Discovery on Sheaves or a dated snapshot repository - **A — Conservative default:** Publish a dated standalone snapshot that links to Causal Discovery on Sheaves but keeps the Judo-specific runners, evidence boundaries, and version history distinct. - **B — Alternative:** Merge the packet into a clearly isolated Judo Calculus directory in Causal Discovery on Sheaves. - **C — Alternative:** Keep the packet private and expose only its provenance record. ### 2. Choose a software license after checking compatibility with reused public code. Stable ID: `judo-license` · Status: **awaiting author** Audit blocker: Choose a license compatible with the public companion - **A — Conservative default:** Use Apache-2.0 only after the dependency and provenance review confirms compatibility; otherwise keep the packet private. - **B — Alternative:** Use the compatible license required by the selected upstream repository and document the reason. - **C — Alternative:** Remove reused components and license only the independently authored snapshot. ### 3. Choose the data-distribution boundary for Sachs, LINCS, and PISA inputs. Stable ID: `judo-dataset-rights` · Status: **awaiting author** Audit blocker: Document redistribution rights and provenance for the Sachs, LINCS, and PISA inputs - **A — Conservative default:** Exclude third-party datasets; publish provenance, retrieval instructions, checksums where lawful, and generated or rights-clear fixtures only. - **B — Alternative:** Include only datasets whose redistribution terms have been reviewed and recorded file by file. - **C — Alternative:** Keep the entire packet private until all three data sources have signed provenance records. ### 4. Choose the PISA experiment boundary for the first release. Stable ID: `judo-pisa-runner` · Status: **awaiting author** Audit blocker: Repair the PISA runner's diagnostic formatting defect and repeat the retained experiments in a clean environment - **A — Conservative default:** Exclude PISA execution claims from the first public snapshot until the formatting defect is repaired and the retained experiment is rerun cleanly. - **B — Alternative:** Delay the whole Judo packet until the PISA runner and clean rerun pass. - **C — Alternative:** Publish the non-PISA portion and a non-executable PISA provenance record that states the unresolved defect. ## `atlas-csql-archive` — ATLAS/CSQL worked examples Priority: medium ### 1. Choose the software license for the rights-clear ATLAS/CSQL companion. Stable ID: `atlas-license` · Status: **awaiting author** Audit blocker: Choose a license for the public companion - **A — Conservative default:** Use Apache-2.0 for the curated SQL, generated fixture, and smoke-test code; apply no license to excluded source documents or unreviewed derived data. - **B — Alternative:** Use MIT for the small standalone code packet. - **C — Alternative:** Keep the packet private and expose only its provenance record. ### 2. Choose whether the corpus-specific notebook is part of the public packet. Stable ID: `atlas-notebook-boundary` · Status: **awaiting author** Audit blocker: Decide whether the corpus-specific notebook belongs in the public packet and pin its separate environment - **A — Conservative default:** Exclude the corpus-specific notebook from the first release; publish the generated synthetic fixture and deterministic DuckDB example as the executable core. - **B — Alternative:** Include the notebook only after its corpus provenance, outputs, and separate environment are reviewed and pinned. - **C — Alternative:** Keep the entire ATLAS/CSQL packet private. ## `deep-url-archive` — Deep URL reproducibility packet Priority: medium ### 1. Choose the software license for the curated Deep URL packet. Stable ID: `deep-url-license` · Status: **awaiting author** Audit blocker: Choose a license for the public companion - **A — Conservative default:** Use Apache-2.0 for the five audited source files and deterministic reproduction support; preserve the result manifest and evidence boundary independently of the license. - **B — Alternative:** Use MIT for the standalone reproducibility packet. - **C — Alternative:** Keep the packet private and expose only its provenance and checksum record. ## `synthetic-creativity-archive` — Infinitesimal Creativity code companion Priority: high ### 1. Choose the source boundary for the first Infinitesimal Creativity repository. Stable ID: `creativity-source-boundary` · Status: **awaiting author** Audit blocker: Separate reusable library code from one-off experiment drivers - **A — Conservative default:** Publish the reusable DIAL library, registered experiment drivers, manifests, and bounded textual result records; place one-off exploratory drivers in a separately labeled archive or omit them. - **B — Alternative:** Publish the full staged source tree with explicit experimental and archival labels. - **C — Alternative:** Keep the companion private until the reusable API has been separated completely. ### 2. Choose the software, dependency, model-access, and media policy as one coherent release contract. Stable ID: `creativity-release-policy` · Status: **awaiting author** Audit blocker: Choose a license, dependency policy, model-access policy, and media provenance format - **A — Conservative default:** Use Apache-2.0 for authored code; pin dependencies; identify model APIs and checkpoints without redistributing weights; exclude image and video payloads until each item has an approved provenance record. - **B — Alternative:** Use MIT for authored code while retaining the same dependency, model, and media boundaries. - **C — Alternative:** Publish no code until every dependency, model, and media record is individually approved. ### 3. Choose the manual-review gate that must pass before repository publication. Stable ID: `creativity-manual-review` · Status: **awaiting author** Audit blocker: Complete manual security, privacy, and publication review beyond the passing narrow path, credential-pattern, media-type, and file-size checks - **A — Conservative default:** Require named manual security, privacy, confidentiality, and media-provenance sign-off on the exact candidate archive before any public repository is created. - **B — Alternative:** Prepare a smaller source-only archive and run the same named review on that reduced boundary. - **C — Alternative:** Keep the companion private and publish only its experiment-to-code metadata. ### 4. Choose whether the six-file ALFWorld bridge is published, vendored, or excluded. Stable ID: `creativity-alfworld-license` · Status: **awaiting author** Audit blocker: Publish or vendor the six-file alfworld_bridge dependency - **A — Conservative default:** Exclude the bridge from the public archive until its authorship and compatible license are documented; preserve its checksum manifest and installation boundary. - **B — Alternative:** Vendor the six files after recording an explicit compatible license and upstream provenance. - **C — Alternative:** Publish the bridge as a separately versioned dependency and require it from the main companion. ### 5. Choose the long-term dependency boundary for the external ALFWorld bridge source. Stable ID: `creativity-alfworld-dependency-boundary` · Status: **awaiting author** Audit blocker: Choose a publication or vendoring boundary for external `alfworld_bridge` from `GT_ALFWorld/alfworld_bridge`. - **A — Conservative default:** Treat the bridge as an optional external dependency with a documented version and checksum; do not copy it into the main repository without a compatible license. - **B — Alternative:** Vendor the reviewed bridge under a clearly separated third-party directory with its own notice. - **C — Alternative:** Remove ALFWorld-dependent experiments from the first public companion. ## Interpretation boundary Selecting an option records author policy; it does not itself create a repository, change access controls, grant redistribution rights, or establish independent replication. The exact candidate archive must still pass its registered technical and manual gates.