Jump to content

Milestone: The Cargo List-Field Fix — The Dependency Graph Becomes Possible

From The Sovereign Games (MoA Lab)

Welcome to the MoA–TSG Lab. The wiki is the bench. The work is Metrology of the Abstract. Adopt the tools or leave them on the rack — either way, the need doesn't wait.

  • Lab Note: A redlink is not a failure. It identifies Calibration Debt—work waiting to be measured, mapped, and calibrated.

CYCLE Calibration position

StatusActive Development

This page is a conceptual instrument under Permanent Beta. It declares a real calibration position, not a finished product waiting to ship. Checking continues; an edit is only required when evidence demands it. Stage: Seed to Fruit.

Feedback welcome — especially clarity, failure modes, and calibration gaps. Use discussion or Contribute.


The Cargo List-Field Fix — The Dependency Graph Becomes Possible

Canonical Question: Could this project's entire dependency-tracking architecture — Calibration Dependent, Calibration Dependencies Display, Ripple Review, the whole tracker ecosystem — have existed without first solving a specific, stubborn technical problem in how multi-value data gets stored and queried?

What was proven: No. Every dependency-graph mechanism built afterward — `Calibration Dependent`, `Calibration Dependencies Display`, the Core-Priority Ripple Review rule, `Breadcrumb Tracking`'s Master Index, the Milestones feed itself — depends on one underlying capability: reliably storing and querying a page's list of dependencies as genuinely separate, matchable values, not one opaque string. That capability did not exist at the start of the session. It was fought for, through multiple real, documented failures, before it worked.

The actual path, worth recording precisely because every failed attempt was reasonable, not careless:

  1. SMW's `+sep=;;` inline separator — attempted, failed.
  2. SMW property-level separator declaration (`Property:Has dependency`, `+sep=;`) — attempted, failed.
  3. `#arraymap` manual splitting — attempted across multiple syntax variations, consistently failed to actually split on the delimiter.
  4. The eventual, working fix: abandoning SMW's list mechanism for this field entirely and switching to Cargo's native `List (;) of Page` field type, paired with the `HOLDS` query operator. This worked immediately, including on pages with multiple dependencies.

Why this is the milestone, and not just a bug fix: this wasn't a cosmetic problem. Until this was solved, a page could not reliably tell you what it depended on, or what depended on it, in a way any query could trust. That single capability is the actual foundation every later piece of infrastructure — the trifecta, the trackers, Distributed Instrumentation's own evidence base — was built on top of. Conceptual Instruments could describe pages as gauge blocks calibrating each other; this fix is what made that description operationally true rather than aspirational.

Evidence

  • Calibration Dependent and Calibration Dependencies Display both function correctly today specifically because of this fix — neither worked before it.
  • The full failed-attempt sequence is preserved in Known Site Issues & Fixes, not smoothed over — the failures are as much a part of the record as the eventual success.
  • Every subsequent Ripple Review, every `depends_on` field populated across dozens of pages tonight, every Milestone Feed entry, relies on this mechanism working correctly.

What This Milestone Does NOT Claim

This does not claim SMW's list mechanism is permanently broken or unfixable in general — only that, for this project's specific configuration and needs, Cargo's native list type was the solution that actually worked, after genuine, good-faith attempts at the SMW-native approach failed. It does not claim no other Cargo-related bugs remain (the field-type audit flagged elsewhere is still outstanding).

Calibration Dependencies

See the Game. Refuse the Game. Build Better.


Page Transparency & Calibration

This page is under continuous calibration in line with the Permanent Beta principle.


Public Discussion Welcome

Questions, suggestions, feedback, disagreement, and proposed improvements are welcome on the Talk page.

Light rules:

  • Prefer evidence and concrete examples over slogans.
  • Apply Diagnostic Inversion Test when criticizing — the same standard to this page that you would apply elsewhere.
  • Distinguish observation from conclusion.
  • Calibration entries and Decision Records are maintenance records; public discussion belongs in ordinary Talk threads.
  • This framework remains in Permanent Beta. Better calibration is always in scope.



Structural Connections

Calibration Dependent

Pages that list this page as a load-bearing dependency: None found. Either nothing currently depends on this page, or no dependent page has yet listed it in their `depends_on` field.

If this page is edited substantively, review the list above per the Ripple Review rule — see Calibration Dependencies: Standards and Process#Rule: Core-Priority Changes Trigger Mandatory Ripple Review.


Calibration Dependencies

Pages this page relies on as load-bearing dependencies: Known Site Issues & Fixes Template:Calibration Dependent Template:Calibration Dependencies Display If incorrect, edit the `depends_on` field in Admin Page Status — do not edit this section directly, it is auto-generated.



Calibration References

This page is calibrated against the following core standards and reference materials:



Page Construction & Maintenance References

How we construct, maintain, and utilize each page as a self-admin control panel.

  • Distributed Instrumentation — the architectural principle behind why this page (and every page) carries its own live instrumentation, rather than relying on a separate central dashboard.
  • Page Structure Calibration Checklist — the Step 0 structural pass every page should pass before content calibration begins; this page's own structure should be checkable against it.
  • Template:New Page Seed — the seed template this page's basic structure was built from.
  • Calibration Log: When to Create One — the decision procedure this page's own Talk-only vs. dedicated-log status was decided against.
  • Framework Features Reference — maintains consistency and traceability across the framework's structural features while avoiding unnecessary maintenance overhead; consult before introducing a new structural pattern this page might otherwise duplicate.



Calibration Procedure

In development. See Calibration Procedure for current status. No formal step-by-step procedure exists yet beyond the practices demonstrated across individual pages developed during the initial creation of this project.



Tracking & Log Pages




Page Reference

Title The Cargo List-Field Fix — The Dependency Graph Becomes Possible
URL https://www.thesovereigngames.com/wiki/The_Cargo_List-Field_Fix_%E2%80%94_The_Dependency_Graph_Becomes_Possible
Description Documents the milestone where a working multi-value dependency field was finally achieved via Cargo's native List (;) of Page type, after multiple failed SMW-based attempts — the technical foundation every later dependency-tracking mechanism depends on.
Category Site Maintenance