# V1 Specialist Review Matrix

**Status:** open pre-stable review control

**Portfolio:** V1

**Release owner:** Elijah Faviel

This matrix defines the independent human review still required before the V1
portfolio can be called stable. It does not imply that one reviewer must read
the entire corpus or that participation constitutes endorsement. Each reviewer
receives an exact source snapshot and a bounded packet suited to their actual
competence.

The earlier pastoral and theological feedback on *Rethinking Reality* remains
part of that book's history. It is not represented here as completion of the
wider portfolio review.

## Required Review Tracks

| Track | Primary scope | Minimum evidence for completion | Current state |
| --- | --- | --- | --- |
| Biblical studies and original languages | Load-bearing Hebrew, Aramaic, and Greek exegesis; disputed texts; translation claims | Named or permission-respecting attribution, exact snapshot, written findings, and dispositions | Not begun |
| Patristics and historical theology | Primary-source use, chronology, reception claims, and limits of patristic agreement | Exact-source spot checks, written findings, and dispositions | Not begun |
| Philosophy and rival-worldview analysis | Metaphysical bridges, moral realism, public explananda, rival steelmanning, and inference limits | Written challenge from a suitably competent reviewer and recorded response | Not begun |
| Human genetics and population history | Population bottlenecks, genealogical versus genetic ancestry, Adamic proposals, and revision triggers | Domain review against current primary literature | Not begun |
| Origin-of-life science | Prebiotic chemistry, RNA and peptide systems, end-to-end claims, and gap language | Domain review against current primary literature | Not begun |
| Clinical psychology and research methods | CRM status, proposed constructs, adverse effects, diagnostic boundaries, study design, and retirement criteria | Licensed or research-qualified review with safety findings dispositioned | Not begun |
| Safeguarding and abuse response | Coercive control, reporting, disclosure, separation, restoration, leadership, and referral boundaries | Practitioner review across representative high-risk chapters and resources | Not begun |
| Spanish language and cultural review | Governing claims, native prose, Scripture references, safety language, and cultural fit | Direct native-speaker review of representative and high-risk material | Not begun |
| Indonesian language and cultural review | Governing claims, native prose, Scripture references, safety language, and cultural fit | Direct native-speaker review of representative and high-risk material beyond the existing editorial pass | Not begun |

## Packet Contract

Every review packet must include:

1. the V1 label and exact full Git commit;
2. the reviewer's bounded domain and the works or sections in scope;
3. the relevant manuscript, chapter Markdown, source ledger, and research
   records;
4. the project's claim-strength and source-jurisdiction rules;
5. known open questions, limits, safety boundaries, and revision triggers;
6. the feedback template and private/public attribution choices; and
7. a statement that review does not imply endorsement of the work outside the
   assigned scope.

The public DDF review bundle and per-book research pages provide the base
materials. A narrower packet may link to those exact artifacts instead of
duplicating them.

## Completion Rules

A track is complete only when the release owner has:

- recorded the exact reviewed snapshot;
- preserved the reviewer's authorized identity or chosen anonymity;
- entered each actionable finding in the feedback process;
- closed, mitigated, removed, or explicitly accepted every blocking finding;
- propagated accepted corrections through affected books, languages, essays,
  tools, public pages, and generated artifacts; and
- obtained reviewer confirmation of the correction when the finding requires
  specialist rechecking.

AI agents, model-family agreement, internal author review, a successful build,
and informal praise do not complete a track. A reviewer may complete one track
without certifying another.

## Public Reporting

The publication manifest begins with no completed formal review domains and no
public reviewer attributions. Those fields change only after the evidence above
exists and the reviewer has granted the relevant permission. Until every
required track and the other release gates are complete, the public state
remains **V1 preview**.