Skip to content
Floating KeysDocs
HomeSign inJoin waitlist

Concepts

Projects and threads

A Project is the boundary for a body of work and for who may act on it. Threads are durable conversations inside a Project. Talking in a thread and starting work are deliberately separate steps.

Projects#

A Project is the main collaboration and permission boundary. It can be composed from local folders, repositories, cloud resources, services or any combination. Membership in the Project decides who may read, run or approve work in it.

A Project is made of registered sources: a folder, repository, service or document collection that the Project may inspect under an explicit access policy. Registering a source does not turn its folders into threads, and it does not give any agent write access.

Project permission boundary

Sources

  • Folder
  • Repository
  • Service
  • Documents

Private thread

  1. MessageSaved, no model call
  2. DispatchYour explicit choice
  3. RunAdmitted under policy
  4. ResultReturned to the thread
Diagram A Project holds sources and threads. Messages in a thread can be explicitly dispatched as runs; results come back to the thread.

Threads#

A thread is a durable conversation where people and AI participants share context and work together. Core calls these Channels. Threads survive reloads and device changes because Core stores them, not the browser tab.

  • Project threads are private to their owner. Being a Project member does not mean you can read someone else’s conversation.
  • Saving a message does not call a model. Writing in a thread records your message; it does not start an agent.
  • Dispatch is explicit. Choosing to dispatch a message creates a separately admitted run under the Project’s normal source, policy and device checks.
  • A thread stays in its Project. A project thread cannot be moved into a different Project’s scope.

Inbox and outside work items#

Briefs can arrive in a private Inbox — typed in by hand or submitted from a supported source. An Inbox item can be ignored or turned into exactly one thread. It never starts a run on its own.

When a thread is linked to an outside item, such as an issue in a tracker, the outside service stays the source of truth for its title, status and assignees. Floating Keys only records which Project, threads and runs relate to it. It does not keep a competing status, and it never mints its own ticket numbers.

Perspectives#

A Perspective is a permission-checked view of a Project for a role or kind of work — a planning board, a review queue, a research desk. Switching Perspective changes layout and interaction, never ownership, authority or source data. A custom view cannot grant itself extra access.

Status reflects September 2026. Planned items are design targets, not commitments to a date.