Backfill postprocessing reference provenance
This commit is contained in:
axiomlogicnexus
parent
e0563aac96
commit
64e4bd4262
3 changed files with 122 additions and 3 deletions
|
|
@ -400,14 +400,16 @@ taxonomy, and leaderboard/report reference side is now explicit too, and the
|
|||
too, and the `pmndrs/react-three-fiber` React renderer and event-bridge
|
||||
reference side is now explicit too, and the `pmndrs/xr` XR session and
|
||||
immersive-interaction reference side is now explicit too, and the
|
||||
`pmndrs/uikit` world-anchored spatial UI reference side is now explicit too.
|
||||
`pmndrs/uikit` world-anchored spatial UI reference side is now explicit too,
|
||||
and the `pmndrs/postprocessing` browser post-processing and effect-boundary
|
||||
reference side is now explicit too.
|
||||
|
||||
The next clean bounded move is a source-backed pass on the remaining
|
||||
repo-backed reference-incorporation families whose hierarchy or canon
|
||||
follow-through is still only implicit in
|
||||
`hypertwist-reference-incorporation-targets.json`, starting with
|
||||
`pmndrs/postprocessing` if you want the adjacent browser post-processing and
|
||||
effect-boundary reference side closed to the same standard.
|
||||
`pmndrs/drei` if you want the adjacent helper-stack and utility reference side
|
||||
closed to the same standard.
|
||||
|
||||
For the readable all-rows follow-up board that pairs this audit with the reset schedule, use:
|
||||
|
||||
|
|
|
|||
|
|
@ -0,0 +1,116 @@
|
|||
# HyperTwist postprocessing Reference Incorporation Provenance Board - 2026-05-27
|
||||
|
||||
## Status
|
||||
|
||||
This document is the source-backed provenance and hierarchy note for the live
|
||||
repo-backed reference-incorporation side currently materialized from
|
||||
`pmndrs/postprocessing`.
|
||||
|
||||
It closes the source-specific reference side that remained implicit after the
|
||||
landed `Phase 3R-F` packet and the broader live-lane audit.
|
||||
|
||||
It answers one narrow question:
|
||||
|
||||
- does the live `pmndrs/postprocessing` reference target reopen already landed
|
||||
first-party browser post-processing and effect-boundary implementation, or
|
||||
does it instead need a reference-side provenance-board and canon backfill
|
||||
|
||||
Result:
|
||||
|
||||
- no product-code reopening is required
|
||||
- yes reference-side provenance-board and feature-canon backfill is required
|
||||
|
||||
## Source basis
|
||||
|
||||
- `C:\HyperTwist\docs\HT_REPO_INCORPORATION_AUDIT_2026-05-11.md`
|
||||
- `C:\HyperTwist\docs\HYPERTWIST_PHASE_3R_PACKET_3R_F_BROWSER_SPATIAL_SUPPORT_IMPLEMENTATION_2026-05-13.md`
|
||||
- `C:\HyperTwist\docs\HYPERTWIST_LIVE_LANES_SOURCE_AND_PRESERVATION_AUDIT_2026-05-13.md`
|
||||
- `C:\HyperTwist\docs\REPO_LICENSE_TRACKING.md`
|
||||
- `C:\HyperTwist\docs\v6_5_deep_manual_pack\HyperTwist\FEATURE_REGISTRY.md`
|
||||
- `C:\HyperTwist\UnrealHyperTwist\Content\HyperTwistTraining\MaterializedCatalog\hypertwist-reference-incorporation-targets.json`
|
||||
- `C:\HyperTwist\UnrealHyperTwist\Content\HyperTwistTraining\MaterializedCatalog\raw-extracts\browser-spatial-support-reference-pages.jsonl`
|
||||
|
||||
## Counts confirmed from current first-party materialization
|
||||
|
||||
Current live `pmndrs/postprocessing` reference-incorporation targets:
|
||||
|
||||
- `1` total rewritten reference target
|
||||
- that target is under `Browser 3D and XR Support`
|
||||
- it stays inside the already-landed `Phase 3R-F` bounded lane
|
||||
|
||||
Exact surface:
|
||||
|
||||
1. `reference/browser-spatial-effect-reference-page-boundary`
|
||||
- `SurfaceType`: `browser-spatial-effect-reference`
|
||||
- `IncorporationChannel`: `browser-spatial-effect-boundary`
|
||||
- `TargetAssetFamily`: `effect-boundary-note`
|
||||
|
||||
Important adjacent fact:
|
||||
|
||||
- this target preserves effect-composer lifecycle, pass ordering and grouping,
|
||||
depth/normal-pass orchestration, and render-priority driven effect routing
|
||||
semantics already enforced by the landed lane
|
||||
- it stays subordinate to the broader landed browser spatial owner trio and
|
||||
does not absorb the adjacent `drei` helper-stack or `uikit` spatial-UI
|
||||
reference slices
|
||||
|
||||
## Slice-local verdict
|
||||
|
||||
| Slice | Primary authority | Secondary value kept | Result |
|
||||
|---|---|---|---|
|
||||
| First-party browser post-processing and effect-boundary implementation | first-party current code plus landed `Phase 3R-F` packet | retained `pmndrs/postprocessing` reference target stays a subordinate provenance-grounding surface | unchanged live implementation owner |
|
||||
| Rewritten effect-composer and effect-boundary grounding | `pmndrs/postprocessing` retained permissive lane | factual composer lifecycle, pass ordering, orchestration, and render-priority semantics are preserved while prose remains first-party | unchanged retained reference-grounding surface beneath first-party contracts |
|
||||
|
||||
## Why no product-code reopening is required
|
||||
|
||||
The live surface here is already a rewritten first-party target, not copied
|
||||
donor effect-gallery wording, donor docs framing, donor demo-shell
|
||||
assumptions, or a silent upstream private fork.
|
||||
|
||||
The checked target explicitly requires:
|
||||
|
||||
- preserving bounded effect-composer, pass-orchestration, and render-priority
|
||||
semantics
|
||||
- rewriting donor effect-gallery wording, donor docs framing, and donor
|
||||
demo-shell assumptions
|
||||
|
||||
That means the retained surface is provenance and factual grounding, not donor
|
||||
browser-shell ownership.
|
||||
|
||||
So this pass does not reopen:
|
||||
|
||||
- the closed `Phase 3R-F` first-party browser spatial lane
|
||||
- the adjacent `pmndrs/drei` helper-stack slice
|
||||
- the adjacent `pmndrs/uikit` spatial-UI slice
|
||||
- any broader browser app-shell or effect-demo ownership posture
|
||||
|
||||
## Current exact grounded role
|
||||
|
||||
`pmndrs/postprocessing` currently grounds one live rewritten first-party
|
||||
contract/reference target for `Browser 3D and XR Support`:
|
||||
|
||||
- browser post-processing and effect boundary
|
||||
|
||||
This target preserves bounded browser effect semantics while keeping all
|
||||
surfaced prose and shell framing first-party.
|
||||
|
||||
## Backfill result
|
||||
|
||||
### Earlier incorporation audit reopened
|
||||
|
||||
- `C:\HyperTwist\docs\HT_REPO_INCORPORATION_AUDIT_2026-05-11.md`
|
||||
|
||||
### Feature canon reopened
|
||||
|
||||
- `C:\HyperTwist\docs\v6_5_deep_manual_pack\HyperTwist\FEATURE_REGISTRY.md`
|
||||
|
||||
## Final call
|
||||
|
||||
The live `pmndrs/postprocessing` reference-incorporation side is now explicit:
|
||||
|
||||
- `1` rewritten first-party contract/reference target
|
||||
- it remains inside the landed `Phase 3R-F` browser spatial lane
|
||||
- effect-composer, pass-ordering, and render-priority grounding stay explicit
|
||||
|
||||
This closes the `pmndrs/postprocessing` reference side without reopening
|
||||
product code.
|
||||
|
|
@ -143,6 +143,7 @@ Do not collapse those three tiers into one undifferentiated "features" voice.
|
|||
| Rewritten React-side browser renderer and event-bridge grounding | Implemented now | `pmndrs/react-three-fiber` retained permissive lane + first-party current code | Current live `Browser 3D and XR Support` reference side includes one rewritten first-party target grounded in retained `react-three-fiber`: the React scene renderer and event bridge. This does not displace the landed `Phase 3R-F` first-party browser spatial owner trio or absorb the adjacent `three.js` scene substrate and `xr` session slices. |
|
||||
| Rewritten browser XR session and immersive-interaction grounding | Implemented now | `pmndrs/xr` retained permissive lane + first-party current code | Current live `Browser 3D and XR Support` reference side includes one rewritten first-party target grounded in retained `pmndrs/xr`: the browser XR session and immersive interaction contract. This does not displace the landed `Phase 3R-F` first-party browser spatial owner trio or absorb the adjacent `three.js` scene substrate and `react-three-fiber` renderer-bridge slices. |
|
||||
| Rewritten world-anchored spatial UI grounding | Implemented now | `pmndrs/uikit` retained permissive lane + first-party current code | Current live `Browser 3D and XR Support` reference side includes one rewritten first-party target grounded in retained `pmndrs/uikit`: browser spatial UI and world-anchored controls. This does not displace the landed `Phase 3R-F` first-party browser spatial owner trio or absorb the adjacent `postprocessing` effect-boundary and `drei` helper-stack slices. |
|
||||
| Rewritten browser post-processing and effect-boundary grounding | Implemented now | `pmndrs/postprocessing` retained permissive lane + first-party current code | Current live `Browser 3D and XR Support` reference side includes one rewritten first-party target grounded in retained `pmndrs/postprocessing`: the browser post-processing and effect boundary. This does not displace the landed `Phase 3R-F` first-party browser spatial owner trio or absorb the adjacent `drei` helper-stack and `uikit` spatial-UI slices. |
|
||||
|
||||
## Feature families
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue