Founder Story, by Brittnay Folkes

2015 to 2026

Timeline

2015 to 2020

I work in multifamily interior design. I see how much money goes into building housing. I cannot work out why living in it keeps costing more.

2016

My mom dies. I am 20.

2018

I start a podcast named Blank Univercity. I design its first logo myself. Then I pay an artist to redraw it.

2021

I move from Dallas to Denver.

2023

I present a proposal to the Denver Housing Authority. It has twelve areas, each named after a constellation.

2022 to 2025

I work in community management, at a nonprofit for homeless youth, and at a community radio station. I attend culinary school. Each job changes how I define the folders.

January 2026

I expand the first model of twelve folders into four departments with twelve folders each.

October 2026

I develop the Resident Portal, the Employee Handbook, and the Agent Operating Standard. I begin defining GENESIS and the way the Assistant should learn about residents.

Now

I am 30. I am the first resident of Universe City. I run all forty eight folders on my own life first, in public. I publish the numbers as I go.

Chapter 01 · 2016

What was lost

My mom just knew me.

She was always someone I could call. She checked in on me. She reminded me that I was loved, but she also reminded me who I was. She knew my strengths and my weaknesses. She was the best hugger in the world, and she had the best laugh.

She had her own struggles with alcohol and mental health, but I still knew what it felt like to have a mother who knew me that deeply.

When she died, it left this huge hole in my chest.

It also created a contrast that is still hard for me to explain. I knew I had to adapt quickly, but there was nothing quick about it. It has taken me almost 10 years, and I think some parts of it may take another 10.

Over time, I started thinking about all the things people had complimented me on. I was well mannered. I was organized. I thought in systems.

A lot of that did not come from me sitting down and deciding to become those things. I learned it passively from her.

That became part of the reason for Universe City.

I want people to have help building that kind of structure into their own lives, even if they did not grow up with a mom like mine.

Chapter 02

What grief did to my life

After my mom died, I started pushing people away.

I ended a long term relationship. I kept friends at arm’s length. I developed an unhealthy relationship with work.

And to be frank, I was angry at God.

I remember thinking, I guess anything goes now.

The first few years after losing her were extremely distracting. I worked a lot. I made bad decisions. I stayed busy.

But I was also trying to make sense of it.

I do not think I was searching for anything.

I think I was trying to heal using the same tools I had always used to soothe myself.

Creating. Planning. Performing. Building ideas. Working.

Those things were already part of me long before grief.

As a kid I had a dog walking business. If we went to the pool, I wanted to sell snacks and Slurpees. If my siblings and I wanted something special, my mom would make us create PowerPoint presentations. We had to think it through, make a plan, and present it.

I loved that.

When I was around 10, I would role play owning a homeless shelter instead of playing with Barbies. In 4th grade, I wanted to open a daycare in our garage. A year later, I was calling wood shops from the Yellow Pages asking if they had spare wood because I was convinced I could build my own car.

I was always asking for a camera or a computer for Christmas or my birthday. We were filming skits when we were 7. I kept doing that through high school, and I still do it now.

Singing was the same way. I wanted to be a huge performer, but even then a big part of the dream was making enough money to retire my mom. I did not even really understand retirement yet.

At career day, I would flip to the back of the books and look for the highest salaries. In 6th grade I decided I was going to be an anesthesiologist because it made the most money in the book.

I loved animals too. I was always bringing something home or calling a bird sanctuary if I found an injured bird.

I had a great childhood.

Creating, planning, caring, building, performing, researching, and trying to own something were already part of me.

After my mom died, I naturally reached for those same things.

Eventually I realized they were not enough.

Chapter 03 · 2018

Blank Univercity

In 2018, I started the Blank Univercity podcast.

Creativity had always been one of the ways I understood myself, so I used the podcast to say out loud what I did not know how to organize anywhere else.

I talked about love, sex, death, grief, feeling lost, feeling confused.

It helped.

But it was still an outlet.

I could express what I was feeling creatively, and I was still struggling to build a life around what I was learning about myself.

Around that same time, I became obsessed with community development corporations and housing.

I was researching ways people could own homes and lower their cost of living. I kept coming back to modular housing and manufactured homes because I thought the stigma around them was getting in the way of a real ownership option.

I talked about it so much that an operations executive I worked with gave me 4 percent equity in a land acquisition deal based on the research I had been doing.

That should probably tell you how much I was talking about housing.

I had a lot of ideas.

Housing. Songwriting. Podcasts. Creative projects. Work. Usually more than one job at a time.

I was interested in everything.

I was also exhausted.

Chapter 04

Structure, sports, and why I kept rebuilding

I did not think of my life as a system.

I just knew that when things felt off, I needed structure.

I usually started with a calendar.

Then sleep. Wake up on time. Go to the gym. Eat better. Read. Get back into some kind of routine.

A lot of that came from sports.

I grew up in a pretty athletic family, and sports taught me that if you want to win, you have to train like a winner.

You do not just show up on game day and hope it works out.

At first, my systems were printouts I hung on the wall.

I would have one in the kitchen for dishes and groceries. Another one for reading, practicing singing, cleaning my bathroom, or whatever I was trying to stay consistent with.

I loved making them.

