TellenzeThe Loop · People and agents
Give every contribution a purpose, an allowed scope and someone who can judge the result. People and agents can work from the same evidence while keeping responsibility for decisions clear.
A useful request has a clear handoff
Name the outcome, its checks and the person responsible.
Give the task, accessible sources and allowed actions.
Record what changed, what was checked and what remains open.
The responsible person checks the result and chooses the next step.
Responsibilities across The Loop
Focus, Execute, Observe, Review, Learn and Adapt are connected practices. Return to an earlier question when the evidence changes. The examples below describe useful requests, not a promise that every client or tool supports every action.
| Practice | People decide and check | Useful agent help |
|---|---|---|
| Focus | Agree on the outcome, its owner, the scope and how to check success. | Read the accessible brief. Identify missing context, assumptions and questions before suggesting a plan. |
| Execute | Choose the work to do, resolve scope questions and check contributions. | Help with the agreed task through configured tools. Keep decisions, output and verification beside the work. |
| Observe | Choose relevant evidence, check its source and notice what is still unknown. | Summarize the available evidence. Separate recorded facts from interpretations and missing information. |
| Review | Judge the result against the intended outcome and acceptance criteria. | Prepare a comparison of the expected result and saved evidence. Name gaps instead of treating a summary as approval. |
| Learn | Decide which lesson is useful, why it matters and where it applies. | Draft a lesson from reviewed sources, including its limits and the situations where it may not fit. |
| Adapt | Approve the next change and give follow-up work a clear home. | Propose a better brief, check or preparation step. Apply supported changes only within the request’s authorization. |
Give an agent a useful request
Start with a work-item identifier, the intended result, acceptance criteria and useful source links. Say whether you want reading, a proposal, a draft or an authorized change. Name the decisions you want brought back for review.
In Tellenze, use Definition for the saved scope and Conversation for questions and progress. Check the output against the source, including any uncertainty the agent reports.
Prepare an agent work request“Read PORT-18 and its linked handover guidance. Check whether the steps and acceptance criteria are clear. List missing facts and propose edits for review. Keep private source material within its current access.”
The person responsible reviews the proposed edits. The request asks for a proposal; it does not authorize unrelated changes or external messages.
Use current context and permissions
Check the connection and the sources needed for this request. A link does not grant access, and a summary can be outdated. Resolve missing or changed context before relying on a proposed action.
Where it applies, supported agent changes need the current pinned reading and a valid receipt. An ordinary document link does not make reading required. A receipt records delivery, not understanding or correctness.
Check Required ContextLooper can answer from accessible workspace context and propose supported changes for confirmation. Ask an agent targets a configured companion on Project work for research, clarification or follow-up coordination.
Agent reactions have limited workspace context and no filesystem access. Repository changes use your normal development workflow.
Read the reaction boundariesCheck recipients and copy before explicitly authorizing an email. Review publication and reader access are explicit author actions. Deployment or another external change needs authorization for that action.
Preparing a draft or plan is a separate result from sending, publishing or applying it.
Read connected-agent email controlsAn illustrative shared contribution
Synthetic example: a team wants a new teammate to follow a support handover without guessing. These are proposed responsibilities and checks, not measured customer results.
The responsible owner names the handover’s purpose and the person who can check it. The task says which steps and decisions the new teammate needs.
An authorized agent reads the accessible task and guidance, flags missing steps and proposes clearer criteria. It names any source it could not read.
The teammate opens the guidance with their own account and follows the steps. The team records unclear instructions and updates the agreed work.
The reviewer checks the finished guide and saves the evidence. Separate enhancements get explicit follow-up work. The owner decides whether the Focus’s main value has been delivered.
Closing a Focus does not complete unfinished tasks. Keep their true state and history, and give remaining work an explicit follow-up Focus. A completed agent request also does not mean the original task is complete.
A few useful details
No. People can use the six practices with their existing board and shared documents. Add an agent where a clear request and usable context make its help worthwhile.
Focus ownership describes responsibility for the outcome. Member and administrator permissions are separate. Work, sources and available actions still follow the workspace’s current access rules.
Focus timing fits the outcome and may be timeboxed. The recommendation of at most three active Focuses per team helps keep attention manageable; it is not a product restriction or a per-person limit. Read Focuses for the full guidance.
In Tellenze, Looper and MCP can help prepare a review draft. Preview publication, named reader access and Publish edition remain explicit actions by its author in the interface. Check the actual report for its intended audience.
Make judgment possible
Choose what would show that the outcome happened, then keep both the result and its limits clear.
Choose outcomes and evidenceKeep the next step useful
COME TAKE A LOOK
Curious? Join the waitlist and see how we welcome your team.
Tell us a little about your team. We’ll explain the next steps and invite you when we have capacity for your workspace.
Join waitlist Start with your email. No payment needed to join.