Cross-Reference Standard¶

Why This Exists¶

The Blueprint is a connected enterprise design. Cross-references show relationships between documents without duplicating content or ownership.

Owner¶

The owner is the Chief Product Officer and Enterprise Architect.

Business Value¶

Clear cross-references improve navigation, reduce duplication, and preserve the One Concept, One Owner principle.

Link Rules¶

Use relative links for internal documents.
Link to the owning document for a concept instead of redefining that concept.
Keep link text descriptive.
Avoid links to headings that are likely to change.
Fix broken links before release.

Preferred Link Format¶

[Blueprint Overview](Blueprint-Overview.md)

Ownership Rule¶

When a document references another concept, it must link to that concept's owning document. It must not copy the full definition unless the owner document requires a local summary.

Architecture Mirror References¶

When software documentation references organizational structures, it must link back to the relevant Blueprint concept. This keeps software architecture aligned with organizational architecture.

flowchart LR
    Source[Referencing Document]
    Owner[Owning Concept Document]
    Implementation[Implementation Document]

    Source --> Owner
    Implementation --> Owner