EM-0033 execution plan

Source content

EM-0033 execution plan

Status: author research packet complete; fresh-clone independent review pending.

Objective

Turn the accepted Mehrabian readiness map into a content-addressed candidate research packet that

separates the two 1967 experiments, the later cross-study proposal, the unresolved origin of the

seven-percent coefficient, authorial qualifications, direct rebuttal, and broad recirculation.

Authority and identity

• immutable task: tasks/contracts/EM-0033.json;
• accepted starting base: 7dca84b0c8477efc09b31215f734348d626957d4;
• branch: codex/em-0033-mehrabian-lineage;
• accepted preliminary packet:

research/how-we-know/library-preliminary/mehrabian-7-38-55.md;

• allowed paths: the EM-0033 research directory, this plan, the Case 004 research note, and

append-only run receipts.

Method

1. Freeze the narrow historical question and a 2026-08-27 evidence cutoff.

2. Bind credential-free primary or authoritative carriers with exact identities, access history,

bytes, SHA-256, license treatment, locators, and quote-minimal spans.

3. Keep P1's word-and-tone task separate from P2's face-and-tone task.

4. Represent the three coefficients as P2's cross-study proposal, not a three-channel experiment.

5. Recompute only transparent arithmetic and label reverse engineering as sensitivity analysis.

6. Preserve the missing .07 source step, uncollated 1981 formula pages, unavailable original

materials, and closed follow-up full text as no-credit gaps.

7. Map participant, speaker, author, grant, stimulus, material, method, scale, citation,

book-edition, and derivation relations as typed evidence-linked edges.

8. Give recirculation zero scientific credit and retain the bounded negative search.

9. Require a fresh-clone reviewer to reproduce every source, span, calculation, edge, gap, and

GO/HOLD/FAIL recommendation on the exact author head.

Deterministic packet

• packet ID:

em:research-packet:sha256:a73dc29f0a0c3f05a112b7c392d115cfcc38a1136a683325bf74bebf0c6b2e40;

• 12 sources, 40 spans, 11 claims, and 6 derivations;
• 6 lineage groups, 5 participant-data roots, and 11 required-dimension lineage edges;
• 3 no-credit propagation objects and 5 follow-up dispositions.

The author recommendation is GO pending independent review for later dossier construction. It

does not admit a case or establish a public verdict.

Validation gates

• deterministic packet rebuild and exact file/content identities;
• exact source, capture, span, claim, derivation, lineage, propagation, and follow-up ID sets;
• independent recomputation of all six derivations;
• explicit omission and structured-transcription semantics;
• no-credit handling for propagation and the missing .07 derivation;
• all 11 required lineage dimensions and evidence links;
• adversarial fail-closed receipt validation;
• Ruff, JSON parsing, path-scope comparison, git diff --check, full make check, disclosure

audit, deterministic public rebuild, and clean tracked state.

Author validation record

• build_packet.py --check reproduced the committed packet and content address;
• verify_packet.py --self-test independently recomputed all six calculations, verified exact

ID/count/lineage sets, and rejected fourteen forged or incomplete receipt mutations;

• verify_packet.py --require-review failed closed with

independent review receipt missing, as required before review;

• Ruff passed for both research Python files;
• make check passed accepted-input validation, the full test suite, disclosure audit,

deterministic independent rebuild, and unchanged accepted source state; and

• append-only author receipt: runs/proposals/20260827T170854Z-2974d169d36f.json; and
• exact 1971 visual-transcription correction receipt:

runs/proposals/20260827T172115Z-97e661f58a1c.json.

Exact author commit, tree, draft PR, and CI identities are recorded after push. An independent

exact-head receipt remains pending.

Boundaries

No dossier construction, catalog admission, public verdict, Pages deployment, provider call,

credential, spend, DNS, workflow, package, release, or broad launch action is authorized.