The work
- Deliverable
- the tangible, measurable result of the work — "Monthly report published", "Launch campaign live". It belongs to a team, which answers for it. It is the "what".
- Recurring deliverable
- a deliverable with Recurring status — a continuing goal, with no final deadline (monthly sales, NPS, uptime). You record the result of each period and it never "finishes" at 100%.
- Task
- the "how". It belongs to a deliverable, and it is task progress that computes the deliverable's progress. Different from your personal to-do list, which belongs to no deliverable.
- Target and target type
- the amount to be produced and the unit it is measured in — percentage, unit or money value (plus any types your organization already uses). There is no "yes/no" target type.
- Recipient
- who benefits from the deliverable — internal, clients/users, beneficiaries, community, suppliers, government, partners, investors.
- Requester
- the team that formally asked for the deliverable.
- Grouping
- the tree of groups the organization uses to classify its deliverables (by area, by business line, by whatever makes sense). It has its own page in the sidebar.
- Planned baseline
- the planned dates, the target type and the deliverable's target. Editable until the planned start date arrives; from then on they are locked, and changes move into the "Updated" fields.
The plans
- Team deliverables plan
- the deliverables a team will work on during a period. It is signed by the manager, and the signature is the moment the scope gets reviewed.
- Planned
- a deliverables plan already signed whose period has not started yet. Not to be confused with Draft — a draft has not been reviewed by anyone.
- Source plan
- the signed deliverables plan (and In progress or Planned) a deliverable has to come from in order to enter a work plan. For an AI worker this rule blocks; for a person, it only records a warning.
- Work plan
- a worker's individual commitment — which deliverables they work on and how their time is split across them, as a percentage of effort.
- Participant and supervisor
- the two signature lines of a work plan. Both signatures advance the plan and automatically create the assessment cycles.
- Agreed
- the work-plan stage after both signatures, before the period starts.
- Adjustment requested
- a stage of its own, created when someone asks for an adjustment to a plan that is not yet agreed. Both signatures are cleared and both parties sign again. Not the same as going back to Draft.
- Work agreement
- the house rules in the form of a structured questionnaire, which comes down from the organization to the team and from the team to the person. When a work plan is signed, the work agreement in effect is frozen inside the plan — what counts is the version from the day of the signature.
Cycles and assessment
- Cycle
- the assessment window created by the signing of the work plan. Its duration comes from the feedback frequency chosen in the plan.
- Cycle report
- what the participant writes about what was done, deliverable by deliverable. It can be submitted from the last day of the cycle onward, and even after the deadline, as long as the manager has not assessed it.
- Feedback given
- the state of the cycle after the supervisor has assessed it. It is still mutable: the window is running to request a review or for the manager to adjust.
- Review requested
- the participant's request to reassess a low feedback, within the window.
- Consolidated
- the final, immutable state of the cycle. After that the rating no longer changes, and a work plan is only finalized when all of its cycles are consolidated.
- Assessment frequency
- how often a participant's work is assessed. It is what determines the length of the cycles.
- Precedent
- the recorded "why" of a decision — the reason, the lesson, the risk taken. It is kept and reused later, both by you and by Orion. It is what makes the system decide more and more the way your house decides.
People, roles and AI
- Org role
- Admin, HR, Audit or User. It applies to the whole organization and is checked on every request.
- Team role
- manager, assistant, member or observer. It applies to one team at a time, and a person has a single role per team.
- Observer
- a read-only team role, meant for a mentor or an outside consultant. Sees the team's work plans, never leads, does not see cost (unless the Admin allows it), and has no write button at all.
- Work group
- the category of a WhatsApp or Telegram group, chosen on the group's row in Orion → Connection (WhatsApp) or in Orion → Telegram. There are three, and every group has one: Regular — the default, where nothing said there enters the work record and Orion answers using public knowledge only; 🏢 Internal work — content captured, and there Orion may use the organization's internal knowledge to answer; and 🤝 External work — content captured, including what people from outside write, but Orion stays on public knowledge and only files a document into the library when you ask; a request from another participant is declined. The category is independent of the authorization to take part, and it exists only on the screen — neither you nor Orion declares a group over chat. See the security and privacy chapter.
- Home team
- a person's main team, recorded on their profile.
- Worker
- the unit that carries a work plan. It can be a person or an AI worker — the work plan is the same object in both cases.
- AI worker
- an AI-powered worker hired by the organization. It takes a seat, has a work plan, submits its own cycle report, and is governed by an autonomy matrix.
- Escalation
- an action the AI worker prepared but cannot run on its own under the organization's autonomy policy. It waits for a decision from those who can give it — the organization's Admins, the account owner and whoever leads the team of the worker's current plan signed by both sides (for a reply from your own Orion in a group, only you) —, who decide in the conversation with their own Orion or on the Orion → AI Team Governance page. In the conversation, a bare "approve" only decides right after the notice, replied on WhatsApp, one born in your own Orion that is the only one waiting on you, while the notice is still Orion's last message to you. Otherwise — in the panel, in the app, by voice, after another message from Orion — and always for one born in another person's Orion, only its number on the list ("approve 1") or its code counts.
- the permission, given by a manager and always optional, for Orion to conclude an act that would be the manager's — applying a cycle's assessment, signing an AI worker's work plan, or creating deliverables and tasks inside an already signed deliverables plan. It is per team, it arrives switched off, it gives notice the day before, it gives a receipt afterwards, and it goes away with one sentence ("stop doing this for me"). What is concluded that way is signed as "by Orion under so-and-so's pre-authorization" — never in the manager's name. It pauses without a subscription (the organization's or the giver's) and applies again on its own. See the work plans and cycles chapter.
Billing
- Seat
- Orion's billing unit. Each person on a paid plan takes one; each billable AI worker and each extra WhatsApp number takes one too, at the WhatsApp plan price.
- Free-seat floor
- the number of human members your organization has for free on Y Managers. It is zero by default: it only exists when the Orion team grants one to the organization. It is subtractive — it comes out of the count before the calculation.
- Billing manager
- who can change the plan, seats, payment method and cancellation, and authorize the new Pix Automático amount (customers in Brazil). Every Admin sees the Billing page; only the billing manager changes it.
- No subscription
- the state of someone with no plan or grant that gives access, or of an organization with nothing backing it. See the No subscription chapter.
- Referral code
- an Orion partner's code, entered once, at the moment you subscribe — either in the conversation's Pix flow (customers in Brazil) or in the field on the subscribe screen. It does not change afterwards, does not alter the price, and is not accepted on a reactivation. Not to be confused with an invitation to join an organization, which is always by email and has no code.
