Appearance
ToR2 Execution Workflow: Blueprint for a Robust Global Geodetic Supply Chain
This workflow defines the step-by-step process for executing the Terms of Reference 2 (ToR2) using the established Context Graph architecture and the specialized UN-GGCE AI agents.
New Agent: Technical Writer
To ensure all deliverables meet the formal, intergovernmental standards of the UN-GGCE (matching the "State of Geodesy 2026" style), a new technical-writer agent has been added to the team.
Workflow by Assignment
Work Assignment 1: Principles for a Robust Global Geodetic Supply Chain
Objective: Establish guiding principles for a "basic" supply chain architecture.
- [x] Step 1:
systems-architectdefines the guiding principles (redundancy, distributed accountability, resilient critical paths) and establishes criteria for minimum viable maturity across PPTD dimensions. - [x] Step 2:
quality-assurancecross-checks the principles against Phase 1 Joint Development Plan objectives. - [x] Step 3:
technical-writerdrafts the formal Principles Document. - [x] Step 4:
quality-assurancereviews the draft Principles Document for alignment with UN-GGCE standards and ToR obligations. - [➔] Step 5 (GATEWAY): Human Review & Decision Log.
- First draft submitted.
- Reviewed by Nicholas Brown (Head of UN-GGCE).
- Draft updated based on feedback.
- 2026-07-05: Nick Brown has largely approved the tier structure (
appendix_egv_levels_and_tiers.mdv1.1) and the Investment Prioritization and Risk Rubric (1b_investment_rubric.mdv3.0, two-track framework). See decision log entry 2026-07-05. Residual reservations behind "largely" to be confirmed. - Status: Confirm whether formal approval by Richard Gross (Chair of the IAG) is still required or is superseded by Nick Brown's approval.
- Validation Output:
outputs/1_basic_principles.md,outputs/1b_investment_rubric.md,outputs/appendix_egv_levels_and_tiers.md(and OTel trace).
Work Assignment 2: Critical Product Mapping Using Essential Geodetic Variables
Objective: Map the end-to-end delivery workflows for the five critical geodetic products (Satellite Orbits, ITRF, EOP, ICRF, Global Gravity Model).
- [x] Step 1 (Research):
geodetic-researchermaps workflows from Level 1 EGVs to Level 3 EGVs for all five products, identifying node topologies, capability dependencies, and operational bottlenecks. - [x] Step 2 (Narratives & Diagrams):
technical-writercompiled mapping data into formal narrative reports (outputs/*_workflow_description.md) and Mermaid diagrams. QA approved 2026-04-28. - [x] Step 3 (Draft DataBooks):
knowledge-graph-engineergenerated baseline DataBooks for all five workflows. ITRF, EOP, ICRF, Gravity are v0.1 stubs; Satellite Orbits is v1.0.0. All pushed to Jena 2026-06-10. - [/] Step 3b (Upgrade Workflow DataBooks — PARTIAL): v0.2 meta graphs pushed for ITRF/EOP/ICRF/Gravity but topology graphs remain v0.1. No longer blocks WA2 scoring — the 2026-06-22 rubric run scored directly at tier granularity. Remains open for capability-level traceability (canonical
ggsc-cap:IRIs, disaggregated PPTD sub-scores per tier node). Seedocs/wa2-wa3-submission-brief.mdStep 2. - [x] Step 4 (Mathematical Rubric): Scoring run completed 2026-06-22 (
urn:ggsc:activity:wa3-risk-scoring-2026-06-22, two-factor operational model per approved two-track rubric). All 25 tier scores in named graphhttps://w3id.org/ggsc/graph/tier-risk-scores-2026-06-22. Superseded 2026-06-10 graph dropped from Fuseki 2026-07-05. - [x] Step 5 (Revise Workflow Documents): All five
outputs/*_workflow_description.mdupdated with principle citations and disaggregated PPTD data (June 2026); all 25 tier score callouts refreshed from the 06-22 graph 2026-07-05 (several classifications changed under the current bands — EOP T1, ICRF T0, Gravity T2/T3 dropped from High to Significant). - [x] Step 5b (Produce Mapping Report):
outputs/2_product_mapping_report.mdv2.0 produced 2026-07-05 — aligned to approved two-track framework, all scores from the 06-22 graph, Purpose and Reading Guide + Key Terms added for HQ reviewers per Nick Brown's standing requirement. - [ ] Step 6 (GATEWAY): Human Review & Decision Log. Submit WA2 v2.0 mapping report to Nick Brown. Record in
outputs/project/decisions.md. - Validation Output:
outputs/2_product_mapping_report.md(v2.0), individual workflow markdown/mermaid files, DataBook files in Jena.
Work Assignment 3: Risk Assessment and Gap Analysis
Objective: Analyze workflows against Phase 1 maturity scores and basic principles.
- [/] Step 1 (Draft Risk Assessment): Draft exists at
outputs/ggsc-wa3-risk-assessment.md. Known defects: ACC/SPOCC bottleneck absent from §3.4; no WA2 tier citations; CNN citation error in §3.4; §5.2 uses binary threshold instead of four-tier rubric. Seedocs/wa2-wa3-submission-brief.mdStep 6 for mandatory fixes (brief dated 2026-06-04 — re-verify each item before executing; some have been overtaken by the 06-22 rescore). - [x] Step 2 (WA3 DataBooks in Jena): All 20 country risk projection DataBooks, event graph holon, and KG holon pushed to Jena 2026-06-10. Event graph available at
urn:ggsc:holon:event-graph:2026-05-07#*. - [x] Step 3 (Rewrite
outputs/3_risk_and_gap_analysis.md): v2.0.0 produced 2026-07-06. All 25 tier scores and bands fromtier-risk-scores-2026-06-22; two-track methodology with governance-track findings per section; capability claims re-verified against DataBook v1.3.0 (Category A list corrected to 9 capabilities incl. Mandate; gravity acquisition P5 claim removed — score is 3.30 not 2.00; Appendix A rebuilt); named-graph IRIs per product domain; event IDs verified against the event graph; HQ Purpose and Reading Guide added; EOP and Gravity domains reclassified Significant; priority ranking re-sequenced (11 entries, EOP Combination added at #4). - [ ] Step 4 (QA):
quality-assurancevalidates all SHACL, citation fixes, rubric tiers, and WA2 cross-references. Sign off inoutputs/project/decisions.md. - [ ] Step 5 (GATEWAY): Human Review & Decision Log.
- Validation Output:
outputs/3_risk_and_gap_analysis.md(v1.0.0 exists but requires rewrite — see Step 3; SHACL validation logs).
Cross-Cutting Follow-Ups (as of 2026-07-05)
- [ ] Math doc reconciliation:
data/mathmatical_rubric.mdstill documents the retired v3.0 three-factor model (Recovery Factor). Update to v4.0 matching the approved two-track framework. Documentation-only — the Jena scores already reflect the approved model. - [ ] Confirm scope of Nick Brown's approval: clarify residual reservations behind "largely approved" before the WA3 rewrite is finalized.
- [ ] HQ readability standing requirement: every deliverable from WA2 onward must carry a plain-language lead-in, ToR linkage, and expanded acronyms for UN Headquarters reviewers (decision log 2026-07-05). Applied to WA2 v2.0; apply to WA3, WA4, WA5 at drafting time.
Work Assignment 4: Basic Supply Chain Architecture Definition
Objective: Define the target state architecture that complies with the basic principles.
- Step 1:
systems-architectredesigns the product delivery workflows and defines the "basic" requirements for all six capability domains. - Step 2:
knowledge-graph-engineermodels the target architecture in the Context Graph. - Step 3:
quality-assuranceverifies the target architecture resolves all Priority 1 gaps. - Step 4:
technical-writerdrafts the Basic Supply Chain Architecture Document. - Step 5:
quality-assurancereviews the drafted Architecture Document against the ToR requirements and defined principles. - Step 6 (GATEWAY): Human Review & Decision Log. Final review of the quality-assured architecture. Record the approved architecture design and implementation constraints in
outputs/project/decisions.md. - Validation Output:
outputs/4_target_architecture.md.
Work Assignment 5: Implementation Roadmap and Blueprint Report
Objective: Compile all work into a cohesive Blueprint and prioritized Roadmap.
- Step 1:
roadmap-plannermaps architectural changes to JDP activities and sequences them into a phased roadmap. - Step 2:
technical-writerintegrates all previous deliverables into the final "Blueprint for a Robust Global Geodetic Supply Chain." - Step 3:
quality-assuranceperforms a final, comprehensive review of the entire Blueprint and Roadmap. - Step 4 (GATEWAY): Final Human Review & Sign-off. Formal approval of the quality-assured Blueprint and Roadmap. The final delivery milestone is recorded in
outputs/project/decisions.md. - Validation Output:
outputs/5_blueprint_final_report.md(and finalized Context Graph snapshot).