Flight Core Memory Model

Flight Core uses explicit memory budgeting instead of hidden dynamic behavior.

The source of truth is space/flight-core-memory-budgets.tsv.

Accepted Memory Classes

The S1 gate accepts these memory classes as local release inputs:

• stack: bounded stack budget evidence;
• static-data: static section budget evidence;
• arena: explicit arena budget and review evidence;
• firmware-image: final image-size budget evidence.

The default S1 limits are intentionally small so local evidence remains easy

to inspect. Mission projects can choose stricter limits in downstream evidence

bundles, but a Flight Core claim cannot omit the budget rows.

Allocation Rules

Flight Core source may use static and stack storage under the declared budget.

Explicit arena allocation requires a review row. Manual memory operations are

review-required and must include owner, release, failure-mode, and reviewer

evidence.

The profile forbids optional GC and hidden allocation. If a program needs a

runtime allocator, it belongs in a broader profile until the operation has

explicit budget and review evidence.