Skip to main content

See whether a task used project memory

Project memory is what runners learned on earlier tasks in a project. Each time Jaah starts a task, it decides whether that run gets the memory, and records the answer on the task. Read it when a task repeated a known mistake, or did better than expected, to see whether memory played a part.

Who can do this: anyone who can view the task. The row shows only once Jaah has started the task at least once.

  1. On the task board, select the task's title. Its page opens beside the board.

  2. Select the Details tab, then Summary.

  3. Find the Project memory row, under Runner. It reads like On (default) · 5 injected · 2 read · 1 cited.

  4. Read the first word: On means the run was given the project's memory, Off means it wasn't.

  5. Read the reason in brackets:

    • project: the project's own Project memory setting decided it.
    • default: the project follows the default, and the default decided it.
    • plan: your organization's plan doesn't include project memory.
    • holdout: Jaah kept this run without memory on purpose, to compare runs with and without it.
    • switched off: project memory is switched off for everyone.
    • set on task or from epic: an older task, recorded when a task or its epic could carry its own setting.
  6. Read the three counts. injected is how many memory units were put in the task's prompt, read how many the runner opened, and cited how many it said it relied on.

    The Project memory row on a task's Summary tab: Off (plan) · 0 injected · 0 read · 0 cited

The row describes the latest start. If the task runs again after you change the project's setting, the row changes with it. A task has no memory setting of its own: to change what the next tasks get, change the project.