UN-GGCE Portal

Appearance

UN-GGCE ToR2 Decision Log (Shared Memory) ​

This document acts as the authoritative record of strategic decisions, architectural pivots, and stakeholder approvals throughout the ToR2 consulting engagement. All agents (systems-architect, geodetic-researcher, risk-analyst, knowledge-graph-engineer, quality-assurance, and technical-writer) MUST read this file to understand the current context and history of the project.

Instructions for Agents ​

  • READ ONLY: Treat this as a source of truth for current project status and strategic direction.
  • DO NOT MODIFY: Only the lead consultant (Human) or the primary orchestrator should update this file after a decision is finalized.

2026-03-23: Project Setup & Infrastructure ​

  • Decision: All OTel telemetry logs will be stored locally on the server drive to avoid Google Drive sync conflicts and maintain a permanent decision trace.
  • Decision: A Context Graph Data Fabric using RDF-Star and SHACL 1.2 will be the primary architecture for tracking and validating the "Robust Global Geodetic Supply Chain."
  • Decision: A specialized technical-writer agent has been created to ensure all deliverables match the formal UN-GGCE style established in the "State of Geodesy 2026" report.
  • Decision: This decisions.md log will serve as the shared "Drop-box" memory for all agents to ensure consistency across the five work assignments.

2026-03-23: Work Assignment 1 - Principles Selection ​

  • Strategic Pivot (QA Mandate): The quality-assurance agent rejected the initial "best-effort" architectural approach. It is now a mandatory requirement that all "Basic Supply Chain" definitions move beyond scientific cooperation to formalized long-term operational agreements (SLAs/MOUs).
  • Strategic Pivot (QA Mandate): All data centres must strictly adhere to FAIR (Findable, Accessible, Interoperable, Reusable) data principles as defined in JDP Objective 1.2.
  • Strategic Pivot (QA Mandate): Workforce resilience, including mandated succession planning and knowledge transfer, is now a non-negotiable PPTD requirement for any observatory or centre to be included in the "critical path."

2026-03-24: Deliverables Portal & CI/CD Pipeline ​

  • Decision: VitePress is the official static site generator for the UN-GGCE Deliverables Portal, providing a high-performance documentation experience.
  • Decision: The portal is deployed via Docker on Google Cloud Run, utilizing a dedicated build/sync pipeline (sync-docs.sh) for rapid deployment of consulting outputs.
  • Decision: All geodetic workflows and capability models must use Mermaid.js syntax enclosed in standard Markdown (.md) files to ensure proper rendering in the portal.
  • Decision: Raw .mmd files in the outputs/ folder are considered source assets and must be mirrored into Markdown wrappers for publication.

2026-03-24: Work Assignment 1 - Document Traceability & Context ​

  • Decision: Renamed the primary guiding principles document from "Part 1" to "Work Assignment 1: Guiding Principles" to accurately reflect the Terms of Reference (ToR2).
  • Decision: Mandated explicit markdown linking for all foundational UN precedents (IGIF, WMO, Sendai) within the deliverables to ensure direct traceability.
  • Decision: Included a broader research appendix in Work Assignment 1 to formally acknowledge the socio-economic impact studies (EUSPA, London Economics), critical infrastructure risk registers (NIST, UK Risk Register), and enterprise architecture standards (TOGAF, DMBOK, FAIR) that informed the baseline assessment.
  • Decision: Updated the technical-writer and geodetic-researcher agents to actively cite this broader library of references and academic research in future outputs.
  • Decision: Created the "Investment Prioritization and Risk Rubric" (1b_investment_rubric.md) to operationalize the guiding principles. The risk-analyst and roadmap-planner agents have been updated to strictly use this rubric for evaluating gaps and sequencing investment recommendations based on existential risk mitigation.
  • Decision: Conducted a comprehensive scan and download of the primary strategic artifacts from the UN-GGCE website (Strategy and Operating Plan, 1st JDP, Needs Assessment, Hidden Risk Report). These documents have been added to the ./docs directory to serve as the authoritative grounding context for all agent research and drafting activities.

