The outcome, next action, or decision is still too vague for a team or agent to move.
CREATE SOMETHING .ltd · The operator library
Run AI work people can trust.
Start with one recurring workflow. Leave with a playbook that tells your team and its AI what can run, what waits for a person, and what proves the work happened.
- Start One workflow
- Name One owner
- Set One boundary
- Keep One receipt
Start where the work is real
A useful system gives everyone the same picture.
A playbook gives the team the decision model: the outcome, owner, approved work, wait point, and receipt. A runbook turns it into live steps, checks, exceptions, and recovery.
Triage inbound work without losing context
Turn an incoming request into a named next action without asking a person to reassemble the story from scratch.
- Approved work: Collect the request, source evidence, urgency, and stated outcome into one brief.
- Receipt: A linked source record, chosen lane, named owner, and reason for the decision.
Give a responsible person the signal, trade-offs, recommendation, and source evidence needed to decide without chasing updates.
- Approved work: Gather approved source records, summarize options, and state what decision is required.
- Receipt: The source set, recommendation, decision, owner, and dated follow-up.
Stop unsafe or uncertain work cleanly, give a person the right context, and leave a recovery path another operator can trust.
- Approved work: Pause the workflow, preserve context, and prepare the exact decision that needs human judgment.
- Receipt: The stop reason, evidence set, reviewer decision, and recovery or rollback action.
What the library is built against
The opposition is unclear work.
Ambiguity, inaccessible context, and untrusted automation are why capable teams still wait. Make the boundary visible before it becomes a failed handoff.
Find the boundary in your workflowThe records or authority needed to help are unavailable, unclear, or outside the allowed boundary.
People cannot inspect the reason, source, owner, or recovery path behind an action.
A library that earns a return visit
Keep the useful rules close to the work.
Choose the play
Find the recurring moment where a workflow needs a clearer decision.
Run it with a boundary
Make the owner, allowed action, wait point, and recovery path inspectable.
Keep the proof
Leave a record that another operator can review, trust, and improve.
Property progression
Put the playbook to work when the boundary is clear.
.ltd gives you the operating language, .io carries the research and evidence, .space lets you rehearse the behavior, and .agency helps when a named workflow needs a dedicated build partner.
You are here .ltd Canon
- 01 .ltd Canon Clarify the principles, standards, and judgment that should guide the work.
- 02 .io Research Inspect the evidence, field reports, and operating notes behind the claim.
- 03 .learn School Follow a guided path and leave with an inspectable working artifact.
- 04 .space Workbench Run the tools and rehearse the behavior before the pattern becomes delivery.
- 05 .agency Build Map one workflow, qualify the control boundary, and choose the delivery path.