---
title: "SubjectResolution"
description: "what a subject stands for when the predicate is armed: names, keys and meaning"
section: concepts
address: /concepts/subjectresolution
contract: 0476e35e6e275db5
---

# SubjectResolution

what a subject stands for when the predicate is armed: names, keys and meaning

[figure: SubjectResolution is a fact at follows scope. The drawing shows its fields and the objects that they point at.]

| property | value |
|---|---|
| kind | fact |
| scope | follows |
| key | the subject a leaf names, and its version |
| store | postgres+lake |
| family | rules_engine |



## Fields


| field | type | required | note |
|---|---|---|---|
| `subject` | `text` | yes |  |
| `entity` | `id` | no |  |
| `names` | `[text]` | yes |  |
| `keys` | [Identifier](/concepts/identifier) | yes |  |
| `vector` | [Vector](/concepts/vector) | no |  |
| `version` | `count` | yes |  |



## Routes that use it
No route takes or returns SubjectResolution directly. The record holds it, and the objects that point at it reach it.