semanticquant · collection · one event, every code
A Promise
Six words about Friday, said on Tuesday.
One event, four instruments. Each section reads the same sentence in its own code; colour marks the destination site.
Tuesday afternoon. A colleague leans into your doorway on the way out: "I'll have it to you by Friday." You say thanks. You block out Friday afternoon to review a document that does not exist yet, and you schedule Monday's meeting on the strength of one sentence.
MatheMetaphor A martingale with a deadline
Behind the sentence sits an estimate, and estimates updated coherently form a martingale: today's best guess of Friday's state equals today's expectation of tomorrow's guess. If your colleague can already foresee Thursday's "it's slipping" message, Tuesday's promise was mispriced — a predictable revision is a revision owed now. Martingales give the law; the promise adds a stopping time, Friday, at which the estimate is forcibly settled against the world. The sentence also does coordination work: said aloud, the deadline becomes common knowledge — each of you knows the other is planning on it, and knows the other knows. And because words are cheap, the commitment borrows credibility from costly signaling: what a broken Friday costs the promiser is what the promise is worth.
CommuniCoupling The knot of mutual waiting, cut
Before the sentence, you and your colleague sit in double contingency: your plan waits on what they will do, their effort waits on what you expect, and each expectation models the other. The promise cuts the knot by binding one side first — a self-imposed constraint that makes the other's planning possible. The simulation would show two agents oscillating while each conditions on the other, then locking into coordinated trajectories the moment one commits; the readout worth watching is how much downstream activity one cheap utterance unlocks. The promise also installs a definition of the situation: from Tuesday on, the document is owed, lateness is a breach rather than an absence, and both parties act inside that definition until Friday tests it.
SocioRhetoric A belonging-seeking commissive
In the catalogue this is the Promise, a commissive: it binds the speaker to a future act, and the world is expected to fit the words. The built entry is still to come — the catalogue locates it — but the axes already place it: Orientation keyed to reality, Motive cooperative, Target outward, with a characteristic slide toward the belonging plane, where "I'll have it by Friday" performs reliability-as-membership and its keeping is incidental. Inside it hides an assertion about the future — a delivery estimate under commissive grammar — and its neighbouring misfire is the palter: a technically sincere sentence engineered to be heard as more certain than the speaker is.
ExploRational Moves for Thursday, run on Tuesday
When Thursday arrives with a bad feeling, the opening move is the premortem: "It is Friday evening; the document never came. Write the history of why." Run it on Tuesday and the failure causes surface while they are cheap — the dependency nobody mentioned, the review that eats Wednesday. Second, trade the binary promise for degrees of belief: "Will you have it by Friday?" invites performance, while "What odds on Friday?" invites a number, and a number can be argued with, tracked, and updated without loss of face. Third, surfacing the assumptions: the promise assumes the spec is stable, the week has no fires, and "it" means the same document to both of you. Say those aloud and Friday gets likelier.
The four readings disagree about what was said on Tuesday: an estimate awaiting settlement, a constraint that lets two futures mesh, a performance of reliability, or a bundle of assumptions nobody has yet said aloud.