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.

​
KG decision history

You can use the Knowledge Graph to recover design decisions from prior sprints before an agent writes new work. This keeps the next spec from contradicting decisions the team already made.

​
The problem

An agent starting a new spec may not know why a choice was made three sprints ago. The answer might live in an old spec, a bug learning, or a superseded decision. KG queries make that context discoverable.

​
How decisions enter the KG

Decisions recorded on specs consolidate into Decision nodes. Alternatives, constraints, entities, learnings, and supersedence edges can connect to those nodes.

​
Query the decision history

Use topic search when you know the area but not the exact node ID. 
okto_pulse_kg_get_decision_history(board_id="...", topic="agent permissions")

​
Follow supersedence

When you have a decision ID, trace its replacement chain. 
okto_pulse_kg_get_supersedence_chain(board_id="...", decision_id="dec_...")

​
Find similar past decisions

Use similarity before creating a new decision. It catches renamed or paraphrased topics. 
okto_pulse_kg_find_similar_decisions(board_id="...", topic="validation gate ownership")

​
Trace contradictions before writing a new spec

Run contradiction search before introducing a change that might violate old constraints. 
okto_pulse_kg_find_contradictions(board_id="...")

​
Read-only reporting agent setup

A reporting agent needs kg.query.decision_history, kg.query.similar_decisions, kg.query.supersedence_chain, and relevant entity read flags. It does not need kg.session.commit or admin flags.
Last modified on May 8, 2026