David decided: Chose threads over projects as the profile grouping primitive

After reviewing design options, David settled on the threads framing and gave his reasoning:

i like the idea of threads more than projects because people might be speaking about philosophy or learning physics and thats not a project per say

He then instructed the agent to sketch the final design in ASCII and to ground it in the actual MCP tool definitions and system schema rather than designing in isolation. The threads primitive aligns with the existing data model (where kerra, snitch, agents, granular etc. are already tracked as threads in the seed data) and avoids excluding non-project intellectual work from the profile surface.