Set a facet whose owner is an **edge** rather than a resource.

A separate route rather than a mode of POST /api/facets, for two reasons that are both about
the owner not being a payload choice: the edge is addressed in the path (matching every other
edge write — /api/relationships/{edge_handle}/retype|reweight|fold), and the authorization
gate is a different question. DbBackend::set_facet dispatches on the typed owner to
check_edge_mutable, which is the same gate that governs re-typing or folding the same edge.

Both statuses are reachable, and they mean different things. 404 for an edge that does not
exist, is folded, or whose target the caller cannot read — that last arm is NotFound rather
than Forbidden on purpose, so the write never confirms the existence of a resource the caller
has no standing to see. 403 for an edge the caller can legitimately see but may not author
into: it fails source-write or container-write on the edge's home.

An earlier version of this comment claimed the endpoint returns "404 rather than 403" outright,
twelve lines above an OpenAPI block declaring 403. The annotation was right and the prose was
wrong; check_edge_mutable renders Forbidden for clauses 1 and 2 and NotFound for the row
lookup and clause 3.

curl --location '/api/relationships//facets' \ --header 'X-Temper-Surface;' \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data '{ "confidence": null, "correlation_id": null, "invocation_id": null, "model": "string", "persona": "string", "rationale": "string", "reasoning": "string", "values": null, "weight": 0 }'

Set a facet whose owner is an edge rather than a resource.

Request

Responses