Dokimazo

Origin and Language

Dokimazo (δοκιμάζω) is a Greek verb that meant, first and concretely, to assay. It was the word for what a merchant or a money changer did with a coin: hold it to the fire, test the metal, weigh it, and find out whether the face stamped on it told the truth. From that physical act came the wider meaning the New Testament writers leaned on: to examine something, to prove it, to discern whether it is genuine, and then to approve what passes.

The related noun dokime means tested character, the quality left in a thing after it has been through the fire. Another relative, dokimos, means approved or genuine, the coin that survived the assay. The whole word family carries a built-in sequence. There is a test, and there is a verdict, and the verdict is earned rather than assumed. Dokimazo is not suspicion, and it is not blind acceptance. It is the work in between.

Scriptural Witness

Paul uses the word at the close of his first letter to Thessalonica: “Prove all things; hold fast that which is good” (1 Thessalonians 5:21, KJV). The “prove” there is dokimazo. The instruction has two halves that belong together. Test everything, and then hold, with a grip, what proves good. Neither half works alone. Testing without holding collapses into mere cynicism. Holding without testing is how a counterfeit gets into the purse.

The same verb shapes Romans 12:2, where Paul writes that the renewed mind exists so a believer “may prove what is that good, and acceptable, and perfect, will of God” (KJV). And in 1 John 4:1 the apostle writes, “believe not every spirit, but try the spirits whether they are of God” (KJV); the word behind “try” is the same root. Scripture treats testing not as a failure of faith but as an exercise of it. Faith that cannot examine what it is asked to swallow is not strong faith. It is unguarded faith.

The Pattern Across Traditions

The instinct is older and wider than the epistles. The Stoics built a daily practice around it. Epictetus taught that the first and hardest task is to test impressions as they arrive and not be carried off by them, to hold an impression at arm’s length and ask whether it is what it claims to be. Marcus Aurelius returns again and again in his Meditations to the habit of stripping a thing down to see it plainly before reacting to it.

Greek philosophy gave the wider culture the word and the practice. Scripture gave it a direction. The Stoic tests an impression to keep his own peace. Paul tests all things in order to hold fast the good, which means the testing serves something beyond the self. The aim is not detachment. The aim is to end up holding what is true.

How It Lands in the Age of AI

An AI agent is, in the precise sense, a thing that cannot perform dokimazo on its own. It reads a web page, an email, a document, and it has no firm wall between the parts it was asked to consider and a command hidden inside them. It cannot assay the coin. It accepts the face. That is exactly the gap a hidden instruction exploits, the failure mode TWO covers under indirect prompt injection.

This is why an ancient assayer’s word suddenly describes a 2026 engineering problem. When intelligence becomes fast and cheap, as it did at this year’s Google I/O, the temptation is to let the quick answer stand because testing it costs the time the quick answer seemed to save. Dokimazo names the missing step. The model can produce. It cannot, by itself, prove. That work stays with the person who deployed it.

How TWO Uses It

TWO uses dokimazo as the counterweight to its own enthusiasm for building with AI. The TWO position is that operators should use these tools eagerly and widely. The discipline that keeps eagerness from becoming recklessness is the assay: before an output ships, before an agent is trusted with an action, someone holds the coin to the fire. This is the practical content of discernment and the close cousin of nepsis, the watchfulness that does not drift off while the work runs.

In editorial terms, dokimazo is why a TWO digest will report a benchmark and then ask what the benchmark does not test. A model that scores well on a public exam has been measured against that exam, not against your contracts. The verdict that matters to an operator is not the one the vendor published. It is the one you reach after the work has been through your own fire.

A Closing Discipline

Pick one place this week where you have been holding a coin without assaying it: an AI draft you forwarded unread, an agent you granted a permission and forgot, a summary you trusted because it sounded confident. Run the test you skipped. Then decide, on the evidence, whether to hold fast or let go. Prove the thing, then grip what is good.