extract-evidence-record
Purpose
Extract a schema-declared evidence record containing methods, data, metrics, results, conditions, limitations, provenance, and explicit missing fields.
Input contract
required: [source, extraction_schema]
optional: [protocol_record, quality_rubric, condition_schema]
constraints: [each extracted value is source-linked and missing or ambiguous fields remain explicit]
Procedure
- Identify source identity, study design, population, intervention/exposure, comparator, and outcome.
- Extract methods, data, evaluation conditions, metrics, estimates, and limitations into the schema.
- Record units, uncertainty, provenance links, and missing/ambiguous fields.
- Run schema and consistency checks before releasing the record.
If the evidence record contains enough design and method detail for appraisal, consider audit-study-validity as the next tactic.
Output contract
produces: [evidence_record, condition_record, source_links, missing_field_log, extraction_notes]
delta_fields: [evidence_updates, uncertainties, open_questions]
Quality gates
- Results cannot be detached from their conditions and metric definitions.
- Missing data are distinct from zero or null results.
- Extraction notes preserve source wording where interpretation is uncertain.
Failure and counterexamples
Do not infer unreported baselines or merge records from different study versions without lineage evidence.
Provenance map
resolved: extract-data
resolved: score-extraction
resolved: condition-cataloging
intermediate: Pass4/extract-study-data
resolved: performance-extraction
intermediate: Pass4/extract-performance-record
intermediate: Pass4/catalog-evaluation-conditions
1---2name: extract-evidence-record3description: "Extract a schema-declared evidence record from a source, including methods, datasets, metrics/results, conditions, limitations, provenance, and explicitly missing/ambiguous fields."4metadata:5 source: https://skillmd.com/skills/yogsoth-ai/extract-evidence-record6---78# extract-evidence-record910## Purpose1112Extract a schema-declared evidence record containing methods, data, metrics, results, conditions, limitations, provenance, and explicit missing fields.1314## Input contract1516```yaml17required: [source, extraction_schema]18optional: [protocol_record, quality_rubric, condition_schema]19constraints: [each extracted value is source-linked and missing or ambiguous fields remain explicit]20```2122## Procedure23241. Identify source identity, study design, population, intervention/exposure, comparator, and outcome.252. Extract methods, data, evaluation conditions, metrics, estimates, and limitations into the schema.263. Record units, uncertainty, provenance links, and missing/ambiguous fields.274. Run schema and consistency checks before releasing the record.2829If the evidence record contains enough design and method detail for appraisal, consider `audit-study-validity` as the next tactic.3031## Output contract3233```yaml34produces: [evidence_record, condition_record, source_links, missing_field_log, extraction_notes]35delta_fields: [evidence_updates, uncertainties, open_questions]36```3738## Quality gates3940- Results cannot be detached from their conditions and metric definitions.41- Missing data are distinct from zero or null results.42- Extraction notes preserve source wording where interpretation is uncertain.4344## Failure and counterexamples4546Do not infer unreported baselines or merge records from different study versions without lineage evidence.4748## Provenance map4950- `resolved: extract-data`51- `resolved: score-extraction`52- `resolved: condition-cataloging`53- `intermediate: Pass4/extract-study-data`54- `resolved: performance-extraction`55- `intermediate: Pass4/extract-performance-record`56- `intermediate: Pass4/catalog-evaluation-conditions`