Skip to content

DataFog Core 0.5.0-beta.1

Pre-release
Pre-release

Choose a tag to compare

View all tags
@sidmohan0 sidmohan0 released this 29 Oct 02:38
v0.5.0-beta.1
31157fe

Developer integration prerelease for Josh’s Chrome extension testing. Cargo/npm: 0.5.0-beta.1; Python: 0.5.0b1.

Install

npm install --save-exact @datafog/wasm@0.5.0-beta.1
npm install --save-exact @datafog/node@0.5.0-beta.1
python -m pip install 'datafog-core==0.5.0b1'
cargo add datafog-core@0.5.0-beta.1

npm publishes to beta; the stable latest channel remains 0.4.4.

Included

  • Rust/WASM persistent workspace pseudonyms, preview/approval, committed-marker follow-ups, strict all-or-nothing restore with issue ranges, atomic batches and encrypted backup/recovery through the reference host workflow.
  • Source-marker preflight rejects damaged/unknown/unbracketed committed markers before approval and provides ranges for edit/retry. Stale WASM plans are reclaimed when the saved head advances.
  • Optional English GLiNER2.5 Small browser sessions with explicitly provisioned pinned assets; native engine selectors and configured descriptor metadata.
  • Fail-closed live cross-SDK parity and a complete versioned browser integration reference covering all 33 calls and 33 error codes.

Integrate

Browser integration contract · Model assets/runtime/CSP setup · Release checklist and verification evidence.

The host owns the vault, encryption, durable save/head comparison and user approval. Save the exact encrypted candidate before activation, then release text only after activation succeeds. Installing the package does not add a product UI or send-button policy. Model files (~297 MB) and matching runtime assets are provisioned separately.

Scope and limitations

Use synthetic data for this developer integration release. Workspace snapshots/API remain provisional; pin the exact beta and recreate disposable development vaults on upgrades unless a migration is explicitly qualified. Provider marker preservation, shipping-model detection qualification, complete snapshot backup coverage and vault review remain real-data pilot gates.

Browser Small is English-only, bounded to 65,536 UTF-8 bytes and 512 tokens including schema, with one inference at a time. It has no inference cancellation/deadline or automatic chunking. Loading can stall its owning page and uses substantial memory; native checkpoint accuracy does not qualify this browser model. Josh’s product still needs workspace/model integration and its own end-to-end acceptance.

Known open native issues include equal-span SSN/PERSON attribution (#84; the value remains redacted), the reported GLiNER2 contraction false positive (#85), CPU-only GLiNER2 device support (#86) and broader worker-fault/resource qualification (#90). Shared engine construction/registry and Decima are separate future work (#124–#127, #113).

Finding sources/recall target 0.5.0-beta.2; other future versions and decisions follow the requirements sheet.

Verification

Qualified source: 31157fe4a5d2ba42c9226675075245f9ed4b4abe. Actual packed-SDK runs in unpacked Chromium 151 and installed Chrome 156 pass all nine model/workspace gates, including real Small inference and encrypted restart recovery. Chrome retains CSP, sandbox and web security in disposable profiles. The unchanged extension commit 8310040 also passes format/typecheck/build and all 29 unit tests with the candidate SDK. Exact native qualification, publication workflow links and post-publication acceptance are recorded in #132.

Assets 3
Loading