C712 — Build the mode-and-mechanism map

Question

How should the reader distinguish source traditions from the operations applied to them?

Inputs

{
  "traditions": [
    "MT",
    "LXX",
    "SP"
  ],
  "modes": [
    "regular",
    "cumulative",
    "rounded",
    "calendar-converted",
    "indexed",
    "mirror/forwarded"
  ]
}

Sources

[
  "C631 integrated synthesis; C632–C711; latest File52c"
]

Opened utc

2026-09-28T01:21:27.480116+00:00

Results

{
  "artifact": {
    "path": "deliverables/Chronological_Mode_Map.md",
    "sha256": "65e8a12103fd133f4825cc91f2004c42ecfe4a32a2625b64d8bf78f8837af74d",
    "bytes": 528
  },
  "rows": [
    [
      "MT/LXX/SP source rows",
      "Different admitted b,r,L values and source states"
    ],
    [
      "Regular",
      "Project selected begetting intervals"
    ],
    [
      "Cumulative",
      "Project lifespans with declared phase and frame"
    ],
    [
      "Rounded",
      "Retain admitted scaffold, residuals and source partitions"
    ],
    [
      "Keys",
      "Transform declared durations about explicit anchors"
    ],
    [
      "Indexed carriers",
      "Retain role index while changing unit/resolution"
    ],
    [
      "Mirror/forwarded",
      "Apply the specific declared reflection or forwarding chart"
    ]
  ]
}

Finding

MT, LXX and SP name source traditions; regular and cumulative name projections; Rounded, Keys and indexed or mirror constructions name further specified operations. Treating these as separate coordinates of a source object removes the false expectation of one global date conversion.

Reassessment

Derive the effective total-span ratios of the new retained macro family.

Checks

{
  "distinct_layers": true,
  "traditional_projection_example": true
}

Closed utc

2026-09-28T01:21:27.480602+00:00

Record provenance

Exact record hash: 57274414d80001c29efd959e7b1a75e8e72c69fc1b6e602a4696b6a1b65bf533

Source journal: Research_Cycles/C0632_C0731/journal.json