The evolution of a listing: record → marketplace tile → SmartCard execution object.
A SmartCard keeps the title the same, but changes what the listing can do: it becomes persona-aware, routed through governed rails (License · Sponsor · Build), and equipped with an Operator interface that produces next steps and artifacts without over-disclosing Blueprint depth.
What a SmartCard is
A disclosure-safe front door that converts a static entry into a governed decision + execution object.
- 1Persona-aware framing (same IP, role-specific header + priorities).
- 2Governed routing into License, Sponsored R&D, or Build rails.
- 3Operator interface that surfaces DoNext, Packs, and Artifacts.
- 4Kernel schema (demo-safe JSON) that your backend can index and measure.
What it is not
SmartCards are intentionally minimal. Depth lives behind governed gates (Blueprint layer).
- —Not a prettier database record.
- —Not a one-size-fits-all marketplace listing.
- —Not a claims rewrite or invention synthesis surface (that’s L2, gated).
- —Not “more disclosure.” It’s better activation with governance.