For knowledge workers

Every ChatGPT thread already knows your company.

Stop re-pasting your team, your quarter, your stakeholder map, and the deck from last Tuesday into every new AI chat. Mara writes a small context folder where context.md is the paste-into-any-chat block, inbox.md catches meeting transcripts and rough notes, and a 20-minute Friday ritual keeps it current so your AI doesn't go stale by Wednesday.

What your context looks like

context.mdWho you are, your team, your quarter, the people you work with. The file you paste into any new chat.
README.mdHow your context works. Day-one usage. ~2KB.
inbox.mdMeeting transcripts, Slack saves, article links, half-baked notes. Triaged Friday.
projects/decide-q3-narrative/brief.mdThe one thing you owe your team this quarter, with the context an AI needs to actually help on it.
weekly-review.mdFive prompts. 20 minutes. Updates context.md so next week's chats know what changed.
CLAUDE.mdDoubles as Cursor rules and ChatGPT custom instructions. Same file, every surface.

How it survives week two

  • No PARA on day one. You bounced off it before. The starter ships with one project, not a folder tree.
  • Capture is dumb on purpose. Everything goes to inbox.md. Triage on Friday, not on capture.
  • The Friday ritual is the heartbeat. If you skip it for two weeks, the system is dead and Mara will tell you so.

Using it

Your default is Obsidian — drop the folder into your vault, done. If you're on Notion, paste README.md first as a page; the markdown import is lossy but the structure survives. Apple Notes has no folder import; paste each file into a new folder called "starter." Voice memos work great there.

Power move: point Claude Code or ChatGPT at the folder and ask "what did I learn about pricing this month?" Plain markdown means every agent can read it.