Skip to Main Content
Status Submitted
Workspace * IBM Cloud Ideas
Categories Compliance
Created by Guest
Created on Nov 22, 2026

Space Object Registration Timeliness and Function Disclosure Compliance Standard

PROBLEM: Under the Registration Convention, a launching state must furnish registration information only "as soon as practicable" — there is no deadline — and the "general function" field need not disclose a military purpose. The UN Register covered 19,928 of about 21,750 functional objects (91.5%) as of August 2025. A military object can therefore be lawfully registered with a bland function label, late, or — for a non-party or a non-reporting state — not at all in the UN Register, with no sanction in the Convention.

SOLUTION: A compliance standard: a proposed timeliness benchmark for furnishing registration information, a function-disclosure standard that distinguishes a bland label from a meaningful one, and a completeness metric against the UN Register, so registration performance can be measured and compared. A compliance and disclosure standard only — not a registry or a record of any object (that is the UN lane's work, UN-17/UN-25).

EVIDENCE BASIS: DOCUMENTED — Registration Convention Articles II and IV: "as soon as practicable," no deadline; "general function" field (F12); UN Register completeness 19,928 of ~21,750 (91.5%) as of August 2025 (prior graded note unoosa-copuos-20261119.md); G07 gap.

Idea priority Low
Needed By Not sure -- Just thought it was cool