NV Tech · the expedition board

Our Manzil.

Every route we are climbing, every camp we have actually reached, and the date each one is aimed at. Altitude here is time — not a number we gave ourselves.

15routes open
37camps reached
1summited

On the wall right now

The pitch being climbed today. It carries a date it can miss — that is the point of writing it down.

weather hold 6 days to the window

Samajh stops being a prototype — real accounts, real storage, real billing

summit is A parent signs in with Google on their own phone, their child works a problem with Jugnu, the app is closed; the next day that chat is still in the notebook, and a Jugnu Plus subscriber's token balance has visibly gone down

2026-08-11 → 2026-09-30

6 done · 7 steps

  1. Storage is live on Cloudflare D1. The hosted database exists, the schema is applied to it, and rows are written and read back from the deployed site — a real parent row landed and was queried back, which is exactly what this task set out to prove. The Postgres path stays as local development; production is D1 and the handlers cannot tell the difference.
  2. Sign in with Google works end to end on the deployed site: the OAuth code flow, the ID token verified against Google's own JWKS, PKCE, and an httpOnly session that keeps while it is used and signs out after thirty minutes idle. A real Google account reached an authenticated session and its parent row exists. Apple is deferred by choice — its button stays hidden until its four secrets are set — and is not a blocker.
  3. Identity: the provider subject is the key, never the email, and the access and refresh tokens are deliberately dropped
  4. Children, sessions, quizzes and now the chat itself are in the database, every route resolved through the signed-in parent. chat_turn is written for the first time: the transcript is sealed with AES-256-GCM before it is stored, a fresh IV per turn, and deleting a child takes the turns with it — verified as ciphertext in the column and readable again on the way out
  5. Every stored session carries the Jugnu version and the UI version that produced it. The earlier sessions show empty because they were saved while the engine was down, and an engine that is not live deliberately stamps nothing rather than guessing — an assumed version would be believed by the curve
  6. Documents and avatars are stored per child in the database, consent-gated: a photo is refused without consent and the bytes are deleted when consent is withdrawn. No R2 bucket, and none needed on the D1 path
  7. REMAINING — Jugnu Plus, the dream's third pillar, real billing, is not built. Server-side debit is live and proved against a real balance — the engine charges the account ledger for every reply and quiz, idempotent on ref — but nothing credits it: Apple IAP is cancelled (this is a web page) and the card payment that would replace it is unwritten, so there is still no way to subscribe. This is the one thing between a live app and the dream being reached.

Summited & closed

Dreams that finished. Kept whether they were reached or missed — a board that only shows what is still open cannot show that anything was ever done.

summited2026-08-10 · 6 days inside the window

NV Tech site live in production

summit was teamnvtech.com serves the site over HTTPS, and a waitlist signup submitted from my phone arrives somewhere I can actually read it

Finished 2026-08-10, six days inside the window. Cloudflare Pages + teamnvtech.com over HTTPS, and the notify form made real: Turnstile -> WAITLIST KV -> Resend, with an end-to-end submit from the phone confirmed arriving (deploy cf7d0b9).

aimed at 2026-08-16

The routes

One line per venture. Each dot is a camp — something that happened, on a date. A long route folds in the middle: it opens at the first camp, skips to the last few, and the small dots are the ones you can unfold. The flag is the year it is aimed at, not a promise it will land there.

2027
NV-01

Someday

Family finance

The first money they'll be glad they didn't spend.

1 camp · aiming at 2027 · building

  1. Jul 28, 2026

    Identified as a build area. Probe being scheduled with three families.

2027
NV-02

Saath

Matrimony

Introductions, not a filter grid.

1 camp · aiming at 2027 · building

  1. Jul 28, 2026

    Identified as a build area. Named Saath.

2026
NV-04

Bazaar

Small business

Built to empower small business owners.

1 camp · aiming at 2026 · building

  1. Jul 28, 2026

    Named. Brief not written yet.

2027
NV-05

Bhav

Markets

What the options tape is paying for — and what it will not say.

1 camp · aiming at 2027 · building

  1. Jul 28, 2026

    Engine, board and stock search built and running against live CBOE and Finviz data. No backtest yet.

2027
NV-03

Unnamed

Insurance

Cyber cover priced on what you actually run.

1 camp · aiming at 2027 · building

  1. Jul 28, 2026

    Identified as a build area. Needs a name before probe.

2027
NV-06

Kadam

Focus and growth

The app that gets harder.

1 camp · aiming at 2027 · building

  1. Jul 31, 2026

    Thesis written and prototype built. Scores 1-for-4 on the studio screen — the retention probe decides whether this goes further. Name is a placeholder.

2027
NV-07

Parakh

Developer tools

Find your floor.

1 camp · aiming at 2027 · building

  1. Aug 2, 2026

    Thesis written and prototype built. Scores 1.5-for-4 on the studio screen. The probe runs on the studio itself, so it costs nothing but has the founder-as-first-user trap attached. Name has a known collision with India's NCERT assessment centre.

2028
NV-08

Jauhari

Talent

