Exact repository-contract gate
Ten VCS, Unity, serialization, path, extractor, Package Manager, LFS, and generated-path fields must match. A different indexing contract cannot receive a clean or blocked comparison verdict.
LOCAL TECHNICAL PREVIEW
No repository upload. No branch execution. No automatic repair.Match the repository contract.
Then inspect structural damage.
This working preview compares a structured manifest from one accepted Unity repository revision with one candidate pull request. It requires ten version-control, Unity, path, extraction, package, LFS, and generated-path fields to match before classifying asset/meta parity, GUID identity, changed serialized project references, Git LFS storage contradictions, and Package Manager movement.
- EXECUTION
- Entirely in your browser
- INPUT
- Structured manifest pair
- POLICY
- Definite findings block
- FAIL-CLOSED
- Mismatch becomes unknown
LOCAL WORKBENCH / PIB-REPOSITORY-SNAPSHOT-V0.1
Compare one accepted repository manifest with one candidate.
VISIBLE POLICY / PROJECT-INTEGRITY-REVIEW-V0.1
Contract before classification. Ten repository and extractor fields must match exactly. Definite observed contradictions block; high-confidence signals require owner review. Declared expected changes remain visible and never dismiss a finding.
01asset/meta parityUNITY IDENTITY
02duplicate and changed GUID identityUNITY IDENTITY
03changed serialized project referencesSERIALIZED EVIDENCE
04Git LFS storage-form contradictionsGIT STORAGE
05direct Package Manager lock consistencyPACKAGE STATE
WHAT THIS PREVIEW PROVES01 02 03 04
Observed identity contradictions
Complete path and GUID inventories support asset/meta parity checks. Duplicate GUIDs and identity changes retain the supplied paths and exact evidence instead of becoming a generic warning.
Expected never means hidden
The repository owner can declare expected finding identifiers. Matching changes stay in the report with an expected label; declarations that never appear remain visible for review.
Bounded inference
The result can prioritize one structural contradiction. It cannot prove Unity import or load success, package resolution, tests, builds, runtime behavior, merge safety, blame, or root cause.
Unity stores an asset's GUID in its paired metadata file and recommends keeping assets and metadata together in version control. Unity's Package Manager lock file records a resolved dependency graph, while Git LFS defines a canonical pointer form. The preview consumes a narrow CI-generated inventory of those surfaces; it never requests the repository or binary objects.
CORE KIT + PRIVATE PILOT
Generate four bounded evidence surfaces now.
The source-visible core kit produces local path/meta, GUID, package, and changed-path LFS evidence while leaving serialized references bounded. A private pilot adds the Unity-aware reference index, studio-owned rules, CI baseline lookup, PR destination, and evaluator-owned success test without requesting repository write access.