Inspect point-in-time fact evidence

ledgr_facts_history() returns supplied assertions retrospectively. ledgr_facts_resolve() returns only the state supported at one decision cutoff. Both functions accept an in-memory fact family or bundle, or a sealed snapshot. Results are eager and read-only. Default prints show the columns needed to interpret the selected family and operation, disclose omitted stored columns, and leave the complete $rows and $evidence members unchanged. Session-resolution knowledge_time is a presentation value derived from applicable $evidence; it is not stored in $rows.

Usage

ledgr_facts_history(
  facts,
  family,
  scope_id,
  instruments = NULL,
  from = NULL,
  to = NULL
)

ledgr_facts_resolve(facts, family, scope_id, at, instruments = NULL)

# S3 method for class 'ledgr_facts_history'
print(x, ...)

# S3 method for class 'ledgr_facts_resolution'
print(x, ...)

Arguments

facts

A fact-family object, a ledgr_facts bundle, or a sealed ledgr_snapshot.

family

Either "membership" or "sessions".

scope_id

The membership universe or session venue identifier.

instruments

Optional instrument identifiers. Valid only for membership. History filters assertions; resolution retains each distinct requested identifier, including false and unknown states.

from, to

Optional history bounds. Membership bounds are full UTC instants interpreted as [from, to). Session bounds are inclusive civil dates.

at

One full UTC cutoff for resolution. Bare dates are rejected.

x

A ledgr_facts_history or ledgr_facts_resolution result.

...

Unused.

Value

A classed list with eager tibble rows and evidence members plus serializable metadata.

Information boundary

History may include future-effective, future-known, and audit-only evidence. Resolution excludes evidence not yet effective and knowable at at. Neither result is a strategy context or a selection surface.

Errors

Invalid argument combinations raise ledgr_facts_inspection_invalid_args. Missing scopes raise ledgr_facts_scope_not_found. Snapshot inputs must be sealed and hash-valid on every call.