---
type: Process
title: GTM field evidence system
description: Plain-English instructions and examples for the evidence, community, decision, and relationship logs.
visibility: internal
---

# GTM field evidence system

These four small YAML files are the execution record for the 60-day GTM plan. They keep observation separate from opinion and prevent a Slack thread or memory from becoming proof.

## The easy way to update them

Tell a Peach Pilot coding agent what happened in plain English. For example:

> Log a de-identified Safe Life workflow session with an established agent. The agent checked a carrier guide after Right Quote and did not permit external quotation.

> Add r/InsuranceAgent as observed. Recruiting posts are restricted and we have not participated yet.

> Record that the objection-roundtable experiment changed because no agent responded without employee prompting.

The agent should update the matching canonical file, preserve the schemas below, remove client PII, and show the diff before committing.

## What goes where

| File | Contents |
| --- | --- |
| [`evidence-log.yaml`](./evidence-log.yaml) | Sessions, observed signals, claims, permissions, and evidence that contradicts a hypothesis |
| [`community-log.yaml`](./community-log.yaml) | Candidate surfaces, conversations, and agent-to-agent interactions |
| [`decision-log.yaml`](./decision-log.yaml) | Evidence-producing experiments and go / change / stop decisions |
| [`relationship-map.yaml`](./relationship-map.yaml) | Potential founding personalities and business relationship paths |

Agency prospects, introductions, stages, and next steps belong only in [`../crm/pipeline.yaml`](../crm/pipeline.yaml).

## Counting rules

- One distinct person or one separate observed work event can contribute one independent signal.
- A compliment without an example is not behavioral evidence.
- A prediction about future use is not repeat use.
- `observed_behavior`, `verbatim_quote`, and `observer_interpretation` must remain separate.
- Every major hypothesis keeps both supporting and disconfirming evidence.
- Unknown means the source was not checked. It never silently becomes zero or passed.

## De-identified evidence example

This example shows the required shape; it is not a real Safe Life result and does not count toward the plan.

```yaml
- id: example-session-do-not-count
  counts_toward_scorecard: false
  session_date: 2026-07-21
  participant_id: demo-established-agent-01
  participant_segment: established_producer
  source: reconstructed_recent_workflow
  recent_task: medication-driven final-expense quote
  observed_behavior: Agent reviewed Right Quote, then opened a carrier guide before choosing a carrier.
  verbatim_quote: "I wanted to confirm the medication rule before I trusted it."
  observer_interpretation: The result was useful, but the medication explanation did not yet replace the guide check.
  artifact_link: null
  permission:
    internal_retention: true
    attribution: false
    external_quote: false
    compensation: none
    revocation_contact: null
  pii_redacted: true
  confidence: high
  hypothesis_effect: contradicts_referenceability
  decision_affected: keep medication explanations in the trust-blocker review
  owner: Tyler
  next_action: Compare the displayed reason with the canonical carrier rule.
```

## Pipeline example

This example is illustrative and must not be copied into the canonical pipeline as a real lead.

```yaml
- id: example-agency-do-not-count
  name: Example Agency
  owner: Tyler
  milestones:
    identified: 2026-07-21
    pitched: null
    proposal: null
    signed: null
  status_history:
    - status: active
      effective_on: 2026-07-21
  warm_intro:
    introducer: Example Connector
    status: received
    updated_on: 2026-07-21
  decision_maker: Example Owner
  confirmed_problem: New agents require leader intervention for carrier matching.
  decision_access: Warm introduction accepted.
  next_action: Review a 5-agent pilot hypothesis
  next_action_due: 2026-07-28
  next_action_accepted_by_both_sides: true
```

## Privacy and approval

- Never store policyholder name, phone, address, health details tied to an identity, SSN, banking data, or application identifiers here.
- Use participant IDs unless attribution is explicitly permitted.
- Access is limited to the internal repo team. Each permissioned claim must have a retention date and deletion owner.
- External use requires the compliance gate in the canonical GTM plan; a true `external_quote` field alone is not approval.