Add jobs (jobs-to-be-done) to the Outcome Graph model#1
Merged
Conversation
Add 'job' as a root-level node kind capturing the progress a customer is trying to make in a specific circumstance. Jobs sit beside ICPs as durable customer context outside the trace chain: outcomes and opportunities reference jobs many-to-many with inheritance down the trace (mirroring ICP references), and jobs reference the ICPs who have them. Referenced jobs are protected from deletion, and context assembly surfaces related jobs and their content to agents. Validation gains severities: structural violations stay errors, while new advisory warnings flag top-level opportunities not connected to a job and jobs without an ICP. 'oe validate' prints warnings without failing. The canvas renders a jobs band beside ICPs with job reference edges, a '+ Job' header action, job chips in the detail panel, and job pickers on outcome and opportunity editors. Skills: new jobs best-practices reference (circumstance, functional/ emotional/social progress, forces of progress, competing alternatives) plus job guidance in oe-cli, oe-grill, oe-graph-audit, oe-validate, and the related reference files. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Mevnh4TCyEqvmd8wPcRMvJ
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add 'job' as a root-level node kind capturing the progress a customer is
trying to make in a specific circumstance. Jobs sit beside ICPs as durable
customer context outside the trace chain: outcomes and opportunities
reference jobs many-to-many with inheritance down the trace (mirroring ICP
references), and jobs reference the ICPs who have them. Referenced jobs are
protected from deletion, and context assembly surfaces related jobs and
their content to agents.
Validation gains severities: structural violations stay errors, while new
advisory warnings flag top-level opportunities not connected to a job and
jobs without an ICP. 'oe validate' prints warnings without failing.
The canvas renders a jobs band beside ICPs with job reference edges, a
'+ Job' header action, job chips in the detail panel, and job pickers on
outcome and opportunity editors.
Skills: new jobs best-practices reference (circumstance, functional/
emotional/social progress, forces of progress, competing alternatives) plus
job guidance in oe-cli, oe-grill, oe-graph-audit, oe-validate, and the
related reference files.
Co-Authored-By: Claude Fable 5 noreply@anthropic.com
Claude-Session: https://claude.ai/code/session_01Mevnh4TCyEqvmd8wPcRMvJ