The hardest part was never getting my life together. It was keeping it that way.

I had gotten so good at pulling myself out of chaos that I think I started believing I could always do it again. And maybe that made it easier to let things fall apart.

But there were times when I really did have it together.

I remember realizing one day that I was 8 weeks into a routine I had created for myself. 8 weeks of doing what I said I was going to do. I wasn't binge eating. My home wasn't getting out of control. I was keeping up with myself and the things that mattered to me.

And I remember how good that felt.

Because it proved something I had questioned for years. I was capable of consistency. I could build structure into my life, and I could actually live within it.

But somehow, knowing I could do it wasn't enough to make it last.

Eventually, the routines would slip. The things I had worked so hard to put in place would start coming undone.

And before I knew it, I was rebuilding the same life I had already figured out how to build.

Chapter 05 · 2023 to 2026

From 12 buckets to the current structure

Parts of me felt like a lot of adults were already gone.

They were buried in work, distracted, exhausted, did not care, or I felt like the matrix had already swallowed them whole.

So naturally I started thinking about the kids.

How do we make this something our young ones can learn early so they do not need it as supplemental education once they get to the point of having to manage it all?

That thinking showed up in earlier versions of Universe City.

At first, I tried to fit everything into 12 little buckets.

The 12 areas were tied to the stars and the zodiac, and the work was much more focused on family management, education, community development, and life skills.

I kept stretching those 12 areas to cover more and more of life.

Activism turned into several different kinds of work. Family started carrying responsibilities that clearly belonged in separate places.

The more I built, the more obvious it became that 12 was not enough.

By 2026, I was burnt out from community radio and from constantly getting distracted by other organizations’ missions while putting Universe City off to the side.

I turned 30 in December 2025, and something in me was like, hey, stop neglecting this.

I was financially comfortable. I lived by myself in a nice apartment in North Boulder. I was working ungodly hours. I had jobs that sounded cool. I was making decent money.

I still felt unfulfilled.

I kept thinking the next thing would fill the hole and it did not.

I had spent years repeating the same habit of work horsing and staying on go. At one point I had 2 jobs and was in culinary school at the same time.

So at the beginning of 2026, I decided to take a real risk.

I quit my job with no backup.

I wanted to believe the universe had my back. I also wanted to put myself in the exact position this operating system was supposed to help someone manage.

No job. Rent due. Moving out. No clear idea what came next.

And I locked in.

I downsized my wardrobe. I bought refillable items for what I used every day. I limited my resources down to what I actually needed. I packed my apartment into storage.

Somewhere in the middle of all that, the 4 departments started to appear.

Housing was the first one I knew had to stand on its own.

It took forever to figure out what belonged inside it. At one point the folders were literally rooms. Living room. Kitchen. Bedroom.

That did not feel right.

Career came next.

After quitting my job, I started thinking about everything that goes into getting a job, keeping a job, and actually excelling at work.

I also had a lot to pull from. I had worked more than 30 jobs by the time I was 30. I felt like I had done every job under the sun.

Life Management was already there.

Standards was the first folder in Life Management, and it still is.

Standards was what made me admit something I had been avoiding.

I do not actually want to work here.

I do not want to keep doing this.

Then came Personal Assessment.

Once my own life got rocked, I did what I always do.

I started asking: what does my schedule look like? What time am I going to sleep? What time am I waking up? Where are my documents? What am I eating? What am I doing to stay healthy?

That later became Agency Assessment because it became the place agents and residents begin during enrollment. It is the assessment of where a resident stands in those 12 areas before getting into the others.

The exact folders will keep developing.

The structure did not arrive fully formed.

It came from trying to make real life fit into the model, realizing where it did not fit, and changing the model.

Chapter 06

Why everyday people need agents

Once I had the 4 departments, I started thinking about what I was actually asking people to do.

I had spent years making calendars, cleaning schedules, financial records, and systems for every part of my life. I knew how much work it took to build them. I also knew how easy it was to stop maintaining them when life got busy.

I could put 48 folders on a website and give people somewhere to organize their information. But if I handed somebody 48 more things to maintain, how much had I really helped?

That bothered me. The people who need support are often the people with the least time to do another assignment.

My little brother is 21, and he plays D1 college football. He has an agent. So when I started thinking about what I was building, I already had an example of representation in my own family.

Professional athletes and entertainers have people who help them manage opportunities, negotiate, and make decisions. People with enough money can hire managers, assistants, accountants, and lawyers.

Everyday people have jobs, bills, homes, appointments, relationships, and goals. We have information spread across emails, applications, and pieces of paper. Somehow we're expected to remember everything and make good decisions about all of it ourselves.

I kept wondering why somebody had to become successful before they could have an agent. Why couldn't representation help them become successful?

That changed the project.

The folders stopped being categories that residents would maintain by themselves. They became the structure an agency would use to understand and manage its responsibilities.

I wanted a human Agent who could represent a resident, and software that could help with the work between those conversations.

I didn't want to build another application that made people feel behind. I wanted to build a service that could carry some of the administrative work for them.

I still had to figure out how to make it affordable. And I still had to figure out how to build the thing.

Those turned out to be 2 very different problems.

Chapter 07

Resident 000001

I decided I would be the 1st resident.

