zetizeti

It asks the questions. You do the thinking. One voice helps you develop an idea; the other stress-tests it — to see if it holds.

A questioning partner for design students. Name the edge you're trying to develop and the stone asks back, grounded in the real tensions of your discipline — or bring an idea you want to stress-test, and it questions that to see whether it holds, pointing to where the text quietly decided for you. It never hands you the answer; the thinking stays yours.

The name doubles zeti, from the Greek zetetic — "proceeding by inquiry" — with an echo of the Sanskrit neti neti, "not this, not this". What the two voices are →

Nothing is ever saved.

Begin an enquiry

Name the edge you're trying to develop and the stone asks back, grounded in the real tensions of design. The thinking stays yours. Nothing is saved — each enquiry lives only while this tab is open.

Nothing is ever saved.

‹ new enquiry
grounded in design · name the edge, then it sharpens
‹ new student
author mode · building 2.0 · captured locally

You are the stone. A student is play-acted — question it as only you do. Your questions fill .capture/zetizeti-testchats.jsonl.

you question · a student is play-acted · your questions are captured

Where your enquiries have travelled

Progress here is not a score. It's the edge getting sharper — how many times you re-drew each goal, and the line from vague to sharp. Private to you.

‹ back

The two voices

zetizeti is a whetstone. A whetstone does not cut for you; it is the stone you draw your own edge against. It asks; it does not answer. It has two voices — one helps you develop an idea, the other stress-tests an idea to see if it holds; both ask questions in your own words, and neither hands you a conclusion.

first voice · to develop

It helps you develop your own idea

You name an edge — what you are trying to do, and where it resists you. The stone asks back, each question grounded in a real, unresolved tension of your discipline. It does not resolve the tension for you; it keeps you in the question long enough to think. This is the older harm it was built against: the answer dropped in too soon, before you have done the thinking that would make it yours. An information gap a sentence can close; an understanding gap only your own movement can close. The stone refuses to close the second one for you.

second voice · to stress-test

It stress-tests an idea — does it hold?

Bring an idea you want to pressure-test — a conclusion you reached in an enquiry, an answer a machine handed you, a claim you found anywhere — and paste it in. The stone questions that text instead of you. A settled idea, wherever it came from, is a conclusion already sitting in your understanding; the question worth asking is whether you reached it, or it was simply deposited there. So the stone does to the text what it does to your own premature certainty — it locates the spots where the text quietly decided something for you (called a thing "intuitive", "best practice", "obviously" — a judgement worn as a description) and asks you about those spots.

What this voice wants. Not to tell you the idea is wrong. It never grades the text, never marks it right or wrong — that would only be a second deposited verdict, this time the tool's. It wants to give you back the act of judging. It locates; you decide. It is the neti neti of the name turned outward — "not this, not this" — subtracting the text's smuggled certainties until what is left is yours to weigh.

Nothing is kept. A critique lives only while this tab is open — the text you paste and the questions asked are never saved, never scored, never ranked, never compared against anything, never rolled into a profile. There is no list and no history; each reading stands alone and then it is gone. That refusal of the aggregate is the line the split-ratio practice this borrows from cares about most: a reading is a self-frame, never a benchmark — and here it cannot become a tally, because no record of it survives.

how the second voice reads · its method

The reading is made of rules you can read

When you paste a text in, nothing about it is decided by a model. It is first broken into segments, and each segment is tagged by plain, stated rules — is this describing, or is it quietly deciding? A value worn as a property (the clean interface), a directive (you should…), a verdict relayed as settled (obviously, best practice) — each is caught by a rule about grammar and a short list of words, not by anything trained on the open web. A second step, also only arithmetic, settles which of those spots the question will point at. Only then does the model arrive, and only to do one thing: phrase a single question about that one spot, in the text's own words. A last check confirms what comes back is still a question, and carries no verdict of its own.

This is deliberate, and it has three consequences worth naming plainly. The reading cannot fail — there is no model call to time out or hallucinate; the worst case is that a spot reads as neutral. It is reproducible — the same text yields the same spots every time, not a different mood on a different day. And it is inspectable — every spot it marks carries the reason it was marked, down to the exact word and the rule that caught it. You can ask the tool why, and get an answer you could check by hand.

Its blind spots are a list, not a mystery. What the tool treats as a deciding word is a short, readable list — not weights you must take on trust. It is deliberately blunt: it would rather miss a smuggled verdict than invent one where there is none. And when it does miss — and it will — the fix is a line added to that list, something you can see and argue with, not a retraining no one can audit. The model does the language; the rules do the locating; you do the judging. Where another tool asks you to trust what it cannot show you, this one shows you how little it is deciding.

what holds across both

Questions only. The thinking stays yours.

The second voice is not a looser version of the first — it is the same discipline, held tighter. Both speak in questions and nothing else. Both reuse your exact words rather than paraphrasing them. Neither explains, advises, reassures, concludes, or scores. There are no grades here, no leaderboards, no percent-complete — only the edge getting sharper, which is private to you. It asks the questions; you do the thinking — whether the premature answer came from you, or from a machine.

All of this is open and checkable — the code, the corpus, the locating rules, and the full verification records (citation ledgers, adversarial passes, sign-off sheets): github.com/zetizeti/zetizeti (AGPL-3.0). Nothing here asks to be trusted; it asks to be read.

Made by Prayas Abhinav.

‹ back

Stress-test an idea — see if it holds

Bring an idea you want to stress-test — a conclusion you reached in an enquiry, an answer a machine gave you, a claim from anywhere — and the stone questions the text to find out whether it holds: pressing where it might not, pointing to where it quietly decided something, where a judgement was slipped in as fact. It never grades it, never says "this is wrong": it locates, you judge. Each critique lives only in this tab — nothing is saved, and it is never scored, ranked, or compared. Each stands alone, then it is gone.

▷ see an example — no key needed
‹ back
nothing saved · never scored or compared
‹ back

Usage

Key usage across users — pool and personal — with turns, spend, and when each was last active. The pool figure runs against the ₹ ceiling; personal spend is shown apart. Read-only; no message content is shown. Figures are the real billed cost, converted at the live rate.