weft-usd 0.1.0__tar.gz

weft_usd-0.1.0/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or Derivative
+          Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Ashraf Ghoniem
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

weft_usd-0.1.0/NOTICE

@@ -0,0 +1,7 @@
+weft
+Copyright 2026 Ashraf Ghoniem
+
+This product includes software developed as the weft project
+(https://github.com/distancetozero/weft).
+
+Licensed under the Apache License, Version 2.0 (see LICENSE).

weft_usd-0.1.0/PKG-INFO

@@ -0,0 +1,238 @@
+Metadata-Version: 2.4
+Name: weft-usd
+Version: 0.1.0
+Summary: weft: see a USD stage as data -- derive relationships, query surgically, certify slices. Pull the thread, not the world.
+Author: Ashraf Ghoniem
+License: Apache-2.0
+Project-URL: Homepage, https://github.com/distancetozero/weft
+Project-URL: Repository, https://github.com/distancetozero/weft
+Project-URL: Issues, https://github.com/distancetozero/weft/issues
+Keywords: usd,openusd,pixar,3d,vfx,scene-description,data,aousd
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Programming Language :: Python :: 3
+Classifier: Topic :: Multimedia :: Graphics :: 3D Modeling
+Requires-Python: >=3.9
+Description-Content-Type: text/markdown
+License-File: LICENSE
+License-File: NOTICE
+Provides-Extra: fast
+Requires-Dist: numpy>=1.24; extra == "fast"
+Provides-Extra: usd
+Requires-Dist: usd-core>=24.0; extra == "usd"
+Provides-Extra: dev
+Requires-Dist: numpy>=1.24; extra == "dev"
+Requires-Dist: usd-core>=24.0; extra == "dev"
+Requires-Dist: pytest>=7; extra == "dev"
+Requires-Dist: jinja2>=3; extra == "dev"
+Dynamic: license-file
+
+# weft
+
+Pull the thread, not the world.
+
+```sh
+pip install "weft-usd[usd]"            # once published; until then, from a clone:
+pip install -e ".[usd]"                # [usd] pulls usd-core; the core runs dep-free
+
+weft rels   myscene.usda               # what relationships are in here, natively?
+weft data   myscene.usda               # the whole stage as a table, nothing loaded
+weft pull  'material:…' --context myscene.usda --follow material:binding:full
+```
+
+Opening a USD stage means loading everything and drilling down. weft
+inverts that: stand at any point — a name, an identity, an attribute, a
+place — and pull the threads you care about. A thread is any relationship:
+a material binding, a mount contract, `electrical:feeds`, or a kind your
+team defines. Hierarchy is just one thread on the spool.
+
+```
+$ weft pull 'where:finish=translucent' --context lab.usda --mask-out pull.mask
+$ usdrecord --mask "$(tr '\n' ',' < pull.mask)" lab.usda out.png
+```
+
+Twenty-six pieces of glassware render, floating at their exact production
+transforms, from a scene that was never loaded. No path appeared in the
+question. Run as written against [Animal Logic's
+ALab](https://dpel.aswf.io/alab/) — real production geometry, not a
+fixture — in [`examples/alab/README.md`](examples/alab/README.md#pulling-at-prim-level).
+
+## Addresses
+
+```
+weft pull id:hero-car                        # identity — no path, survives restructures
+weft pull id:occ:weld-47                     # one placement, restructure-proof
+weft pull role:propSocket                    # by contract role
+weft pull 'where:finish=translucent'         # by attribute
+weft pull 'near:id:rack-R42,5'               # within 5 units of a thing, by name
+weft pull bottle01 --follow up:electrical:feeds*8   # trace upstream, 8 hops
+weft pull path:/root/shelf01/bottle_0004     # location — the fallback, not the default
+```
+
+Three rules keep pulls trustworthy:
+
+- **What you didn't pull is declared, never silently absent** — every
+  boundary is counted by kind, and omissions are classed *inert* (a grey
+  material) or *meaning-changing* (a physics joint that would silently
+  re-anchor to the world).
+- **Every answer carries a receipt** — seeds, follow rules, cost, and a
+  digest; a pull is verifiable by recompute-and-compare.
+- **Compatibility is measured, not asserted** — a republish is checked
+  against every consumer's own declared tolerance, not just the provider's
+  promise.
+
+## USD as data
+
+Point weft at a stage you didn't build and *see it as data* — no authoring, no
+schema changes, no load:
+
+```
+weft rels  shot.usda            # the native relationship kinds, with counts
+weft data  shot.usda            # prims x columns: type, bbox, centroid, ...
+weft data  shot.usda --select 'where:bbox_volume>1e6' --load \
+                     --columns point_count,poly_count,byte_cost
+```
+
+Most of that data is **derived, not authored** — weft reads what USD already
+encodes: hierarchy, `UsdCollectionAPI`, and material bindings resolved per
+*purpose* (`full`/`preview`) and inheritance. On ALab that surfaces ~13,600
+material relationships and 114 collections for free. Relationships authored
+anywhere — a native `rel electrical:feeds`, a `UsdPhysics` joint, your team's
+own — are followed (`--follow`), sliced, and certified with **no declaration**;
+weft consumes what your DCC authored rather than asking you to author again. A
+`weft__kinds` block is an optional annotation (a lens, an omission class), not a
+place relationships get made.
+
+## Runs on any USD file, today
+
+No server, no schema changes, no buy-in:
+
+```
+$ weft pull 'chemistry_bottle01*' --context shot.usda --follow Mount
+$ weft who 'name:glass' --context shot.usda    # what depends on this prim?
+$ python -m deps breaks ./assets hub.usda       # what breaks if I republish?
+$ python -m absent shot.usda                    # what silently resolves to nothing?
+```
+
+`deps` sees edges no stock USD API reports (bindings, connections, class
+arcs) and answers the reverse question USD can't. `absent` finds the
+silences USD ships with — stale overrides, bindings to deactivated
+materials — that none of its 28 validators catch.
+
+## usdview plugin
+
+The same `pull`/`who` reasoning, live in the viewer: a "Weft" menu adds
+**Ask…** (resolve a seed against the open stage and select the results),
+**Solo threads** (pull the current selection's threads and deactivate
+everything outside the mask — a *view solo*, not a population mask), **Restore
+world** (undo it), and **Who depends on this?** (incoming edges onto the
+selection, browsable by depth). A docked receipt panel shows the last pull's
+resolutions, members, and boundary, with buttons to copy the member mask or
+save a full manifest.
+
+```
+$ export PXR_PLUGINPATH_NAME=/path/to/weft/extras/usdview:$PXR_PLUGINPATH_NAME
+$ export PYTHONPATH=/path/to/weft/extras/usdview:/path/to/weft:$PYTHONPATH
+$ usdview shot.usda
+```
+
+Both `PXR_PLUGINPATH_NAME` (so libplug finds `extras/usdview/plugInfo.json`)
+and `PYTHONPATH` (so `import weftViewer` — its declared module name —
+resolves) need `extras/usdview` itself, since the plugin's `__init__.py`
+lives one level inside it, in `extras/usdview/weftViewer/`; `PYTHONPATH`
+additionally needs the weft repo root, since the plugin imports `weft.ask`
+and `weft.pull` directly against the live stage. Code, not memory: a python
+usdview plugin is loaded with a plain `import <Name>` off `PYTHONPATH`
+(`pxr/base/plug/plugin.cpp`, `PlugPlugin::_Load()`), so `plugInfo.json`'s own
+directory plays no part in the import — only in libplug's discovery of the
+JSON file itself, via `PXR_PLUGINPATH_NAME`
+(`pxr/usdImaging/usdviewq/plugin.py`'s `loadPlugins()`).
+
+## The engine
+
+For teams that want ground truth, not just queries: a content-addressed
+store, immutable revisions, channels, and baselines — with a promotion gate
+that re-evaluates consumers.
+
+Proven on [Animal Logic's ALab](https://dpel.aswf.io/alab/) (437 real
+placements, contracts derived, not hand-written): a shelf moved 0.7 cm
+passes the provider's 1 cm promise and is **refused by 19 consumers** whose
+own tolerances are tighter — each named, with what it tolerates. Seeding one
+bottle with `--follow Mount` pulls 2 assets instead of 165; the other 163
+threads are declared at the boundary.
+
+```
+$ weft save car car.usda -m "first pass"     # immutable, deduped
+$ weft promote car v002 --to approved        # gated: measured compatibility
+$ weft select 'chassis*' --follow Mount      # a slice, priced before loading
+```
+
+Teams share *ways of seeing* as versioned content: rule sets (which threads
+to follow), edge extractors (your soft-reference conventions become real
+edges), and omission classes — the vocabulary is yours; the machinery
+stays fixed.
+
+## Measured
+
+All from real runs, not projections:
+
+- Seeding one bottle pulls 2 assets instead of 165 — the other 163 are
+  declared at the boundary, not silently dropped.
+- The translucent pull's 26-placement mask is asserted byte-identical to a
+  hand-built reference in the acceptance suite.
+- A 0.7 cm republish, inside the provider's own 1 cm promise, is refused by
+  19 consumers — each named, with its own tolerance.
+- 4,296 production layers walked in 1.75 s (23 ms incremental).
+- The whole scene is addressable in ~126 ms without loading it.
+- 25× storage dedup at 64 KiB chunks.
+
+And on ALab opened whole (47,401 composed prims, 14.5 M points), from
+[`docs/superpowers/specs/2026-10-05-alab-benchmarks.md`](docs/superpowers/specs/2026-10-05-alab-benchmarks.md):
+
+- Pulling one asset vs. loading everything: **0.9 % of the prims, 0.25 % of the
+  geometry — ~3× faster, ~2× lighter.** The win scales with slice size and
+  crosses to a loss near ~99 %, exactly where it should.
+- Query the whole scene as a table in **0.15 s, 125 MB, zero geometry loaded.**
+- A repeated pull of an unchanged context is cached: **0.11 s → 0.003 s (~77×).**
+
+## Status
+
+A working prototype, tested against real production USD (365 tests, CI on a
+no-deps "bare" env and a full `usd-core` env), with no outside users yet. The
+design docs came first; where measurement disagreed with design, the docs
+record the correction — see `docs/superpowers/specs/` for the full design trail,
+including an adversarial review that scoped weft to **consuming and certifying**
+USD rather than authoring it. The core runs with zero dependencies; `usd-core`
+unlocks the USD-facing tools. Apache-2.0; contributions welcome.
+
+## Reading
+
+[`docs/index.html`](docs/index.html) is the single-page design brief.
+The rest, in reading order:
+
+| | |
+|---|---|
+| [`docs/01-overview.md`](docs/01-overview.md) | thesis and cross-industry mapping |
+| [`docs/02-architecture.md`](docs/02-architecture.md) | the resolution layer and USD integration points |
+| [`docs/03-versioning.md`](docs/03-versioning.md) | revisions, channels, baselines |
+| [`docs/04-contracts.md`](docs/04-contracts.md) | generators, archetypes, tolerances |
+| [`docs/05-contexts.md`](docs/05-contexts.md) | claims and approval |
+| [`docs/06-storage.md`](docs/06-storage.md) | stores, layout, Merkle hierarchy |
+| [`docs/07-adoption.md`](docs/07-adoption.md) | the rung ladder; comparisons to USD / Omniverse / Fabric |
+| [`docs/09-usd-audit.md`](docs/09-usd-audit.md) | what USD already holds, what is genuinely absent |
+| [`docs/08-open-questions.md`](docs/08-open-questions.md) | what is still undecided |
+| [`docs/10-slices.md`](docs/10-slices.md) | the slice interaction model |
+| [`specs/weftContracts/schema.usda`](specs/weftContracts/schema.usda) | codeless API schemas for the contract archetypes |
+
+The design documents predate the rename and say "JIT-SD" throughout — same
+project.
+
+## Commitments
+
+- Versions are acts of intent; the only mutable thing is a channel pointer.
+- Couple to contracts, not names — prim paths are an output, not a
+  precondition.
+- Identity is metadata, never an address. Time is an index, never an
+  address.
+- Every rung works solo and offline; no rung requires a higher one.

weft_usd-0.1.0/README.md

@@ -0,0 +1,208 @@
+# weft
+
+Pull the thread, not the world.
+
+```sh
+pip install "weft-usd[usd]"            # once published; until then, from a clone:
+pip install -e ".[usd]"                # [usd] pulls usd-core; the core runs dep-free
+
+weft rels   myscene.usda               # what relationships are in here, natively?
+weft data   myscene.usda               # the whole stage as a table, nothing loaded
+weft pull  'material:…' --context myscene.usda --follow material:binding:full
+```
+
+Opening a USD stage means loading everything and drilling down. weft
+inverts that: stand at any point — a name, an identity, an attribute, a
+place — and pull the threads you care about. A thread is any relationship:
+a material binding, a mount contract, `electrical:feeds`, or a kind your
+team defines. Hierarchy is just one thread on the spool.
+
+```
+$ weft pull 'where:finish=translucent' --context lab.usda --mask-out pull.mask
+$ usdrecord --mask "$(tr '\n' ',' < pull.mask)" lab.usda out.png
+```
+
+Twenty-six pieces of glassware render, floating at their exact production
+transforms, from a scene that was never loaded. No path appeared in the
+question. Run as written against [Animal Logic's
+ALab](https://dpel.aswf.io/alab/) — real production geometry, not a
+fixture — in [`examples/alab/README.md`](examples/alab/README.md#pulling-at-prim-level).
+
+## Addresses
+
+```
+weft pull id:hero-car                        # identity — no path, survives restructures
+weft pull id:occ:weld-47                     # one placement, restructure-proof
+weft pull role:propSocket                    # by contract role
+weft pull 'where:finish=translucent'         # by attribute
+weft pull 'near:id:rack-R42,5'               # within 5 units of a thing, by name
+weft pull bottle01 --follow up:electrical:feeds*8   # trace upstream, 8 hops
+weft pull path:/root/shelf01/bottle_0004     # location — the fallback, not the default
+```
+
+Three rules keep pulls trustworthy:
+
+- **What you didn't pull is declared, never silently absent** — every
+  boundary is counted by kind, and omissions are classed *inert* (a grey
+  material) or *meaning-changing* (a physics joint that would silently
+  re-anchor to the world).
+- **Every answer carries a receipt** — seeds, follow rules, cost, and a
+  digest; a pull is verifiable by recompute-and-compare.
+- **Compatibility is measured, not asserted** — a republish is checked
+  against every consumer's own declared tolerance, not just the provider's
+  promise.
+
+## USD as data
+
+Point weft at a stage you didn't build and *see it as data* — no authoring, no
+schema changes, no load:
+
+```
+weft rels  shot.usda            # the native relationship kinds, with counts
+weft data  shot.usda            # prims x columns: type, bbox, centroid, ...
+weft data  shot.usda --select 'where:bbox_volume>1e6' --load \
+                     --columns point_count,poly_count,byte_cost
+```
+
+Most of that data is **derived, not authored** — weft reads what USD already
+encodes: hierarchy, `UsdCollectionAPI`, and material bindings resolved per
+*purpose* (`full`/`preview`) and inheritance. On ALab that surfaces ~13,600
+material relationships and 114 collections for free. Relationships authored
+anywhere — a native `rel electrical:feeds`, a `UsdPhysics` joint, your team's
+own — are followed (`--follow`), sliced, and certified with **no declaration**;
+weft consumes what your DCC authored rather than asking you to author again. A
+`weft__kinds` block is an optional annotation (a lens, an omission class), not a
+place relationships get made.
+
+## Runs on any USD file, today
+
+No server, no schema changes, no buy-in:
+
+```
+$ weft pull 'chemistry_bottle01*' --context shot.usda --follow Mount
+$ weft who 'name:glass' --context shot.usda    # what depends on this prim?
+$ python -m deps breaks ./assets hub.usda       # what breaks if I republish?
+$ python -m absent shot.usda                    # what silently resolves to nothing?
+```
+
+`deps` sees edges no stock USD API reports (bindings, connections, class
+arcs) and answers the reverse question USD can't. `absent` finds the
+silences USD ships with — stale overrides, bindings to deactivated
+materials — that none of its 28 validators catch.
+
+## usdview plugin
+
+The same `pull`/`who` reasoning, live in the viewer: a "Weft" menu adds
+**Ask…** (resolve a seed against the open stage and select the results),
+**Solo threads** (pull the current selection's threads and deactivate
+everything outside the mask — a *view solo*, not a population mask), **Restore
+world** (undo it), and **Who depends on this?** (incoming edges onto the
+selection, browsable by depth). A docked receipt panel shows the last pull's
+resolutions, members, and boundary, with buttons to copy the member mask or
+save a full manifest.
+
+```
+$ export PXR_PLUGINPATH_NAME=/path/to/weft/extras/usdview:$PXR_PLUGINPATH_NAME
+$ export PYTHONPATH=/path/to/weft/extras/usdview:/path/to/weft:$PYTHONPATH
+$ usdview shot.usda
+```
+
+Both `PXR_PLUGINPATH_NAME` (so libplug finds `extras/usdview/plugInfo.json`)
+and `PYTHONPATH` (so `import weftViewer` — its declared module name —
+resolves) need `extras/usdview` itself, since the plugin's `__init__.py`
+lives one level inside it, in `extras/usdview/weftViewer/`; `PYTHONPATH`
+additionally needs the weft repo root, since the plugin imports `weft.ask`
+and `weft.pull` directly against the live stage. Code, not memory: a python
+usdview plugin is loaded with a plain `import <Name>` off `PYTHONPATH`
+(`pxr/base/plug/plugin.cpp`, `PlugPlugin::_Load()`), so `plugInfo.json`'s own
+directory plays no part in the import — only in libplug's discovery of the
+JSON file itself, via `PXR_PLUGINPATH_NAME`
+(`pxr/usdImaging/usdviewq/plugin.py`'s `loadPlugins()`).
+
+## The engine
+
+For teams that want ground truth, not just queries: a content-addressed
+store, immutable revisions, channels, and baselines — with a promotion gate
+that re-evaluates consumers.
+
+Proven on [Animal Logic's ALab](https://dpel.aswf.io/alab/) (437 real
+placements, contracts derived, not hand-written): a shelf moved 0.7 cm
+passes the provider's 1 cm promise and is **refused by 19 consumers** whose
+own tolerances are tighter — each named, with what it tolerates. Seeding one
+bottle with `--follow Mount` pulls 2 assets instead of 165; the other 163
+threads are declared at the boundary.
+
+```
+$ weft save car car.usda -m "first pass"     # immutable, deduped
+$ weft promote car v002 --to approved        # gated: measured compatibility
+$ weft select 'chassis*' --follow Mount      # a slice, priced before loading
+```
+
+Teams share *ways of seeing* as versioned content: rule sets (which threads
+to follow), edge extractors (your soft-reference conventions become real
+edges), and omission classes — the vocabulary is yours; the machinery
+stays fixed.
+
+## Measured
+
+All from real runs, not projections:
+
+- Seeding one bottle pulls 2 assets instead of 165 — the other 163 are
+  declared at the boundary, not silently dropped.
+- The translucent pull's 26-placement mask is asserted byte-identical to a
+  hand-built reference in the acceptance suite.
+- A 0.7 cm republish, inside the provider's own 1 cm promise, is refused by
+  19 consumers — each named, with its own tolerance.
+- 4,296 production layers walked in 1.75 s (23 ms incremental).
+- The whole scene is addressable in ~126 ms without loading it.
+- 25× storage dedup at 64 KiB chunks.
+
+And on ALab opened whole (47,401 composed prims, 14.5 M points), from
+[`docs/superpowers/specs/2026-10-05-alab-benchmarks.md`](docs/superpowers/specs/2026-10-05-alab-benchmarks.md):
+
+- Pulling one asset vs. loading everything: **0.9 % of the prims, 0.25 % of the
+  geometry — ~3× faster, ~2× lighter.** The win scales with slice size and
+  crosses to a loss near ~99 %, exactly where it should.
+- Query the whole scene as a table in **0.15 s, 125 MB, zero geometry loaded.**
+- A repeated pull of an unchanged context is cached: **0.11 s → 0.003 s (~77×).**
+
+## Status
+
+A working prototype, tested against real production USD (365 tests, CI on a
+no-deps "bare" env and a full `usd-core` env), with no outside users yet. The
+design docs came first; where measurement disagreed with design, the docs
+record the correction — see `docs/superpowers/specs/` for the full design trail,
+including an adversarial review that scoped weft to **consuming and certifying**
+USD rather than authoring it. The core runs with zero dependencies; `usd-core`
+unlocks the USD-facing tools. Apache-2.0; contributions welcome.
+
+## Reading
+
+[`docs/index.html`](docs/index.html) is the single-page design brief.
+The rest, in reading order:
+
+| | |
+|---|---|
+| [`docs/01-overview.md`](docs/01-overview.md) | thesis and cross-industry mapping |
+| [`docs/02-architecture.md`](docs/02-architecture.md) | the resolution layer and USD integration points |
+| [`docs/03-versioning.md`](docs/03-versioning.md) | revisions, channels, baselines |
+| [`docs/04-contracts.md`](docs/04-contracts.md) | generators, archetypes, tolerances |
+| [`docs/05-contexts.md`](docs/05-contexts.md) | claims and approval |
+| [`docs/06-storage.md`](docs/06-storage.md) | stores, layout, Merkle hierarchy |
+| [`docs/07-adoption.md`](docs/07-adoption.md) | the rung ladder; comparisons to USD / Omniverse / Fabric |
+| [`docs/09-usd-audit.md`](docs/09-usd-audit.md) | what USD already holds, what is genuinely absent |
+| [`docs/08-open-questions.md`](docs/08-open-questions.md) | what is still undecided |
+| [`docs/10-slices.md`](docs/10-slices.md) | the slice interaction model |
+| [`specs/weftContracts/schema.usda`](specs/weftContracts/schema.usda) | codeless API schemas for the contract archetypes |
+
+The design documents predate the rename and say "JIT-SD" throughout — same
+project.
+
+## Commitments
+
+- Versions are acts of intent; the only mutable thing is a channel pointer.
+- Couple to contracts, not names — prim paths are an output, not a
+  precondition.
+- Identity is metadata, never an address. Time is an index, never an
+  address.
+- Every rung works solo and offline; no rung requires a higher one.

weft_usd-0.1.0/absent/__init__.py

@@ -0,0 +1,22 @@
+"""absent -- find what a USD stage refers to that is no longer there.
+
+USD can tell you what is in a scene. This tells you what isn't, and why.
+"""
+
+from .detect import (  # noqa: F401
+    ANCHOR_KEY,
+    AUTHORED_AGAINST_KEY,
+    DEAD,
+    MOVED,
+    UNKNOWN,
+    Finding,
+    Report,
+    anchor_index,
+    scan,
+    scan_file,
+)
+
+__all__ = [
+    "ANCHOR_KEY", "AUTHORED_AGAINST_KEY", "DEAD", "MOVED", "UNKNOWN",
+    "Finding", "Report", "anchor_index", "scan", "scan_file",
+]