@ours.network/cowork 1.0.2 → 1.0.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +1 -1
- package/dist/daemon.js +773 -567
- package/package.json +3 -1
package/README.md
CHANGED
|
@@ -19,7 +19,7 @@ Start or install the shared daemon with `@ours.network/cli` 2.5.0 before startin
|
|
|
19
19
|
|
|
20
20
|
The shared daemon retains application payload history outside its protocol packets: each identity has a `history.sqlite3` database and immutable content-addressed file blobs. Cowork authorizes unread metadata by authenticated CID, reads the corresponding persistent history or blob, durably archives the room item and its complete fan-out, and only then advances that exact SDK unread item. There is no packet-inbox fallback, defer queue, host outbox, or cross-store transaction.
|
|
21
21
|
|
|
22
|
-
The package keeps
|
|
22
|
+
The package keeps room metadata and a per-room indexed `archive.sqlite3` in its own state directory. The archive uses WAL with `synchronous=FULL`; a record is durable at the completed SQLite commit. File bytes are immutable content-addressed blobs written and directory-synced before their referencing transaction, so interruption can leave only an unreferenced blob, never a committed partial file. Only identity names are used to select cowork rooms from the daemon-global identity list; this bookkeeping is not a provenance or authorization boundary. Operator room commands use one JSONL request over `management.sock`. Use `--json` for automation; its stdout is a single JSON value and diagnostics are included in that value.
|
|
23
23
|
|
|
24
24
|
Ordinary ours-mcp identities can join only as remote participants over the ours protocol.
|
|
25
25
|
|