How a collection of independent software projects evolved into a connected ecosystem exploring artificial intelligence, developer infrastructure, geospatial technology, digital publishing, and knowledge discovery.
Over the past several years, I’ve been building software across several different domains.
Some projects started as solutions to problems I encountered while working as a land surveyor. Others emerged from experiments with artificial intelligence, music production, developer tooling, and digital publishing.
At first glance, these projects might appear unrelated.
What does a professional experience-tracking application have in common with an AI execution framework?
How does a geographic music atlas relate to file management software?
And why would someone working in land surveying also build tools for monetization, blogging, and AI-assisted music?
The answer is that many of these projects emerged from a common interest:
Building software that gives people more control over their work, knowledge, creativity, and digital infrastructure.
This article introduces the ecosystem I’ve been developing, the problems each project addresses, and the architectural direction connecting them.
⸻
- OpenVerb — Building an Execution Layer for AI Actions
One of the most significant developments in artificial intelligence is the transition from systems that generate information to systems that execute actions.
Modern AI models can interpret instructions, generate code, and interact with external tools.
But connecting intelligence to execution introduces additional architectural challenges.
How does an agent discover available actions?
How are inputs validated?
How are permissions enforced?
How do we determine whether an operation succeeded?
And how do we establish a verifiable record of what happened?
These questions led me to develop OpenVerb.
OpenVerb is an open execution layer for AI actions built around structured verbs, schemas, policies, execution, and receipts.
The underlying concept is that an action should be treated as more than an arbitrary function call.
An action has a purpose, a contract, execution requirements, potential side effects, and a result.
OpenVerb explores how these elements can be organized into reusable infrastructure.
The OpenVerb architecture
The ecosystem includes packages addressing different parts of the execution lifecycle:
- Runtime
- Policy
- SDK
- CLI
- Core
- Standard library
- Developer integrations
It also includes specialized packages exploring applications in areas such as GIS, formatting, and geographic storytelling.
The broader objective is to establish infrastructure that can support AI-driven operations across different software environments.
Intelligence determines what should be done. Action infrastructure governs how it gets done.
This distinction becomes increasingly important as AI agents interact with business applications, enterprise systems, development environments, and real-world operations.
OpenVerb is my exploration of that architectural direction.
⸻
- PaywallOS — Monetization as Software Infrastructure
🌐 https://paywallos.openverb.org
Software monetization is often treated as something developers add after building their applications.
A payment provider is integrated.
A subscription table is created.
Some premium features are hidden behind a conditional statement.
But monetization becomes much more complicated as applications grow.
Different subscription tiers need different permissions.
Some users receive access to specific features.
Others receive usage allowances.
Certain actions might require payment, while others remain freely available.
And eventually, the application needs to understand not simply whether someone paid, but what that payment authorizes them to do.
This is the problem space behind PaywallOS.
The project explores a portable monetization layer organized around a structured execution model:
Tier
↓
Policy
↓
Verb
↓
Execution
↓
Receipt
The objective is to connect monetization decisions to application behavior.
Rather than treating payment infrastructure and application execution as entirely separate concerns, PaywallOS explores how they can operate together.
It also connects naturally to OpenVerb’s broader approach to governed actions.
A premium feature is ultimately an action that someone is authorized to perform under particular conditions.
The challenge is making that relationship explicit, reusable, and manageable.
⸻
- FolderCopilot — Making Existing File Systems More Useful
One of the recurring challenges I’ve encountered in professional environments is managing large collections of project files.
Engineering and surveying projects often contain years of accumulated information.
CAD drawings.
Survey computations.
GIS datasets.
PDF plans.
Project correspondence.
Field records.
Supporting documents.
The problem isn’t necessarily that these files are poorly organized.
Sometimes, the underlying directory structure is perfectly reasonable.
The difficulty is understanding what’s already there.
A project folder might contain hundreds of files distributed across multiple directories, and determining the current state of the project requires navigating the entire structure.
This was part of the motivation behind FolderCopilot.
FolderCopilot explores ways to make existing file systems easier to navigate, understand, and work with.
The underlying philosophy is straightforward:
You shouldn’t have to reorganize your entire digital workspace before software can help you understand it.
The project is particularly relevant to professionals working with large, structured collections of project information.
It also reflects a broader theme across my ecosystem: helping people make better use of information they’ve already created.
⸻
- Survey Manager Pro — Software Built Around Surveying Workflows
🌐 https://surveymanagerapp.com
My professional background is in geography, geospatial technology, and land surveying.
I’ve worked with boundary analysis, CAD drafting, GIS data, project preparation, and other surveying workflows.
One thing I’ve observed is that surveyors often depend on multiple applications to complete a single project.
GIS software handles one part of the workflow.
CAD software handles another.
Project documents exist in file directories.
Computations, field information, and other supporting materials may be distributed across different systems.
The challenge is not necessarily replacing those applications.
It’s improving how the workflow comes together.
Survey Manager Pro is my exploration of software designed around the practical needs of surveying professionals.
The project includes desktop, web, and QGIS-oriented development, connecting my professional experience with my software engineering interests.
I’m particularly interested in the relationship between project organization, geographic information, and the actual work surveyors perform.
The broader objective is to develop tools that understand professional workflows rather than requiring professionals to adapt everything they do to generic software.
⸻
- Elevatr — Turning Professional Experience Into a Documented Asset
Another project emerged directly from my experience pursuing professional land surveying licensure.
In many regulated professions, completing the work is only one part of professional development.
You also need to demonstrate what you’ve done.
That may involve documenting experience, projects, responsibilities, supervision, and hours.
And reconstructing several years of professional experience after the fact can be difficult.
I began thinking about a different approach.
What if professionals maintained a structured record of their experience as it happened?
Instead of trying to remember every project years later, they could build a professional history throughout their careers.
That thinking led to Elevatr.
Elevatr helps professionals document their work experience, track projects, record hours, and maintain a history of their professional development.
The platform includes web, desktop, and mobile development.
The Android application has also been published on Google Play.
Beyond professional licensure
Although land surveying provided the original context, the underlying problem exists across many professions.
Engineers, architects, technicians, and other professionals accumulate valuable experience throughout their careers.
But professional experience is often represented by little more than job titles and employment dates.
I believe there’s an opportunity to document it more meaningfully.
A résumé tells people where you worked. A professional experience record can help explain what you actually did.
Elevatr is my attempt to make that documentation more accessible and useful.
⸻
Expanding Beyond Traditional Productivity Software
Not every project in my ecosystem began with a conventional workplace problem.
Some emerged from exploring what artificial intelligence makes possible in education, creativity, and digital knowledge systems.
Two of those projects have become particularly significant.
⸻
- Topics Archive — AI-Assisted Music as a Knowledge Interface
🌐 https://topicsarchive.openverb.org
Music is traditionally organized around artists, albums, and genres.
But music can also be organized around knowledge.
History.
Geography.
Biographies.
Scientific discoveries.
Religious narratives.
Cultural events.
This is the thinking behind Topics Archive.
Topics Archive explores how AI-assisted music production can be used to create educational and thematic musical collections.
The project includes archives covering historical figures, biblical narratives, inventions, geography, and FIFA World Cup history.
The idea is not simply to generate songs about random subjects.
It’s to organize musical works into meaningful collections that people can explore.
A biography becomes a musical storytelling opportunity.
A historical event becomes part of a thematic archive.
A geographic location becomes a musical discovery experience.
From individual songs to structured collections
One of the most interesting aspects of this project is the relationship between content generation and software architecture.
Generating a song is one operation.
Organizing hundreds of songs into a coherent archive is another.
Building discovery mechanisms around those archives introduces an entirely different technical challenge.
And allowing people to create and curate their own collections creates additional opportunities.
Topics Archive is increasingly becoming an exploration of what happens when AI-assisted creative production is connected to structured digital publishing and curation.
⸻
- World Music Atlas — Geography as a Music Discovery Interface
The World Music Atlas emerged from the geographic music experiments within Topics Archive.
I wanted to explore a simple concept:
Could a geographic atlas become an interface for discovering music?
Instead of beginning with an artist or a genre, someone could begin with a place.
A country.
A territory.
Eventually, perhaps a city, river, region, or ocean.
The geographic location becomes the entry point into a musical experience.
This led to the creation of the World Music Atlas — 2026 Founding Edition.
The founding collection includes musical works inspired by 203 places around the world, including 195 countries and eight additional territories.
The technical architecture
The platform uses Next.js and Vercel, with the atlas accessing the underlying Topics Archive data through a read-only database connection.
I also published an initial TypeScript SDK:
npm install @openverb/music-atlas
The package provides a foundation for integrating atlas functionality into other software projects.
The broader vision includes developer integrations, geographic storytelling, additional musical editions, and new ways of exploring cultural and geographic information.
The World Music Atlas is not intended to replace traditional geographic research or serve as an authoritative collection of indigenous musical traditions.
It’s a born-digital creative atlas exploring the intersection of geography, AI-assisted music, and digital curation.
The music is the medium. Geography provides the structure. Discovery is the experience.
⸻
- OpenBlog — Giving Ideas Room to Develop
🌐 https://openblog.openverb.org
Another problem I’ve encountered is the limitation of short-form publishing.
Platforms such as LinkedIn and X are useful for discovering ideas and starting conversations.
But some ideas need more space.
A technical explanation might require architecture diagrams, implementation details, and examples.
A professional experience might require several thousand words.
A research observation might develop into an entire article.
When everything has to fit within a social media character limit, important context can disappear.
This is part of the motivation behind OpenBlog.
OpenBlog explores AI-assisted digital publishing, including the ability to develop articles from prompts and expand shorter social media posts into more complete written content.
The concept is particularly relevant to my broader ecosystem.
A technical observation about OpenVerb could begin as a LinkedIn post and eventually become a detailed development article.
A project announcement could become a longer explanation of the problem, architecture, and implementation.
A short reflection could develop into a more substantial piece of writing.
Social media can introduce an idea. Long-form publishing gives that idea room to develop.
⸻
The Bigger Picture: Building Systems That Connect
Looking at these projects together, I see several recurring architectural themes.
They may address different audiences, but many of the underlying problems are related.
Structured information
Elevatr structures professional experience.
Topics Archive structures educational music collections.
The World Music Atlas organizes music geographically.
FolderCopilot explores ways to understand existing file structures.
Execution and governance
OpenVerb explores structured AI actions.
PaywallOS explores policies governing access to monetized functionality.
Domain-specific workflows
Survey Manager Pro focuses on surveying and geospatial professionals.
Elevatr addresses professional experience documentation.
The World Music Atlas explores geographic discovery.
Publishing and distribution
OpenBlog provides a publishing environment.
Topics Archive organizes and publishes musical collections.
The World Music Atlas creates another interface for discovering those collections.
These projects are not all components of one monolithic application.
Each addresses a particular problem and can have its own identity, users, and development direction.
But there are opportunities for shared infrastructure, integrations, and architectural reuse.
That’s what makes the ecosystem interesting to me.
⸻
Why I’m Building Across Multiple Domains
There’s a common assumption that developers should focus exclusively on one industry or problem.
Specialization has obvious advantages.
But working across different domains can also reveal recurring patterns that are less obvious when viewed from within a single industry.
My experience in land surveying informs the way I think about structured data, professional workflows, documentation, and geographic information.
My work with AI infrastructure influences how I approach execution, automation, policies, and developer tooling.
My experiments with music and digital publishing have introduced different challenges involving content organization, discovery, curation, and distribution.
These experiences continuously inform one another.
Sometimes an architectural concept developed for one project becomes relevant to another.
Sometimes a workflow problem encountered professionally becomes the foundation of an entirely new application.
And sometimes an experimental project reveals an opportunity that wasn’t part of the original plan.
The connection isn’t necessarily the industry. It’s the way I approach building software.
⸻
What I’ve Learned From Building an Ecosystem
Developing multiple projects has taught me several things.
First, the problem behind a project matters more than the number of features it contains.
Second, software becomes more interesting when it reflects a genuine understanding of the environment in which people will use it.
Third, reusable infrastructure creates opportunities that isolated implementations may not.
And finally, not every project needs to begin with a fully developed business model or a prediction about its eventual market size.
Some projects begin as experiments.
Others begin as tools developed to solve an immediate problem.
Over time, the architecture, audience, and opportunities become clearer.
Of course, building multiple projects also introduces challenges.
Maintaining software requires time.
Documentation matters.
Testing matters.
User experience matters.
And deciding what to prioritize becomes increasingly important as the ecosystem grows.
But I see these challenges as part of the process of developing a sustainable body of work.
⸻
What’s Next?
My focus is on continuing to develop these projects while improving the infrastructure, usability, documentation, and integrations surrounding them.
For OpenVerb, that means continuing to explore the architecture of AI action execution.
For Elevatr and Survey Manager Pro, it means developing tools grounded in real professional workflows.
For FolderCopilot, it means improving how people interact with existing digital information.
For Topics Archive and the World Music Atlas, it means expanding the possibilities of AI-assisted music, digital curation, and knowledge discovery.
For PaywallOS and OpenBlog, it means exploring better systems for monetization and publishing.
I also want to continue documenting the development process.
Not just announcements about new features, but the architectural decisions, challenges, experiments, and lessons behind the software.
That’s one reason I’m sharing this work on DEV.
I’m interested in connecting with other developers who are building infrastructure, experimenting with AI, working in geospatial technology, or exploring unconventional intersections between software and other disciplines.
⸻
Final Thoughts
When I look at these projects together, I don’t simply see a collection of applications.
I see a growing body of work shaped by different professional experiences, technical interests, and experiments.
Some projects address problems I’ve encountered directly.
Others explore possibilities that emerging technologies have made accessible.
And others are attempts to build infrastructure that can support entirely new categories of applications.
The objective isn’t to build software for the sake of having more projects.
It’s to create useful systems, learn from the process, and explore how different technologies can work together.
Software development gives us the opportunity to turn observations into tools, tools into platforms, and platforms into infrastructure that other people can build upon.
That’s the opportunity I’m exploring through this ecosystem.
And I’m still building.
⸻
Explore the Ecosystem
Project Focus Website
OpenVerb AI action infrastructure https://openverb.org
PaywallOS Monetization infrastructure https://paywallos.openverb.org
FolderCopilot File management and discovery https://foldercopilot.com
Survey Manager Pro Surveying and geospatial workflows https://surveymanagerapp.com
Elevatr Professional experience documentation https://elevatr.dev
Topics Archive AI-assisted educational music https://topicsarchive.openverb.org
World Music Atlas Geographic music discovery https://openmusicatlas.org
OpenBlog AI-assisted digital publishing https://openblog.openverb.org
⸻
About the Author
I’m Roman Hancel, a geospatial technology professional, software developer, and founder building projects across AI infrastructure, land surveying, professional development, music, and digital publishing.
My work explores how software can connect different disciplines, make professional knowledge more accessible, and create new opportunities for independent developers and creators.
Top comments (0)