--- title: Decision history & reoptimization | SpinForge url: https://spin-forge.com/solutions/decision-history description: Retain the model, assumptions and result history so changed requirements can be checked and re-evaluated without losing their meaning. --- [All solution workflows](https://spin-forge.com/workflows) 12 / Maintain & learn Decision history & reoptimization # Keep the decision. Update the conditions. Retain the model, assumptions and result history so changed requirements can be checked and re-evaluated without losing their meaning. [Discuss the scope](https://spin-forge.com/contact?product=workflow-decision-history&interface=all&brief=SpinForge+request%3A+Decision+history+%26+reoptimization%0A%0APlease+scope+this+customer-specific+engagement.%0A%0ABoundary%3A+UNISOLVE+supports+scoped+sessions+and+checked+theorem+reuse%2C+not+full+live+reoptimization+for+every+engine.+The+customer-facing+workspace%2C+retention+system+and+integration+require+engineering.+Preserving+a+lower+bound+does+not+make+a+prior+witness+feasible+under+new+restrictions.) [See what you get](https://spin-forge.com/solutions/decision-history?section=workflow-delivery) Customer-specific engineering Selected product access: CLI · MCP · Headless BUILT FOR Teams that repeatedly plan, configure, allocate or evaluate the same system as its inputs and requirements change. THE CHALLENGE / THE RESPONSE ## Start with what needs to change. Agree the business requirement, model and outcome before choosing the implementation. 01 ### Yesterday’s evidence is being used for today’s model. A changed objective, resource bound or requirement can invalidate an earlier conclusion. HOW SPINFORGE HELPS Bind decisions to the exact solved revision and identify which earlier claims must be checked again. 02 ### The same work is repeated without a clear reuse policy. A saved answer is not the same as a reusable theorem or a retained search frontier. HOW SPINFORGE HELPS Use supported warm starts, sessions and checked bound reuse where their preservation conditions hold; measure total cost rather than assume a speedup. 03 ### No one can reconstruct why the decision was approved. Source versions, assumptions, candidate outputs and operating decisions can live in separate places. HOW SPINFORGE HELPS Define a retained decision record, export path, customer approval step and revision history appropriate to the deployment. WHAT YOU GET ## A usable deliverable. Not just a score. The written scope names the inputs, implementation, evidence and handover your team receives. 01 ### A revision-bound decision record Model and data identity, assumptions, candidates, checking status and customer review history. 02 ### A supported update workflow Permitted changes, invalidation rules and repeatable solve/check operations. 03 ### A reuse assessment A clear distinction between reusable evidence, warm starts and work that must be recomputed. 04 ### A retention and handover plan Storage, export, deletion, access and operating responsibilities agreed with the customer. AN ILLUSTRATIVE WORKFLOW ## See the work in context. A planning team adds resource restrictions to a previously solved model. The workflow checks whether a parent bound still applies, finds or checks a current-model witness, and preserves the new revision. Illustrative, not a customer case study. ### Capacity changes, but the history remains clear. Illustration of the engagement, not a live solver or a customer case study. 01 / 03 ### Capture the accepted baseline Retain the approved source, data, result and required evidence. QUALIFY THE FIT ## Your requirements. An explicit scope. The following inputs and measures guide the proposal and acceptance plan. ### What you bring - Original and revised models - Allowed mutation and ownership rules - Required evidence, retention and access policies - Recurring schedule and accepted baseline ### What we measure - Correct invalidation after changes - Current-model feasibility and result interpretation - Complete reoptimization cost versus fresh execution - Reconstruction and export of decision history THE BOUNDARY UNISOLVE supports scoped sessions and checked theorem reuse, not full live reoptimization for every engine. The customer-facing workspace, retention system and integration require engineering. Preserving a lower bound does not make a prior witness feasible under new restrictions. PRODUCTS TO CONSIDER Select only what the task needs. These links do not assert a completed combined integration. [UNISOLVE](https://spin-forge.com/unisolve) [GARMO UCS](https://spin-forge.com/ucs) [GarmoForge](https://spin-forge.com/garmoforge) [StateForge](https://spin-forge.com/stateforge) [AgentForge](https://spin-forge.com/agentforge) HOW TO BUY ## Define one useful deployment. Commission a bounded scope using the existing engineering and licensing options. A $15,000 workload assessment or $30,000 focused sprint may fit a limited first step; neither includes the entire workflow by default. Larger implementation, operated delivery, compute and continuing rights are agreed separately. [Single-workload assessment — $15,000](https://spin-forge.com/engineering/workload-assessment) [Focused sprint — $30,000](https://spin-forge.com/engineering/focused-sprint) [All prices & rights](https://spin-forge.com/pricing) PREPARE YOUR SCOPE Delivery preference Preferred access What should this accomplish? What would make the result acceptable? Prepared locally. Review and send through your email application. No model upload, job execution, payment or account activation occurs here. BEFORE YOU BUY ## A few useful distinctions. **Is this another product or an already integrated application?**This is a customer-specific engagement using selected existing products. The model, adapters, user experience and acceptance work are scoped before delivery. It does not add another underlying product or establish a completed integration. **Can we use our existing software?**Yes, where its input, output and operating interfaces fit the agreed scope. A custom adapter may be required. The existing tools do not have to be replaced to qualify one useful component. **How are price and acceptance set?**Agree the baseline, required result, explicit limits, delivery capacity and acceptance tests before work begins. Existing software rates remain unchanged; engineering already included in a larger scope is not charged twice. RELATED WORK ## A complete process. Selected capabilities. These workflows can be scoped together or independently. [10 / Customer-specific engineering ### Executable decision models Turn business rules, objectives and approved data into a reusable decision model your team can inspect and run.](https://spin-forge.com/solutions/decision-modeling) [17 / Customer-specific engineering ### Workload-fit evidence Build a permissioned record of which engine and configuration fit a supported workload, including the cost of preparation and checking.](https://spin-forge.com/solutions/workload-fit) [Explore all 17 solution workflows](https://spin-forge.com/workflows)