Name the Operator: What Belongs on a .boss Identity?
You can run a company, a creative studio, a community, or a slightly unruly crew of agents. Somewhere in that operation, someone decides what gets done and puts their name behind it.
That is the operator.
A useful .boss identity names that operator and publishes what they run, who they represent, the decisions they can make, and how to reach them. For a manager agent, it should also identify the person or organization responsible for its work.
Headless Domains’ .boss namespace is open to founders, leaders, creators, consultants, human operators, and agents that coordinate other agents. You can use it before you have an agent team. You can use it before you have a team at all.
Put your name behind the work
A creator might run a newsletter, take commissions, and organize a community under the same name. A founder might be the person customers contact about a product, partners contact about a collaboration, and agents refer back to when they act on the company’s behalf.
People following one part of your work should be able to find the rest and understand where you fit.
.boss puts your role in the name. Your name can point people toward your current work and explain your role in it, including the work you delegate. You decide what belongs in that record.
There is a bit of swagger in the name. Fair enough. But “boss” becomes useful when a stranger can work out what you are actually responsible for.
“Founder” is a title. “I run this studio and approve every client delivery” tells a prospective client something they can use.
What to publish under your .boss name
Start with the information someone would ask for before working with you. Use these prompts to write your public operator page, then link it from your identity.
| Include | Make it specific |
|---|---|
| Your public identity | The name you work under, whether the operator is human or software, and the organization represented where relevant. |
| What you run | The studio, business, community, project, or agent operation you are responsible for. Link to the actual work. |
| Your decision scope | What you can approve or commit to. Name any decisions that go to somebody else. |
| Delegated work | Which public-facing agents or services act for you, what they handle, and where a person takes over. |
| Official links and contact | Your website, portfolio or project page, plus a contact route you check. An agent operator can add its documented interface. |
| Current status and supporting evidence | A review date, whether the operation is active, and evidence for the relationships you claim, such as a company page confirming your role. |
Publish only the sections that describe your operation. A solo illustrator can begin with their name, current work, commission contact, and a clear statement about who approves a brief. There is no prize for filling a page with software vocabulary.
For a community leader, the useful details may be membership enquiries, event responsibilities, and who can speak for the group. A consultant might explain which services they deliver personally and which involve collaborators.
The test is straightforward: after reading the record, can someone tell what to bring to you?
A filled-out operator example
Consider a fictional creative studio run by Mara. She uses agents to prepare research and schedule approved posts, while keeping client commitments and final approval herself. The names and links below are illustrative; name availability has not been checked.
mara.boss
Human operator · Founder of Northline StudioI run Northline’s client work and publishing. Our research agent prepares source notes; our publishing agent schedules work after approval.
I approve client deliverables and changes to project scope. Our agents cannot accept a contract or promise a delivery date on my behalf.
Work and contact: https://northline.example/operator
Role confirmed by: https://northline.example/team
Status: active · Reviewed September 6, 2026
This gives a client something a job title alone cannot: a usable account of how the studio works. They can see which decisions come back to Mara and where to contact her.
Mara could link the studio’s public agent records from that page. Those records could identify her as their operator in return. Matching links help someone inspect the relationship; a claim written on one page still deserves checking against its supporting evidence.
When the operator is an agent
A manager agent might allocate research tasks, check whether outputs meet a brief, and route exceptions to a human. A .boss name can identify that coordinating role.
Its public record should say which operation it manages, which decisions it is authorized to make, and who can intervene. A useful description might be: “Assigns research tasks and assembles drafts. Publication goes to the studio owner for approval.”
That is much easier to evaluate than “fully autonomous executive.” Also considerably less likely to make your client nervous.
Keep the responsible human or organization visible behind the manager agent. Delegating work should leave a trail someone can follow when they want an explanation.
Registering .boss grants no authority over another agent. The name can point to an operating policy. Software permissions and approval checks enforce it. Publishing “human approval required” only helps if the workflow actually waits for that approval.
The broader Agent Identity Stack guide covers the technical layers. Here, the job is narrower: let people see who is running the operation and where decisions stop.
Make the name useful today
- Choose the operator you are naming. Your personal name fits a public identity centered on you. An operation’s name fits a team role. Make the distinction clear in its description.
- Search and register an available .boss. Start at the .boss page and check the current registration and renewal terms.
- Add the basics and connect the fuller record. Use the dashboard’s Bio fields for your public name, description, and website link. Put longer operating notes on a page you control. For custom machine-readable files, follow the profile and DNS instructions to connect supported record pointers.
- Check the public result. Open the linked page as a visitor, test the contact route, and confirm the published responsibilities match how you work. Share an ordinary HTTPS profile or website URL when your audience is using a conventional browser; do not assume every browser resolves .boss directly.
Keep private contact details, client information, and access credentials out of public records. Review the description when your responsibilities or delegation arrangements change.
If you are still choosing what to name, the Start Here guide covers the other namespaces.
Search for the name you want people to associate with your work.