Research Payload Family — Shared Core, Run Receipt & Promotion Boundaries

What belongs in this family

A research artifact earns the smallest form that carries its job:

• Executable research payload — a self-contained instrument with a receiving decision, evidence hierarchy, required outputs, and stopping event.
• Research payload candidate — a promising research route whose runnable method, falsifier, or completion evidence is still forming.
• Modular annex — a recurring method such as source-authority mapping, verification, provenance, or recovery that several payloads can reuse.
• Parameter pack — jurisdiction, population, system, configuration, horizon, or domain variables supplied without rewriting the canonical instrument.
• Run receipt — the exact invocation, reached evidence, deviations, outputs, uncertainties, and next receiver.
• Generated report — the evidence-bearing result of one execution.
• Worked example — an inspectable application with enough local state to teach the method.
• Release history — the rationale for changes, kept one link away from the active instrument.

Shared payload core

Every executable payload names:

1. Identity — stable title, version, artifact role, and current public route when one exists.
2. Receiving decision — the decision this research supports and the role authorized to make it.
3. Working frame — active sources, interpretive vantage, held-aside material, adjacent open claim, and the evidence that widens the frame.
4. As-of coordinates — research date, source window, jurisdiction, population, system, task, and material configuration.
5. Declared inputs — required parameters, optional parameters, accepted defaults, and unresolved values.
6. Claim classes — current fact, supported transfer, practitioner interpretation, and open or local hypothesis.
7. Coverage record — sources reached, sampled, estimated, unavailable, or replaced by a named fallback.
8. Disconfirmation route — confounders, alternative explanations, counterevidence, and the observation that changes the decision.
9. Output contract — human-readable findings, source and transfer ledger, decision readout, machine-readable receipt, and accessible equivalents where visuals appear.
10. Completion and recovery — stopping event, evidence ceiling, unresolved conflicts, next receiver, safe re-entry point, and reopening triggers.

The core stays compact. Domain-earned scoring, visuals, regulatory profiles, numerical methods, and test depth remain with the payload that needs them.

Run receipt

A run receipt records one execution while the active instrument stays compact.

Evidence and language posture

• Lead with the state the research can establish, then state its scope.
• Preserve source wording in quotations and cited data.
• Resolve operational referents by role: retrieval operation, evidence-adjudication step, synthesis operation, accountable decision owner, or receiving collaborator.
• State probability as probability of a named event, for a named population, over a named horizon, under named conditions.
• Treat an unavailable source as coverage information. Record the claim that remains open and the fallback that was used.
• Pair consequential boundaries with the useful replacement behavior that keeps the work moving.
• Carry visuals from a canonical source table with definitions, units, lineage, estimate markers, runtime information, and an accessible text equivalent.

Longitudinal behavior

A delta run is the default when a prior receipt and source package remain adequate. A full run becomes fitting when one of these triggers changes the research frame:

• regulation, enforcement, policy, or market structure changes materially;
• a source disappears or a higher-authority source becomes available;
• a material platform, model, or system configuration changes;
• contradictory evidence changes a claim class or transfer limit;
• the receiving decision, population, jurisdiction, or operating model changes;
• the review horizon elapses.

Promotion boundary

A candidate becomes an executable payload when:

• the receiving decision is recurring and consequential;
• the evidence hierarchy is distinctive enough to warrant a dedicated instrument;
• the method produces an observable result;
• a falsifier or disconfirmation route is present;
• the stopping event and next receiver are explicit;
• one materially meaningful use establishes that the instrument can travel.

A useful method stays an annex or parameter pack when shared authority and single-point maintenance create the clearer route.

Source and projection authority

The Notion source page carries the current research instrument. The public Super route is a delivery projection. A projection observation records the source edit time, payload version, public route request time, and visible version or digest. The request time establishes delivery observation; substantive currency continues to come from the payload's as-of and review coordinates.

Related working sources

• Working Frame Declaration — What Is in View, What Is Held Aside & What Changes the Frame
• Evidence-Bearing Test Design — Behavior, Boundary & Observable Proof
• Goal Fidelity Under Partial Context — Proportionate Structure, Material Evidence & Calm Recovery
• Deep Research Atlas — Self-Contained Payload
• LIMS Build-or-Buy — Self-Contained Deep Research Payload
• Competitive Landscape & Portfolio Contribution — Self-Contained Research Payload

Copy-ready payload kernel

Copy-ready run receipt

One execution creates one receipt. Substantive findings belong in a generated report; the receipt carries the exact run coordinate and handback.

Machine node

Corpus integrity and provenance

This page synthesizes patterns already present across the Registry's mature research payloads and supporting Practitioner Probes. It defines a coordination contract for future instruments; individual payloads retain their domain methods, evidence ceilings, and decision authority.