Trust Methodology

Four states

• Curated corpus

  A human-selected entry with source, reference, commentary, and practice. Keyword retrieval can ground a Sutra in that entry. On matched Trust Pack journeys, lineage may also show as source-detail fields (original, translation, commentary, application) — empty fields are omitted, never invented.

• Model composition

  When enrich runs, understanding, wisdom, and reflection may be rewritten from the matched entry. Source, practice, citations, and source-detail fields stay locked to the corpus. Separate chips say when AI composition happened.

• Not yet field-reviewed

  Most corpus rows — and four of twelve Trust Pack entries — have no dated field-scoped human review yet. That is not rejection; it means no scoped badge.

• Field-reviewed

  A dated review lists which fields were checked. Today that is often source, reference, commentary, and application on a subset of the Trust Pack. It never means the full entry, full Trust Pack, or full corpus is verified. Thin original/translation concept labels are not claimed as verse-level review.

What badges mean

Example: Reviewed · source, reference, commentary, application · 2026-07-23Credit on current badges: Founder review (external advisor shortfall documented).

• Date — when the field review was recorded.
• Fields — only those listed were reviewed; other fields may still be pending.
• Optional credit — e.g. founder review, or an advisor with consent.
• Never “fully verified” unless every claimable field for that entry is listed.
• Concept-label original/translation text is shown as lineage when present, but is not treated as verse-level review unless those fields appear on the badge.

Curated-vs-AI chips (Week 5) are a different vocabulary from field-review badges. They answer different questions.

Trust Pack scope

The front-door Trust Pack is a small Ready set of 12 entries with precise references. A CI / build guard fails if any pack id lacks a non-empty reference. Field reviews currently cover 8 of 12 pack entries (cold-demo lock 5 plus three more). Unreviewed pack entries stay Not yet field-reviewed — no vanity Reviewed chrome.

Source detail (lineage)

Matched journeys can show “Where this came from” with source, reference, and omit-empty lineage fields. That block answers where the answer came from; the dated badge answers which fields a human actually checked. Empty lineage fields are omitted — never padded with Pending theater.

How reviews happen

Reviews are a manual packet workflow: entry id, fields checklist, claim boundaries, then additive corpus metadata. There is no advisor login, review queue, or scholar console in product. The shared packet lives in docs/ADVISOR_REVIEW_PACKET.md. Until an external advisor completes a pass, badges credit Founder review honestly.

Claim boundaries

• Curated is not the same as field-reviewed.
• AI composition is not scholar approval.
• One field reviewed is not a fully verified entry.
• Eight of twelve pack badges is not a fully verified Trust Pack.
• The Trust Pack is not the full corpus.
• Source detail on a journey is corpus lineage — not an extra review claim.
• There is no live Wisdom Council validating every answer.
• Reviews today are founder-credited; external advisors are invited via a manual packet, not a console.