claw-negotiate

APOA-constrained SAFE negotiation for OpenClaw.

For the demo, a founder and an investor each use their own OpenClaw. Each person privately authorizes negotiation bounds, the two OpenClaws negotiate in a Telegram room, and the final SAFE is signed only after each human approves their own sshsign link.

The point is not that agents can chat. The point is that agents can act creatively while staying inside authority their users explicitly granted.

Demo

Watch the demo

What This Shows

• Bounded AI-agent delegation through APOA authorizations.
• Two independent OpenClaws negotiating on behalf of two humans.
• Private negotiation bounds with public offer-by-offer visibility.
• Human approval before any signature is completed.
• Executed SAFE PDF with signatures and an sshsign audit trail.

Typical Flow

1. The founder sends their OpenClaw a SAFE negotiation request with cap, check size, discount, and pro-rata limits.
2. The founder reviews the authorization card and replies GO.
3. The investor joins from their own OpenClaw with their own limits.
4. The parties create a Telegram negotiation room and bind it with /bind INV-XXXXX.
5. Both OpenClaws post offers in the group while APOA blocks out-of-bounds terms privately.
6. If a deal is reached, each human receives a private sshsign approval link.
7. After both humans sign, the executed SAFE is shared with the audit trail.

Example Founder Request

Live negotiation for Series Seed SAFE with Nora Vassileva at SD Capital.

Cap: $20M-$30M post.
Check: $500k-$1M.
Pro rata: required.
Discount: 0%

Runtime Commands

• profile shows the saved founder or investor profile.
• prepare reads a negotiation request and renders an authorization card.
• negotiate mints the APOA authorization and runs the workflow after GO.
• bind connects an INV-XXXXX negotiation to a Telegram group.
• cancel revokes an in-progress negotiation.
• doctor checks local OpenClaw, Telegram, sshsign, and env setup.

Security Model

• User bounds are stored in a per-negotiation APOA authorization.
• Offers are validated before they are displayed.
• Signing links are private DM-only.
• The SAFE is not executed unless each human signer personally approves in sshsign.
• Use dedicated Telegram bots and sshsign keys for public or production testing.
• Use a private per-chat work directory, such as /tmp/claw-negotiate/.

OpenClaw Instructions

Use this skill for SAFE negotiation requests, exact GO confirmations after a review card, profile setup messages, /bind ... in Telegram groups, and cancellation requests.

Write user-supplied Telegram or negotiation text to a per-chat file before invoking the runtime. Do not pass freeform Telegram text as an inline command argument.

Dispatch:

/bind ...
  write message to /tmp/claw-negotiate/<chat.id>/bind.txt
  python3 {baseDir}/negotiate_safe/run_safe.py bind --message-file /tmp/claw-negotiate/<chat.id>/bind.txt --chat-id <chat.id> --from-id <from.id>

/cancel, cancel, stop, abort
  python3 {baseDir}/negotiate_safe/run_safe.py cancel --output-dir /tmp/claw-negotiate/<chat.id> --chat-id <chat.id>

GO
  python3 {baseDir}/negotiate_safe/run_safe.py negotiate --output-dir /tmp/claw-negotiate/<chat.id> --chat-id <chat.id>

profile lookup
  python3 {baseDir}/negotiate_safe/run_safe.py profile

profile update or first-run identity setup
  write message to /tmp/claw-negotiate/<chat.id>/identity.txt
  python3 {baseDir}/negotiate_safe/run_safe.py setup --message-file /tmp/claw-negotiate/<chat.id>/identity.txt

new negotiation request or correction
  write message to /tmp/claw-negotiate/<chat.id>/request.txt
  python3 {baseDir}/negotiate_safe/run_safe.py prepare --message-file /tmp/claw-negotiate/<chat.id>/request.txt --output-dir /tmp/claw-negotiate/<chat.id>

For negotiate, use a long timeout. The runtime posts Telegram cards, signing links, status updates, and the executed PDF itself.