The jeweler's eye for how people think.

2 camps · aiming at 2028 · building

  1. Aug 1, 2026

    Thesis written and probe instrument built — frozen rubric, blind scoring protocol, analysis with kill criteria. Scores 0-for-4 as a consumer network, ~2.5-for-4 as compliance-first hiring assessment. The probe subject is the founder's own judgment: the first thing tested, not the market.

  2. Aug 3, 2026

    Clickable prototype of the scout's instrument built — the log, a read with cited evidence, the too-thin refusal, the ledger, and the thirty-second gut capture. Five views, no engine behind them.

2027
NV-09

Andaza

Judgment and forecasting

Score the read before you know.

1 camp · aiming at 2027 · building

  1. Aug 4, 2026

    Thesis written and the instrument built. Scores 1-for-4 — the sixth consecutive consumer venture to land there, which is now a note about the screen as much as the venture. The probe runs on the studio's own eight theses, none of which has ever been scored.

2027
NV-10

Sanad

AI security

The record of what the machine was allowed to read.

1 camp · aiming at 2027 · building

  1. Aug 5, 2026

    The spec turned out to be a diagram of a product that shipped eight months earlier. Rather than bury that, the thesis leads with it: do not build the enforcement layer. Three capabilities survived the check because nobody sells them, and one wedge appeared the same day the research ran — Anthropic’s Inference Hooks, which make a clientless approval point possible for the first time. Scored 3 of 4 on the studio screen, the joint best in the folder, and still nothing is built beyond a staged plan.

2026
NV-11

Samajh

Education

The answer you reached yourself.

18 camps · aiming at 2026 · live

  1. Aug 7, 2026

    Thesis written and the first prototype built. It scores 0.5 out of 4 on our own screen — the lowest in the folder — and we published that rather than hiding it.

  2. 14 camps between
    1. Aug 8, 2026

      The tutor got a name: Jugnu, the firefly — a small light that cannot flood the page. The mode that refuses the answer is called Apne.

    2. Aug 8, 2026

      Ask anything, typed or photographed, in any subject. Essays get a grammar pass that never writes a line for you. Sign-up, a parent link, and a short quiz that tunes how Jugnu talks.

    3. Aug 8, 2026

      The notebook works: it starts empty, saves only when the student says yes, and the summary describes what actually happened — never the answer.

    4. Aug 8, 2026

      Profiles: a photo and a name, kept on the device and nowhere else. Jugnu greets you by name. Noted for the real build: a child's name is protected information and we ask for it before consent, which has to be the other way round.

    5. Aug 8, 2026

      A monster maker: instead of a photo, a student can build one of Jugnu's cousins — furry creatures with horns and paw pads, 60,480 combinations.

    6. Aug 9, 2026

      Jugnu became a real tutor instead of a script. It runs on a live AI model, and the rule that it never hands over the answer is now enforced by our own server rather than asked of the model. We tested why: a small model refused four times, then gave the whole answer when asked for “the same problem with a different letter”.

    7. Aug 10, 2026

      Jugnu now runs on a phone. Point your camera at a QR code and it loads — no typing, no app to install. Voice needs a secure connection, so there is a mode that sets one up.

    8. Aug 10, 2026

      Fixed a bug that stopped the app starting at all. Nothing else changed — it had shipped broken, and that is worth writing down.

    9. Aug 10, 2026

      You can tell Jugnu how to talk to you — but if you say you are stupid, or that a parent will be angry, that instruction is dropped for the rest of the conversation. The tone changes; the rule about never giving the answer never does.

    10. Aug 10, 2026

      The notebook now separates what you were given from what you wrote. Files are read on your own machine and never uploaded, and if a scan is unreadable Jugnu says so instead of inventing a summary. Twenty-four screens to thirty-one.

    11. Aug 10, 2026

      Free help now follows your account, not your phone, and resets 24 hours after you first use it. We store a scrambled version of your email, never the address itself. You do not need an account to start.

    12. Aug 10, 2026

      Jugnu Code: a separate room for building things, with its own monthly budget so it cannot eat into homework help. Code it writes runs in a locked-off preview that cannot reach your notebook or your saved work.

    13. Aug 11, 2026

      The door is Google or Apple and nothing else: no password to invent, none stored. On this build the buttons let you in and say on screen that this is what they did, because Apple will not talk to a laptop at all and we would rather admit that than let a stand-in wear the logo. And the personality setting is gone one day after it arrived — the largest instruction in the file, and a small model recites a voice rather than adopting one. Nothing that keeps Jugnu honest was reading from it.

    14. Aug 11, 2026

      Samajh on a laptop — the same app, and literally the same record, so a problem worked on the phone is there when the laptop opens. Width is not more room for the same layout: the hint ladder moves beside the conversation and says what each rung costs before you spend it, and Jugnu Code runs your program next to the chat that asked for it. There is still no reading a page from a photo, so the web build takes a screenshot, shows it, and asks you to type the question — saying why.

  3. Aug 12, 2026

    Signing in became real. The proof Google or Apple hands back is checked on our server against their own published keys instead of being taken on trust, the session is a cookie the page's scripts cannot read, and we keep the provider's id for you and deliberately throw away the token that would let us into your Google account. Twenty-seven tests hold it.

  4. Aug 12, 2026

    Your work moved off the phone that made it. Nine tables now hold children, sessions, chats and quizzes — written for both the database we deploy on and Postgres, so the choice of host is not a rewrite — and every one of them is reached through the parent who signed in. It is not switched on yet: the database itself has not been created, so nothing is stored anywhere but a laptop.

  5. Sep 4, 2026

    Samajh is live. It has its own address — samajh.me — and Google sign-in works end to end: you go to Google, come back, and a session that keeps while you use it and signs out when you have walked away. The tutor, the quiz, the code room and the reader that opens a PDF or a .docx all run on the same origin as the page, backed by a real database rather than a laptop. Being live does not move the score: it is still 0.5 out of 4 on our own screen, and the question the thesis asked is still unanswered — a live app is where you start finding out, not proof of anything.

