# Bounded evidence package research

Status: curated research record, 26 September 2026. This page helps readers
find the supplied 19 September work. It does not adopt a bounded evidence
package (BEP) standard, change Ask OKF, establish source authority or provide
DWP entitlement guidance. The separate [implementation status](bep-implementation-status.md)
compares these proposals with the code and recorded checks at a named revision.

## Start with the research

- [Original research handover](../research/bep-research-2026-09-19/00_START_HERE.md)
  states the two tasks, their baseline and unresolved questions. Its
  [source register](../research/bep-research-2026-09-19/SOURCES.md) and
  [handover manifest](../research/bep-research-2026-09-19/MANIFEST.json)
  identify the starting material.
- [Research A report](../research/bep-research-2026-09-19/outputs/Deep%20Research%20Report_%20Ask%20OKF,%20Bounded%20Evidence%20Packages,%20and%20DWP%20Imprisonment_Hospital%20Guidance.md)
  discusses the proposed evidence contract and DWP imprisonment and hospital
  scope. Its platform citation tokens may not resolve in this static copy;
  consult the source register and recheck material claims before reuse.
- [Research B report](../research/bep-research-2026-09-19/outputs/Research%20B%20%E2%80%94%20Storage,%20deterministic%20compilation%20and%20efficient%20BEP%20serving.md)
  compares serving and publication designs. It records that the `00_START_HERE`
  attachment was unavailable during that run. Its recommendations are not
  measurements of this project's load or a decision to add DBOS.
- [Reconstructed Research A package](../research/bep_research_A_RECONSTRUCTED_2026-09-19/README.md)
  starts with a delivery audit and the
  [reconstructed analysis](../research/bep_research_A_RECONSTRUCTED_2026-09-19/REPORT.md).
  It is a **new replacement**, not the missing original archive. Its proposed
  `bep-core.v0.1-reconstructed.1` schema, examples and local synthetic checks
  do not establish an OKF standard, real-engine performance or specialist
  approval. Most restored literature references were not rechecked claim by
  claim. The package's own [manifest](../research/bep_research_A_RECONSTRUCTED_2026-09-19/manifest.json)
  and [verification record](../research/bep_research_A_RECONSTRUCTED_2026-09-19/verification.json)
  retain their original scope.

## What was curated

The [curation inventory](../research/bep-curation-inventory.json) lists the
source and copied SHA-256 for each of the 66 retained files. Both supplied
package directories were copied byte for byte from an untracked local Explorer
checkout. Its Git commit identifies the surrounding code, **not** the
untracked research bytes. The first handover manifest covers five starting
files; the curation inventory additionally covers its six report formats and
one manifest. The reconstructed package retains its own 52-file manifest and
checksum index. Narrow Git attributes preserve the supplied line endings, including four CRLF
CSV files; staged Git blobs are checked against the same inventory. Copy and hash checks establish byte custody only. We did not
execute the supplied research scripts, reproduce model work, re-audit external
citations or run a new benchmark.

Each report has one primary Markdown link above. PDF, Word and HTML versions
remain in the package to preserve delivery history. Git retains the Word
files and the reconstructed package’s original HTML. The Site serves its
Markdown-derived reading pages at the HTML routes, avoiding same-name route
collisions. The reconstructed ZIP was left out
because it duplicates all 54 retained directory files byte for byte. macOS
`.DS_Store` files were left out. The original files remain outside this
curated worktree.

The package Markdown is excluded from the small default semantic bundle. This
navigation page is documentation; the retained reports are research for human
review, not runtime evidence or legal assertions.

## Deferred material

Jev-Mem research is **deferred** from this publication. The 24 September
Evidence Workbench WebMCP handover is a historical task prompt with local
checkout and browser-state instructions. It is preserved in the owner’s verified external archive as an archive-only
lead, rather than being presented as a research finding or current
implementation description.