create-evda 0.1.7 → 0.1.8

package/CHANGELOG.md

@@ -4,6 +4,15 @@ Plain-English notes on how Iris behaves differently after each version. Not a co
 
 ## Unreleased
 
+Your phone can join your EVÐA. `evda pair` on the computer your record is on shows a one-time code
+and a QR link; it works once, for 10 minutes, and the phone gets only the parts you name (the
+journal by default). `evda sync` adds the phone once it has used the code, takes in what it wrote,
+and sends what changed; a note written on the phone lands under the day, in your words. `evda
+devices` lists what is paired and `evda remove <device>` removes one: it adds nothing more and
+receives nothing new. You can also ask your AI to pair a phone (`evda_pair_device`). Pairing goes
+through a relay that cannot read what it carries, and needs Node 22.13 or newer; everything else
+still runs on Node 20.
+
 Organizing is on from the start. Setup installs the morning organize on a Mac (a launchd job that
 runs your own Claude each morning at 8:00, or when the computer wakes), says so in one line, and
 offers off: answer no during setup, pass `--no-routines`, or later run `evda routine morning

package/README.md

@@ -91,9 +91,12 @@ apply places only what is new, in the record's own folders.
     evda_write_skill       writes or revises a skill at .claude/skills/<name>/SKILL.md. Never outside that folder, never a rule about your life
     evda_create_subrecord  an EVÐA inside this one, with the four roles and its own AGENTS.md, then doctor. Your evda.json changes only on bounded with confirmed: true
     evda_doctor            evda doctor, as a report
-    evda_check_update      whether newer EVDA tooling exists. The only tool that reaches the network
+    evda_pair_device       a one-time code and QR link for your phone, and what to do on it; the phone gets only the parts named
+    evda_sync_devices      adds a phone that used its code, takes in what your devices wrote, sends what changed
+    evda_devices           the devices paired with your EVÐA and what each reads
+    evda_check_update      whether newer EVDA tooling exists
 
-Every write appends, refuses anything shaped like a password, key or token, and says the path it wrote. The one call that leaves this machine is `evda_check_update` asking the npm registry for a version number; it carries nothing from the record and installs nothing, and the update itself is a command you run in a terminal. `evda connect` prints the setup for your record, with its path filled in:
+Every write appends, refuses anything shaped like a password, key or token, and says the path it wrote. Two kinds of call leave this machine. `evda_check_update` asks the npm registry for a version number; it carries nothing from the record and installs nothing, and the update itself is a command you run in a terminal. The device tools talk to the relay that carries your EVÐA between your own devices, and everything they send is sealed here first: the relay cannot read it. `evda connect` prints the setup for your record, with its path filled in:
 
 ```bash
 claude mcp add --scope user evda -- /path/to/node /path/to/evda.mjs mcp ~/my-evda   # Claude Code

package/bin/evda.mjs

@@ -26,7 +26,7 @@ import { holderOf, HOLDER_KINDS } from "../lib/manifest.mjs";
 import { EvdaError, isEntry } from "../lib/errors.mjs";
 import { publishCommand } from "../lib/publish.mjs";
 import { checkForUpdate, summarize, stampInstalledVersion } from "../lib/update-check.mjs";
-import { planCircles, coverage, declare, deviceCircles, planBeside } from "../lib/circle-plan.mjs";
+import { planCircles, coverage, declare, deviceCircles, planBeside, defaultParts } from "../lib/circle-plan.mjs";
 import { circleIndex, grantView } from "../lib/filechanges.mjs";
 import { mountRoot } from "../lib/declarations.mjs";
 import { excluder } from "../lib/sync-rules.mjs";
