Project and operator
PCCX is an open-source semiconductor project initiated, operated, and supported by Altifigence. We develop shared designs, verification resources, and technical documentation so developers can learn, build, and improve the project together.
PCCX does not currently operate as a separate independent nonprofit foundation or an IRS-recognized 501(c)(3) or 501(c)(6) organization. A foundation is a longer-term direction for consideration. Altifigence is the current operator.
The role of PCCX
PCCX develops NPU and RTL designs, testbenches, verification examples, execution scripts, documentation, and educational resources that we have the right to publish. We aim to make their usage terms clear and provide practical value to people who do not buy Altifigence products.
The role of Altifigence
Altifigence is responsible for operations, budgets, and contracts. Its product and service activities include Digital Design Studio (DDS), ALcad, design and verification automation, cloud execution, AI features, collaboration, and enterprise support.
Decisions and commercial interests
Under the current structure, Altifigence has final responsibility for operating direction, budgets, and contracts. Repository maintainers review technical changes and contributions under the relevant contribution guidelines. Our principle is to record significant technical proposals and the reasons for changes in public issues, discussions, and pull requests.
Altifigence seeks to grow PCCX technology and its community while increasing adoption of its tools and revenue from commercial services. Our operating direction is to reinvest revenue and feedback in PCCX and product development. This does not promise a fixed revenue share or reinvestment amount unless separately announced.
We aim to document baseline execution paths and offer optional Altifigence workflows when they are available. A paid purchase, use of a particular tool, or a positive review is not a condition for participating in PCCX.
Proposals and objections can be raised in public discussions or the relevant repository's issues. Changes to maintainership and decision processes will be explained in the relevant repositories and this document.
Public assets and usage rights
Publication does not place every file under the same license. Check the license and copyright notices for each repository and file. Existing code and external contributions are not assumed to become Altifigence property merely by joining the project.
The current pccx repository rights notice applies Apache-2.0 to source code unless stated otherwise. Documentation, site copy, diagrams, logos, and trademarks are outside that code license and require the permission or terms specified for those assets. Other PCCX repositories have their own notices.
Modification, redistribution, and commercial use of open-source code follow its license, including use by competitors. Separate commercial products such as DDS and ALcad have their own terms and contracts. License obligations still apply when open-source code is incorporated into a commercial product.
Contributors must have the right to submit their work and must not include third-party confidential or infringing material. Follow the contribution guide and the applicable repository terms.
This overview does not revoke earlier license grants or transfer contributor ownership. Altifigence can grant permission only for assets it owns or is authorized to license. For substantial new prose or artwork, publication rights must be resolved before a contribution is merged; a draft CLA is not an executed agreement.
Funding and external support
Our initial operating model is to fund PCCX and developer tool support through Altifigence's development and community budgets. Resources are directed toward maintenance, public technology and documentation, development infrastructure, and contributor support.
If external sponsorship or support is introduced, we will disclose the recipient, intended use, conditions, and sponsor benefits in advance. Service fees, commercial sponsorship, and project support will be identified according to their purpose.
We do not present support for PCCX as a tax-deductible contribution to a US 501(c)(3) organization. Any future separate entity or tax-exempt status will be documented with verifiable official information and its scope.
Developer support program
Altifigence Open Source Program
This is a planned Altifigence developer support program. The proposed starting point is PCCX, with possible expansion to other public semiconductor projects as capacity allows.
Current status: in preparation. The outline below does not announce open applications or available grants of access or credits. Eligibility, selection criteria, scope, duration, limits, and renewal conditions will be published when the program launches.
| Participants | Proposed support |
|---|---|
| PCCX workshop and event participants | Time-limited trials or small execution credit allocations |
| Code, verification, and documentation contributors | Time-limited access to advanced features and capped cloud and AI credits |
| Active, sustained maintainers | Longer-term access, development support, and credits according to need |
Product feature access will be managed separately from metered cloud and AI credits. Credits will have monthly limits, with selection and renewal conditions disclosed.
Contributors may participate without receiving support and may use other tools. Positive reviews and paid purchases are not conditions of support.
A future foundation
We remain open to a separate foundation or shared governance organization over time. We would revisit the structure when public education and research need independent funding and governance, or when multiple semiconductor and EDA companies need an organization to address common industry problems.
Neither US 501(c)(3) nor 501(c)(6) is an established status for PCCX. An organization pursuing public educational or research purposes and one improving common industry conditions have different requirements. Any future choice must fit the actual activities and governance.
Official references: IRS 501(c)(3) requirements · IRS 501(c)(6) business leagues
In the meantime, we aim to maintain asset inventories, license notices, contribution records, and operating rules. An actual transition would separately explain the operator, governance, scope of asset and rights transfers, and handling of support funds. A future plan does not itself transfer existing rights.
Documents and contact
This page explains PCCX's current operating relationships and intended operating principles. It does not replace or amend asset licenses, rights notices, or separately executed contracts.
- Rights and licensesTerms for repository assets
- Code licenseApache License 2.0
- Trademark policyPCCX names and brand use
- IP policyAsset boundaries and contribution rights
- Contribution guideProposals and contributions
Questions and corrections
For questions about operations, rights, or external support, contact [email protected]. Public proposals can be raised in GitHub Discussions.
Change record: September 27, 2026 — Initial description of company-led operations, asset terms, the planned developer support program, and a potential foundation transition.