ALLOWLISTED DURABLE SOURCE

001-release-record.md

docs/builds/001-release-record.md

This is the retained record itself—not a chat summary. It is exposed because it materially documents the research, method, evidence, audit, production, planning or release history of The 100.

# Build 001 — Release Record

Status: CERTIFICATION PASS / not final until acceptance matrix closes.

## A — Human Review Design Framework
Engine: 001.1.0. Eight dimensions scored 0/1/2. Composite thresholds and equal weighting are explicitly product heuristics, not requirements imposed by NIST, the EU AI Act, or ICO. Result dimensions now expose source-family basis; full source/section mapping lives in `data/build-001-evidence-v1.json`.

## Technological-ceiling review
Implemented: broad-comprehension quick/deep paths; consequence-aware priority promotion; machine-readable evidence manifest; result-level provenance IDs; interactive B-Web; feed-native B-MP4; deterministic/adversarial test fixtures; input limits.
Evaluated: a more complex rules engine is not currently warranted because 001 has eight transparent deterministic dimensions and no jurisdiction-specific compliance claim. Scenario simulation would materially expand the public job and belongs in later consequence/simulation builds. Export/share is useful but must not precede privacy acceptance; therefore it remains blocking rather than being added casually.

## Evidence classification
Dimension concepts are direct support or cross-source synthesis. Scoring, thresholds, equal weighting and priority ordering are product heuristics. No compliance certification is made.

## B-Web
Interactive control architecture: role, timing, authority, evidence, escalation and recordkeeping become manipulable rather than decorative. Manual accessibility/collision acceptance remains required.

## B-LinkedIn
Silent-first 4:5 film. Story: “human in the loop” → person present but powerless/late → move review before consequence → evidence/timing/authority/escalation/record → final proposition. Canonical file hash belongs in artifact manifest.

## Remaining release blockers
- privacy/data-flow record and export/share decision;
- artifact manifest/hash record;
- automated fixture run passing in CI plus manual AT/device acceptance;
- metadata/OG record;
- actual lineage proof.