Teleo approval workflows should support human-readable approval bundles so reviewers can approve a named packet, numbered list, or semantic label instead of copying long proposal UUIDs.
Strongest rival: Long explicit proposal IDs reduce ambiguity and are easy for scripts to apply; semantic labels can create accidental overbroad approvals if packet membership changes.
Claim
The current approval interaction forced the reviewer to approve eight 36-character proposal IDs in one message. That is brittle, hard to audit in conversation, and unfriendly to human reviewers. A better workflow should let Leo present a named approval packet with a short label, natural-language summary, exact included proposal IDs, and a digest or count receipt. The reviewer could then say 'approve the post-scarcity definition repair packet' or 'approve items 1-8 in the post-scarcity packet.' The system should resolve that phrase to exact proposal IDs, show the mapping before application when risk is high, and preserve the full UUID receipt after application. This preserves machine precision without making humans operate at database-ID level.