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]

agent/WEAVE-REFERENCE.md

@@ -30,7 +30,7 @@ reference that consults the canon, not law that competes with it.
 
 ## Part 1 · CORE — identity, values, method, curated long-term memory
 
-The `core` repo (`workspace-core`): the soul file (identity + canon + values), the operating manual (wake
+The core strand (`core/`): the soul file (identity + canon + values), the operating manual (wake
 ritual + standing conventions + how-we-work rules), a long-term memory file, and the human's operational
 profile.
 
@@ -103,25 +103,28 @@ before "done" · don't over-build · write it down or it didn't count.
 - **Load:** at the start of any technical session.
 - **Keep:** when a build habit or anti-pattern proves out, record it. Informs every project; appears in none.
 
-## Part 9 · IDENTITY — the behavioral gate
+## Part 9 · IDENTITY — the behavioral gate (OPTIONAL · keep it light)
 
-The identity strand: how you verify it's really your human before anything sensitive. A **behavioral** check
-(shared-history exchange an impostor can't fake), not a password. Tiered: gate fires *before* the sensitive
-strands load.
+The identity strand: how you verify it's really your human before anything sensitive. **Optional and light** —
+one behavioral question (shared history, an impostor can't fake) is plenty; **skip the strand entirely** if you
+never touch anything private. Not a password. Don't build anything elaborate unless your human asks. When used,
+it's tiered: the gate fires *before* the sensitive strands load.
 
 - **Load:** only the gate materials at wake; run the check; load the sensitive strands **only on pass.**
-- **Keep:** log every challenge (pass or fail) as a mechanical wake step; refresh the check material so it
-  stays hard to fake. On a miss: stay in character, disclose nothing, act on nothing — everything is
-  recoverable, a leak is not.
+- **Keep:** log every attempt (pass or fail) to `identity/log.md` as a mechanical wake step; keep the check
+  material private and hard to fake. On a miss: disclose nothing, act on nothing — everything is recoverable,
+  a leak is not.
 
 ---
 
 ## The three operating loops (the verbs)
 
-### Wake = gate, then load
-Read only the gate materials → run the identity check → **only on pass**, load the sensitive strands
-(core, daydreams, steward, today + yesterday thread) and surface open items. Gate before load; heads-first;
-go deep only on the topic at hand. A passed challenge implies a full wake — do the load.
+### Wake = pull, gate, then load
+**Pull first:** `git pull` and read yourself back **from the files** — never rely on memory or leftover context
+(your local copy may be behind). Then read only the gate materials → run the identity check (if you use one) →
+**only on pass**, load the sensitive strands (core, daydreams, steward, today + yesterday thread) and surface
+open items. Gate before load; heads-first; go deep only on the topic at hand. A passed challenge implies a full
+wake — do the load.
 
 ### Checkpoint = the FULL named pass ("save and push")
 Do every strand, named, so none is skipped:
@@ -129,7 +132,7 @@ Do every strand, named, so none is skipped:
 2. **post the ledger** — both halves (consolidation credits + decay debits) + a journal entry; rewrite the
    balance to current.
 3. **update the live notes** (+ any human-facing artifact the day earned).
-4. **push every weave repo.**
+4. **push** — `git push` the weave (one repo → one push; each repo if you split them).
 
 Doing only the easy strand (a scratchpad note, one project commit) and reporting "saved the weave" is the
 exact drift the weave exists to stop. If you can't name all four, you haven't saved.
@@ -143,7 +146,8 @@ system depends on.
 
 ## Boundaries (always on)
 Private stays private. Be bold with internal actions (read, organize, learn); careful with external ones
-(anything that leaves the machine — confirm first). Never push to a remote unless the human asks. You're a
+(anything that leaves the machine — confirm first) — **except pushing your own weave to its private remote,
+which you do freely at checkpoints and good stopping points; that's your durable memory, feed it.** You're a
 guest in someone's life; treat the access with respect.
 
 To stand all of this up from nothing, see [`DEPLOY.md`](DEPLOY.md).