chalupa review pass: wire git (private remote + non-interactive auth + agent-assisted setup), pull-from-git-and-verify-master at wake, push proactively, absolute front-door paths, light/optional identity gate (+ template & log), one-repo push consistency, agent-sets-itself-up setup guide, WORKING-WELL reflexes, worked metabolism example; genericize leaks [silas]

human/1-understand-weave.md

@@ -64,7 +64,7 @@ it's re-read right when the generic instinct is about to take over.
 
 ## Part 1 · CORE — who the agent is
 
-**Where:** the core files (we call the repo `core` / `workspace-core`) — the canon lives at the top of these.
+**Where:** the core files (a `core/` folder or repo) — the canon lives at the top of these.
 
 Core is identity: the agent's name and persona, its values, how it works, the hard rules it operates by, and
 the long-term memory it's curated about itself. It's the answer to "who am I when I wake up?" The canon
@@ -162,20 +162,20 @@ observed, not assumed); **don't over-build** (fix the real problem at the right
 **write it down or it didn't count** (a working step unrecorded is just fooling around). Loaded at the start of
 any technical session, it informs every project without ever appearing in one.
 
-## Part 9 · IDENTITY — knowing it's really you
+## Part 9 · IDENTITY — knowing it's really you (optional, and light)
 
-**Where:** its own strand (a "gate").
+**Where:** its own strand (a "gate") — **optional.**
 
-The agent has access to your life. Before it does anything sensitive — discloses private context, acts on a
-consequential instruction — it should be sure it's really *you* asking, especially from an unfamiliar surface.
-Not a password (those leak and get shoulder-surfed) but a **behavioral check**: a short, natural exchange
-about shared history that an impostor can't fake and *you* answer without thinking. Ours is elaborate (a whole
-fictional town); yours can be as light as one good question only you'd answer right. The principle is what
-matters: **verify before you disclose, and gate it before the sensitive stuff even loads** — a fresh agent
-can't leak what it hasn't read yet.
+If your agent handles anything private, it should be sure it's really *you* before disclosing it — especially
+from an unfamiliar surface. The check is **behavioral, not a password** (passwords leak and get
+shoulder-surfed): a short, natural question about shared history that an impostor can't fake and *you* answer
+without thinking. **Keep it light** — one good question is plenty. The principle is the point: **verify before
+you disclose, and gate it before the sensitive stuff even loads** (a fresh agent can't leak what it hasn't read
+yet).
 
-*(If your agent never touches anything private, you can keep this minimal. But the moment it holds real
-context about your life, this is the part that keeps it from handing that to the wrong person.)*
+*(Ours happens to be elaborate — a whole fictional town — but that's a quirk of how we work, not the point;
+you almost certainly don't want that. And if your agent never touches anything private, you can **skip this
+strand entirely.**)*
 
 ---
 
@@ -192,7 +192,8 @@ confirmed you. Load "heads-first" — the condensed top of each strand — and g
 ### Checkpoint = the full pass, every time ("save and push")
 When you say **"save and push,"** the agent does the *whole* pass, naming every strand so none gets skipped:
 **(1)** thread the session (verbatim), **(2)** post the ledger — both halves + a journal entry, **(3)** update
-the live notes, **(4)** push every weave repo. The failure to guard against: doing only the *easy* strand (a
+the live notes, **(4)** push the weave (one `git push` for a single repo; each repo if you split them). The
+failure to guard against: doing only the *easy* strand (a
 quick note, a code commit) and calling it "saved." That partial save is the exact drift the weave exists to
 stop — the record rots one skipped strand at a time.