UNOOSA

Packet identity

Packet ID

organizations:entity-unoosa

Packet SHA-256 identity

7368bb21457758570d4b103077d0244002451fbce79a1e27f8212d01247824d8

Corpus SHA-256 identity

8fa944604ca189f5a9216ca59f640ad2ca20972ad512f2f4970764716782e18d

Release ID

public-alpha-2026-07-26-research-visuals-r14

Source commit

3eb036fce3d711336c8c605625895e8a2e799ab0

Frozen corpus date

2026-07-25

Primary records

1

Reference sources

1

Questions and exclusions

Required questions

1. Required question 1 (exact ID: question-1)
   Does the official source establish the entity, current program, and bounded capability described?
2. Required question 2 (exact ID: question-2)
   Are potential fit, risks, access, geography, and engagement boundaries current and proportionate?
3. Required question 3 (exact ID: question-3)
   Could any wording imply partnership, endorsement, availability, procurement, authority, or affiliation that does not exist?

Explicit exclusions

• Indexing is not endorsement, due diligence completion, outreach, procurement, or a relationship.
• No aggregate organization score or sponsor-purchased ranking is permitted.

Requested controlled scopes: ecosystem-due-diligence, information-science

Frozen-evidence decision window: 90 days from the packet freeze. Not applicable to this packet family.

Complete primary record set

Every record below has one primary packet owner. Decisions must bind to the exact record and packet fingerprints; a changed lesson body, evidence grade, citation, locator, source snapshot, requirement, policy, release, or commit expires the old packet.

1. ecosystem-organization · entity-unoosa

   UNOOSA

   Record fingerprint

   07d45b53bc68bb6bd4c93ad35a97d1f4f6f3ba3c4721c83c5d09c860ec76f17e

   Minimum approvals

   1

   Required scope groups

   bounded-competence: ecosystem-due-diligence

   High-consequence domains

   None under the named two-person rule

   Review state

   pending

   Published human decisions

   0

   Inspect the complete frozen review surface

   ID

   entity-unoosa

   Legacy ID

   org-agency-s-022

   Slug

   unoosa

   Name

   UNOOSA

   URL

   https://www.unoosa.org/↗ (opens external site in a new tab)

   Category

   Agency, standards, and public research infrastructure

   Geography

   International

   Relevance

   enabling

   Engagement

   Proposed only, subject to a future fit check and formal UN processes: use public treaty and registry resources; consider participation only through an eligible, transparent mechanism for a defined issue. No outreach, observer status, representation, commitment, or funding has occurred.

   Capability

   Space-law and treaty resources, object registration, support for intergovernmental space governance, capacity building, international cooperation, and public information.

   Entity Kind

   United Nations space-affairs office

   Link Checked At

   2026-07-25

   Relationship

   indexed only; no formal relationship

   Engagement Status

   proposed; not undertaken

   Profile Summary

   The United Nations Office for Outer Space Affairs supports the Committee on the Peaceful Uses of Outer Space, maintains treaty and object-registration resources, and runs capacity-building and international-cooperation programs. It administers and explains processes but does not license all missions or endorse indexed projects.

   Potential Fit

   Could provide authoritative primary materials for international space law, registration, peaceful-use norms, long-term sustainability, capacity building, and governance baselines for Solar System precursors.

   Risks

   1. UNOOSA does not resolve all treaty ambiguities, private-law issues, national licensing, liability, or future settlement governance.
   2. Referencing the UN can falsely imply endorsement, authority, or legal clearance.
   3. Intergovernmental processes are state-driven and may not provide direct access to an unaffiliated project.

   Evidence Boundary

   Official-link review: the UNOOSA site was reachable and documents treaties, COPUOS support, registration, capacity building, and office functions. This review does not establish legal advice, participation eligibility, mission approval, or any relationship with GShips; independent review pending.

   Conflicts

   Conflicts were not assessed beyond publisher disclosure in this official-link review; member-state positions, observer organizations, program donors, and political disagreements were not independently investigated.

   What Would Change

   A concrete precursor activity, current treaty and national-law analysis, formal eligibility, member-state practice, and independent legal review would refine relevance.

Frozen source snapshots

Source inclusion does not determine the disposition. Reviewers must inspect the cited locator and relation, note inaccessible material, and identify stronger or conflicting evidence.

Offline packet and worksheet

Downloads contain no reviewer contact details. Downloading does not create an account or store a review response in the GShips application. Ordinary provider request or analytics logs may record the download request. Work locally: the public site has no review account, upload endpoint, or decision-submission API.

Do not paste a completed decision, identity documents, private contact data, confidential conflict evidence, medical information, controlled material, or exploit details into a public form. Until a separately authorized private handoff exists, retain the completed worksheet locally.

Packet schema · JSON · Decision-bundle schema · JSON

Validate offline

Use Node.js 22.13.0 or later. Keep the packet, worksheet, completed decision, and all six kit files together in a local directory.

1. Download the six kit files below. Complete a copy of the JSON template offline and preserve its templateFingerprint.
2. Finalize a separate output file.

   node finalize-review-decision.mjs \
     --input DRAFT.json \
     --output COMPLETED.json

   This marks the copy complete and calculates an unkeyed canonical bundle fingerprint. A fingerprint detects changes; it is not a reviewer signature.

3. Validate the packet and completed copy.

   node check-review-decisions.mjs \
     --packet PACKET.json \
     --decision COMPLETED.json

   Add another --decision for each independent reviewer.

4. Interpret the result narrowly. A zero exit proves structural consistency only. Neither command appoints or qualifies a reviewer, establishes independence, accepts a decision, or authorizes publication.

• Bundle finalizer
• Validator command
• Decision policy module
• Fingerprint and packet-integrity module
• Review-domain policy module
• Canonical synthesis and interactive review specs