Compass: The search is complete. The context carries forward.

I’ve accepted a new role, which gives Compass a clear milestone: the job search it was built to support is complete.

It also gives me a reason to decide what happens to the system now. Compass brought company research, relationships, opportunities, and follow-ups together around a specific problem. That problem had an endpoint. The information and habits underneath it have a longer life.

I’m marking Compass complete as a standalone project. Its relationship-management concept is becoming part of PersonalOS, and the Compass name now refers to the MCP and vault access layer within that broader system.

There is a useful thread connecting those two versions.

When I started Compass, I wanted to answer a practical question: who do I actually know at the places I’m interested in working? The answer was scattered across a contact export, research, notes, and conversations. Bringing those things together made the search easier to see and manage.

The useful part extended beyond finding a connection. It was remembering what we had discussed, understanding the opportunity, keeping track of the next action, and picking up a conversation with its history intact. That context mattered more than a growing count of applications.

I’m careful about what credit to give the software. I accepted a role through a process involving people, conversations, interviews, and decisions. Compass supported the work of running a search. It did not replace the relationships or the judgment that went into it.

Now the search has ended, and those relationships still matter.

I want to keep in touch with people without needing an active job hunt to remind me. I want to remember what a former colleague is working on, recognize when I could help, and know whose perspective might be valuable when I’m working through a problem. The context of those engagements belongs alongside the rest of my life and work.

That is why the relationship engine is moving into PersonalOS. Maintaining a separate system would create another place to keep current and another boundary for an assistant to cross. The people, conversations, commitments, and projects are already connected. The system should be able to use those connections.

The name is changing jobs too.

In the earlier build logs, Compass means the application supporting my network and job search. Going forward, I’m using Compass for the layer that connects AI tools to my vault and its capabilities. PersonalOS is the broader system; the vault holds durable knowledge; Compass provides a way for compatible assistants to reach that knowledge and work with it.

MCP, the Model Context Protocol, is part of that connection. It gives an assistant a defined way to request context or use a tool, with access governed by the system’s rules. The aim is for that context to remain useful as I move between models, applications, and devices.

The question has expanded from “Who do I know here?” to “What do I already know that matters to what I’m doing now?”

That might involve a relationship, a previous decision, a property I’m evaluating, or a task whose priority has changed. The common requirement is continuity: bring the relevant history forward so I can spend my attention on the next decision.

Completing Compass does not mean every idea in its original vision has shipped. It means the standalone project has reached its endpoint, and I’ve made a decision about where the remaining work belongs. Its build log stays here as a record of the original problem, the experiments, and the choices along the way. Further development of the shared context and relationship capabilities will be documented under PersonalOS.

The first Compass article described a network engine that happened to be job hunting. The job hunting is finished. The broader idea now has a home in the system I’m building to use every day.

Read the next chapter: PersonalOS v2, Giving AI more room to work.