Engineering systems, automation, traceability, reproducible analysis, and agent orchestration.
- 👀 Interested in processes and people, engineering systems, and workflow design.
- 🧭 Current focus: QPLANT/QPS engineering, governed automation, CI/quality evidence, document traceability, mathematical runtime, and federated agent workflows.
- 💞️ Open to collaboration on debugging, workflow pipelines, automation, and engineering tooling.
- 📫 Reach me through GitHub.
- 😄 Pronouns: he/him/his
- ⚡ Outside the tooling: Rugby.
Launch-page rule: this profile repository is a navigation, producer-evidence, and lineage surface. It is not the engineering, TRIAGE, Mission Control, release, or portfolio-readiness SSOT.
authority_transfer=false· refreshed 2026-10-02
| Repository | Current role | Primary use |
|---|---|---|
| cryoplant-project | QPS / QPLANT engineering authority and governed release workbench | OCD/ADR, controlled sources, requirements, interfaces, release contracts, QA/DoV and engineering disposition |
| ABACUS | TRIAGE DOW analytical/runtime parent | DMAIC/12-cluster analysis, DAB measurement, test/coverage/static-analysis burn-down, evidence and observability |
| CODEX | TRIAGE KEB semantic/provenance parent and GitHub/publication automation | Federation contracts, semantic provenance, governed workbenches, publication/Pages and automation |
| pipeline-automation-hub | Mission Control, fleet/cohort orchestration and planning-data processing | QPS TRIAGE orchestration, TOP7/TOP14/TOP21 control, recursive processing, schedule engine and cross-repo receipts |
| DOCX_RTM_Automation | Document / RTM extraction, traceability and rendering | Canonical extraction, manifests, QPS federation, RTM reconciliation and outward document generation |
| CODESPACES_jyperter | Runtime, property-data, artifact-processing and notebook workbench | Reproducible engineering calculations, artifact processing, Level-1 runtime, notebooks and execution tooling |
| gg_MATH | Governed mathematical runtime and research provider | PCA, uncertainty, Monte Carlo, ranking/statistics, temporal methods, visual evidence and releasable method surfaces |
| skills | Canonical reusable skill definitions | Shared math/plots and other governed reusable skill contracts |
The repositories above are intentionally separate. Their root README/CURRENT/control files are the authoritative place to read current state. This profile page should not duplicate volatile percentages, SHAs, workflow counts, release gates, or readiness claims.
The current cross-repository architecture has two different control planes that should not be conflated:
| Concern | Canonical owner / control surface | Profile-repo role |
|---|---|---|
| QPS engineering TRIAGE disposition | cryoplant-project child SSOT | Navigation only |
| TRIAGE semantic/provenance governance | CODEX KEB parent | Navigation only |
| TRIAGE analytical/runtime processing | ABACUS DOW parent | Navigation only |
| Mission Control / fleet execution | pipeline-automation-hub | Navigation + producer/receiver lineage |
| TOP7 → TOP14 → TOP21 cohort model | pipeline-automation-hub / mission-control | Cohort participant only |
| Excel schedule engine implementation | pipeline-automation-hub / excel_schedule_engine | Thin canonical pointer; historical snapshot archived |
| Reusable skill SSOT | skills | Thin canonical pointer; historical snapshot archived |
| Mathematical runtime/provider | gg_MATH | Navigation / provider pointer |
The QPS TRIAGE federation currently follows the child → KEB → DOW → KEB → child route. Parent repositories may append analysis or provenance receipts but do not replace child engineering authority.
Mission Control currently lists GBOGEB/GBOGEB in TOP14_EXTENSION, with telemetry state NOT_YET_MEASURED. That is a fleet/cohort classification only: it does not make this profile repository a TOP14 authority, nor does it imply release or engineering readiness.
Canonical cohort and status sources:
The earlier “QPLANT Digital Twin System” was useful as an umbrella description, but the implementation has since decomposed into explicit governed repositories:
- Engineering baseline, OCD/ADR, requirements, interfaces and release: cryoplant-project
- Document/RTM extraction, traceability and rendering: DOCX_RTM_Automation
- Analysis, quality measurement and DOW runtime: ABACUS
- Semantic/provenance KEB, GitHub automation and publication: CODEX
- Mission Control, cohort orchestration and planning pipelines: pipeline-automation-hub
- Runtime/property/notebook execution: CODESPACES_jyperter
- Mathematical methods and uncertainty/runtime support: gg_MATH
| Legacy phase | Old profile state | 2026 treatment |
|---|---|---|
| Phase 1 — Foundation & GitHub Integration | ✅ Complete | Historical milestone. Capability now lives across CODEX, ABACUS, CODESPACES_jyperter and repository-local GitHub/CI controls. |
| Phase 2 — Document Processing & Digital Twin | ✅ Complete | Historical milestone. Current document/RTM/engineering evidence work is split across DOCX_RTM_Automation, cryoplant-project and pipeline-automation-hub. |
| Phase 3 — AI Enhancement & Real-time Analytics | 🔄 35% | Retired as a single percentage. AI/analytics work spans ABACUS, gg_MATH and project-specific QPS surfaces and is measured by repo-local executed evidence. |
The old 35% Phase 3 value is not a current progress claim.
The implementation and operational authority for the Excel scheduling lane live in pipeline-automation-hub / excel_schedule_engine.
This profile repository now retains only a thin canonical pointer at governance/GLOBAL_EXCEL_SCHEDULE_ENGINE_TOPOLOGY_v1.yaml. The former payload is preserved immutably under artifacts/governance-snapshots/ and implementation/status truth belongs to the owning repository. Generated schedule views remain derived evidence and do not transfer source authority.
See the machine-readable portfolio authority map and governance directory guide.
The intended disposition is:
- Keep here:
PROJECT_*knowledge-map, conversation-corpus, source-class/block-graph and RUN-DELTA controls, proofs, scripts and tests. These are producer evidence created by this repository and are referenced by receiver handovers. - Pointerized bridge paths:
GLOBAL_EXCEL_*andGLOBAL_MATH_PLOTS_*now remain as thin canonical pointers. Their pre-pointer payloads are archived underartifacts/governance-snapshots/; live implementation/control belongs to pipeline-automation-hub, skills and/or gg_MATH. - Do not move directly into cryoplant/CODEX/ABACUS TRIAGE: doing so would blur engineering, KEB and DOW authority boundaries.
- Do not create local TOP7/TOP14/TOP21 folders: cohort assignment is external Mission Control state, not a profile-repository storage taxonomy.
- Reference census complete: the exact governance paths are preserved for historical lineage; the full census is
governance/BRIDGE_REFERENCE_CENSUS_20261002_v1.yaml. Destructive rename/delete remains forbidden.
This repository still has a small executable producer lane:
scripts/project_knowledge_mapper.pyscripts/project_run_delta.pytests/test_project_knowledge_mapper.pytests/test_project_run_delta.pytests/test_profile_authority_guard.py.github/workflows/project-knowledge-smoke.yml
These are profile-repository producer tools, not substitutes for Mission Control or QPS TRIAGE.
Historical project documents remain under artifacts/ for provenance. “Current” wording inside old v1.0-era documents should be read in its historical context unless a newer control explicitly supersedes it.
Working principle: one logical fact, one authority, many deterministic views. Prefer executable proof, source lineage, hashes, explicit authority boundaries and current-main readback over static “complete / production-ready / x%” labels.