| name | ir-runtime-design |
| description | Design or refactor Talqor IR, lowering, runtime services, ABI, and backend boundaries with explicit invariants, migration costs, and extension strategy. |
| argument-hint | ["ir-or-runtime-topic"] |
| allowed-tools | Read, Grep, Glob, Edit, Write, Bash |
| context | fork |
| agent | compiler-architect |
| effort | high |
IR and Runtime Design
Analyze $ARGUMENTS as a compiler architecture problem.
Required workflow
- Read the current architecture docs and relevant implementation files.
- State the user-visible or compiler-internal pressure that motivates the change.
- Define the boundary under discussion:
- AST to HIR
- HIR to MIR
- MIR to backend
- runtime service boundary
- ABI / FFI boundary
- Compare at least two credible designs if the decision is foundational.
- Prefer the smallest stable contract that unblocks v1.
- Record consequences for:
- optimization
- diagnostics
- backend targets
- stdlib design
- testing strategy
- future language features
Supporting files
Final output
Provide a compact ADR-style result, even if you are not editing an ADR file yet.
