Oso Cloud rejects facts that dont match the policy type signature

When an Oso Cloud fact write is rejected, check the predicate against your policy: the argument count and types must match how the rule uses it, and the predicate name must be spelled exactly as in the policy. For tagging-style facts the policy does not use yet, add a declare statement with the allowed type signature before writing them.

Context: Official docs (Facts as Data, Oso Cloud): documents a gotcha that trips agents writing facts. Facts stored as data must be unconditionally true with no if clauses, and Oso infers the expected argument types from how the predicate is used in policy rules. Mismatched types, missing arguments, and unrecognized predicates are all rejected. If you want to store a fact type the policy does not reference yet, you must declare its type signature with a declare statement first.