orlix-runtime-claim-verification

name	orlix-runtime-claim-verification
description	Use before claiming Orlix work is fixed, green, complete, runtime-ready, package-ready, or upstream-test successful. Verifies that exact commands, logs, failure/skip accounting, crash reports, and ADR proof order support the claim.

Orlix Runtime Claim Verification

Use this skill before any completion claim.

Claim Check

Identify:

• the exact claim being made;
• the proof lane it belongs to;
• the required command or runtime evidence;
• the observed command output and logs;
• OrlixOS payload/session evidence when claiming product boot, PTY, shell, or package runtime behavior;
• failure and skip counts;
• simulator or app crash reports checked;
• missing evidence.
• whether the recorded evidence is current and directly relevant to the exact claim, not just any prior command output.

Promotion Order

Product runtime claims must follow ADR 0017:

1. Kernel dependency proof
2. Kselftest kernel-interface proof
3. OrlixMLibC libc proof
4. OrlixMLibC-built syscall/UAPI proof
5. POSIX shell environment proof
6. Third-party package ladder: jq, curl, zsh

Product boot, PTY, shell, or package claims must go through the OrlixOS Kit/session surface. Do not claim them from a resurrected OrlixKit, a hardcoded HostAdapter bundle lookup, an OrlixTerminal UI-only path, or packaging alone.

Output

Say what is proven, what is not proven, and what command or log would close the gap. Do not soften missing proof into success.