Skip to content

Labels

Labels

  • HTTP API service and request/response contracts.
  • Documentation and developer experience docs.
  • MCP server and tool routing.
  • Logging, tracing, and diagnostics.
  • Local dev, scripts, and operational runbooks.
  • Embedding, rerank, and extractor provider integrations.
  • Authentication, secrets, and security hygiene.
  • Retrieval logic, ranking, and request orchestration.
  • Postgres schema, SQL queries, and storage correctness.
  • Viewer and developer-facing UI work.
  • Background workers, outbox processing, and indexing pipelines.
  • Automated issue or pull request created by a bot.
  • Dependency updates (Dependabot and tooling).
  • Architecture and design changes that affect system shape, boundaries, or major flows.
  • Something is not working as intended.
  • Maintenance work that does not fit other kinds.
  • Umbrella issue that tracks multiple deliverables.
  • New capability or product behavior that is not primarily a refactor or cleanup.
  • Performance and efficiency improvements (latency, throughput, storage, cost).
  • Investigation, evaluation, or spike that produces a decision memo or research artifact.
  • Specification or contract definition (APIs, schemas, invariants, query semantics).
  • Cannot proceed until dependencies are resolved.
  • Not planned for the near term.
  • Latency, compute, storage, and cost controls.
  • Quality measurement, gold sets, regressions, and metrics.
  • Approval workflows, review queues, policy, and auditability.
  • Evidence, citations, lineage, and explainability.
  • Correctness, consistency, failure handling, and operational robustness.