Hardware · reference designs · fleet · silicon
Core is where the Implexus engine meets hardware: the reference designs an OEM builds against, the FPGA bitstreams and ASIC IP that run it, the fleets that carry it, and the pipeline that takes a new design to a shuttle. Efficiency first, nothing wasted.
Three surfaces
The spec an OEM builds against, the hardware in the field, and the silicon that comes next, in one place. Credentials and routing live next door in AIOS.
01 · Reference designs
Every reference design carries its pinout, power envelope, FPGA bitstream and ASIC IP blocks, versioned together. An OEM reads one page and knows what to build against.
designs · pinouts · envelopes · bitstreams · IP blocks · errata
02 · Fleet
A device enrols with a one-time token from AIOS and reports back here. Firmware and bitstreams roll out in waves, canary first, rollback ready. Telemetry sits beside the device.
devices · sites · firmware · waves · telemetry · alerts
03 · Silicon
Lint, test, synthesise and harden in the cloud with a pinned PDK. Review the layout and reports in Core. Submit to a shuttle run without leaving it.
projects · runs · artefacts · shuttles · packaging · delivery
How it fits
Both sit on the Implexus engine and its three endpoints. Core owns what the engine runs on; AIOS owns who may call it, how it is routed, and what happened. An OEM moves between them with one account.
Go to AIOS →Engineering rails
Spec, bitstream and IP blocks share one revision. No mismatched pairs.
Every silicon run names its PDK hash. Reproducible years later.
A known issue on RD-2 shows on every page that references RD-2.
Devices speak to Core with the certificate AIOS issued them. Nothing else gets in.
Firmware never goes to the whole fleet at once.
Efficiency figures appear only with a method and a date. Otherwise the chart says “sample”.
Core Integrate · for OEMs
Integrate is the signed-in mode of Core for an OEM: the reference design, the conformance checks your product must pass, and, when it passes, the AIOS credentials that let it call the engine.
Integration guide on developer.implexus.io →# check an OEM board against reference design RD-2 rev C core integrate check --design RD-2@C --board ./acme-gw-v1 pinout match power envelope within (4.1 W peak of 4.5 W) bitstream 2.4.1 conformance 42 / 42 # passed: request credentials from AIOS for this board class aios credentials create --profile oem-acme-gw --bind-design RD-2@C
Access
Core comes with the licence, on the same terms as the engine. Four licence types today; more are coming. Rates are agreed in the licensing conversation and are not shown here.
A sandbox workspace and one fleet.
One product line, royalty per device.
Many product lines, one agreement.
Teaching and research use.