Start with a line of sight
A useful trace runs from a transformation objective to the relevant delivery project, from that project to proposed architecture changes, and from those changes to work items and implementation evidence. Each link should have an owner and enough identity to remain navigable.
Keep sources of truth where they belong
Use the architecture repository for models, relationships, decisions and approved states. Use the work-management system for backlog items, acceptance criteria, sprint progress and task ownership. Use project scheduling tools for milestones, resources and critical-path analysis. Refer to external identifiers rather than copying fields that will rapidly diverge.
Model the project architecture as a change set
A proposed programme does not need a second, full copy of the enterprise estate. It needs a bounded set of elements being introduced, modified or retired, plus the context required to assess the consequences. Multiple projects may propose different changes to the same element; that deserves explicit comparison and resolution, not last-writer-wins updates.
Treat implementation and activation differently
A work item being marked complete does not necessarily make the proposed architecture the operational truth. Evidence, approval and the applicable operating-state transition must be considered independently. Conversely, an approved design is not proof that it has been implemented.
The pragmatic minimum
Begin with just four traceable facts: the project identifier, the architectural item affected, the nature of the proposed change and the linked delivery work. Add milestones and dependency detail only where they improve governance or impact assessment.
Strong architecture practice depends on precise models, explicit ownership and decisions that remain useful as systems change. Examples are fictional and are presented as architectural guidance.