Skip to content

Define armory-core integration strategy on top of RIMS #187

@fusion94

Description

@fusion94

Description

armory-core is one of the strongest candidates for eventually running on top of RIMS, but it contains domain-specific logic that should not be pushed into the framework.

This issue defines the integration strategy:

  • what armory-core should inherit from RIMS
  • what remains armory-core-specific
  • what migration path makes sense
  • what should happen only after RIMS is proven by additional domains

Acceptance Criteria

  • Identify which armory-core capabilities map cleanly to RIMS core
  • Identify which armory-core capabilities must remain domain-specific
  • Define likely migration phases or layering approach
  • Document risks of trying to migrate too much too early
  • Ensure the strategy aligns with the RIMS boundary ADR
  • Produce a written integration plan for future implementation

Metadata

Metadata

Assignees

No one assigned

    Labels

    architectureArchitecture and system design decisionsenhancementintegrationIntegration strategy between systems or modulesplanningPlanning, scoping, and roadmap work

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions