Tasks And The Graph

Intent files are Jumpspace’s default memory object. In the advanced task graph, a task is a source-backed unit of workflow state parsed from Markdown.

What A Task Connects

A task can connect:

intent from a product doc, spec, ADR, or runbook
code files
tests
dependencies on other tasks
references to related tasks
external source links
acceptance criteria
durable plan state
verification records
known gaps

This lets an agent move from “what is this feature?” to “what files and checks matter?” without guessing from search results alone.

Source Of Truth

Markdown task blocks are source of truth. .jumpspace/index.json is generated by:

npx @jumpspace/cli task scan

Commit the source docs. Treat .jumpspace/index.json and mutation logs according to your team’s repo policy. The managed .gitignore block created by init ignores runtime locks, semantic retrieval caches, and one-shot bootstrap proposal files because they can be rebuilt.

Relationships

Use depends_on when one task cannot be safely executed until another is complete. Use refs for looser typed relationships such as related_to, implements, supersedes, or blocked_by.

depends_on:
  - PM-ROADMAP-001
refs:
  - type: related_to
    id: PM-RUNBOOK-004
    note: Project runbook describes manual validation steps.

Graph relationships make deterministic questions possible:

npx @jumpspace/cli task query --depends-on-transitive PM-ROADMAP-001 --no-tests --json
npx @jumpspace/cli task related DOC-EXAMPLE-001 --json

Health Checks

Use audit after metadata edits:

npx @jumpspace/cli task audit --json

Audit catches broken references, missing linked files, invalid plans, dependency cycles, and completed plan steps without evidence.

Use doctor after mutations:

npx @jumpspace/cli task doctor --json

Doctor focuses on post-change health and repair suggestions.