Date: 2026-03-12 Author: Codex (GPT-5) Purpose: define the recommended one-by-one execution order for full-scope publisher enrichment across the current OSHConnect-Python public-data fleet. Scope: nws, ndbc, coops, aviation_wx, opensky, iss, usgs_water, usgs_nims, usgs_eq Relationship to prior analysis: this plan operationalizes the findings in All_Bootstraps_Full_Scope_Gap_Analysis_2026-03-12.md and its appendices.

Do not enrich the publishers in alphabetical order, by repo age, or only by which one looks weakest.

The recommended sequence is:

1. ISS
2. USGS Water
3. NWS
4. USGS EQ
5. OpenSky
6. NDBC
7. USGS NIMS
8. CO-OPS
9. Aviation WX

This is not a pure maturity ranking. It is a rework-minimizing, semantics-first execution order designed to:

• close the biggest current-fleet contradiction first;
• resolve dependency roots before dependent publishers;
• establish canonical templates before catch-up work;
• convert the strongest current ideas into reusable patterns early;
• delay the lowest-leverage catch-up work until the family conventions are already stable.

The order above was chosen using six criteria.

If a publisher slot is supposed to exist in the active fleet but is materially incomplete, that gap should be closed early because it corrupts the credibility of the whole corpus.

This is why ISS is first.

If one publisher depends on another publisher's systems, semantics, or sidecars, the upstream publisher should usually be enriched first.

This is why USGS Water must precede USGS NIMS.

The first few enrichments should define reusable family standards:

• canonical station-family enrichment expectations;
• canonical Pattern C feed-adapter expectations;
• canonical Pattern A companion-datastream expectations.

This is why NWS, USGS EQ, and OpenSky are early, and why CO-OPS and Aviation WX are late.

Publishers whose current artifact state is contradictory, misleading, or absent should be addressed before publishers that are already materially present and inspectable.

This is why ISS and USGS Water are ahead of already-packaged publishers like USGS NIMS and USGS EQ.

An enrichment should be prioritized earlier if finishing it gives the rest of the fleet a better template, stronger test discipline, or clearer vocabulary.

This is why NWS is ahead of CO-OPS and Aviation WX, and why USGS EQ is ahead of a second-pass refinement on already-strong USGS NIMS.

The thinnest publishers should not be first if their enrichment would otherwise be designed in a vacuum.

This is why CO-OPS and especially Aviation WX are late-phase work rather than first-phase work.

Before the first publisher enrichment begins, define these fleet-level guardrails once and then reuse them for every publisher:

1. a standard full-scope package contract
   • required folders
   • required manifests
   • required worked examples
   • required patch candidates
   • required source-corpus notes
2. a standard semantic acceptance checklist
   • procedure
   • system
   • datastream
   • deployment
   • feature-of-interest
   • provenance
   • units and null semantics
3. a standard round-trip verification checklist
   • POST
   • GET back
   • SensorML inspection
   • result-schema inspection
   • observation write-path verification
4. a standard runtime hardening checklist
   • TLS verification
   • auth handling
   • retry and dedupe policy
   • logging and observability
5. a standard artifact state label
   • metadata pack
   • total pack
   • source basis
   • historical artifact
   • migration artifact

This preflight is important because otherwise the first three enrichments will each reinvent package shape and acceptance criteria.

1. ISS
2. USGS Water
3. NWS

This wave fixes the biggest fleet contradiction, repairs the most important current artifact mismatch, and establishes the first canonical station-family enrichment method.

4. USGS EQ
5. OpenSky
6. NDBC
7. USGS NIMS

This wave completes the strongest reusable family references:

• Pattern C total-package reference;
• second Pattern C implementation;
• multi-stream station-family reference;
• Pattern A companion-datastream reference.

8. CO-OPS
9. Aviation WX

This wave uses already-proven conventions to bring the remaining station-family publishers to full-package parity with much lower design risk.

Why first

• The current fleet is semantically incomplete while ISS remains a runtime without a current bootstrap.
• The migration path is unusually well defined because scripts/bootstrap_iss.py already exists as a strong precedent.
• The project should not start a long enrichment program while one advertised active publisher is still missing its bootstrap artifact.

What "full-scope enrichment" means here

• migrate bootstrap_iss.py into publishers/iss/
• modernize it to current helper-layer and env conventions
• produce a current ISS package, not just a migrated script
• preserve the dual-product model and rich SensorML
• remove every legacy credential, TLS, and hardcoded-endpoint anti-pattern

Exit condition

ISS is no longer a special-case hole in the active fleet.

Why second

• USGS NIMS depends on it structurally
• the current repo has a claimed total pack that is not actually present on disk
• the water publisher is already semantically stronger than its artifact state suggests

What "full-scope enrichment" means here

