functoryWhat shipped
Public reviews to create a quality signal, an in-app channel to talk to us, clear error labeling for failed runs, embedded run history in the editor, and strict versioning on republish.
Why it matters
Trust compounds when good work is discoverable and feedback loops are fast. Versioning keeps releases auditable and reversible.
Notes on design
We optimized for signal over noise with simple ratings and structured comments. Version IDs are immutable and linked to run history.
What’s next
Reply notifications, flagged review workflows, and author replies that can be marked as helpful by the community.