Document source: 58297516d707; code reference: 58297516d707. 中文. Source language: zh_CN; requested: en; actual: en; translation: reviewed.

Source documentation does not establish software or physical hardware qualification. See the support and qualification records for their exact scope.

Original ledgers, exit conditions and derived views

The pages below derive from seven original CSV files and do not establish a second status database. Each task retains its original ID, order, all fields, exit conditions, implementation status, software/physical status and original evidence locators; the source SHA-256 is checkable. When the original CSV has no separate exit field, this is explicitly stated; do not construct a supposedly passed condition from other ledgers.

• Original platform-reconstruction ledger
• Factory and TDD ledger
• Original OS workstream ledger
• I/O refinement ledger
• Original SoC workstream ledger
• Original build-system workstream ledger
• Documentation-system ledger

Interpret statuses correctly

• implemented means implementation exists; it does not guarantee complete software qualification for the current checkout.

• development_passed retains its development-validation meaning; do not expand it into formal clean-source archiving.

• Consult the exact results index for qualification_record_authority.

• implemented_tooling only means tooling is implemented; unexecuted physical work remains not_executed.

• not_implemented, not_executed, failures and conditional extensions retain their original values.

• Different workstreams cover overlapping mechanisms; do not add their counts or calculate project-wide completion percentages.

The old 48-item OS checklist has been expanded. Current CSV IDs are OS01–OS55; OS49–OS55 cover physical tooling/actual acceptance, with all original statuses retained. The 48 build-system tasks form a separate ledger. Historical RF ledgers remain under docs/archive/implementation/, reachable through the history entry, and cannot establish current support qualification.

Maintain derived pages

python -m tools.documentation.status
python -m tools.documentation.status --check

The first command only regenerates views from the same original CSV. The second checks missing/stale output, returns nonzero on failure and writes nothing. Regenerate after changing original ledgers; commit/CI checks the same derivation relationship. Successful generation/checking only proves documentation matches original fields; it executes no firmware and acquires no hardware observations. Actual test evidence is in the original results indexes.