Writes to the same browser-local database

Insert SQLite row

Session only · nothing uploaded

Stored rows, not derived answers

SQLite tables

Select a table to inspect its schema

Prepared question

Who needs a follow-up?

Find people who were promised an update for a project that is currently blocked.

Project operations· Turn blocked promises into a concrete follow-up list.

Datalog rule executed by the SQLite extension

Ctrl/⌘ + Enter0 results

SQL scratchpad

Inspect or change the session database directly

No SQL result rows yet

Integrity constraints

Governed-memory constraints are intentionally a Remembero policy layer, not part of this SQLite bridge. The IDE shows the boundary instead of pretending the native extension executes it.

:- status(Project, active), status(Project, blocked).Open constraint docs

Derived, never stored

Result

0 rows

No derived rowsThe rule is valid, but the current SQLite rows do not support an answer.

Lineage

oldest → newest

sample seed INSERT project_owner 2 sample rows
sample seed INSERT project_contributor 3 sample rows
sample seed INSERT promised_update 2 sample rows
sample seed INSERT status 2 sample rows

Native console

—SQLite + Wasm boot

—rule + proof

—last insert

—last SQL

> sqlite3_auto_extension(sqlite3_rembero_init)Loading extension…> SELECT sqlite_version();…

Raw JSON

{
  "rows": [],
  "proof": null
}

Build details

SQLite: loading
Extension: loading
Wasm SHA-256: loading
Source SHA3-256: loading

Compiled SQL

Run a rule to inspect its compiled SQL.

The database is the demo.

Add a row, run a rule, and inspect every premise. Nothing leaves the browser and no derived answer is written back as truth.

SQLite owns the rows.

Ordinary tables remain storage and transaction authority.

The extension owns the query.

The Remembero C extension is compiled into SQLite WebAssembly.

The proof owns the answer.

Results, proof ladders, and graphs come from one exact execution.

Build agents that can show their work.

View the source Return to the main site