Kernel skeleton and test harness authored
error: unknown Cargo.toml feature `bindeps` — resolved in .cargo/config.toml
A hang, panic, or missing marker can never pass. Absence of output is never success.
1 · HOST UNIT TESTS
2 · QEMU BOOT SMOKE
3 · QEMU SELFTEST SUITE
4 · NEGATIVE CASES
// serial marker grammar (specification — not a boot capture)
// harness gate: all stages ∧ fail=0 ∧ pass>0 ∧ exit=33
Evidence per run: artifacts/qemu/<label>.serial.log + <label>.result.json. Rules: no skipped tests to obtain green status; a bug fix lands with a regression test; “passing” is only claimed from an actual run’s evidence.
| ID | Requirement | Status | Evidence convention |
|---|---|---|---|
| BOOT-001 | QEMU reaches kernel entry (B010) | IN DEVELOPMENT | qemu-runner label boot-smoke-* |
| BOOT-002 | Serial logging works (B020) | IN DEVELOPMENT | qemu-runner label boot-smoke-* |
| MEM-001 | Physical memory manager works | PLANNED | unit + QEMU selftests |
| INT-001 | Exceptions/IDT installed | PLANNED | controlled exception test |
| TASK-001 | Scheduler runs multiple tasks | PLANNED | deterministic task output tests |
| DIAG-001 | Panic produces useful serial evidence | IN DEVELOPMENT | panic handler emits [ITISYOU:PANIC]; negative test pending |
A requirement is never deleted because it is difficult. Statuses collapse to implemented+verified / blocked / not-applicable at reporting time.
error: unknown Cargo.toml feature `bindeps` — resolved in .cargo/config.toml
docs/REQUIREMENTS.md · docs/adr/0001..0003 · design/stitch/ (13 screens + DESIGN.md)