MirevoxGitHub (opens in a new tab)

Module 04 · Project continuity

runnable

Shadow Versioning

One human-readable identity across project artifacts.

View on GitHub (opens in a new tab)

Runnable v0.1 slice available on GitHub — architecture and scope below.

Problem

One project can have its brief in Confluence, approvals in SharePoint, code in Git, and evidence in a testing system. Humans see one piece of work, but the tools expose unrelated histories and technical version language.

Where it sits

Sits alongside the delivery workflow and binds its records across business and engineering systems. It is meant to give people project continuity without asking them to understand Git terminology.

Shadow Versioning is designed to follow the project people recognize, not the storage mechanics underneath it. The interface should talk about the current project, stage, artifact, and change—not commits, branches, merges, or hashes. Non-technical people will not learn Git verbs; that is the point.

The project ID binds references from Confluence, SharePoint, GitHub or Bitbucket, and testing tools. It pairs with Stage Gate so a person can see what changed, which evidence belongs to the current stage, and what still needs attention.

How it fits

This module forms the project flow with Stage Gate: both use the same project ID, while Context Engine indexes the referenced material. Source systems stay authoritative; this is a readable projection, not a new VCS.

Capabilities