Skip to content

docs: record registry_env as a stopgap bundle in decision 5 #183

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jcschaff merged 1 commit into from
Sep 23, 2026
Merged

docs: record registry_env as a stopgap bundle in decision 5 #183

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 15 additions & 1 deletion docs/strategy.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Strategy

**Status:** draft, opened 2026-09-13, revised 2026-09-22 (decision 5 added). This is how we reach the goals in [goals.md](goals.md): the layering, the
**Status:** draft, opened 2026-09-13, revised 2026-09-22 (decision 5 added) and 2026-09-23 (`registry_env` as a stopgap bundle). This is how we reach the goals in [goals.md](goals.md): the layering, the
decisions taken, the order they land in, and the risks. It changes as decisions land. Each decision cites the
analysis it rests on rather than repeating it, so this document stays short and the evidence stays where it was
measured.
Expand Down Expand Up @@ -264,6 +264,20 @@ independently. In order of preference:

Namespacing process addresses by entry removes the flat-name collision as a side effect.

**Today's `registry_env` is the first bundle, and a stopgap.** The service currently runs every composite in one
image, `registry_env`, holding every library in its pinned list (COPASI, Tellurium, ReaDDy, multiscale actin) plus
the toolkit. That is an all-in-one environment, the shape this section rejects at scale. It stays, for now, because
those four coexist and cover the composites people actually submit today, the likely first G1 composite included. In
the terms above it is simply the first pre-built bundle (rule 2) arrived at before rule 1 exists. Three rules keep it
from becoming the registry by default:

- **It grows only while additions are conflict-free.** The first library that will not co-install is the signal to
build the per-composite resolver, not to force the library in.
- **It is not the registry.** Entries are registered and curated individually; membership of the bundle confers no
curation level.
- **It is retired into rule 1, not replaced beside it.** Once the resolver exists, this image becomes one cached
resolution among many, identified by digest like the rest.

### Adapters

Adapters are a category of the same registry, on the same ladder. They cannot reach *curated* without declared port
Expand Down
Loading