chore: initial commit of vault before dashboard work

wiki/queries/2026-07-14-best-first-skill-for-beginner.md

@@ -0,0 +1,35 @@
+# Best First Claude Skill for a Beginner
+
+#query
+
+## Question
+
+What would be the best Claude skill to give to a Claude beginner user?
+
+## Answer
+
+The corpus converges on a two-part answer:
+
+1. **The single best skill is a skill-*making* skill** — the built-in **skill-creator** (or Allie Miller's "just complain" pattern, where rambling frustration is turned into proposed skills). It is the only skill that compounds: instead of one capability, the beginner gets the habit of converting every repeated annoyance into a reusable folder-of-markdown. Konstantin's engineering version is the same idea as an automatic heuristic: *if a task took >5 tool calls, create a skill from it*. For someone who doesn't yet know what skills they need, the meta-skill bootstraps all the rest.
+
+2. **The best first *content* skill is a tone-of-voice / anti-AI-language skill.** Allie's starter set for non-engineers is tone-of-voice + brand-guidelines + anti-AI-language. It wins as a first skill because the payoff is immediate and visible (every output stops sounding like AI), it requires no technical setup — just examples of the user's own writing — and it demonstrates composition (a LinkedIn-voice skill *calling* the anti-AI-language skill), which teaches how skills work.
+
+**One important caveat from the same source:** Allie's ordering puts skills *second*. The first hour of a beginner's investment should go to the three foundation context documents (Personal Constitution, Goals, Core Business Strategy), created by letting Claude interview you — that alone moves outputs from generic to ~50% "your zone." A tone skill layered on top of those docs is far more effective than either alone. See [[personal-ai-operating-system]].
+
+**Why skills at all (vs. tools/MCP) for a beginner:** skills are authored in plain text in any language, need no developer, load only when relevant (no context blowout), and port across Claude / Perplexity / Gemini — "just folders with markdown." See [[evolution-of-agent-tooling]].
+
+## Evidence Trail
+
+- Starter skill set (tone-of-voice, brand-guidelines, anti-AI-language), built-in skill-creator, "just complain," composition example, foundation-docs-first ordering — [[2026-07-14-gap-between-ai-users-irreversible]]
+- ">5 tool calls → create a skill" auto-creation heuristic; skills as agent memory; two-stage loading — [[2026-07-14-skills-based-on-git]], [[skills-as-memory]]
+- Skills vs tools vs MCP trade-offs (no developer needed, no context blowout, portable) — [[evolution-of-agent-tooling]]
+
+## Follow-up Questions
+
+- What does a good tone-of-voice `SKILL.md` actually contain — how many writing samples are enough?
+- Reusable templates for the three foundation docs (already an open question on [[personal-ai-operating-system]]).
+
+## Changed Existing Pages
+
+- [[skills-as-memory]] — its "Next Questions" item on a starter skill set for non-engineers is now answered here; link added.
+- `index.md`, `log.md` updated.

wiki/queries/2026-07-14-network-from-standing-start.md

@@ -0,0 +1,55 @@
+# How Does an Individual Build a Network From a Standing Start?
+
+#query
+
+## Question Asked
+
+"How does an individual actually build a network from a standing start?" — the vault-level open question left unresolved by the Sebastian interview (principles offered, mechanics missing), and Eugene's own ~6-month blocker.
+
+## Answer
+
+The corpus cannot answer it yet, so this query produces two artifacts instead of a synthesis:
+
+1. **A tentative protocol** distilled from existing fragments — now at [[network-from-a-standing-start]] (pick recurring venues → sustainable cadence → lead with humanness → engineer second meetings in different circumstances → track second meetings, not contacts → let referrals replace outreach). Marked tentative throughout.
+2. **A follow-up interview instrument for Sebastian** (below) — designed to extract *biographical mechanics* rather than principles, because people give principles when asked abstractly and mechanics when asked about their own past.
+
+### Interview instrument: Sebastian, round 2
+
+**A. The bootstrap (tests whether a standing start ever existed)**
+
+1. Walk me through Virtido's first year. Where did clients #1, #2, #3 actually come from — the specific chain of introductions, person by person?
+2. Before Virtido: what network did you inherit from prior jobs or study? How much of year-one business traces back to it?
+3. If the inherited network was the seed — what would you have done without it?
+
+**B. The mechanics (turns principles into steps)**
+
+4. Month one, week one: what did you literally do? Which events, how did you find them, how did you choose?
+5. First conversations with strangers: what did you lead with? What approaches failed?
+6. The second-meeting mechanic — do you deliberately re-attend venues to re-meet the same people, or does it happen by accident?
+7. Rough funnel numbers for year one: events attended → real conversations → second meetings → clients. How long until the first referral arrived?
+
+**C. The falsification (tests "Big zero" and the protocol)**
+
+8. What did you try that failed *before* concluding online outreach is a "Big zero"? Did LinkedIn/content/email ever produce even one client?
+9. Dropped in a new city today, zero contacts: what exactly would you do in the first 90 days?
+10. Eugene isn't selling a company — he's an employed engineer building individual reputation. What's his equivalent of your business lunches, and what's the minimum viable cadence (your 2–4 days/week is a full sales motion)?
+
+### Complementary route (not yet run)
+
+Outside literature via deep research — weak-ties research (Granovetter), mere-exposure effects behind the second-meeting mechanic, and practitioner from-zero playbooks — scoped to *exclude* content marketing and cold outreach so it tests Sebastian's "Big zero" claim rather than ignoring it. Available on request; its output would ingest as a normal source.
+
+## Evidence Trail
+
+- Principles-without-mechanics gap, "Big zero", second-meeting mechanics — [[2026-07-14-sebastian-eugene-interview]]
+- Eugene's ~6-month blocker and online-tactics disagreement — [[connections-as-moat]], [[eugene]]
+- The live experiment framing (webinar as repeated exposure) — [[2026-07-14-nina-interview]], [[2026-07-14-yulia-interview]]
+
+## Follow-up Questions
+
+- Run the round-2 interview (Eugene's existing record→transcribe pipeline makes it a free new source).
+- Decide whether to run the deep-research complement.
+- Track the webinar → paid-HR-build chain as the protocol's first case study.
+
+## Did This Change Existing Pages?
+
+Yes — created [[network-from-a-standing-start]] (concept); updated [[connections-as-moat]] (open question now has a protocol + validation plan), [[overview]] (vault-level open question annotated), `index.md`, `log.md`.

wiki/queries/2026-07-22-webinar-theses.md

@@ -0,0 +1,59 @@
+# Webinar Theses — From Chat Box to Your Own Agentic OS
+
+#query
+
+## Question
+
+"I need to make some theses for the webinar (theme: 'from chatbox to your own agentic operating system'). What theses can I suggest based on what you already have?" (2026-07-22)
+
+## Answer — candidate theses
+
+Grouped by the role they play in the talk. Each thesis is one sentence you could put on a slide; the sub-line is the grounding.
+
+### The spine (what the talk claims)
+
+1. **The model isn't the product — the harness is.** Same model at every level of the demo; only the harness around it grows. The journey from chat box to OS is a journey of *harness*, not intelligence. — [[harness]], Webinar script closing arc
+2. **A chat box is an app you open; an OS is a system that runs around you.** The perspective shift is stranger → doer → yours → teammate → knows-you → always-on. — Webinar Plan through-line
+3. **Skills are the new memory.** A folder plus a plain-text note — no code — is how the assistant stops being stateless and starts sounding like you. — [[skills-as-memory]] (Konstantin ↔ Allie ↔ Eugene convergence)
+4. **Context is the scarce resource.** Every capability rung (tools → memory → skills → processes) is really a technique for spending limited context wisely. — [[context-as-scarce-resource]], [[evolution-of-agent-tooling]]
+5. **You don't buy your OS — you build it, one small tool at a time.** Tools made for exactly one person, in an evening, asked-for rather than written. — Webinar script (OS section), [[personal-ai-operating-system]]
+
+### The stakes (why now)
+
+6. **The cost of producing work is going to zero; value migrates to directing and verifying it.** Judgment, ownership, taste, and relationships are what stay yours. — vault through-line ([[code-as-throwaway]], [[product-ownership]])
+7. **The gap between AI users and everyone else compounds — and is becoming irreversible.** The person who builds their OS this week fears no release, because each new capability slots into a system that already knows them. — [[2026-07-14-gap-between-ai-users-irreversible|Allie Miller]]
+8. **The more the world is mediated by AI proxies, the more valuable real human connection becomes.** The "market of one" raises, not lowers, the price of being human. — [[connections-as-moat]] (Sebastian ↔ Allie ↔ Eugene)
+
+### The obstacles (what the audience actually hits)
+
+9. **Adoption is blocked by friction, not resistance.** People aren't against AI — the setup is. Remove three clicks and they come. — [[2026-07-14-nina-interview|Nina]], [[2026-07-14-yulia-interview|Yulia]]
+10. **Even advanced users hit structural walls: no durable memory, integrations that dead-end, drift on loose specs.** The skills rung is the corpus's answer to the first and third. — [[2026-07-21-larysa-interview|Larysa]], [[integration-dead-ends]]
+11. **Leave less room for imagination.** Every gap in your instructions gets filled — invisibly. Tight specs and frozen skills are how you keep the agent honest. — [[leave-less-room-for-imagination]]
+
+### The method (what to do)
+
+12. **Solve first, then skillify.** Don't design abstractions up front — solve the task once in conversation, then freeze the working recipe into a skill (~3 messages or >5 tool calls = it's skill time). — [[solve-first-then-skillify]]
+13. **The assistant does the research; you do the judgment.** The Insights Collector meta-punchline: this very talk was mined out of AI-processed interview notes. — Webinar Plan §3, [[2026-07-14-sebastian-eugene-interview]]
+14. **Walk in a week what took the industry three years.** One hour for foundation docs, one skill from your #1 recurring annoyance, one real file in Claude Desktop tonight. — Webinar Plan §5, [[levels-of-ai-usage]]
+
+### Honest tensions (if you want a "debates" slide or Q&A ammo)
+
+- Personal harness (Eugene) vs company-managed harness (Sebastian) — [[enterprise-ai-reality]]
+- Built-in agent memory as anti-feature (Eugene/Larysa) vs persistent context docs used happily (Allie) — [[skills-as-memory]]
+- Tight specs ([[leave-less-room-for-imagination]]) vs wide latitude ([[think-wider-not-bigger]])
+
+## Evidence trail
+
+- [[overview]] — through-line and agree/diverge map
+- Raw deliverables (not yet ingested, read directly): `raw/sources/Webinar Plan - From Chat Box to Your Own OS.md`, `raw/sources/Webinar script.md` (script ladder: Chat box → ReAct → Tools → Memory → Skills → Process → OS), `raw/sources/Ideas for webinar.md`
+- Source summaries: [[2026-07-14-skills-based-on-git]], [[2026-07-14-gap-between-ai-users-irreversible]], [[2026-07-14-everything-we-knew-about-software-has-changed]], [[2026-07-14-sebastian-eugene-interview]], [[2026-07-14-nina-interview]], [[2026-07-14-yulia-interview]], [[2026-07-21-larysa-interview]]
+
+## Follow-up questions
+
+- Which subset fits the 30-min format? (Recommend: 1, 2, 3, 7, 9, 12, 14 as the seven load-bearing ones — one per talk segment.)
+- Should theses 9–11 (obstacles) get their own station on the spine, or live inside "Do this tonight"?
+- Ingesting the three webinar deliverable docs would let future queries cite them as wiki sources instead of raw.
+
+## Changed existing pages?
+
+No concept/entity pages changed — this is pure synthesis. `index.md` and `log.md` updated.

wiki/queries/2026-07-24-non-engineer-throwaway-verification.md

@@ -0,0 +1,49 @@
+# Non-Engineer's Analog of Throwaway Verification Code
+
+#query
+
+**Question asked:** What is the non-engineer's analog of throwaway verification code ([[make-more-cheap-code]])?
+
+**Asked:** 2026-07-24 · **Status:** synthesis from existing pages (no new source)
+
+## Answer
+
+**The analog is disposable AI work whose only purpose is to attack, misread, and simulate your real deliverable before a human sees it — generated *checks*, not generated *content*.**
+
+Theo's engineer version: for every line that ships, generate 100–10,000 lines of never-shipped code that verifies it. The non-engineer's deliverables are documents and decisions — job descriptions, candidate profiles, specs, outreach emails, offer terms — so the analog is: **for every document you ship, generate several documents you never ship, whose job is to find out where the shipped one fails.** The webinar audience mostly uses AI on the *production* side (draft it for me); this points the same firehose at the *verification* side.
+
+Theo's concrete patterns map one-to-one onto the vault's HR/BA use cases:
+
+| Theo's engineer move ([[2026-07-24-youre-reading-way-too-much-code]]) | Non-engineer analog (grounded in corpus use cases) |
+|---|---|
+| Dumb-model agents try to build on your API — their failures are UX bugs in the API | Give your job description or spec to a **fresh agent with zero context** and ask it to restate who is being sought / what is being built. Where its naive reading diverges from your intent, the document is ambiguous. This is [[leave-less-room-for-imagination]] inverted: the AI's "fantasy" becomes an **ambiguity detector** — drift as diagnostic, safe because it happens in a throwaway sandbox instead of your deliverable. |
+| Test 3 theories of an ambiguous PR in parallel | Ambiguous stakeholder ask → have the agent draft **3 divergent interpretations** cheaply and compare them, instead of committing to one reading. (Directly serves Larysa's BA work — [[2026-07-21-larysa-interview]].) |
+| Generate a custom lint rule for a bug pattern you just found | Every recurring caught mistake (AI-sounding language, tone, missing salary band, unverifiable spec claim) becomes a **checker skill** that reviews future drafts. Allie's anti-AI-language skill is literally this ([[personal-ai-operating-system]]). |
+| Load-test rigs; stress the system with throwaway infrastructure | **Simulate before real users arrive:** run 10 synthetic candidate profiles through a new screening process; query the candidate knowledge base ([[2026-07-14-yulia-interview]]) with naive questions to test whether profiles are standardized enough to be findable. |
+| Red-team the sacred core with slop | Spawn an agent playing the **skeptical reader** — the picky hiring manager, the candidate deciding whether to reply, the developer misreading the spec — and let it generate the 20 objections before a human raises them. |
+| Read every signature/API; skim bodies; agent-summarize diffs | Read the **boundaries**: names, numbers, dates, commitments — the document's "signatures" — by hand; let AI cross-check the body. |
+| AI reviews code before humans do | AI reviews the document before your team/candidate does — a pre-human review step, same as Theo's. |
+
+**The method already exists in the vault — it just runs in one direction.** [[solve-first-then-skillify]] freezes proven *production* workflows into skills. This query adds the second species: **checker skills** — the correction loop you just went through (per Eugene's ~3-message heuristic) is not only a producer skill waiting to be frozen, it is also a *verifier* skill: "here is the mistake pattern; check every future draft for it." That gives the [[levels-of-ai-usage]] skills rung a dual population, producers and checkers, at zero extra conceptual cost for the audience.
+
+**What does not map.** Engineers verify against ground truth (tests pass or fail); a non-engineer's verification bottoms out in **human judgment** — there is no fuzzer for "is this offer fair." So tier D stays irreducibly human: offer terms, rejection communications, anything compliance-adjacent gets read line-by-line, exactly as Theo keeps hand-verification of shipped code. And Theo's "there's always another layer" still holds in weakened form: if you don't trust AI review of the document, have AI generate the **checklist you apply yourself**.
+
+**One-line webinar version:** *AI's first job isn't writing your document — it's breaking your document before a person does. What you ship, you still read; what checks it, you never read.*
+
+## Evidence trail
+
+- Engineer-side concept and all mapped patterns — [[make-more-cheap-code]], [[2026-07-24-youre-reading-way-too-much-code]]
+- Non-engineer use cases (job descriptions, profiles, sourcing, candidate KB) — [[2026-07-14-nina-interview]], [[2026-07-14-yulia-interview]]
+- BA/spec ambiguity and invisible drift — [[2026-07-21-larysa-interview]], [[leave-less-room-for-imagination]]
+- Checker-skill precedent (anti-AI-language) — [[personal-ai-operating-system]], [[2026-07-14-gap-between-ai-users-irreversible]]
+- Method being extended — [[solve-first-then-skillify]], [[levels-of-ai-usage]]
+
+## Follow-up questions
+
+- Does a "checker skill" need its own rung in the webinar ladder, or is it a footnote on the skills rung?
+- Nina's finding that *the transcript matters more than the summary* cuts against agent-summary review — for non-engineers, when is the raw artifact (transcript, full document) the only safe thing to read? (Cousin of the Theo/Dax-vs-Eugene tension logged in [[leave-less-room-for-imagination]].)
+- Is there a measurable claim for the webinar — e.g., "one fresh-agent misread test catches X% of spec ambiguities"? Currently pure assertion by analogy. Status: tentative.
+
+## Changed existing pages?
+
+Yes — light pointers only: [[make-more-cheap-code]] (next-question answered with link here), [[leave-less-room-for-imagination]] (drift-as-diagnostic inversion noted in Next Questions), plus `index.md` and `log.md`.