Chapter 04 : Projects: one folder, one JAY.md
Without a project, every session starts from scratch. With a project, Jay already knows the folder, the client, the tone, the history and the reference documents. In Jay, a project isn't an abstract space: it's a folder on your Mac, and everything Jay knows and remembers lives there, next to your files.
What a project is
A project, in the sessions rail, groups sessions and meetings together. It can be attached to a folder, or not.
| Project with a folder | Project without a folder | |
|---|---|---|
| What it's for | Working: Jay reads the folder, puts what it produces there, remembers things there | Grouping sessions by topic |
| What Jay reads | The folder tree (two levels), the JAY.md, and the files it opens itself | The JAY.md and the project memory |
| Where Jay writes | In the Jay/ subfolder on its own; in your other files depending on the access level | Nowhere on disk |
| Terminal, Git | Yes | No |
A project without a folder carries the "No folder" label. To attach it later, open its settings: "Put this project in a folder: its memory, documents and meetings move there."
The three components
JAY.md, the standing brief. A text file at the root of the folder, read at the start of every session in the project. It tells Jay how to work here: the client's context, the writing rules, where to put what, what it must never do. It is read in full up to 4,000 characters, about one well-filled page: beyond that, Jay cuts it off. Keep it short, and put long documents in the folder.
The Jay/ folder, Jay's footprint. It's the only subfolder Jay writes to on its own. It holds its knowledge base (Jay/knowledge: the documents, presentations, spreadsheets and meeting transcripts it produced or that you added), its memory (memory.md), the project's Design System (DESIGN.md), the brand kits, the deliverables. You can see it in Finder, open it, read it, correct it. Jay reads the rest of the folder, and only changes it according to the access level: in Ask, every write goes through a card that you accept or reject.
Memory, what was said there. Each project has its own memory, separate from the others, so your clients don't get mixed up. It fills up in two ways: when you say "remember that…", and, if you turn it on, through an automatic summary of each session when you leave it. It's off by default; the first "remember" turns it on and says so. It stays local: Jay keeps it out of Git.
| What you want | What you do |
|---|---|
| Have it remember something | "Remember that this client's reports are always in English." |
| Check what Jay knows | "What do you know about this project? Sort it into true, false, outdated." |
| Correct or forget | Ask for it, or edit Jay/memory.md directly |
| Find a past session | "Pick up what we decided last week about the budget." Jay searches your sessions and your meetings |
| Remember outside a project | In a session without a folder, "remember" writes to your global memory, read everywhere |
Linking other folders
A project has one folder, but Jay can read others. Drag a folder onto the session, or use the "+" in the message area, "Link a folder for reading". The linked folder is read-only by design: no write function and no command can reach it. It's the right way to give Jay your archive folder, a reference template or a colleague's folder, with no risk. A session can also link another of your Jay projects, for reading (chapter 15).
When to create a project
My rule: as soon as a topic comes up at least once a week, or as soon as a folder on your Mac deserves to be known by Jay. A key client, a recurring report, your industry monitoring, your LinkedIn posts, your accounting, a code project.
Three JAY.md templates to copy
Create a JAY.md file at the root of the folder, paste, adapt the brackets. Or ask Jay to write it: "create this project's JAY.md from what you see in the folder, and ask me the questions that are missing".
You are my partner on the [client] account, a [industry] company that [activity]. Contacts: [names and roles]. Current stake: [stake]. What they value: [criteria]. What annoys them: [pain points]. The folder: Contracts/ (the signed proposal), Minutes/ (one dated file per meeting), Deliverables/ (what we send them). When I ask you for an email: [tone] tone, formal address, 150 words maximum, as a draft in my mailbox, never sent. When I ask you for an analysis: start with the conclusion, then the arguments, and cite the source file. Put everything you produce in Deliverables/[YYYY-MM]/. Never change a file in Contracts/. If a piece of information is missing, look in Minutes/ before asking me.
You help me follow [industry] in order to [goal: anticipate, advise my clients, write content]. Players to follow: [list]. Priority topics: [list]. Trusted sources: [list]. Sources to ignore: [list]. For each monitoring brief: search the web, cite every source with its date, separate facts from interpretations, and end with "What this changes for me" in 3 points. Save each brief in Monitoring/YYYY-MM-DD.md. Before writing, reread the previous one so you don't repeat yourself. Ignore purely promotional press releases, unless they announce a concrete change.
You help me write my LinkedIn posts. My audience: [audience]. My promise: [what I bring]. My topics: [3 to 5 themes]. My best posts are in References/: borrow their tone, not their ideas. Rules: one idea per post, a one-line hook, short sentences, no jargon, no emoji bullet lists, no hashtags. End with an open question. Before writing, suggest 3 angles and wait for my choice. Save each approved post in Posts/YYYY-MM-DD-title.md. Never publish yourself: I publish.
Best practices
- One project per recurring topic. Avoid the catch-all project: the memory and the knowledge base would end up mixed together.
- A clean folder. Five up-to-date documents beat fifty, half of them outdated. Put the date in file names, and say in the JAY.md which ones are authoritative.
- A project fact sheet. A Jay/knowledge/fact-sheet.md file that sums up the essentials: goals, contacts, decisions made, added to the knowledge base with "Sync the folder". Update it once a month.
- Improve the JAY.md after every disappointment. If you correct the same thing twice, a rule is missing.
- Archive finished projects. The rail stays readable, ⌘K finds everything.