algovoi-keystone-odbc

Bind ODBC / DB-API database operations to the AlgoVoi keystone. Wrap any DB-API 2.0 cursor (pyodbc, sqlite3, psycopg, …) and every executed statement gets a content-addressed execution_ref binding that operation to the keystone decision that authorised it. Open, keystone-only edition, Apache-2.0.

execution_ref = "sha256:" + SHA-256(JCS({ decision_ref, action_type, scope, outcome, executed_at_ms }))

import pyodbc
from algovoi_keystone_odbc import keystone_cursor

conn = pyodbc.connect(dsn)
cur = keystone_cursor(conn.cursor(), decision_ref="sha256:…", scope="orders")

cur.execute("INSERT INTO orders (id, total) VALUES (?, ?)", 1, 4200)
cur.execution_ref   # sha256:… — binds that INSERT to the authorising keystone decision
cur.executions      # [{statement, action_type: "db:insert", outcome: "COMMITTED", execution_ref, …}]

A failed statement is recorded with outcome FAILED and the error re-raised. action_type is derived from the SQL verb (db:insert, db:update, db:delete, db:select, …). The wrapper is a drop-in: attribute access (fetchone, description, …) falls through to the real cursor.

Standalone, without the cursor:

from algovoi_keystone_odbc import db_execution_ref, tamper_detected

ref = db_execution_ref(decision_ref="sha256:…", statement="UPDATE orders SET total=0",
                       scope="orders", outcome="REVERSED", executed_at_ms=1716460800000)
tamper_detected(ref, decision_ref="sha256:…", statement="UPDATE orders SET total=0",
                scope="orders", outcome="REVERSED", executed_at_ms=1716460800000)  # -> False

Keystone-only edition

This edition binds and verifies each database operation. Chaining operations into a signed, tamper-evident audit log is the commercial tier.

License

Apache-2.0. Copyright AlgoVoi. Byte-compatible with algovoi-execution-ref.