# Investigate a new task missing from semantic search

Illustrative planning brief; no automatic product import.

Illustrative case: a newly created task is not returned by tb_search_tasks immediately afterward.

## Decision

Check the saved task reference and exact structured evidence before concluding creation failed.

## Owned work

- Check the creation evidence
  - Owner role: Task owner
  - Acceptance evidence: The saved reference and operation outcome are available.
- Review context and exact evidence
  - Owner role: Agent
  - Acceptance evidence: Workspace binding and structured filtering are checked independently of semantic ranking.
- Classify the gap
  - Owner role: Support owner
  - Acceptance evidence: The conclusion distinguishes missing persistence from delayed embeddings or query relevance.

## Workflow

1. Inspect the original creation outcome without repeating the write.
2. Verify scope and use exact evidence where supported.
3. Report the semantic gap with the source limitation and observed conditions.

## Judgment

The source documents delayed semantic availability for new tasks. That is a possible explanation, not proof of the cause of every missing result.


## Illustrative missing-result diagnosis

Observed: recent task absent from topic matches.
Check first: creation reference, workspace and exact evidence.
Possible source limitation: embeddings not yet available.
Do not infer: deletion or failed creation from semantic search alone.


## Workflow questions

### Should I recreate the task?

Not before reconciling saved evidence; an uncertain search result can otherwise create duplicates.

### Does a semantic miss mean the task is deleted?

No. Search visibility, persistence and workspace scope are separate conditions.

## Product connection

The TeamBoost MCP example distinguishes a saved record from its semantic-search visibility so a search miss does not prompt duplicate creation.

Confirm account availability before adopting this manual outline.