Twitxy Saved

Patrick O'Meara

Verified account This account is verified. Learn more

@omearaop

Husband, Dad, Entrepreneur in decentralized economy infrastructure, DeFi, Blockchain, Crypto, attribution for AI, and tentmaker.
Joined September 2021
1.2K Following 851 Followers 26K Posts

Latest posts 5

Patrick O'Meara Verified account @omearaop
This is literally inveniam.io and dgml.io, as a tool to show original state and process of data improvement anchored on chain, most likely many chains so angents can reorganize the logs in a quantum resistant manner.. We believe the metachain or first chain will always be @NVNM_Chain as an agentically native chain for proof of process, origin, and state of data. This is how private markets go digital.
www.inveniam.io Inveniam - Smarter Markets Start Here Inveniam transforms unstructured, fragmented data into verifiable, AI-ready intelligence that institutions can use for valuation, reporting, risk analysis, tokenization, and AI-enabled market...
Mark Ajzenstadt Verified account @mardehaym 4d
Before agents do to operations what Claude Code did to engineering, operations needs what engineering already has: version control, tests, review, rollback and a named owner.

People are moving from doing ops, sales and support by hand to managing agents that do the work for them.

But the reason this worked in engineering often gets skipped.

Claude Code could move fast because the repo already had a history, tests, a reviewer and a way back. A bad change is cheap to undo. You see it, you revert it.

Most operations teams don't have that.

A prompt in somebody's chat history isn't a system of record. A payment to the wrong vendor doesn't just fail a test. It hits the bank.

Operations needs a harness around the agent: the context it works from, the tools it's allowed to use, the checks on its work and the points where a person takes over.

If I were putting an agent on AP, claims or the month-end close, I'd want the operations version of those five things first:

01 → Version control.
The rules the agent follows live in one place, with a history. You can see who changed the approval threshold from $5,000 to $15,000 and when, without digging through a Slack thread for the prompt.

02 → Tests and evals.
Real cases with agreed expected outcomes. Last month's close. Invoices that should be paid, held or flagged. Claims that should or shouldn't be denied. Did the agent follow the approval rules? Did it send the cases it couldn't resolve to a person? Rerun the set whenever the prompt, tools or model changes. If those checks fail, the change doesn't ship.

03 → Review.
Somebody who does the work signs off before a new version reaches production. The controller reviews a change to the close the way an engineer reviews a pull request.

04 → Rollback.
If this week's close agent starts booking entries to the wrong account, you can switch back to last week's version in minutes. “We'll fix it by Friday” isn't good enough.

05 → A named owner.
“The finance team uses it” doesn't tell you who's responsible. You need one person who can change it, pause it and answer for what it does to the close, to AP or to claims.

Claude Code didn't replace engineering practice. It ran on top of it.

Operations has to build that layer first.
View quoted post on X
4 replies 4 reposts 19 likes 1.8K views View on X
Patrick O'Meara Verified account @omearaop
I will take you away from among the nations,
gather you from all the foreign lands,
and bring you back to your own land.

I will sprinkle clean water upon you
to cleanse you from all your impurities,
and from all your idols I will cleanse you.

I will give you a new heart
and place a new spirit within you,
taking from your bodies your stony hearts
and giving you natural hearts.

I will put my spirit within you
and make you live by my statutes,
careful to observe my decrees.

You shall live in the land I gave your fathers;
you shall be my people,
and I will be your God.
- Ezekiel 36:24-28
4 replies 4 reposts 24 likes 1.6K views View on X
Patrick O'Meara Verified account @omearaop
Praised be God, the Father of our Lord Jesus Christ, the Father of mercies, and the God of all consolation! He comforts us in all our afflictions and thus enables us to comfort those who are in trouble, with the same consolation we have received from him. As we have shared much in the suffering of Christ, so through Christ do we share abundantly in his consolation.
- 2 Corinthians 1:3-5
7 replies 2 reposts 18 likes 720 views View on X
Patrick O'Meara Verified account @omearaop
I invite any suggested corrections, additions, deletions, or amendments to make this better. Please let me know how to make this a better document. @jp_mullin888 @jeanpaoli @EDMsnob @Profoneur @WallStreetApes @cz_binance @TalalAlKaissi @_RichardTeng @DavidSacks @brian_armstrong @chamath

This is the basis for real time proof of illiquid reserves and providing for the world's balance sheet a machine readable understanding of any data rich, seldom traded asset with no data leakage. This is the tip of the spear for AI auditability and tracability. With the ability to index, vector embed, and semantically chunk inside your own security envelope using @InveniamIO and then run large data set pattern recognition ticking and tying every single number over multiple quarters real time is how Real World Assets will trade digitally, and with out leaking your data. @InveniamIO is the control plane for data sovereignity in the Agentic Age.
NVNM Chain Verified account @NVNM_Chain Oct 28
Why NVNM Chain exists: In an age of AI agents, truth needs proof. x.com/i/article/2115…
View quoted post on X