Resident 000001.

That seemed like the most reasonable place to begin. I'd already spent years building systems around my own life, and I was in the middle of the kind of transition the agency was supposed to help people navigate.

I had quit my job. I was changing how I lived, downsizing, putting things into storage, and trying to develop the company while figuring out what came next.

It's easy to design a system for an imaginary person who enters every detail on time. You picture somebody following their schedule, checking every box, and carefully recording what they did.

Then you have an actual day.

You wake up later than planned. Something takes longer. Somebody calls. You change your mind about dinner. You remember a responsibility while you're already doing something else.

Life doesn't wait for you to finish updating an application.

I started testing every feature against that reality.

If I had to organize everything before the software could help me, it wasn't doing enough. If I told the Assistant something in conversation, I shouldn't have to find the right folder and repeat myself.

And I started noticing how much of a commitment happens outside the obvious event. Getting to work involves getting ready, traveling there, working, returning, and recovering. Sleep has a beginning and an end. A purchase can affect a budget, an inventory, and a plan.

I wanted the system to understand those connections without requiring the resident to explain every piece as a separate task.

Being the 1st resident made the weaknesses personal. I couldn't hide behind the idea that a feature would probably work for somebody else.

I had become very good at rebuilding my life.

Now I was trying to build something that could help keep it together.

Chapter 08

The 4 departments

At some point, I stopped looking at the 48 folders as a giant organizational chart.

I started seeing them as 48 ways of understanding the same life.

Agency Assessment establishes where a resident stands. Housing Stability concerns the environment and resources that support everyday living. Career Development deals with work and professional opportunities. Life Management concerns the standards and decisions that shape how somebody chooses to live.

There are 12 folders in each department.

I wanted the structure to be consistent without pretending every part of life works the same way.

Somebody might struggle to get to work. That sounds like Transportation, but it might also involve their work Schedule, Salary, housing, or the Time available before the shift.

The folders help the agency recognize those different parts of the problem. They shouldn't make somebody explain it 5 times.

I spent a lot of time changing definitions because certain names sounded good until I tried to put an actual situation inside them. Sometimes a folder was too broad. Sometimes 2 folders sounded almost identical. Sometimes I'd created a category because it seemed important, not because I knew what work belonged there.

I wanted every folder to have a responsibility.

I also wanted the agency to recognize when something belongs in several places.

That means the names have to be consistent. I don't want the Assistant inventing another folder just because a name sounds reasonable. There is an actual structure.

But I don't want the structure to make the conversation rigid.

The resident shouldn't have to think in departments. They should be able to talk about their lives normally.

The departments are for organizing the work.

The person is still the person.

Chapter 09

Agency Assessment

Agency Assessment was influenced by my time working as a Youth Development Specialist at a homeless youth shelter in Boulder.

We cared for youth ages 7 to 17, many of whom arrived in crisis. When someone entered our care, there was an entire intake process to establish their immediate needs.

Within the first 72 hours, essential medical appointments needed to be scheduled. Annual physicals, dental examinations, eye appointments, and meetings with the resident therapist.

Then there was school enrollment, parental or guardian permissions, medications, mental health support, legal obligations, and information about previous conflicts or circumstances that might affect how a youth interacted with certain peers or adults.

As staff, we didn't necessarily know these kids when they arrived. But we were already responsible for their everyday care.

That experience taught me how much coordination goes into assuming responsibility for someone else's well-being, and why establishing their circumstances is so important.

When I started developing Agency Assessment for ucitysocial, I drew heavily from that experience.

I wanted the agency to have an organized way to understand where each resident stood before developing a strategy for representing them.

Time was the first folder because I kept returning to my calendar whenever I needed to rebuild my life. I wanted to understand how somebody actually spent their days, what they were responsible for, and how their existing commitments affected their availability.

Health was especially influenced by the shelter. Medical appointments, preventive care, medications, and support needs were all important parts of intake. But I also wanted to consider everyday health, including sleep, nutrition, movement, hygiene, and the habits that support physical and mental well-being.

Language concerns how someone reads, writes, speaks, comprehends, and communicates. I wanted the agency to recognize whether someone could comfortably understand the information and responsibilities being presented to them, as well as any communication skills they wanted to develop.

Background provides context for someone's history. Family, upbringing, relationships, significant experiences, and the circumstances that shaped their present life. It also helps the agency understand important connections and responsibilities that might not be obvious from an initial conversation.

Identification concerns the documents people need to establish who they are and access employment, housing, education, healthcare, and other services. I wanted residents to understand what documents they had, what might be missing, and how to maintain them securely.

Finance establishes a person's actual financial circumstances. Income, spending, savings, debts, accounts, and obligations. Financial information is essential when developing realistic plans because opportunities have costs, and the agency needs to understand what someone can actually afford.

Legal concerns relevant legal circumstances, documentation, rights, and obligations. At the shelter, legal and guardianship considerations were part of understanding what decisions could be made and by whom. For adult residents, the circumstances are different, but legal responsibilities still affect everyday life.

Mediation addresses conflict and the relationships involved in it. That might include disagreements with family, coworkers, neighbors, or other people. I wanted the agency to understand relevant histories and provide appropriate support in navigating difficult interactions without making assumptions about who was responsible.

