Guides and reference
Where does the answer to your question actually live?
Where to find guidance
Three places, and which one you need depends on whether your question is about the product, your configuration, or the screen in front of you.
Runcible Oversing is a configurable institutional platform, so a lot of “how do I” questions have an answer that is specific to how your organisation set it up. Routing you correctly is more useful than a large library that answers a different organisation’s question.
In the application
Anything that depends on what is on your screen right now.
Task-level help lives in Runcible Oversing itself, where it can see the state you are actually in: what kind of object you are looking at, what state it is in, what your role permits, and what the next available action is.
That is not a limitation of this site. It is where the help belongs. A written guide that says “click Approve” cannot know whether you hold the authority to approve, and this class of question is exactly the one where a generic answer is worse than none.
On this site
How the platform is structured, and what implementing it involves.
Product-level explanation lives here, and it is the material that is true regardless of configuration:
- The Operating WorldThe object model: purpose, people, work, authority, resources, memory.
- Authority, Workflow, and PermissionsHow decision rights, workflow state, approval, and delegation work.
- Runcible AI in OversingWhat the intelligence does, and where the validation boundary sits.
- ImplementationWhat a real implementation involves and who does which part.
- What Is Built, What Is NotComponent-level maturity, reviewed quarterly.
From us directly
For now, this is the honest answer to most implementation questions.
Runcible Oversing is at a stage where implementations run with direct involvement from the people who built the system. There is no tiered support organisation behind this today, and What Is Built, What Is Not says so plainly rather than leaving you to discover it.
The practical consequence is good in one way and limited in another: you get the people who know the answer, and there are not many of them.
What is coming here
Written reference is being built from the application’s own help tree, and is not published yet.
The application carries a substantial body of task and administrator help accumulated over years of real use. Some of it describes behaviour that has changed, and some describes behaviour that was designed but never implemented. Publishing it wholesale would put material on a public site that we cannot stand behind — which is precisely the failure the previous version of this site shipped, with dozens of unfinished sections published as if complete.
So it is being inventoried first, and separated into what is implemented and what is not, before any of it appears here.