Teammately Docs
Docs menu

reference

Project Tools

Understand the current Project Tools asset surface and its deliberately limited public behavior.

Project Tools

Definition

Project Tools is a visible project-level Asset category intended for reusable callable capabilities. In the current product, the page presents an empty state and does not expose creation, editing, versioning, permissions, activation, or execution controls.

Harness source and dependencies remain in Harnesses. Connected knowledge remains in Reference Materials. Static Case inputs and materials remain governed by Project Input Schema and the Case.

Fields, states, or lifecycle rules

There are currently no public fields, durable states, or lifecycle actions on this page. The absence of controls is itself the verified boundary.

What to use today

Keep candidate-specific code and declared dependencies inside the Harness bundle. Use Workspace Secrets for credentials granted to the exact Harness, Reference Materials for connected knowledge, and Project Input Schema for Case inputs and materials. Do not relabel those objects as Project Tools because their ownership and evidence boundaries differ.

The empty state does not provide a Project Tool ID, activation action, persistence contract, or Harness-selection control.

Source confidence

Code-backed: the Assets layout exposes the Project Tools tab and its current route renders “No Project Tools yet.” No additional public behavior is claimed.

Found something unclear?

Report outdated, unsupported, or confusing docs so we can fix the source page.

Report a docs issue

Continue learning

Related docs

AI context