TetraMesa

Archives for July 2026

The Tokenization Taxonomy: A Practical Map of Assets, Rights, Services, and Credentials

By

A multidimensional guide to what is being tokenized, what rights holders receive, which record controls, where the supporting information comes from, and what changes with tokenization.

In the individual series of work about Real World Assets (RWA) that led to this, one part developed a more detailed taxonomy of the kinds of oracle data an asset may require, while others examined the people, incentives, controls, and failure modes surrounding those records. Those remain companion frameworks rather than branches of the hierarchy presented in this final wrap-up.

This will be an extensive long-form article bringing together a central classification framework. The underlying asset, service, right, or credential forms the primary taxonomy. The token-holder’s rights, the authoritative record, the provenance of supporting information, and the changes introduced by tokenization operate as separate dimensions across that hierarchy.

Want to skip this entire article? Then here it is in a sentence: “Buying a token does not mean you own the underlying asset; it means you own whatever contractual rights the issuer’s legal jurisdiction enforces.”

That’s really it. If you want all the details, or at least as much as I’ve been able to get together, then continue…

I’ve used GPTs to help generate the graphics, and they’ve come out fairly well, but may require a click to enlarge them in some cases. (Or right-click and enlarge in a new window.) If you want, you can use them to just skim and pick up the basic ideas here without having to read through everything.

[Read more…]

RWA, Meet RWL, Part 6: The Token Is Not the Thing

By

Part 6 of 6 in “Real World Assets (RWA), Meet Real World Lies (RWL): Knowing What You Own in the Tokenized World,” a series about what tokenized assets represent, how information about them reaches the blockchain, and why none of this eliminates the need for trust.

The earlier parts of this series examined the underlying assets, the data that describes them, the people and institutions involved, and the failure modes that persist even when records are on-chain. This final part brings those threads together and offers a practical test.

The token is only one layer in a larger arrangement. The token is not the thing.

[Read more…]

RWA, Meet RWL, Part 5: When the Asset Is Already Digital

By

Part 5 of 6 in “Real World Assets (RWA), Meet Real World Lies (RWL): Knowing What You Own in the Tokenized World,” a series about what tokenized assets represent, how information about them reaches the blockchain, and why none of this eliminates the need for trust.

Parts 2–4 examined the data, the people, and the failure modes surrounding tokenized assets. We now return to the taxonomy itself. The original split between intangible legal claims and tangible physical assets works for most conventional RWAs. It does not cover the growing set of things that are digital from the start; data, compute, software, network rights, game objects, and credentials. Some of these are assets, some are services or licenses; some may not be assets at all. We need a third branch.

[Read more…]

RWA, Meet RWL, Part 4: No Blockchain Solution Fixes Real-World Lies

By

Part 4 of 6 in “Real World Assets (RWA), Meet Real World Lies (RWL): Knowing What You Own in the Tokenized World,” a series about what tokenized assets represent, how information about them reaches the blockchain, and why none of this eliminates the need for trust.

The first three parts looked at the assets, the data, and the people involved.

Part 1 asked what kind of thing was being tokenized and what claim the token actually gave its holder. Part 2 looked at the information required to describe and evaluate that thing. Part 3 examined the people and institutions responsible for reporting, checking, and acting on the information.

This part looks at what happens when those trust structures fail.

[Read more…]

RWA, Meet RWL, Part 3: Permissionless Does Not Mean Trust-Free

By

Part 3 of 6 in “Real World Assets (RWA), Meet Real World Lies (RWL): Knowing What You Own in the Tokenized World,” a series about what tokenized assets represent, how information about them reaches the blockchain, and why none of this eliminates the need for trust.

Parts 1 and 2 examined the underlying assets and the data used to describe them. Now we turn to the people and institutions responsible for that information.

Before getting into that, it’s worth clearing up two terms that tend to get used somewhat loosely.

[Read more…]

RWA, Meet RWL, Part 2: The Oracle Problem

By

Part 2 of 6 in “Real World Assets (RWA), Meet Real World Lies (RWL): Knowing What You Own in the Tokenized World,” a series about what tokenized assets represent, how information about them reaches the blockchain, and why none of this eliminates the need for trust.

Part 1 asked what kind of thing is being tokenized. Once we know that, we still need information about it: how much gold is in the vault, who owns the building, whether the aircraft was inspected, whether the borrower is paying. That is where the oracle problem begins.

[Read more…]

RWA, Meet RWL, Part 1: “Real-World Asset” Is Not an Asset Class

By

