Unity Organization Compressed Wiki

Primary role: bounded organization-wide source discovery for Unity Game UI research.

Independent research — not affiliated with or endorsed by Unity Technologies. Snapshot evidence, not a support-status catalog.

This locally authored index compresses 804 public repositories into one tracked data inventory and 20 exclusive primary clusters. It is not produced, sponsored, endorsed, or maintained by Unity Technologies. Organization placement does not establish authorship of forked, mirrored, vendored, or third-party content. Each repository retains its own license and terms.

The machine-readable source is data/unity-technologies-public-repositories.json. It records one row per captured public repository, including stable identity, repository URL, raw fork/archive/template state, default branch and observed HEAD when resolved, snapshot time, license metadata, UI relevance, and one exclusive primary_cluster.

The source snapshot was captured at 2026-07-14T12:59:16Z. The pre-projection inventory SHA-256 was 8291b471251053a8921651eb7c791d13a4794984b73670a51cdb1116deb49657; the tracked JSON SHA-256 is b1438e6e8d438bab3eff2ff02f5a10e9374fdfb89b0581ffb936a42920fa2e05. It records 59 archived repositories, 356 forks, and 4 templates.

Repository Boundary

The inventory covers the public Unity-Technologies organization snapshot and no other owner. NGUI and other third-party sources remain outside its counts. Public organization metadata is discovery evidence; it is not an affiliation, authorship, quality, or support claim.

Reusable Method

1. Start with Unity UI Systems for a current system-choice decision.
2. Use the Unity Repository Map to find UI authority, examples, adjacent evidence, and historical material.
3. Use this page when a UI question depends on a broader engine subject such as rendering, input, ECS, networking, XR, platform integration, services, or tooling.
4. Open the tracked inventory for individual repository URLs and captured metadata.
5. Before turning a repository observation into guidance, resolve and pin the exact Unity/package version and source revision.

The evidence order is: versioned Unity manuals and package changelogs; SHA-pinned implementation source; current version-bounded examples; dated announcements; historical demos; then community anecdotes. Stars, recent pushes, and organization placement are discovery signals, not authority or support status.

Exclusive Cluster Index

First match wins. Fork and archive gates precede subjects; UI authority precedes adjacent technical subjects; technical subjects precede generic samples; the residual is an explicit covered value.

Primary cluster	Repositories	Game UI use boundary
meta-forks-mirrors	356	Discovery only. GitHub fork: true does not establish first-party authority.
meta-archived-historical	32	Archaeology and migration context, not current guidance.
game-ui-primary	9	Explicit UI sources/examples; refine lifecycle and version before use.
graphics-rendering	38	Rendering constraints, shaders, pipelines, VFX, materials, and display behavior.
ecs-dots	22	Data-oriented runtime architecture that can constrain UI state flow.
networking	21	Multiplayer state, transport, lobby, relay, matchmaking, and server flows.
xr-ar	25	Spatial interaction, device input, world-space presentation, and XR constraints.
ml-ai	23	ML, inference, perception, and synthetic-data context; no UI defaults.
robotics	6	Simulation and operator-interface observations only.
2d	7	Sprite, tilemap, 2D package, and pixel-oriented implementation context.
animation	10	Timeline, rigging, Cinemachine, and animation-system dependencies.
audio	3	Audio/DSP and spatial-audio state dependencies.
physics	1	Physics-system context only.
editor-tooling	29	Authoring, profiling, build, package, recorder, and asset-tooling surfaces.
ci-infra	2	Build and test infrastructure; not product UI evidence.
language-runtime	3	Runtime, compilation, scripting, and serialization dependencies.
services-cloud	3	Authentication, economy, analytics, leaderboard, and remote-service states.
platform-mobile	9	Native integration, safe areas, packaging, device constraints, and platform input.
samples-templates	30	Observation-only examples without a stronger subject assignment.
other-mixed-or-insufficient-metadata	175	Covered residual; no speculative subject claim.
Total	804	Exactly one primary cluster per tracked row.

localization-text remains a reserved search facet with zero primary rows in this snapshot. A zero primary count does not prove absence; use UI relevance and repository-specific inspection.

UI Authority Route

The current source triangle is deliberately split:

• uGUI owns the GameObject/Canvas UI package source and current TextMesh Pro source. Use the package version in the target project and a matching SHA.
• UnityCsReference contains the broad UI Toolkit reference implementation within engine C# reference source; it is not a package mirror.
• InputSystem owns UI-input integration such as action maps and InputSystemUIInputModule, not rendering or layout.

