Labyricorn/XZBT
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

test: record Phase 0 feasibility probe and manual evidence

Browse Source
This commit is contained in:
Labyricorn
2026-09-04 20:31:56 -07:00
parent 05fe2b4e02
commit 7b2e486095
27 changed files with 2036 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/XZBT_0-1_Gap_Closure_Decisions.md
+4 -2
View File
@@ -1,7 +1,7 @@
# XZBT 0.1 Gap Closure Decisions
**Record version:** 0.1
**Status:** Incorporated into the planning baseline; implementation verification pending
**Record version:** 0.1\
**Status:** Incorporated into the planning baseline; implementation verification pending\
**Related resources:** [PRD](../XZBT_0-1_MVP_Product_Requirements_Document.md), [format specification](XZBT_0-1_Format_Specification.md), [verification gates](XZBT_0-1_Verification_Gates.md)
Numbering preserves the seven gaps discussed during PRD preparation. Recording a decision closes a design question; it does not establish that a browser feature, performance target, or lifecycle guarantee has passed testing.
@@ -28,6 +28,8 @@ Moving or renaming the HTML is a separate compatibility case. Do not promise tha
**Gate:** GC1 in the verification checklist. A failure of direct-file persistence in the chosen supported environment reopens the deployment decision; do not silently replace the distribution promise with hosted-only operation.
**Verified packaging refinement:** The [version 3 manual probe](evidence/phase0/2026-09-04-user-run-v3.md) loads and connects the engine-owned worklet from an embedded data URL in direct-file Chrome 152; the earlier Blob URL approach failed in the same user's testing. Use the verified data-URL approach for this packaging path, with an explicit page script-source allowlist and network connections disabled. This does not permit exhibit-authored executable code or declare the remaining GC1 checks complete.
**Basis:** [MDN file-origin behavior](https://developer.mozilla.org/en-US/docs/Web/Security/Defenses/Same-origin_policy#file_origins), [Chrome File System Access API](https://developer.chrome.com/docs/capabilities/web-apis/file-system-access), and [AudioWorklet requirements](https://developer.mozilla.org/en-US/docs/Web/API/AudioWorklet). These describe platform constraints, not evidence that the XZBT prototype has passed.
## 2. One authoritative format specification