The object model
How much of what your organisation knows lives only in the heads of the people currently holding it?
One operating world, not another system of record
Institutions do not lose capacity because they lack systems. They lose it because their systems each hold a fragment.
Runcible Oversing represents an institution as one connected world: purpose, people, work, authority, resources, and history as related parts of the same thing, rather than as six databases that have to be reconciled by whoever is asked the question.
This page is the model. If you recognise your own organisation in it, the rest of the site is about what follows from that.
Purpose and structure
What the institution is trying to do, held where the work can see it.
Organisations, objectives, programmes, projects, and the relationships between them are objects in Runcible Oversing, not headings in a planning document that was accurate in March.
The primary unit is purpose, not department. When objectives change, programmes and the work they justify can be reallocated inside the same operating world — adaptation from inside the platform rather than a reconfiguration project across disconnected tools. The design reason is on Why Built This Way.
The practical consequence is that a piece of work can answer what it is for. Not by convention, and not because someone wrote the objective into the project description, but because the connection is part of the record. When the objective changes, the work that was justified by it is identifiable.
Most organisations can produce a strategy document and a task list. What they cannot usually produce is the line between them.
People and responsibility
Who is accountable is a fact about the institution, not an attribute of a ticket.
People, groups, organisations, customers, and contacts each have a place in the model. So do the things that make a person the right person: their role, their discipline, their skills, their availability, and what they are already committed to.
Responsibility is therefore not a name in an assignee field. It is a relationship between a person, a role, and a matter — which means it survives the person changing jobs, and it can be answered for after the fact.
Work
One work object, however your part of the organisation prefers to run.
Different functions organise work differently, and they are usually right to. A delivery team runs sprints. A service desk runs tickets against response commitments. A studio runs traffic. A capital programme runs a structured breakdown with dependencies and dates. Forcing all four into one discipline is how organisations end up with four systems instead.
Runcible Oversing keeps one underlying work object and lets each part of the organisation operate on it through the discipline that suits it. Work nests as deeply as the real work does. Operating state is uniform across every programme, so “where is this” has the same meaning everywhere.
The result is that a chief executive and a service desk analyst are looking at the same institution, not at two reports that disagree.
Authority
Permission that depends on the state of the matter, not only on the seniority of the person.
Who may act depends on what the thing is, what state it is in, and what role the person holds in relation to it. A claim awaiting regulatory review is not editable by the team that wants to publish it — not by policy, but because the permission does not exist while it is in that state.
Approval and validation are part of the object’s life rather than a parallel process. So is delegation, including who holds authority when the named person is unavailable.
This is also where the boundary with Runcible AI is drawn, and it is important enough to have its own page: Authority, Workflow, and Permissions.
Resources and consequence
What the work costs, attached to the work rather than to a reporting cycle.
Time, capacity, allocation, cost, and obligation are properties of the matter. Forecast sits next to actuals, by person, by programme, by customer, by line of business — so the gap between what was planned and what happened is visible where the work is, not a month later in a different system.
Approved financial relationships — contracts, budgets, rates, invoicing — are represented where implemented. That qualification is deliberate and it is the same one Runcible uses on its corporate site. Financial capability exists in the running application; it is not offered as production-hardened.
History and memory
The part that usually evaporates.
Every institution keeps its decisions. Very few keep the reasoning, the evidence, the objection that was raised and answered, and what happened afterwards — all attached to the thing they concerned.
Runcible Oversing keeps the episode: what the institution intended, what it knew, who was responsible, what authority applied, what was decided and done, what resulted, and what was learned. That connected record is what makes an institution able to answer a hard question in an afternoon instead of a fortnight, and able to not make the same error twice.
It is easier to see than to describe. Follow one matter through all six stages →
Everything above describes capacities of the running application. They are enabled capacities, not measured customer outcomes, and none is offered as evidence of one. What is built, what is partial, and what is not built is set out on What Is Built, What Is Not.