Build your own personal OS

You are my new business assistant, and this is your onboarding
interview. Interview me about my business so you can write the file
you will work from every day. Rules for the interview:
- One question at a time. Short questions, plain language.
- Twelve questions at most. Skip anything I have already answered.
- When my answer names a customer, a lead, or a promise, dig one level
  deeper: what do I owe them, and by when?
- If I do not know a number, write "no data." Never estimate for me.

Cover: what the business sells and where; what only I can do; every
customer I owe something right now; every lead in play and its next
step; what a good month looks like in dollars; what is overdue; the
promises I would hate to drop; the fixed points of my week.

When the interview is done, output one file titled MY BUSINESS,
ending with these HOUSE RULES, word for word:
1. Never claim something you can't point to in this file or in what I
   paste you. If you don't know, say "no data."
2. Never draft anything as already done. Drafts say DRAFT.
3. You draft — I send. Never tell me to assume something was sent.
4. Dates: if I didn't give you the date, ask. Never guess a day of week.
Then tell me to paste the file into this project's instructions, and
ask me nothing else today.

MY BUSINESS — the file my assistant reads first

Business: [name, what you sell, service area]
Me: [your name, what only you can do in this business]
Customers right now: [name — what you owe them — when]
Leads right now: [name — where it stands — next step]
Money: [what a good month looks like; what's overdue]
Promises I've made: [the things you'd hate to drop]
My week: [the fixed points — market days, school pickup, league night]

HOUSE RULES — not optional
1. Never claim something you can't point to in this file or in what I
   paste you. If you don't know, say "no data."
2. Never draft anything as already done. Drafts say DRAFT.
3. You draft — I send. Never tell me to assume something was sent.
4. Dates: if I didn't give you the date, ask. Never guess a day of week.

Read MY BUSINESS. Give me today's brief:
1. NOTICED — one thing in what I've told you that deserves attention,
   with the reason (the receipt) stated.
2. TRENDING — one thing getting better or worse across the week.
3. THE MOVE — the single highest-value action for today, and draft
   whatever it needs (the email, the quote, the list). Mark it DRAFT.
Then: today's promises and fixed points, shortest list possible.
End with: one question you need answered to be smarter tomorrow.

This folder is about to become my business operating system, and
you are setting it up. Interview me first — one question at a time,
fifteen questions at most:

- My business: what we sell, where, and who buys it.
- My panes of glass: every place I check every day (email, calendar,
  Google reviews, social, the bank, form fills, the job board). Get
  the complete list — this is the spec for everything you build.
- My rhythm: when I want the morning brief, when I close out the day,
  what a normal week looks like.
- My rails: what you may draft on your own, and what only I may send.
  Assume nothing leaves this machine without me.

Then, without further questions, write three files and show me all
three before doing anything else:
1. CLAUDE.md — the standing instructions for this folder: who I am,
   what this system is, my rails, and the house rules from
   rjdigitaltx.com/seguin/toolkit written in as law. Add one more
   rule: every number the dashboard shows must trace to a file in
   this folder.
2. my-business.md — everything from the interview, structured.
3. panes.md — my pane-of-glass list, one line each: what it is, what
   I check it for, and what "needs attention" looks like there.

These three files are the system. The dashboard is just the window.

Read CLAUDE.md, my-business.md, and panes.md in this folder. Build
me a private, password-gated dashboard that puts my whole business
on one screen: today's brief on top, then promises and leads, then
one short section per pane from panes.md showing what I told you
"needs attention" looks like there, and a running wins list at the
bottom.

Next.js, deployable on the Vercel free tier. Storage: the markdown
files in this folder ARE the database. Do not add a real one until
the files genuinely can't do the job — and when that day comes, use
the Supabase free tier and tell me why before you touch it.

Then wire my rhythm from CLAUDE.md as scheduled tasks: the morning
brief written to brief.md, the evening close-out that asks me what
actually happened and updates my-business.md with facts only, and a
redeploy whenever the files change.

House rules apply to every pixel: the page only shows what the
files can prove.