garura:decode

To extract brownfield business logic for migration, reverse-engineer the encoded codebase using a feature catalog to produce linked feature, flow, and aspect specifications with executable verification.

Code-to-contract verification works by generating a tiered test suite that must execute baseline-green against the current codebase before any extracted specification is considered captured and staged.

Yes, you can generate deterministic migration contracts across detected tech stacks by synthesizing ephemeral extraction skills at runtime from the physical architecture, provided a tech-stack playbook is present.

Yes, you need a tech-stack playbook present to extract cross-cutting concerns, as the system requires it to detect stacks from physical architecture and synthesize temporary extraction skills at runtime.

The best way to capture issue-scoped artifacts is to enforce strict citation integrity and baseline-green test gating before staging the linked feature, flow, and aspect specifications in STM.

Temporary extraction skills synthesized at runtime are cleaned up automatically after the user’s final Tether, ensuring no ephemeral components remain in the environment post-extraction.