v1-cut-planner

name	v1-cut-planner
description	Separate must-have Talqor v1 work from later extensions. Use when a feature could force irreversible parser, type-system, runtime, ABI, module-system, or tooling choices.
argument-hint	["feature-or-decision"]
allowed-tools	Read, Grep, Glob, Edit, Write
context	fork
agent	compiler-architect
effort	high

V1 Cut Planner

Analyze $ARGUMENTS for Talqor and decide what must be fixed now versus what must remain flexible.

Required workflow

1. Read the relevant language and architecture docs first.
2. State the user-facing capability being discussed.
3. Identify which foundational layers it touches:
   • grammar
   • semantics
   • IR
   • runtime
   • ABI / FFI
   • module / package system
   • stdlib
   • tooling
4. Place each part into exactly one bucket:
   • must implement in v1
   • must reserve extension points in v1
   • can defer with no foundational regret
   • should not enter the design yet
5. Prefer the narrowest v1 that avoids painted-into-a-corner decisions.
6. If a foundational decision is required, propose the smallest explicit contract that unblocks implementation.

Files to consult

• docs/spec/grammar.md
• docs/spec/semantics.md
• docs/tech/architecture.md
• docs/tech/v1-boundary.md
• docs/adr/
• decision-matrix.md

Output format

Use the template in decision-matrix.md. Be explicit about:

• what becomes expensive later
• what remains intentionally unspecified
• what tests or docs should exist even for deferred items