Projects¶

This is the fastest way to understand what each public Bijux repository does. The projects stay separate in ownership, but they still share a common runtime language and a common standards layer.

Open this after Platform when you want the fastest sense of where each repository belongs.

If your question is still about governance or shared standards, open Bijux Infrastructure-as-Code or Bijux Standards first. Projects begin where those two shared layers stop and repository-owned runtime, delivery, knowledge, or domain work takes over.

graph TD
    foundations["Shared foundations<br/>bijux-iac + bijux-std"] --> core["Shared runtime backbone<br/>bijux-core"]
    core --> canon["Canon"]
    core --> atlas["Atlas"]
    core --> domains["Proteomics + Pollenomics"]
    core --> systems["Telecom + Genomics"]

Primary Responsibility Clusters¶

Capability cluster	Repositories
runtime authority and execution governance	Bijux Core
knowledge-system orchestration and reasoning boundaries	Bijux Canon
public delivery interfaces and service publication	Bijux Atlas
proteomics scientific product workflows	Bijux Proteomics
evidence-mapping product workflows	Bijux Pollenomics

Learning is a top-level branch reference, not a peer project repository: Learning catalog.

The foundations that support all of these are:

bijux-iac for GitHub governance as code
bijux-std for shared standards

The shared runtime backbone for the project family is:

bijux-core for CLI, DAG, evidence, and release discipline reused across projects

The public hub for the family is:

bijux.github.io for documentation and movement across the family

runtime and governance backbone

Bijux Core

The runtime authority repository for CLI and DAG execution.

It keeps execution behavior and governance boundaries stable under long-term change.

Open Bijux Core

governed knowledge system

Bijux Canon

The knowledge-system orchestration repository.

It separates ingest, indexing, reasoning, orchestration, and runtime control into durable interfaces.

Open Bijux Canon

data and service delivery

Bijux Atlas

The public delivery-interface repository for APIs, datasets, and publication routes.

It treats service delivery as a maintained product surface.

Open Bijux Atlas

applied scientific products

Bijux Proteomics

The proteomics scientific product repository.

It applies platform discipline to evidence-heavy discovery workflows.

Open Bijux Proteomics

evidence and site selection

Bijux Pollenomics

The evidence-mapping scientific product repository.

It keeps archaeology/eDNA/aDNA interpretation outputs traceable and reproducible.

Open Bijux Pollenomics

Primary Responsibility By Repository¶

Repository	Primary job	What you can inspect quickly
Bijux Core	runtime authority and execution governance	CLI/DAG split, evidence routes, release discipline
Bijux Canon	governed knowledge-system decomposition	ingest/index/reason/orchestrate/runtime layer split
Bijux Atlas	data-service delivery and operated publication	API, datasets, OpenAPI, reporting, control plane
Bijux Proteomics	proteomics scientific product engineering	workflow contracts, evidence posture, lab-facing outputs
Bijux Pollenomics	evidence-mapping scientific product engineering	mapped outputs, report bundles, reproducible evidence handling

Reading Guide¶

If you care most about...	Start here
shared governance and repo-wide review controls	Bijux Infrastructure-as-Code
shared standards and cross-repository continuity	Bijux Standards
platform and runtime engineering	Bijux Core
governed AI and knowledge systems	Bijux Canon
data delivery and service architecture	Bijux Atlas
bioinformatics and scientific product work	Bijux Proteomics
evidence mapping and field-oriented domain systems	Bijux Pollenomics
teaching and engineering communication	Learning catalog

Reading Rule¶

Use the cards for quick orientation, then open the project pages for repository-owned details.