# Multica Skill: Evidence Labels

Attach this skill to every agent in the starter pod.

## Purpose

Evidence labels keep agent work honest. They make the difference between “we know this,” “we think this,” and “we are currently tap-dancing over a missing fact.”

Use labels on any claim that matters to a decision, recommendation, report, draft, or approval.

## Labels

### Confirmed

Directly observed in source data, logs, screenshots, docs, customer words, platform output, website pages, tool output, or another verifiable source.

Use when the agent can point to the evidence.

### Inferred

Reasonable conclusion from evidence, but not directly observed.

Use when the conclusion is likely but still interpretive.

### Assumption

A useful working belief that must not be reported as fact.

Use when moving forward is reasonable, but validation is still needed.

### Gap

Missing access, missing data, failed read, blocked source, unresolved uncertainty, or unavailable context.

Use when the absence affects confidence, completeness, or the next decision.

## Usage pattern

```md
- [Confirmed] Claim — evidence/source/link.
- [Inferred] Claim — based on X and Y.
- [Assumption] Claim — needs validation by Z.
- [Gap] Missing thing — why it matters and how to resolve it.
```

## When labels are required

Use labels for:

- audit findings
- competitor claims
- customer/buyer language
- content recommendations
- technical claims
- risk statements
- prioritisation rationale
- approval packages
- anything that could influence publishing, spending, customer-facing changes, or production work

Labels are optional for harmless workflow narration like “created a ticket” or “attached the file.”

## Source standard

When possible, include:

- URL or file name
- page/title/section
- tool output or screenshot reference
- date if the source is time-sensitive
- whether access was public or provided

## Escalation rule

If a gap blocks a decision, say so clearly and set the status to `Hold` or `Approval needed` rather than pretending the work is done.

## Anti-patterns

Do not:

- label a guess as confirmed
- hide a gap in a footnote
- cite a competitor marketing page as objective proof
- treat missing data as zero
- use vague sources like “research shows” without a source
- remove labels from final copy if the claim still needs review

## Hard rule

A gap is not a zero. A gap is not permission to invent facts. A gap is a gap.