AI Ingestion

Gemini Copilot

Status Updates

The Status Update is the atomic unit of the Parallel Ledger.

Every instance details a specific fact for a specific point in time.

Status Update Struct
%StatusUpdate{
  # The Atomic Trio (Required)
  :context_slug         # Namespace (CLIENT_A_*)
  :slug                 # Entity Identifier
  :code                 # Property (module--property)

  # Payload Values
  :status_dt            # Flexible date/time (ie: ETA)
  :status_int           # Numeric value (boolean/bigint)
  :status_slug          # Flexible slug reference
  :status_text_value    # Description or raw data
  :reported_dt          # Source system reported time
  :executed_by_slug     # Authority that initiated change

  # Audit & Lineage
  :witnessed_dt         # Appliance-assigned seal time
  :property_sequence_no # Property chain position
  :chain_hash           # Cryptographic proof
}

The Atomic Trio

Every update is defined by a composite key trio that uniquely identifies the property being tracked. The protocol uses this trio to chain historical changes and maintain the current state.

context_slug

The administrative namespace

ie: CLIENT_A_FINANCE

slug

The identifier for an entity

ie: user_1234 or vin_98765

code

The attribute being updated

ie: sensor--temp_celsius

Property-Level Chaining

The protocol tracks each code as a discrete stream of facts. If an incoming event contains multiple changes (e.g., an email and a phone number), the Partner Gateway must decompose that event into two separate Status Updates.

"By isolating properties at the point of ingestion, the Ledger ensures that every individual change is independently verifiable and historically immutable."

Cryptographic Finality

Once a Status Update is accepted by the Ledger, the protocol performs all necessary operations to:

  • Sequence: Position the update within the property's historical chain.
  • Seal: Generate a cryptographic hash proof for the update.
  • Finalize: Commit the state to both the immutable Ledger and the current-state observation table.

Next Step: Review Context Management to learn how to structure your namespaces and mandatory client-slug prefixing.