The ideas, one at a time, each with a picture
How it works
Nine short pages, one idea each, each with a picture. The first five are the reasons to choose Vigile; the last four say how it runs.
Vigile is one service that holds one plan: items, and links between them. Every change goes through an operation that is checked against the plan before it is stored. What can start, what waits and where the plan contradicts itself are worked out from it whenever someone asks.
The ideas
The plan
- The plan as a graphProjects, tasks and users, joined by links. A task that holds tasks is a group.
- Statuses and the rules of movingSeven statuses, the moves allowed between them, and what a refusal carries.
- Next and waitingWhat can start now is worked out from the plan on every read, never stored.
- Versions, conflicts and historyChanging an item names the version the change was based on. What was done is kept.
- Problems the plan finds in itselfWhat the plan says when a rightful change leaves something else wrong.
The service
- Users, keys and who can do whatWho a connection acts as, with a key and without, and what each may do.
- Four interfaces, one planMCP, HTTP, the command line and the page: one set of operations behind all four.
- Storage, the data folder and backupsOne SQLite file in one folder, each change stored whole, backups while it runs.
- One service, one folderOne process on one port holds one data folder. A second one is refused.
These ideas are also why the vision reaches further than the product does today. To run it, go to Install and first run. For the exact input of an operation, a setting or a command, see the documentation.