Start by acknowledging the real source of truth
A pattern record needs a stable identity, meaningful name, owner, status and a link to its authoritative source. Capture the published version or revision where possible. The architecture repository governs discovery and relationships; the original authoring location can remain authoritative for the content.
Add structure only where it adds value
When a new pattern is authored within the architecture tool, a lightweight structure helps authors: intent, context or problem, structure, participants, consequences and known uses. Drafts should be saveable before every field is complete. Completeness rules belong at review or publication, not on the first keystroke.
Govern application separately from publication
A pattern being approved does not mean that a particular solution conforms to it. Model where patterns are applied, which decisions support their selection and which controlled publication represents a particular version. A PDF or DOCX export is a snapshot, not a new master source.
Avoid duplicating related assets
Architecture principles, ADRs, standards and technology records are their own managed assets. Link the pattern to them instead of pasting their content inside the pattern. That preserves ownership and enables more precise search, dependency and impact views.
Practical lesson
The best architecture pattern library minimises the work required to register existing knowledge and makes reuse easy. Authoring, approval, controlled export and eventual publication can be progressive capabilities rather than mandatory complexity on day one.
This article explains design principles and lessons from developing architecture tooling. Examples are illustrative. A described design approach does not, by itself, indicate that a feature is enabled or generally available in a deployed product.