# HyperTwist screenpipe 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
`screenpipe/screenpipe`.

It closes the source-specific reference side that remained implicit after the
landed `Phase 4R-E` packet and the broader live-lane and license-boundary
audits.

It answers one narrow question:

- do the live `screenpipe/screenpipe` reference targets reopen already landed
  first-party capture-history, replay, vault, and compliance implementation, or
  do they 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_4R_PACKET_4R_E_SCREENPIPE_CAPTURE_HISTORY_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\screenpipe-screenpipe-capture-history-reference-pages.jsonl`

## Counts confirmed from current first-party materialization

Current live `screenpipe/screenpipe` reference-incorporation targets:

- `6` total rewritten reference targets
- all `6` are under `Capture History, Replay, and Vault Support`
- all `6` stay inside the already-landed `Phase 4R-E` bounded lane

Exact surfaces:

1. `reference/screenpipe-event-capture-reference-page`
   - `SurfaceType`: `capture-history-event-capture-reference`
   - `IncorporationChannel`: `event-capture-contract`
   - `TargetAssetFamily`: `capture-event-note`
2. `reference/screenpipe-pipe-permission-reference-page`
   - `SurfaceType`: `capture-history-permission-reference`
   - `IncorporationChannel`: `pipe-permission-contract`
   - `TargetAssetFamily`: `permission-boundary-note`
3. `reference/screenpipe-persistence-reference-page`
   - `SurfaceType`: `capture-history-persistence-reference`
   - `IncorporationChannel`: `capture-persistence-contract`
   - `TargetAssetFamily`: `capture-persistence-note`
4. `reference/screenpipe-vault-reference-page`
   - `SurfaceType`: `capture-history-vault-reference`
   - `IncorporationChannel`: `vault-lifecycle-contract`
   - `TargetAssetFamily`: `vault-lifecycle-note`
5. `reference/screenpipe-timeline-review-reference-page`
   - `SurfaceType`: `capture-history-timeline-reference`
   - `IncorporationChannel`: `timeline-review-contract`
   - `TargetAssetFamily`: `timeline-review-note`
6. `reference/screenpipe-compliance-boundary-reference-page`
   - `SurfaceType`: `capture-history-compliance-boundary-reference`
   - `IncorporationChannel`: `compliance-boundary`
   - `TargetAssetFamily`: `compliance-boundary-note`

Important adjacent fact:

- all six targets preserve the explicit `MIT OR Apache-2.0` core versus
  enterprise `ee/` exclusion boundary already enforced by the landed lane

## Slice-local verdict

| Slice | Primary authority | Secondary value kept | Result |
|---|---|---|---|
| First-party capture-history, replay, vault, and compliance implementation | first-party current code plus landed `Phase 4R-E` packet | retained `screenpipe/screenpipe` reference targets stay subordinate provenance-grounding surfaces | unchanged live implementation owner |
| Rewritten event-capture, permission, persistence, vault, and timeline-review grounding | `screenpipe/screenpipe` retained boundary-sensitive lane | factual trigger, gating, write-queue, lifecycle, and replay-review semantics are preserved while prose remains first-party | unchanged retained reference-grounding surface beneath first-party contracts |
| Mixed-license and enterprise-subtree compliance boundary grounding | `screenpipe/screenpipe` retained boundary-sensitive lane | the permissive-core versus `ee/` exclusion boundary stays explicit in a first-party compliance note | unchanged bounded compliance-grounding surface |

## Why no product-code reopening is required

The live surfaces here are already rewritten first-party targets, not copied
donor pages or donor shell UI.

The checked targets explicitly require:

- preserving factual event-capture, permission, persistence, vault, timeline,
  and compliance semantics
- rewriting donor wording, donor product-shell framing, and any broader
  surveillance, platform, or cloud assumptions

That means the retained surfaces are provenance and factual grounding, not
donor shell ownership.

So this pass does not reopen:

- the closed `Phase 4R-E` first-party capture-history lane
- the first-party replay shell or broader training runtime
- any donor `ee/` subtree usage
- any broad screenpipe product-shell adoption

## Current exact grounded role

`screenpipe/screenpipe` currently grounds six live rewritten first-party
contract/reference targets for `Capture History, Replay, and Vault Support`:

- event-driven capture and trigger routing
- pipe permission and backpressure boundaries
- write queue, retention, and sleep-aware persistence
- vault lock, unlock, and migration lifecycle
- rewind timeline grouping and review posture
- permissive-core versus `ee/` compliance boundary

These targets preserve bounded factual capture-history semantics while keeping
all surfaced prose and product 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 `screenpipe/screenpipe` reference-incorporation side is now explicit:

- `6` rewritten first-party contract/reference targets
- all `6` remain inside the landed `Phase 4R-E` capture-history lane
- the permissive-core versus enterprise-`ee/` boundary stays explicit

This closes the `screenpipe/screenpipe` reference side without reopening
product code.
