Align templates with proven-useful prize policy#93
Open
fryorcraken wants to merge 8 commits into
Open
Conversation
Encode the proven-useful model in the templates so the policy is enforced at authoring, submission, and payment time: - prizes/LP-0000.md: add a Consumer section (named consumer, accountable green-light owner, contact channel, redundancy/fallback, out-of-scope consumer shapes) required before Draft -> Open; add an Adoption win condition to Success Criteria; add the 50/50 delivery/adoption split and the consumer-unresponsive fallback to Prize Structure; add an operational- security requirement; add an "Up for fork" status. Drop the "Logos Circle: N/A" line (no default consumer type). - solutions/LP-0000.md: add an Adoption Evidence section (named consumer, contact channel, integration status, evidence link). - lambda-prize-claim.yml: add a "which release" field (full / delivery-only / adoption) for the split model. Source: the proven-useful redline of the internal process doc. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
❌ Validation failedFix before review:
Warnings (non-blocking):
Automated check. See solution template and TERMS. |
Multiple candidate consumers are optional insurance, not a hard publish requirement: adoption by any one flagged consumer meets the win condition. Reword the Consumer 'redundancy/fallback' field and the Adoption criterion to match. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The submission issue carries the whole prize timeline: opening it is the delivery signal and stakes the builder's dibs on adoption; the consumer's adoption is filled in later by editing the same submission. There is no separate builder-facing payment claim for each slice. - solutions/LP-0000.md: add a two-phase note up top (open = delivery + dibs; edit later to fill adoption); reframe Adoption Evidence as a fill-later placeholder, empty at submission time. - lambda-prize-claim.yml: remove the 'which release' dropdown. Which slice is paid is Logos/Finance's determination, not a builder self-classification. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
…sage) Adoption has two mutually-exclusive regimes depending on the prize's stage: - Testnet: a named consumer adopts it (the proven-useful gate). No usage metrics exist pre-mainnet, so a specific consumer is the proof. - Mainnet: usage thresholds (TVL / active users / volume). No named consumer; the market is the consumer. The named-consumer machinery falls away. - prizes/LP-0000.md: add an Adoption Stage field; scope the Consumer section to testnet-stage prizes; split the Adoption criterion into testnet/mainnet forms; make the split fallback note testnet-specific. - solutions/LP-0000.md: split Adoption Evidence into a testnet (named consumer) block and a mainnet (usage threshold) block; fill one, not both. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
A DeFi deliverable whose value depends on real TVL/liquidity that is also needed for mainnet launch fails both arms of the adoption XOR: testnet adoption is hollow (testnet value is unreal) and the mainnet usage criterion cannot gate something that must exist before launch. The realistic instrument is a win-win/co-venture RFP. Add the guard to the Adoption Stage section. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
… an LP Partner-as-builder (a partner integrating their own product) is the wrong fit for an LP: the competitive dibs/fork mechanics would let someone swoop in on their integration, and the partner needs committed deliver-X-get-Y criteria, not a discretionary adoption-gated prize. Route it to a light integration RFP scoped to that partner. Partner-as-consumer (third party builds, partner adopts) stays a valid testnet-LP consumer type. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The evaluation order is security-first, then customer. Operationalize it on the submission: a Customer Notified section the builder fills only after Logos confirms the security check, with a link to the message sent to the customer. We don't put unvetted code in front of a customer. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Make the gate auditable: instead of a vague confirmation, link to the comment on this issue where the Logos team gives the security green light. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updates the prize, submission, and payment-claim templates to encode the proven-useful policy: a prize is not published until a named consumer exists, and adoption by that consumer is the win condition.
Changes
prizes/LP-0000.md(prize template)Logos Circle: N/Aline — no default consumer type.solutions/LP-0000.md(submission template).github/ISSUE_TEMPLATE/lambda-prize-claim.yml(payment claim)Notes
🤖 Generated with Claude Code