Repository map

Active Pipeline Repos

Active pipeline

Repos and data locations used by this pipeline

ComponentRole in productRepository / pathInterview framing
Registry runtimePipeline engine for source inventory, upload-pack generation, metadata stamping, Snowflake load-plan SQL, validation SQL, and run artifacts.github.com/JNA31A_AIT/registry-runtimeExecutable runtime for generating registry pipeline artifacts across the registry set.
Registry control-plane metadataPromoted candidate metadata handoff: manifests, metadata references, Snowflake SQL, validation SQL, checksums, and promotion state. No CSV payloads.github.com/JNA31A_AIT/registry-control-plane-metadataReviewable, versioned control-plane output for architects and deployment planning.
Registry mapping review consoleHuman review and demo surface for metadata, mappings, schema drift, registry coverage pages, and future Snowflake Streamlit views.github.com/JNA31A_AIT/registry-mapping-review-consoleProduct/review interface for explaining and governing pipeline outputs.
Registry control-plane data dumpLocal encrypted PHI-bearing CSV bundle storage. Holds generated upload-pack archives as .tar.gz.gpg files./mnt/c/Users/jna31a/advent-repos/jna31a_ait/registry-control-plane-data-dumpOperational PHI payload store. Intentionally not a Git repository.

Honorable mention

Platform tooling used to plan and govern work

ComponentRole in this programRepository / pathWhy it is separate
Codex platform toolingReusable orchestration layer for DAGs, grouped DAGs, execplans, validation gates, research-to-implementation handoff, and governed agent workflow rules.github.com/JNA31A_AIT/codex_platform
platform-template-bootstrap/
It governs how work is planned and executed across projects; it is not part of the registry data pipeline runtime itself.