01-projects/personal-brand/ship30

locked topics and question bank

2026-10-07·plan·status: active·source: founder iMessage 2026-10-07 20:46 ET ("Yes. Good to lock it in.")
ship30writingtopics

Ship 30: locked topics + question bank

Umbrella (founder's words)

"How to make agents useful to all sorts of domains." The lean is enterprise agents, which trail cutting-edge work because they need governance controls and have to be made available inside trusted platforms. That is why Snowflake and Anthropic are a good vendor focus.

The 3 topics (LOCKED 2026-10-07; Ray proposed them, founder approved)

  1. Agents that actually work: the plumbing behind useful agents (the harness around the model, testing, quiet failures). Case study: Ray.
  2. Agents + data platforms: semantic layers, definitions in git, agent-ready data, governance inside trusted platforms (Snowflake, Anthropic). phData lane.
  3. Which jobs to give agents first, by domain: small business admin, healthcare billing, family logistics, kids' learning. [[agentify-3000-series|Fifth-job series]], Agentify 3000 scoring.

Question bank (first-hand, from a 2026-10-07 Claude Code activation session on the agentic software development lifecycle, ~30 advanced users)

Context: spec-driven development, where the agent writes intent.md, plan.md and test.md.

# Question Founder's answer in the session Ray's angle from our own build
Q1 Are those documents thrown away? Yes Our dispatch briefs are single-use too. What survives is the decision log and the tests.
Q2 Isn't there long-running context? How is it kept? How do you capture tacit knowledge? A knowledge base. For enterprises, how to wrangle that context is still open. Vault + working-context + memory files; corrections become rules. Enterprise version = governance (Topic 2).
Q3 Is spec-driven development overkill? It makes sense for features, but bug fixes? (open) Scale the ceremony to the size of the change. A one-line brief plus a failing test is a spec.
Q4 Agent code reviews catch things outside the spec. Do you triage them into a new task, send the work back to the builder, or add a test that catches it earlier? (open) Tonight's live example: a fresh critic found defects the brief never named, so they went back to the builder, each with a test, and the loop is capped (breaker).

Rule: activation calls are a source of questions. Capture them first-hand and write about them. Do not persist client names or attendee details.

2026-10-08 addition: practitioner signal (LinkedIn DM, former Progress SQL analyst from the Mammoth engagement)

2026-10-08 addition: AWS AI-DLC vs Claude AI-native SDLC playbook (founder-shared)

2026-10-09 addition: activation call #4 (advanced Claude Code working session, 2026-10-08; founder's first-hand notes, no client details)

Pains heard, clustered: