Goal Hierarchy

Every Job Knows Its Purpose

Company objectives, project targets, and task goals flow down into every expert agent execution. Agents work with strategic context, not just instructions.

Request Access
COMPANY

Q2 GOAL

Reduce auth
latency 40%

PROJECT

Migrate to JWT

auth token refactor

Redis Session Cache

add redis adapter

TASK
impl jwt-middleware
write jwt tests
update auth docs
add redis adapter
config TTL + eviction
perf benchmark
AGENTS
code-ts
test-vitest
code-redis
docs
perf
Q2: reduce latency → JWT migration → impl jwt-middleware
Company goal set — a Q2 objective (reduce auth latency 40%) sits at the root
Branches into projects and tasks — JWT migration and Redis cache break into atomic work items
Context flows to agents — goal ancestry is injected into every expert agent prompt

Three Levels of Goals

C

Company

Organization-wide objectives. Set once, inherited by all projects and tasks. Examples: ship v2 platform, achieve SOC 2 compliance.

P

Project

Repository or initiative-scoped targets. Link to a specific project and its jobs. Examples: migrate auth service, reduce p99 latency.

T

Task

Atomic work-item goals. Attached directly to a job. Examples: add MFA endpoint, fix null pointer in checkout flow.

Context Flows Into Every Run

When a job has a goal, the full ancestry chain — from company down to task — is assembled and injected into the expert agent's context before execution. Agents understand why they are working, not just what to do.

Context Assembly — priority order
0.0 Job spec + requirements
0.5 → Goal ancestry (company → project → task)
1.0 Guardrails + compliance rules
1.5 Skill documents
2.0+ Project genome + knowledge

Ancestry Chain

getAncestry() walks the goal tree up to 10 levels deep, returning the root-to-leaf path as structured Markdown.

Priority 0.5 Injection

Goal context is injected before guardrails (priority 1.0), ensuring strategic intent frames every constraint check.

Job Linkage

Each job carries an optional goalId. The scheduler, manual triggers, and webhook handlers all support goal association.

Give Your Agents Strategic Direction

Goals are not documentation. They are live context that shapes every decision your expert agents make.

Request Early Access