Resolve

POST /v1/resolve. One value for one declared fact at one point in time, chosen by the declared policy, or a refusal with every candidate attached.

The fact must be declared first. Candidates are the nodes carrying that fact_key that were known at as_of (and, with valid_at, in force then). The declared policy picks one. When it cannot, the answer says so and attaches every candidate.

Request

fact · string · required

The fact_key.

as_of · timestamp or date · required

valid_at · timestamp

rules_as_of · timestamp

Apply the declaration that was in force at this instant instead of at as_of. Declarations are time-aware, so a fact declared today is undeclared_fact for a 2024 as_of unless you pass rules_as_of. When given, it is recorded in the certificate.

Response

Always 200.

status · string

answered or no_answer.

value · any

The chosen fact_value, when answered.

reason · string

When no_answer: undeclared_fact (no declaration at that instant), no_data (no node carries this key), not_yet (values exist but none was known at as_of), no_value_at (none in force at valid_at), unresolved_conflict (the policy cannot choose; all candidates attached).

policy · string

The policy applied.

candidates · object[]

Every candidate considered, with its value and times.

certificate · object

Scoped to this fact. Carries rules_as_of when it was given.

Request

curl -s -X POST $TCKG/v1/resolve -H 'content-type: application/json' -d '{
  "fact": "belief:user:randy:NVDA:direction",
  "as_of": "2024-10-01", "rules_as_of": "2026-10-03T07:30:00Z"
}'

Add "valid_at": "2024-06-01" to the first request to ask “what was in force in June, as known in October”: the answer is up.