Open UnityCsReference as a Unity-engine C# study and reference textbook surface when tracing module architecture, ownership boundaries, and version-pinned implementation paths. It is valuable for readers who already know C# and want to study how Unity's managed engine layer is organized; it is not a learn-C#-from-zero or general-purpose C# curriculum. Read a branch or SHA matched to the target Unity version line, and treat the repository as reference source rather than a package mirror or the complete engine: native/C++ implementation remains outside this corpus.

Current scoped examples include BagelGame, ui-toolkit-manual-code-examples, and a11y-public-sample. Preserve each example's recorded Unity/package baseline.

Historical UIElements/UI Toolkit conference and runtime demos remain historical even if unarchived or recently pushed. com.unity.uiwidgets is a separate archived framework, not UI Toolkit.

NGUI is third-party tasharen/ngui. It is outside the Unity-Technologies 804-repository inventory and appears only as a separately pinned migration comparison in Unity UI Systems.

Opinionated Guidance

• Use game-ui-primary only as a candidate route; open the repository-map lifecycle disposition before citing it.
• Prefer a matching release or Unity-version SHA over a mutable default-branch HEAD for implementation claims.
• Keep engine-subject clusters as dependency context. They do not supply visual defaults or universal Game UI rules.
• Treat stars, recent pushes, and repository names as discovery signals only.

Platform-Specific Guidance

• Match uGUI and UnityCsReference source to the target Unity editor/package line.
• Match Input System evidence to the project's installed package version and UI module configuration.
• Revalidate XR, mobile, safe-area, HDR, and native-integration examples on the target device and render pipeline.
• Preserve each sample's recorded Unity version even when its repository is unarchived or recently pushed.

Residual And Provenance Policy

The 175-row residual means the bounded metadata classifier selected no earlier cluster. It does not mean irrelevant, empty, undocumented, or free of UI evidence. Curated overrides must be versioned and must recompute the full partition; do not edit cluster counts by hand.

Raw fork, archived, and is_template values remain in the inventory. GitHub's fork flag is not a complete authorship model: non-fork repositories can still describe themselves as mirrors, forks, or vendored sources. Treat provenance as unresolved until repository evidence establishes it.

Completeness And Refresh Limits

• The snapshot excludes private, deleted, transferred, and non-default-branch-only material.
• Five stored tree scans were truncated and two zero-size repositories returned tree-fetch errors; absence claims do not rely on those trees.
• Some repository HEADs, versions, licenses, lifecycle statements, and replacement paths remain unresolved.
• X/Twitter evidence was unavailable during the research session. No post, handle, date, URL, or quotation is inferred from that absence.
• The taxonomy is metadata-first. The residual protects against false precision; it is not editorial completion for 175 individual repositories.

Refresh by rebuilding the complete public inventory, preserving stable identities and raw lifecycle fields, rerunning the exclusive classifier, validating all 804 assignments, reviewing changed authority records, and updating the snapshot identity. Never hand-edit one count without recomputing the whole partition.

Unsupported Absolutes

• “In the Unity-Technologies organization” does not mean Unity authored every file.
• “Unarchived” or “recently pushed” does not mean current or supported.
• “No UI signal” does not prove a repository contains no interface code.
• The 175-row residual does not mean the repositories are irrelevant or unclassifiable with deeper evidence.
• This snapshot does not establish the contents of private, deleted, transferred, or non-default branches.

Verification Contract

Run node scripts/validate-unity-org-wiki.mjs --json and node scripts/test-validate-unity-org-wiki.mjs. A refreshed publication must retain 804 unique identities for this snapshot, preserve the exclusive cluster sum, keep NGUI external, and update the page, data, snapshot identity, and tests together.

Source, License, And Attribution

• Inventory basis: public GitHub repository metadata and captured default-branch inspection at 2026-07-14T12:59:16Z.
• Inventory identity before tracked projection: SHA-256 8291b471251053a8921651eb7c791d13a4794984b73670a51cdb1116deb49657; tracked JSON SHA-256 b1438e6e8d438bab3eff2ff02f5a10e9374fdfb89b0581ffb936a42920fa2e05; 59 archived repositories, 356 forks, and 4 templates.
• Repository licenses and reuse terms differ. Follow each repository's recorded and current license before copying code or assets.
• Reuse form: locally authored taxonomy, discovery index, and metadata projection; no Unity logos, trade dress, or first-person organizational voice.

Review Trigger

Revisit this experimental page when the public snapshot is refreshed, a current UI authority source changes ownership or lifecycle, high-value unresolved HEAD/version fields are pinned, curated residual overrides are accepted, or verified social evidence materially changes the source-ranking discussion.

Implementation handoff: Unity public-repository inventory and compressed discovery index.

Consumer reference: not_applicable

Consumer reference reason: This implementation adds repository provenance and discovery evidence, not consumer-specific visual or component guidance.

IA Navigation

Parent: Game UI. Next: Platform Guides.