# p10q > A boutique software studio making useful macOS and iOS apps, plus tools for the web. ## Cairn Cairn shows which coding-agent workspace needs attention and what changed while you were away. It keeps terminals and supported Claude Code and Codex CLI sessions attached to their workspaces. Cairn Remote extends that control to iPhone and iPad. Cairn Remote is available on the App Store for $19.99: https://apps.apple.com/us/app/cairn-remote/id6781109004 It requires a separately licensed copy of Cairn for macOS. Remote connections use SSH and infrastructure in the customer's own AWS account. ## Record Maps Record Maps keeps public-record facts attached to their government or primary source. The directory covers 11 maps and 352,483 records. Senior Care Record Maps covers 51,188 facilities. Record Maps Pro costs $19 once and includes saved multi-layer views, private notes, same-entity-type comparison, CSV exports, and every current and future entity type. ## Site map - https://p10q.com/: Cairn and Record Maps product showcases - https://p10q.com/about/: About the studio and its working principles - https://p10q.com/cairn/: Cairn (flagship product) - https://p10q.com/record-maps/: Record Maps product page - https://p10q.com/cairn/privacy/: Cairn privacy policy - https://p10q.com/cairn/terms/: Cairn terms - https://p10q.com/cairn/eula/: Cairn end user license agreement - https://p10q.com/cairn/refunds/: Cairn refund policy - https://p10q.com/cairn/support/: Cairn support - https://p10q.com/cairn/security/: Cairn security reporting - https://p10q.com/cairn/setup/: Cairn Remote setup - https://p10q.com/cairn/releases/: Cairn release notes and version history ## Cairn Developers - https://p10q.com/cairn/developers/: Cairn local API, plugin, reference, and example documentation ## Writing Essays and talks on building software, working with agents, and keeping useful context intact. - https://p10q.com/articles/journey-to-cairn/: How durable terminals, agent state, notifications, and remote hosts led to a minimal control surface for parallel coding work. - https://p10q.com/articles/journey-to-record-maps/: How a family search for senior living became a source-linked way to research care, childcare, education, health, and local services. - https://p10q.com/articles/ai-learnings-2026/: Six practical rules for building software with coding agents. - https://p10q.com/writing/: Reviewed writing index and dependency graph --- ## Journey to Cairn: expanded article context URL: https://p10q.com/articles/journey-to-cairn/ Claude Code made one terminal coding agent useful for repository inspection, editing, commands, tests, and Git. Pi opened the surrounding harness to extensions, skills, providers, prompt templates, and custom commands. The parallel-worker behavior described in the article came from a local extension, not a built-in Pi subagent feature. cmux made those parallel workers visible in native macOS workspaces and splits. As more work moved to always-on remote machines, Ghostty and tmux kept it running across SSH disconnects. These workflows exposed a new bottleneck: starting agents was easier than finding the workspace that needed a human response, seeing what had changed, and resuming the exact work later. Herdr kept real agent terminals alive, rolled their state up as working, blocked, done, or idle, and supported reattachment from another machine. Shepherd extended that view across local and remote Herdr hosts from the macOS menu bar. Community notification plugins made the feedback loop explicit: watch meaningful state changes, keep routine activity quiet, and return the operator to the right pane. The current Cairn workbench keeps real local and SSH terminals at the center, relates them to durable workspaces and supported agent sessions, and uses a minimal attention and history surface to show which workspace needs a decision, what changed, and which terminal should resume. Many machines and hundreds of agents remain a design goal. Current usage does not support a fleet-size statistic. Reaching that scale requires aggregation, selective rendering, provenance, permissions, and clear review boundaries while every status remains tied to real workspace evidence. Grok Bot and Raft provide opinionated collaboration layers for persistent agents through identities, shared context, and handoffs. Cairn keeps that layer replaceable. Every workspace resolves to a terminal and its PTY session, so models, harnesses, and coordination patterns can evolve without changing how work is observed or resumed. Keep coordination flexible and terminal sessions durable. --- ## Journey to Record Maps: expanded article context URL: https://p10q.com/articles/journey-to-record-maps/ Record Maps began when the author's mom needed to find senior living in the Bay Area. General web searches produced listings and advertisements, but the family still had to move among agency sites, documents, and datasets to understand what public records said about each place. The first Senior Care map put nearby records into one geographic research view. It preserved the source, source definition, observation date, and missing values. The map did not rank facilities or choose one for the family. It reduced clerical work and made it easier to arrive at visits and conversations with better questions. The same research problem appears in childcare, education, health, treatment services, contractors, and other local services. Record Maps brings those separate public datasets into a consistent interface while keeping each fact attached to the record that supports it.