What is Amphora Ops?
Amphora Ops holds the organisation's work in one place and fills in what really happened from our own systems.
What does Amphora Ops hold?
Amphora Ops holds the organisation (units, positions and their holders), its processes, its projects with milestones and tasks, and the decisions asked to people. A holder can be a person, an AI bot, a service or an outside party.
Where do its facts come from?
From what happens in our own systems: messages between the team's bots and people (only who, when and to whom, never the text), code changes, test runs and status updates. Every change is kept as an event, so the history stays.
Times are measured only between real events. Where an event is missing, Amphora Ops shows instead of a guess.
Can I change something on the web?
No. The web views are read-only: nothing you click changes data. Changes come from the team's work itself, and from plain-language requests in the team's channel, which the bots record.
Which view answers which question?
| View | Question it answers |
|---|---|
| Org | Who holds which position, and since when? |
| Main process | Where does work wait between need and live? |
| Processes | Which processes do we have, and what is still missing from each? |
| Services | Which services do we offer? |
| Board | How does each project and release stand? |
| Decisions | What is asked of whom? |