frontend-patterns/workplans/FEP-WP-0010-reference-consumption.md

---
id: FEP-WP-0010
type: workplan
title: "Close local reference-consumption gaps"
domain: infotech
repo: frontend-patterns
status: finished
owner: codex
topic_slug: canon
created: "2026-10-04"
updated: "2026-10-04"
state_hub_workstream_id: "c46b02ca-26a8-5313-b0f2-eb0385ff820c"
---

# Close local reference-consumption gaps

Requested in the October 4 scope-versus-intent review. Reviewed against `07f1f37`,
the immutable 0.1 validator/export and activity-core's schema-v1 consumer event
contract. [Assessment](../history/2026-10-04T084941+0200-scope-vs-intent.md) ranks the
remaining gaps. This plan implements a finite local consumption bridge; it does not
claim real usefulness, independent validation, canonical export or autonomous operation.

## Reconcile actual capabilities and ranked gaps

```task
id: FEP-WP-0010-T01
status: done
priority: high
state_hub_task_id: "e2a595b9-2a46-59e1-96a0-58793968c011"
```

Update SCOPE.md from actual artifacts and record a timestamped assessment against
INTENT. Distinguish 18 live hypotheses from the frozen 17-record preview, developed
core paths from stubs, reporting from improvement and development checks from
independent/held-out evidence. Name existing owners for the most relevant gaps.

## Implement verified pinned lookup and citation

```task
id: FEP-WP-0010-T02
status: done
priority: high
state_hub_task_id: "52e73505-dadc-52b9-aedb-4ba0889e580c"
```

Add a small stdlib CLI to filter the verified candidate preview by explicit IDs,
improving forces and responsibilities. Carry force costs, evidence limits and
conditional relations without inferring compatibility or applicability. Empty or
unknown constraints must clarify/abstain honestly. Provide commit-specific corpus
and packaging locators; never silently read moving candidate prose. Reuse the existing
release validation and fail on tampering or unavailable pins.

## Prepare immutable consumer closeout receipts

```task
id: FEP-WP-0010-T03
status: done
priority: high
state_hub_task_id: "08762144-141e-5f13-ab58-2054da04a221"
```

Accept an explicit consumer decision/provenance input and prepare a schema-v1 event
with verified release pins, considered/selected IDs, unchanged unknown outcomes and
exact file digest/index entry. Write new files exclusively; refuse overwrite and unsafe
source-relative paths. Validate inputs before writes. Real versus synthetic is explicit;
no consumer enrollment, fabricated real outcome, arbitrary feedback execution or
producer claim of verified collector origin. Match activity-core's existing event
contract instead of creating a second collection service.

## Verify the bridge and hand remaining gaps to live owners

```task
id: FEP-WP-0010-T04
status: done
priority: high
state_hub_task_id: "7efb810a-d6f8-540c-90a5-3c333e0bdbea"
```

Run disclosed synthetic lookup/citation/receipt cases, including unsupported/no-match,
missing context, unknown IDs, changed live research, tampered release, invalid provenance,
selection/action mismatch, delayed follow-up and duplicate writes. Verify generated
receipts with the actual activity-core validator and document exact owner revision.
Provide consumer commands in existing entry points. No model call or production
mutation is required. Run repository checks and record limitations.

Before finishing, link delivered bridge and residual acceptance to existing WP-0008
T01/T02 (real consumer/template/enrollment/outcomes), WP-0009 (human/fresh validation),
WP-0003/0004 (broader/gated applicability) and WP-0006 (comparable windows). Add live
record references there. This plan may finish its local deliverable while the empirical
owners remain open; do not claim those gaps closed or leave actionable residuals only
in prose/history.

## Completion — 2026-10-04

The local consume → cite → prepare-receipt bridge is delivered. `reference_consume.py`
verifies the immutable preview before filtering or receipt preparation; results carry
corpus/packaging pins, force costs, proposed relation conditions and explicit limits.
Input validation precedes exclusive source-relative writes; returned digests identify
the exact JSON/YAML bytes. The consumer retains its own decision and evidence authority.

Validation: 104 tests pass with zero skips (31 consumption, 2 schema, 33 bench/admission,
22 evolution, 16 preview), including actual activity-core validator acceptance at
`3dd68d1`. Synthetic bench planning and evolution/classification/reference checks pass.
[Verification record](../docs/evidence/2026-10-04-reference-consumption.json) preserves
owner hash and boundaries. No paid inference, production mutation, enrolled consumer,
new empirical learning cycle, canonical admission or usefulness claim was introduced.

Residual acceptance was handed to the existing live WP-0008 T01/T02 descriptions
before finish: actual hosted/template/consumer decision integration, hook invocation,
index/enrollment, real use plus outcome and delayed refresh. WP-0009 retains independent
human/fresh replication/M1; WP-0003/0004 retains contrasting/gated applicability;
WP-0006 retains useful comparable returns evidence. Those existing obligations are not
new duplicate tasks and are not closed by the bridge's disclosed development cases.
Scope/assessment and capability guidance now describe this separation accurately.

State Hub implementation decision: `6914093c-e540-4d31-a1ea-607021c5e185`; plan UUID
`c46b02ca-26a8-5313-b0f2-eb0385ff820c`. Registration assigned all task UUIDs and verified
the initial pushed plan on primary/railiance01; final source statuses are synced at close.