nedb-engine 3.3.1 → 4.1.0

package/LICENSE

@@ -1,21 +1,151 @@
-MIT License
-
-Copyright (c) 2026 Interchained LLC and VibeCode 101
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
+Business Source License 1.1
+
+License text copyright (c) 2020 MariaDB Corporation Ab, All Rights Reserved.
+"Business Source License" is a trademark of MariaDB Corporation Ab.
+
+-----------------------------------------------------------------------------
+
+Parameters
+
+Licensor:             INTERCHAINED LLC
+
+Licensed Work:        NEDB, version 4.0.0 and later.
+                      The Licensed Work is (c) 2026 INTERCHAINED LLC.
+
+Additional Use Grant: You may make production use of the Licensed Work,
+                      without limitation and without obtaining any further
+                      permission or license from the Licensor, provided that
+                      your Annual Revenue is less than one million United
+                      States dollars (USD $1,000,000).
+
+                      "Annual Revenue" means the total gross revenue,
+                      recognised under the accounting standards you ordinarily
+                      apply, of you together with all of your Affiliates, over
+                      your most recently completed fiscal year. "Affiliates"
+                      means any entity that controls, is controlled by, or is
+                      under common control with you, where "control" means
+                      direct or indirect ownership of more than fifty percent
+                      (50%) of the voting interests of an entity.
+
+                      Annual Revenue is measured on your organisation as a
+                      whole. It is NOT limited to revenue derived from, or
+                      attributable to, the Licensed Work. An organisation
+                      whose Annual Revenue is USD $1,000,000 or more must
+                      obtain an additional use grant from the Licensor before
+                      making production use of the Licensed Work.
+
+                      Regardless of Annual Revenue, this Additional Use Grant
+                      does not permit you to offer the Licensed Work, or a
+                      substantially similar derivative of it, to third parties
+                      as a managed, hosted or database-as-a-service offering.
+                      That use requires a separate commercial license.
+
+                      Non-production use is always permitted: development,
+                      testing, continuous integration, evaluation, research,
+                      teaching and personal projects are unrestricted for
+                      everyone, at any revenue.
+
+                      To obtain an additional use grant, contact
+                      licensing@interchained.org.
+
+Change Date:          2030-09-11
+
+Change License:       Apache License, Version 2.0
+                      The full text ships in this repository as
+                      COPYING-APACHE-2.0.txt, so the grant is verifiable from
+                      the source tree alone.
+
+                      The Change License relicenses the Licensed Work's OWN
+                      source. It does not relicense third-party dependencies,
+                      which keep their own terms — inventoried in
+                      THIRD_PARTY.md.
+
+-----------------------------------------------------------------------------
+
+Terms
+
+The Licensor hereby grants you the right to copy, modify, create derivative
+works, redistribute, and make non-production use of the Licensed Work. The
+Licensor may make an Additional Use Grant, above, permitting limited
+production use.
+
+Effective on the Change Date, or the fourth anniversary of the first publicly
+available distribution of a specific version of the Licensed Work under this
+License, whichever comes first, the Licensor hereby grants you rights under
+the terms of the Change License, and the rights granted in the paragraph
+above terminate.
+
+If your use of the Licensed Work does not comply with the requirements
+currently in effect as described in this License, you must purchase a
+commercial license from the Licensor, its affiliated entities, or authorized
+resellers, or you must refrain from using the Licensed Work.
+
+All copies of the original and modified Licensed Work, and derivative works
+of the Licensed Work, are subject to this License. This License applies
+separately for each version of the Licensed Work and the Change Date may vary
+for each version of the Licensed Work released by Licensor.
+
+You must conspicuously display this License on each original or modified copy
+of the Licensed Work. If you receive the Licensed Work in original or
+modified form from a third party, the terms and conditions set forth in this
+License apply to your use of that work.
+
+Any use of the Licensed Work in violation of this License will automatically
+terminate your rights under this License for the current and all other
+versions of the Licensed Work.
+
+This License does not grant you any right in any trademark or logo of
+Licensor or its affiliates (provided that you may use a trademark or logo of
+Licensor as expressly required by this License).
+
+TO THE EXTENT PERMITTED BY APPLICABLE LAW, THE LICENSED WORK IS PROVIDED ON
+AN "AS IS" BASIS. LICENSOR HEREBY DISCLAIMS ALL WARRANTIES AND CONDITIONS,
+EXPRESS OR IMPLIED, INCLUDING (WITHOUT LIMITATION) WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, AND
+TITLE.
+
+MariaDB hereby grants you permission to use this License's text to license
+your works, and to refer to it using the trademark "Business Source License",
+as long as you comply with the Covenants of Licensor below.
+
+-----------------------------------------------------------------------------
+
+Covenants of Licensor
+
+In consideration of the right to use this License's text and the "Business
+Source License" name and trademark, Licensor covenants to MariaDB, and to all
+other recipients of the licensed work to be provided by Licensor:
+
+1. To specify as the Change License the GPL Version 2.0 or any later version,
+   or a license that is compatible with GPL Version 2.0 or a later version,
+   where "compatible" means that software provided under the Change License
+   can be included in a program with software provided under GPL Version 2.0
+   or a later version. Licensor may specify additional Change Licenses
+   without limitation.
+
+2. To either: (a) specify an additional grant of rights to use that does not
+   impose any additional restriction on the right granted in this License, as
+   the Additional Use Grant; or (b) insert the text "None".
+
+3. To specify a Change Date.
+
+4. Not to modify this License in any other way.
+
+-----------------------------------------------------------------------------
+
+Notice
+
+The Business Source License (this document, or the "License") is not an Open
+Source license. However, the Licensed Work will eventually be made available
+under an Open Source License, as stated in this License.
+
+-----------------------------------------------------------------------------
+
+Prior versions
+
+NEDB versions 3.0.0 through 3.3.1 were released under the MIT License. That
+grant is irrevocable for those versions: if you obtained NEDB at 3.3.1 or
+earlier, your rights in that copy are unchanged by this License and are not
+affected by it. This License governs version 4.0.0 and later only.
+
+© 2026 INTERCHAINED LLC

