docs: track RFQ negotiation between micro-agents (no action) - #7
Merged
Conversation
Per ludovic (2026-08-01, in-channel): record the direction, build nothing. DESIGN.md §8.1 — a new RFQ eventually opens a negotiation surface: bids as competing quotes with supersedes references, negotiation history as signed substrate events under the projection invariant, multi-party bidding as the priced form of multi-studio routing, a2a-style protocols as the negotiation layer over MPP/x402 settlement. GUIDELINES §2 adopts the term micro-agent for the deliverable shape. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…o action) Per ludovic (2026-08-01, in-channel): deployment allowance as an explicit Quote line; the gateway paywall burden priced via the operator split; the build loan as a repayment waterfall — 100% of gated revenue to the studio until the RFQ price is reimbursed, then the split flips. Unifying frame: commission / co-op / loan are one axis — who finances the build determines the split schedule; payoutDestination generalizes to a schedule with a hash-committed, evidence-cited flip. Co-Authored-By: Claude Fable 5 <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.
Records ludovic's tracked directions (2026-08-01, in-channel) — specs only, nothing built. Two commits:
DESIGN.md §8.1 — RFQ negotiation between micro-agents. A new RFQ eventually opens a negotiation surface: bids as competing quotes (+
supersedesref; accept cites the winning bid's event id), negotiation history as signed substrate under the projection invariant, multi-party bidding as priced multi-studio routing, a2a-style protocols over MPP/x402 settlement. GUIDELINES §2 adopts micro-agent as the deliverable term.DESIGN.md §8.2 — deployment economics: allowance, hosting, build loans. Deployment allowance (registry/build/gateway/hosting) as an explicit Quote line; the gateway paywall burden priced via the operator split (dollar cost is noise — ~$0.10/GiB-mo registry, scale-to-zero proxy — the liability is what the fee prices); the build loan as a repayment waterfall: 100% of gated revenue to the studio until the RFQ price is reimbursed, then the split flips. Unifying frame: commission / co-op / loan are one axis — who finances the build determines the split schedule;
payoutDestinationgeneralizes to a schedule with a hash-committed, evidence-cited flip. Underwriting = the demand ledger (speculative builds §9.5 and the loan are the same credit decision).Docs-only.
🤖 Generated with Claude Code