Education concerns schooling, academic history, qualifications, current studies, and future learning opportunities. At the shelter, making sure a youth could continue their education was an immediate priority. I wanted the agency to recognize that education can remain important throughout adulthood, whether someone is enrolled in school or pursuing something new.

Employment establishes a person's work history and present employment circumstances. Their employer, role, responsibilities, working conditions, and professional intentions all provide context for the other systems the agency helps maintain.

Regulation concerns rest, recreation, recovery, and the things people do to maintain themselves. I wanted to understand how someone spends time outside their obligations and what helps them feel restored.

Community concerns relationships, belonging, participation, and support networks. Who someone can rely on, what communities they're connected to, and whether they want to develop those connections further.

Those became the 12 folders of Agency Assessment.

Of course, the experience of caring for youth in crisis is very different from working with adults who voluntarily enroll in a life management agency.

I wasn't trying to recreate institutional intake.

I wanted to apply what I'd learned about identifying responsibilities, establishing missing information, and coordinating support, while allowing residents to introduce themselves naturally.

The agency needs to understand where someone is starting, what responsibilities already exist, what requires attention, and what they want their circumstances to become.

That's what Agency Assessment is intended to establish.

And the information continues developing as the agency gets to know the resident.

Chapter 10

Housing Stability

Housing Stability was influenced by my experience working at the homeless youth shelter, too.

These were kids experiencing homelessness, and the shelter wasn't necessarily their final destination. It was a temporary environment where their needs could be addressed while arrangements were made for what came next.

I spent a lot of time thinking about what someone actually needs when they're in transition.

If a child arrives with nothing, what should their essential toolkit contain?

That question stayed with me.

When I quit my job in 2026 and moved out of my beautiful apartment in North Boulder, I decided to challenge myself.

I wanted to reduce everything I owned to what I actually needed.

I bought a little wagon trolley cart, approximately 3 feet long and 1.5 feet wide, and allowed myself 1 large suitcase.

That was it.

The trolley would hold my everyday essentials, and the suitcase would hold seasonal clothing and things I didn't need regularly.

If my belongings couldn't fit into those 2 things, something had to go.

I also bought vacuum seal bags to compress my clothing and make better use of the limited space.

I started with my wardrobe.

I don't remember the exact quantities, but I got it down to roughly 3 long sleeve shirts, 4 pairs of pants, 12 socks, 14 pairs of panties, 8 sports bras, and 3 pairs of shoes.

I tried choosing shoes that could serve multiple occasions, while still accounting for weather conditions like snow.

Then I started thinking about seasons.

Raincoats. Winter coats. Scarves. Hats.

Okay, those needed somewhere to go.

The vacuum seal bags were especially useful for compressing the clothes I didn't need every day and keeping them in the suitcase.

Then I thought about working out.

What was I going to wear to the gym? What about the clothes I needed after working out?

And what if I got another job? Would I have anything appropriate to wear?

It became this entire process of thinking through different circumstances and figuring out which items could realistically serve more than 1 purpose.

I was having so much fun with it.

Then came hygiene products.

I bought clear, color coded toiletry bags, each containing 3 airplane safe bottles.

One bag was for shower products: body wash, shampoo, and conditioner.

Another was for oral hygiene and facial skincare: mouthwash, witch hazel toner, and face moisturizer.

The 3rd was for full body skincare: body oil, lotion, and sunscreen.

I even made sure the body wash I purchased was gentle enough to double as face wash.

And while I was organizing all these little bottles, I started thinking about how cool it would be if there were local refill stations where people could replenish their essentials without constantly purchasing new plastic containers.

Why keep buying another bottle of shampoo when you could just refill the one you already own?

The same goes for lotion, body wash, and other products we use regularly.

I started imagining an entire essentials system that ucitysocial could eventually develop.

A standardized collection of affordable, non-name-brand clothing, undergarments, and body and hygiene products.

Almost like a personal uniform.

Not a uniform that residents would be required to wear, but a thoughtfully designed collection of everyday essentials that someone could choose if they wanted to simplify their life.

Basic clothing for different occasions. Seasonal options. Undergarments. Toiletries. Personal care products.

And a refill system to help maintain it all.

Everything packaged into a 3 × 1.5 foot trolley cart and 1 large suitcase, just like the setup I was developing for myself.

Imagine how much decision fatigue that could eliminate.

We all need clean clothes. We all need to bathe, brush our teeth, and maintain our personal hygiene. These are recurring needs that don't disappear, regardless of where we live or how much money we make.

Yet we spend so much time deciding which products to buy, remembering when we're running low, replacing containers, and figuring out where to store everything.

What if somebody could choose a reliable set of essentials, know exactly what they had, and have a simple way to replenish it?

It could also create opportunities to reduce packaging waste and explore more environmentally responsible ways of distributing everyday products.

That's something I want ucitysocial to explore in the future.

Not everybody wants to live with a limited wardrobe or use the same basic products, and that's completely fine.

But for people who do want to simplify, I think having that option could be incredibly valuable.

By March 2026, I had started living primarily from my trolley, suitcase, and a few additional supplies.

And now, as I'm writing this in October, I'm still relying on that same basic setup.

