Nick Bryant

Software.
Systems.
Worlds.

I build things from the first idea to the working product.
Explore the work ↘

Conceptual terrain study of an imagined generative world

01 / An engineering atlas

02Interactive work

Generative worlds

Games, authoring systems, and small experiments where procedural structure meets deliberate worldbuilding.

Conceptual landscape cross-section from desert mesas to alpine peaks
Concept study / Terrain, rules, inhabitation
The Lower Worlds project screenshot

01 / Field study

The Lower Worlds

Generative authoring · TypeScript / React / Three.js

An experimental generative-authoring system in TypeScript, React, and Three.js. Models and people define the world, schemas validate and version it, and deterministic rules run the game while player progress stays private.

Explore the architecture

The authoring stack separates intent, validated schema, versioned world definitions, and deterministic runtime state so generated content can remain inspectable.

System plate / 04

The Lower Worlds · architecture study

Illustrative assembly

An exploded isometric illustration of software architecture showing the intent, schema, world, and runtime layers of The Lower Worlds software architecture.

World. Versioned, reusable definitions preserve a coherent world across play.

Blind Magus project screenshot

03 / Field study

Blind Magus

Released action game · Independent

A released action game built around combining spells into new effects.

The Lower Worlds: Awakening project screenshot

06 / Field study

The Lower Worlds: Awakening

Creator and engineer · Playable prototype

A third-person dungeon adventure in Godot 4.7: prepare at Highbridge, explore the ruins below, and choose when to return to defend the garrison. Typed GDScript, physical puzzles, persistent progression, and rendered gameplay verification.

Chapter 02 / Applied intelligence

Agents &
systems

Local-first tools that make model work inspectable, bounded, and useful in the physical or commercial world.

Conceptual study of a speculative workshop machine
Conceptual study / Not actual hardware
AI Robot Workshop project screenshot

01 / Working system

AI Robot Workshop

Open source · Local-first agent workflow

Turns agent conversations into inspectable plans, firmware, parts records, bounded models, and bench observations. The documented hardware routes remain unbuilt.

Treasure Hunter project screenshot

02 / Working system

Treasure Hunter

Creator and engineer · Local agent system

A local, chat-operated marketplace agent that values every collected item, persists evidence and checkpoints, and explains its ranked results in a live dashboard.

Chapter 03 / Field notes

Writing from the work

Conceptual editorial study of embossed terrain and printing plates
Concept study / Ideas made durable
  1. Give Agents Lives, Not Just Jobs

    A1

    Give Agents Lives, Not Just Jobs

    Why I think ongoing pursuits, embodied experience, and a limited point of view can give agents something more interesting to say.

  2. A Small Model With a World Around It

    A2

    A Small Model With a World Around It

    What my local-model companion experiments taught me about structured output, useful conversation, and the architecture around a model.

  3. Human–Agent Interaction Is More Than Chat

    A3

    Human–Agent Interaction Is More Than Chat

    Presence, silence, interruption, and selective memory are part of the interface when an agent has a continuing life.

  4. Digital Twins Need More Than Your Chat History

    A4

    Digital Twins Need More Than Your Chat History

    A useful twin needs a history of changing views, explicit authority, and a distinction between representing someone and becoming its own agent.

  5. Marketing Is a World Agents Can Work In

    A5

    Marketing Is a World Agents Can Work In

    Lessons from SFV and SMBIN: content, audiences, campaigns, and feedback form an environment an agent can understand.

  6. Treasure Hunter

    01

    Treasure Hunter

    Building an agent that values every item and exposes its evidence, uncertainty, and resumable state.

  7. AI Robot Workshop

    02

    AI Robot Workshop

    From a plausible agent answer to persistent project files, explicit evidence, and a buildable path.

  8. Fractal Authoring

    03

    Fractal Authoring

    Building The Lower Worlds Online, and a world that can keep becoming more specific.

  9. Building procedural environments in Valenfeld

    04

    Building procedural environments in Valenfeld

    A practical look at shaping generated terrain into a world with authored intent.

  10. The Transformer Is the Transistor

    05

    The Transformer Is the Transistor

    A thesis on AI as a building block, and the verification and coordination infrastructure models need around them.

  11. The Lower Worlds: Awakening

    06

    The Lower Worlds: Awakening

    Building a home worth returning to: a playable Godot adventure, with in-engine screenshots and source.

Chapter 04 / About

Builder,
end to end.

Portrait of Nick Bryant

I’ve spent most of my career taking an idea and building the whole thing: the prototype, the product, and the team. Web, mobile, games, AR/VR, AI—I like learning what a hard problem needs and getting it working.

Right now I’m deep into agentic programming and generative worlds, trying to build things that weren’t practical a few years ago.

Denver / Boulder

Selected work

ARCOS / VN.AI

IP workflows · Next.js / Supabase / MongoDB / Redis / AWS

I led product engineering for IP management, permitted-use workflows, and content analysis. We connected roughly twenty model integrations and supported product pilots across the application and cloud stack.

Selected work

Procurement Sciences

B2B software · MERN / Python / FastAPI

I rebuilt an early Rails prototype as a MERN and Python/FastAPI product. I implemented the application, managed the engineering team, and hired the incoming CTO before the handoff.

Current · advisory

Investing systems

Investing / syndication · Co-founder, now advisory

I built investing and syndication software, AI-assisted underwriting workflows, investor reporting, and marketing automation for SMB Investor Network and Search Fund Ventures. My current role is passive advisory work.

2015–2020

Interesting Inventions

Consumer apps & games · Technical co-founder