2026-03-25: Geodetic Terminology, Mathematical Prioritization, & Data Provenance ​

  • Decision: Adopted IAG/GGOS Authoritative Terminology: Shifted from IT-centric "nodes" to geodetic "observatories" and "centres" across all documents, reflecting the terminology of the International Association of Geodesy (IAG) and the Global Geodetic Observing System (GGOS). geodesy.science is now the ultimate grounding source for all agents.
  • Decision: Mathematical Translation of the Rubric (Agent Handoff): Documented the explicit mathematical algorithm (Weighted Gap Analysis + Network Criticality Multiplier) in data/mathmatical_rubric.md to translate qualitative PPTD scores into a sequenced JDP roadmap. This establishes a clear workflow: the risk-analyst evaluates the PPTD gap, the knowledge-graph-engineer maps the network topology (EGV bottlenecks, co-location, scarcity), and the roadmap-planner uses SPARQL to compute the Final_Investment_Priority.
  • Decision: W3C PROV-O Implementation for UN Traceability: Upgraded the observatories.json dataset to JSON-LD with strict W3C PROV Ontology tracking (ggsc:provenance). The geodetic-researcher and extraction scripts now log exact source URLs and timestamps for every metadata point (from ITRF, IGS, IVS, ILRS). This ensures the quality-assurance agent can validate all infrastructure data against UN transparency mandates.
  • Decision: Consolidated Core Observatory Network: Refined the raw instrument data into 664 unique physical observatories. Identified 107 "Core Sites" based on GGOS co-location criteria (3+ techniques) and ITRF/IGS official core network designations. Published an interactive component (ObservatoryTable.vue) to the portal for stakeholders to explore this validated infrastructure.
  • Decision: Capability Model Visualization: Replaced the wide, difficult-to-read Mermaid rendering of the Capability Model with a responsive, CSS-grid-based HTML layout directly within Markdown to vastly improve readability on the portal.

2026-03-27: Infrastructure Migration ​

  • Decision: The UN-GGCE Deliverables Portal (Cloud Run instance) has been successfully migrated to the ben@risemarketing.com.au account under the rise-infrastructure-491413 project. The new authoritative deployment URL is https://un-ggce-portal-d2zfxnoqxa-uc.a.run.app. This consolidates the portal hosting under the Rise Marketing infrastructure as requested by the Sysadmin agent.

2026-03-26: EGV-Specific Supply Chain Modeling (Satellite Orbits) ​

  • Decision: EGV-Specific Risk Mapping: Decided to model supply chain risks at the individual Essential Geodetic Variable (EGV) level (starting with GNSS Satellite Orbits) rather than a monolithic view, recognizing that an observatory's criticality varies significantly depending on the specific product pipeline it supports.
  • Decision: 4-Tier Architecture Decomposition: Restructured the Satellite Orbits workflow into four explicit tiers (Tier 0: Acquisition, Tier 1: Archiving, Tier 2: Analysis Centers & Software, Tier 3: Combination & Distribution) to accurately pinpoint institutional and technological bottlenecks.
  • Decision: Software Diversity vs. Maintenance Risk: Formally documented that while the Analysis Center layer is algorithmically secure due to software diversity (Bernese, GipsyX, NAPEOS, PANDA, EPOS.P8), it carries a High "Key Person" maintenance risk due to reliance on niche academic teams.
  • Decision: Identification of Critical Bottlenecks: Identified the Analysis Center Coordinator (ACC) and the SPOCC combination engine workflow is classified as a "High Risk" bottleneck due to process/governance vulnerability, explicitly validated by historical U.S. government shutdowns (2013, 2018-2019).
  • Decision: Stakeholder Accountability Matrix: Shifted workflow documentation from purely institutional to human-centric accountability. Key personnel within the IGS Central Bureau (JPL), Infrastructure Committee (GFZ, EarthScope, CDDIS), and SPOCC development team (GFZ) are now explicitly mapped to their respective supply chain tiers to highlight "Key Person" dependencies.

