Skip to content

Platform

Platform explains how the Bijux repository family is held together.

It shows the shared foundations underneath the family, the runtime backbone in the middle, and the project and learning surfaces built on top.

It introduces the family shape without replacing the deeper bijux-iac and bijux-std branches.

Start with responsibility before repository count. The key question is why each part of the family has its own home, yet still reads as one system.

Platform Map

graph TD
    foundations["Shared foundations<br/>bijux-iac + bijux-std"] --> hub["Documentation hub<br/>bijux.github.io"]
    foundations --> core["Shared runtime backbone<br/>bijux-core"]
    foundations --> projects["Project repositories"]
    hub --> projects
    core --> projects
    projects --> learning["Learning programs<br/>bijux-masterclass"]

What This Branch Covers

  • the shared layers underneath the family
  • the route from foundations to projects and learning
  • the best next page for the question you want to answer

Where To Continue

System Shape

Control Plane

`bijux-iac` keeps GitHub governance visible as code instead of leaving it buried in repository settings.

Hub

`bijux.github.io` is the public route layer: it helps readers move through the repository family, but it is not the source of shared shell behavior.

Core

`bijux-core` is the shared runtime backbone for command surfaces, DAG behavior, evidence, and repository discipline used across the project family.

Canon

The governed knowledge-system stack for ingest, indexing, reasoning, orchestration, and controlled runtime behavior.

Atlas

The delivery and control-plane surface for APIs, datasets, docs-aware checks, and operational reporting.

Bijux Standard Layer

`bijux-std` is the shared standards source for documentation shell continuity, cross-repository checks, and promoted shared make behavior.

Products And Programs

Canon, Atlas, Proteomics, Pollenomics, Telecom, Genomics, and Masterclass consume these shared layers while owning their own knowledge, delivery, domain, or learning work.

Reading Order

Read this first when you need to understand... Open
the layered structure of the whole public system family System map
where live GitHub governance is owned and enforced Bijux Infrastructure-as-Code
where shared standards are defined and verified across repositories Bijux standard layer
where delivery work shows up most clearly across the repositories Delivery surfaces
how the engineering extends into domain-heavy product work Applied domains
which qualities recur across the public work Work qualities
why the docs shell is shared instead of duplicated carelessly Documentation network