Three complete jobs
Start with work that needs a decision.
The value appears when another person reviews the artifact, an agent revises it, and a named reviewer closes the loop.
Designed launch page
Review the real visual hierarchy, promise, evidence labels, and calls to action before release.
Open live artifact →Decision-oriented research brief
Challenge sources and inference strength, then approve the recommendation and its limits.
Open live artifact →Living status report
Keep changing metrics, risks, owners, and decisions at one URL across recurring reviews.
Open live artifact →Run the complete loop
Follow the publish, attributable feedback, focused revision, and named approval procedure.
Read the workflow and source →Use one
Publish with the workspace default.
The example configurations intentionally omit access fields so cloning one never widens visibility without your decision.
git clone https://github.com/derive-to/derive.git cd derive/examples/launch-page derive login derive publish
Then invite a real review. Select the intended link role in Derive, ask a reviewer to comment on the exact output, let a compatible agent address every thread, and approve only the resulting named version.
Proof standard
What we will and will not call evidence.
Official samples stay labeledIllustrative metrics, companies, and scenarios are never presented as customer results.
Customer stories require consentA real case names the workflow, baseline, revisions, outcome, and limits its participant approved for publication.
A link alone is not adoptionSuccess means publish → non-author feedback → revision → named approval, repeated in real work.