funduq's mechanisms

Six mechanisms are funduq's own inventions. Everything else funduq does is either a standard protocol carried unchanged (see the integration contract) or an implementation detail of one of these six.

Identity is an Ed25519 keypair

A provider is its keypair — a name is deliberately not an identity — and every operation that changes what funduq will serve is signed: registering, deleting, opening a link, calling for a completion. funduq has a keypair of its own, so a provider can pin the funduq it means to serve. → Details

Actor chain

A run can carry provenance: a hash-linked chain of self-signed hops recording on whose behalf, through whose hands. funduq verifies chains and carries them; it does not vouch for them — what a chain proves and deliberately does not prove is part of the mechanism. → Details

Runs and cancels are requests

Everything funduq sends a provider is a request, never a command. An offered run can be declined or refused; a cancel can be complied with or not; funduq records only the outcomes it observes and never decides on a provider's behalf. → Details

Provider quality counters

Capacity is a provider's own declaration, and funduq counts what it then observes — offers unanswered, runs abandoned, completions refused or failed — per provider, judging nothing. The counters are the record a serving layer or a policy can act on. → Details

Keep your own key (KYOK)

A run can be bound to an LLM offering so that the agent working it calls "an LLM" without ever holding the caller's credential: funduq relays each completion to the bound provider, which serves it with its own key and its own policy. → Details

Responsibility chains

Design, not implementation. When a run pauses for a human, who may answer? Responsibility chains make that an explicit, per-edge decision — each delegation edge can carry, break, or extend the right to act, with its cost and visibility bundled. → Details