The Courtesy Layer
A personal AI capability should make a person more prepared without making everyone else guess when it is speaking, promising, or carrying something that is not its own.
01 / the social problem
A stack enters relationships before it enters a workflow.
App People learned to operate inside systems. Stack People will need to decide how an evolving capability behaves around other people.
A fixed application generally made its role obvious. A calendar sent an invitation. A customer system displayed a record. A form collected a field. The person could still misunderstand the software, but other people usually knew which system had made the move and who was accountable for the result.
A personal AI capability changes the texture of that encounter. It can prepare a reply in a familiar voice, draw on notes from an earlier conversation, spot an opportunity to follow up, and make a next step feel frictionless. Those are useful powers. They also make it easier to blur a line that matters: the difference between a person being helped and a person being represented.
The courtesy layer is the set of explicit habits that tells a Stack Person’s capability when to prepare, when to ask, and when only a named human may speak or carry context forward.
This is not an argument for making every interaction slow or ceremonial. It is an argument for making agency legible. The more a stack can anticipate, draft, connect, and remember, the more it needs a practiced way to avoid turning convenience into an unannounced claim on another person’s time, information, or trust.
02 / three habits
Courtesy is not a feature. It is a boundary practiced at the moment of contact.
The point is not to make a stack timid. It is to let its owner be effective without becoming opaque to colleagues, clients, friends, or strangers.
Mark the voice.
When a message matters, the recipient should be able to tell whether it is a person’s considered reply, a person-approved draft, or an automated acknowledgment. A polished sentence should not impersonate deliberation it did not receive.
Ask before the crossing.
A stack may notice that a past note could help with a current relationship. That does not mean it may carry the note over. Context is often useful precisely because someone trusted it to remain bounded.
Keep the promise human.
A capability can assemble options and make a handoff easier. It should not silently convert preparation into a commitment, a disclosure, an escalation, or a claim about what its owner will do next.
03 / a small exchange
The courtesy layer makes the stack intelligible from the other side.
Consider a familiar situation: a capability finds an old note that could make a response more useful. The efficient move is to insert it and send. The courteous move is to distinguish the work of preparing from the authority to use it.
That distinction can be nearly invisible to the owner and profoundly important to the recipient. It leaves room for a person to check whether the earlier context still belongs, whether the tone fits this relationship, and whether the action makes a promise they intend to keep.
04 / the institutional consequence
Organizations can establish social clarity without taking ownership of every personal method.
Companies, schools, and professional groups will be tempted to solve this problem with a single rule: either ban personal capability or absorb it entirely into an approved system. Neither response understands the actual change. People will develop methods that help them notice, compare, draft, and remember. The practical question is how those methods encounter shared relationships.
A stronger approach names a few consequential crossings. Which communications may be drafted but not sent? Which customer or student context must remain inside a protected environment? Which commitments require a named approval? What does a recipient need to know in order to understand the source and status of a message? These are not merely technical settings. They are the social grammar of work with evolving capabilities.
For Stack People, that grammar becomes part of professional judgment. A good stack does not merely help its person act faster. It helps them remain someone other people can understand and trust.
- Can the recipient tell what kind of voice they are hearing?
- Did the context arrive with a reason and a boundary?
- Has preparation been mistaken for a promise?