UN-GGCE Portal

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-architect defines the guiding principles (redundancy, distributed accountability, resilient critical paths) and establishes criteria for minimum viable maturity across PPTD dimensions.
  • [x] Step 2: quality-assurance cross-checks the principles against Phase 1 Joint Development Plan objectives.
  • [x] Step 3: technical-writer drafts the formal Principles Document.
  • [x] Step 4: quality-assurance reviews 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.
    • Status: Awaiting formal approval by Richard Gross (Chair of the IAG).
  • Validation Output: outputs/1_basic_principles.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).

  • [/] Step 1 (Research): geodetic-researcher maps workflows from Level 1 EGVs to Level 3 EGVs for all five products, identifying node topologies, capability dependencies (from the 59 Phase 1 capabilities), and operational bottlenecks.
  • [/] Step 2 (Narratives & Diagrams): technical-writer compiles the mapping data into formal narrative reports (outputs/*_workflow_description.md) and Mermaid diagrams.
  • [ ] Step 3 (Draft DataBooks): knowledge-graph-engineer generates baseline (v0.1) .databook.md files representing these pipelines in RDF/PROV-O. Note: Strict SHACL validation is deferred until the Holonic architecture model is finalized by Kurt Cagle.
  • [ ] Step 4 (QA & Audit Logging): quality-assurance inspects all outputs (reports, diagrams, draft databooks) to ensure explicit compliance with ToR2 requirements. The QA agent must record its validation steps, findings, and sign-offs directly in outputs/project/decisions.md.
  • [ ] Step 5 (GATEWAY): Human Review & Decision Log. Review the quality-assured mapping report. Finalized workflow structures and key dependencies are confirmed in outputs/project/decisions.md.
  • Validation Output: outputs/2_product_mapping_report.md, individual workflow markdown/mermaid files, and draft .databook.md files.

Work Assignment 3: Risk Assessment and Gap Analysis ​

Objective: Analyze workflows against Phase 1 maturity scores and basic principles.

  • Step 1: risk-analyst assesses vulnerabilities using the Phase 1 PPTD maturity scores.
  • Step 2: knowledge-graph-engineer runs SHACL validation rules against the graph to identify gaps.
  • Step 3: technical-writer drafts the Risk Assessment and Gap Analysis Report.
  • Step 4: quality-assurance reviews the Risk Assessment to ensure all identified gaps are robustly supported by evidence from Phase 1.
  • Step 5 (GATEWAY): Human Review & Decision Log. Review the quality-assured Risk Assessment. Critical vulnerabilities and prioritization decisions are recorded in outputs/project/decisions.md.
  • Validation Output: outputs/3_risk_and_gap_analysis.md (and SHACL validation logs).

Work Assignment 4: Basic Supply Chain Architecture Definition ​

Objective: Define the target state architecture that complies with the basic principles.

  • Step 1: systems-architect redesigns the product delivery workflows and defines the "basic" requirements for all six capability domains.
  • Step 2: knowledge-graph-engineer models the target architecture in the Context Graph.
  • Step 3: quality-assurance verifies the target architecture resolves all Priority 1 gaps.
  • Step 4: technical-writer drafts the Basic Supply Chain Architecture Document.
  • Step 5: quality-assurance reviews 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-planner maps architectural changes to JDP activities and sequences them into a phased roadmap.
  • Step 2: technical-writer integrates all previous deliverables into the final "Blueprint for a Robust Global Geodetic Supply Chain."
  • Step 3: quality-assurance performs 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).