Teammately Docs
Docs menu

reference

Logs & Status

Inspect contribution reviews, sessions, interviews, engagement, and operational records within the benchmark scope.

Logs & Status

Definition

Logs & Status is the benchmark-scoped operational record for Expert Contributions. It exposes reviews, review sessions and plans, interviews, expert or contribution engagement, and related activity tables. Use it to answer when work happened, which record is active, and where a stalled or disputed result came from.

Fields, states, or lifecycle rules

  • Every table remains scoped to the selected benchmark.
  • Review, session, interview, engagement, and artifact records keep separate identities and statuses.
  • Filters, sorting, and detail views change presentation without rewriting the underlying Contribution.
  • Available transcript and response detail follows the user's project permissions.

Choose the right record

  • Reviews shows review work and its Case or artifact relationship.
  • Review Sessions and plans show the bounded sequence that presented work to an expert.
  • Interviews exposes interview identity, targets, state, and available transcript detail.
  • Expert Engagement and Contribution Engagement show participation and operational progress.
  • Specialized tables can expose new-Case, output, draft-Policy, Case-specific Rubric, or review-question activity.
Expert Contribution progress summary showing unassigned, in-review, aligned, pending, and reviewed counts by assignee.

Use progress counts to locate work operationally; they do not establish whether contributed judgment was accepted.

Expert Contribution review-session table showing assignee planning state, completed sessions, result counts, task counts, and reviewers.

Open a session when you need its task and result provenance rather than inferring it from aggregate progress.

Filter and sort within the benchmark scope before comparing counts. A session, interview, review, and contributed artifact are separate objects and may have different completion times. Do not add their row counts together as a measure of unique Contributions or experts.

Provenance and diagnosis

Start from the Contribution when explaining intent, then follow its planned activity to the session, review, interview, checkpoint, and materialized artifact. Transcript or response evidence may explain a decision, but the owning Policy, Rubric, Case, or coverage surface determines the artifact's current governance status.

When work appears stuck, compare durable status with the latest task or checkpoint rather than inferring from engagement alone. An expert can open a Contribution without completing a task, and a completed interview can still be waiting for checkpoint reconciliation or materialization.

Related task pages

Task / Expert ContributionsRequest an Expert ContributionCreate a focused benchmark contribution with an accountable expert, clear objectives, selected cases, attachments, and appropriate task components.Task / Expert ContributionsComplete an Expert ContributionWork through form, chat, interview, case-review, and checkpoint tasks while keeping specialist judgment attributable.

Source confidence

Code-backed: the active Logs & Status routes define benchmark-scoped review, session, interview, and engagement tables and their detail surfaces.

Found something unclear?

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

Report a docs issue

Continue learning

Related docs

Expert Contributions Expert Contributions Coordinate benchmark-scoped expert work, attributable judgment, governed artifacts, and the decisions that move correctness forward. Expert Contributions Contribution Lifecycle and Status Interpret Contribution, activity, task, expert-runtime, and checkpoint states without inferring completion. Expert Contributions Contributed Artifacts Inspect policies, rubrics, cases, and coverage observations produced through attributable expert contribution work.
AI context