I documented the process on video and plan to share it on the ucitysocial YouTube channel. There's something really interesting about watching yourself question whether you actually need an item you've owned for years.

But the experiment also made me think more seriously about those kids.

If someone is moving between temporary living arrangements, having a suitcase and trolley cart could give them a practical way to maintain and transport their belongings.

I kept thinking that every child entering transitional care should have access to something like that.

A basic set of supplies that belongs to them.

Clothes appropriate for different seasons. Hygiene products. Personal belongings. A reliable way to store everything and take it with them when they move.

My decision to downsize was voluntary, so I don't compare it to experiencing homelessness. But it gave me a practical way to examine what it takes to maintain essential possessions with limited storage.

That's where Inventory and Storage really began taking shape.

Inventory establishes what someone has, what they need, how much remains, and when something might need to be replaced.

Storage establishes where those belongings are kept, how they're organized, and how easily they can be accessed or transported.

And the more I worked on those 2 folders, the more I understood how the remaining Housing Stability folders connected.

Sanitation concerns cleaning and maintaining a hygienic living environment. Organization concerns arranging that environment and the resources within it so they can be used effectively.

Information concerns the knowledge and records needed to manage a living situation. Administration concerns the paperwork, contacts, arrangements, and ongoing responsibilities associated with it.

Law addresses the rules and agreements governing a living environment, while Privacy concerns control over personal space, belongings, access, and information.

Transportation concerns how someone moves between places and maintains access to necessary resources. Maintenance addresses the upkeep and repair of the things they rely on.

Technology concerns the devices and systems supporting their personal and household life.

And Communal Space concerns shared living environments, common areas, and the responsibilities that come with using spaces alongside other people.

Those are the 12 folders of Housing Stability.

I wanted them to apply whether somebody lived in a house, an apartment, shared housing, a temporary arrangement, or somewhere else entirely.

Because housing stability is about much more than having an address.

It's also about having the resources and systems necessary to maintain your everyday life.

And there's another part of my experience in Boulder that makes this department especially important to me.

As of October 2026, the youth shelter where I worked is no longer operating because of funding challenges.

That genuinely bothers me.

I had already become frustrated with the priorities I saw in Boulder, especially during my time working at a neighboring nonprofit.

I couldn't understand how there seemed to be so much enthusiasm for certain cultural projects and entertainment, including honky-tonk radio, while essential services for vulnerable kids struggled to survive.

And then I'd see people protesting on Canyon and Pearl Street with signs saying, "No Kings."

I'd think, how about "No Homeless Kids"?

Seriously.

I'm not against the arts, radio, protests, or people expressing themselves. I've spent a significant part of my own life working in creative spaces.

But I became frustrated with what felt like a performance of caring.

There were people doing genuinely important work in that community. I worked alongside some of them.

But the loss of a shelter serving vulnerable youth made me question what the larger community was actually prepared to sustain.

When I heard Sundance was moving to Boulder, I remember thinking that the city certainly knew how to put on a performance.

Maybe that's unfair to some people there.

But that's how frustrated I'd become.

And it's part of why I began questioning the way resources were allocated, the sustainability of nonprofit services, and how much responsibility organizations could realistically maintain when their funding disappeared.

I couldn't stop thinking about the difference between providing temporary assistance and creating lasting stability.

And that became another important part of how I thought about Housing Stability.

I didn't want to build a department that only recognized whether somebody had somewhere to sleep.

I wanted it to understand the belongings, resources, environments, arrangements, and responsibilities that make everyday living possible.

Because if somebody's living situation changes tomorrow, those needs don't disappear.

And neither does the responsibility of figuring out what comes next.

Chapter 11

Career Development

By the time I turned 30, I'd worked more than 30 jobs.

I learned a lot about employment, and not always in ways that look impressive on a résumé. I've been the new person, the person learning everything quickly, the person taking on too much, and the person realizing a job wasn't what I thought it would be.

Career Development became a place to organize everything involved in getting work, maintaining it, and growing professionally.

Salary concerns compensation and what that means for a person's life. Schedule concerns working hours and professional commitments. Skill concerns what somebody knows and wants to learn. Scope concerns the actual responsibilities of their role.

Integrity concerns honesty and responsibility at work. Professionalism concerns conduct, communication, and workplace expectations. Resources concerns the things somebody needs to do their job properly.

Key Performance Indicators concerns how performance is evaluated and what results are expected. Advancement concerns moving forward professionally. Leadership concerns the responsibility involved in guiding work and people.

Information Technology concerns technology used in professional environments. It's different from the personal Technology folder in Housing Stability. Networking concerns professional relationships and connections.

Those are the 12 folders.

I don't believe everybody wants a promotion or a corporate career.

Somebody might want a higher salary. Somebody else might want predictable hours, less responsibility, a different industry, a trade, or a business of their own.

I know what it's like to have jobs that sound impressive and still feel like they don't fit the life you want.

An opportunity can look wonderful on paper and be a terrible fit when you account for someone's household, health, commute, and other responsibilities.

The agency shouldn't decide what professional success means for the resident.

It should help them understand how to pursue the version they actually want.

Chapter 12

Life Management

Life Management was probably the most personal department.

