Evidence

Evidence records state exactly what a source supports, who supplied it, when it was reviewed, its scope, confidence, and limitations. Store one record per file, named with its immutable ID: EV_<scope>_<nnn>.md.

Valid scope segments are a vertical ID for one vertical, MULTI for several explicitly supported verticals, and PRODUCT for product facts.

Interactive evidence

W9 may create evidence from structured questions answered by a user. A call recording, transcript, screenshot, export, or other attachment is optional. The record must:

• identify the contributing user or role in publisher_or_owner;
• describe the interactive authoring session in source, using a stable task, thread, transcript, or session reference when available;
• preserve the supplied observation faithfully in supports or notes;
• distinguish direct observation from estimates, inference, and second-hand buyer confirmation;
• state the applicable product, account, or vertical scope; and
• record confidence and material limitations.

When no separate stable reference exists, preserve the relevant user answer in notes so the canonical evidence record itself remains inspectable. Never invent a recording or attachment.

Use buyer_interview when the buyer answers directly, call_learning when a contributor reports what a buyer said, and internal_validation when an expert reports product behavior. Interactive evidence is canonical only after W9 creates the record and S4 validates it; raw chat text is not itself an evidence_id.

Current records

Evidence ID	Type	Scope
EV_PRODUCT_001	internal_validation	Naologic Global Pricing product workflow
EV_MULTI_001	call_learning	All current verticals; one reported buyer
EV_PRODUCT_002	internal_validation	Naologic manufacturing costing workflow
EV_MULTI_003	internal_validation	All current verticals; production margin dashboard
EV_MULTI_004	call_learning	All current verticals; pre-commit work-center planning