How VANRY Transformed from 'Testing Cost' to 'Fixed Budget'
First: The VANRY in the testing phase should not be 'taken seriously'.
If you look at VANRY from the early stages of system construction, it is almost destined to be underestimated. Because at this stage, the way it appears determines that it will not be considered a 'core variable'. Testing, trial runs, verifying stability, and checking if the interface is usable—there is only one logic behind these actions: first, see if it can run. At this stage, VANRY's role is more like a 'necessary but replaceable cost item'; it exists but is not important. The team's focus is on whether the system throws errors, whether calls are smooth, and whether uncontrollable problems arise under continuous operation, rather than the settlement itself. This is also why many people have the illusion at this stage: VANRY seems to be just a transitional consumable with no stickiness. But if you truly understand how systems are adopted, you will know that this 'neglect' is actually a necessary stage for all infrastructure before entering the main process.