Public-source use
Repository license terms apply to public code and must be reviewed per core.
Docs
This page explains the structured format used for AccelFury IP core pages, JSON exports, integration notes and verification boundaries.
Schema
Each public core is represented by typed data and exported as JSON.
| Field | Purpose |
|---|---|
| slug, name, shortDescription | Stable identification and catalog copy. |
| category, tags, domain | Filtering, discovery and related-core logic. |
| status, verificationLevel | Evidence-aware maturity and validation state. |
| license, commercialSupport | Open/commercial use boundary. |
| repositoryUrl, docsUrl, packageUrl | Public evidence and package links where available. |
| supportedBoards, supportedToolchains | Target support without implying measured validation. |
| interfaces, clocks, resets, parameters, ports | Integration contract. |
| resourceUsage, benchmarks | Measured or explicitly pending evidence. |
| maturityScore | Optional. Omit unless a public formula and evidence source are documented. |
| limitations, aiSummary | Do-not-overclaim guidance for humans and LLMs. |
type CoreStatus =
| 'concept'
| 'planned'
| 'in_development'
| 'prototype'
| 'simulation_tested'
| 'board_tested'
| 'production_ready'
| 'deprecated';
Rules
A core page must say what the core does, what it does not do, target support, gaps and limitations.
License
Public code and proprietary use are separate review paths.
Repository license terms apply to public code and must be reviewed per core.
Closed-source, proprietary or customer-delivered bitstream use requires direct licensing discussion where stated.
Paid support depends on integration scope, board target and release criteria.