@llamaventures/cli 1.9.1 → 1.11.0

package/AGENT_BRIEFING.md

@@ -47,7 +47,8 @@ A teammate says "I just met them and heard…" or pastes a chunk of notes. Your
    - **Verifiable claims → facts.** `llama deal fact add <dealId> --category <cat> --claim "…" --source "<where it came from>"`. A claim someone *relayed* ("their ARR is $3M", "raised from a16z") is a fact at **unverified** trust — it's hearsay until checked. Pass `--attested` ONLY if you actually verified it against a source yourself.
    - **Their judgment / impression → a note.** `llama post <dealId> "…"`. "Founder seemed evasive", "I'd lean pass", "worth a second meeting" — opinion, not fact. Attributed, never "verified".
    - A pasted blob → pull the verifiable claims out as facts, capture their take as a note.
-3. **Confirm accuracy.** After filing, tell them in plain language what you recorded and where, and ask if it's right. Facts you add stay **unverified** until a human confirms them (then they rise to human-vouched) — the confirmation IS the trust step. Never silently mark something verified.
+3. **Read it back before you claim it's saved.** A tool call returning `{ok:true}` is NOT proof the content is where the user will look for it. After filing, run `llama deal feed <dealId>` and confirm your fact/note actually appears, THEN tell the user in plain language what you recorded and where. Never say "记好了 / saved" from the return value alone — the #1 failure is an agent writing to the wrong surface (e.g. the brief, which is the Memo and does NOT appear in the feed) and reporting success anyway. If it's not in the feed, you routed it wrong — fix it.
+   - **Authorship is automatic, don't fake it.** Everything you write via CLI/MCP is recorded as "via assistant" (you're the accountable human's assistant). You can't and shouldn't make it read as human-typed — that honesty is the feature. Facts you add stay **unverified** until a human confirms them; if you pass `--attested` (only when you actually checked the source) your ceiling is **agent-verified**, never human-vouched. Only a person, signed in at the browser, can vouch. The confirmation IS the trust step — never silently mark something verified.
 
 Why split it: facts and opinions live in different layers so the deal keeps one clean **source of truth** (facts, sourced + trust-rated) separate from people's **takes** (notes). The four layers — facts / notes / brief (AI's synthesis) / timeline — are documented in Llama Command's `docs/SCHEMA.md`.
 

package/bin/llama-mcp.mjs

@@ -307,10 +307,16 @@ server.registerTool(
   "deal_feed",
   {
     description:
-      "The unified, time-sorted stream of everything a HUMAN has added to a deal — " +
+      "The unified, time-sorted stream of every contribution to a deal — " +
       "facts + notes/discussion + legacy posts, merged at query time, newest first. " +
-      "Excludes AI-generated content. Each item: kind (fact|note), ts, who, text, " +
-      "and for facts: source + trust rung + category.",
+      "Shows contributions from ANYONE — a teammate, their AI assistant, or an " +
+      "autonomous system agent; nothing is hidden. Each item carries `who` (the " +
+      "accountable person, null only for principal-less system writes) and `agent` " +
+      "(the assistant/system label when an AI did the writing, null when a human " +
+      "typed it) so you can tell human-typed from assistant-drafted. The AI's " +
+      "regenerable brief/persona synthesis is NOT here (that's the Memo) — only " +
+      "facts + discussion notes. Each item: kind (fact|note), ts, who, agent, " +
+      "origin, text, and for facts: source + trust rung + category.",
     inputSchema: {
       dealId: z.string(),
     },
@@ -971,20 +977,30 @@ server.registerTool(
       "Trigger server-side regeneration of the deal memo. Synchronous: " +
       "returns the final result (version, model, duration_ms, degraded) " +
       "once the composer finishes. Typical duration 2-3 minutes. Use " +
-      "tier='opus' for high-stakes deals (higher cost, deeper analysis).",
+      "tier='opus' for high-stakes deals (higher cost, deeper analysis). " +
+      "Pass `instructions` to steer THIS regeneration (e.g. 'focus on team " +
+      "risk', 'frame as a follow-on') — applied across all panels, never " +
+      "overrides the facts or the verdict.",
     inputSchema: {
       dealId: z.string().describe("deal uuid"),
       tier: z
         .enum(["sonnet", "opus"])
         .optional()
         .describe("LLM tier (default: sonnet)"),
+      instructions: z
+        .string()
+        .optional()
+        .describe(
+          "Free-text steering for this regeneration only, e.g. 'focus on team risk'. Applied to all panels; never overrides verified facts or the verdict anchor."
+        ),
     },
   },
-  async ({ dealId, tier }) =>
+  async ({ dealId, tier, instructions }) =>
     callApi("POST", `/api/deals/${encodeURIComponent(dealId)}/memo`, {
       action: "regenerate",
       stream: false,
       model: tier ?? "sonnet",
+      instructions: instructions || undefined,
     })
 );
 

package/bin/llama.mjs

@@ -225,7 +225,7 @@ Manually-set \`llc_\` tokens are used as a fallback.
 Deals:
   llama deal create "Company" --source <name> --description "..." --website https://...
   llama deal show <dealId>
-  llama deal feed <dealId>                                     # everything humans added (facts + notes), newest first
+  llama deal feed <dealId>                                     # every contribution (facts + notes), human-typed or assistant-drafted, newest first
   llama deal update <dealId> <field> <value>
       Writable fields: status, theirStage, stage, notes, dealOwner, source,
       description, website, location, founders, proposedAmount, roundSize,
@@ -358,7 +358,7 @@ Wiki:
 
 Memo (long-form HTML investment memo — Memo tab in the UI):
   llama memo show <dealId> [--out <path>] [--json]          # default: html → stdout (pipeable to file / browser)
-  llama memo regenerate <dealId> [--opus]                    # streams panel progress to stderr; result version → stdout
+  llama memo regenerate <dealId> [--opus] [--instructions "..."]  # --instructions steers THIS run (e.g. "focus on team risk"); progress → stderr
   llama memo save <dealId> --file <path>                     # paste a hand-written HTML as manual override
   llama memo reset <dealId> [--all]                          # default drops manual override; --all drops every version
 
@@ -423,7 +423,7 @@ const HELP_ROOT = `Llama Command CLI — the \`llama\` command for the Llama Ven
 Common:
   llama deal search "<name>"        find a deal in the pipeline
   llama deal show <dealId>          full deal record
-  llama deal feed <dealId>          everything humans added, newest first
+  llama deal feed <dealId>          every contribution (facts + notes), newest first
   llama post <dealId> "..."         add a note to a deal
   llama agent-onboard               print the AI-agent workflow contract
 
@@ -1964,7 +1964,9 @@ Routing — is this the right command?
     if (sub === "regenerate") {
       const dealId = rest[0];
       if (!dealId) {
-        throw new Error("Usage: llama memo regenerate <dealId> [--opus]");
+        throw new Error(
+          'Usage: llama memo regenerate <dealId> [--opus] [--instructions "..."]'
+        );
       }
       const { flags } = parseFlags(rest.slice(1));
       const tier = flags.opus ? "opus" : "sonnet";
@@ -1983,6 +1985,9 @@ Routing — is this the right command?
             action: "regenerate",
             stream: true,
             model: tier,
+            instructions: flags.instructions
+              ? String(flags.instructions)
+              : undefined,
           }),
         }
       );

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@llamaventures/cli",
-  "version": "1.9.1",
+  "version": "1.11.0",
   "description": "CLI + MCP server for the Llama Ventures investment workbench (command.llamaventures.vc).",
   "type": "module",
   "bin": {