Repository navigation
v0.2.0
·
27 commits
to main
since this release
A study can now hold more than one core job.
- When the people interviewed do different jobs, for example owner-operators
who plan loads and fleet managers who keep trucks running, the skill finds
each core job by abstracting from every interview's own job. Each core job
gets a letter (A, B…) and its own job map. - Every interview is linked to the core job its own job rolls up to. A related
job can link the same person to another core job. People whose job fits none
are listed with the reason, which moves to history once they are linked. - After the first batch, each core job comes with a decision to confirm it
("approve P1"), saying how many people back it. Before, a first core job
stayed "proposed" with no way to confirm it. - New decisions for the team: add a core job, confirm one, move a step to
another core job, and change which core job an earlier interview is linked
to. - The review sheet has a job map and a people section per core job. The
discovery map has a core job switcher under the title and shows each
person's jobs. - Step and outcome IDs now start with their core job's letter: step
6
is nowA.6and outcome6.3is nowA.6.3, even in a study with one core
job, so no ID changes when a second job appears. - Existing knowledge bases need one migration. The assistant runs
kb_tool migratewhen the tool asks for it. It keeps a backup, turns the
core job into core job A and adds the letter to every ID. Patches written
for 0.1 still merge into a study with one core job. A discovery map made
with 0.1 cannot be used as a template any more; the skill's own template is
used instead.