• materialize the missing total package
• reconcile research-note claims with actual on-disk artifacts
• preserve and extend the strong parameter/statistic semantics
• formalize datum, QC, null, and feature-of-interest semantics more explicitly

Exit condition

USGS Water becomes the canonical USGS station-family base that NIMS can depend on without ambiguity.

Why third

• NWS is the best place to institutionalize the lessons from the historical SensorML field-shape failure
• it already has substantial adjacent metadata-pack work
• it can become the station-family proof point for round-trip validation discipline

What "full-scope enrichment" means here

• converge the best metadata-pack content into a live canonical package
• codify station-family semantic-contract conventions
• add explicit round-trip verification expectations
• deepen QC, null, and feature-of-interest semantics

Exit condition

NWS becomes the reference station-family enrichment against which later station publishers are judged.

Why fourth

• it is already one of the strongest current total packages
• it can define the canonical Pattern C total-package template with the least uncertainty
• its lifecycle, provenance, and crosswalk semantics are unusually rich and reusable

What "full-scope enrichment" means here

• turn strong current package materials into the authoritative Pattern C template
• deepen summary/detail/FDSN crosswalk semantics
• formalize lifecycle, supersession, and quality semantics
• define the feed-adapter artifact and acceptance pattern other Pattern C publishers should follow

Exit condition

USGS EQ becomes the canonical Pattern C reference package.

Why fifth

• OpenSky is already a strong Pattern C implementation, but it still trails USGS EQ in package maturity
• once USGS EQ defines the full Pattern C standard, OpenSky can be upgraded without inventing a second incompatible model

What "full-scope enrichment" means here

• graduate from metadata pack to total package
• formalize auth-aware and budget-aware operational semantics
• deepen data quality, provenance, and coverage semantics
• align its package shape to the Pattern C standard frozen in the previous step

Exit condition

The fleet has two aligned Pattern C references rather than one strong feed-adapter and one separate event-feed model.

Why sixth

• NDBC is the richest current station-family multi-stream case
• it benefits from earlier station-family and Pattern C decisions
• it is the best place to formalize how imagery-related semantics coexist with a fixed-station observation model

What "full-scope enrichment" means here

• convert the existing metadata pack into a total-package-grade artifact
• deepen the buoy-plus-imagery relationship model
• sharpen QC, null, and provenance semantics
• decide whether NDBC becomes the canonical "multi-stream station" reference

Exit condition

The station family now has a strong simple reference and a strong multi-stream reference.

Why seventh

• it is already strong and materially present
• its next gains depend more on dependency clarification than on raw metadata creation
• it benefits from earlier USGS Water and imagery-related lessons

What "full-scope enrichment" means here

• formalize the dependency contract on USGS Water systems
• decide whether selected-camera-per-station is permanent policy or transitional implementation
• deepen coverage, product, and asset provenance semantics
• align Pattern A packaging to the conventions proven earlier

Exit condition

USGS NIMS becomes the canonical Pattern A reference with explicit dependency semantics.

Why eighth

• it is a good publisher, but not a template setter
• it currently lacks a pack
• its enrichment can be done faster and more cleanly after station-family conventions are settled

What "full-scope enrichment" means here

• create a full package from scratch
• sharpen product-family, datum, and coastal semantics
• apply already-proven station-family packaging and validation discipline

Exit condition

CO-OPS reaches full-package parity without forcing the project to learn station-family lessons the hard way.

Why ninth

• it is the thinnest current publisher
• it has the least leverage on the rest of the fleet
• it will benefit most from arriving after the station-family conventions and package contract are already stable

What "full-scope enrichment" means here

• create its first full package
• deepen airport/system/procedure semantics
• formalize aviation vocabulary and null/missing-value handling
• bring it to parity without turning it into the family template

Exit condition

Aviation WX is no longer the semantic and artifact outlier of the current fleet.

Do not run the whole program as nine disconnected tasks. Use checkpoints.

Lock down:

• the standard package contract
• the migration-artifact policy
• the dependency-root policy

Lock down:

• canonical station-family acceptance criteria
• canonical Pattern C acceptance criteria
• round-trip verification expectations

Lock down:

• final Pattern C conventions
• final multi-stream station conventions
• final Pattern A dependency conventions

Run a parity review to confirm the lagging station-family publishers now meet the same artifact and semantic baseline as the rest of the fleet.

For this program, done should mean more than "a richer bootstrap file exists."

For each publisher, completion should require:

• a current bootstrap aligned to the target model
• a materially present package on disk
• corrected and verified provenance corpus
• explicit semantic-contract notes
• round-trip verification evidence
• a runtime follow-on list if runtime work remains outside the package scope

If the project follows that rule, the enrichment program will produce a canonical fleet rather than a collection of better comments.