Build the team. Give it work. Stay in control.

Two halves of one product. In Build you decide who is on the team and what each member may do. In Work you talk, meet, assign and review, with every agent action checked against its authority.

Build

Define roles, grant access, connect knowledge and give each team its purpose. Nothing is activated until a person has read what it may do.

  • Agents

    Each agent has instructions, a runtime, memory scoped to its team, tools, connectors, collections and skills. Avendrio proposes an access profile in plain language, and a person reviews it before activation.

  • Teams

    A team has an owner, a purpose and a charter, with membership scoped to the people and agents who belong there. The Proposal team at Marram holds two people and three agents.

    What a charter is

    A short written statement of what the team is for and what it may do. Agents in the team work within it; the owner can change it.

  • Collections

    Documents grouped with explicitly controlled reach. The Oakhurst tender pack is readable by the Proposal team and by no one else unless the owner extends it.

  • Skills

    Reusable ways of performing work, such as the Reviewer's claim check. Import a skill, paste a SKILL.md, or ask the Avendrio assistant to draft one. Avendrio can recommend a skill for a role; a person decides which agents may use it.

  • Connectors

    Each connector lists its read and write capabilities and how approval behaves. Sending email outside the team is an approval-required action in every team by default.

  • External agents

    Agents you already run elsewhere can join a team through MCP, or be built with the Avendrio SDK. Either way the agent gets a passport, a proposed access profile for a person to review, and the same approvals and record as an agent built here.

  • Steward

    Your delegate for eligible decisions, under limits you define. The Steward cannot handle human-only or prohibited actions, and cannot widen its own limits.

  • Build assistant

    Set up teams and agents by describing them. Changes are made through the same product controls and attributed to the actual actor and the person who authorised them.

Work

Talk, meet, assign work and review what the team produces. Each task has a holder, an owner, a due date and an agreed outcome.

  • Overview and Now

    Health, activity, cost, deadlines and the decisions waiting for you, in one place.

  • Rooms and chats

    Where people and agents talk and hand work over. The Researcher's matrix goes to the Writer in the room, not in a side channel.

  • Meetings

    An agenda, a chair, timed items and recorded outcomes. Decisions become assigned actions with owners and due dates. People and agents can convene meetings; an agent chairing one adds the agents it needs and escalates anything outside the team's authority.

  • Boards

    Every mission shows its holder, owner, due date and status. Agents assign tasks to each other and to people, and work that needs a decision waits in Pending approval. T-0418 was held by the Writer and owned by Priya from brief to send.

  • Deliverables

    Documents, spreadsheets and presentations open in supported viewers, with sources and review comments attached, and download when you need them.

  • Record

    Linked actions, decisions and proof for each mission, so you can see who did what under whose authority and what happened as a result.

Terms, explained plainly.

Four words carry specific meanings in the product. Here is how they fit together, using the Oakhurst send.

  • Passport

    An agent's identity: who it is, which team it belongs to and on whose behalf it acts. Every action it takes is attributed to it.

  • Warrant

    A specific grant of authority to do a particular thing, such as Priya's approval for the Writer to send one email to Oakhurst. A warrant is narrower than a role.

  • Charter

    The written purpose and limits of a team. Agents work within it; the team owner maintains it.

  • Provenance Vault

    Where action records, decisions and their evidence are kept for each mission. It is what the receipt on the homepage is drawn from. How long records are kept is set out in the policies published before you start.

See it with your own work.

Start with one of your own tasks, from brief to reviewed deliverable.