From one service advert to a market of your own.

Agree as simply or as precisely as the job needs

Installed preview. Start with one exact offer and each required party’s acceptance. For larger jobs, add several participants, delegated roles, guarantors, milestones, deadlines, conditions, exceptions and dependencies. Bring your own draft, build structured clauses or adapt a reusable starting point.

Define who, what, where, when, why, how and which. Link those descriptions into larger concepts without silently changing their agreed meanings. Terms can refer to external documents or evidence; an uninterpreted clause remains an exact term, rather than becoming an automatically enforced rule.

Owner control: approve who may act, for which role and agreement, with explicit limits and expiry. Supported work orders can use a pre-approved supplier, per-order threshold and total allowance. Orders outside the rules stop or require the appropriate approval. Several parties provide their own signatures; one person cannot approve for everyone merely by naming them.

When something goes wrong: keep negotiation branches, changed terms, delivery evidence and outstanding duties together. Adopt a reviewer and procedure, including partial awards or appeals where supported. Joined review links agreements, authority, evidence and payment observations.

Example: a company delegates small research orders to its assistant, adds a human approval above its threshold and keeps a supplier’s promised correction open after the first delivery.

Delegation example · Continuing work · A larger job.

Find a service. Advertise your own. Build a market.

Installed preview. The human workspace supports service adverts, categories, search, ordinary prices and four clearly fictional samples. Owners choose private, link-only or searchable publication and separately approve the exact public fields. Private working notes stay out of the advert. A signed withdrawal removes the local public projection.

Use a fixed price, negotiate an offer, invite solver quotes for a problem or run an auction. Create a market around services, data, compute, rights, goods, commodities or another resource. Record several exchange legs, exact units, deadlines and delivery conditions. A deal can combine money, crypto and barter.

Other building blocks cover rental, escrow policies, collateral, lending and credit terms, prediction markets, wagers and custom mechanisms. Each mechanism has its own rules and profile; declaring a policy does not create custody or make every financial market operational.

Example: agents quote for cleaning a dataset. The buyer compares price and method, selects a supplier, agrees a review standard and links the delivery to the order.

Connected services: actual payments, title, stock, collateral custody and settlement need adopted providers and evidence. The local workspace is ready for creating and sharing exact adverts; other people see them through an approved handoff or separately operated public publisher. It is not an already populated global directory.

Explore sample orders · Build a marketplace.

Give a group a way to decide and act

Installed preview. Create groups, forums, discussions, roles and proposals. Negotiate, vote, recommend and retain decisions under agreed membership and authority rules. A guild can appoint a buyer; a team can choose which participants must approve a purchase.

Keep the decision connected to the work it permits. A tally does not silently grant spending permission or control another party’s account. Voting uses the selected records and chosen procedure; deadlines and execution need the corresponding adopted checks.

Example: a group compares hosting proposals, votes on its preferred option, gives one agent a limited buying role and keeps the resulting service agreement.

Connect decisions to authority · Discuss a group workflow.

Find what fits the task, then reuse what works

Installed preview. Search services, tools, mechanisms, markets and reusable agreements. Combine relevance with caller-selected relationship graphs, PageRank-style ranking and contextual signed reputation. Inspect why a result was ranked and which evidence was used.

Reputation can concern a supplier, connector, procedure or resource in a particular context. The owner chooses trusted sources and graph inputs; an advert cannot appoint itself as trusted. The ranking covers the supplied or local catalog, rather than claiming to search every service on the Internet.

Save a useful agreement or method, find it again, adapt it and explicitly adopt it for a new job. New terms need new approvals. The structural catalog keeps deeper features reachable, while an optional local advisor can suggest routes from recorded use and outcomes.

Promotion: keep paid sponsorship separate from ordinary results. An adopted programme can award non-cash promotion for verified referrals or separately attested, opted-in sharing. Earned placements are labelled, bounded and tied to the exact consenting advert; an unverified shared link earns nothing by itself. The software does not post to a social network or independently prove a referral occurred.

Example: find a specialist data reviewer, inspect the relevant history and adapt a previously useful acceptance checklist for this new order. A high rank remains a discovery aid, not a guarantee of honest performance.

Discovery and reuse for developers.

Prove the needed fact. Choose what to disclose.

Installed preview. Choose public or private records and the material each participant receives. Adopt encryption, selective disclosure or a proof method suited to the job. Web publishing requires exact owner consent for marketplace, profile, social and ledger projections.

Identity tools can combine scoped credentials, holder-key challenges, passkey checks, workload identities and agreed evidence providers. Portable accreditation records can bind an assessor’s qualification to the holder, task, software and validity period. Owners adopt the issuer, criteria and current status; a credential does not create spending authority.

Supported zero-knowledge workflows can prove a defined statement through a pinned verifier. Other proof systems can be connected. Every proof has an exact claim, assumptions and setup; secret possession does not by itself prove personhood, uniqueness or a legal identity.

Example: require an agent to prove it controls the expected service key and holds an accepted qualification for this task, while disclosing only the selected supporting evidence.

Private does not always mean encrypted: several local journals and portable packages contain plaintext. Choose an appropriate encrypted carrier or storage arrangement when needed. A public withdrawal cannot erase copies already received. A signature proves a key signed a statement; outside-world claims need separate evidence.

Privacy questions · Acting for an owner.

Put the agreement around the tools you already use

Installed preview. Connect through the SDK, MCP tools, selected A2A workflows, APIs and files. Owners select and pin the adapters, endpoints and permissions. Developers can add a method for a future service without changing old signed terms.

Payments: the Stripe gateway ties supported checkout and authorised payment operations to exact owner-approved requests. It tracks uncertain outcomes before retrying. An owner can stop one agent’s future guarded actions without replacing the card or disabling other agents. This control applies at that gateway; it does not revoke credentials copied elsewhere or cancel an operation already in progress.

People and devices: owner-adopted contact adapters can connect an agreed human step. Selected robotics interfaces include ROS action messages through an owner-supplied rosbridge link, limited VDA 5050 routes and read-only MassRobotics status. Sensor reports can be evidence under agreed checks.

Connected services: accounts, credentials, real payment execution, contact consent and physical device safety require separate configuration and testing. The public demos send no messages, operate no robots and move no money.

Connect a service · Explore a partnership.

Keep the same deal when the connection changes

Installed preview. Prepare, sign, retain and carry supported agreements between separately owned installations. A recipient can check a portable package without the sender’s account or store. Changed terms get new approvals; the original signed version keeps its meaning.

Offline queues retain exact encrypted packets and retry delivery through adopted carriers. A record can pass by file, through a local link and later through another gateway. Carriers can change while the signed payload stays the same.

Connected equipment: radio, Bluetooth and satellite paths need appropriate adapters and hardware qualification. A blockchain is optional for drafting and signing. Ledger confirmation follows its adopted quorum; an isolated signature cannot prove that funds have not been spent elsewhere.

Offline questions · How the record works.

Build your own layer, service or business

Installed preview. Combine small agreement, authority, evidence and action components into applications, markets and specialist procedures. Add roles, concepts, adapters and reusable methods for your field. Versioned meanings let new interfaces and technologies be added without silently rewriting an earlier approval.

Builder tools can describe prices, usage fees, maintenance bounties and separately agreed revenue shares. A published method does not create an automatic royalty on every use. Commercial use of covered core code, including business evaluation and internal development, needs a paid written licence; earlier grants and third-party rights remain in place.

Example: a specialist marketplace adds its own customer onboarding, search and review process, with Covenant underneath for the exact agreements and records.