Eve library

Pinned repository discovery

Guide

Revision 1

On this page

Source revision: 1ceae52c7896a59ac74a4429d410f3218f0b91c6.

This index accounts for the complete tracked Git tree, including subjects absent from Docs Center. It is a discovery aid, not semantic-unit coverage, a resolved workspace graph, source review or teaching completion. No guide is added and no teaching assignment is promoted by this collection.

What is recorded#

Observation Count
Tracked entries 140,123
Regular files, including executable files 140,121
Symlinks / submodule pointers 1 / 1
Root groups 43
Package / project JSON manifests 3,324 / 3,505
Paths in the documentation inventory 9,262
Paths outside that inventory 130,861
Paths cited by the current presentations 238

The root groups are 42 tracked top-level directories, including dot-directories, plus . for the 59 root files. Each entry retains its exact path, Git mode, object type, SHA-1 object ID and Git blob size. Repeated blob IDs remain separate file contexts. The summed blob sizes count each file context, not unique object storage, checkout disk use or external asset size.

The one symlink is V2/ue/Plugins/BellonaUnrealEditor. Its target is not followed. The one gitlink is V6/ue/Plugins/VRM4U; the pinned external commit is recorded, but its repository contents are not inventoried. Git LFS payloads are not fetched or inspected: a Git blob may be a pointer, not the underlying asset. Untracked, ignored, live runtime and private local files are outside this pinned Git view.

index.json binds every root shard and manifests.json, the source tree, collector modules, documentation index and citation map. Every root shard contains ordered records; use its index entry to locate it. Path hints overlap and are explicitly candidates. For example, a test can also be code, and a JSON file may be configuration or data. The 2,088 unclassified entries remain visible for review; no unknown family is silently excluded.

Manifest reconciliation and limits#

The manifest projection records declared names, target names, dependency names, workspace-protocol presence, tags and implicit dependency declarations. It does not export command bodies, dependency URL/version values or raw manifest bodies. All projected manifest blobs are read from Git by object ID and byte-verified; malformed JSON or unsupported field shapes remain explicit issues. The current collection has no such parse/shape issues.

The pnpm comparison implements the pinned file's literal, * and ** patterns and exclusions. Unsupported glob syntax fails rather than receiving guessed semantics. This is pattern matching, not an executed pnpm resolution: implicit tool exclusions, lockfile resolution, package aliases and installation behavior need separate evidence. The root package is identified separately. There are 3,279 pattern-matching package manifests and 44 other non-root manifests. Examples outside the patterns include test fixtures, Unity packages, embedded mobile modules, infrastructure projects and nested libraries. Do not call all 44 omissions dependency defects or remove them from discovery.

Ten package names occur in multiple directories. The dependency projection keeps all same-name candidates instead of arbitrarily resolving an edge. A name match does not prove an effective dependency, and an unmatched name is not necessarily a broken workspace reference. nearestManifestDirectory describes containment in the tracked tree, not runtime ownership or a deployed service boundary.

The registry projection retains all 58 declarations—48 domains, four platform entries and six product entries—and 88 declared code roots. Their status, owner and project count are declared metadata, not implementation acceptance. All 88 roots have tracked entries at this pin. The comparison with the 54 Docs Center domain records has six registry-only product IDs (v3, v6, v7, v8, v9, v10) and two documentation-only IDs (concordia, nike). These systems have different classification purposes; name-set differences do not by themselves establish a navigation defect. The final Domains/source/code/planned-root audit remains open.

Continue from discovery to explanation#

  1. Reconcile the effective workspace and inferred dependency graph, plus native, Rust, Python, schema, infrastructure and workflow-specific manifests.
  2. Extract meaningful non-Markdown symbols, configuration sections, workflow nodes and asset contracts. Keep generated/vendored origins and distinct file contexts; determine ownership and implementation state from actual sources.
  3. Map those units to substantive explanations and worked cases, then enforce their source, slide and review freshness through the complete coverage gate.
  4. Complete the existing documentation teaching backlog too. A file map, citation or directory listing cannot substitute for an explanation.

The established documentation inventory and its 26 reviewed / 103,300 unassigned meaningful-unit result are unchanged. Section 6 of TODOS.md remains the whole-monorepo completion contract.

Reproduce#

Use the prepared presentation environment and repository resource checks:

sh
python tools/presentations/inventory-repository.py
python tools/presentations/inventory-repository.py --check
python -m unittest discover -s tools/presentations/tests -p 'test_repository_inventory.py'

Collection uses the existing source pin, without checking out a second workspace, running Nx, importing project code, installing dependencies or starting a browser or model. --check independently recollects and compares all generated files. Unknown extra JSON shards require explicit review; the collector never deletes them. Authored documentation in this directory is not generator-owned.