2026-04-23: Network Operations & Global Network Monitoring Gap ​

  • Strategic Finding: A longitudinal review of the IGS Technical Reports (2013 and 2018) revealed widespread failure across major Analysis Centers, Global Data Centers (SIO, IGN, KASI), and critical Working Groups (e.g., Reference Frame) to submit annual reports.
  • Mapping to Capability Model: This administrative and reporting fragility has been formally mapped as a direct symptom of the low maturity score (2.3) in the "Network Operations" capability.
  • Impact on Supply Chain: The inability to consistently document and report on system health signifies a critical gap in Global Network Monitoring. While data may continue to flow (technical resilience), the lack of systematic monitoring and administrative reporting blinds the supply chain to creeping degradation and capacity constraints, reinforcing the necessity for formalized Service Level Agreements (SLAs).

2026-06-10: Graph Database State — WA2/WA3 Readiness ​

  • Decision: Jena Fuseki (http://localhost:3030, dataset ggsc) is the authoritative datastore. HolonBridge v2.1.0 running on port 3031 provides NL query and SHACL-validated update access.
  • DataBooks in Jena (as of 2026-06-10):
    • capability-maturity-2026-05-12 — 890 triples; 58 capabilities with full PPTD scores (v1.1.0). This is the authoritative source for all maturity scores in WA2 and WA3. Do not read scores from prose.
    • satellite-orbits-v1 — Satellite Orbits workflow v1.0.0 (pushed; blocks landed in default graph pending DataBook format fix — knowledge-graph-engineer to migrate to named graph https://w3id.org/ggsc/satellite-orbits/workflow).
    • itrf-workflow-v0.1, eop-workflow-v0.1, icrf-workflow-v0.1, gravity-workflow-v0.1 — v0.1 stub topology only; must be upgraded before rubric can run (see tor2_workflow.md Step 3b).
    • ggsc-event-graph-holon (20 WA3 country risk DataBooks + event graph + KG holon) — all pushed 2026-06-10.
    • Richard Gross review AssertionEvent v1.2.1 — 10 assertions in graph/events-2026-04-23.
  • Namespace status: 537 triples use legacy ontologist.io namespace. Official migration bridge at http://w3id.org/holon/spec/migration-bridge#graph. Full GGSC reconciliation pending Kurt Cagle's supplement to HGA Pass A §1. This does not block WA2/WA3 content work.
  • Blocking item for WA2: Workflow DataBook stubs (ITRF/EOP/ICRF/Gravity) must be upgraded to use canonical ggsc-cap: IRIs and disaggregated PPTD scores before the mathematical rubric can run. See docs/wa2-wa3-submission-brief.md.

2026-06-10: HGA Namespace Migration Decision ​

  • Decision: HGA vocabulary has migrated from https://ontologist.io/ns/holon# to http://w3id.org/holon/ (W3C Holon CG, acting chair Kurt Cagle). Spec published at https://github.com/w3c-cg/holon. 15 normative DataBooks across Passes 0–F. CC0-1.0 ontology license.
  • Decision: The ;|} RDF-star annotation block terminator convention has been applied across all 21 WA3 DataBooks (committed 2026-06-09).
  • Deferred: Full DataBook rewrite to new namespace deferred until Kurt Cagle completes the GGSC namespace reconciliation supplement (HGA Pass A §1). GGSC-specific terms (holon:EventEnvelope, holon:EventGraphHolon, holon:AssertionRecord etc.) have no bridge mappings yet.

2026-04-28: QA Review - Work Assignment 2 (EGV Workflow Modeling) ​

  • Finding (Positive) - EGV Progression & Tone: The narrative workflow reports (outputs/itrf_workflow_description.md, outputs/eop_workflow_description.md, outputs/icrf_workflow_description.md, outputs/global_gravity_model_workflow_description.md) excellently model the progression from Level 0 to Level 3 EGVs. Institutional mappings and bottleneck analyses correctly identify Single Points of Failure (e.g., VLBI correlation, ITRS Product Center at IGN) and align perfectly with ToR2 expectations. The professional tone meets UN-GGCE standards.
  • Finding (Positive) - DataBook Adherence: The draft DataBooks (data/shacl/*-workflow.databook.md) correctly implement v0.9 standards, utilizing PROV-O (prov:Activity, prov:wasAssociatedWith) to model the multi-tier supply chains as directed.
  • Remediation Completed - Capability Linking: The DataBooks now explicitly bind to the 59 Phase 1 capability instances in data/ontology/ggsc-capabilities.ttl (e.g., ggsc-cap:VLBIDataAcquisition, ggsc-cap:GeodeticDataProcessing).
  • Remediation Completed - Vendor Neutrality: The process metadata block in the DataBooks has been generalized to use "UN-GGCE LLM Pipeline" and "urn:ggsc:pipeline:llm-v1", complying with the strict vendor-agnostic architecture principle.
  • Remediation Completed - Evidence Traceability: The DataBooks have been updated to include prov:wasDerivedFrom links pointing to authoritative IAG/GGOS primary sources and local narrative descriptions, satisfying the Zero Hallucination and Evidence Mandate.
  • DataBook Approval Gate Status: APPROVED. All remediation items have been successfully addressed. Final sign-off is granted for graph database load.

2026-07-05: Stakeholder Approval — Tier Structure and Investment Risk Framework ​

  • Approval: Nicholas Brown (Head of UN-GGCE) has reviewed and largely approved the two framework documents submitted in late June 2026:
    • outputs/appendix_egv_levels_and_tiers.md (v1.1) — EGV Data Levels and Supply Chain Tiers, previously reviewed by R. Gross (IAG President).
    • outputs/1b_investment_rubric.md (v3.0, June 2026) — Investment Prioritization and Risk Rubric, using the two-track operational/governance framework (Tier Risk Score = PPTD Gap × Step Criticality for the operational track; Principles 2, 3, 4, and 6 assessed qualitatively in the governance track).
  • Consequence: The two-track framework is now the approved scoring basis for all ToR2 deliverables. The authoritative tier risk scores are in Jena named graph https://w3id.org/ggsc/graph/tier-risk-scores-2026-06-22 (206 triples; straight unweighted 4-dimension PPTD average per commit 10fcb65, capability DataBook v1.3.0 scores).
  • Decision: The superseded named graph https://w3id.org/ggsc/graph/tier-risk-scores-2026-06-10 (181 triples; old two-factor scoring run) is dropped from Fuseki so agents cannot pull stale scores. The scores remain recoverable from git history and the 2026-06-10 decision log entry if audit reconstruction is required.
  • Standing requirement (Nick Brown, June 2026): All deliverables must include a plain-language lead-in and explicit Terms of Reference linkage so UN Headquarters reviewers (payment approval chain) can follow the documents without prior familiarity with the engagement. This applies to every WA deliverable from this point forward.
  • Follow-up items:
    • data/mathmatical_rubric.md still documents the retired v3.0 three-factor model (Recovery Factor). Requires a v4.0 update to match the approved two-track framework — documentation reconciliation only; the Jena scores already reflect the approved model.
    • Confirm with Nick which residual reservations sit behind "largely approved" before WA3 rewrite is finalized.
    • Confirm whether formal approval by Richard Gross (Chair of IAG) is still required for the WA1 gateway (per tor2_workflow.md WA1 Step 5) or whether Nick's approval supersedes it.

2026-07-06: Capability Maturity Graph — Traceability Gap Closed ​

  • Finding: The named graph https://w3id.org/ggsc/graph/capability-maturity-2026-05-12 — cited by WA2 §2.1 and the standing traceability rule as the authoritative machine-readable score record — contained zero scored capabilities. The 58 scored capabilities existed only in the local file data/shacl/ggsc-capability-maturity.databook.md (v1.3.0). The 2026-06-10 decision entry claiming "890 triples; 58 capabilities with full PPTD scores" in Jena was inaccurate as of this check.
  • Root cause: The six cap-* turtle blocks in the DataBook had a blank line between the <!-- databook:id: ... --> annotation and the code fence, so databook push treated them as anonymous blocks and PUT them sequentially to the default graph, each overwriting the last. Same defect class as the satellite-orbits routing issue logged 2026-06-10.
  • Fix: Removed the six blank lines (whitespace-only change to the DataBook); re-pushed all blocks to their urn:ggsc:holon:capability-maturity:2026-05-12#<block> graphs; additionally merged the seven capability blocks into the canonical https://w3id.org/ggsc/graph/capability-maturity-2026-05-12 graph via databook push -b <id> -g <graph> --merge. Verified: 58 subjects with ggsc:averageMaturityScore; spot-check gravity-data-acquisition-and-storage = 3.3 per v1.3.0 correction.
  • Caveat (resolved 2026-07-06): During the initial (mis-routed) push, the default graph was overwritten before its prior contents were inventoried. Re-pushed data/satellite-orbits.databook.md as a precaution and verified: block graph triple counts (workflow 156, risks 50, capabilities 74) exactly match the pre-existing canonical https://w3id.org/ggsc/satellite-orbits/* graphs — the earlier migration had already copied everything out of the default graph, so no data was lost. Default graph dropped (now 0 triples).
  • Also completed 2026-07-06: data/mathmatical_rubric.md updated to v4.0 — Part A now documents the two-track model actually used in the 2026-06-22 scoring run (two-factor operational score, qualitative governance track, NA=0/÷4 tier-gap convention); retired three-factor/Recovery Factor content removed. Closes the math-doc reconciliation follow-up from the 2026-07-05 entry.
  • Follow-up (resolved 2026-07-06): databook validate (CLI v1.4.2) crashed with require is not defined. Root cause: three CommonJS require() calls inside executeLocalValidation in the ESM module commands/validate.js, plus a fallback-logic bug that invoked local validation with a null engine when neither Jena nor pyshacl was installed. Same defect confirmed present in upstream w3c-cg/holon main (architectures/databook/commands/validate.js) — patch to be sent to Kurt Cagle / filed upstream. Local install patched (requires → top-level imports; clear die() when no engine found); pyshacl 0.31.0 installed via uv tool install as the validation engine.
  • SHACL validation status (2026-07-06): all six DataBooks validate CONFORMS against ggsc-shacl-all.databook.md#ggsc-shacl-all-block: capability-maturity, itrf-workflow, eop-workflow, icrf-workflow, gravity-workflow, satellite-orbits. Brief Step 7 validation checklist items are satisfied.

2026-07-06: QA Sign-Off — WA2/WA3 Submission Package ​

  • QA validation pass (quality-assurance agent): full 10-item checklist run against the live Fuseki graphs and deliverable files. Nine of ten items passed on first pass: all 50 tier-score citations across WA2 and WA3 match tier-risk-scores-2026-06-22 exactly; classification bands and labels consistent; capability claims (9×1.00 Category A list, Network Operations dims, Appendix A bottom-12, domain averages) match the capability-maturity graph; principle citations meet the ≥3-of-5 threshold for all six principles; provenance complete (all 25 tier scores carry prov:wasGeneratedBy → typed prov:Activity with model version and score source); HQ lead-ins present in all seven documents; no stale-model artifacts outside version-history tables.
  • Defect found and fixed: WA3 §3.2–3.5 cited four named-graph IRIs (https://w3id.org/ggsc/graph/{itrf,eop,icrf,gravity}-workflow, taken from the 2026-06-04 submission brief) that contain zero triples in Fuseki. The workflow DataBooks declare — and the data resolves at — https://w3id.org/ggsc/databooks/{x}-workflow-v0.1#{x}-workflow-topology. Citations corrected to the declared IRIs; all four verified resolving (251/228/194/191 triples). The brief's named-graph table is aspirational and should not be used for citations until the Step 3b DataBook upgrade adopts canonical IRIs.
  • Verdict: SIGN-OFF APPROVED (QA verdict was "one four-line citation correction away from approval; no re-verification needed beyond the resolution check" — correction applied and resolution re-verified 2026-07-06).
  • Package status: WA2 v2.0 and WA3 v2.0.0 are submission-ready pending the Human Review gateway (Nick Brown).