documentation-architecture

To create architecture documentation, provide a module name and version to automatically generate a canonical Architecture_<Module>_Vx.y.md document. This enforces a consistent template structure, section boundaries, and cross-references.

Canonical architecture documentation ensures your project's architectural records are consistent, properly scoped, and aligned with the project hub. It solves the problem of scattered, unstructured design docs by enforcing a standard template.

Updating architecture markdown files safely requires refreshing the canonical document by providing the module name and new version. This process automatically maintains template structure, section boundaries, versioning, and cross-references.

Yes, updating the hub registry is part of the orchestration workflow when you generate or refresh an architecture document. This ensures the hub remains aligned with the latest module documentation automatically.

Yes, the canonical architecture documentation applies to both specific modules and broader project themes. It maintains consistent scoping and structure across the Documentation/Arquitetura/ directory regardless of the subject.

The automation is limited to enforcing template structure, section boundaries, versioning, and cross-references. It requires providing a specific module name and version, and operates strictly within the Documentation/Arquitetura/ directory.