Repurposing Methodology and Architecture for AIQ Integrations

Last reviewed: October 2, 2026

Use this article to plan when existing automation assets can be repurposed for AIQ integrations instead of rebuilt from scratch.

What changed in this article

• Reframed the page as integration planning guidance rather than an abstract methodology note.
• Added checks for asset ownership, current relevance, dependency health, data compatibility, runtime support, and maintenance cost.
• Added decision guidance for reuse, refactor, migration, or retirement of existing assets.

Validation workflow

1. Inventory the existing asset, its owner, runtime, dependencies, data inputs, and known limitations.
2. Decide whether the asset should be reused as-is, refactored, migrated, or retired.
3. Validate the repurposed asset in AIQ with clear evidence and a maintenance owner.

Review note: This page now supports practical integration decisions instead of generic architecture language.

Last updated: October 2, 2026

If you have feedback on this topic, contact documentation@appvance.ai.