Uncovering Capability Architecture

Borrowing and extending from a few chats w/LLMs…

…am liking a direction my recent work has been going: interpretive anchors around concepts like: invitation-based systems, contextual computing, trust surfaces, and human-centered operations

It might sound a bit “deep,” or “complicated” here. But truth is, I’ve pushed away from stages like LinkedIn to orchestrate a more durable way forward. That’s meant building a new (to me) identity framework. That’s meant a credential branch for LLMs/agents to work with that’s prescribe to how id like to be engaged, not how to extract from my signals something else.

I’ve been scheming/designing for an identity-aware context that doesn’t quite exist yet (but Google kind of points to it coming). I’ve been designing a canvas for my incoming Brilliant Labs Halo glasses and current Frame glasses which is even differentiated from what Meta recently published for their MRB Display glasses platform…

…I am not saying that some of the directions noted in those and other pieces don’t matter. I see and am approaching the evolution in software, services, and product in a manner that fits enabling humane capabilities more than it does system engineering.

And honestly, being a capability architect resonates way more with what I do, what I want to do, and what I leave behind than much else. For those who are geared in this direction, it’s been quite a journey to find this kind of clarity.

Next, finding the folks who need their capabilities unlocked when systems, people, and technology are no longer cohering… or being more discoverable to those folks, will be the better test of this direction and focus.