I build AI systems and the products that carry them. One set of agent rules that runs above the model you already use, plus products shipped end to end — most of them Hebrew-first: business systems, a visual HTML editor, a private PDF workspace, 42 browser tools and signed lead pipelines.
Independent, in Israel. Everything below is live, and every number on this page is measured, not guessed.
Most of my AI work lives in fabius — a plugin, not a platform: 22 routing rules and 15 non-overlapping skills, loaded above whatever model you already run — Claude, GPT, Gemini, Mistral, Grok and the rest. The agent is the easy half. The apparatus around it is the work.
|
Each task is answered by the bare model, a "be concise" control and the plugin's rules, then blind-scored. The four-panel benchmark keeps its controls, regressions and limits beside the wins. |
Each release carries a SHA-256 Merkle root over the skill contracts, an Ed25519-signed tag and an OpenTimestamps Bitcoin anchor. Pending is reported as pending; |
Behaviour is a versioned routing core, an identity contract and 15 skill contracts. Adapters serve Claude Code, Codex and Grok Build; a zero-dependency suite checks the contracts, links and routing rules. |
|
AI specification and implementation for businesses My agency. A 23-page Hebrew RTL system for websites, CRM, automation, agents and GEO. Its homepage turns 28 concrete offers into one guided product story; a Gemini agent qualifies the lead in the conversation, then an HMAC-signed Cloudflare pipeline stores and routes it.
|
A plugin, not a platform — one set of rules above every model One stance — scout wide, strike narrow — as 15 non-overlapping skills and 22 routing rules that install into Claude Code, Codex or Grok Build and run on the model you already use. Version 2.7.1, sealed and reproducibly checked before release.
|
|
A private, mobile-first Hebrew PDF workspace Sign, stamp, merge, compress and edit in a responsive workspace — the document operations run locally in the browser. A separate verifiable SEAL flow binds a file to a hash anyone can re-check, protected at the edge by Turnstile and a Cloudflare Worker.
|
Visual HTML editor with clean source underneath Design a landing page visually and export clean HTML — nothing to install. Start from 70 brand templates or use Mix mode to fuse three systems into one direction; the editor stays RTL-aware while account authority and publishing run through Cloudflare.
|
|
42 privacy-first developer tools Nine groups for hashing, encryption, signatures, key derivation, generation and conversion — from HMAC and Argon2id to Shamir secret sharing, PASETO and post-quantum ML-KEM/ML-DSA. Computation stays in the browser. Only two explicit lookups leave the page, DNS-over-HTTPS and a k-anonymity Have I Been Pwned check, and only when triggered.
|
11 case studies, each with a live demo A no-build Hebrew RTL site with dark landing surfaces and quiet reading pages behind them. Each selected case study opens both the written work and the running product; a filterable project index, long-form writing, an on-site AI assistant and an HMAC-gated Cloudflare lead pipeline complete the system.
|
A prompt you cannot diff is a prompt you cannot fix. Stance, routing and skills are versioned documents an agent loads verbatim, so a change in behaviour is a diff, a review and a tag — never an edit in a chat window.
Nothing ships on "looks right". A change is checked against the running system, not the source — headless browser, real URL, console and network asserted. Code reading is fine for fixing and not for concluding.
Claims carry receipts, including the ones that hurt. Benchmarks keep regressions visible, release seals distinguish pending anchors from confirmed ones, and research corrections stay in the record rather than disappearing behind the next version.
A trustless anchor for document provenance ↗
A signature proves who. It does not prove when — and in the generative-AI era, when is the field that decides whether a document is evidence or a fabrication. A 63-page position and architecture paper on sealing files so their provenance survives adversaries, transcoding, hash breaks and decades of time.
It makes exactly three claims — a trustless timestamp anchor whose anti-backdating bound terminates in Bitcoin, a verifiable soft-binding resolution registry built in the Certificate-Transparency pattern, and salted, renewable seals that survive a hash-function break — and is explicit about what it does not claim: hard and soft binding of what, who and when is C2PA and JPEG Trust's, and an earlier draft claimed it as novel before review established it was already an ISO standard.
The published reference package regenerates every figure in the paper — 15/15 tests against a registry contract with no owner and no upgrade path, a 17-vector conformance suite with real ML-DSA-65, and the benchmarks — so nothing has to be taken on faith.
Solidity EIP-712 OpenTimestamps Certificate Transparency ML-DSA-65
Work with me ↗ · Portfolio ↗ · All repositories ↗
Stat bar, cards and snake are generated and served from this repository — no third-party README services.