Module app

Modules§

backend_hook: The one statically selected application’s physical-backend boundary.

compatibility_probe: Handle the exact identity-only probe before fbinit or app startup. The executable still owns its binary-only preinit stdin reservation.
compatibility_probe_with_backend: The corresponding pre-fbinit entry for one statically linked adapter. This uses only the adapter type’s compiled identity; it constructs no adapter/options, consumes no stdin and admits no private runtime role. It is metadata-only: held dispatch requires executable_entry_with_backend.
executable_entry: Executable-only entry before fbinit, private roles or normal app setup. Returns a terminal status for a metadata request/refusal, or replaces this process with the exact compatible backend executable. None retains the ordinary builtin application path. The binary still owns its preinit hook.
executable_entry_with_backend: The matching early entry for one statically linked backend executable. Call this before fbinit and before constructing the adapter/options. It handles metadata or adopts the core’s affine input handoff; it never redispatches, reads guest stdin, or grants a private runtime role.
main: Run the application after the executable has initialized its process.
main_with_backend: Run the shared application with this executable’s one linked backend.