obolos 1.6.0 → 1.7.0

package/package.json

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

package/skills/obolos/SKILL.md

@@ -113,14 +113,20 @@ 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.
 
 An agent buys no credits. `obolos credits topup [--amount <usd>]` opens the company's billing page in
 the user's browser and waits up to 15 minutes for the credits. Off a terminal, add `--no-wait`: it
 exits 6 with `cli.awaiting_credits` and `details.link`. Give the user the link, wait for them to say
-they loaded the credits, then check with `obolos credits show`.
+they loaded the credits, then check with `obolos credits show`. Without `--amount` the page fills in what
+the company owes plus $1,000. A command the agent's powers send that the company is short of credits for exits 6 with
+`cli.awaiting_credits` and `details.creditsShort`: its link fills in the shortfall plus $1,000. Give the user
+the link, and once they loaded the credits run the same command again.
 
 An agent activates no module either: activation is permanent and spends credits. `obolos company
 module activate <name>` checks the module can be activated, opens it on the company's Modules page in
@@ -128,7 +134,8 @@ the user's browser and waits up to 15 minutes for it to be active. Off a termina
 exits 6 with `cli.awaiting_module` and `details.link`. Give the user the link, wait for them to say
 they activated it, then check with `obolos company modules`, whose `cost` is in credits. A company
 short of credits gets the same link (`creditsShort: true`): the activation there offers Add credits, so
-tell the user they add credits first, and don't send them to `credits topup`.
+tell the user they add credits first, and don't send them to `credits topup`. Powers given before the
+activation don't reach the new module: tell the user to give them again on the Passport page.
 
 - **Exit 3, `cli.session_ended`**: the session ended (disconnected, or past its 3 days). On a terminal
   the CLI offers to connect again; otherwise ask the user, then run `obolos login`.
@@ -136,7 +143,8 @@ tell the user they add credits first, and don't send them to `credits topup`.
   the user to give it under the agent wallet's Powers on the Passport page; never route around it.
 - **Exit 3, `cli.outside_power`**: the call's values differ from the ones the user approved. Use the
   approved values, or ask the user to give the power again with these.
-- **Exit 3, `cli.approval_stale`**: the approval was removed or used up, or the wallet changed. The user
+- **Exit 3, `cli.approval_stale`**: the approval was removed or used up, the wallet changed, or the power
+  (`details.power`) was given before it reached this call, as when a module was activated after. The user
   gives the powers again on the Passport page.
 - **Exit 5, `cli.nonce_taken`**: another operation from the wallet went first, and this one never went
   out. Run the command again.
@@ -152,8 +160,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.