Results for sql_capsule

Terminal-first AST dependency graph and session memory engine for AI coding agents

SBO3L Phase 3.1: on-chain audit-chain anchoring — periodically publish audit-root digests to AnchorRegistry contracts on Ethereum / Optimism / Base / Polygon for tamper-evident verification.

SBO3L CLI binary: validate, decide, sign, audit, passport run/verify/explain, doctor.

SBO3L core: protocol types, request hashing, error model, signed receipts.

SBO3L execution: sponsor adapters (KeeperHub, Uniswap) wrapping the GuardedExecutor trait.

SBO3L identity: ENS-backed agent identity resolution (offline fixture + live RPC).

SBO3L MCP — stdio JSON-RPC server wrapping SBO3L primitives (validate_aprp, decide, run_guarded_execution, verify_capsule, audit_lookup, explain_denial).

SBO3L policy engine: YAML/JSON policy parsing + rule evaluation + persistent budget tracking.

SBO3L HTTP daemon: POST /v1/payment-requests pipeline (auth, idempotency, policy, budget, audit, signed receipt).

SBO3L storage: SQLite persistence + hash-chained audit log.

Claw VCS: intent-native, agent-native version control.

Core object types and Claw Object Format encoding for Claw VCS.

SQLCapsule is the culmination of many of my thoughts and concerns surrounding ORMs and how we use Ruby to interact with databases. The goal is to be a small and easy to understand tool to help you talk to your database without the baggage of a using a full fledged ORM. SQLCapsule is reminiscent of the repository pattern (though you may use it however you like) and works by registering and naming SQL queries for later use. SQLCapsule aims to provide helpful errors, and to assist you along the way to building an application specific PostgreSQL interaction layer.