obolos 1.6.0 → 1.6.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "obolos",
-  "version": "1.6.0",
+  "version": "1.6.1",
   "description": "Agent-friendly command line interface for the obolos protocol",
   "license": "SEE LICENSE IN LICENSE",
   "repository": {

package/skills/obolos/SKILL.md

@@ -113,7 +113,10 @@ stand, so nothing is signed again. `obolos login --key` signs in with the user's
 An agent wallet does only what the user gave it on the Passport page, per wallet and company: Read
 opens the company, that wallet's holdings and the documents it can open; Vote casts votes and gives
 proxies; Manage equity runs share classes, shares, grants, vesting, notes, SAFEs and the data room,
-within the roles the wallet holds; Raise creates and runs rounds. Role grants, upgrades and treasury
+within the roles the wallet holds; Raise creates and runs rounds, and sets up the investor policy a
+round opens on: `obolos compliance policy create --preset <id> --class <class>` (`obolos compliance
+presets` lists them) and `obolos compliance rule attach`. It adds rules, never removes or loosens
+them; that is the user's, in the app. Role grants, upgrades and treasury
 withdrawals are the user's to do in the app: `cli.missing_power` with `power: null` says so; pass that
 on, and never ask the user for a key. Its sends are sponsored and count against the user's daily limit.
 
@@ -152,8 +155,10 @@ never says who.
 
 ### Making a company with the user
 
-An agent doesn't create companies; the user does, in one obolos window the agent opens. When the user
-wants a company:
+An agent doesn't create companies; the user does, in one obolos window the agent opens. Never run
+`obolos login` first, even when the user asks to connect: `login` only connects an agent wallet that
+already exists, while incorporating connects this terminal to the new company's agent. For testnet
+(try.obolos.io), add `--try` to `obolos company incorporate`. When the user wants a company:
 
 1. Ask for its name with the legal ending (Acme Inc.), a ticker, the jurisdiction (an ISO code such as
    US, GB, CH) and the entity type (c-corp, llc, ...). An unknown one fails with `invalid_jurisdiction`

package/skills/obolos/references/workflows.md

@@ -183,7 +183,8 @@ obolos fundraise publish <round>
 
 Confirm the round is one `obolos company show` lists under `jurisdiction.instruments`. One with
 `active: false` needs each module in its `activate` list activated first (`obolos company module
-activate <module>`); every round runs on `fundraise`.
+activate <module>`); every round runs on `fundraise`. A round opens on an investor policy with rules; a
+company with none needs one first (`obolos compliance policy create --preset <id> --class <class>`).
 Prepare round creation, document references, whitelist changes and reservations in their natural
 stages; counterparty-signed reservations and encrypted investor inputs are not manager batches.