CinvanaAI
← All projects

Tool · Conversations & archives

Message Version Bundle Builder

Bundle an original message and nine prepared context versions with checked original text and character counts.

Repository: CinvanaAI/message-version-bundle-builder

Recorded synthetic example. Source with a complete offline example.

See the idea in action.

One JSON bundle contains levels 0–9 and freshly calculated character counts. Level 0 is required to match the canonical message exactly.

Example input
One canonical message and nine explicitly authored context versions.
Captured result
{
  "output": "output\\versions.json",
  "level_count": 10,
  "level_0_char_count": 100,
  "counts": {
    "0": 100,
    "1": 56,
    "2": 37,
    "3": 18,
    "4": 13,
    "5": 13,
    "6": 14,
    "7": 5,
    "8": 8,
    "9": 8
  },
  "bom": false
}

Try the example.

From the repository root, follow the dependency requirements in the README. This example uses supplied synthetic material.

python -m pip install -e .
message-version-bundle-builder --message-file examples/canonical_message.json --levels-file examples/levels.txt --output output/versions.json

One JSON bundle contains levels 0–9 and freshly calculated character counts. Level 0 is required to match the canonical message exactly.

Complete setup and instructions ↗

The interesting part.

A context representation can be validated structurally without pretending that shorter text is semantically equivalent.

Focused extraction

Where it came from.

Codex_Index version-bundle helper from the historical Python workbench.

Packages canonical level 0 and reviewed context lenses as a independently checked bundle.

Historical chatroom support does not by itself establish current automatic delivery or consumption.

Source ↗

Follow the family: Builder, Factory and the Python Foundry

  • Historical context companionAgent Chatroom Ledger

    Understand why canonical message identity and alternative context views were useful. A documented historical purpose; current direct import/consumption compatibility is not established.

    Source 1 ↗, Source 2 ↗