# evm.execution_observation_facts

Authored address labels.

Canonical HTML: <https://determica.com/docs/tables/evm-execution-observation-facts>

- Kind: View
- Layer: execution_read_model
- Category: Simulation
- Tags: Program, Execution, Public, View

## Contract and lifecycle

**Grain:** One contextual attempt fact per (execution_id, attempt_kind, step_index or observation_index, global_index); attempt_id identifies the reusable physical attempt.

**Lifecycle:** run publishes this immutable row set atomically with its owning run. Statement failure or caller rollback publishes no durable prefix; direct DML is unsupported because it can corrupt the documented invariants.

**Status and NULLs:** Interpret nullable payloads only through their owning status fields. Defensive poisoned and engine_error outcomes mean the engine refused to claim a trustworthy normal result; broad view nullability also covers owner alternatives and left-joined evidence.

### Join guidance

- Join evm.executions on execution_id for candidate and run context.
- Use attempt_id to deduplicate physical facts expanded across contextual owners.
- For program owners use step_index; for observation-call owners use observation_index and observation_key.

### Effect semantics

- Access flags describe attempted EVM access, not committed state change.
- Effect facts retain attempted evidence and final committed, reverted, discarded, or poisoned disposition.
- execution_state_deltas contains committed checkpoint transitions only; observation-call effects are excluded from execution_effect_summary.

## Columns

### Identity and ownership

Contextual keys and reusable identities that establish row ownership.

- `execution_id` (UUID; nullable) — Contextual execution association identity; do not use it as reusable artifact identity.

### Ordering and cardinality

Stable indexes and counts used to reconstruct deterministic order.

- `declaration_index` (UINTEGER; nullable) — Documented declaration_index value for this public execution-data row.

### Payload and evidence

Operation-specific inputs, outputs, and authenticated evidence.

- `address` (ADDRESS; nullable) — Account or storage-owner address described by this fact.
- `label` (VARCHAR; nullable) — Documented label value for this public execution-data row.
- `effective` (BOOLEAN; nullable) — Documented effective value for this public execution-data row.

### Timestamps

Contextual publication times that are excluded from reusable semantic identity.

- `created_at` (TIMESTAMP; nullable) — Context association or publication timestamp; not a reusable semantic identity.

## Linked joins

- `execution_id` → [evm.executions](/docs/tables/evm-executions.md) (`execution_id`) — Contextual execution that exposes this public row.

## Related public objects

- [evm.executions](/docs/tables/evm-executions.md) — upstream

## Verified queries

### Confirm fixture coverage

Confirm that this object has rows owned by the stable seven-candidate public fixture.

```sql
SELECT 'evm.execution_observation_facts'::VARCHAR AS object_name, CASE WHEN count(*) > 0 THEN 'PASS' ELSE 'FAIL' END::VARCHAR AS status FROM evm."execution_observation_facts" o JOIN evm.executions e USING (execution_id) WHERE e.candidate_key IN ('complete-effects', 'later-revert', 'ordered-logs', 'create', 'selfdestruct', 'blockhash', 'transient-access');
```

### Check candidate ownership

Diagnose whether this object remains linked to at least one stable fixture candidate through public keys.

```sql
SELECT 'evm.execution_observation_facts'::VARCHAR AS object_name, CASE WHEN count(DISTINCT e.candidate_key) > 0 THEN 'PASS' ELSE 'FAIL' END::VARCHAR AS status FROM evm."execution_observation_facts" o JOIN evm.executions e USING (execution_id) WHERE e.candidate_key IN ('complete-effects', 'later-revert', 'ordered-logs', 'create', 'selfdestruct', 'blockhash', 'transient-access');
```