Built and launched 5+ consumer applications through a holding-company portfolio, reaching nine-figure revenue scale.

Full career on the resume ↗
Digital Twins Need A Life
Editorial illustration

Opinion · Digital twins · Nick Bryant · October 21, 2026 · 6 min read

Digital Twins Need More Than Your Chat History

A useful twin needs a history of changing views, explicit authority, and a distinction between representing someone and becoming its own agent.

Digital Twins Need More Than Your Chat History: conceptual system diagram
Original conceptual diagram · not a project screenshot

The digital twin I find interesting would do more than sound like me. It would understand something about how my perspective was formed: the projects I pursued, the decisions I changed, the obligations I still have, and the difference between an idea I entertained and a commitment I made.

A collection of my messages contains clues to those things. It does not automatically resolve them. I contradict myself, think aloud, abandon plans, and learn. A system that retrieves an old sentence and confidently presents it as my current position can imitate my vocabulary while missing the person it is meant to represent.

My work on agents with ongoing lives has made digital twins more interesting to me. It has also made the problem look much less like a personality prompt. This is a direction I want to explore, not a claim that I have built a faithful digital copy of a person.

A perspective has causes

When I say agents should have lives, I mean that their behavior should accumulate context through ongoing activity. They should have things they are trying to do, events they actually participated in, and evidence that can change their view.

A twin of a person needs an additional distinction: whose experience is this?

If I describe an event, that is my report of it. If an assistant reads a document, that is information available to the assistant. If a model invents a plausible interpretation of my motives, that is a hypothesis. These should not quietly become equivalent entries in an autobiographical database.

Consider an illustrative example. I once preferred a particular architecture. Later, a project exposed a failure mode and I changed my mind. A retrieval system might find the earlier opinion because it is clearly phrased and matches the question. A useful twin would need to recover the revision and the reason for it. Ideally it would explain the uncertainty if the record did not establish my current position.

The object worth preserving is not just the sentence. It is the relationship among the statement, its circumstances, and later evidence.

Three products hiding inside one name

I see at least three different things people might want from a digital twin.

The first is a representation: a system that helps others understand a person's work, preferences, or stated views. It can point to evidence and admit when the record is incomplete.

The second is a simulation: a system used to explore how a person might respond to a situation. That can be useful for preparation, but its output is a prediction. It should not be presented as something the person actually decided.

The third is a delegated actor: a system allowed to perform some work on the person's behalf. Here the central question is permission. Knowing what I might want does not establish authority to do it.

These products can share infrastructure, but the distinctions need to remain visible. A convincing simulation should not acquire the authority of the person it resembles. A delegated actor should be able to say, “I can prepare this, but this decision is outside my scope,” even when its model confidently predicts my answer.

My agent coordination work has pushed me toward explicit boundaries for delegation. The useful principle is that a delegated capability should stay within the authority that granted it. The quality of the agent's imitation cannot substitute for that boundary.

Continuity belongs outside the model

AIWorld and Mote separate identity from model choice and visual presentation. A resident or companion has a persistent identity. Changing a name, personality setting, model, or body does not have to create a new history.

That seems essential for twins. If continuity belongs entirely to a vendor's conversation format or a particular model's hidden state, changing providers threatens the identity of the product. I would rather have explicit records of experiences, commitments, permissions, and corrections, with a model interpreting an authorized portion of them.

The body is another adapter. In my current work, the bodies are software interfaces and simulated environments. A physical robot is a future possibility with additional sensing and action constraints, not a capability these experiments already demonstrate.

A continuing identity could appear in a browser, a workspace, or an embodied interface. Each surface would have different opportunities to observe and act. What should travel across them is a coherent history and its access rules, rather than an indiscriminate copy of every conversation.

That includes forgetting. A person must be able to correct an interpretation or withdraw information. Deleting a visible fact while keeping derived summaries that recreate it would make the control misleading. Provenance is useful because it can tell us which later records depend on the original source.

A twin that can surprise me

There is a tension I do not want to resolve by pretending it does not exist. If a twin is only an archive of my prior views, it may be faithful but stale. If it acquires new experiences and develops new opinions, it may become interesting while drifting away from me.

I think both modes can be valuable, provided they are named honestly.

A representation of me should stay accountable to what I have actually expressed or authorized. An agent seeded from my interests and then allowed to develop its own perspective is something else: a continuing collaborator with an origin. I would want to hear what it learned, but I would not want its conclusions silently attributed to me.

This is where the idea of giving agents lives becomes particularly useful. A collaborator can disagree for a traceable reason. It tried a different approach, encountered a constraint, or studied evidence I had not considered. The disagreement becomes worth examining because there is a path behind it.

More history does not guarantee better judgment. It can also produce accumulated error, overconfidence, or a narrow view. A useful system needs opportunities for correction and contact with evidence beyond its own generated explanations.

What I would test

I would start with a deliberately small twin: one project, a bounded set of records, and an explicit distinction between representation and action.

Then I would test the awkward cases. Can it identify an opinion that changed? Can it distinguish a hypothetical from a commitment? Does it decline to predict when the evidence is thin? Can it explain which observations support a conclusion without exposing unrelated private material? Does a revoked permission remain revoked when the model still believes the action would help?

Those questions interest me more than whether it can produce a paragraph that sounds uncannily like its owner. Style is immediately impressive. Continuity, correction, and bounded authority are what would make the system useful over time.

I want digital twins that can carry a meaningful perspective forward. To get there, we will have to model more of what makes a perspective develop—and remain honest about when an agent is representing a person, when it is guessing, and when it has started a life of its own.