liveframe 0.2.0__tar.gz → 0.3.0__tar.gz

liveframe-0.3.0/.gitignore

@@ -0,0 +1,61 @@
+.DS_Store
+.venv/
+__pycache__/
+*.py[cod]
+.pytest_cache/
+.mypy_cache/
+.ruff_cache/
+dist/
+build/
+*.egg-info/
+release/
+
+# LaTeX build scratch files
+paper/arxiv/*.aux
+paper/arxiv/*.blg
+paper/arxiv/*.log
+paper/arxiv/*.out
+paper/arxiv_submission_runbook.local.md
+
+# Large or machine-local artifacts
+outputs/
+weights/
+checkpoints/
+third_party/
+artifacts/h100-holdout-results/
+artifacts/mlx-holdout-results/
+artifacts/shared-rolling-noise.v1/
+artifacts/taew21-campaign-noise.v1/
+*.pt
+*.pth
+*.safetensors
+*.mp4
+*.mov
+*.mkv
+
+# Runtime state
+.liveframe/
+.claude/settings.local.json
+
+# World-harness run outputs (never committed; evidence bundles go under agent/world/evidence/)
+/runs/
+.hf_token.env
+*.env.local
+.env
+
+# Stray legacy package artifacts (not part of the build)
+liveframe-0.1.0-package.zip
+liveframe-0.1.0-package/
+
+# World evidence: keep small receipts (json/html/jsonl); never the frame payloads (GBs of .npz)
+agent/world/evidence/**/*.npz
+agent/world/evidence/**/frames_*/
+
+# Internal world planning / process notes (not part of the public release)
+/liveframe-world-handoff.md
+/liveframe-world-addendum-flywheel.md
+agent/world/flywheel/
+agent/world/*.md
+
+# Launch / go-to-market drafts (local only)
+publishing/

liveframe-0.3.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 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 [yyyy] [name of copyright owner]
+
+   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.

liveframe-0.3.0/PKG-INFO

@@ -0,0 +1,267 @@
+Metadata-Version: 2.5
+Name: liveframe
+Version: 0.3.0
+Summary: Honest runtime qualification for streaming and interactive video generation.
+Project-URL: Homepage, https://github.com/kkjcodes/liveframe
+Project-URL: Repository, https://github.com/kkjcodes/liveframe
+Project-URL: Issues, https://github.com/kkjcodes/liveframe/issues
+Author: kkjcodes
+License: Apache-2.0
+License-File: LICENSE
+Keywords: benchmark,evaluation,runtime,streaming,video-generation,world-models
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: Intended Audience :: Science/Research
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Topic :: Scientific/Engineering :: Artificial Intelligence
+Classifier: Topic :: Software Development :: Testing
+Requires-Python: >=3.10
+Provides-Extra: cuda
+Requires-Dist: torch>=2.6; extra == 'cuda'
+Provides-Extra: dev
+Requires-Dist: mypy>=1.14; extra == 'dev'
+Requires-Dist: pytest>=8.3; extra == 'dev'
+Requires-Dist: ruff>=0.9; extra == 'dev'
+Provides-Extra: metrics
+Requires-Dist: lpips>=0.1.4; extra == 'metrics'
+Requires-Dist: numpy>=2.0; extra == 'metrics'
+Requires-Dist: pillow>=11.0; extra == 'metrics'
+Requires-Dist: scipy>=1.14; extra == 'metrics'
+Requires-Dist: torch>=2.6; extra == 'metrics'
+Requires-Dist: torchvision>=0.21; extra == 'metrics'
+Requires-Dist: transformers>=5.0; extra == 'metrics'
+Provides-Extra: mlx
+Requires-Dist: mlx>=0.31; (platform_system == 'Darwin') and extra == 'mlx'
+Provides-Extra: world
+Requires-Dist: jsonschema>=4.21; extra == 'world'
+Requires-Dist: numpy>=1.26; extra == 'world'
+Requires-Dist: opencv-python-headless>=4.9; extra == 'world'
+Provides-Extra: world-gpu
+Requires-Dist: jsonschema>=4.21; extra == 'world-gpu'
+Requires-Dist: numpy>=1.26; extra == 'world-gpu'
+Requires-Dist: opencv-python-headless>=4.9; extra == 'world-gpu'
+Requires-Dist: pynvml>=11.5; extra == 'world-gpu'
+Requires-Dist: torch>=2.4; extra == 'world-gpu'
+Provides-Extra: world-quality
+Requires-Dist: jsonschema>=4.21; extra == 'world-quality'
+Requires-Dist: lpips>=0.1.4; extra == 'world-quality'
+Requires-Dist: numpy>=1.26; extra == 'world-quality'
+Requires-Dist: opencv-python-headless>=4.9; extra == 'world-quality'
+Requires-Dist: pynvml>=11.5; extra == 'world-quality'
+Requires-Dist: torch>=2.4; extra == 'world-quality'
+Requires-Dist: transformers>=5.0; extra == 'world-quality'
+Description-Content-Type: text/markdown
+
+# LiveFrame
+
+LiveFrame helps engineers determine whether a streaming video-generation system works for a real
+workload, understand why it fails, and verify that an optimization improves complete-wall
+performance without silently weakening quality or deployment eligibility. The active product
+mission is documented in [agent/liveframe_product_mission.md](agent/liveframe_product_mission.md).
+
+## LiveFrame World: runtime truth for interactive world models
+
+Point the harness at an action-conditioned world model and get a verified
+runtime + control + stability report — one command, one GPU, minutes:
+
+```bash
+# From a source checkout:
+pip install -e ".[world]"
+# (PyPI: `pip install "liveframe[world]"` once 0.3.0 is published.)
+
+# Prove the loop end to end on CPU first (~seconds):
+liveframe world run synthetic --suite smoke
+
+# Bring your own model: any FILE.py:ClassName implementing the adapter
+# protocol, in-process. pip users write their own file (see QUICKSTART.md for a
+# complete paste-and-run adapter); source checkouts can start from the template
+# in examples/byo_adapter/drift_world.py. Declare every action the suites
+# command (W S A D L R U N 0) or the case fails with a clear contract error.
+liveframe world run my_world.py:MyWorld --suite quick
+
+# Same adapter file, running inside your model's own environment:
+liveframe world run my_model.py:MyWorld --suite quick \
+    --python /path/to/model-env/bin/python
+
+# Matrix-Game 2.0 reference adapter (weights + checkout required; run
+# `liveframe world doctor matrix-game-2 --python ...` first — every failed
+# check prints its exact fix):
+liveframe world run matrix-game-2 --suite quick --python /opt/envs/mg2/bin/python
+```
+
+Each run writes a self-contained `report.html` (no scripts, no network), a
+machine-readable `report.json`, and a digest-bound ledger; the command prints
+the `report.html` path when it finishes, and
+`liveframe world verify <run>/ledger.json` re-checks every artifact byte.
+(`smoke` and `quick` are deliberately short, so `realtime_pass` reports `null`
+— the real-time rule needs a continuous 60-second stream; use `soak` for it.)
+Generated FPS counts decoded native frames only — interpolated or duplicated
+frames never count, cold start is reported as context rather than blended into
+generation numbers, and vendor claims are compared with neutral verdicts
+(`different configuration` when the claim names a setup, else `config not
+stated`) — the builder never says "reproduced". Suites: `smoke`,
+`quick`, `standard`, `soak`, `memory` (`liveframe world suites`). Also:
+`world compare A B` (config differences listed before any numbers) and
+`world export --format worldmark|wbench|raw` for interop with quality-focused
+benchmarks. Start at [QUICKSTART.md](QUICKSTART.md) for a step-by-step guide —
+install, a paste-and-run adapter, reading the report, and verifying the ledger —
+or the template in [examples/byo_adapter/](examples/byo_adapter/).
+
+### Measured references (with receipts)
+
+We ran four published interactive world models through the harness, each in a
+stated configuration, every number backed by a re-verifiable ledger. The headline
+isn't "these models are slow" — it's that published frame rates are hard to
+reproduce from what's shipped. When a claim is fully specified and we run that
+exact config (Matrix-Game 2.0), it reproduces; otherwise we show which condition
+differs (a different GPU, a proprietary engine vs the open weights, or a streaming
+mode that isn't the released code).
+
+| Model | Claim (as published) | Measured | Why they differ (stated conditions) |
+|---|---|---|---|
+| Matrix-Game 2.0 | 25 fps (1× H100) | **19.7 fps** | same H100, same steps — **reproduces** |
+| ABot-World-0 | 16 fps (720p, 1× RTX 5090) | **5.85 fps** | same RTX 5090; remaining gap = their optional fp8/sage stack off (not pip-installable) + the interactive delivery path. (A100 reference: 3.70) |
+| Oasis-500M | 20 fps (Decart's proprietary engine) | **1.06 fps** | we measured the open 500M weights vanilla (1× A100 PCIe) — a different artifact than the engine behind the claim |
+| HY-World 1.5 | 24 fps (streaming; GPU/steps unstated) | **1.36 fps** | released pipeline runs batch, not streaming — not directly comparable |
+
+**None of these results contradict a vendor's claim.** The one claim that is fully
+specified and matched (Matrix-Game 2.0) reproduces; the other three can't be tested
+as published from what's shipped — a different GPU class, a proprietary serving
+engine, or a mode not in the released code. That reproducibility gap, stated
+precisely, is the finding.
+
+It times frames as they are delivered (so it errs low, never inflates) and counts
+native decoded frames only. We run the released pipeline with conservative settings
+(optional fp8/attention/compile off — for ABot this includes stubbing its optional
+fp8 kernel, unused at our settings), so these are floors, not each model's best.
+The Oasis adapter decodes every frame as it is generated (the interactive cost);
+the upstream script batch-decodes at the end. Every number reproduces from a
+digest-bound ledger (`liveframe world verify`). Matrix-Game 3.0's claim is 9 GPUs
+(8 DiT + 1 VAE) — more than a single node — so its cluster figure is pending; its
+single-GPU number is 2.04 fps.
+
+LiveFrame defines **real-time** as at least **16 native generated frames per second for a continuous 60-second stream**, with time-to-first-frame, p95 chunk latency, thermal state, memory, intrinsic quality, same-seed identity, and long-horizon drift disclosed. Interpolated or duplicated presentation frames never count as generated FPS.
+
+The strongest clean Apple result in this repository is **1.418 native generated FPS**, measured on an Apple M5 Max with MLX/MLX Metal 0.32.0, Wan2.1-T2V-1.3B Causal-Forcing++ one-step generation, and 480x832 output over an 81-frame fixture. It is **11.28x short of 16 FPS** and is not a 60-second sustained-streaming result.
+
+That miss is the headline, not a footnote. LiveFrame's contribution is an evidence-first methodology, one exact-output systems speedup, and three scoped negative results that prevented broader false claims.
+
+## Results
+
+| Result | Measurement | Scope |
+| --- | --- | --- |
+| M5 allocator optimization | 69.167s to 57.127s complete wall; 1.171 to 1.418 FPS; `1.2108x` speedup | Apple M5 Max, MLX 0.32.0, one-step CF++, 480x832, 81 frames |
+| Cross-runtime AR divergence | pairwise identity passed 0/128 videos and 0/32 prompt-horizon cells | Frozen Rolling Forcing checkpoint, byte-identical CUDA/MLX stochastic inputs, 15s and 60s |
+| M5 target gap | 1.418 FPS, 11.28x below the 16 FPS threshold | Clean short fixture, not a hardware impossibility or sustained claim |
+| Periodic refresh reuse | 0/16 quality cells; temporal identity failed 64/64 videos | H100 numerical campaign, two high-redundancy strata, 15s and 60s |
+
+The M5 speedup came from increasing the bounded MLX free-buffer cache from 1 GiB to 4 GiB before model loading. All measured trials reported the same pre-encode raw RGB digest and zero swap. The original 97 MB raw RGB payload was not retained; the immutable benchmark artifact records the repeated digest, while the shipped H.264 file and its decoded RGB have separate hashes. See [the ledger audit](agent/liveframe_ledger_audit.md).
+
+The 60-second M5 holdout campaign measured 0.185 FPS median, but concurrent memory pressure and sustained swap make that timing ineligible as the clean headline denominator. Its quality and identity evidence remains valid because output bytes were unaffected by timing contamination.
+
+## What Failed, Precisely
+
+### 1. Cross-runtime autoregressive reproduction
+
+CUDA and MLX consumed byte-identical serialized BF16 stochastic tensors under the frozen Rolling Forcing schedule. The MLX outputs often remained independently plausible, but they did not preserve the same trajectory:
+
+- Intrinsic quality: 90/128 videos and 19/32 prompt-horizon cells passed.
+- Same-seed identity: 0/128 videos and 0/32 cells passed.
+- Pairwise temporal CLIP identity: 0/128 videos passed.
+
+This rejects the tested checkpoint/runtime pair under the frozen portability contract. It does not establish that every CUDA and MLX video implementation must diverge.
+
+### 2. The tested M5 configuration was not real-time
+
+The clean optimized row is 1.418 native FPS at 480x832. Quantization, lower-resolution tiers, different models, custom Metal kernels, decoder redesign, and disclosed interpolation were not exhausted, so this is a configuration result rather than an Apple Silicon impossibility claim.
+
+### 3. Periodic refresh K/V reuse was not quality-safe
+
+The tested H100 mechanism reused raw normalized K/V from a full-refresh anchor for the next two framewise refreshes after reapplying temporal RoPE. It failed all 16 frozen prompt-horizon cells. No authoritative timing replay was run because numerical quality GO was a prerequisite.
+
+The broader denoise-side Delta Scheduling oracle was **never run**. The research track stopped after the refresh gate by choice. On the frozen H100 denominator, a denoise-only path needed at least 70.3667% denoise reclaim before overhead to reach the 17% complete-wall gate. That is an untested feasibility bar, not a failed oracle.
+
+## Measurement Method
+
+LiveFrame separates four claims that are often conflated:
+
+1. **Numerical trajectory:** cache invariants and latent drift under identical inputs.
+2. **Intrinsic quality:** prompt alignment, motion, flicker, and temporal behavior against prompt-specific teacher distributions.
+3. **Same-seed identity:** whether reference and candidate remain recognizably the same generated video.
+4. **Complete-wall performance:** end-to-end timing including denoise, mandatory refresh, VAE, materialization, synchronization, and encoding.
+
+The evidence system includes:
+
+- Pre-registered prompts, seeds, content strata, 15-second and 60-second horizons, thresholds, and aggregation.
+- Serialized stochastic tensors with literal cross-runtime byte checks.
+- Digest-bound checkpoints, source revisions, metric weights, runtimes, and outputs.
+- Independent numerical and timing eligibility.
+- Component-resolved timing and zero-swap checks.
+- Atomic publication and fail-closed complete-campaign validation.
+- Proof-blind H100 allocation testing before prospective result visibility.
+
+The machine-readable claim surface is [artifacts/liveframe-publication-claims.v1.json](artifacts/liveframe-publication-claims.v1.json). The publication plan and limitations are in [agent/liveframe_publication_package.md](agent/liveframe_publication_package.md).
+
+## Evidence Release
+
+Evidence is split by cost and reproducibility:
+
+- **Compact release:** schemas, manifests, metric JSON, decision artifacts, and reports.
+- **Representative previews:** 64 CUDA/MLX pairs selected using the protocol's pre-registered seed ranks 0 and 2 at both horizons.
+- **Cold archive:** complete raw pixel, latent, stochastic, and refresh campaign corpora.
+
+The SHA-bound extraction manifest is [artifacts/liveframe-publication-release-tiers.v1.json](artifacts/liveframe-publication-release-tiers.v1.json). Generated release payloads are staged under ignored `release/` storage rather than committed to Git.
+
+## Reproduction Boundary
+
+LiveFrame source is Apache-2.0. Upstream Causal-Forcing source, Causal-Forcing checkpoints, Wan2.1 weights, and tokenizer weights are not redistributed in this repository. Users acquire pinned assets from their publishers and verify them against [artifacts/upstream.v1.json](artifacts/upstream.v1.json). See [THIRD_PARTY.md](THIRD_PARTY.md) before distributing a reproduction bundle.
+
+The frozen evidence revision is tagged `evidence-freeze-2026-08-06`. That tag resolves to commit `ea742ee2ea438b6d9ff2d1bca0b4053f9eeaeb44` and contains the campaign evidence and initial publication ledger.
+
+## Development
+
+Python 3.11 or newer is required.
+
+```bash
+python -m venv .venv
+source .venv/bin/activate
+python -m pip install -e '.[dev]'
+pytest
+ruff check src/liveframe tests tools
+mypy
+```
+
+Metal-dependent tests require a native macOS session with an accessible Metal device. The VS Code sandbox can run the CPU suite but cannot initialize MLX Metal.
+
+Useful verification commands:
+
+```bash
+liveframe gate verify
+liveframe doctor
+liveframe qualify --backend synthetic --profile interactive-480p \
+	--output artifacts/synthetic-qualification.v1.json
+liveframe qualification verify artifacts/synthetic-qualification.v1.json
+python tools/prepare_publication_release.py --help
+```
+
+The synthetic qualification exercises request construction, native-frame accounting, timing, and
+profile gates without a GPU. Its overall verdict is intentionally `incomplete` until required
+quality, long-horizon, memory, and thermal evidence is attached; passing FPS alone never qualifies
+a deployment.
+
+## Repository Layout
+
+- `src/liveframe/`: runtime-neutral contracts, MLX backend, quality policy, evidence capture, and refresh proof code.
+- `tools/`: pinned benchmark, H100 campaign, and publication extraction tools.
+- `artifacts/`: compact immutable protocols, manifests, measurements, and decisions.
+- `agent/`: standalone reports, runbooks, project state, and publication package.
+- `tests/`: contract, evidence, policy, backend, and publication-ledger tests.
+
+## License
+
+LiveFrame is licensed under Apache-2.0. See [LICENSE](LICENSE) and [THIRD_PARTY.md](THIRD_PARTY.md).