DEV Community

Shi
Shi

Posted on AI-assisted

יומן הבטחות — Hebrew promise-ledger for מסמך (not a CRM) · Path Two

#sanity #sanitychallenge #nextjs #hebrew

Sanity Challenge Path Two Submission

Path Two: יומן הבטחות (promise-ledger)

Challenge: Sanity Challenge 2026

Path: Two — Vibe-code something strange

Brand / DEV: מסמך / כלים נבחרים · kelimok47

Sanity project ID: 8axt363c

Dataset: production (free)

Public app / repo: add URL after deploy

Method label: BUILD-FROM-SELF

Live free-project ID from Sanity manage (org כלים נבחרים). Do not publish this post until review.

Checklist

  • [x] Working app + Sanity schema/Studio behind it
  • [x] Real Sanity project ID above (8axt363c)
  • [x] Tag #sanitychallenge
  • [x] Honest build-process writeup (incl. NEED_TOKEN / demo path)
  • [x] Torah / brand root stated (not an English CRM clone)
  • [ ] Seed docs in Lake via Studio login (NEED_BROWSER)
  • [ ] Publish on DEV as kelimok47 after approval

Overview

יומן הבטחות is a Hebrew RTL promise ledger for מסמך leads (and כלים נבחרים when relevant).

Someone asks for a document / quote. We promise an answer by a date. The ledger records:

  • who asked
  • what they asked
  • what we promised
  • due date
  • status: received → promised → in_progress → done / released

Not a CRM. No funnel, no drip spam — a notebook for keeping your word.

Torah root

«מוצא שפתיך תשמור» — speech creates obligation. The product encodes that for a small Hebrew-brand business: write the promise down, fulfill it, or release it with dignity.

BUILD-FROM-SELF

Built from our own ops need (מסמך / כלים נבחרים · kelimok47), not a translated SaaS template: Hebrew-first schema titles, RTL board, brandTag mismach | kelim, and a Studio structure ordered by due date / honor-release — not pipeline stages.

Why Sanity

  1. havtacha documents in the Content Lake
  2. Custom Studio structure (open by due date / released)
  3. Status as workflow data next to the content
  4. Embedded Studio at /studio beside the Hebrew board

Build process (honest)

Started: 2026-09-20 IDT — inside the challenge window (Sep 18–Oct 4, 2026).

Method: AI-assisted vibe-coding under free-stack constraints (kelimok47, Path Two, no autonomous publish).

What AI/agent did:

  • Scaffold Next.js 15 + embedded Sanity Studio
  • Schema havtacha + Hebrew Studio lists
  • RTL ledger UI + demo מסמך / כלים rows
  • Wired live project 8axt363c / production in .env.local and config fallbacks
  • Attempted npx sanity schema deploy → NEED_TOKEN (“login first”); kept read-only + demo fallback until Studio login
  • Drafted this DEV post with #sanitychallenge

What still needs a human browser (kelimok47, free only):

  1. Log into /studio, allow localhost CORS if asked
  2. Create 2–3 הבטחה documents (schema then lives in Lake via Studio)
  3. Fact-check this writeup; keep plan on $0 Free (no Growth pay)
  4. Publish on DEV with #sanitychallenge only after approval

Deliberately not done: fake project ID; English CRM clone; paid tier; CLI write without login; autonomous DEV publish.

Local-first honesty: / shows demo rows while the Lake is empty; footer says “הדגמה מקומית” until real docs exist.

Schema (havtacha)

Fields: title, requesterName, requesterContact, pninaSummary, promiseText, dueDate, status, releasedAt, releaseNote, brandTag (mismach | kelim), internalNote.

How to test

  1. Open app (npm run dev → localhost:3000) — Hebrew יומן הבטחות board
  2. /studio — login as kelimok47 → create הבטחה for a מסמך lead
  3. Refresh / — leaves demo banner when Lake has docs
  4. Mark done/released with release note

Links

  • Sanity project ID: 8axt363c
  • App / code: TBD · path business-os/projects/sanity-challenge-2026
  • Brand DEV: kelimok47

Credits

Sanity Challenge 2026 · מסמך / כלים נבחרים (kelimok47) · AI-assisted; human review before publish · BUILD-FROM-SELF

Top comments (0)