Skip to content

Independent human verifier — verification independence #14

Description

@O6lvl4

Part of #12 (Gap 3). Organisation rung B4 in almide/almide docs/roadmap/active/flight-organization.md.

Why this cannot be closed by the project alone

DO-178C verification independence (DAL A/B) means the author does not decide pass/fail. Today the author, the verifier, the ratchet mover and the merger are the same person. Agents can be given author/verifier roles and the record kept, but that is a mitigation whose acceptance is an authority question (#17; the C4 position paper in #12) — not independence in the standard's sense. A second account of the same person is not independence either.

What is needed

  • At least one qualification engineer with prior tool-qualification experience who owns verification sign-off on this repository.
  • The independence story written down: who verifies what, and what the agents' output counts as.

Prepared in advance (solo, tracked in #12)

CODEOWNERS, the review rules (required_approving_review_count ≥ 1, author ≠ approver), the ratchet-separation gate, the review-record format per ALS section (#10).

Exit

A person other than the author approves normative and ratchet changes; branch protection enforces it; the independence structure is documented for the first qualification attempt.

Metadata

Metadata

Assignees

No one assigned

    Labels

    needs-externalImpossible alone: needs an external party (independent verifier, DER, customer, authority)

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions