v1
latestOpenAPI 3.1.02026-07-13250151.3 KBfindings
Record a write-back finding against an intent: a contradiction that building the spec surfaced. The inverse of a decision — the next agent that pulls this intent reads open findings as 'the spec may be stale here' so the refinement loop converges instead of repeating a dead premise.
Rate-limited by the 'general' bucket (300/h sliding window, keyed user:<userId> or ip:<ip>). Findings are stored as a read-modify-write append on the intent's implementation_findings JSONB array (prior findings are preserved); the merged set is sanitized (capped length, malformed legacy rows dropped) before persisting. Every new finding is created with status 'open' and a server-assigned id + recordedAt (epoch ms); target, correction, and source are echoed back only when supplied. openCount is the number of findings still in status 'open' after the write.
post/api/v1/intents/{id}/findings
Path parameters
idstring required
id path parameter.
Query parameters
workspace_idstring
Required ONLY for cookie-session auth; identifies the target workspace. Ignored for API-key auth.
Request body
Response
Created — returns { intentId, finding, openCount }
object required