Accelerator architecture with evidence at the boundary.

PCCX™ publishes architecture notes, reference RTL direction, and lab tooling for edge-class inference research. Public claims stay tied to reviewed, reproducible evidence.

A public front door for serious hardware work.

The site now follows a semiconductor/IP company pattern: compact navigation, large hardware-area hero treatment, product-style technology sections, developer access points, and plain evidence boundaries. It avoids unsupported benchmark, timing, bitstream, board inference, and non-™ mark language.

PCCX™ Standard

Terminology, interface notes, and conformance direction for implementation-independent review.

PublicSpec

PCCX™ OpenCore

Reference RTL and FPGA-oriented research artifacts for study, validation, and ecosystem feedback.

SourceExperimental

PCCX™ Lab

CLI-first analysis, trace handling, and verification workflow tooling for reproducible review.

ToolsWorkflow

PCCX™ Evaluation

Architecture review and integration planning for teams that need a controlled technical discussion.

ContactReview
Technology platform

From public contract to reviewed evidence.

PCCX™ separates architecture documentation, reference RTL, lab tooling, and evaluation discussions. Public pages describe the current boundary instead of presenting targets as measured results.

Developers

Docs and source before marketing.

Public routes are engineering entry points: documentation, source repositories, contribution rules, and security reporting. Claims about hardware behavior belong with the commands, logs, reports, and setup that produced them.

Documentation

Architecture notes, project status, terminology, and evidence rules.

Open

GitHub

Public repositories for RTL-oriented work, lab tooling, launcher scaffolding, and issue-driven development.

Open

Contributing

Repository selection, issue expectations, documentation style, and evidence boundaries.

Open

Public evidence notes

Trademark

Public brand usage is limited to PCCX™ and avoids other mark wording.

Hardware

No production, timing, bitstream, throughput, or board-inference claim is made without reviewed evidence.

Assistant

The assistant route is a static preview and does not call a provider endpoint.