Publish assumptions, artifacts, and evidence together.
Cerebral Chips intends to build in public where technically and legally practical, beginning with useful engineering artifacts rather than unsupported repository promises.
Repositories remain unpublished until scope, license, and evidence are confirmed
Open engineering should make decisions easier to inspect and reproduce.
Architecture notes, workload models, software, RTL, verification methods, and evidence are intended to be published in useful increments rather than as marketing placeholders.
No repository card appears before a real repository exists.
Repository names, URLs, licenses, hardware targets, supported workloads, and contribution rules remain intentionally absent until verified.
Useful systems can precede custom silicon.
Open RISC-V cores, toolchains, simulation, and accessible hardware may provide early environments for runtime, kernel, and verification bring-up after dependency review.
Candidate specifications need status and rationale.
Published architecture material should separate proposals, evaluated options, selected decisions, implemented behavior, and verified evidence.
Implementation follows a reviewable dependency and license policy.
Source publication is intended where ownership, upstream obligations, documentation, build instructions, and validation status are clear.
Results require workloads, methods, and reproducible evidence.
No benchmark is published without the model, configuration, hardware or simulator state, measurement method, limitations, and an inspectable evidence path.
Collaboration channels exist before public contribution workflows.
Contribution guidance will follow real repositories and maintainable review capacity. Technical collaboration can begin through the published contact channels.