2028
NV-13

Kasauti

Judgment and forecasting

How the decision was made, scored before anyone knows if it worked.

1 camp · aiming at 2028 · building

  1. Aug 11, 2026

    Eight load-bearing claims were checked the day this was drafted and two changed the verdict. The service the idea described scores 1 of 4 against an incumbent that has shipped the shape since 2018. The narrow compliance form scored 3.5 and was split out under its own name rather than left blurring this one. What is committed to is the instrument only: a frozen rubric and ten commands, free to run on the studio itself, with the noise check as the first thing that could sink it.

2028
NV-14

Zabta

AI governance

Proof a human actually oversaw the machine.

1 camp · aiming at 2028 · building

  1. Aug 11, 2026

    Split out of Kasauti on the day Kasauti was written, because the compliance form scored 3.5 against the service form’s 1 and leaving them in one file would have let the good score cover for the bad one. The instrument was built the same day; the venture was not. What it owes before a thesis is worth writing is a real compliance read and an incumbent check — the AI governance platforms almost certainly already sell an oversight-evidence feature, and if they do, this ends here.

2026
NV-15

Shajra

Provenance

Where the code came from, link by link.

5 camps · aiming at 2026 · building

  1. Aug 27, 2026

    Thesis drafted from model memory — the first in the folder shipped without a verification pass, and it says so on line one. The probe was built and armed the same day: advise, record, trace and a graph view over git notes, three frozen kill criteria, and the founder's confidences recorded first as Andaza reads #7–9 — which jointly give a ~42% chance at least one kill fires.

  2. Aug 28, 2026

    Two more design passes grew the vision toward a graph-native control plane; the thesis froze a rule alongside the kill criteria instead — no fourth design pass until the probe has data. Every edge now carries its basis: observed, declared, or inferred.

  3. Aug 28, 2026

    The founder overrode the phase gates — "implement fully" — and Phases 2 through 5 shipped the same day: the observed code graph, branch semantic deltas, three-way reconciliation with a passing acceptance demo (a semantic conflict found where git reported none, with merge order and the protecting test named), node contracts whose evidence goes stale when the graph moves, and a merge gate that blocks only on observed evidence and is lifted only by auditable overrides. The probe was not widened to flatter the build: its three kills stand unchanged and resolve Sep 29.

  4. Sep 16, 2026

    The lineage got a room you can walk around in. The repository's history imports as a 3D graph — git in grey, provenance in colour — where any node opens, scanners plug in per node or across a selection (an in-house data-leak pass, dependency advisories, adapters for outside tools), and a finding is traced back to the commit that introduced it, with the diff. Above the graph sit views for people who never open one: the same repository read as a CEO, an SVP, a VP, engineering leads, security or a reviewer would — each a persona written in Markdown that an admin can duplicate and rewrite — and a top-down security posture: the bill of materials, what escapes to the release branch, what is past its deadline, how the third-party code is ageing. None of it touches the probe: the room never writes a note, and an opened view counts toward nothing. The three kills stand unchanged and resolve Sep 29.

  5. Sep 18, 2026

    Shajra has an address: teamnvtech.com/shajra. Anyone can sign in with Google and ask to come in; nobody is asked for a password, and only the people an admin lets in see anything — the repository it reads is the studio's own, ledgers and all, so the door is open and the room is not. The site's edge proves who is asking, a signed header carries that to the server, and the server keeps the list. It runs from a laptop behind a tunnel, which means it is up when the laptop is: an honest address, not a service. Two things broke on the way and are fixed — a sign-out that signed nobody out, and a page that drew the last graph it remembered before it had asked who you were.

2027
NV-12

Manzil

Direction

The destination the steps are for.

1 camp · aiming at 2027 · building

  1. Aug 9, 2026

    Built as the missing layer above the four instruments, not as a market bet — no thesis, no screen score, and last on the board for that reason. It exists because the studio could measure its floor, its people and its reads, and could not say what any of that was in service of. First honest test is whether it survives a month of use, which the four instruments below it have not yet had.