Skip to content
Jumpspace

Ask Questions With Evidence

jumpspace task ask returns an evidence summary, not an authoritative answer.

Basic Flow

Section titled “Basic Flow”
Terminal window
npx @jumpspace/cli task scan
npx @jumpspace/cli task ask "Where is project invitation implemented?"

The useful output is the evidence:

  • task IDs
  • source doc paths
  • match reasons
  • matched and unanswered terms
  • coverage
  • linked code and tests
  • semantic retrieval status, if enabled

Broader Recall

Section titled “Broader Recall”
Terminal window
npx @jumpspace/cli task find project invitation --mode any

find defaults to strict all-term matching. Use --mode any when orientation matters more than precision.

Semantic Retrieval

Section titled “Semantic Retrieval”
Terminal window
npx @jumpspace/cli task semantic build
npx @jumpspace/cli task semantic status --json
npx @jumpspace/cli task ask "Where does the repo handle member onboarding?" --json

The default semantic backend is local and deterministic. Dense LanceDB/ONNX retrieval is optional and falls back when dependencies are missing.

Inspect The Source Task

Section titled “Inspect The Source Task”
Terminal window
npx @jumpspace/cli task context DOC-PROJECT-001 --json

Use context when you need raw task metadata, plan state, links, and execution readiness.

Trust Rule

Section titled “Trust Rule”

If ask has weak coverage or unanswered terms, inspect the cited files or fall back to code search. Jumpspace should reduce guessing, not hide uncertainty.