Tailoring Guide¶

How an organization shapes the framework to itself. The full schema is reference/manifest.md; this is the tour.

Start from an archetype¶

ea preset list                     # compare the archetypes: domains, method weight
ea preset show open-agile-architecture
ea manifest adopt open-agile-architecture            # review the plan…
ea manifest adopt open-agile-architecture --confirm <token>

Adoption expands the preset to explicit values: methods materialize into definitions/, domains land in ea.manifest.yaml. Nothing is inherited by reference; the Manifest afterwards fully describes your configuration.

Tailor incrementally¶

Add/adjust domains as your practice grows: ea manifest domain add security --types control,risk · domain set-types business --types capability,principle,okr · domain remove <id>.
Add methods one at a time: ea pack list / pack show <pack@version> to inspect, then ea method add <pack@version#method>. A type added this way arrives unmapped — assign it to a domain before authoring.
Cross-pack edges: when two packs should link (a UX pack's ui-flow to an outcome type), add an org relationship overlay: ea manifest relationship add addresses --source capability --target risk --cardinality 0..*. Override or disable a pack's own edge the same way.
Id collisions: if two packs ship the same rule id (refs-resolve is everywhere), rename one locally: ea manifest rename add --pack lean-ux --kind rule --from refs-resolve --to lux-refs-resolve — set it before the clashing method add, then retry.
Governance: ea method deprecate <id> --reason "…" blocks new use of types only that method produces, while existing artifacts are grandfathered.

Evolve¶

Growing heavier is a migration, not a rebuild:

ea migrate enterprise-architecture      # three-way delta: your additions kept,
                                        # undiverged values evolve, conflicts warned

Your own domains, methods, policies, and overlays are carried forward; only genuine differences surface for a decision. The same verb with pack@version bumps a pinned pack version instead.

All of this is also available conversationally — ask the ea-architect agent to tailor and it will discover the real options (preset list, pack show) and walk you through these same verbs, every write propose → review → confirm.