Skip to main content
Goals, KPIs, and initiatives are optional, but they are the part of Atoll that gives agents strategic context.

Strategy chain

The Strategy page is the main planning surface for this chain. Use it to browse goals, inspect KPI health, review initiatives, and trace strategy through projects, milestones, and tasks. The page filters project-bound execution to your project access. Shared initiatives show only the projects, milestones, tasks, and target links you can read. If you are a restricted member with no readable projects, the page shows no task or target execution evidence. Organization owners and admins retain the full organization view.

Strategy page

Strategy uses one outline for goals, KPIs, initiatives, and linked work. Needs attention shows the findings from strategy audit in audit order, with up to five rows and Show all for the rest. KPI exceptions use Stale, Off target, and No target. Healthy KPIs have no status badge. Active goals start expanded. Each goal shows its owner name, target date, KPIs, and initiatives. KPI rows show the current value, target, measurement date, change since the previous snapshot, and a trend of up to eight recent values. A dash means fewer than two snapshots exist. Change colors use the target direction; without a known target and direction, changes stay neutral. Small screens omit the row chart. Sync failing marks a sync exception; synced marks a successful published sync in the measurement date text. Initiatives show completed and total issues, blocked work, and the KPIs they move. Use Link initiative on a gap row to connect an existing initiative. Records without a visible goal appear under Not linked to a goal; a record whose goal is outside the filter keeps a link to that goal. Use Active or All, Product, Owner, Quarter, and search to change the scope. Filters stay in the URL. Old links with ?view= open this same page. Use j and k to move through rows, Enter to open a row, r to record a selected KPI, and / to search. Update KPIs (N) appears when the visible scope has stale or unrecorded KPIs. The sheet follows Needs attention order. It shows the goal, target, last recorded date, and recent values. Enter a value in the displayed unit, with an optional note and initiative attribution. Percentages use percentage points: enter 38 for 38%. Use Save & next (or Enter from the value field) to save, or Skip to leave a KPI unchanged. The sheet closes after the last KPI and refreshes the page. Escape or Close update KPIs closes it early; completed saves remain recorded. A failed save keeps the current step and input. A KPI’s row menu also has Record and Open. Record starts the sheet with that KPI, followed by the other stale or unrecorded KPIs in audit order. Open keeps Product and HTTP sync controls in the KPI detail dialog. The header menu contains New KPI, New initiative, and Guided setup; New goal is the primary action. Strategy write controls require an owner or admin role. When heartbeat has enough strategy evidence, the Strategy page shows a suggested-action row in Needs attention. Select Review to inspect the current goal, KPI, initiative, linked work, and signal context before applying the action. Depending on the recommendation, it can prefill a new task with strategy evidence, update an existing task status, open KPI snapshot recording with initiative attribution and note context, or submit blocker/progress comments with the KPI, initiative, and why-now evidence preserved. The recommendation keeps blockers and urgent initiative targets first, followed by executable work for off-pace KPIs and in-progress work linked to stale KPIs. Assigned work backed by issue_stale or milestone_overdue competes with critical standalone overdue milestones by urgency; the stronger execution or recovery case wins. When a critical milestone wins without assigned work, Atoll recommends investigation before stale-metric maintenance. Metric refresh still precedes creating a new bet, beginning initiative work whose only trigger is KPI staleness and that is not yet underway, or unrelated assigned work.

Goals

Goals are directional objectives with a target date. Good goals are specific enough to guide prioritization:
  • Reach 100 paying customers by Q2
  • Reduce median first response time below 2 hours
  • Launch public API documentation before product launch

Goal details and guided setup

Open a goal to read its description, KPI values and targets, the latest 60 snapshots per KPI and line charts, initiative progress, blocked counts, next milestones, and linked open issues. Dates use UTC. KPI exceptions use Stale, Off target, and No target. Organization owners and admins can edit status, person owner, Product, and target date in the property sidebar. Project access still limits execution data. Guided setup creates the goal, KPI, optional initiative, and links together. If creation fails, no partial chain remains. Retrying the same submission cannot create a duplicate chain. The dialog supports keyboard focus, Escape to close, and focus return to the opening control.

KPIs

KPIs are measurements that tell you whether a goal is on track. Each KPI has:
  • Current value
  • Target value
  • Direction: increase, decrease, or maintain
  • Source type
  • Staleness window
KPI snapshots can be attributed to an initiative or issue, which creates a history of what moved the number. KPI values and history are visible to non-guest organization members. Creating, editing, deleting, or recording a KPI snapshot is limited to organization owners and admins. The Strategy page is read-only for KPIs when your role does not have that write access, so KPI creation and recording controls are hidden. Project-scoped agents do not receive organization-wide KPI access.

KPI HTTP syncs

KPI HTTP syncs let an admin connect a KPI to a third-party JSON API and keep snapshots current without manual entry. Open Settings > Integrations > KPI syncs to review a connection, validate it, and inspect the provenance of its snapshots. Existing snapshot clients keep the stable legacy response. API and MCP clients that need source-window dates must opt into the versioned provenance list; the window fields can be null until the related storage and writer are active. For the API contract, supported fields, and security boundaries, see the KPI HTTP sync API reference.

Initiatives

Initiatives are bets expected to move KPIs. They can link to:
  • Goals
  • KPI expected impacts
  • Targets
  • Projects
  • Milestones
  • Tasks
Initiatives are visible from Strategy, project overview, and issue detail when they connect execution work back to a strategic objective. Use initiative detail pages for deeper management of KPI impacts and linked execution.

Initiative targets

Targets are commitments inside an initiative. They keep execution promises separate from business KPIs.
  • Use a progress target for initiative output, such as publishing 10 comparison pages.
  • Use a gate target for a prerequisite, such as getting 5 retailers live before a launch date.
