When a personal capability enters a real promise
The Stack Alibi
A personal AI capability can make an obligation easier to meet. It cannot become the story that lets its person step outside the obligation when the work reaches someone else.
01 / the convenient exit
As capability grows, the temptation to blame the capability grows with it.
Personal AI can make a person remarkably effective at the edge of their commitments. It can help them remember a customer preference, prepare a difficult message, compare options, notice a missed deadline, or turn a scattered conversation into a workable plan. That capacity is one of the promises of the app-to-stack transition: a person can assemble tools around their context and become more able to carry the work they care about.
But a more capable stack creates a new kind of evasive sentence. The appointment was missed because the assistant did not flag it. The client received a confident answer because the system drafted it. The colleague was excluded because an automated summary did not capture their objection. Each sentence may describe a technical fact. None, by itself, settles who made the commitment, chose the level of review, or owes the next repair.
A stack alibi is the use of a personal AI capability as an explanation that quietly separates a person from the obligation they chose to carry.
The point is not that people must control every output perfectly. They cannot. Software fails, sources conflict, instructions get misunderstood, and a person can make a reasonable choice that still harms someone. The danger begins when capability becomes a one-way shield: useful enough to claim when a result succeeds, but separate enough to blame when the same result disappoints. A Stack Person needs a better distinction between assistance and authorship.
02 / test the sentence
Where did responsibility actually sit?
Use the switchboard to separate a technical explanation from a human obligation. The same incident can contain both, but they should not be confused.
State the mechanism honestly.
It is useful to say what malfunctioned, what source was wrong, or what the system did not know. Technical clarity helps prevent the same failure from repeating.
But do not stop there.
A system description cannot answer whether its use was appropriate for this promise, or whether a person should have checked before relying on it.
Name the point of choice.
Someone decided to send, defer, accept, automate, or trust a result. That choice may have been pressured or imperfect, but it remains part of the event.
Keep ownership specific.
Responsibility does not require total control. It requires the ability to acknowledge a chosen role and make the next corrective move.
Start with the effect.
A customer may be waiting, a colleague may be misled, or a family member may have planned around an assurance. The relationship is not a technical edge case.
Repair is the test.
The relevant question becomes: what does the person now need to clarify, correct, restore, or renegotiate with the people affected?
03 / a stronger kind of ownership
Keep the capability. Keep the obligation visible.
App People often encountered responsibility inside a fixed workflow. The required fields, assigned queue, approved button, and system record gave an organization a visible place to ask what happened. That visibility could be constraining, but it made one fact hard to ignore: a tool was part of a larger arrangement of people and promises.
Stack People will work across more personal arrangements. A capability may be partly private, adaptive, and difficult for an institution to see. That is exactly why the social contract around it has to become more explicit. The person need not disclose every prompt, memory, or private connection. They do need a way to say what they have undertaken, what the stack may do, and when a human check remains necessary.
This extends The First Stack Generation. The app-to-stack transition gives people more agency over the capabilities that surround their work and lives. Agency is not freedom from consequence. It is the growing capacity to enter commitments with better help while remaining present when that help is wrong, insufficient, or misapplied.
A stack alibi is tempting because it offers a clean divide: the tool did the thing; therefore the person did not. But personal capability is valuable precisely because it joins a person to more context, more choices, and more possible action. The better cultural norm is not blame for every technical imperfection. It is a practice of repair that treats assistance as real, failure as explainable, and human responsibility as something no capable stack should make invisible.