Skip to content

docs(v003): reflect pccx-v003 canonical, retire pccx-LLM-v003 feeder#79

Merged
hkimw merged 1 commit intomainfrom
docs/retire-pccx-llm-v003-references-20260508
May 8, 2026
Merged

docs(v003): reflect pccx-v003 canonical, retire pccx-LLM-v003 feeder#79
hkimw merged 1 commit intomainfrom
docs/retire-pccx-llm-v003-references-20260508

Conversation

@hkimw
Copy link
Copy Markdown
Member

@hkimw hkimw commented May 8, 2026

Reflects the current public state across EN + KO docs:

  • pccxai/pccx-v003 is the canonical v003 IP-core planning package (planning, evidence-gated).
  • pccxai/pccx-LLM-v003 is superseded / retired and is no longer an active public track.

Touched: docs/v003/{overview,repository-boundary,compatibility-contract,open-questions}.md, docs/reference/repo-topology.md, docs/roadmap.md, docs/roadmap/milestones.md, index.rst, ko/index.rst, ko/docs/roadmap.md, ko/docs/v003/index.md, _static/diagrams/pccx_family_tree.svg.

Local sphinx-build / sphinx-lint are not installed in this clone; relying on CI to enforce strict and lint.

No timing, bitstream, board-runtime, model-execution, throughput, FPS, mAP, production-readiness, or trademark-registration claim is made here.

Updates the v003 documentation surface across EN and KO so it stops
treating pccxai/pccx-v003 as a future repository and pccxai/pccx-LLM-v003
as an active temporary feeder.

Changes:
- docs/v003/overview.md: 'does not exist yet' / 'temporary line' wording
  is replaced with pccx-v003 as the canonical planning package and
  pccx-LLM-v003 as a superseded / retired feeder.
- docs/v003/repository-boundary.md: 'Today' table now lists pccx-v003
  as the active canonical package and pccx-LLM-v003 as historical;
  'Future location' column relabelled to 'Active location'; migration
  sequence rephrased so step 3 no longer says 'decide whether to create
  pccxai/pccx-v003'.
- docs/v003/compatibility-contract.md: removes the parenthetical
  'pccxai/pccx-v003 does not exist today' note and points at the existing
  canonical repo.
- docs/v003/open-questions.md: drops the stale 'when does pccxai/pccx-v003
  get created' / 'when does pccx-LLM-v003 get folded' phrasing in favour
  of contract-freeze and intake-protocol questions.
- docs/reference/repo-topology.md: pccx-v003 moves into the active
  repository table; pccx-LLM-v003 moves into a new 'Historical / retired
  repositories' section; the 'Future repositories' table is removed.
- docs/roadmap.md and docs/roadmap/milestones.md: rephrase the v003
  blocks so pccx-v003 is the active planning home and pccx-LLM-v003 is
  superseded / retired (no more 'temporary planning line' or 'placeholder
  track').
- index.rst: drops the 'temporary pccx-LLM-v003 line feeds the v003 LLM
  planning track' phrasing in favour of a superseded-feeder note.
- _static/diagrams/pccx_family_tree.svg: v003 node spec line and tooltip
  point at pccx-v003 as the canonical package; Gemma 4 E4B is marked
  as planning-only inside the diagram.
- ko/index.rst, ko/docs/roadmap.md, ko/docs/v003/index.md: KO mirror
  pages that still referenced pccx-LLM-v003 as an active line are
  rephrased to match the EN updates; the public exposure of the private
  pccx-LLM-v003-staging repo is removed from the KO v003 index page.

Local sphinx-build / sphinx-lint are not installed in this clone; relied
on CI to enforce strict and lint.

No timing closure, bitstream, board runtime, model execution, throughput,
FPS, mAP, production-readiness, stable API/ABI, or trademark-registration
claim is made or strengthened by this change. PCCX(TM) only.
@cloudflare-workers-and-pages
Copy link
Copy Markdown

Deploying pccx with  Cloudflare Pages  Cloudflare Pages

Latest commit: b3826dd
Status: ✅  Deploy successful!
Preview URL: https://261c0998.pccx.pages.dev
Branch Preview URL: https://docs-retire-pccx-llm-v003-re.pccx.pages.dev

View logs

@hkimw hkimw merged commit 2d6c1aa into main May 8, 2026
5 checks passed
@hkimw hkimw deleted the docs/retire-pccx-llm-v003-references-20260508 branch May 8, 2026 08:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant