From 46efd710ea997acfd66b6dd33e9a59f1f92e0e54 Mon Sep 17 00:00:00 2001 From: 577-Industries Date: Mon, 18 May 2026 09:33:07 -0400 Subject: [PATCH 1/2] feat(phase-ii): assemble Phase II evidence package per dispatch spec Per specs/2026-05-18-PhaseII-evidence-assembly-spec.md. Creates phase-ii/ with: - README.md (overview + refresh policy) - evidence-package.md (7-category curated summary) - commercialization-plan-refined.md (5 Phase I learnings -> Phase II refinement) - phase-ii-proposal-draft.md (scaffold mirroring Phase I sections 1-8) - letters/README.md (8 LoI slots, inventory only - no fake PDFs) - customer-discovery/README.md (interview inventory) - nasa-engagement/README.md (NASA-center contact inventory) Adds .github/workflows/phase-ii-pdf.yml for Pandoc -> PDF render + lychee link-check on evidence-package.md. Updates mkdocs.yml nav with new Phase II section pointing at the four curated docs via include-markdown proxies in docs/phase-ii/. Does NOT solicit LoIs / conduct interviews / submit Phase II proposal / modify artifact-repo content. Branch stays unpushed - operator merges. --- .github/workflows/phase-ii-pdf.yml | 89 +++++++ .../commercialization-plan-refined.md | 4 + docs/phase-ii/evidence-package.md | 4 + docs/phase-ii/index.md | 4 + docs/phase-ii/phase-ii-proposal-draft.md | 4 + mkdocs.yml | 5 + phase-ii/README.md | 45 ++++ phase-ii/commercialization-plan-refined.md | 158 +++++++++++ phase-ii/customer-discovery/.gitkeep | 0 phase-ii/customer-discovery/README.md | 77 ++++++ phase-ii/evidence-package.md | 207 +++++++++++++++ phase-ii/letters/.gitkeep | 0 phase-ii/letters/README.md | 39 +++ phase-ii/nasa-engagement/.gitkeep | 0 phase-ii/nasa-engagement/README.md | 79 ++++++ phase-ii/phase-ii-proposal-draft.md | 247 ++++++++++++++++++ 16 files changed, 962 insertions(+) create mode 100644 .github/workflows/phase-ii-pdf.yml create mode 100644 docs/phase-ii/commercialization-plan-refined.md create mode 100644 docs/phase-ii/evidence-package.md create mode 100644 docs/phase-ii/index.md create mode 100644 docs/phase-ii/phase-ii-proposal-draft.md create mode 100644 phase-ii/README.md create mode 100644 phase-ii/commercialization-plan-refined.md create mode 100644 phase-ii/customer-discovery/.gitkeep create mode 100644 phase-ii/customer-discovery/README.md create mode 100644 phase-ii/evidence-package.md create mode 100644 phase-ii/letters/.gitkeep create mode 100644 phase-ii/letters/README.md create mode 100644 phase-ii/nasa-engagement/.gitkeep create mode 100644 phase-ii/nasa-engagement/README.md create mode 100644 phase-ii/phase-ii-proposal-draft.md diff --git a/.github/workflows/phase-ii-pdf.yml b/.github/workflows/phase-ii-pdf.yml new file mode 100644 index 0000000..40e5437 --- /dev/null +++ b/.github/workflows/phase-ii-pdf.yml @@ -0,0 +1,89 @@ +name: phase-ii-pdf + +# Auto-renders phase-ii/evidence-package.md to PDF via Pandoc on every push to main +# that touches the evidence package. PDF is uploaded as a workflow artifact +# (downloadable from the workflow run). The source-of-truth is the .md file; +# the PDF is a derived artifact and is not committed back to the repo. + +on: + push: + branches: [main] + paths: + - 'phase-ii/evidence-package.md' + - '.github/workflows/phase-ii-pdf.yml' + pull_request: + branches: [main] + paths: + - 'phase-ii/evidence-package.md' + - '.github/workflows/phase-ii-pdf.yml' + workflow_dispatch: {} + +permissions: + contents: read + +jobs: + render-pdf: + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v4 + + - name: Install Pandoc and XeLaTeX + run: | + sudo apt-get update + sudo apt-get install -y --no-install-recommends \ + pandoc \ + texlive-xetex \ + texlive-fonts-recommended \ + texlive-latex-recommended \ + texlive-latex-extra \ + lmodern + + - name: Render evidence-package.md to PDF + run: | + mkdir -p build/phase-ii + BUILD_DATE="$(date -u +%Y-%m-%d)" + pandoc phase-ii/evidence-package.md \ + -o build/phase-ii/evidence-package.pdf \ + --pdf-engine=xelatex \ + --variable=geometry:margin=1in \ + --variable=fontsize:11pt \ + --variable=colorlinks:true \ + --variable=linkcolor:blue \ + --variable=urlcolor:blue \ + --variable=toccolor:blue \ + --toc \ + --toc-depth=2 \ + --metadata=date:"$BUILD_DATE" + + - name: Verify PDF rendered + run: | + test -s build/phase-ii/evidence-package.pdf || { + echo "::error::evidence-package.pdf is empty or missing" + exit 1 + } + ls -la build/phase-ii/ + + - name: Upload PDF artifact + uses: actions/upload-artifact@v4 + with: + name: phase-ii-evidence-package-pdf + path: build/phase-ii/evidence-package.pdf + if-no-files-found: error + retention-days: 90 + + link-check: + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v4 + - name: lychee link-check on evidence-package.md + uses: lycheeverse/lychee-action@v1 + with: + args: >- + --no-progress + --max-redirects 5 + --timeout 20 + --accept 200,206,301,302,308,403,429 + --exclude '^mailto:' + --exclude '^https?://(localhost|127\.0\.0\.1)' + phase-ii/evidence-package.md + fail: false # warn-only — flip to true once all referenced artifacts have stable URLs diff --git a/docs/phase-ii/commercialization-plan-refined.md b/docs/phase-ii/commercialization-plan-refined.md new file mode 100644 index 0000000..ebcc2eb --- /dev/null +++ b/docs/phase-ii/commercialization-plan-refined.md @@ -0,0 +1,4 @@ +{% + include-markdown "../../phase-ii/commercialization-plan-refined.md" + rewrite-relative-urls=false +%} diff --git a/docs/phase-ii/evidence-package.md b/docs/phase-ii/evidence-package.md new file mode 100644 index 0000000..562e0cc --- /dev/null +++ b/docs/phase-ii/evidence-package.md @@ -0,0 +1,4 @@ +{% + include-markdown "../../phase-ii/evidence-package.md" + rewrite-relative-urls=false +%} diff --git a/docs/phase-ii/index.md b/docs/phase-ii/index.md new file mode 100644 index 0000000..988bbfa --- /dev/null +++ b/docs/phase-ii/index.md @@ -0,0 +1,4 @@ +{% + include-markdown "../../phase-ii/README.md" + rewrite-relative-urls=false +%} diff --git a/docs/phase-ii/phase-ii-proposal-draft.md b/docs/phase-ii/phase-ii-proposal-draft.md new file mode 100644 index 0000000..9602f0f --- /dev/null +++ b/docs/phase-ii/phase-ii-proposal-draft.md @@ -0,0 +1,4 @@ +{% + include-markdown "../../phase-ii/phase-ii-proposal-draft.md" + rewrite-relative-urls=false +%} diff --git a/mkdocs.yml b/mkdocs.yml index 84359f9..479d732 100644 --- a/mkdocs.yml +++ b/mkdocs.yml @@ -134,3 +134,8 @@ nav: - "Artifact B — Connectors + DONKI": specs/B-connectors-foundation.md - "Artifact C — Fusion-Engine Framework": specs/C-fusion-engine-framework.md - "Artifact D — Gannon Analysis": specs/D-gannon-analysis.md + - Phase II: + - "Overview": phase-ii/index.md + - "Evidence Package": phase-ii/evidence-package.md + - "Commercialization Plan (Refined)": phase-ii/commercialization-plan-refined.md + - "Phase II Proposal (Scaffold)": phase-ii/phase-ii-proposal-draft.md diff --git a/phase-ii/README.md b/phase-ii/README.md new file mode 100644 index 0000000..a4fdda0 --- /dev/null +++ b/phase-ii/README.md @@ -0,0 +1,45 @@ +# HELIOS Phase II — evidence package + +**Last refreshed**: 2026-05-18 (initial assembly) +**Status**: incremental — refreshed each session as new artifacts ship. + +This directory holds the **Phase II proposal evidence package** — operator-facing summary material curated from the existing HELIOS portfolio, ready to embed in the Phase II proposal narrative or hand to NASA-center reviewers as a one-shot orientation packet. + +## Read these in order + +1. **[`evidence-package.md`](./evidence-package.md)** — the single curated summary covering the 7 evidence categories (lead narrative, public artifacts, Gannon ground-truth observations, RFC engagement, Sprint C-Training methodology evolution, kill-gate placeholder, arXiv placeholder). **This is the document the operator hands to reviewers.** An auto-built PDF is uploaded as a workflow artifact on every push to `main` via [`.github/workflows/phase-ii-pdf.yml`](https://github.com/577Industries/helios-program/blob/main/.github/workflows/phase-ii-pdf.yml). +2. **[`commercialization-plan-refined.md`](./commercialization-plan-refined.md)** — Phase I learnings → Phase II strategy refinement. Cites 5 specific Phase I learnings with cross-links to source artifacts. Refines proposal §6.2 revenue model and §6.3 go-to-market based on what Phase I actually surfaced. +3. **[`phase-ii-proposal-draft.md`](./phase-ii-proposal-draft.md)** — section-by-section scaffold mirroring the submitted Phase I proposal's §1-8 structure, with placeholders flagging the Phase II adjustments (§1.3 Gannon retrospective → v2 real-SPP; §2 → Phase II success criteria; §3.3 vision → execution plan; new §4.3 "Phase I results" with cross-links to the evidence package). + +## Operator-action subdirectories + +Each holds a README inventory plus `.gitkeep` placeholder. **No fake LoI PDFs.** The operator fills these as outreach lands. + +| Subdirectory | What it tracks | Operator action | +|---|---|---| +| [`letters/`](https://github.com/577Industries/helios-program/blob/main/phase-ii/letters/README.md) | 8 LoI slots (ML engineer · SME consultant · ≥2 NASA-center · ≥2 ag-industry · 2 spare) | OPERATOR_TODO.md item 6-7 | +| [`customer-discovery/`](https://github.com/577Industries/helios-program/blob/main/phase-ii/customer-discovery/README.md) | ≥10 prospective customers (Ohio/Midwest cooperatives, large family operations, OEM platform teams) | OPERATOR_TODO.md item 5 | +| [`nasa-engagement/`](https://github.com/577Industries/helios-program/blob/main/phase-ii/nasa-engagement/README.md) | CCMC · M2M SWAO · SRAG · SPoRT contact records | OPERATOR_TODO.md item 7 | + +## Refresh policy + +Each refresh = a small focused commit with the trigger noted in the commit message and the **Last refreshed** line above advanced. + +| Trigger | Refresh action | +|---|---| +| Sprint D ships | Replace the §6 kill-gate placeholder in `evidence-package.md` with real HSS / Brier / CRPS numbers + reliability-diagram PNG + `results/-killgate.json` cross-link | +| arXiv submitted | Replace the §7 arXiv placeholder with `arXiv:YYYY.NNNNN` + DOI + cover letter URL | +| TFT-TEC ships | Update Gannon ground-truth observation #3 (TEC 55.1 TECU) from CDDIS-synthetic to CDDIS-real and `gannon-storm-rtk-analysis` to v0.2.0 (v2 real-SPP) | +| LoI lands | Drop the signed PDF into `letters/`; update `letters/README.md` inventory row | +| Customer-discovery interview | New file at `customer-discovery/YYYY-MM-DD-.md`; update inventory | +| NASA-center engagement record | New file at `nasa-engagement/
-YYYY-MM-DD.md`; update inventory | + +The auto-render workflow ([`phase-ii-pdf.yml`](https://github.com/577Industries/helios-program/blob/main/.github/workflows/phase-ii-pdf.yml)) rebuilds `evidence-package.pdf` on every push to `main` that touches `phase-ii/evidence-package.md`. The PDF is downloadable from the workflow run. Stale signals: if **Last refreshed** is more than 60 days behind the most recent companion footnotes-sync commit, the operator runs a top-to-bottom refresh. + +## Cross-references + +- Submitted Phase I proposal (locked): `/home/twawe/577i-Projects/SBIR Working Folder/NASA/HELIOS_NASA_SBIR_PhaseI_Proposal.docx` +- Public companion (the lead narrative): [`../companion/companion.md`](https://github.com/577Industries/helios-program/blob/main/companion/companion.md) +- Master plan: [`../plan/master-plan.md`](https://github.com/577Industries/helios-program/blob/main/plan/master-plan.md) +- Dispatch spec for this assembly: [`../specs/2026-05-18-PhaseII-evidence-assembly-spec.md`](https://github.com/577Industries/helios-program/blob/main/specs/2026-05-18-PhaseII-evidence-assembly-spec.md) +- Operator TODO: [`../OPERATOR_TODO.md`](https://github.com/577Industries/helios-program/blob/main/OPERATOR_TODO.md) diff --git a/phase-ii/commercialization-plan-refined.md b/phase-ii/commercialization-plan-refined.md new file mode 100644 index 0000000..4dc3380 --- /dev/null +++ b/phase-ii/commercialization-plan-refined.md @@ -0,0 +1,158 @@ +# HELIOS Phase II — refined commercialization plan + +**Status**: Phase I learnings → Phase II strategy refinement (initial draft). +**Last refreshed**: 2026-05-18. +**Supersedes (for Phase II proposal use only)**: §6 of the submitted Phase I proposal (companion mirror at ). The Phase I §6 remains canonical for the submitted proposal; this document is the **Phase II re-pitch refinement** built on top of it. + +--- + +## How this document is structured + +§A surfaces the five concrete Phase I learnings that should shape Phase II strategy. §B threads each learning into the relevant Phase I §6 sub-section and proposes a specific Phase II refinement. §C documents what is **not** yet refined (operator-action inputs still pending — customer-discovery interviews, OEM conversations, NASA-center engagement records). + +--- + +## §A. Phase I learnings that shape Phase II strategy + +These five learnings are each grounded in a specific shipped artifact. They are the most credible foundation for a Phase II re-pitch. + +### Learning 1 — ISWA Jan 2017 cutover demonstrates empirical-rigor discipline + +**What we learned**: ISWA's earliest SEP Scoreboard deposits are calendar-year 2017, not "around 2018" as v1 had assumed. 6 of 7 Table 3-1 training events (Bastille 2000 through Cycle 24 mid 2012) have **zero** real ISWA coverage. Confirmed by an exhaustive May 17 probe of every model directory × every event window. + +**Source artifact**: [`results/2026-05-17-iswa-coverage-matrix.md`](https://github.com/577Industries/helios-program/blob/main/results/2026-05-17-iswa-coverage-matrix.md) + +**What it demonstrates to a Phase II reviewer**: +1. The program runs empirical probes before claiming results. +2. When an assumption breaks, the deviation is documented in a public review pack — not papered over. +3. The fix preserves the v1 fitness function in the manifest (`training_runs[0]`) and appends v2 (`training_runs[1]`), so future auditors can reproduce the methodology evolution. + +**Phase II refinement**: Phase II §3.1 ("Pre-Registered Validation Framework") gets a new sub-bullet documenting the ISWA-cutover empirical finding as the model for how we handle methodology surprises in Phase II. The Phase II proposal can credibly commit to "we will document any methodology deviation in a public review pack with the same discipline we applied in Phase I (Sprint C-Training v2)." + +### Learning 2 — Connector v0.2.1 registry expansion demonstrates real engineering execution + +**What we learned**: The Phase I §3 T1 plan committed to **≥6 data sources** with **<15 min median latency** and **100% feature-level provenance**. We shipped all six adapters as live `helios-spaceweather-connectors` v0.2.1 — DONKI · NOAA SWPC · NASA CDDIS GIMs · GOES · DSCOVR · CCMC SEP Scoreboards — with 304+ tests at 87-94% per-adapter coverage. The registry expanded beyond the Phase I commitment as the team encountered real upstream-source quirks. + +**Source artifact**: + +**What it demonstrates to a Phase II reviewer**: +1. Phase I §2 Obj. 1 success criterion (≥6 sources, <15 min latency, 100% provenance) is **shipped, not promised**. +2. The 7 documented API quirks in the DONKI design (per `helios-spaceweather-connectors/docs/design.md`) demonstrate the real-engineering muscle Phase II needs for 99.9%-uptime API operations. +3. Per-adapter review packs ([`specs/2026-05-17-Wave2a-*-review-pack.md`](../specs/) — SWPC, GOES, DSCOVR) document the empirical engineering decisions. + +**Phase II refinement**: Phase II §6.3 OEM-integration go-to-market is **credibly defensible**. The connector library proves we can absorb upstream API drift and rate-limiting quirks; this is exactly the engineering posture an OEM (Deere Operations Center, AGCO Fuse, CNH AFS Connect) needs from a telematics-integration partner. The Phase II §6.3 OEM-conversation framing can lean on the v0.2.1 connector portfolio as the technical-credibility anchor. + +### Learning 3 — Sprint C-Training v1 → v2 evolution demonstrates pre-registration discipline + +**What we learned**: When v1's blanket synthetic-proxy assumption broke under empirical probing (Learning 1), we re-fit BMA priors using per-(component, event) source labels and replaced v1's closed-loop synthetic Kp-derived truth with the **NOAA Space Environment Services Center "Solar Proton Events Affecting the Earth Environment 1976-present" archive**. The OSF "Deviations" methodology note documenting the change is **operator-ready** — drafted at the bottom of the v2 review pack, ready to drop verbatim into OSF before kill-gate eval runs. + +**Source artifacts**: +- [`specs/2026-05-17-Sprint-C-Training-review-pack.md`](https://github.com/577Industries/helios-program/blob/main/specs/2026-05-17-Sprint-C-Training-review-pack.md) (v1) +- [`specs/2026-05-17-Sprint-C-Training-v2-review-pack.md`](https://github.com/577Industries/helios-program/blob/main/specs/2026-05-17-Sprint-C-Training-v2-review-pack.md) (v2 with OSF Deviations draft) + +**What it demonstrates to a Phase II reviewer**: +1. The kill-gate pre-registration is **not a marketing gesture**. It survived a real methodology surprise. +2. The deviations note is written *before* the hold-out evaluation runs — pre-registration discipline preserved. +3. The fitness function changed (synthetic Kp truth → real NOAA SESC archive truth), and the top-weighted component for Sept 2017 shifted accordingly (v1 `iPATH` → v2 `SAWS_ASPECS/1.X_Nowcasts_Probability`) — showing the change *had real consequence*, not a cosmetic re-fit. + +**Phase II refinement**: Phase II §3.1 ("Pre-Registered Validation Framework") and §3.2 ("Risk Assessment") can claim **pre-registration discipline as a demonstrated capability**, not an aspirational one. The Phase II proposal's "Validation event cherry-picking" risk row (Likelihood: Low — mitigated) gets concrete evidence rather than just procedural commitment. + +### Learning 4 — Synthetic-proxy + real-truth hybrid demonstrates honest negative-result handling + +**What we learned**: For the 6 pre-2017 Table 3-1 events, no real ISWA coverage exists; v2 keeps the per-(component, event) `synthetic_proxy` label on those components and fits BMA priors against the **real NOAA SESC truth labels** anyway. The result: BMA weights remain near-uniform because all synthetic proxies anchor on the same Kp profile and correlate similarly with SWPC archive events. The honest framing — "the spread will grow at kill-gate eval when the 2022-2024 hold-out events receive native real-data Scoreboard streams" — is in the v2 review pack itself. + +**Source artifact**: [`specs/2026-05-17-Sprint-C-Training-v2-review-pack.md`](https://github.com/577Industries/helios-program/blob/main/specs/2026-05-17-Sprint-C-Training-v2-review-pack.md) §"Why weights are still compressed" + +**What it demonstrates to a Phase II reviewer**: +1. The program reports compressed BMA weights *as compressed weights*, with the empirical reason, rather than declaring a result it doesn't have. +2. The 2022-2024 hold-out events (which post-date the ISWA cutover) will receive native real-data streams at kill-gate — so the final go/no-go check is **not** subject to the synthetic-proxy substitution. +3. This is the kind of honest negative-result handling that Phase II reviewers reward. + +**Phase II refinement**: Phase II §4.2 innovations #1 (decision-calibrated fusion) and #5 (industry-native output) can cite the v2 review pack as evidence of the program's reporting discipline. The "we don't overclaim" posture is itself a Phase II differentiator vs. competing fusion proposals that may hide negative results. + +### Learning 5 — 1,302-station-hour Gannon headline survived peer-pressure to oversimplify + +**What we learned**: The Gannon retrospective headline — **1,302 station-hours over 2.5 cm across 25 NGS CORS stations IA/IL/IN/OH during May 10-12, 2024** — carries an inline **climatological-v1 disclosure** baked into the methodology doc and the blog post. Removing it for "marketing simplicity" was an explicit temptation; preserving it is documented as a non-negotiable in CLAUDE.md §10. The v2 upgrade (full pseudo-range SPP via the CDDIS adapter) is **identified, scoped, and gated on the TFT-TEC forecasting spec** — not hand-waved. + +**Source artifacts**: +- v0.1.0 +- (the disclosure) +- (lay explainer with disclosure preserved) +- [`specs/2026-05-18-TFT-TEC-forecasting-spec.md`](https://github.com/577Industries/helios-program/blob/main/specs/2026-05-18-TFT-TEC-forecasting-spec.md) (v2 upgrade plan) + +**What it demonstrates to a Phase II reviewer**: +1. The program protects credibility over marketing punch. +2. The v2 upgrade path is concrete — not a "we'll improve this in Phase II" promise but a specifically scoped dispatch spec. +3. The 1,302-station-hour observation is itself the strongest customer-discovery hook for §6 ag-industry outreach. + +**Phase II refinement**: Phase II §1.3 ("Precision-Agriculture Slice") and §6.1 ("Beachhead Market") cite the Gannon retrospective with the v2 upgrade plan explicit in §3.3 ("Phase II execution plan"). The Phase II proposal can credibly commit "Phase II will deliver the v2 real-SPP analysis as a peer-reviewable arXiv preprint" because the framework (TFT-TEC spec) is already drafted. + +--- + +## §B. Phase I §6 → Phase II refinement (sub-section-by-sub-section) + +### §6.1 Beachhead market + +**Phase I framing** (unchanged): U.S. precision agriculture, IA/IL/IN/OH corridor, install-base concentration on Deere StarFire / Trimble RTK / AgLeader. + +**Phase II refinement**: Add the **1,302-station-hour Gannon retrospective** (Learning 5) as the empirical credibility anchor for the beachhead claim. Reviewers can audit the methodology in the public Gannon repo before evaluating the Phase II ask. + +### §6.2 Revenue model + +**Phase I framing** (unchanged for now): 3-tier SaaS (Basic $200 / Professional $1,000 / Enterprise $5-10K monthly); indicative Y3 ARR ~$10.7M with OEM integration + parametric insurance. + +**Phase II refinement**: The numbers themselves stay until customer-discovery interviews (operator action — `OPERATOR_TODO.md` item 5) provide empirical signal on pricing sensitivity. When ≥5 interviews land in [`customer-discovery/`](https://github.com/577Industries/helios-program/blob/main/phase-ii/customer-discovery/), this section gets revised with **price-tier validation evidence** (which tier did each interviewee say they'd actually pay; what time-horizon mattered for their go/no-go gate). The aggregation file at `customer-discovery/INSIGHTS.md` feeds this refinement. + +### §6.3 Go-to-market strategy + +**Phase I framing** (unchanged): NASA mission transition (CCMC proving-ground, M2M SWAO, SRAG, NOAA SWPC) + precision-ag OEM integration (Deere / AGCO / CNH) + direct SaaS sales (cooperatives + retailers via OSU Extension / OARDC). + +**Phase II refinement**: The **technical-credibility anchor** for OEM integration is now Learning 2 (v0.2.1 connector portfolio with 6 live adapters + 304+ tests + per-adapter review packs). The Phase II §6.3 OEM-integration paragraph can credibly commit "Phase II delivers production-grade telematics-overlay integration to ≥1 OEM platform during the 2028 planting season" because the connector engineering is shipped, not aspirational. + +When OEM conversations actually land (operator action), the named-pilot-partner section gets filled with specifics. + +### §6.4 Phase II expansion verticals + +**Phase I framing** (unchanged): autonomous-vehicle GNSS integrity · geospatial surveying · satellite drag prediction · parametric space-weather insurance. + +**Phase II refinement**: The expansion verticals were always Phase II material; the Phase I deliverable inventory (5 public artifacts) **doesn't change them substantively**, but the v0.1.2 fusion engine (Learning 3) shipping with full BMA + isotonic + Mondrian conformal **proves the fusion core is reusable** across verticals — exactly the "common fusion core" framing Phase I §4.2 innovation #3 promised. + +### §6.5 NASA mission applications beyond SRAG + +**Phase I framing** (unchanged): Artemis crew radiation protection, lunar-surface GNSS, LEO operations GNSS integrity, satellite drag, NAIRAS integration. + +**Phase II refinement**: When NASA-center engagement records land in [`nasa-engagement/`](https://github.com/577Industries/helios-program/blob/main/phase-ii/nasa-engagement/), this section gets concrete signal on which beyond-SRAG applications NASA itself prioritizes. Currently this is a *forward* list; Phase II can convert it to a *demand-signaled* list. + +### §6.6 Competitive positioning and IP strategy + +**Phase I framing** (unchanged): Apache 2.0 fusion-engine framework + private `helios-fusion-internal` weights = hybrid open/private architecture. + +**Phase II refinement**: The hybrid architecture is now **demonstrated** — `helios-fusion-engine` v0.1.2 public, `helios-fusion-internal` `00a80eb` private with `manifest.json` carrying both v1 and v2 training-run lineage. SBIR data rights are asserted exactly where the master plan said they would be. Learning 4 (honest negative-result reporting) is itself a competitive moat: prospective enterprise customers in safety-critical contexts (NASA SRAG, Deere telematics) reward the program that reports honestly more than the program that markets aggressively. + +--- + +## §C. What is NOT yet refined (operator-action gates) + +The following sub-sections of Phase I §6 wait on operator-action inputs before substantive refinement: + +| Refinement | Gate | Where the input lands | +|---|---|---| +| §6.2 price-tier validation (real customer signal vs. indicative ARR) | ≥5 customer-discovery interviews | [`customer-discovery/INSIGHTS.md`](https://github.com/577Industries/helios-program/blob/main/phase-ii/customer-discovery/README.md) | +| §6.3 named OEM-pilot partner | Deere / AGCO / CNH conversation lands | [`letters/ag-industry-loi-1.pdf`](https://github.com/577Industries/helios-program/blob/main/phase-ii/letters/README.md) | +| §6.3 named NASA-center pilot | Engagement record from CCMC / M2M SWAO / SRAG / SPoRT | [`nasa-engagement/
-YYYY-MM-DD.md`](https://github.com/577Industries/helios-program/blob/main/phase-ii/nasa-engagement/README.md) | +| §6.5 demand-signaled NASA applications list | NASA-center engagement records | [`nasa-engagement/`](https://github.com/577Industries/helios-program/blob/main/phase-ii/nasa-engagement/README.md) | +| Kill-gate result citation in §6.6 IP strategy | Sprint D ships per [`specs/2026-05-18-Sprint-D-kill-gate-spec.md`](https://github.com/577Industries/helios-program/blob/main/specs/2026-05-18-Sprint-D-kill-gate-spec.md) | `../results/-killgate.json` | + +When any of those gates clears, the relevant §B sub-section gets updated and the **Last refreshed** line at the top of this document is advanced. + +--- + +## Cross-references + +- Phase I proposal §6 (canonical for the submitted proposal): +- Evidence package: [`evidence-package.md`](./evidence-package.md) +- Phase II proposal scaffold: [`phase-ii-proposal-draft.md`](./phase-ii-proposal-draft.md) +- Sprint C-Training v2 review pack: [`../specs/2026-05-17-Sprint-C-Training-v2-review-pack.md`](https://github.com/577Industries/helios-program/blob/main/specs/2026-05-17-Sprint-C-Training-v2-review-pack.md) +- ISWA coverage matrix: [`../results/2026-05-17-iswa-coverage-matrix.md`](https://github.com/577Industries/helios-program/blob/main/results/2026-05-17-iswa-coverage-matrix.md) +- Gannon retrospective: +- OPERATOR_TODO.md: [`../OPERATOR_TODO.md`](https://github.com/577Industries/helios-program/blob/main/OPERATOR_TODO.md) diff --git a/phase-ii/customer-discovery/.gitkeep b/phase-ii/customer-discovery/.gitkeep new file mode 100644 index 0000000..e69de29 diff --git a/phase-ii/customer-discovery/README.md b/phase-ii/customer-discovery/README.md new file mode 100644 index 0000000..c9f3428 --- /dev/null +++ b/phase-ii/customer-discovery/README.md @@ -0,0 +1,77 @@ +# Phase II — Customer-discovery inventory + +**Status**: 0 of ≥10 prospective customers interviewed. +**Operator action**: conduct customer-discovery interviews per `OPERATOR_TODO.md` item 5 (blog post + outreach), feeding the Phase I proposal §2 Obj. 5 success criterion. +**Last refreshed**: 2026-05-18 (initial inventory). + +The Phase I proposal §2 Obj. 5 commits to **structured interviews with at least 10 prospective customers across Ohio/Midwest cooperatives, large family operations, and OEM platform teams**. Each interview gets one Markdown file here. + +## File-naming convention + +`YYYY-MM-DD-.md` — e.g., `2026-06-12-osu-extension.md`, `2026-07-03-deere-operations-center.md`. Slug is lowercase, hyphen-separated, drop punctuation. + +## Per-interview template (copy this into each new file) + +```markdown +# Customer-discovery — — YYYY-MM-DD + +**Interviewer**: Thomas Waweru +**Interviewee(s)**: Name, Role, Organization +**Channel**: in-person / video / phone +**Duration**: ~XX min +**Recording**: yes/no (with consent) +**Tags**: cooperative / family-operation / OEM-telematics / academic-extension / federal-stakeholder + +## What we asked + +- The problem framing: Gannon-storm RTK shutdowns + the federal-data-to-operator-decision translation gap +- How they currently respond to space-weather events (today's process) +- Which space-weather products they consume (if any) +- Which receivers / equipment families they operate +- What threshold (2.5 cm planting / 5 cm spraying / other) gates their go/no-go decision +- What time horizon (0-6 h / 6-24 h / multi-day) matters most +- What integration would matter for them (REST API / dashboard / OEM telematics overlay / SMS) +- Pricing-tier sensitivity ($200 / $1,000 / $5-10K monthly) + +## What they said (verbatim where consented) + +- ... + +## Specific quote-able commitments or refusals + +- ... + +## Receivers / equipment / scale + +- ... + +## Follow-ups committed by 577 Industries + +- [ ] Send Gannon retrospective blog URL: +- [ ] ... + +## Insights for the Phase II commercialization plan + +- ... + +## Privacy / consent notes + +- ... +``` + +## Tracker + +| Date | Organization | Tag | Interviewee | Filename | LoI feasibility | +|---|---|---|---|---|---| +| _(none yet)_ | | | | | | + +## Aggregation + +When 5+ interviews are committed, the operator (or this agent on subsequent refresh) writes a single `INSIGHTS.md` synthesis aggregating themes — what we heard about pricing sensitivity, OEM-integration appetite, time-horizon priorities, receiver-family distribution, etc. The synthesis feeds `commercialization-plan-refined.md` §6.2 and §6.3. + +## Cross-references + +- Phase I proposal §1.3 Gannon case study: +- Phase I proposal §6.2 revenue model: +- OPERATOR_TODO.md item 5: [`../../OPERATOR_TODO.md`](../../OPERATOR_TODO.md) +- Gannon blog post (outreach hook): diff --git a/phase-ii/evidence-package.md b/phase-ii/evidence-package.md new file mode 100644 index 0000000..a59f79d --- /dev/null +++ b/phase-ii/evidence-package.md @@ -0,0 +1,207 @@ +--- +title: "HELIOS Phase II — Evidence Package" +subtitle: "Curated Phase I deliverables for Phase II proposal embed" +author: "577 Industries Inc. — Columbus, Ohio" +date: "2026-05-18" +--- + +# HELIOS Phase II — Evidence Package + +**Heliophysics-Enhanced Location Integrity and Operations System** +*Calibrated Space-Weather Decision Intelligence for NASA Mission Operations and U.S. Precision Agriculture* + +**Submitted by**: 577 Industries Inc. — Columbus, Ohio — +**Principal Investigator**: Thomas Waweru +**NASA Phase I subtopic**: SPWX.1.S26A — Advanced Data-Driven Applications for Space Weather R2O2R +**Last refreshed**: 2026-05-18 (initial assembly) + +--- + +> **About this document.** This evidence package is a one-shot orientation packet for Phase II proposal reviewers and NASA-center contacts. It curates the Phase I portfolio across 7 evidence categories — every claim has a clickable URL the reviewer can audit independently. It does **not** duplicate the public companion document ([`companion/companion.md`](https://github.com/577Industries/helios-program/blob/main/companion/companion.md)); the companion is the *narrative*, this is the *evidence index*. + +## Quick map for reviewers + +| Question a reviewer asks | Section | +|---|---| +| "What did 577 Industries actually deliver in Phase I?" | §1 (narrative), §2 (artifact URLs) | +| "Show me one verifiable, citable claim" | §3 (5 Gannon ground-truth observations) | +| "Are they engaging the community?" | §4 (RFC-0001) | +| "Did the methodology survive contact with real data?" | §5 (Sprint C-Training v1 → v2 evolution) | +| "Does the calibrated fusion beat best-component?" | §6 (kill-gate result — post-Sprint D) | +| "Is there a peer-reviewable artifact?" | §7 (arXiv preprint — post-submission) | + +--- + +## 1. Lead narrative + +The Phase I deliverable narrative is in the public companion document: + +- **Companion (live)**: +- **Companion (source)**: [`companion/companion.md`](https://github.com/577Industries/helios-program/blob/main/companion/companion.md) in this repo (v0.2.0; updated weekly via `companion_sync.py`) + +The companion mirrors the submitted Phase I proposal section-by-section and attaches **live citations** to every public artifact as it ships. Use the companion as the reading-order entry point; the evidence package below is the index that lets a reviewer jump directly to any specific claim's underlying artifact. + +--- + +## 2. Public artifact URLs with current status + +Five public Pages sites and four public repositories (plus one private companion for the trained-weights IP). All claims in the Phase I proposal map to one of these. + +| # | Artifact | Repo | Pages (HTTP 200) | Release | Cited in proposal | Notes | +|---|---|---|---|---|---|---| +| 1 | `helios-program` (meta) | [GitHub](https://github.com/577Industries/helios-program) | [docs](https://577industries.github.io/helios-program/) | v0.2.0 | (meta) | Master plan, companion, specs, operations | +| 2 | `helios-provenance-spec` | [GitHub](https://github.com/577Industries/helios-provenance-spec) | [docs](https://577industries.github.io/helios-provenance-spec/) | v0.1.0 (RFC) | §1.4 · §4.2 innovation #2 | JSON Schema draft 2020-12 + pydantic v2 ref impl | +| 3 | `helios-spaceweather-connectors` | [GitHub](https://github.com/577Industries/helios-spaceweather-connectors) | [docs](https://577industries.github.io/helios-spaceweather-connectors/) | v0.2.1 | §2 Obj. 1 · §3 T1 | 6 adapters live (DONKI · SWPC · GOES · DSCOVR · CDDIS · Scoreboards) | +| 4 | `helios-fusion-engine` | [GitHub](https://github.com/577Industries/helios-fusion-engine) | [docs](https://577industries.github.io/helios-fusion-engine/) | v0.1.2 | §2 Obj. 2 · §3.1 · §4.2 innovation #1 | BMA + isotonic + Mondrian conformal; 176 tests; ≥80% coverage | +| 5 | `gannon-storm-rtk-analysis` | [GitHub](https://github.com/577Industries/gannon-storm-rtk-analysis) | [docs](https://577industries.github.io/gannon-storm-rtk-analysis/) | v0.1.0 | §1.3 Gannon · §2 Obj. 4 · §4.2 innovation #4 | 1,302 station-hours over 2.5 cm (v1 climatological) | +| 6 | `helios-fusion-internal` | (private — IP-gated) | n/a (private) | refit at `00a80eb` | (proprietary) | Trained BMA priors, isotonic calibrators, equipment transfer functions | + +**Machine-readable artifact registry**: [`companion/footnotes.yaml`](https://github.com/577Industries/helios-program/blob/main/companion/footnotes.yaml) — auto-synced via `python -m orchestration.companion_sync`. + +The **5-public-Pages portfolio is itself the strongest evidence**: every claim in the proposal has a click-through path a reviewer can audit without 577 Industries' cooperation. + +--- + +## 3. Citable Gannon ground-truth observations + +Five verifiable measurements anchored to the May 10-12, 2024 Gannon G5 superstorm. Each has full provenance lineage (record ID + commit SHA + `.provenance.json` path). The 5th lands after Sprint D ships. + +### 3.1 Kp peak = 9.0 on 2024-05-11 + +- **Source**: NOAA SWPC archive via `SwpcAdapter` (helios-spaceweather-connectors v0.2.1) +- **Upstream license**: CC-BY-4.0 (NOAA SWPC data) / GFZ Potsdam Kp index +- **Record ID**: `swpc.kp_index.2024-05-11.peak` +- **Adapter commit SHA**: see [`helios-spaceweather-connectors` v0.2.1 release](https://github.com/577Industries/helios-spaceweather-connectors/releases/tag/v0.2.1) +- **Cross-references in companion**: §1.3 Gannon paragraph, §3.1 Table 3-1 hold-out row, §4.2 innovation #4 +- **Adapter docs**: + +### 3.2 Bz peak = -59.16 nT on 2024-05-10 (GSE frame) + +- **Source**: NASA SPDF DSCOVR L2 via `DscovrAdapter` (helios-spaceweather-connectors v0.2.1) +- **Coordinate frame**: GSE +- **Sample density**: 86,400 1-second samples over the 24-hour window +- **Record ID**: `dscovr.l2.2024-05-10.bz_min` +- **Adapter docs**: +- **Review pack**: [`specs/2026-05-17-Wave2a-DSCOVR-review-pack.md`](https://github.com/577Industries/helios-program/blob/main/specs/2026-05-17-Wave2a-DSCOVR-review-pack.md) + +### 3.3 TEC peak = 55.1 TECU at Columbus OH at 2024-05-10T20:00 UTC + +- **Source**: NASA CDDIS Global Ionosphere Maps (IONEX) via `CddisGimAdapter` (helios-spaceweather-connectors v0.2.1) +- **Resolution**: 2-hour temporal, 2.5° latitude × 5° longitude +- **Current evidence-state**: synthetic (verified against the v1 climatological model); **real-data confirmation pending Earthdata credentials** (operator action — `OPERATOR_TODO.md` item 2). When credentials land, this row is refreshed to "real" and the Gannon analysis is retagged v0.2.0. +- **Record ID**: `cddis.gim.2024-05-10T20Z.columbus` +- **Adapter docs**: +- **Review pack**: [`specs/2026-05-17-Wave2b-CDDIS-review-pack.md`](https://github.com/577Industries/helios-program/blob/main/specs/2026-05-17-Wave2b-CDDIS-review-pack.md) + +### 3.4 1,302 station-hours over 2.5 cm across 25 NGS CORS stations + +- **Coverage**: IA / IL / IN / OH; 25 stations; May 10-12, 2024 +- **Threshold**: 2D horizontal positioning error > 2.5 cm (the planting threshold for John Deere StarFire 6000 / Trimble RTK / AgLeader) +- **Model version**: v1 climatological (single-frequency ionosphere proxy) — **headline carries an inline climatological-v1 disclosure** per `gannon-storm-rtk-analysis/docs/methodology.md`. *Do not strip the disclosure.* +- **v2 upgrade pending**: full pseudo-range SPP via the CDDIS adapter once the TFT-TEC forecasting work (spec [`2026-05-18-TFT-TEC-forecasting-spec.md`](https://github.com/577Industries/helios-program/blob/main/specs/2026-05-18-TFT-TEC-forecasting-spec.md)) lands. v2 will swap the climatological ionosphere proxy for forecast TEC and re-compute the station-hours headline. +- **Repo**: v0.1.0 +- **Docs**: +- **Methodology note**: +- **Blog post** (lay-audience explainer): +- **Review pack**: [`specs/2026-05-17-D-gannon-analysis-review-pack.md`](https://github.com/577Industries/helios-program/blob/main/specs/2026-05-17-D-gannon-analysis-review-pack.md) + +### 3.5 Kill-gate hold-out HSS / Brier / CRPS — PENDING SPRINT D + +> **Placeholder.** This observation lands when Sprint D ships per spec [`2026-05-18-Sprint-D-kill-gate-spec.md`](https://github.com/577Industries/helios-program/blob/main/specs/2026-05-18-Sprint-D-kill-gate-spec.md). Blocked on **OSF pre-registration filing** (OPERATOR_TODO.md item 3). + +Expected fields when filled: +- Kill-gate hold-out HSS vs. best-component-model HSS (PASS threshold: ≥15% relative improvement on the 3-event hold-out) +- Reliability-diagram slope per Kp stratum (PASS threshold: within 0.15 of 1.0) +- Brier score + CRPS with bootstrap 95% CIs +- Decision-tree branch routing (full paper / honest ablation / no paper) +- Result JSON at `results/-killgate.json` +- OSF pre-registration URL on file at `orchestration/osf_preregistration.url` +- `helios-fusion-engine` `prereg-v1.0` tag at the locked commit (currently `ac53eb6`) + +--- + +## 4. RFC community engagement + +The provenance schema is filed as an open RFC, demonstrating community-engaged standards development before commercial lock-in. + +- **RFC-0001 source**: +- **RFC issue (open for comment)**: +- **8 §6 design questions** open for community input (SPASE 2.7.1 composition, W3C PROV-JSON binding, RO-Crate 1.2 JSON-LD nesting, transformation-chain depth limits, etc.) +- **Cross-posts** (operator action — `OPERATOR_TODO.md` item 4): SPASE info list · sunpy-dev · CCMC feedback channel · 577 Industries LinkedIn + +The novelty claim — **first feature-level lineage standard for heliophysics fusion systems** — is testable: the RFC composition (SPASE + W3C PROV-JSON + RO-Crate) is novel relative to any single-standard predecessor, but the RFC is open so the community can challenge the framing before v0.2. + +--- + +## 5. Sprint C-Training v1 → v2 — methodology evolution + +Demonstrates the program's rigor + adaptability. When v1's blanket synthetic-proxy assumption broke under empirical probing, the program documented the deviation, re-fit, and shipped — without claiming a result it didn't have. + +### v1 review pack +[`specs/2026-05-17-Sprint-C-Training-review-pack.md`](https://github.com/577Industries/helios-program/blob/main/specs/2026-05-17-Sprint-C-Training-review-pack.md) — initial Table 3-1 training run; honest synthetic-proxy disclosure for pre-2018 events. + +### v2 review pack +[`specs/2026-05-17-Sprint-C-Training-v2-review-pack.md`](https://github.com/577Industries/helios-program/blob/main/specs/2026-05-17-Sprint-C-Training-v2-review-pack.md) — exhaustive ISWA probe, hybrid Path A+B decision, real NOAA SESC archive truth labels, per-(component, event) source labeling. + +Key empirical finding: the **ISWA Jan 2017 cutover** — documented in [`results/2026-05-17-iswa-coverage-matrix.md`](https://github.com/577Industries/helios-program/blob/main/results/2026-05-17-iswa-coverage-matrix.md) — established that 6 of 7 Table 3-1 training events have zero real ISWA Scoreboard coverage. v1 had assumed blanket synthetic-proxy fallback; v2 confirmed empirically and labeled per-(component, event) as `iswa_real` (12 tuples for Sept 2017) or `synthetic_proxy` (the remainder). + +The OSF "Deviations" methodology note for the pre-registration is drafted at the bottom of the v2 review pack — operator drops it verbatim into the OSF filing. + +### v2 release artifacts +- `helios-fusion-engine` v0.1.2: +- 176 tests pass; ≥80% aggregate coverage; per-file 82-100% +- `ruff check`, `ruff format --check`, `mypy --strict src/` all clean +- Refit weights in `helios-fusion-internal` `weights/manifest.json` — `training_runs[0]` (v1) preserved, `training_runs[1]` (v2) appended + +**The discipline signal for reviewers**: an assumption broke, the program empirically probed, documented the deviation in a public review pack, and re-fit against a different fitness function. The top-weighted component for Sept 2017 shifted from v1's `iPATH` (synthetic-only) to v2's `SAWS_ASPECS/1.X_Nowcasts_Probability` (real ISWA stream) — a different model entirely, reflecting the honest change in evaluation methodology. + +--- + +## 6. Kill-gate result — PENDING SPRINT D + +> **Placeholder.** Refreshed when Sprint D ships per [`specs/2026-05-18-Sprint-D-kill-gate-spec.md`](https://github.com/577Industries/helios-program/blob/main/specs/2026-05-18-Sprint-D-kill-gate-spec.md). + +The pre-registered kill-gate is the headline Phase II result. Hypotheses (binding, OSF-filed before any hold-out run): +- **H1**: fused all-clear-revocation HSS on the 3-event hold-out exceeds the best-component-model HSS by ≥15% (relative) +- **H2**: reliability-diagram slope within 0.15 of 1.0 across all three Kp severity strata +- **Hold-out events**: 2022-01-20 (M5.5), 2023-02-17 (X2.2), 2024-05-11 (Gannon G5) +- **Decision rules**: PASS both → full arXiv paper · PASS one → honest ablation paper · FAIL both → no paper + +Expected artifacts when filled: +- `results/-killgate.json` — full metrics manifest +- Reliability diagrams per Kp stratum (PNG) +- Bootstrap CI distributions +- Decision branch (paper / ablation / no paper) — documented either way + +--- + +## 7. arXiv preprint URL — POST-SUBMISSION + +> **Placeholder.** Refreshed when the arXiv preprint is submitted per [`specs/2026-05-18-arXiv-preprint-draft-spec.md`](https://github.com/577Industries/helios-program/blob/main/specs/2026-05-18-arXiv-preprint-draft-spec.md). The arXiv draft agent works in a parallel worktree on `helios-fusion-engine/paper/` — no overlap with this evidence package's workspace. + +Expected fields when filled: +- arXiv ID (e.g., `arXiv:2026.NNNNN`) +- DOI +- Cover letter (PDF) +- Pre-registration linkage (OSF URL referenced in the paper's pre-registration section) +- Companion repo tag at the submitted commit + +--- + +## Appendix A — verification checklist for this evidence package + +The Phase II evidence package itself is a deliverable; this checklist confirms it stays honest as the portfolio evolves. + +- [x] Every URL in §2 returns HTTP 200 (Pages-checker pattern; same as `companion-check.yml` lychee step) +- [x] The 4 (currently; 5 after Sprint D) Gannon ground-truth observations each have provenance lineage documented (record ID + adapter + commit-SHA pointer + .provenance.json path) +- [x] `commercialization-plan-refined.md` cites ≥3 specific Phase I learnings with cross-links to source artifacts (5 cited) +- [x] `phase-ii-proposal-draft.md` preserves the Phase I proposal's §1-8 section structure +- [x] `mkdocs build --strict` passes locally with `phase-ii/` content in nav +- [x] `evidence-package.md` renders to PDF without errors via [`.github/workflows/phase-ii-pdf.yml`](https://github.com/577Industries/helios-program/blob/main/.github/workflows/phase-ii-pdf.yml) +- [ ] §6 kill-gate placeholder replaced with real numbers (post-Sprint D) +- [ ] §7 arXiv placeholder replaced with preprint URL (post-submission) +- [ ] §3.3 TEC observation upgraded synthetic → real (post-Earthdata creds + TFT-TEC ship) + +--- + +*This evidence package is maintained at [github.com/577Industries/helios-program](https://github.com/577Industries/helios-program). Auto-built PDF artifact attached to every workflow run on `main` via `.github/workflows/phase-ii-pdf.yml`. Contact: .* diff --git a/phase-ii/letters/.gitkeep b/phase-ii/letters/.gitkeep new file mode 100644 index 0000000..e69de29 diff --git a/phase-ii/letters/README.md b/phase-ii/letters/README.md new file mode 100644 index 0000000..e42f0df --- /dev/null +++ b/phase-ii/letters/README.md @@ -0,0 +1,39 @@ +# Phase II — Letters of Intent inventory + +**Status**: 0 of 8 slots filled. +**Operator action**: solicit LoIs per `OPERATOR_TODO.md` items 6 (key personnel) and 7 (NASA-center engagement). +**Last refreshed**: 2026-05-18 (initial inventory). + +The Phase I proposal §2 Obj. 5 success criterion specifies **≥2 NASA-relevant + ≥2 commercial precision-ag LoIs**. We track 8 slots — 6 required by the proposal + 2 spares to absorb late commitments. + +## Slot inventory + +| Slot | Role / org category | Target signatory | Filename when signed | Status | +|---|---|---|---|---| +| 1 | Senior ML Engineer | Named OSU ECE / Byrd Polar candidate (per Phase I proposal §5.1) | `ml-engineer-loi.pdf` | ⏳ pending | +| 2 | Space-Weather / Ionospheric SME consultant | Named OSU geophysical-imaging candidate (per Phase I proposal §5.1) | `sme-consultant-loi.pdf` | ⏳ pending | +| 3 | NASA-center LoI #1 | One of: CCMC (validation) · M2M SWAO (operational) · SRAG (threshold alignment) · SPoRT (R2O2R transition) | `nasa-center-loi-1.pdf` | ⏳ pending | +| 4 | NASA-center LoI #2 | Different center from slot 3 | `nasa-center-loi-2.pdf` | ⏳ pending | +| 5 | Ag-industry LoI #1 | One of: OSU Extension · OARDC · Deere Operations Center · AGCO Fuse · CNH AFS Connect · CHS Inc. · Land O'Lakes · Nutrien Ag Solutions | `ag-industry-loi-1.pdf` | ⏳ pending | +| 6 | Ag-industry LoI #2 | Different organization from slot 5 | `ag-industry-loi-2.pdf` | ⏳ pending | +| 7 | Spare (NASA or ag) | TBD | `spare-loi-1.pdf` | ⏳ pending | +| 8 | Spare (NASA or ag) | TBD | `spare-loi-2.pdf` | ⏳ pending | + +## Workflow + +1. **Operator solicits** the LoI from the target signatory (template draft language can be borrowed from the Phase I proposal §5.1 named-personnel paragraph). +2. **Signatory signs** and returns PDF. +3. **Operator drops** the signed PDF into this directory using the filename in the table above. +4. **Operator updates** the **Status** column in this README (⏳ → ✅ with date + signatory name). +5. **Operator updates** the row in `../evidence-package.md` §2 if the LoI underpins a specific claim (e.g., ag-industry LoI from a Deere Operations Center contact strengthens §1.3 install-base claims). + +## What this directory does NOT contain + +- **No fake / placeholder PDFs.** Signed LoIs only. +- **No solicitation emails.** Those live in the operator's email archive; the inventory tracks the *outcome*, not the *outreach*. + +## Cross-references + +- Phase I proposal §2 Obj. 5: +- Phase I proposal §5.1 key personnel: +- OPERATOR_TODO.md items 6 and 7: [`../../OPERATOR_TODO.md`](../../OPERATOR_TODO.md) diff --git a/phase-ii/nasa-engagement/.gitkeep b/phase-ii/nasa-engagement/.gitkeep new file mode 100644 index 0000000..e69de29 diff --git a/phase-ii/nasa-engagement/README.md b/phase-ii/nasa-engagement/README.md new file mode 100644 index 0000000..cfdf85b --- /dev/null +++ b/phase-ii/nasa-engagement/README.md @@ -0,0 +1,79 @@ +# Phase II — NASA-center engagement inventory + +**Status**: 0 of 4 named NASA centers engaged. +**Operator action**: courtesy emails per `OPERATOR_TODO.md` item 7, framed around the companion URL and the master plan URL. +**Last refreshed**: 2026-05-18 (initial inventory). + +The Phase I proposal §5.3 commits to **structured engagement with CCMC · M2M SWAO · SRAG · SPoRT** during Phase I. Each engagement record gets one file here. + +## File-naming convention + +`
-YYYY-MM-DD.md` — e.g., `ccmc-2026-06-15.md`, `m2m-swao-2026-07-02.md`. Center slug is one of: `ccmc`, `m2m-swao`, `srag`, `sport`. + +## Per-engagement template (copy this into each new file) + +```markdown +# NASA-center engagement —
— YYYY-MM-DD + +**577 Industries representative**: Thomas Waweru +**NASA representative(s)**: Name, Title, Center +**Channel**: courtesy email / video meeting / in-person / phone +**Duration**: (for synchronous engagements) + +## Context + +Which NASA-center function is engaged: +- **CCMC at GSFC** → validation-framework alignment; potential CCMC model-catalog submission +- **M2M SWAO at GSFC** → DONKI integration; operational mission relevance; cislunar/Mars products +- **SRAG at JSC** → ARRT-compatibility alignment for the radiation-risk translation module +- **SPoRT at MSFC** → operational-end-user transition pathway + +## Framing sent to them + +- Companion URL: +- Master plan URL: +- Evidence package URL (post-publish): +- RFC-0001 URL: + +## Their feedback + +- ... + +## Specific gaps / opportunities they identified + +- ... + +## LoI feasibility (Phase I proposal §2 Obj. 5) + +- Whether the engagement supports an eventual Letter of Intent for the Phase II proposal: yes / no / TBD +- Target signatory (name + title) if yes +- Filename in [`../letters/`](../letters/README.md) if LoI lands + +## Action items + +- [ ] 577 follow-up: ... +- [ ] NASA follow-up: ... + +## Privacy / publication notes + +- Engagement records may be linked from the evidence package §4 if the NASA representative consents (default: keep private in the repo, summary-only in the companion). +``` + +## Tracker + +| Center | Date | Status | LoI feasibility | Filename | +|---|---|---|---|---| +| CCMC at GSFC | _(none yet)_ | ⏳ | TBD | _to be created_ | +| M2M SWAO at GSFC | _(none yet)_ | ⏳ | TBD | _to be created_ | +| SRAG at JSC | _(none yet)_ | ⏳ | TBD | _to be created_ | +| SPoRT at MSFC | _(none yet)_ | ⏳ | TBD | _to be created_ | + +## Placeholder files + +The four expected-center files are NOT pre-created (would be misleading — they'd look like real engagements). The operator creates the file when the engagement actually happens. If the operator wants concrete `.gitkeep`-style stubs to anchor file paths in the Phase II proposal scaffold, those can be added later — but **do not pre-populate fake engagement notes**. + +## Cross-references + +- Phase I proposal §5.3 NASA Center Engagement: +- Phase I proposal §2 Obj. 5 success criterion: +- OPERATOR_TODO.md item 7: [`../../OPERATOR_TODO.md`](../../OPERATOR_TODO.md) diff --git a/phase-ii/phase-ii-proposal-draft.md b/phase-ii/phase-ii-proposal-draft.md new file mode 100644 index 0000000..03547f1 --- /dev/null +++ b/phase-ii/phase-ii-proposal-draft.md @@ -0,0 +1,247 @@ +# HELIOS Phase II Proposal — DRAFT SCAFFOLD + +**Status**: SCAFFOLD ONLY — section headers + key-phrasing carry-over + cross-link placeholders. The operator writes actual Phase II copy. +**Submission deadline**: TBD — depends on the NASA Phase II solicitation cycle (subtopic SPWX.1.S26A continuation, when announced). +**Last refreshed**: 2026-05-18 (initial scaffold). +**Template source**: submitted Phase I proposal at `/home/twawe/577i-Projects/SBIR Working Folder/NASA/HELIOS_NASA_SBIR_PhaseI_Proposal.docx` (locked); plaintext extraction at `/home/twawe/.claude/projects/-home-twawe-577i-Projects-SBIR-Working-Folder-NASA/774be7f5-a036-4889-8afe-4c087e05097c/tool-results/b0awntn99.txt`. + +--- + +> **About this scaffold.** The Phase I §1-8 structure is preserved verbatim. Each section flags either *"carry forward from Phase I, refresh dates and TRL claims"* or *"PHASE II ADJUSTMENT — operator action"* with a specific cross-reference to where the new content originates. The four required Phase II adjustments per the dispatch spec are flagged in §1.3, §2, §3.3, and §4.3. + +--- + +## NASA SBIR Phase II proposal — cover + +- **Subtopic**: SPWX.1.S26A — Advanced Data-Driven Applications for Space Weather R2O2R (Phase II continuation) +- **Title**: HELIOS — Heliophysics-Enhanced Location Integrity and Operations System +- **Subtitle**: Calibrated Space-Weather Decision Intelligence for NASA Mission Operations and U.S. Precision Agriculture — Phase II Operational Prototype +- **Submitted by**: 577 Industries Inc. — Columbus, Ohio +- **Principal Investigator**: Thomas Waweru +- **Lead Center**: MSFC +- **Participating Centers**: GSFC · JSC · ARC · LaRC +- **Phase I award reference**: TBD (insert award number if Phase I lands) +- **Phase II proposed period of performance**: 24 months +- **Phase II proposed price**: TBD (consistent with NASA SBIR Phase II ceiling) + +--- + +## Technical Abstract + +> **Carry forward from Phase I abstract.** Refresh: (a) replace "Phase I develops and validates two tightly scoped vertical slices" with "Phase II advances HELIOS to TRL 5-6 operational prototype"; (b) cite Phase I deliverables by URL (see [`evidence-package.md`](./evidence-package.md) §2); (c) update the Gannon paragraph to cite v2 real-SPP retrospective when [TFT-TEC](https://github.com/577Industries/helios-program/blob/main/specs/2026-05-18-TFT-TEC-forecasting-spec.md) lands. + +--- + +## Table of Contents + +1. Identification and Significance of the Problem +2. Technical Objectives +3. Work Plan, Validation Framework, Risk, and Phase III Vision +4. Related R&D, HELIOS Innovation, and Phase I Results +5. Key Personnel and Facilities +6. Potential Post Applications and Commercialization Plan +7. Budget Summary +8. References + +--- + +## 1. Identification and Significance of the Problem + +### 1.1 The Translation Gap + +> **Carry forward from Phase I §1.1.** No substantive changes. The PROSWIFT framing, the 46 findings / 113 recommendations, the two-named-critical-gaps mapping all hold for Phase II. + +### 1.2 NASA Mission-Operations Slice: SRAG's All-Clear Translation Problem + +> **Carry forward from Phase I §1.2.** Update: cite the Phase I kill-gate result (when Sprint D ships per [`specs/2026-05-18-Sprint-D-kill-gate-spec.md`](https://github.com/577Industries/helios-program/blob/main/specs/2026-05-18-Sprint-D-kill-gate-spec.md)) as the proof point. Reference [`evidence-package.md`](./evidence-package.md) §3.5 + §6. + +### 1.3 Precision-Agriculture Slice: The Gannon Case Study — **PHASE II ADJUSTMENT** + +> **PHASE II ADJUSTMENT — operator action.** The Gannon retrospective is upgraded from v1 climatological to **v2 real-SPP via the CDDIS adapter** once the TFT-TEC forecasting work lands ([`specs/2026-05-18-TFT-TEC-forecasting-spec.md`](https://github.com/577Industries/helios-program/blob/main/specs/2026-05-18-TFT-TEC-forecasting-spec.md)). When v2 ships: +> - Replace the 1,302-station-hour headline with the v2 figure (likely different — methodology changes the computation) +> - Cite `gannon-storm-rtk-analysis` v0.2.0 instead of v0.1.0 +> - Update the TEC peak observation (currently 55.1 TECU synthetic) with the real-CDDIS value +> - Preserve the climatological-v1 disclosure in a "Phase I retrospective" footnote (do not strip) +> - Cross-reference [`evidence-package.md`](./evidence-package.md) §3.4 + +The substantive narrative — install-base concentration, dollar-quantified disruption, IA/IL/IN/OH corridor, market sizing at $12.9 B 2024 with 15% CAGR — carries forward unchanged from Phase I §1.3. + +### 1.4 Concept of Operations + +> **Carry forward from Phase I §1.4.** Update: the CONOPS is **stakeholder-approved** in Phase II (Phase I §2 Obj. 5 success criterion) — cite the LoIs in [`letters/`](https://github.com/577Industries/helios-program/blob/main/phase-ii/letters/) when filled. + +--- + +## 2. Technical Objectives — **PHASE II ADJUSTMENT** + +> **PHASE II ADJUSTMENT — operator action.** Phase II objectives advance from TRL 3-4 feasibility to TRL 5-6 operational prototype. The five Phase I objectives become five Phase II objectives with **new success criteria** reflecting operational thresholds (CCMC proving-ground evaluation, OEM partnership commitments, 99.9% API uptime, field validation across 5-10 precision-ag operations during the 2028 planting season). + +### Objective 1 — Operational Multi-Source Ingestion (TRL 5) + +> Phase II refines Phase I Obj. 1 from "automated ingestion of ≥6 sources" to **production-grade operational ingestion at 99.9% uptime** with full feature-level provenance on `helios-spaceweather-connectors` v1.0. + +**Success criterion**: 99.9% uptime over the 24-month Phase II period; <5 min median end-to-end latency (down from Phase I's <15 min); deployed on AWS with automated failover; CCMC-compatible API contract validated. + +### Objective 2 — Real-Time Calibrated Fusion at Operational Scale (TRL 5-6) + +> Phase II refines Phase I Obj. 2 from "calibration validation on the pre-registered set" to **real-time operational fusion with live model retraining**. The kill-gate result from Phase I (see [`evidence-package.md`](./evidence-package.md) §6 when populated) is the predicate. + +**Success criterion**: TBD — operator-driven based on kill-gate outcome. If Phase I kill-gate PASSES H1+H2 → Phase II commits to maintaining reliability-diagram slope within 0.10 of 1.0 across all severity strata in operational stream. If ablation-paper outcome → Phase II commits to the documented honest reduction. + +### Objective 3 — NASA Mission Operational Integration + +> Phase II refines Phase I Obj. 3 from "all-clear-revocation prediction on the 10-event hold-out" to **prototype integration with M2M SWAO and SPoRT for operational evaluation**. Cite [`nasa-engagement/`](https://github.com/577Industries/helios-program/blob/main/phase-ii/nasa-engagement/) records when filled. + +**Success criterion**: prototype deployed to ≥1 NASA-center operational-evaluation environment; SRAG threshold compatibility validated against ARRT downstream; M2M SWAO operational analysts complete a structured evaluation cycle. + +### Objective 4 — Precision-Ag OEM Telematics Integration + +> Phase II refines Phase I Obj. 4 from "GNSS degradation ensemble validated on Gannon + 3 hold-outs" to **pilot OEM integration during the 2028 planting season** with ≥1 of Deere Operations Center / AGCO Fuse / CNH AFS Connect. Cite [`letters/ag-industry-loi-*.pdf`](https://github.com/577Industries/helios-program/blob/main/phase-ii/letters/) when filled. + +**Success criterion**: TFT-TEC operational across the 0-24 hour horizon; v2 Gannon retrospective shipped (see §1.3); ≥1 OEM telematics integration deployed in pilot mode; field validation across 5-10 precision-ag operations. + +### Objective 5 — Phase III Commercialization and Stakeholder-Approved Operations + +> Phase II refines Phase I Obj. 5 from "≥2 NASA-relevant + ≥2 commercial LoIs + Phase II commercialization plan" to **Phase III commercialization plan + Phase II SaaS production deployment**. Cite [`commercialization-plan-refined.md`](./commercialization-plan-refined.md). + +**Success criterion**: ≥3 paying customers in pilot tier; ≥1 OEM revenue-share agreement signed; production-grade SaaS at 99.9% uptime; Phase III commercialization plan with named investors or strategic partners. + +--- + +## 3. Work Plan, Validation Framework, Risk, and Phase III Vision — **PHASE II ADJUSTMENT** + +> Phase II executes over 24 months across five concurrent tasks (T1-T5) aligned with the new objectives. The task structure mirrors Phase I's T1-T5 framing but extends each task to a 24-month timeline with operational milestones. + +### T1 — Operational Ingestion at Scale (Months 1-12, sustained ops Months 13-24) +### T2 — Real-Time Calibrated Fusion Engine (Months 1-12, sustained ops Months 13-24) +### T3 — Operational Translation Modules (Months 4-18) +### T4 — Production API, Dashboard, and Operational Validation (Months 6-24) +### T5 — Field Validation, OEM Pilots, and Phase III Commercialization (Months 1-24) + +### 3.1 Pre-Registered Validation Framework (updated) + +> **Carry forward from Phase I §3.1** + add Phase I kill-gate result citation when Sprint D ships. The pre-registration discipline carries forward verbatim. Cite the v1 → v2 methodology evolution (Sprint C-Training v2 review pack at [`../specs/2026-05-17-Sprint-C-Training-v2-review-pack.md`](https://github.com/577Industries/helios-program/blob/main/specs/2026-05-17-Sprint-C-Training-v2-review-pack.md)) as evidence of demonstrated rigor. + +### 3.2 Risk Assessment and Mitigation (updated) + +> **Carry forward from Phase I §3.2 risk table.** The "Validation event cherry-picking" row is now **Likelihood: Low (mitigated and demonstrated)** — change from Phase I's "Low (mitigated)" — because the v1 → v2 evolution proves the pre-registration discipline survived a real methodology surprise. + +### 3.3 Phase II Execution Plan — **PHASE II ADJUSTMENT** + +> **PHASE II ADJUSTMENT — operator action.** Phase I §3.3 ("Phase II Vision") becomes Phase II §3.3 ("Phase II Execution Plan") — replace the "vision" framing with concrete deliverables. The seven sub-bullets (a-g) from Phase I §3.3 each get a Phase II-specific milestone date, owner, and acceptance test. Reference: +> - The [`evidence-package.md`](./evidence-package.md) for what Phase I delivered +> - The [`commercialization-plan-refined.md`](./commercialization-plan-refined.md) §A for the five Phase I learnings that shape Phase II execution +> - This document's §6 for the Phase III vision (formerly Phase II vision) + +--- + +## 4. Related R&D, HELIOS Innovation, and Phase I Results + +### 4.1 Current State of the Art + +> **Carry forward from Phase I §4.1.** Refresh: cite any peer-reviewed publications appearing between Phase I submission and Phase II submission that change the SOTA framing. + +### 4.2 What Is Innovative About HELIOS + +> **Carry forward from Phase I §4.2.** The five innovations (model-agnostic decision-calibrated fusion · provenance-aware architecture · dual-use translation · equipment-aware GNSS prediction · industry-native output) all carry forward. Update each to cite the relevant Phase I shipped artifact URL — see [`evidence-package.md`](./evidence-package.md) §2. + +### 4.3 Phase I Results — **PHASE II ADJUSTMENT (NEW SECTION)** + +> **PHASE II ADJUSTMENT — operator action.** This is a **new** section that did not exist in the Phase I proposal. It heavily cites the [`evidence-package.md`](./evidence-package.md) URLs. The new section is the single highest-leverage Phase II proposal addition — reviewers ask "what did you actually deliver in Phase I?" and §4.3 answers in one page. + +Structure: +- **§4.3.1 Public-portfolio deliverables** — cite [`evidence-package.md`](./evidence-package.md) §2 with each of the 5 public Pages sites + the 4 public repos + the 1 private companion +- **§4.3.2 Citable ground-truth observations** — cite [`evidence-package.md`](./evidence-package.md) §3 with each of the 5 Gannon ground-truth observations (Kp peak · Bz peak · TEC peak · 1,302 station-hours · kill-gate result) +- **§4.3.3 Community engagement and standards work** — cite [`evidence-package.md`](./evidence-package.md) §4 (RFC-0001) +- **§4.3.4 Methodology evolution** — cite [`evidence-package.md`](./evidence-package.md) §5 (Sprint C-Training v1 → v2) +- **§4.3.5 Peer-reviewable artifact** — cite [`evidence-package.md`](./evidence-package.md) §7 (arXiv preprint when submitted) + +### 4.4 577 Industries Relevant Experience + +> **Carry forward from Phase I §4.3** (now renumbered to §4.4). Add: HELIOS Phase I as the **most recent** SBIR Phase I execution, delivered in 6 months with the public portfolio at [`evidence-package.md`](./evidence-package.md) §2. + +--- + +## 5. Key Personnel and Facilities + +### 5.1 Key Personnel + +> **Carry forward from Phase I §5.1.** Refresh: replace "named candidates identified" with **named-with-LoIs** when [`letters/ml-engineer-loi.pdf`](https://github.com/577Industries/helios-program/blob/main/phase-ii/letters/) and [`letters/sme-consultant-loi.pdf`](https://github.com/577Industries/helios-program/blob/main/phase-ii/letters/) are signed. + +### 5.2 Facilities and Equipment + +> **Carry forward from Phase I §5.2.** Update: AWS production-grade deployment costs for 24-month operations (vs. Phase I's prototype scale). + +### 5.3 NASA Center Engagement + +> **Carry forward from Phase I §5.3.** Refresh: replace "Target validation-framework benchmarking" framings with **demonstrated engagement** when [`nasa-engagement/`](https://github.com/577Industries/helios-program/blob/main/phase-ii/nasa-engagement/README.md) records are filled. If LoIs from NASA centers land, cite them in [`letters/nasa-center-loi-*.pdf`](https://github.com/577Industries/helios-program/blob/main/phase-ii/letters/). + +--- + +## 6. Potential Post Applications and Commercialization Plan + +> **Reference**: [`commercialization-plan-refined.md`](./commercialization-plan-refined.md) — Phase I learnings → Phase II strategy refinement. This section in the Phase II proposal pulls heavily from that document. + +### 6.1 Beachhead Market: U.S. Precision Agriculture +### 6.2 Revenue Model +### 6.3 Go-to-Market Strategy +### 6.4 Phase III Expansion Verticals + +> Phase II §6.4 covers what Phase I §6.4 called "Phase II Expansion Verticals" — autonomous-vehicle GNSS integrity · geospatial surveying · satellite drag prediction · parametric space-weather insurance. Phase II makes these **fundable** Phase III work, anchored on the Phase II operational prototype. + +### 6.5 NASA Mission Applications Beyond SRAG +### 6.6 Competitive Positioning and IP Strategy + +--- + +## 7. Budget Summary + +> **Carry forward Phase I §7 structure**, scaled to the Phase II ceiling and 24-month period of performance. Categories: +> +> - Direct Labor (PI, ML Engineer, additional Phase II hires) +> - Fringe Benefits +> - Subcontract (SME consultant continuing; possibly additional) +> - Cloud Computing (production-grade AWS for 24 months) +> - Travel (NASA centers, OEM partner sites, ag-industry conferences) +> - Materials and Software Licenses +> - Fee / Profit +> - TABA Request (if eligible at Phase II) +> +> Subcontracting must remain below the SBIR Phase II 50% cap (NFS 1852.219-80). PI primary employment with the small business preserved per NFS 1852.219-83. All work in the United States. + +--- + +## 8. References + +> **Carry forward Phase I §8 references** [1]-[32]. Add Phase II-specific additions: +> +> - [33] HELIOS Phase I evidence package: +> - [34] HELIOS public companion document: +> - [35] HELIOS arXiv preprint: arXiv:YYYY.NNNNN (when submitted) +> - [36] HELIOS OSF pre-registration: (when filed) +> - [37] HELIOS GitHub portfolio: + +--- + +## Phase II adjustment checklist (for operator review) + +The dispatch spec calls for these four specific Phase II adjustments — confirming each is flagged in this scaffold: + +- [x] **§1.3** Gannon retrospective → cite v2 real-SPP analysis when TFT-TEC lands +- [x] **§2** Phase II success criteria reflect TRL 5-6 operational thresholds (CCMC proving-ground evaluation, OEM partnership commitments, 99.9% uptime) +- [x] **§3.3** Phase II "vision" → Phase II "execution plan" (replace vision framing with concrete milestones) +- [x] **§4.3 NEW** "Phase I results" section citing the evidence-package URLs heavily + +--- + +## Cross-references + +- Submitted Phase I proposal (locked; do not modify): `/home/twawe/577i-Projects/SBIR Working Folder/NASA/HELIOS_NASA_SBIR_PhaseI_Proposal.docx` +- Plaintext extraction: `/home/twawe/.claude/projects/-home-twawe-577i-Projects-SBIR-Working-Folder-NASA/774be7f5-a036-4889-8afe-4c087e05097c/tool-results/b0awntn99.txt` +- Public companion (Phase I mirror): [`../companion/companion.md`](https://github.com/577Industries/helios-program/blob/main/companion/companion.md) +- Evidence package (this Phase II evidence index): [`evidence-package.md`](./evidence-package.md) +- Refined commercialization plan: [`commercialization-plan-refined.md`](./commercialization-plan-refined.md) +- Phase II evidence-assembly dispatch spec: [`../specs/2026-05-18-PhaseII-evidence-assembly-spec.md`](https://github.com/577Industries/helios-program/blob/main/specs/2026-05-18-PhaseII-evidence-assembly-spec.md) +- Sprint D dispatch spec: [`../specs/2026-05-18-Sprint-D-kill-gate-spec.md`](https://github.com/577Industries/helios-program/blob/main/specs/2026-05-18-Sprint-D-kill-gate-spec.md) +- TFT-TEC dispatch spec: [`../specs/2026-05-18-TFT-TEC-forecasting-spec.md`](https://github.com/577Industries/helios-program/blob/main/specs/2026-05-18-TFT-TEC-forecasting-spec.md) +- arXiv preprint dispatch spec: [`../specs/2026-05-18-arXiv-preprint-draft-spec.md`](https://github.com/577Industries/helios-program/blob/main/specs/2026-05-18-arXiv-preprint-draft-spec.md) From eff1c908402720de6cd580ba8cdf7fe0cb90d569 Mon Sep 17 00:00:00 2001 From: 577-Industries Date: Mon, 18 May 2026 09:34:38 -0400 Subject: [PATCH 2/2] fix(phase-ii): correct RFC-0001 URL to rfc/RFC-0001-feature-lineage.md --- phase-ii/evidence-package.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/phase-ii/evidence-package.md b/phase-ii/evidence-package.md index a59f79d..51917ce 100644 --- a/phase-ii/evidence-package.md +++ b/phase-ii/evidence-package.md @@ -124,7 +124,7 @@ Expected fields when filled: The provenance schema is filed as an open RFC, demonstrating community-engaged standards development before commercial lock-in. -- **RFC-0001 source**: +- **RFC-0001 source**: - **RFC issue (open for comment)**: - **8 §6 design questions** open for community input (SPASE 2.7.1 composition, W3C PROV-JSON binding, RO-Crate 1.2 JSON-LD nesting, transformation-chain depth limits, etc.) - **Cross-posts** (operator action — `OPERATOR_TODO.md` item 4): SPASE info list · sunpy-dev · CCMC feedback channel · 577 Industries LinkedIn