@@ -35,6 +35,7 @@ import { note, releaseNote, ownerSearch, readContext, readersFor, describeReader
 import { runHook } from "../lib/guard.mjs";
 import { markdownFiles } from "../lib/circles.mjs";
 import { refuseSecrets, message as messageTool, replies as repliesTool } from "../lib/tools.mjs";
+import * as pairing from "../lib/pairing.mjs";
 
 const HELP = `evda: operate an EVDA. The files are the truth; this is optional.
 
@@ -112,6 +113,14 @@ const HELP = `evda: operate an EVDA. The files are the truth; this is optional.
                                  add the preset's folders and manifests. Only adds: an existing
                                  manifest that differs is a CONFLICT and is left as it is
   evda preset diff <id> [dir]    what the preset has that this record does not
+  evda pair [dir] [--name phone] [--parts journal[,people]] [--json]
+                                 a one-time code (and a QR link) for a phone to join this EVÐA. It
+                                 works once, for 10 minutes, and gives the device only the parts named
+  evda devices [dir] [--json]    the devices paired with this EVÐA, and what each reads
+  evda remove <device> [dir]     remove a device: it adds nothing more and receives nothing new
+  evda sync [dir]                add devices that used their code, take in what they sent, send what
+                                 changed. Pairing needs Node 22.13 or newer; --relay <url> for another relay
+                                 --json on pair, devices, remove and sync prints data for an app, no ids
   evda status [dir]              one screen summary
   evda publish public [dir] --out <dir> --key <seed file>
                                  the public circle as a signed plaintext export; refuses (exit 2) on a
@@ -123,6 +132,10 @@ const HELP = `evda: operate an EVDA. The files are the truth; this is optional.
                                  circles and grants roles and their folders; moves and changes no file.
                                  A circle rooted at "" is written as the root itself, and a circle
                                  already declared keeps its id, release, rules, mount and policy
+  evda circles default [--dry-run] [--json] [dir]
+                                 split a record that has no parts into the default two: journal (the
+                                 day files and captures) and private (everything else). A record that
+                                 has parts is left as it is. --dry-run says what it would make
   evda circles check [--plan <file>] [dir]
                                  every syncable file in exactly one circle (CHECKED n files); fails on a
                                  file no circle covers, and on a symlink, iCloud stub or oversize file.
@@ -172,7 +185,7 @@ function isDirArg(a) {
 }
 
 // `--name value` or `--name=value`. The value of a `--name value` pair is not a positional.
-const VALUE_FLAGS = ["to", "kind", "name", "role", "by", "as", "model", "project", "hour", "weekday", "out", "key", "plan", "device", "shadow", "record-id", "env-file", "port", "host", "public-url", "log", "lifeline", "ttl"];
+const VALUE_FLAGS = ["to", "kind", "name", "role", "by", "as", "model", "project", "hour", "weekday", "out", "key", "plan", "device", "shadow", "record-id", "env-file", "port", "host", "public-url", "log", "lifeline", "ttl", "parts", "relay"];
 function flagValue(args, name) {
   const eq = args.find((a) => a.startsWith(`--${name}=`));
   if (eq) return eq.slice(name.length + 3);
@@ -492,6 +505,41 @@ async function main(argv) {
       return 0;
     }
 
+    case "pair": {
+      const { dir } = pickDir(args);
+      const r = await pairing.pair(dir, { name: flagValue(args, "name"), parts: flagValue(args, "parts"), relay: flagValue(args, "relay") });
+      // --json is for an app (the EVÐA Mac app, HQ-1925): the code and its QR link, and nothing with an id.
+      if (args.includes("--json")) console.log(JSON.stringify({ name: r.name, code: r.code, qr: r.qr, computer: r.computer, expiresAt: r.expiresAt, parts: r.parts }));
+      else for (const line of r.lines) console.log(line);
+      return 0;
+    }
+
+    case "devices":
+    case "sync": {
+      const { dir } = pickDir(args);
+      const relay = flagValue(args, "relay");
+      if (args.includes("--json")) {
+        console.log(JSON.stringify(cmd === "devices" ? await pairing.deviceData(dir, { relay }) : await pairing.syncData(dir, { relay })));
+        return 0;
+      }
+      const lines = await pairing[cmd](dir, { relay });
+      for (const line of lines) console.log(line);
+      return 0;
+    }
+
+    case "remove": {
+      // The device's name comes first and is never read as the record, even when a folder by
+      // that name sits in the working directory.
+      const values = new Set(VALUE_FLAGS.map((n) => args.indexOf(`--${n}`)).filter((i) => i >= 0).map((i) => i + 1));
+      const at = args.findIndex((a, i) => !a.startsWith("--") && !values.has(i));
+      const name = at >= 0 ? args[at] : flagValue(args, "name");
+      const { dir } = pickDir(at >= 0 ? args.filter((_, i) => i !== at) : args);
+      const lines = await pairing.remove(dir, name, { relay: flagValue(args, "relay") });
+      if (args.includes("--json")) console.log(JSON.stringify({ removed: String(name).trim(), lines }));
+      else for (const line of lines) console.log(line);
+      return 0;
+    }
+
     case "doctor": {
       const { dir, via } = pickDir(args);
       return doctor(dir, { via }).exit;
@@ -839,6 +887,16 @@ async function main(argv) {
         console.log(`wrote ${written.length} files: ${written.map((p) => relative(dir, p)).join(", ")}`);
         return 0;
       }
+      if (sub === "default") {
+        // The default parts (HQ-1925), for a record that has none: the app's one button, on the
+        // owner's yes. --dry-run is the question and writes nothing.
+        const r = defaultParts(dir, { dryRun: args.includes("--dry-run") });
+        if (args.includes("--json")) { console.log(JSON.stringify(r)); return 0; }
+        if (r.declared) console.log(`Split into parts: ${r.parts.join(", ")}. Nothing in your files moved.`);
+        else if (r.needed) console.log(`Not split into parts yet. Saying yes makes: ${r.parts.join(", ")}. Nothing was written.`);
+        else console.log(`This EVÐA is already split into parts: ${r.parts.join(", ")}. Nothing was written.`);
+        return 0;
+      }
       if (sub === "check") {
         const evda = openEvda(dir);
         // Without --plan, the plan kept beside the circles (`<circles role>/plan.json`) says what is
@@ -855,7 +913,7 @@ async function main(argv) {
         if (r.checked === 0) { console.log("FAIL CHECKED 0: nothing was examined"); return 1; }
         return r.problems.length ? 1 : 0;
       }
-      throw new EvdaError("circles needs plan, declare or check", { exit: 2 });
+      throw new EvdaError("circles needs plan, declare, default or check", { exit: 2 });
     }
 
     case "parity": {

package/create-evda.mjs

@@ -3,7 +3,7 @@
 //
 //   create-evda <dir> [--agent-name NAME] [--owner NAME] [--purpose TEXT] [--voice TEXT]
 //                     [--platform claude|chatgpt|gemini|cursor|other] [--training-off] [--yes]
-//                     [--filing everything|asked] [--no-prompt-hook]
+//                     [--filing everything|asked] [--no-prompt-hook] [--no-parts]
 //                     [--name NAME] [--layers record,ledger[,circles]] [--preset ID|none] [--force]
 //
 // On a terminal, any setup answer not given as a flag is asked, one question at a time, and setup
@@ -13,7 +13,10 @@
 //
 // Writes the manifest, the operating layer with the owner's answers in its owner section, the
 // loaders for the tools that do not read AGENTS.md on their own, the corpus, the ledger, and
-// .evda/. Then runs `evda doctor` on what it wrote. It creates no example notes: an empty record
+// .evda/. Splits the record into its default parts (HQ-1925): journal, the day files and captures,
+// and private, everything else, both held by this computer, so a phone can be added with no
+// terminal step (--no-parts leaves it unsplit, for parts declared by hand). Then runs `evda doctor`
+// on what it wrote. It creates no example notes: an empty record
 // that fills with a real life is the product. The one file it writes under record/ is today's
 // daily file holding a true event, the record's own creation, so the first session has something
 // dated to read and the owner sees where their words go.
@@ -35,7 +38,8 @@ import { installHook } from "./lib/hooks.mjs";
 import { applyPreset, listPresets, planLines, presetIds, NONE } from "./lib/presets.mjs";
 import { FILING_MODES } from "./lib/day-file.mjs";
 import { installPromptHook } from "./lib/hooks.mjs";
-import { PLATFORMS, PLATFORM_KEYS, LOADERS, DESKTOP_FILESYSTEM, DICTATION, DEFAULT_AGENT_NAME, platformKey, fillOwnerSection, aiLine, interview, trainingSection, termsSection, readerFor, INTRO } from "./lib/setup.mjs";
+import { defaultParts } from "./lib/circle-plan.mjs";
+import { PLATFORMS, PLATFORM_KEYS, PARTS_LINE, LOADERS, DESKTOP_FILESYSTEM, DICTATION, DEFAULT_AGENT_NAME, platformKey, fillOwnerSection, aiLine, interview, trainingSection, termsSection, readerFor, INTRO } from "./lib/setup.mjs";
 import { describeReaders, parseReaders } from "./lib/readers.mjs";
 
 const HERE = dirname(fileURLToPath(import.meta.url));
@@ -65,13 +69,13 @@ const FOLDER_TYPES = {
   messages: "message",
 };
 
-const USAGE = `usage: create-evda <dir> [--agent-name NAME] [--owner NAME] [--purpose TEXT] [--voice TEXT] [--platform ${PLATFORM_KEYS.join("|")}] [--training-off] [--filing everything|asked] [--no-prompt-hook] [--yes] [--name NAME] [--kind person|agent|company] [--id ATLAS-ID] [--layers record,ledger] [--skill] [--routines morning,weekly] [--preset ${presetIds().join("|")}|none] [--use] [--no-pointer] [--no-guard]`;
+const USAGE = `usage: create-evda <dir> [--agent-name NAME] [--owner NAME] [--purpose TEXT] [--voice TEXT] [--platform ${PLATFORM_KEYS.join("|")}] [--training-off] [--filing everything|asked] [--no-prompt-hook] [--no-parts] [--yes] [--name NAME] [--kind person|agent|company] [--id ATLAS-ID] [--layers record,ledger] [--skill] [--routines morning,weekly] [--preset ${presetIds().join("|")}|none] [--use] [--no-pointer] [--no-guard]`;
 
 export function parseArgs(argv) {
   const opts = {
     layers: ["record", "ledger"], force: false, name: null, owner: "", kind: "person", id: null, pointer: true, use: false,
     yes: false, trainingOff: false, agentName: null, purpose: "", voice: "", platform: null, platformName: null,
-    skill: null, routines: null, preset: null, guard: true, filing: null, promptHook: true,
+    skill: null, routines: null, preset: null, guard: true, filing: null, promptHook: true, parts: true,
   };
   const args = argv.flatMap((a) => {
     const eq = /^(--[a-z-]+)=([\s\S]*)$/.exec(a);
@@ -92,6 +96,7 @@ export function parseArgs(argv) {
     else if (a === "--skill") opts.skill = true;
     else if (a === "--no-guard") opts.guard = false;
     else if (a === "--no-prompt-hook") opts.promptHook = false;
+    else if (a === "--no-parts") opts.parts = false;
     else if (a === "--filing") {
       opts.filing = value(++i, a).trim().toLowerCase();
       if (!FILING_MODES.includes(opts.filing)) throw new EvdaError(`--filing takes ${FILING_MODES.join(" or ")}, got ${args[i]}`, { exit: 2 });
@@ -302,6 +307,12 @@ export async function main(argv, io = null) {
     for (const l of planLines(plan)) log(l);
     log("");
   }
+  // The default parts, after the preset so its folders exist, and before doctor so doctor reads them.
+  if (opts.parts !== false) {
+    const parts = defaultParts(dir);
+    log(parts.parts.includes("journal") ? PARTS_LINE : `parts: ${parts.parts.join(", ")}`);
+    log("");
+  }
   const report = doctor(dir, { out: log, via: "create-evda" });
   if (report.exit !== 0) {
     console.error("\ncreate-evda wrote the layout but doctor does not pass on it. That is a bug in create-evda; the output above says where.");