Part 1 of 6 in “Real World Assets (RWA), Meet Real World Lies (RWL): Knowing What You Own in the Tokenized World,” a series about what tokenized assets represent, how information about them reaches the blockchain, and why none of this eliminates the need for trust.

RWL is what I’m calling “Real-World Lies.” That might seem a little strong. Maybe it is. But I don’t necessarily mean “lies” only in the malicious sense. There are also mistakes, omissions, outdated records, stretched definitions, poorly understood rights, and information distorted by incentives. Right now, there seem to be plenty of ways for something that isn’t quite true to enter a system, become tacitly accepted, and continue moving through it as though it were fact. This series looks at how that happens, at least somewhat. But more importantly, how to classify and evaluate the many parts that finally seem to be coming together to bring more tokenized assets to market.

Much of the following is not new. If you’re already deeply familiar with tokenized assets, you may want to skip this entire series. However, if you’re still new to Real World Asset and trying to get a sense of the whole big picture, perhaps this series will help. It was created as part of a project to help some new to the area to build a wide scope taxonomy of the space and the issues across types of things involved. This isn’t about mechanisms of tokenization. We’ll be more focused on compare and contrast with real world assets and building an evaluation framework that helps us navigate these spaces.

[Read more…]

AI Build Copilot, Part 6: MORE Bonus Bits & Pieces

By

It doesn’t matter what you’re doing. Product Management work, Creative work. Requirements. Code. We’re all over these tools now and across disciplines, we face some of the same challenges. Here’s yet another set of practical snippets for dealing with AI-assisted coding and building. The tools can move fast and sometimes faster than we can track. This installment collects a few more practical habits for staying in control. These are the small, deliberate practices that keep “trust but verify” from turning into “hope it worked.”

[Read more…]

AI Build Copilot, Part 5: Bonus Bits & Pieces

By

Intro

I thought Part 4: Preparing for Production was going to wrap up the series. But wait, there’s more! Not every useful lesson about building with AI tools fits neatly into the larger themes of the past articles in this series. So this final section is a collection of extra bits and pieces that don’t quite belong anywhere else, but may still save you a lot of trouble. Yes, I could have just called it “Misc.” I suppose. But in any case, there’s just some random bits that didn’t fit cleanly into earlier docs and fell out of the edits.

Here they are in one random walk place.

[Read more…]

AI Build Copilot, Part 4: Preparing for Production

By

Part 3 was about building durably, so what happens after that? A successful prototype creates a new problem if you actually put it into some form of production. Not too long ago, if we built what we called prototypes, maybe they went to user testing, or we ‘sort of’ put them out there. But now? A lot of so-called tests really aren’t. That is, they’re really more actual rollouts. Just maybe not necessarily with the same rigor we used to give product launches. The line between that which was intended as prototype testing and so-called Minimum Viable Product (MVP) seems like it might get blurry.

The next challenge with launching a kind of prototype, but that which is maybe real product is someone may decide to use it. So… Is it really a prototype? Meaning… is this just some brochureware for testing or is there actual sign-up functionality, any kind of real billing, private information collection, and so on.

This is when the low-stakes experiment begins accumulating customers, private information, billing relationships, operational dependencies, and consequences. You have to make your own call on this kind of thing. I have to tell you, personally I’ve never loved the “false front door” thing for testing. I get that it can be useful, but sometimes it’s on the edge of unethical in how it seems to trick people. If your prototype is really a test and that’s understood, great. If the truth is it’s not much of a test, but a rollout? Then there’s probably some more risk elements and due diligence that should be covered.

Prototypes have a way of becoming products. Temporary credentials become permanent. Test data becomes customer data. A one-time API connection becomes a critical service. The final part of an AI-assisted build is not clicking Deploy.

It’s deciding whether the thing can be operated safely. One thing that I’ve done along the way when building is created something I’ve called “Launch Blockers.” This is different than a UI backlog or minor changes you find along the way. It’s things like purging schemas, or making sure live production feature flags are set properly. It means a real security review. Things like that.

[Read more…]

Location

We're located in Stamford, CT, "The City that Works." Most of our in person engagement Clients are located in the metro NYC area in either New York City, Westchester or Fairfield Counties, as well as Los Angeles and San Francisco. We do off site work for a variety of Clients as well.

Have a Project?

If you have a project you would like to discuss, just get in touch via our Contact Form.

Connect

As a small consultancy, we spend more time with our Clients' social media than our own. If you would like to keep up with us the rare times we have something important enough to say via social media, feel free to follow our accounts.