What works today and what doesn’t yet

Sometimes your assigned AI can’t do everything you hand over. When that happens, UpServe doesn’t stop the whole thing. It handles what it can first, then shows what was done and what wasn’t.

There are two reasons it can’t

Reason	Example	What happens
Input or a connection is missing	You haven’t uploaded the material yet. An outside service isn’t connected	Your assigned AI asks right there with a chat question or a connection prompt. The task gets a Question or Connection needed label
It can’t be done with today’s features	It needs an integration that doesn’t exist yet, or exact ledger posting	Your assigned AI notes the part it couldn’t do

Missing material or connections are not recorded as “a feature is needed”. Only what really has to be built is kept as described below.

Noting what couldn’t be done

While your assigned AI records the part it couldn’t do, the chat shows “Noting what couldn’t be done”. When it’s recorded, you see the following.

The result also says “Some parts need a feature we don’t have yet”.
A badge such as Not done · Request received appears beside the task. The badge shows only the real state: Request received, In development (only for work that has actually started), or Released.
The result is split into Done and Not done, and the task’s reason label becomes Partly done.
If you press Confirm what’s done, only the done part is accepted and the rest stays as a request.

For work that needs a verified feature, such as exact ledger posting or settlement, UpServe doesn’t do it a rough other way and tell you it’s finished.

Work request board

Press the badge to open the Work request board. For now it is a view-only ranking.

It gathers the parts your assigned AI couldn’t do with today’s features.
The more people blocked by the same feature, the higher it ranks. It shows “Blocked (times) times · (people) people”.
What users wrote is never shown. Only feature names that UpServe organized appear.
If your own request is on it, it is marked Your request. If you have requests that are not on the board yet, the count is shown.
Rankings and progress are not a release date or a promise to build.

Cost

Running a task you handed over uses SU as usual.
A scheduled run uses SU each time it runs once you turn it on.
Adding work or connecting a work screen does not run anything by itself.

Advanced

You don’t need this section for everyday use. Read it only if you want to know what the ranking counts.

Records of what couldn’t be done have kinds. Missing input and missing connections are recorded but are not counted in the ranking’s people and times. Only things that have to be newly built, such as a new command, integration or data structure, are counted for the ranking.
The Work request board address is /work/requests.