Space Assurance Profile

0x0 supports space-software evidence generation through explicit profiles. The

profiles are review aids, not certification claims. A mission team still owns

hazard acceptance, project tailoring, physical hardware evidence, and external

approval.

The authoritative machine-readable profile rows are in space/profiles.tsv.

Profiles

Flight Core is the smallest analyzable subset. It uses freestanding or

bare-metal runtime profiles, explicit memory sections, no hidden host effects,

and fail-closed physical target claims. It is the profile a reviewer should use

for flight-software prototypes.

Flight Extended allows reviewed service, file, actor, replay, protocol, or

device boundaries around Flight Core code. It is useful for mission software

that needs explicit integration behavior but still wants flight-style review

evidence.

Ground/Twin is for operations, simulation, replay, digital twins, browser or

live UIs, distributed tests, and mission-analysis tooling. Hosted runtime

features are allowed when they are explicit and tested.

Evidence Boundary

0x0 can generate and verify evidence bundles. It cannot certify a mission,

hardware target, toolchain use, or safety case by itself. The bundle shows what

the repository can prove from local inputs:

• source and package metadata;
• runtime and capability evidence;
• compiler and backend evidence;
• emulated hardware evidence;
• physical hardware evidence when supplied by a lab;
• requirement, hazard, and standards-tailoring documents.

S0 Requirement Mapping

• REQ-S0-001: profile mapping is in space/profiles.tsv.
• REQ-S0-002: claim boundaries are in docs/space-known-limitations.html.
• REQ-S0-003: Flight Core obligations are in docs/space-safety-manual.html.
• REQ-S0-004: standards tailoring is in docs/space-standards-mapping.html.
• REQ-S0-005: hazard links are in docs/space-hazard-analysis.html and

space/hazards.tsv.

Review Use

A reviewer should start with space/requirements-trace.tsv, then follow each

row to source docs, tests, evidence bundles, runtime profiles, and known

limitations. Rows with a gap value are not closed for the relevant phase and

must remain visible in project safety review.