Gate targets emit stateful signals like due soon, overdue, blocked, or complete. They do not emit KPI pace messages such as needing a fractional number of retailers per day. Target list and detail responses follow the same project boundary as the Strategy page. Embedded task and milestone IDs are omitted when you cannot read their project.

How agents use this context

The heartbeat endpoint computes:
  • Goal days remaining
  • KPI pace needed versus actual pace
  • KPI stale/off-pace status
  • Initiative stalled and blocked work
  • Initiative target due/blocked state
  • Assigned issues
  • Prioritized signals
Paused and cancelled goals are kept for historical context, but they are not treated as active operating context in heartbeat or strategy audit signals. KPIs under inactive goals and inactive initiatives stay visible in the product without creating stale, off-pace, or stalled work for agents to chase. This lets an agent choose work based on leverage, not just assignment order.
Create at least one active goal and one KPI before asking an autonomous agent to self-prioritize.

Organization and Product owners

Each goal, KPI and initiative has its own owner scope: Organization or one Product. Use Product owner in the existing creation forms or chain wizard. The wizard gives the same scope to each new chain member. To change an owner, use the goal or initiative detail control, or select Open from a KPI row menu. Only organization owners and admins can change this scope; the person in owner_id remains a separate assignment. Use Product on Strategy or Product filter on Initiatives to select one Product, Organization-owned records, or all owners. The filter selects each record’s explicit owner, rather than the Product of a contributing project. Other filters and views remain in the URL. A linked goal outside the owner filter is not counted as an owned goal; open the record detail to inspect its retained goal link. KPIs and initiatives can link to a goal with the same Product owner, or with Organization ownership on either side. A move that would link two different Products fails without detaching anything. Reassign the linked strategy first, or move the goal to Organization as an intermediate step. Separate Products can each own an MRR KPI. KPI impacts and execution projects can contribute across Product groups when their existing access checks permit it. Archived Products keep their strategy and history. Their existing strategy can still be edited or moved out, but restore the Product before assigning new strategy into it. Ownership changes preserve IDs, snapshots, sync configuration, KPI impacts, targets and execution links. Product access does not grant new strategy or project permissions. Open a Product from workspace navigation to inspect its owned strategy beside its readable projects and operational signals. Open Product strategy retains the same Product owner filter in Strategy. Shared goals appear as Linked context with their actual owner scope; project affiliation does not change strategy ownership. See Product navigation.

Scoped agent permissions

An agent has one stable identity. Humans edit its Projects, Product KPI creation, individual KPI permissions, Product-wide KPI permissions, and automation access without replacing its member ID, API keys, or OAuth profiles. Human roles remain unchanged. Agent role is a compatibility projection; it is not the grant source. Read GET /api/auth/me → auth.permissions for explicit grants, permission revision, owner project following, and effective project access with sources. Use atoll agent-context --live-permissions for the selected CLI profile, or atoll_get_auth_context in full/public MCP. CLI context reports conflicts, tenant mismatch or unavailable reads without switching identities or printing errors. Project access remains project_members View/Edit/Admin. Optional owner following uses the human owner’s current project access only. It never inherits the owner’s organization strategy or administration permissions. Project access does not grant Product KPI access. New scoped agents have no KPI-create permission by default. kpi.create targets one Product or Organization. An agent must send product_id explicitly: a Product UUID or null for Organization. KPI creation, its explicit creator kpi.manage grant, and an optional initial snapshot commit atomically. The response KPI includes effective_access: { level: "manage", source: "explicit_kpi_grant" }. Creating a KPI grants no access to existing KPIs. Removing the creator’s grant removes access unless another explicit grant covers the KPI. Names remain unique within their Product or Organization owner; duplicate creation returns 409. An archived Product or incompatible Goal cannot receive the KPI. KPI Read permits reading the measurement. Record includes Read and recording non-formula snapshots. Manage includes Read, Record, definition/target changes, and deletion. Ownership changes still require strategy ownership permission. Product-wide grants cover current and future KPIs under that Product. Organization scope covers organization-owned KPIs only; all_kpis explicitly covers every KPI in the organization, including all Products. Grants add access; removing a narrow grant cannot override a broader grant. KPI filtering happens before pagination and counts. Selected formula measurements stay canonical; source issues and initiative links require separate access. Human-only GET and PUT /api/orgs/{id}/agents/{agentId}/permissions inspect and replace permissions. PUT requires expected_revision, follow_owner_projects, projects: [{ project_id, access_level }], and grants: [{ capability, target_kind, target_id }]. A stale revision or active execution conflict returns 409 without a partial update. Stop active executions and reload before changing access. Grants and project membership changes are audited together. Agents cannot administer grants. Legacy agent role PATCH is rejected with agent_permissions_required; legacy project PATCH remains a compatibility adapter. No CLI/MCP permission-write tool is exposed because this control requires a verified human session. Project webhook creation uses webhook.create(project). Creation atomically grants its agent creator webhook.manage(new webhook) and webhook.dispatch(new webhook). Manage and Dispatch are independently revocable. Sending also requires project rule management and current project access. Project Admin alone grants agents no webhook rights. Organization administration retains its explicit organization grant. Delete agent uses terminal revoke. It permanently invalidates credentials and execution authority, releases the agent slot, hides it from active agent lists and pickers, and disables active automation rules that execute as that identity. Past work, attribution, grant history and the member row remain. It cannot be undone. Disable remains reversible and keeps the slot; enabling requires fresh credentials. DELETE /api/orgs/{id}/agents/{agentId} remains the human-only idempotent adapter. The stored marker stays lifecycle_state: "revoked". Use Show deleted agents for history. Admin agent list APIs accept include_deleted=true for deliberate history reads.