Build ecosystem
Market and core compatibility
Market v1 is a GitHub-hosted FPGA core catalog, creator submission flow and moderation gate for Build-compatible free/open or paid source-available cores.
Use when
- You want reusable cores that may fit future Build graph workflows.
- You are submitting a GitHub-hosted core for compatibility and license review.
- You need the boundary between catalog listing, Build promotion and AccelFury af review.
Outcome
- Free/open and paid source-available options are separated before submission.
- Compatibility evidence is separated from signoff claims.
- Submitted cores enter moderation instead of automatic publication.
Available now
- Public Market catalog, /api/market/cores and static /data/cores.json fallback.
- Core detail pages with license, language, top module, interfaces and source notes.
- Authenticated submission form, creator dashboard and license guide for moderation and review.
Compatibility checklist
- Public GitHub repository and license choice: open/free or paid source-available commercial terms.
- Top module, parameters, interfaces, clocks and reset assumptions.
- Simulation, synthesis or other tool evidence with version notes.
- AccelFury af metadata path or a clear plan for adding it.
Submit-flow
- Sign in via GitHub or Google.
- Open /market/submit and follow the 4-step license wizard.
- After moderation, published cores are eligible for paid Build usage.
License chooser
- Wizard ranks the eight license templates from MIT to ASAL-1.0-COMMERCIAL.
- Top-3 recommendations are rendered side-by-side with use-when / pros / cons / caution.
- /market/licenses keeps the full comparison and per-license anchors.
Auto-validation pipeline
- GitHub raw fetch reads the declared manifest paths on a public repository.
- Manifest is checked for required v1 fields; AccelFury af manifest is parsed for core_id and top.
- Optional /v1/af/check bridge produces a draft compatibility verdict.
- Statuses populate draft af_status, verification_status and build_compatible flags; admin review still gates publication.
Manual payouts
- Creator earnings live in market_core_usage_events; payouts are processed manually in alpha.
- Admins export unpaid earnings as CSV and record mark-as-paid entries through /admin/market.
- Creators see Payout history on /market/creator and are notified by email when a payout is dispatched.
Boundary
- Paid Build usage is ledgered after review; direct marketplace checkout and automated payouts are not enabled.
- No automatic Build promotion.
- No timing, CDC/RDC or board signoff is implied by a catalog listing.