Implementation
Design decisions
Most of the difficulty in a cross-institution run is operational rather than
statistical: version skew between sites, partially completed configuration, and setup
instructions a partner has to interpret. The following address those.
A single configuration file
federation.yaml declares who you are, who your partners are, and what
each is doing. Every generator, configuration file, document template and check
reads from it. Nothing in src/ contains a coordinator identity, an
endpoint UUID or a site name, and CI verifies this, since the repository has to be
usable by someone other than its author.
Partner bundles are generated, not templated
A bundle is a directory containing a partner's configuration fully resolved:
their site ID, their data assignment, the coordinator's identity, and their
scheduler's provider block, along with their two setup documents with no
placeholders remaining.
Partner-facing content is a closed set
Bundles are built from docs/partner/ and nowhere else, enforced in
code, so nothing outside that tree can reach a partner by accident.
Exact version pinning
Every site runs byte-identical versions of the Globus Compute stack. Version skew
does not fail at install time; it surfaces as a deserialization error several
rounds into a run on another institution's cluster. constraints.txt
pins the stack and preflight --check pins verifies it.
Troubleshooting is indexed by symptom
The troubleshooting registry is keyed on the error a partner actually sees, and
records the underlying mechanism alongside the fix, so a message resolves to a
cause rather than to a support thread.
The CLI
appfl-bio-suite preflight [--experiment X] environment, pins, configs, endpoints
appfl-bio-suite endpoint status [SITE] is it online
appfl-bio-suite endpoint smoke [SITE] round-trip: does it actually work
appfl-bio-suite identity validate <mapping.json> catch mapping bugs offline, in a second
appfl-bio-suite simulate EXPERIMENT --scenario NAME generate and split synthetic data
appfl-bio-suite run EXPERIMENT run it
appfl-bio-suite partner-bundle EXPERIMENT --site X a partner's complete setup package
appfl-bio-suite watch build | serve | export the federation, on a map
appfl-bio-suite ga4gh duo | drs | trs | tes data use, data objects, tools, tasks