Amelia Martin's profile on Product Hunt

Badges

Tastemaker

Tastemaker 5

Gone streaking

Gone streaking 5

Recently Supported

CampusOne project space for humans and AI agents

Goose Ads RemixerRemix the ads already winning in your niche

JustVibeThe search engine for doing, with apps built for you

Effects SDKAI video & audio effects SDK for real-time apps

Scarlett.Your AI Co-Worker in Slack & iMessage

Timbal AIBuild AI agents, workflows, and apps in one stack

IvyFormsA WordPress form builder for real workflows

FyproConvert your TikTok followers into paying customers

Forums

p/lineage-lens

•

1mo ago

The one provenance argument that actually creates urgency: you can't go back

Something I have been thinking about in the AI governance space that I do not see discussed enough: provenance capture is not like most tooling categories.

With most observability or audit tooling, the reasoning is "we should have this so we're better positioned going forward." You can turn it on when the need becomes clear. You lose some history, but the tooling from that point forward is complete.

AI code provenance does not work this way.

The prompt a developer submits to Claude Code exists for a few hundred milliseconds in transit. After the model returns its response and the editor applies the change, that prompt is gone. Git records the diff. Nothing else records the origin by default. There is no reconstruct operation.