Curriculum · Filing an intent (intent/1)

Filing an Intent: Opening the Loop

5 lessons · For: Anyone who wants a matcher — not a human reading a page — to act on what their organization is trying to do

Most collaboration between organizations starts with a human reading a page and deciding to reach out. That does not scale to an economy of agents. An intent is the machine-readable alternative: a statement of what you want, filed so a matcher can find it and act on it without a person in the middle.

This is the first step of the four-product loop taught in The GatewayZ Loop, seen close up: how an intent is shaped, and why its shape decides whether it can be answered at all.

Five short lessons. You will finish able to file an intent that routing can actually act on, and to see why a vague one is the same as no intent at all.

Lessons

The loop begins with a want, stated for a machine

You should be able to: Explain what an intent is and why it is filed rather than described in prose.

An intent is a machine-readable statement of what an organization is trying to do — filed as data a matcher reasons over, not written as prose a person has to read and interpret. It opens the collaboration loop: intent, then a match, then a consented introduction, then a sealed outcome.

Filing it as data rather than prose is the whole point. A page describing what you want can be found by a search engine and read by a human; an intent can be matched by an agent against the declared capabilities of every organization on the mesh, at once, without anyone reading anything.

So the discipline of a good intent is the discipline of any estate record: say the thing precisely enough that a machine can act on it, because a machine is exactly what will.

Source: IntentMesh — stating an intent

An intent with no "wants" is invisible

You should be able to: State why an intent must name what it wants, or it cannot be routed.

The one thing an intent cannot omit is what it wants. An intent with nothing it wants is invisible to routing — there is nothing for a matcher to match against, so it reaches no one, no matter how it is phrased. This is the same refusal the estate’s other formats make: a record missing its load-bearing field is not a lenient record, it is one that cannot do its job.

Concretely, "we are open to opportunities" is not an intent — it names no want a capability could satisfy. "We want a market-making desk for a gold-denominated instrument" is, because a matcher can compare it to what organizations declare they can do.

So before filing, ask the matcher’s question of your own intent: what declared capability would answer this? If you cannot name one, the intent is not yet routable, and filing it changes nothing.

Source: IntentMesh — an intent with no wants is unroutable

A request, not a commitment

You should be able to: Distinguish filing an intent from agreeing to work with anyone.

Filing an intent commits you to nothing and to no one. It is a request that opens the loop; it does not choose a counterparty, accept a match, or authorize any work. Everything downstream still passes through consent — a match is a suggestion, an introduction needs a human yes on each side.

This matters because the ease of filing could otherwise feel like exposure. It is not: an intent is discoverable to the matcher, but discovery obeys the same consent as listing, and nothing about having filed an intent obliges you to say yes to what comes back.

So an intent is safe to file the moment you can state a real want. It starts a conversation the rest of the loop governs; it does not pre-commit you to the outcome.

Source: Flashy Academy — The GatewayZ Loop

Intent is the future tense, pointed outward

You should be able to: Relate an intent to the estate’s two tenses.

You have met the estate’s two tenses: the backlog (what you intend, internal, decaying) and the shiplog (what you did, sealed). An intent is a third thing — the future tense pointed outward. Not "here is our roadmap" for our own reference, but "here is a specific thing we want help with, stated so a stranger’s agent can find it."

Like the backlog, it is provisional and about the future; unlike the backlog, its whole purpose is to be seen by other organizations, so it is shaped for matching rather than for private planning. When an intent is answered and work settles, the outcome becomes past tense — a sealed record — closing the arc from want to proof.

Holding the three tenses together is the mental model: intent opens outward, the backlog plans inward, and the shiplog records what actually happened. Each is shaped by what it is for.

Source: Flashy Academy — The Two Tenses

From intent to a match

You should be able to: Describe the handoff from a filed intent to the matcher, and what you do next.

A filed intent is picked up by the mesh matcher, which finds organizations whose declared capabilities fit it — grounded in their charters and directory fragments, not their marketing. What comes back is a set of candidates, each of which is a suggestion you may pursue, never a connection already made.

Your next act is a human one: review a candidate and, if it fits, ask for a consented introduction — which hands off to Magician and the rest of the loop. The intent did its job the moment it was matchable; from here the loop’s consent machinery takes over.

That is the arc in miniature: you state a want as data, the mesh finds who could answer, and you decide whom to actually engage. An intent is how an organization enters that arc on its own terms rather than waiting to be found.

Source: Flashy Academy — Joining the Mesh

Frequently asked

What makes an intent routable?

Naming what it wants in terms a matcher can compare to declared capabilities. An intent with nothing it wants is invisible to routing — it reaches no one. "We are open to opportunities" is not an intent; "we want a market-making desk for a gold-denominated instrument" is.

Does filing an intent commit me to anything?

No. An intent is a request that opens the loop; it chooses no counterparty and authorizes no work. Everything downstream passes through consent — a match is a suggestion, an introduction needs a human yes on each side — so filing exposes a want to the matcher without obliging you to accept anything that comes back.

How is an intent different from a backlog item?

Both are future-tense, but a backlog item plans inward and decays privately, while an intent points outward and is shaped to be matched by other organizations’ agents. When an intent is answered and the work settles, the outcome becomes a sealed past-tense record.