Skip to content

Authority acceptance — TQL in a certification program (SOI reviews) #17

Description

@O6lvl4

Part of #12 (Gap 3). The only item whose closure makes "aviation-grade" a sentence that can be said out loud (rung R3 in #9).

Why external

DO-178C certification is of an airborne system and is granted by an authority; a tool is qualified (DO-330) inside that program, through Stage-of-Involvement reviews. No ledger fact in this or the implementation repository can produce it, and "prove-the-checker as tool qualification" has no precedent with any authority yet (flight-qualification.md §2).

Prerequisites

#14 (independence), #15 (gap assessment), #16 (a program to be qualified in), #18 (a qualified native seat), #19 (an entity that can sign) — and the engineering epics #10 #11 #13.

Exit

A written acceptance: "Almide toolchain qualified as TQL-n in program X under DO-330", with the DO-333 formal credit actually taken. Until then the honest phrasing stays the one in QUALIFICATION.md: process discipline operating, certification not claimed.

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