NVIDIACatProof is a member of NVIDIA Inception.Explore the program
catproof.
Get Started ↗
THE INTERACTIVE DEMO

Follow Ember.
From mystery to accountability.

Ember is our fictional invoice-triage agent. Connect the identities,
name an owner, then see what survives a source refresh.

Fictional scenario · Simulated actions · No provider calls · Resets on reload
01 The record: one business agent02 The registry: two source identities03 Governance: a preserved decision
INVOICE TRIAGE / DEMO
STEP 01 / DISCOVER

Two identities. One business agent.

A fictional invoice agent appears in two platforms. Its source identities are deliberately linked to a single business record.

CANONICAL BUSINESS RECORD

Ember · Invoice triage

Active
BUSINESS PURPOSE

Classify invoice exceptions for a finance reviewer.

ACCOUNTABLE OWNER

Owner needed

SOURCE IDENTITIES

Databricks · db-invoice-07
ServiceNow · sn-triage-12

SOURCE OBSERVATION

Invoice triage · Observed at 09:00

Explore Ember’s identity & ownership map
SOURCE IDENTITYDatabricksdb-invoice-07
SOURCE IDENTITYServiceNowsn-triage-12
CANONICAL RECORDEmber · Invoice triageOne purpose. One business record.
ACCOUNTABLE OWNEROwner needed

Illustrative relationship view. The source identities are deliberately linked in this fictional scenario.

01 / 04

This demo illustrates record governance. It does not invoke agents, enforce runtime policies, or establish compliance.