Organizations Preview

Ask the people who know. Keep what they decide.

An organization is a client or a team you work with: its people, its projects, and one git repo that holds all of it. Sova asks each person through their own link, one at a time, and keeps every answer with who gave it and in which words.

Baton sessions

One conversation, handed from person to person.

Start a conversation with a goal only you can see. The model talks to whoever holds the baton. When they don't know, it hands the baton to someone on the roster with a question and a short briefing, and Sova makes that person a link.

They see the conversation and nothing else: no tool calls, no goal, no other sessions. Every message carries its sender's name.

  • Decisions are recorded as they're made, with the speaker's own words.
  • Profiles learn each person's language and skills from their own words. The page people see never shows a profile.

People who can't reach your machine open their link on a public address you set up: Sova's share port, which only serves shared pages, behind a web server or tunnel you run. It needs setup: docs/public-links.md walks through it. Sova's own page never goes public, and each link is shown once.

A baton session in a fictional organization. On the left, the operator's transcript: Dana from Finance asks which payroll export the bank takes, the model hands the conversation to Priya with that question and a short briefing, Priya answers, and the answer is noted as a decision. On the right, Priya's phone shows the shared page: the conversation with each sender's name, "Your turn, Priya.", and a reply box.
  • Decisions with provenance

    Each decision keeps who said it, where, when, and in their words. Sova compares the decisions on each topic and sends any contradiction to the person who decides that area. You then promote the settled ones into the project's own spec.

    No model writes the spec. Promotion is a fixed writer, a few decisions at a time, and only when you choose.

  • A project overseer

    One session per project that watches for new decisions, spots who hasn't been asked, and acts at the level you grant: propose, gather, reconcile, or build. Build starts coding sessions, each in its own worktree.

    Starts at gather. Limits per message, per day and at once are enforced by the tools, not the prompt.

  • A page for the owner

    Pick the client's owner and send one link. They read how each project is going, in everyday words: updates at real milestones, who was asked, what was decided, what was built.

    Read only. Never shows goals, profiles, code, models or costs. The link lasts 90 days.

  • The whole organization is one repo

    Roster, projects, conversations, decisions and the overseer's notes live in a plain git repo. Clone it onto another Sova host and attach it.

    Links don't travel, so you send new ones. On the new host, overseers start paused.

Start with the sessions you already have.

Organizations live in the same Sova as your coding sessions. Install it, then open Organizations from the home page.

curl -fsSL https://raw.githubusercontent.com/Naomarik/sova/master/scripts/install.sh | SOVA_REF=master bash

Then run sova, then sova open.

← Back to Sova