Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.oktolabs.ai/llms.txt

Use this file to discover all available pages before exploring further.

​
Decisions

You can use Decisions to preserve why a spec chose one path over another. Requirements say what must happen; Decisions explain the choice, alternatives, rationale, and supersedence chain.

​
What is a decision in Pulse

A Decision is a formal design choice on a spec. It has a title, rationale, alternatives, criteria, linked requirements, and optional supersedes_decision_id for replacement.

​
How decisions feed the KG

When specs consolidate into the Knowledge Graph, Decisions become Decision nodes. Related alternatives, constraints, entities, and learnings can connect to them. This lets future agents retrieve prior rationale instead of rediscovering it in chat.

​
Recording a decision on a spec

Use the decision tools when the team picks an architecture, data model, API shape, permission rule, deployment strategy, or validation threshold. 
okto_pulse_add_decision
okto_pulse_update_decision
okto_pulse_remove_decision

​
Supersedence

Do not overwrite an old Decision when the choice changes. Create or update the new Decision with supersedes_decision_id so the old one becomes part of the chain.

​
Querying decisions later

Use KG tools to recover the chain: 
okto_pulse_kg_get_decision_history
okto_pulse_kg_find_similar_decisions
okto_pulse_kg_get_supersedence_chain
Last modified on May 8, 2026