Trust
What LDTT is — and what it is not.
Is
Portable trust stamp for drone software connectors (tools/plugins that talk to a drone).
Observe = first trust level: declared scope, read-oriented limits, revocable. About the connector, not flight clearance.
Is not
- Aircraft certification
- Operator certification / licensing
- Airworthiness
- Flight safety / “safe to fly”
- FAA or other regulatory claim
- Fleet dashboard
Badge lockups
Observe stamp · Declared read scope
Checked · Declared · Revocable
What was checked (Observe)
At Observe, the intent is: no malicious/write-heavy scope for that level, declared limits (what it may send/receive), and build/provenance details in order for that stamp record — so you have a clearer basis to run the connector. Exact controls live in the stamp spec.
Revocable: Yes. LDTT is designed so a bad or outdated connector can be cut off with a signed revocation list.
Draft vs real issuance
Treat current reference artifacts as draft / placeholder until real Issuer + trust-root signing is live. Prefer “checked against the Observe reference” over “certified.”
Do not claim
- FAA approval, certification, or endorsement
- Any other civil aviation authority approval
- Aircraft certification or type design approval
- Operator certification or licensing
- Airworthiness
- Flight safety certification or “safe to fly”
- That LDTT replaces operational risk assessment, SOPs, or insurance requirements
- That a stamped connector makes the vehicle or mission compliant
- Military / weapons certification (out of scope entirely)
- Guarantees about third-party software beyond the stamp’s stated connector controls
Stamp + logo use
On-page: stamp with connector-scope context; logo in header/footer.
Off-page (intended): display stamp alongside a connector product/docs; link to verify / this page / Spec. Do not imply LDTT certifies the airframe or operator; do not use in FAA filings.
Spec: Spec v0.2 r5.1 frozen · Repo: rockmed888-ship-it/ldtt