Know what needs
your attention.
Follow a delivery blocker from evidence to an approved action.
Your action queue
Exact wording. Explicit approval.Jira simulator
Persisted comments and receiptsSource records.
These are the records available to the selected demo identity.
The action trail.
Proposal, decision and dispatch are recorded separately. This local hash chain is inspectable; it is not immutable storage.
Your next workflow
starts here.
Use the Python SDK in your application, connect a versioned evidence source, or export an approved decision to Graphiti Local.
Start with a source
Implement EvidenceConnector.read(). Each record carries a stable ID, source, customer, quote, revision and access groups. Resolve identity in your own application.
Keep the write boundary
The lifecycle is propose → review → dispatch. Review binds the exact payload and source versions. A changed record requires a fresh review.
from determa_context import Context
from determa_context.connectors import MAYA
ctx = Context("demo.sqlite3")
signals = ctx.signals(MAYA)
draft = ctx.propose(
MAYA, "jira-aurora",
"Please confirm the revised test date."
)
# Display draft to a person before review.
Take the approved decision with you
Download JSONL for a separate Graphiti Local demo graph. Export includes dispatched decisions only. Import is manual; this demo does not run graph retrieval.
This starter has no SSO, live Jira connector, tenant isolation, semantic retrieval or background sync. The identity selector is a demonstration control. Run on loopback with synthetic data.