Product tour
Understand the small set of objects you will use to operate OpenNeko.
The core objects
| Object | What it is | Why it matters |
|---|
| Thread | A conversation with the AI and its working context. | Keeps a request, evidence, files, actions, and decisions together. |
| Briefing | A prepared view of important changes and exceptions. | Gives operators a starting point without asking the same questions every day. |
| Watcher | A recurring check over approved data. | Surfaces a condition when it appears instead of waiting for someone to look. |
| Workflow | A repeatable sequence of AI and system steps. | Turns a recurring operating routine into controlled execution. |
| Action request | A proposed change outside the conversation. | Applies policy, approval, and audit before the change happens. |
| Skill | Instructions and resources for doing a job well. | Makes useful operating knowledge reusable and reviewable. |
One operating loop
- OpenNeko observes approved data or receives a request.
- The AI explains the condition and gathers relevant evidence.
- It recommends a decision or prepares an action.
- Policy decides whether the action may run, needs approval, or must remain human-only.
- The result and evidence remain attached to the work for review.