Maintainer-written foundation

Hybrid built the original project.

The project history through commit 05a1034, named Checkpoint before Codex, was written by Hybrid. That foundation includes the initial Go project, Speedrobo card-data pagination, normalized local card data, search and filtering, the first Fyne interface, dynamic name search, rudimentary deckbuilding, copy-limit enforcement, sorting, and in-editor card dragging.

Hybrid remains responsible for product direction, game knowledge, requested behavior, acceptance decisions, hands-on testing, tester feedback, release decisions, and relationships with artists and data providers. Provided artwork and card data are not AI-generated by this project.

Codex-assisted v0.1.3 migration

Implementation followed maintainer-defined requirements.

From the commits after 05a1034 through the v0.1.3 release and its accompanying repository and website migration, implementation and documentation were drafted with OpenAI Codex under Hybrid's direction and review.

This is area-level attribution. Mixed commits contain related code, tests, configuration, and documentation, while Git author metadata uses the maintainer's local identity even when Codex drafted a change.

Policy after the v0.1.3 migration

Production code remains maintainer-written; automated tests may be Codex-authored.

Once the v0.1.3 repository and website migration is complete, new production application code on development branches is intended to be written by Hybrid. AI tools may provide guidance, explanations, design discussion, review, test ideas, and debugging suggestions, but will not directly author the production implementation.

Automated tests, test fixtures, testing utilities, and testing scripts may be implemented by OpenAI Codex under Hybrid's direction and review. This standing exception applies only to test and test-support code, is covered by this blanket disclosure, and does not extend to the application's production behavior.

If the production-code policy changes for a specific contribution, the exception will be disclosed in the relevant pull request, commit, or release notes.

Read the canonical statement in the repository

Disclosed v0.1.4 exception

Final TTS integration included limited, authorized production assistance.

Hybrid designed and implemented the core batch-selection, text-format, and Tabletop Simulator export behavior with Codex providing guidance, review, debugging support, and comprehensive automated tests.

To reduce repetitive hand strain during final integration, Hybrid explicitly authorized Codex to author the default embedded card-back provider, public TTS installation coordinator, automatic cross-platform TTS location detection, remembered custom-location behavior, and final Fyne button/dialog wiring. Codex also prepared the related release documentation, website updates, and packaging metadata under Hybrid's direction and review.

This is a contribution-specific exception, not a blanket change to the post-v0.1.3 production-code policy.

Disclosed v0.1.5 exception

The hosted catalog was an authorized Codex implementation.

Hybrid selected the architecture, obtained publisher permission, configured and validated Cloudflare R2 and the custom domain, specified the multiplayer goal, and explicitly authorized OpenAI Codex to implement the complete hosted-catalog patch so Hybrid could move to other project work.

Codex authored the distribution schemas, deterministic catalog and TTS-sheet generator, R2 publication workflow, integrity-checked database client, hosted saved-object integration, automatic local fallback, automated tests, maintainer documentation, release notes, website changes, and packaging metadata. Hybrid remains responsible for acceptance, service operation, release approval, and later maintenance.

This is a complete, contribution-specific production implementation exception. It does not silently change the policy for unrelated future features.

Disclosed project-professionalization exception

Repository quality and support infrastructure were explicitly authorized.

After reviewing an external assessment, Hybrid explicitly authorized Codex to implement the applicable professionalization work: pull-request CI, release checksums, SPDX SBOM generation, artifact attestations, dependency automation, contribution and security policies, issue and pull-request templates, documentation updates, and the local Diagnostic Information dialog and tests.

The diagnostic feature exposes only reviewed support context and sends no telemetry. Hybrid remains responsible for choosing a future code license, supplying authentic screenshots, accepting the contribution, enabling repository protections, and deciding when it ships.

This is a contribution-specific exception and does not silently change the policy for unrelated future features.

Disclosed v0.1.6 exception

Selectable backgrounds were an authorized Codex implementation.

Hybrid supplied the approved artwork, selected the feature for v0.1.6, and explicitly authorized OpenAI Codex to implement and release the background options.

Codex authored the embedded-artwork package, persistent settings controls, full-window composition and readability layer, application-screen integration, automated tests, documentation, website changes, release notes, and packaging metadata. After Hybrid found the initial renderer incompatibility, Codex also authored the disclosed v0.1.6-hotfix.1 correction and regression test. Hybrid remains responsible for artwork authorization, visual acceptance, and release approval.

This is a contribution-specific exception and does not silently change the policy for unrelated future features.