Skip to content

Clarify upstream import source wording #184

@shiny-code-bot

Description

@shiny-code-bot

Objective

Update upstream/import wording to reflect that Every Code may pull from both just-every/code and openai/codex, with codex-rs as the local OpenAI mirror.

Current Status

State: Active
Next action: Update local-overlay and workflow docs after the naming ledger lands.
Blocked by: #180 naming ledger.
Last verified: 2026-05-28 after owner clarified future imports may pull more directly from openai/codex.

Finish Line

Docs distinguish just-every/code, openai/codex, codex-rs, and code-rs

Acceptance Criteria

  • Use “upstream import sources” for the general category.
  • Describe just-every/code as a fork upstream/import source.
  • Describe openai/codex / Codex CLI as original/direct upstream and provenance source.
  • Keep codex-rs read-only mirror wording clear.
  • Keep import workflow docs aligned with current scripts and remote roles.

Relationships

Sub-issue of #179.
Related to #124 upstream intake.
Related to #88 layout confusion.

Metadata

Metadata

Assignees

No one assigned

    Labels

    planDurable planning issueplan:donePlan completed or superseded

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions