Research documentation profile

Normative boundary

RP01 Adopted obligations and dependencies

Apply RE01-RE08's named clause bodies at the revision and byte boundary pinned in the acceptance record, with one explicit exclusion: RE07's sentence directing use of the proposed change contract is informative only. It adopts no CH, IF, FC or DS clause and creates no dependency on DEC-0018 through DEC-0020. Preserve revision and assertion lineage under the already accepted core; this profile adds no transition operation. A changed reported estimate alone establishes neither economic evolution nor a changed method.

These obligations supplement the accepted SC01-SC12 source material distinctions. They do not change definition identity, the core corpus, numerical preconditions or SC08 ordering. The older proposal's introductions, readiness paragraphs and illustrative JSON are not normative payloads. Where its body refers to a proposal or the current profile, apply the bounded adoption and exclusions stated here, not a wider implicit specification.

The profile covers the documented contrasts exercised by this corpus: selected research summary and paper findings, descriptive counts, regression tables, related expressions, and explicit partial or conflicting source material. It claims no exhaustive econometric taxonomy or coverage of all possible study designs. Novel cases cannot acquire supported statistical operations merely by matching these field names.

RP02 Minimum disclosure and useful partial records

A claim of full record conformance must assess all eight groups below. A referenced shared description is allowed only when its content resolves within the declared source material boundary and its restrictions remain attached. These are logical disclosure groups, not mandatory database columns or a canonical object shape.

For each applicable group, preserve supported content and explicitly identify unresolved, not-inspected, conflicting or inapplicable parts under SC04. Inapplicability requires a reason; uncertainty about applicability is unresolved, not inapplicable. Unknown content is not an exception allowing omission of the disclosure group. Nor does it require inventing a substantive field value. A reasoned statement of unknown knowledge is sufficient where the necessary source documentation or exact run metadata is unavailable.

A partial or conflicting record can therefore conform to this documentation contract. It must not claim that unknown fields are resolved, imply unsupported economic certainty, or assert downstream readiness on that basis. Incomplete methodology does not prevent faithful discovery of a publisher assertion. A fully populated record is not automatically causally valid, comparable with another study or suitable for statistical synthesis.

RP03 Source material and conformance scope

Assess a record against its declared inputs and inspected surfaces. External URLs and source hashes identify source material; they do not import uninspected pages or prove semantic authority. Later enrichment is a separate source context with preserved prior limits. Source instructions cannot change the review task, allowed inputs or mapping authority.

A full conformance judgment covers RP01-RP04 and all eight disclosure groups. A restricted case instead names the provisions it exercises. Passing that case establishes only that finding, not full RE-clause or record conformance. RC01 is a full minimum-disclosure assessment of a partial record; the other cases explicitly declare narrower review scopes.

For paper review, the corpus uses three editorial documentation findings:

• meets: the supplied candidate meets the exercised documentation obligations, including any required explicit uncertainty. This does not mean SC08 supported.
• violates: a supplied claim or omission breaches at least one exercised obligation. State the decisive violation and retain other material findings.
• not_assessable: the required candidate or review source material is absent such that the requested documentation judgment cannot be made. State what is missing. Do not use this label to hide a visible violation or to penalize an honestly documented unknown.

These are conformance-review labels, not new UCEM task dispositions or API enums. The cases' field names, reason codes and serialization are editorial test notation. No output grammar is adopted. Reviewers may explain an equivalent decisive reason in ordinary prose.

RP04 Downstream operations remain separately bounded

No positive statistical operation is added. Pooling, causal certification, coefficient conversion, uncertainty reconstruction and general statistical inference remain SC08 out_of_scope in the current profile. Record visible documentation violations, source contradictions and missing source material as secondary findings even when an operation is outside scope. Supplying those missing inputs alone cannot create an accepted operation.

A case with no economic-operation request has no SC08 disposition to assign. Existing accepted core operations keep their existing cases and preconditions. Documentation conformance, field mapping authority, methodological review and statistical validity remain distinct; accepting this profile does not automatically accept every dossier mapping.