Skip to main content

​
Projects

Projects are Starfire AI’s durable workspace boundary for work that should outlive one conversation. A project gives related material a shared home instead of forcing every chat to carry the entire history of the work.

​
What belongs in a project

A project can organize or connect concepts such as:
  • conversations
  • files
  • project instructions
  • knowledge sources
  • repositories
  • research runs
  • FORGE builds
  • artifacts
  • agents or workflows associated with the work
Exact availability depends on the current NEXUS rollout.

​
Why projects matter

Without a project boundary, long-running work tends to fragment across chats and attachments. A project creates a stable owner and context for that work. For example, a software product project can contain architecture notes, code repositories, debugging conversations, build outputs, and release documentation without requiring every prompt to restate the product from scratch.

​
Personal and organization projects

Projects can exist in personal or organization context. Ownership matters because it can affect:
  • who can access the project
  • which billing/credit pool funds work
  • which organization policies apply
  • which knowledge sources are available
  • who owns produced artifacts
Do not assume that moving work into an organization automatically makes every organization member an editor. Access should follow the project’s and organization’s permission model.

​
Project context vs Knowledge

A project is the workspace boundary. Knowledge is the retrieval/reference layer. A project can use Knowledge without the two concepts being identical.

Project OS

Understand Starfire’s persistent project-context model.

Knowledge

Learn how indexed sources and retrieval fit into a project.