AILang

T

Brummel bd62f2b9d0 docs(design): name the fn-value resolution carve-out in 0018

Audit follow-up (typed-MIR milestone-close drift review, clean). The
boundary contract said codegen does "no callee resolution"; that is true
for App callees — the only thing `Callee` totality claims over — but
`resolve_top_level_fn` still resolves a dotted fn used as a *value* via
`import_map` (the in-corpus-unreachable type-home residue the spec
blessed at mir.2), and ctor/const resolution stay codegen-side. Tighten
the prose to "no App-callee resolution" and name the value-position
carve-out, so the contract is precise and a future drift review does not
read the blanket claim as violated. Prose-only; no code, no test change.

2026-06-01 01:39:30 +02:00

.claude

glossary: bootstrap AILang nomenclature ledger

2026-05-31 17:10:46 +02:00

ail-embed

convention: counter-prefix file naming across docs/specs/, docs/plans/, design/contracts/, design/models/

2026-05-28 13:31:31 +02:00

bench

docs(design): ratify the check→codegen boundary (mir.5, typed-MIR close)

2026-06-01 01:34:37 +02:00

crates

docs(design): ratify the check→codegen boundary (mir.5, typed-MIR close)