Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Phase 05 · Sub-layer 04 — Add a developmental connectome if one is available

Recommended model: DeepSeek v4 Flash (opencode) — effort high

Routed: carter route -c moderate -r subagent -n coding,scientific → deepseek-v4-flash / high (bar 72, capability 75.3)

Bounded availability-check-then-ingest: the realistic outcome is often “no second staged dataset exists yet”, which is itself a valid, documented result — so a mid-tier subagent fits.

Working tree

Repository root. Cluster write + ETL if a dataset exists. Does not edit bio/*.tex/discussion.tex.

Goal

The developmental analysis rests on more than the single Witvliet 2021 dataset — by ingesting a second staged/developmental connectome if a suitable public one exists, or by explicitly confirming none does so the single-dataset caveat is stated as a deliberate, current-state limitation rather than an oversight.

Why this matters now

The developmental finding (CF10/S3) is explicitly “a more limited statement” on one dataset (Witvliet). A second staged dataset would let the remodelling/stability claims generalise; if none exists, the manuscript should say so precisely.

Out of scope

  • The other coverage streams.
  • Fabricating developmental stages from a non-staged dataset.
  • Re-running the developmental stats by hand (merge re-runs the harness).

Plan

  1. Survey for a public connectome with multiple developmental/age stages beyond Witvliet (staged EM reconstructions). Assess licence + whether it carries the per-stage connectivity the developmental analysis needs (developmental_graph_metrics, connection_stability).
  2. If a suitable dataset exists: add a Rust ETL importer + registry entry; ingest; validate load_developmental_connectome_data() sees the stages; add citation.
  3. If none exists: record the survey result (what was checked, why each candidate was unsuitable) so the merge can word the Limitations bullet as a deliberate current-state constraint.
  4. Hand the merge the outcome (dataset live, or documented “none available”).

Acceptance criteria

  • Either a second staged developmental connectome is ingested and load_developmental_connectome_data() returns its stages; or a documented survey confirms no suitable public staged dataset is currently available.
  • If ingested: Rust ETL, registry entry with modality + DOI/licence, citation in references.bib.
  • Outcome recorded under article/reproducibility/ for the merge to word the caveat.

Files likely touched

  • crates/tools/etl/ + etl_registry/ (only if a dataset is ingested).
  • article/references.bib (if ingested).
  • article/reproducibility/ — survey/ingest note.

Pitfalls

  • Symptom: candidate dataset isn’t actually staged. Cause: “developmental” in a title without per-stage connectivity. Recovery: require explicit multiple time points with connectivity before ingesting.
  • Symptom: scope creep into a big ingest. Cause: treating “no easy dataset” as “build a hard one”. Recovery: “none available, documented” is an acceptable deliverable — do not force it.

Reference

  • packages/plot/src/syndb_plot/manuscript/data.py (load_developmental_connectome_data).
  • Memory: “No Python in ETL”.
  • Gap inventory item 12.