It was also the hardest to explain without making it sound like I wanted to tell people how to live.

I don't.

Standards was the 1st folder I knew belonged here. I'd spent years creating routines, but a routine only makes sense when you know what matters to you. Survival concerns the basic conditions somebody needs to keep going.

Perception concerns how someone understands and experiences situations. Instinct concerns their immediate responses and signals. Identity concerns their sense of self. Ethics concerns the principles they use to decide what they believe is right.

Equilibrium addresses balance and the effort it takes to maintain it. Boundary concerns the limits somebody chooses to establish or protect.

Discernment concerns judgment. Prioritization concerns what receives attention when everything feels important. Systems concerns methods and repeatable processes. Socializing concerns how somebody engages with other people.

Those are the 12 folders.

I can design a calendar perfectly and still decide not to follow it. I can know what would be useful and still want something else. I can want 5 different things at the same time and have only so much energy to give them.

I didn't want a system that pretended people aren't complicated.

A resident can choose different standards than I would. They can change their mind. They can decide that something they wanted last year doesn't matter anymore.

The agency should understand their choices instead of quietly replacing them.

When I looked at the 4 departments together, I could see how much of the project had come from trying to understand myself.

But building it for other people meant I had to stop assuming my own answers would work for everybody.

Chapter 13

Building the Resident Portal

Once I had the structure, I needed somewhere for the agency to operate.

I started building the ucitysocial website and Resident Portal. I wanted the website to explain the service, and I wanted the portal to feel like somewhere a person could actually receive assistance.

The conversation became central.

People don't naturally announce that they're submitting information to Department 2, Folder 9. They talk about what happened, what they need, what they're worried about, and what they'd like to change.

I wanted them to be able to say those things normally and have the Assistant recognize which parts of the agency mattered.

Behind the conversation, the folders needed working systems. Time needed a calendar that understood commitments. Inventory needed categories, quantities, and ways to update possessions. Other folders needed thoughtful interfaces and curriculum.

I started learning how many decisions go into building a usable product.

Where should a button go? What should happen when somebody corrects something? How do you show a resident what changed without sending them through their entire File?

I became very particular about the website, too. I didn't want a marketing demonstration that barely resembled the portal I'd actually built. If the real interface existed, why were we showing people a fake version?

The human Agent needed a different view of the same information. And I wanted City Hall to create a space for residents to connect without requiring everybody to participate in the same way.

I've been working with a $12/week residency model while figuring out the actual costs of technology and human support.

I've also been planning livestream demonstrations and building toward my 1st 144 residents in a city. My beta target is December 1, 2026.

Those are plans I'm working toward, not a claim that every part of the service already exists.

The screens kept improving. But eventually the biggest question wasn't where the information would appear.

It was whether the Assistant understood it.

Chapter 14

A chatbot wasn't going to be enough

The early Assistant could hold a conversation.

That was exciting until I started giving it responsibilities.

I'd explain something, get a thoughtful answer, and watch the conversation end even though the work hadn't begun.

Sometimes it would ask something I'd already answered. Sometimes it would treat my latest message as though it was the only message that existed. Sometimes I'd be discussing an ordinary problem and it would pull me right back into the schedule.

I kept thinking about what I'd expect from somebody I'd actually hired.

If I asked an employee to investigate an opportunity, I wouldn't want a speech about why researching opportunities is a good idea.

I'd want the research.

I also wouldn't want them making important decisions without asking me.

That was the difficult part. I wanted initiative without the Assistant taking authority away from the resident.

Answering a question isn't the same as maintaining a responsibility. Recording a goal isn't the same as researching how to accomplish it. Making a plan isn't proof the work happened.

I started separating those things in the instructions.

The Assistant needed to understand the work it had been entrusted to do, identify the next useful step, and maintain continuity when something remained unresolved.

It also needed to know when it lacked evidence, tools, permission, or the human Agent's judgment.

I couldn't fix that by adding another friendly sentence to a prompt.

I needed to define the job.

Then I needed to build the systems that would let it do the job.

Chapter 15

Writing the Employee Handbook

At some point, I started thinking about the Assistant like an employee who hadn't received proper training.

That sounds funny, but it helped me understand what was missing.

A person joining an agency would need to know the company, its services, its standards, and what responsibilities they were allowed to carry.

So I started developing a shared Employee Handbook for human Agents and the Assistant.

The handbook introduces ucitysocial, its history, departments, roles, governing documents, and professional training references.

I also began writing a much more detailed Agent Operating Standard. That document defines what the Assistant is responsible for understanding, how it should approach a resident, and how its performance should be evaluated.

I wanted the language to be serious because the responsibility is serious.

But I also learned that writing an instruction doesn't give software the ability to follow it.

If the Assistant has to remember something, it needs reliable memory and retrieval. If it's supposed to research an opportunity, it needs actual research tools. If it's supposed to prepare information for the human Agent, there has to be somewhere to store and inspect that work.

The instructions, information, permissions, tools, and evaluation have to support each other.

I've been reviewing the operating standard section by section rather than immediately placing an unfinished document into the live application.

By the end of October 2026, Mission sections 1.1 through 1.7 and Section 2.1 of the Standard of Devotion had been approved in the research branch. The remaining sections were still under review.

