Teammately Docs
Docs menu

reference

IDs and keys

Understand the identifiers used across Teammately projects, records, benchmarks, runs, policies, and rubrics.

IDs and keys

Definition

IDs and keys identify Teammately objects across projects, records, cases, benchmarks, runs, policies, rubrics, and administration surfaces. They matter because review context and benchmark evidence are only reproducible when the referenced objects are unambiguous.

Use this reference when a note, run, comparison, or troubleshooting path depends on matching the same project, case, standard, benchmark version, or candidate boundary.

Fields, states, or lifecycle rules

  • IDs should preserve which object a page, result, or review note is talking about.
  • Keys and identifiers may appear in URLs, metadata, manifests, admin surfaces, or internal source refs.
  • A stable ID does not imply that a public API, export format, or integration contract exists.
  • Review notes should name object boundaries, not only human-readable titles, when reproducibility matters.
  • Do not expose secrets or infer API-key behavior beyond source-backed admin pages.

IDs and keys should be read with Workspaces and projects, Assets, Run Metadata, and Permissions.

Worked example

IDs and keys boundary

01

Start

Behavior input

Scenario
A comparison note says the candidate improved but does not identify the benchmark version or candidate run.
02

Middle

Judgment into standard

ID boundary
The note should identify the benchmark version, run, candidate metadata, and changed artifact if those references are available.
03

Result

Interpretation

Interpretation
Without those identities, the comparison is weak evidence even if the score is visible.

Source confidence

Code-backed: current Project, user, workspace, Benchmark, Policy, and Rubric types show distinct opaque identifiers for those product objects. The reference does not assert that every internal identifier is accepted by a customer-facing API or safe to construct.

Related task pages

Concept / Object ModelWorkspaces and projectsLearn how Teammately organizes teams, projects, product goals, and access boundaries.Reference / Reference LibraryPermissionsUnderstand the user-facing permission boundaries for projects, reviewers, settings, and expert UI access.Concept / AssetsAssetsManage reusable project cases, worlds, project tools, harnesses, weights, comparison directions, and review screens before selecting them for benchmark work.Quickstart / Learning ManualProduct quickstartConfigure one project foundation, one benchmark slice, one expert contribution, one evaluation, and one evidence-backed improvement.Concept / Operating ManualTask indexRoute correctness work to the current project foundation, benchmark workspace, evaluation, or improvement surface.

Found something unclear?

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

Report a docs issue

Continue learning

Related docs

Object Model Workspaces and projects Learn how Teammately organizes teams, projects, product goals, and access boundaries. Reference Library Permissions Understand the user-facing permission boundaries for projects, reviewers, settings, and expert UI access. Assets Cases Understand canonical project cases, their input and materials, and how they become members of benchmark datasets.
AI context