Organizational architecture

One registry.
Several accountable surfaces.

Elixpo is organized around evidence and responsibility, not a claim that every project shares one technical stack. The registry provides shared identity; each project and publication surface retains the architecture it actually needs.

System map

How work moves through Elixpo.

The diagram separates owning repositories, the Chapter coordination layer, specialized publishers, and the public record. Arrows describe information and release flow—not automatic ownership transfer.

flowchart LR
  registry[Canonical registry] --> portal[elixpo.com]
  registry --> standards[Repository Standard]
  standards --> chapter[Elixpo Chapter]

  projects[Project repositories] --> chapter
  researchProjects[Research repositories] --> chapter
  services[Operated services] --> chapter

  chapter --> releases[Public releases]
  releases --> portal
  researchProjects --> research[research.elixpo.com]
  projects --> packages[packages.elixpo.com]
  research --> portal
  packages --> portal

  contributors[Contributors and maintainers] --> projects
  contributors --> researchProjects
  contributors --> services
  portal --> record[Lifecycle, custody, credit, and history]

  classDef authority fill:#142018,color:#ffffff,stroke:#142018,stroke-width:2px;
  classDef work fill:#f0e6d3,color:#142018,stroke:#b8aa91;
  classDef publish fill:#dfe9ff,color:#142018,stroke:#7891c7;
  classDef evidence fill:#dfeee5,color:#142018,stroke:#75a58a;
  class registry,standards,chapter authority;
  class projects,researchProjects,services,contributors work;
  class portal,research,packages publish;
  class releases,record evidence;

Canonical registry

Defines every repository’s public family, lifecycle, stewardship relationship, custody, and verification state.

Chapters

Time-bounded public build and release programmes for active work with a concrete, documented outcome.

Member Projects

Independently led projects with an ongoing relationship and explicit authority and stewardship boundaries.

Project repositories

Own source code, experiments, evidence, releases, licenses, maintainers, and project-specific technical documentation.

Public dossiers

Search-readable portal routes that connect work, status, repositories, evidence, people, packages, and research publications.

Shared standards

Define repository structure, contribution paths, review workflows, licensing defaults, conduct, metadata, and brand rules.

Specialized repositories

Research publishing and package distribution are maintained separately.

The main portal owns organization-level discovery and classification. The specialized repositories own their publication and distribution operations while consuming shared identifiers and metadata contracts.

RESEARCH.ELIXPO

Research publisher

Papers, citations, datasets, models, demonstrations, and reproducibility presentation. Source experiments and evidence remain in their project repositories.

Planned research destination

PACKAGES.ELIXPO

Distribution authority

Package builds, signed APT metadata, installers, checksums, release artifacts, and distribution documentation.

Open package distribution