That doesn't mean the new standard is already operating in the live Assistant.

The engineering and testing still have to happen.

I've learned to stop confusing a beautifully written plan with something that actually works.

Chapter 16

My mom just knew me

While I was writing the training, I found myself returning to something from the beginning of this book.

My mom just knew me.

I hadn't expected that sentence to become part of a technical discussion about artificial intelligence.

But there's a difference between remembering a fact about somebody and understanding how that fact fits into their life.

Knowing somebody works at a restaurant is useful. But what do they do there? How long have they worked there? What do they enjoy? What do they dislike? What do they want to do next?

That understanding develops over time.

I remembered how it felt to have somebody who knew my interests, strengths, weaknesses, and habits without making me explain everything from the beginning.

I didn't want the Assistant to pretend it was somebody's mother. You can't recreate that relationship through software.

I didn't want it making up things about a resident's emotions, either.

I wanted it to pay attention.

Remember what somebody actually said. Notice when things change. Recognize how different parts of their life connect. Learn what kind of support works for them and what doesn't.

Respect the things they don't want to discuss.

And understand that sometimes a person needs help getting started, sometimes they need a practical answer, and sometimes they just want to talk.

I kept trying to explain that I didn't need the Assistant to sound more affectionate.

I needed it to be more competent.

The idea of being deeply understood had become part of the agency's standard of service.

Chapter 17

IMAGINE

I didn't want residency to begin with somebody listing everything wrong with their life.

I wanted it to begin with possibility.

That's how I arrived at IMAGINE, an opening conversation about what the resident actually wants.

Somebody might want to earn $144,000 a year. Somebody might want a particular car, a better apartment, a relationship, a vacation, or a business.

Another person might like their circumstances and just want help keeping everything organized.

I wanted all of those answers to matter.

Then I noticed something during testing. The Assistant could become so eager to make a plan that it interrupted the imagining part.

A person would share 1 ambition and suddenly the conversation was turning into an assessment.

But what if they had 5 more things to say?

People remember things as they talk. They change their minds. They say, "Oh, and another thing."

I wanted the Assistant to leave room for that.

Once the person is ready, though, the agency has work to do.

If they want a higher income, what are their current circumstances? What opportunities might realistically support that target? What qualifications, resources, time, and decisions would be involved?

If they want a Ford Bronco, it may be a Transportation goal, but affording it can also involve Finance, Salary, and other responsibilities.

I don't want the Assistant giving an inspiring answer and then leaving all the research to the resident.

I want it to investigate how the person could move from the life they have toward the life they described.

The ambition belongs to the resident.

The agency should help make the route understandable.

Chapter 18

GENESIS

The more I worked on the Assistant, the more I realized that a conversation transcript wasn't enough for the human Agent.

An Agent could read 100 messages and still struggle to find what mattered. A nice summary wasn't enough if nobody could explain where the information came from.

I started developing a knowledge blueprint called GENESIS.

The proposed structure has 4 areas of understanding within each of the 48 existing folders. That makes 192 areas across the agency.

They aren't 192 questions residents have to answer.

They're professional reference areas for the Agent Portal.

Employment, for example, has areas for current employment, employment history, workplace experience, and employment intentions.

Somebody might mention their job today, describe their hours next week, and talk about changing careers 3 months later.

I wanted the Assistant to recognize those details as they appeared and maintain the appropriate information without interrogating the person.

A statement can connect to several folders, too.

If somebody says their manager kept them late and now they're exhausted, that might be relevant to Time, Employment, Schedule, and Regulation.

But it doesn't establish that they lost pay, that their employer broke an agreement, or that the situation happens every day.

GENESIS needs to distinguish what the resident said from what was verified, calculated, or only interpreted.

The evidence should remain connected to the finding. Corrections should be visible. Unknown details should stay unknown. Privacy and sharing permissions still matter.

The Assistant would prepare this information for the Agent, who could inspect it, question it, and make corrections.

Right now GENESIS is a detailed design and training blueprint. The complete system hasn't been deployed in the live Agent Portal.

But it gave me a way to explain something I'd been trying to articulate for months.

Knowing somebody is ongoing work.

It needs a structure without becoming a checklist.

Chapter 19

Teaching the Assistant to notice

I started asking myself what happens before the Assistant responds to a message.

What does it notice?

A greeting. A joke. A complaint. A correction. A short answer. Somebody telling a story because they feel like telling it.

I didn't want the Assistant deciding that only dramatic interactions deserved attention.

So I developed a requirement for every interaction to produce at least 1 internally generated descriptive condition code.

I didn't want a fixed list of labels. I didn't want every conversation squeezed into categories like happy, sad, frustrated, or confused.

The code should describe something the Assistant actually observed.

Then it needs to distinguish what was observed, what that might mean, and what remains unresolved.

If somebody normally sends long messages and suddenly replies with 1 word, the change might be observable.

It doesn't automatically mean they're angry. They might be busy. The question might only require a short answer.

The Assistant has to consider the circumstances and the person before deciding how to respond.

The same resident might appreciate a joke when they're annoyed about something small and absolutely hate that joke when they're discussing something serious.

And not every observation needs an intervention.

