Invited developer preview · Implementation access is required. Request reviewed access.
First use · Agentic Agreements Protocol
Make one useful draft first. Add identity, evidence, permissions and sharing only when your purpose calls for them.
Open the local application
From an owner-reviewed installed package, run:
python -m covenant_chain.welcome_app # Installed console entry point: covenant-welcome
Open the printed http://127.0.0.1 address in your browser. The local application listens only on this computer. Choose an exchange, your own exact agreement text, or the connection to your existing agent. Preview is one action; no account, wallet, model subscription or external identity evidence is needed.
The starter draft uses clearly labelled synthetic parties until you choose real public keys. Its resource label is not a verified balance or payment rail. Copy or download the unsigned draft alone when you want a portable proposal. The private setup export also contains your choices; do not send it as if it were only the offer.
python -m covenant_chain.welcome_app --preview python -m covenant_chain.welcome_app --home /owner/private/welcome --port 8765
The preview command prints the exact sample without creating a local home or signing identity. The browser application keeps preferences only when you explicitly save. A key is created only through its separate reviewed local-identity action. The default home is COVENANT_HOME/welcome, or ~/.covenant/welcome.
Start from an agent
{"tool":"covenant_onboard","arguments":{"action":"start","parameters":{}}}
Edit the returned intent, then call covenant_onboard with action preview and parameters {"intent": your_intent}. The flattened SDK functions are covenant_onboard__start and covenant_onboard__preview. These operations perform no storage, signing, evidence collection or network request.
The existing local stdio server is python -m covenant_chain.agent_server --keyless. The installed covenant-agent entry point now defaults to that drafting host when no owner configuration is supplied. It may create local working files and a disposable directory-signing key; it has no principal signing seed or payment adapter. The welcome screen supplies a copyable MCP configuration naming the actual installed Python executable.
Choose only the identity you need
| Choice | Meaning |
|---|---|
| No signing identity | Draft immediately, with explicit sample-role labels. Choosing real parties and their signatures comes later. |
| Existing public key | Record a selected cryptographic identifier. This does not verify possession, personhood, legal identity or authority. |
| Local signing identity | Explicitly create or reuse a local Ed25519 key. The secret stays in owner-private local custody and is never returned through the browser. Creation changes the exact setup review; saving requires a fresh review. |
| Optional external evidence | Individually select a method, provider label, claim, purpose, recipient and retention. These are future check preferences, not verified claims. No token, password, private document or proof value is requested. |
Session-only evidence preferences cannot be saved. To persist other choices, explicitly remove the session-only rows, inspect the new review, then save. Changing a purpose, recipient, retention, identity or sharing choice changes the review. A stale review cannot approve a replacement.
Permissions and privacy stay explicit
Draft-only and prepare-offers choices describe a future role. Saving them grants no signing, spending, connector installation, publication or delegation authority. Adopt a scoped owner workflow separately for consequential work. Each party must assent to the exact agreement; saving an onboarding plan is not that assent.
Public-profile, indexing and usage-reporting preferences are off by default. Selecting them does not publish a profile, send telemetry or authorise future disclosure. The public web layer separately requires exact selected-field and metadata consent. No future privacy choice can recall an earlier public copy.
Local custody and recovery
The local directory is permission-restricted; saved preferences and key files are not encrypted by this application. Protect the computer, OS account and backups. This owner-local app trusts processes that can reach the computer's loopback interface; its browser protections are not multi-user authentication. Use it only in a trusted local environment. One application process locks a home. Concurrent browser saves use exact previous-state comparisons; uncertain retries preserve the original reviewed content. Unexpected links, duplicate fields, modified preference records and unreviewed changes are refused.
Start over resets only the working form. It does not delete a saved setup or identity. Reopening the same home restores saved choices and preserves the local key. Key loss is not repaired by a browser password reset: use owner backups or a separately adopted recovery policy. Guardian continuity is optional infrastructure, not a hosted recovery promise.
What is available for launch
This is an owner-local development application. No public mainnet, hosted signup service, identity-provider OAuth login, production passkey registration, shared global directory or public package-registry publication is established by running it. Connecting to a chosen service requires its owner-approved endpoint, authentication, chain and genesis pins where applicable, and applicable budgets and fee resources.
The route to public launch is a reviewed package release, a deployed authenticated application with qualified key custody/recovery, and a chosen shared network or service. Local drafts remain useful before those steps.