evidence.ingest

Append one or more evidence records to the tamper-evident evidence log for the caller’s tenant. Use this to write back what an agent did and observed (the trace that later derives lessons). Server computes tenant_id/hashes/id; do not supply them. actor_type/actor_id are optional — they default to your token’s principal; supply them only to attest a different actor (e.g. a CI bot).

Input

Field	Type	Required	Description
`evidence`	array (nullable)	yes	(items 1–500)
`options`	object

`evidence`

Field	Type	Required	Description
`action_type`	ActionType		from the closed high-risk action taxonomy (schemas.md §1)
`actor_id`	string
`actor_type`	ActorType
`artifact_refs`	array of string (nullable)
`entity_mentions`	array of string (nullable)
`event_ts`	string (date-time)	yes
`labels`	array of string (nullable)
`metadata`	object
`payload_ref`	string
`risk_class`	RiskClass
`scope_key`	string	yes	level:id, e.g. repo:payments-service
`sensitivity`	Sensitivity
`source_ref`	string	yes
`source_type`	SourceTypePublic	yes
`summary`	string	yes
`workspace_id`	string		optional; defaults to your token’s workspace

`options`

Field	Type	Required
`derive`	boolean (nullable)
`idempotency_key`	string

Output

Field	Type	Required
`accepted`	array (nullable)	yes
`chain_head`	object (nullable)
`rejected`	array (nullable)	yes
`request_id`	string

`accepted`

Field	Type	Required
`chain`	string	yes
`deduped`	boolean	yes
`derivation_task_id`	string
`event_hash`	string	yes
`id`	string	yes
`prev_hash`	string

`chain_head`

Field	Type	Required
`chain`	string	yes
`head_hash`	string	yes
`length`	integer	yes

`rejected`

Field	Type	Required
`code`	string	yes
`index`	integer	yes
`message`	string	yes