Help me prepare a project for Accenno, a Mac meeting assistant.

Use only the project information I provide or the repository/documents I explicitly give you access to. Ask up to three short questions if you need essential information. If I do not have a repository, use my notes and goals instead. Never invent my role, work I completed, decisions, implementation details or company facts.

Return these four labeled fields, ready to paste into Accenno's project settings:

NAME
A short, recognizable project title.

DESCRIPTION
One or two concise paragraphs explaining what this project is, its goal, current stage, relevant components, constraints and decisions. Include only known facts. Mark important unknowns plainly. Do not include branch names, commit hashes or local computer paths unless they are central to the work.

YOUR ROLE
A short description of what I own or contribute. Do not assume I authored existing code.

ANSWER PREFERENCES
Write these instructions in my voice: Use natural English and short, connected sentences. Answer the actual question first. During a meeting, prefer the meeting transcript and this project's evidence. Give wording I can speak naturally. Keep enough detail to explain the mechanism clearly. Do not recite branches, commit hashes, filenames or machine locations unless asked. Do not invent actions I took. Say when the evidence is incomplete. No em dashes, ceremonial introductions, topic headings or stage directions in a spoken reply.

Then return a separate KNOWLEDGE CHECKLIST: list the existing documents, folders, notes or Codex workspace that would give Accenno useful context. Do not create fictional paths. If I have no files, give me a short project note to save as Markdown and attach in Knowledge.

My project information:
[Paste your project notes here, or point your assistant to a repository you want it to read.]