pccx-lab research lineage

Page in flux. Refreshed 2026-04-24 to match pccx-lab HEAD.

Status: between architectures

This page is a placeholder while the research-lineage lane is rebuilt. The previous revision auto-generated its two citation tables (analyzers + UVM strategies) from pccx_core::research::CITATIONS — a compile-time registry living in core/src/research.rs. Phase 1’s module exodus removed that file. The citations have not yet re-landed in another crate, so there is no authoritative on-disk source this page can regenerate from today.

The used_by ids that keyed the old tables (kv_cache_pressure, phase_classifier, speculative_draft_probe, qoq_kv4_quantize, …) referenced analyzer and UVM-strategy slugs that were likewise retired during the Phase 1 split. Publishing a stale table against ids that no longer exist in code would be actively misleading, so the tables have been removed until a new home lands.

Where the work moved

None of the research-grounded analytics code has been deleted — the free functions it drove (pccx_core::roofline::analyze, pccx_core::bottleneck::detect, pccx_core::synth_report::*, …) all still ship from pccx-core, they just no longer carry inline citations. The pccx-ai-copilot crate retains five literature-grounded UVM strategy stubs exposed via list_uvm_strategies() (see Copilot API).

Active design surfaces that will feed the rebuilt lineage:

  • pccx-evolve (Phase 5 seed) — SurrogateModel, EvoOperator, PRMGate trait scaffolds plus speculative-decoding primitives. The EAGLE-family references belong here.

  • pccx-authoring (IsaCompiler, ApiCompiler) — upstream of the ISA / API spec lineage that the old table’s authoring-adjacent rows tracked.

  • pccx-lsp — the CompletionSource enum tags every completion as Lsp / AiFast / AiDeep / Cache; when the AI-fast / AI-deep backends land they will need their own provenance lineage.

The four design documents (docs/design/phase2_intellisense.md, phase3_remote_backend.md, phase4_insane_reports.md, phase5_alphaevolve.md) plus phase6_dev_docs_generation.md in the pccx-lab repo call out the papers their work inherits from. Those docs are the closest thing to a live lineage until the on-disk registry returns.

The knowledge/sail_language/ corpus inside pccx-lab tracks the Cambridge Sail ISA specification language — the Phase 4 finale (M4.8–M4.10 “Sail finale”) and the Phase 5 PRM gate both rely on Sail for formal RTL refinement, so the design docs cite it heavily. The pccx-FPGA repo also ships a Sail model under formal/sail/ (see the Formal section).

When this page refreshes

The page will be regenerated from scratch when:

  1. A crate re-publishes a stable CITATIONS registry (likely pccx-reports or a new pccx-analytics), and

  2. The curated set of analyzers / UVM strategies is re-landed with stable used_by ids we can key the tables off.

At that point the two tables reappear here, generated by whichever binary replaces the old pccx_analyze --research-list surface (see CLI reference for the current binary catalogue).

Roadmap pointers

Cite this page

@misc{pccx_lab_research_2026,
  title        = {pccx-lab research lineage (placeholder): registry rebuild underway after Phase 1 module exodus},
  author       = {Kim, Hyunwoo},
  year         = {2026},
  howpublished = {\url{https://pccxai.github.io/pccx/en/docs/Lab/research.html}},
  note         = {Part of pccx: \url{https://pccxai.github.io/pccx/}}
}

When this page carries real tables again, the citation key stays the same so previously-cited references keep resolving.