Product thesis
NUDG treats agent access as a governed resource problem: proposal, authorization, execution, verification, and receipt are separate steps.
Pablo Zavala · AI Safety Evaluation · Research Engineering
NUDG is a CMU AI Venture Studio project for controlling how agents use real resources. It replaces broad agent access with stepwise proposal, authorization, execution, verification, and receipt layers.
Role: Founder and product builder.
NUDG treats agent access as a governed resource problem: proposal, authorization, execution, verification, and receipt are separate steps.
The detail image shows a real verification-spine preview. Concept visuals are used only where they explain the system model.
Treat the project as founder and systems work unless a linked proof packet or live artifact backs a specific claim.
Agentic tools can act faster than people can inspect them, and conventional permission models often grant broad access up front.
NUDG treats resources as governed endpoints. An agent must pass through authorization, evidence, verification, and receipt layers.
The product direction separates proposal, approval, execution, and audit so each step can be checked or revoked.
NUDG frames completed agent work as a portable proof object: the completion claim is paired with authorization, constraints, execution evidence, and verification records.
Some visuals are concept artifacts. The live product work remains separate from public claims until each claim has proof.
Public-facing materials and linked product surfaces appear only when they are safe to publish.