Repos

marola is seven repos: the umbrella, the devkit and five code or data repos. This page says which repo owns what, what each publishes, and how a consumer pins it. How the product works end to end is Architecture; why the code was split this way is The split.

Three layers

Layer	Holds	Can a repo override it?
Umbrella (marola-dev/marola)	The workspace AGENTS.md, the ways of working, MIPs and their .tasks.md, MIP and cross-repo parent issues, the phase list, the aggregated docs site, the submodule pointers	—
Devkit (marola-devkit)	The shared harness at a tag: dev-flow tools, git hooks, the Claude Code plugin, reusable workflows, the just module, the invariants block	Yes: a repo opts into each piece, and its AGENTS.md says what it leaves out
Repo	Its own AGENTS.md, docs/, build, tests, gates, repo-only skills and rules	It owns them outright

The org invariants are the exception to "the repo wins": cost and deployment safety, no secrets in code, the agent-ready gate, the three commit trailers and phase discipline. A repo may make them stricter, never looser. Every repo's AGENTS.md carries them as the devkit's invariants block, and agents-check compares that copy with the pinned devkit's.

The routing table

Where a change belongs, and what moves when it lands. This is the table's only copy: the umbrella's AGENTS.md links here, and scripts/agents_repos_check.sh fails if it restates it. The pin each artifact moves is in Artifacts, pins and dispatches.

Repo	Owns	Publishes	Consumers	Moved by
marola (umbrella)	Ways of working, MIPs, research, PHASES.md, the docs site, the submodule pointers, the eli5 skill	docs.marola.dev; stats/ on marola-site's site-data	Readers; marola-site's stats panel	docs.yml, pointer-sync.yml, ci.yml
marola-devkit (not a submodule)	Dev-flow tools, git hooks, the marola-devkit plugin, reusable workflows, the invariants block	A tag: flake input, plugin marketplace, uses: workflows	Every repo	A tag
marola-app	The Scala 3 + Kyo product on JDK 25 (sbt modules core, local, cli): the pipeline, CLI, MCP and chat servers, the benchmark runner; the OODS ingest code with MIP-0056	The image ghcr.io/marola-dev/marola-app; ml-resources-<tag>.tar.gz; Scaladoc on its api-docs branch; coverage/ and smoke/ on site-data	site, ml, oods; the umbrella's docs	docker.yml, release.yml (a v* tag), api-docs.yml, ci.yml, docker-smoke.yml
marola-site	The map: the static page, areas.json, live checks, the site-data branch	marola.dev on GitHub Pages	Visitors	site.yml: every 3 h, on an image bump or a site-data dispatch
marola-corpus	The sourced ocean knowledge (Markdown under knowledge), the corpus-doc skill	marola-corpus-<tag>.tar.gz	app, ml	release.yml (a v* tag)
marola-ml	Offline Python: the DSPy prompt compile, the marola-sea fine-tune, the benchmark gate and its kept runs	Compiled-prompt PRs; marola-sea on Hugging Face; the image ghcr.io/marola-dev/marola-ml (Ollama with the fine-tuned model, :local once the benchmark gate passes); pdoc on its api-docs branch	app; the umbrella's docs	compile-prompt.yml, marola-sea-publish.yml, docker-local.yml, api-docs.yml
marola-oods	The Open Ocean Data Store's data only (data/oods/, MIP-0056); empty for now	The dataset; an export tag (planned, MIP-0056 §5.5)	app	The app's ingest workflow (with MIP-0056); oods-check.yml

Each repo's README is its landing page on this site, under 5 Repos.

The contracts

No repo reads another repo's tree, in CI or in tests, and no consumer builds its producer from source. A producer publishes a versioned artifact; a consumer pins it and moves to a new version by bumping the pin in a PR. Inside an umbrella checkout the submodules sit side by side, but that is a convenience for people and agents, never a build input.

Artifacts, pins and dispatches

Artifact	Produced by	Read by	Pinned by
The app image, ghcr.io/marola-dev/marola-app:<tag>@<digest>	marola-app docker.yml, on a push to main	marola-site site.yml (the boards, data only), marola-ml docker-local.yml (the benchmark), marola-oods oods-check.yml	marola-image in each consumer, tag and digest
marola-corpus-<tag>.tar.gz	marola-corpus release.yml, on a v* tag	marola-app (unpacked into .tmp/knowledge; the image ships /app/knowledge), marola-ml	corpus.version in each consumer
ml-resources-<tag>.tar.gz (the app's prompt and fixture resources)	marola-app release.yml, on a v* tag	marola-ml's fine-tune dataset and benchmark gate	resources.version
Each repo's api-docs branch: one force-pushed commit of generated API docs	marola-app and marola-ml api-docs.yml (the devkit's reusable workflow), on a push to main	The umbrella's prepare-docs.sh, under 5-Repos/<name>/api-docs/	None: the latest main
Compiled-prompt PRs (recommendation_prompt.json, review_prompt.json)	marola-ml compile-prompt.yml, run by hand	marola-app's resources, once the PR merges	The file in marola-app
The site-data branch: coverage/, smoke/, stats/	marola-app ci.yml and docker-smoke.yml (each then sends a site-data-updated dispatch); the umbrella's ci.yml writes stats/ with no dispatch	marola-site site.yml	None: the branch's content
OODS ingest commits and export	marola-app's ingest workflow (MIP-0056, not built)	marola-oods; the export back to marola-app	An export tag and its env var (planned)
notify-umbrella dispatches (submodule-docs-updated)	Every repo's notify-umbrella.yml, on a push to main touching README.md or docs/	The umbrella's docs.yml and pointer-sync.yml	The gitlinks, moved by the sync PR
A devkit tag	marola-devkit	Every repo	flake.lock, @v…/devkit-ref:, the marketplace ref
The ml image, ghcr.io/marola-dev/marola-ml:local (candidates :local-<sha>)	marola-ml docker-local.yml, on a push to main, promoted after the benchmark gate	Nothing yet	Nothing

The site reads each repo's api-docs branch, not a release asset.

A contract change follows the producer: it merges and releases first, each consumer bumps its pin in its own PR, and the umbrella's pointers move last, through the sync PR.