If somebody says hello, a normal hello can be a perfectly good response. The Assistant doesn't have to turn it into a psychological assessment.

I was particularly determined that the internal instructions stay internal.

If I tell the Assistant to determine what it notices, I don't want it turning around and asking the resident, "What are you noticing?"

I'm telling you what happened. You're supposed to do that part.

We developed a more explicit internal sequence for observing, interpreting, relating, validating, responding, and maintaining information.

Section 2.1 of the operating standard now describes that requirement. It has been approved in the research branch, but the runtime implementation still needs work.

I want the conversation to feel natural because the software is paying better attention, not because it learned to sound more human.

Chapter 20

When the Assistant gets it wrong

I have had some ridiculous conversations with this software.

I would explain something, receive a response that sounded like it understood, and then watch it do the exact opposite.

At 1 point, it invented a Career Development folder called Business.

There is no Business folder.

We have a defined set of 48 folders, and the model decided that Business sounded like a reasonable addition.

I sat there wondering how much clearer the instructions needed to be.

Then there was the sleep problem.

The Assistant treated waking up as a completely separate counted commitment from sleeping.

I was looking at it thinking, how is waking up not the end of sleep?

A morning routine can be separate. Getting ready for work can be separate. But if somebody sleeps until 8 AM, waking up at 8 AM is how that sleep period ends.

We've updated the instructions and tests around that.

Then there were commitments that still appeared pending after the resident reported completing them. Or the Assistant asking for the same answer again after a filing operation failed.

I also tested a goal involving earning $144,000 and buying a Ford Bronco. That should require more than categorizing the vehicle under Transportation.

The Assistant needs to understand the relationship between income, cost, timing, and the resident's other goals.

And when I looked at what a test Assistant prepared for the human Agent, I wasn't seeing the deeper GENESIS information we'd been defining.

I was irritated.

But those failures revealed real problems.

A planned activity isn't proof it happened. A plausible folder name isn't an actual folder. A nice response isn't a completed assignment. And a conversation transcript isn't a professionally organized understanding of a person.

We've made practical changes to the live instructions around active work, missed commitments, guided progression, and sleep.

Not every problem is fixed.

But I'm trying to turn the moments that make me want to scream into better specifications and tests.

Chapter 21

The human Agent

I want the human Agent to see the same life the resident is actually working with.

Not a different version created from whatever the Assistant decided to summarize.

The Agent Portal is being designed as a professional mirror of the Resident Portal.

The Agent should understand the resident's actual information and systems, along with the evidence, research, pending decisions, permissions, and work that needs supervision.

I don't want an Agent spending an entire meeting reconstructing somebody's history from conversation transcripts.

The Assistant should prepare the relevant information as the relationship develops.

And the Agent should be able to question it.

If the Assistant interpreted something incorrectly, the Agent needs to correct it. If the software claims it researched something, the sources and actual work should be inspectable. If it says an assignment is complete, the outcome needs to be real.

The resident's privacy still matters. Access to information doesn't automatically mean permission to use it however the agency wants.

I think artificial intelligence creates an opportunity to change how human professionals spend their time.

Instead of collecting the same details again, the Agent could focus on judgment, investigation, strategy, and representation.

But that only works if the Assistant is reliable.

I keep coming back to the 3 roles.

The resident decides what matters in their own life. The human Agent is accountable for professional representation. The Assistant maintains information and performs authorized operational work.

The technology should make the human service better.

It shouldn't give us an excuse to pretend somebody already did work that still needs to happen.

Chapter 22 · October 2026

What I'm building toward

It's the end of October 2026, and the project still feels bigger than the version I can see on my screen.

The website exists. The Resident Portal exists. The 4 departments and 48 folders have a defined structure. Some systems are further along than others.

I'm working through curriculum, interfaces, integrations, model instructions, and details that only become obvious when I try using everything together.

There is also an enormous amount that isn't finished.

The new operating standard needs further review and integration. GENESIS needs real storage and Agent Portal interfaces. The condition code process needs implementation and evaluation. The Assistant has to become better at retrieving relevant information and keeping work active between conversations.

I want it to know the organization, understand the resident responsibly, and prepare work the human Agent can actually trust.

I don't want it claiming it finished something because it wrote a convincing paragraph about how it would do it.

The business has to work, too.

I've been examining a $12/week model, the cost of the technology, and how the agency can support residents without making the service inaccessible.

I'm planning live demonstrations and building toward a December 1 beta.

Longer term, I still think about housing and community development. That idea never really left. I want the company to create opportunities for residents and communities if we can build a sustainable business.

But I'm not going to pretend we're already there.

Right now a lot of the work is reading another deployment log. Fixing an interaction. Moving a button. Rewriting a definition. Testing something I thought was obvious and finding out it wasn't.

I used to think the hardest part of my routines was getting organized. Then I realized it was staying organized.

I'm starting to see the same thing in the company.

Building a beautiful system is possible. Making that system useful on an ordinary Tuesday, when somebody is tired and behind schedule and just trying to live, is much harder.

I don't know what every part of ucitysocial will look like when it's finished.

I'm still discovering some of the problems by trying to solve others.

But I know why I started.

I wanted people to have help managing everyday life without having to do all of the managing alone.

And I'm still building toward that.