Flight Core Source Subset

Flight Core is the smallest 0x0 source profile intended for analyzable

flight-software prototypes. It is checked by

make flight-core-profile-check.

The machine-readable source table is space/flight-core-source-forms.tsv.

Positive corpus files live under examples/flight-core/. Negative fixtures

live under tests/fixtures/flight-core/.

Allowed Forms

Flight Core source may use:

• module declarations with ⊙;
• exports with ↦;
• locked imports with ↥;
• functions with ƒ;
• explicit function type annotations with ∷;
• primitive I64, Text, Bool, and Unit values;
• direct checked calls;
• local bindings when the checker can account for them.

Every Flight Core function must have explicit source type evidence. The gate

rejects functions that would rely on broad unknown fallback.

Forbidden Forms

Flight Core source must not use:

• filesystem, network, process, browser, or other host effects;
• optional GC;
• implicit or explicit Any;
• hidden allocation;
• unbounded recursion;
• reflection-like metadata;
• unbounded dynamic dispatch.

The gate reports stable diagnostics for these cases:

FLIGHT_CORE_HOST_EFFECT
FLIGHT_CORE_OPTIONAL_GC
FLIGHT_CORE_IMPLICIT_ANY
FLIGHT_CORE_HIDDEN_ALLOC
FLIGHT_CORE_RECURSION
FLIGHT_CORE_DYNAMIC
FLIGHT_CORE_UNREVIEWED_UNSAFE

Positive Corpus

The positive corpus compiles through the bounded compiler path:

./bin/zero oisa examples/flight-core/main.0x0
./bin/zero oisa examples/flight-core/command-health.0x0
./bin/zero oisa examples/flight-core/safe-mode.0x0
./bin/zero oisa examples/flight-core/telemetry.0x0

space/flight-core-build-manifest.tsv records the command, entrypoint, trace

ID, and generated OISA artifact for each corpus file.