Evidence Workflow

Evidence connects claims in the operating graph to source material. External agents should usually create candidate evidence proposals, not accepted evidence. A WyrdOS user or FDE can then approve or reject the proposal.

Flow

Fetch review context.
Inspect warnings, stale evidence, current evidence, and pending proposals.
Choose the exact entityType and entityId.
Create a candidate evidence proposal with source metadata and a reason.
Approve or reject the proposal.

Rejected proposals are preserved for audit history and do not create accepted evidence.

1. Fetch Review Context

curl -H "Authorization: Bearer <API_KEY>" \
  "https://<your-wyrdos-api-host>/api/v1/ontology/review-context?organisationId=<organisationId>"

Inspect:

data.warnings
data.staleEvidence
data.evidence
data.proposals.items
data.entities

2. Create A Proposal

curl -X POST \
  -H "Authorization: Bearer <API_KEY>" \
  -H "Content-Type: application/json" \
  "https://<your-wyrdos-api-host>/api/v1/evidence-proposals?organisationId=<organisationId>" \
  --data '{
    "entityType": "container",
    "entityId": "container_product",
    "type": "artifact",
    "title": "Beta launch plan was published",
    "summary": "The launch plan names Product as owner for beta onboarding readiness.",
    "sourceType": "url",
    "sourceName": "Launch docs",
    "sourceLabel": "Beta launch plan",
    "sourceUrl": "https://example.com/beta-launch-plan",
    "confidence": "medium",
    "reason": "Review context showed Product is goal-linked but missing recent evidence.",
    "sourcePayload": {
      "agent": "actor",
      "reviewWarningId": "container_without_recent_evidence:container:container_product"
    }
  }'

Required:

entityType
entityId
type
title
summary
reason

Recommended:

sourceName
sourceLabel
sourceUrl or sourcePayload
confidence

3. Approve Or Reject

Approve:

curl -X POST \
  -H "Authorization: Bearer <API_KEY>" \
  "https://<your-wyrdos-api-host>/api/v1/evidence-proposals/<proposalId>/approve?organisationId=<organisationId>"

Reject:

curl -X POST \
  -H "Authorization: Bearer <API_KEY>" \
  "https://<your-wyrdos-api-host>/api/v1/evidence-proposals/<proposalId>/reject?organisationId=<organisationId>"

Approval creates accepted evidence and stores the created evidence ID on the proposal. Rejection keeps the proposal for review history.

Agent Rules

Use review context before proposing evidence.
Do not guess entity IDs; choose them from data.entities or a focused graph endpoint.
Include source metadata whenever available.
Include a plain-language reason.
Do not create accepted evidence directly unless the workflow explicitly permits it.
Treat duplicate pending proposals as a signal to review instead of retrying.