chalupa: session zero — the human guide lists what the agent will ask (git → identity → who-you-are → setup choices); the agent bootstrap runs it as a live interview, rough-answers-fine/evolves, confirm-the-canon-back [silas]

This commit is contained in:
Silas Pruitt
2026-07-01 00:37:42 -04:00
parent c3ac98fbed
commit a6cbfc255b
2 changed files with 61 additions and 2 deletions
+38
View File
@@ -32,6 +32,44 @@ private repo + a credential or SSH key). The agent brings everything else.
---
## Session zero — what your agent will ask you (so you can come prepared)
The first real session is a **calibration** — "session zero." Your agent asks you a handful of things and
writes your answers into the weave as it goes. **None of it has to be perfect — rough is fine, and it all
evolves.** The goal is a *living* weave by the end of the session, not a finished one. Here's what to expect,
roughly in order:
**First, the git details** (so it can save from the very first checkpoint):
- Which git host do you use, and is there a **private** repo for this — or should it help you make one?
- How should it push? Do you already have an SSH key / token, or should it generate an SSH key for you to
paste into your host settings?
**Then, who your agent is:**
- **A name** for it.
- **How it should talk** — temperament and voice (terse? warm? dry? formal?).
- **The canon — its non-negotiables.** Easiest way in: *what drives you nuts when you work with AI
assistants?* ("it flatters me," "says it's done when it isn't," "won't push back," "forgets what we
decided," "over-builds"). Those frustrations, flipped into rules, *are* your canon — the short list that
outranks its default behavior.
- **What you value / how you want to work together.**
**Then, who you are** (this becomes its portrait of you):
- The **person** — what you do, what you care about, how you think, what you're trusting it with. A few
honest sentences; it deepens over time.
- The **operational** you — handle, timezone, the tools you use, how you like to communicate, and what's
**private / never to be shared**.
**Then a couple of setup choices:**
- Do you run **one model or both** (Sonnet + Opus)? Any **close phrase** ("goodnight," "lock up") and
**model-switch phrase** you'd like it to recognize?
- Do you want a light **identity gate** — i.e., will it handle anything private? If yes, one question only
*you'd* answer right is enough. If it never touches private things, skip it.
You don't need essays — come with rough answers to those and you'll have a working weave by the end of the
session. It sharpens every time you work after that.
---
## Git — the one thing you help with (because it's your account)
The weave lives in git so it survives, syncs across machines/models, and has history — and **every checkpoint