Open decisions
Ten business policies the feedback brief leaves open. None of them is approved. Every “Provisional” chip in the prototype links to its decision on this page.
These decisions do not block the prototype. Layout and workflow shown on the screens are reversible, so they were built without waiting. What depends on a decision (a calculation, a threshold, a policy, a system boundary) is shown as a configurable setting or as a visibly provisional assumption, and stays that way until management approves it.
Illustrative values are not approved defaults. Amounts, thresholds, percentages and timelines quoted in the review (for example 14 days of inactivity, 60% occupancy, a 12.0M target, any revenue split) are used as test data only. Approval types added in this revision have no monetary limit: the setting reads “limit not set”.
How a dependent value looks on a screen:
The assistant never settles one of these. It may draft a proposal; a named role approves.
| Decision | What has to be decided | Prototype treatment until approved | Requirements | Screens with the chip | Status |
|---|
What approving a decision changes
When management approves a decision, the matching setting loses its “Provisional” chip, the approved value replaces the illustrative one in the shared data, and every screen listed under the decision shows the new value, because screens read it from one place.
Nothing on this page records an approval. The prototype has no sign-in and no stored state; status here changes only when the project team edits the shared data after a real decision.