Module 04 · Project continuity
runnableShadow Versioning
One human-readable identity across project artifacts.
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
- Intended project IDs such as appcode-xyz-0
- References across Confluence, SharePoint, Git, and testing systems
- Human-facing change history without Git vocabulary
- Artifact grouping by project and delivery stage
- Links between stage criteria and supporting evidence
- Portable project identity across connected tools
Other modules
- Smart RouterModel access gets scattered across provider keys, endpoints, deployment rules, and separate UIs. Even a VS Code assistant and a home chatbot can end up repeating the same integration work.
- Evals & English GovernanceEach model platform has its own eval screens, scoring terms, and policy controls. Teams end up comparing results by hand, while governance rules live in documents that do not map cleanly to provider settings.
- Stage GateAI-assisted projects can jump from an appointment straight into generated code. The missing middle—prerequisites, requirements, decisions, and clear advance criteria—is usually spread across documents and understood by only a few people.
- Context EngineAn agent working across 15 repositories can spend more tokens rediscovering the codebase than answering the question. Every tool builds its own partial picture, then throws much of that work away.
- Data LineageOnce a prompt crosses a gateway, it can be hard to explain which provider, region, model, or internal service handled it. Existing lineage tools cover data estates well, but AI request paths often need a smaller, trace-linked view.
- AI-DORAAI coding agents inflate commit counts and PR volume, hiding code churn, review bottlenecks, and rework. Traditional DORA dashboards track deployment frequency without telling you if half the AI-written lines were reverted two weeks later.