package/README.md

@@ -13,14 +13,19 @@ One Rust core → ships to **PyPI** and **npm** from a single source.
 [![CI](https://img.shields.io/github/actions/workflow/status/Eth-Interchained/nedb/release.yml?label=CI&color=34d399)](https://github.com/Eth-Interchained/nedb/actions)
 [![nedb-engine-client PyPI](https://img.shields.io/pypi/v/nedb-engine-client?label=nedb-engine-client&color=34d399)](https://pypi.org/project/nedb-engine-client/)
 [![nedb-engine-client npm](https://img.shields.io/npm/v/nedb-engine-client?label=nedb-engine-client&color=34d399)](https://www.npmjs.com/package/nedb-engine-client)
-[![License: MIT](https://img.shields.io/badge/license-MIT-22c55e?logo=opensourceinitiative&logoColor=white)](https://github.com/Eth-Interchained/nedb/blob/master/LICENSE)
+[![License: BUSL-1.1](https://img.shields.io/badge/license-BUSL--1.1-f59e0b)](https://github.com/Eth-Interchained/nedb/blob/master/LICENSE) [![Free under $1M revenue](https://img.shields.io/badge/free%20under%20%241M%20revenue-22c55e)](https://github.com/Eth-Interchained/nedb/blob/master/LICENSE)
 
 **[Studio → studio.interchained.org](https://studio.interchained.org)**  ·  **[nedb.aiassist.net](https://nedb.aiassist.net)**
 
-> ## 🟢 MIT Licensed — free for any use, including commercial & production
-> NEDB is licensed under the **MIT License** — use it in production, embed it in commercial
-> products, ship it in closed-source software, fork it, sell it. No restrictions, no royalties,
-> no copyleft. See [`LICENSE`](LICENSE). The database is free; the moat is what you build on it.
+> ## 🟢 Free in production under $1M revenue
+> NEDB 4.0.0 is licensed under the **Business Source License 1.1**. If your organisation's annual
+> revenue is **under USD $1,000,000**, you may use it in production — commercially, embedded, in
+> closed-source software — with **no permission needed and no royalty**. At **$1M or more**, you
+> need an additional use grant from Interchained LLC: **licensing@interchained.org**.
+>
+> Non-production use is unrestricted for everyone, at any revenue: development, testing, CI,
+> evaluation, research, teaching. On **2030-09-11** this version converts to **Apache 2.0**
+> automatically and permanently. See [`LICENSE`](LICENSE).
 
 </div>
 
@@ -98,45 +103,261 @@ identical answers.
 
 ---
 
+## Postgres wire protocol — run your SQL, get history for free
+
+`nedbd --pg-port 5433` opens a **PostgreSQL wire-protocol endpoint** — reads
+*and* writes. `psql`, DBeaver, Metabase, Grafana, psycopg — anything that
+speaks pgwire can use a tamper-evident NEDB store with ordinary SQL, with no
+bespoke client.
+
+**The reason the write path matters** is that SQL's write semantics and NEDB's
+append-only model already line up:
+
+| SQL | NEDB | and therefore |
+| --- | --- | --- |
+| `INSERT` | a put | — |
+| `UPDATE … WHERE` | a **new version** of each match | the prior value stays readable |
+| `DELETE … WHERE` | a **tombstone** | the deleted row stays in history |
+
+So this is not a compromise of the append-only design — it *is* the design,
+reached through a protocol every tool already speaks:
+
+```sql
+UPDATE orders SET total = 999 WHERE _id = 'o1';
+SELECT total FROM orders WHERE _id = 'o1';                       -- 999
+SELECT total FROM orders AS OF SYSTEM TIME 0 WHERE _id = 'o1';   -- 120
+```
+
+Run the SQL you would run against Postgres, and the tamper-evident audit trail
+is free. No triggers, no shadow table, no application code. `verify()` still
+passes afterwards, because a SQL write is an ordinary engine write and not a
+side door around the hash chain.
+
+Writes are **on by default**. `NEDBD_PG_READ_ONLY=1` gives the deployment where
+this door must never mutate anything.
+
+```console
+$ nedbd --data ./data --pg-port 5433
+  pgwire   postgres endpoint on 127.0.0.1:5433 — psql / DBeaver / psycopg (SELECT + INSERT/UPDATE/DELETE)
+
+$ psql -h 127.0.0.1 -p 5433 -d shop
+shop=> SELECT status, total FROM orders WHERE status IN ('paid','open') ORDER BY total DESC;
+ status | total
+--------+-------
+ paid   |   300
+ paid   |   120
+ open   |    40
+
+shop=> SELECT SUM(total) FROM orders WHERE region = 'eu';
+ sum
+-----
+ 420
+
+shop=> SELECT * FROM orders AS OF SYSTEM TIME 1;     -- time travel, in SQL
+```
+
+**`AS OF SYSTEM TIME` is the bridge worth knowing about.** It is the spelling
+Postgres and CockroachDB use, and here it reaches NEDB's permanent,
+never-garbage-collected history rather than a few hours of MVCC.[^compact] A wall-clock
+timestamp is refused with the reason: NEDB's history is sequence-addressed, so
+a seq is exact where a time would be approximate.
+
+[^compact]: One caveat, stated rather than buried. `Db::compact()` reclaims disk
+    space by rewriting the object segments with only each document's **current**
+    version — so it prunes superseded versions and tombstones, and `AS OF` can
+    no longer reach them. Nothing invokes it automatically: it is not on the
+    HTTP surface, not in the CLI, and not on any timer. It exists for the
+    operator who has explicitly chosen to trade the audit trail for space. A
+    compacted store answers "not available at that sequence" rather than
+    returning a stale value, and `verify()` stays clean.
+
+Provenance is selectable like any other column:
+
+```sql
+SELECT _id, _hash, _seq FROM audit ORDER BY _seq;
+```
+
+**This is not "NEDB speaks SQL", and the endpoint is careful to say so.** It is
+a documented subset of `SELECT` translated to NQL:
+
+| Supported | Refused, with the reason |
+| --- | --- |
+| `*`, a column list, `COUNT(*)`, `SUM`/`AVG`/`MIN`/`MAX(col)` | `JOIN` — NQL is single-collection |
+| `WHERE` — the whole NQL predicate surface | subqueries, `UNION`, window functions |
+| `GROUP BY`, `HAVING`, `ORDER BY`, `LIMIT`, `OFFSET` | expressions in the select list |
+| `AS OF SYSTEM TIME <seq>` | DDL, `TRUNCATE`, `GRANT`/`REVOKE` |
+| `INSERT` / `UPDATE` / `DELETE`, all with `RETURNING` | an `INSERT` with no column list |
+| `_caused_by` / `_valid_from` / `_valid_to` as INSERT columns | values that are expressions, not literals |
+
+Every refusal names the boundary instead of saying "syntax error", and a
+grouped query that projects a column SQL would reject gets Postgres's own
+message rather than a silent `NULL`.
+
+**Provenance is settable from SQL**, so the causal chain does not require the
+HTTP API:
+
+```sql
+INSERT INTO audit (_id, _caused_by, kind) VALUES ('leaf', '<parent-hash>', 'reprice');
+SELECT _id FROM audit TRACE caused_by;
+```
+
+An `INSERT` requires an explicit column list, because NEDB is schemaless and
+there is no declared column order to infer. Values must be literals — a number,
+a quoted string, `TRUE`/`FALSE`/`NULL` — since storing an unevaluated
+expression as text would be worse than refusing it.
+
+### Your driver, not just `psql`
+
+**Both wire protocols are implemented**, which is the difference between "psql
+works" and "your application framework works":
+
+| Protocol | Used by | Status |
+| --- | --- | --- |
+| simple (`Q`) | `psql`, libpq/`PQexec`, **psycopg2** | ✅ |
+| extended (`Parse`/`Bind`/`Describe`/`Execute`) | **psycopg3**, **asyncpg**, **JDBC** | ✅ |
+
+Those last three send `Parse`/`Bind` for every parameterised statement, so
+until the extended protocol landed they could not run a *single* query — not
+slower, not degraded: psycopg3 hung and asyncpg refused outright.
+
+```python
+# psycopg3 — parameters are bound server-side
+cur.execute("SELECT _id, total FROM orders WHERE status = %s AND total > %s",
+            ("paid", 100))
+
+# asyncpg — same statement, same endpoint
+await conn.fetch("SELECT _id, total FROM orders WHERE status = $1 AND total > $2",
+                 "paid", 100)
+```
+
+Parameters arrive in text **and binary** format (psycopg3 sends a small `int`
+as binary int2, a float as binary float8), and a row-capped `Execute` suspends
+its portal, so a JDBC `setFetchSize` pages a large result instead of stalling.
+
+**Typing parameters in a store with no schema** is the interesting part. A
+relational server reads `$1`'s type out of its catalogue; NEDB has no
+catalogue, so the type is sampled from the documents already stored — the
+stored data *is* the schema. Where a placeholder sits in a clause rather than
+beside a column (`AS OF SYSTEM TIME $1`, `LIMIT $1`) the grammar supplies the
+type, and an aggregate is typed from what it means: a `COUNT` is an integer, an
+`AVG` fractional, a `MAX` whatever the field it ranges over is.
+
+A driver that declares its own parameter types is believed, and only its
+unspecified slots are inferred.
+
+### Limits, stated plainly
+
+SQL-level cursors (`DECLARE`/`FETCH`) and `pg_catalog` introspection are not
+implemented, so `\dt` and DBeaver's schema browser come back empty — both are
+refused by name rather than hanging. A column whose stored values disagree
+about their type across documents is advertised as `text`, and cannot be sent
+in binary format.
+
+And the connection is **cleartext**, which is why the endpoint is off unless
+you pass `--pg-port` and binds to loopback by default. Put it behind a tunnel
+to go further.
+
+Verified in CI by `tests/test_pgwire.py` — **64 checks driven through psycopg2,
+which is libpq**. Unit tests can prove the translation; only a real client
+proves the protocol. One of those checks is the one that matters: after a plain
+SQL `UPDATE`, the prior value is still readable at its original sequence.
+
+---
+
 ## New in 3.2.0 — wrap the databases you already run
 
 NEDB adds **tamper-evident causal provenance to a database you already have**, in one line, without
 rip-and-replace. Five adapters, one surface:
 
+**One flag. No table list, no registration, no per-write calls.**
+
 ```python
-from nedb import wrap_redis, wrap_sqlite, wrap_mysql, wrap_mongo, wrap_postgresql
+from nedb import wrap_postgresql
+import psycopg2
+
+conn = wrap_postgresql(psycopg2.connect("dbname=app"), db_name="app")
+conn.nedb.shadow_writes = True          # ← that is the whole setup
+
+# Your app runs UNCHANGED.
+cur = conn.cursor()
+cur.execute("INSERT INTO drivers (name, status) VALUES (%s, %s)", ("Bob", "active"))
+cur.execute("UPDATE drivers SET status = %s WHERE name = %s", ("off", "Bob"))
+conn.commit()
 
-r = wrap_redis(redis.Redis())        # or wrap_sqlite(sqlite3.connect("app.db")), ...
-r.nedb.register("driver:*", "driver")   # teach NEDB the host's shape
-r.nedb.backfill()                       # import what is already there
-r.nedb.shadow_writes = True             # every future write is chained
+conn.nedb.query('FROM drivers WHERE status = "off"')   # NQL over your Postgres data
+conn.nedb.query('FROM drivers AS OF 0')                # → status "active", the prior value
+conn.nedb.verify()                                     # True — BLAKE2b chain intact
+```
 
-r.set("driver:d1", json.dumps({"name": "Bob", "status": "active"}))
+Setting the flag reads the host's own catalogue and mirrors **every table**, with its
+real primary key. Coverage is **opt-out**, because opt-in auditing has a worse failure
+mode than none: three tables registered out of twelve looks exactly like a complete
+audit trail until the day you need it.
 
-r.nedb.query('FROM driver WHERE status = "active"')   # NQL over your Redis data
-r.nedb.query('FROM driver AS OF 41')                  # what it looked like at seq 41
-r.nedb.verify()                                       # True — BLAKE2b chain intact
+```python
+conn.nedb.exclude = {"sessions", "audit_log_*"}        # tables to leave alone
+conn.nedb.exclude_columns = {"password_hash", "ssn"}   # columns that must NEVER be mirrored
+assert not conn.nedb.unmirrored_tables                 # a real check, not a hope
 ```
 
+`exclude_columns` is the one setting that is about correctness rather than convenience.
+**NEDB cannot forget** — that is the product, and it is exactly wrong for a secret or for
+a row somebody has a right to erase. Nothing is excluded by default; guessing which of
+your columns are sensitive would be its own silent wrong answer.
+
 | wrapper | host | shadowing |
 |---|---|---|
-| `wrap_redis` | `redis.Redis` / compatible | automatic — every write command intercepted |
-| `wrap_sqlite` | `sqlite3.Connection` | automatic — `execute()` intercepted post-write |
+| `wrap_redis` | `redis.Redis` / compatible | **automatic** — every write command intercepted |
+| `wrap_sqlite` | `sqlite3.Connection` | **automatic** — `conn.execute`, `cursor.execute`, `executemany` |
+| `wrap_postgresql` | DB-API 2.0 (psycopg2, psycopg 3) | **automatic** — every cursor write, via `RETURNING` |
 | `wrap_mysql` | DB-API 2.0 (mysql-connector, PyMySQL) | explicit `shadow_row()` |
 | `wrap_mongo` | `pymongo.MongoClient` | explicit `shadow_row()` |
-| `wrap_postgresql` | DB-API 2.0 (psycopg2, psycopg 3) | explicit `shadow_row()` |
 
 **NEDB never writes into the host database's namespace.** Shadow data lives only in the NEDB engine.
 
+### The limit, stated plainly
+
+Interception sees writes made **through this connection**. Your production Postgres is
+also written by `psql`, cron jobs, migration tools, and other services — and none of
+those pass through here. For whole-database coverage independent of the client, the right
+mechanism is Postgres **logical replication** (a replication slot decoded with the
+built-in `pgoutput`), which observes every committed change whatever made it. That needs
+`wal_level = logical` and a replication role, and it is not implemented yet.
+
+So this covers your application's writes completely, and it does not pretend to cover
+writes it cannot see. A write to a table that could not be mirrored lands in
+`nedb.unmirrored_tables` rather than vanishing.
+
 Three backends behind the same surface, selected by `backend="auto"`: **nedbd over HTTP** (`nedbd_url=`),
 **embedded v2/v3 DAG** (the Rust core, in-process, no server — `dag_path=` for a durable store,
 `dag_tmk=` for AES-256-GCM at rest), or the **v1 in-process AOF** engine as a universal fallback. On the
 DAG backend you also get `tip()`, `tip_collection()`, `since()` (changefeed) and `scan_status()`.
 
-### 🟢 MIT licensed since 3.0.0
+### Licensing — BUSL-1.1 as of 4.0.0
 
-No production restriction, no copyleft, no Change Date. Use it in production, embed it commercially,
-ship it closed-source, fork it, sell it. License review is a wall, not a speed bump — that wall is gone.
+| Your annual revenue | Production use |
+|---|---|
+| **under USD $1,000,000** | **free.** No permission, no royalty, no registration. Commercial, embedded and closed-source all included. |
+| **USD $1,000,000 or more** | needs an additional use grant — **licensing@interchained.org** |
+
+Measured on your whole organisation, not on revenue attributable to NEDB. Non-production use —
+development, testing, CI, evaluation, research, teaching — is unrestricted for **everyone**, at any
+revenue. Offering NEDB itself as a hosted database service needs a separate commercial license
+regardless of revenue.
+
+**Change Date 2030-09-11**: this version becomes **Apache 2.0** on that date, automatically. The
+grant is in the license text, not a promise — nobody has to be asked, and it cannot be withdrawn.
+The full Apache text ships as [`COPYING-APACHE-2.0.txt`](COPYING-APACHE-2.0.txt) so that is
+verifiable from the source tree alone.
+
+Every source file carries `SPDX-License-Identifier: BUSL-1.1`, so license scanners read the terms
+out of the code rather than guessing. Dependencies keep their own licenses — the Change License
+never relicenses them — and they are inventoried in [`THIRD_PARTY.md`](THIRD_PARTY.md). There is
+**no GPL, AGPL, SSPL or BUSL third-party dependency** in the tree; all 206 third-party crates are
+permissive, and the two Python runtime dependencies are BSD and Apache.
+
+**Versions 3.0.0 – 3.3.1 stay MIT, irrevocably.** If you already have NEDB at 3.3.1 or earlier, your
+rights in that copy are untouched. This applies to 4.0.0 and later only.
 
 ### Also in 3.2.0
 

package/index.js

@@ -1,3 +1,7 @@
+// SPDX-FileCopyrightText: 2026 INTERCHAINED LLC
+// SPDX-License-Identifier: BUSL-1.1
+// NEDB · © 2026 INTERCHAINED LLC × Eth-Interchained × Vex (Claude Opus 5)
+
 'use strict';
 // nedb-engine — durable-mode auto-flush-on-exit wrapper.
 //

package/nedb-inspector.mjs

@@ -1,4 +1,8 @@
 #!/usr/bin/env node
+// SPDX-FileCopyrightText: 2026 INTERCHAINED LLC
+// SPDX-License-Identifier: BUSL-1.1
+// NEDB · © 2026 INTERCHAINED LLC × Eth-Interchained × Vex (Claude Opus 5)
+
 // nedb-inspector — deterministic embedder-code checker for NEDB durability.
 //
 //   nedb-inspector.mjs <pathToTarget.(rs|js|mjs|ts|py)> [more paths...]

package/nedbd-v2.js

@@ -1,4 +1,8 @@
 #!/usr/bin/env node
+// SPDX-FileCopyrightText: 2026 INTERCHAINED LLC
+// SPDX-License-Identifier: BUSL-1.1
+// NEDB · © 2026 INTERCHAINED LLC × Eth-Interchained × Vex (Claude Opus 5)
+
 // nedbd-v2 — thin platform shim that locates and spawns the right
 // pre-built native binary for the current platform/arch.
 //

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "nedb-engine",
-  "version": "3.3.1",
+  "version": "4.1.0",
   "description": "NEDB \u2014 hash-chained, time-traveling, bi-temporal embedded database with Rust native core. SQL, Redis, MongoDB adapters. Causal Write Provenance. RESP2 wire protocol.",
   "main": "index.js",
   "exports": {
@@ -31,7 +31,7 @@
     "README.md",
     "LICENSE"
   ],
-  "license": "MIT",
+  "license": "BUSL-1.1",
   "homepage": "https://github.com/aiassistsecure/nedb#readme",
   "repository": {
     "type": "git",

package/test/durability.test.mjs

@@ -1,4 +1,8 @@
 #!/usr/bin/env node
+// SPDX-FileCopyrightText: 2026 INTERCHAINED LLC
+// SPDX-License-Identifier: BUSL-1.1
+// NEDB · © 2026 INTERCHAINED LLC × Eth-Interchained × Vex (Claude Opus 5)
+
 // nedb-engine — embedded durability under SIGKILL (2.8.5)
 // ---------------------------------------------------------------------------
 // The contract: an acknowledged write is on disk within one manifest tick (default 1 s) or at

package/test/smoke.mjs

@@ -1,4 +1,8 @@
 #!/usr/bin/env node
+// SPDX-FileCopyrightText: 2026 INTERCHAINED LLC
+// SPDX-License-Identifier: BUSL-1.1
+// NEDB · © 2026 INTERCHAINED LLC × Eth-Interchained × Vex (Claude Opus 5)
+
 // nedb-engine — cinematic smoke test (`npm test`)
 // ---------------------------------------------------------------------------
 // A five-act tour of the engine, driven entirely by the real native addon

package/wrap/index.js

@@ -1,3 +1,7 @@
+// SPDX-FileCopyrightText: 2026 INTERCHAINED LLC
+// SPDX-License-Identifier: BUSL-1.1
+// NEDB · © 2026 INTERCHAINED LLC × Eth-Interchained × Vex (Claude Opus 5)
+
 'use strict';
 // nedb/wrap/index.js — the JS wrap adapter family.
 //

package/wrap/mongo.js

@@ -1,3 +1,7 @@
+// SPDX-FileCopyrightText: 2026 INTERCHAINED LLC
+// SPDX-License-Identifier: BUSL-1.1
+// NEDB · © 2026 INTERCHAINED LLC × Eth-Interchained × Vex (Claude Opus 5)
+
 'use strict';
 // nedb/wrap/mongo.js — wrapMongo: causal provenance for MongoDB (JS).
 //

package/wrap/redis.js

@@ -1,3 +1,7 @@
+// SPDX-FileCopyrightText: 2026 INTERCHAINED LLC
+// SPDX-License-Identifier: BUSL-1.1
+// NEDB · © 2026 INTERCHAINED LLC × Eth-Interchained × Vex (Claude Opus 5)
+
 'use strict';
 // nedb/wrap/redis.js — wrapRedis: one-line causal provenance for Redis (JS).
 //

package/wrap/sql.js

@@ -1,3 +1,7 @@
+// SPDX-FileCopyrightText: 2026 INTERCHAINED LLC
+// SPDX-License-Identifier: BUSL-1.1
+// NEDB · © 2026 INTERCHAINED LLC × Eth-Interchained × Vex (Claude Opus 5)
+
 'use strict';
 // nedb/wrap/sql.js — wrapSqlite / wrapMysql / wrapPg: causal provenance for
 // SQL databases (JS).

package/wrap/surface.js

@@ -1,3 +1,7 @@
+// SPDX-FileCopyrightText: 2026 INTERCHAINED LLC
+// SPDX-License-Identifier: BUSL-1.1
+// NEDB · © 2026 INTERCHAINED LLC × Eth-Interchained × Vex (Claude Opus 5)
+
 'use strict';
 // nedb/wrap/surface.js — the engine-agnostic NEDB layer-2 surface (JS).
 //