Context: I'm running a company in Jinn with multiple projects active at the same time. The company -> employees -> Todos/Workflows/Notes model is great but company tends to have multiple projects and not all employees work on all projects.

Problem:
There's no project concept, and Notes/Skills/knowledge are shared org-wide only, so once more than a company as more than one project, work and context from unrelated projects mix together. So there's no clean way to:

• group work by project
• scope an employee to a project
• give each project its own working directory, tools, knowledge while still keeping company-wide knowledge shared.

Everything lives at the org level, which gets noisy fast once more than one project is in flight.

Proposal:
A first-class Project one level below the company, plus the ability to vary the existing session-launch knobs per project.

1. Project as a unit — e.g. a YAML file under ~/.jinn/projects/, mirroring how employees live in ~/.jinn/org/. A Project can:

• Group Todos and Workflows (optionally tag/filter by project).
• Have employees assigned to it, so work and context stay bounded.
• Appear on the Jinn MCP surface as project tools, so employees operate in project terms like they already do for org/sessions/Todos.

2. Per-project engine launch context (the key part), when a session runs under a Project, let the Project define:

• cwd the engine's working directory for that project's sessions (instead of always JINN_HOME). This alone gives each project its own working folder/knowledge space with no knowledge feature in Jinn.
• mcpServers MCP servers attached for that project's sessions (per-project tools / memory).
• extra env injected at spawn alongside the existing vars (per-project secrets, config, ids).

Is this something you'd consider for the roadmap? Glad to help test or spec it further