---
title: Maintain a recurring decision | SpinForge
url: https://spin-forge.com/programs/living-decisions
description: Commission a revision-aware workflow that keeps models, assumptions, results and evidence connected as inputs change.
---

[All decision programs](https://spin-forge.com/decision-systems) 02 / Decision program

Maintain a recurring decision

# A decision that stays
attached to its conditions.

Commission a revision-aware workflow that keeps models, assumptions, results and evidence connected as inputs change.

[Discuss the scope](https://spin-forge.com/contact?product=program-living-decisions&interface=all&brief=SpinForge+request%3A+Maintain+a+recurring+decision%0A%0APlease+scope+this+customer-specific+engagement.%0A%0ABoundary%3A+The+current+engines+provide+scoped+sessions+and+recovery.+A+complete+multiuser+decision+workspace+and+customer+operating+service+are+integration+deliverables%2C+not+implied+by+CLI%2FMCP+availability.+Reuse+does+not+guarantee+lower+runtime.) [See what you get](https://spin-forge.com/programs/living-decisions?section=workflow-delivery)

Scoped customer program
Selected product access: CLI · MCP · Headless

BUILT FOR

Teams with recurring schedules, allocations, configurations or planning models.

THE CHALLENGE / THE RESPONSE

## Start with what
needs to change.

Agree the business requirement, model and outcome before choosing the implementation.

01

### Changed inputs are not reflected in retained conclusions.

Old results can remain visible after the conditions that justified them have changed.

HOW SPINFORGE HELPS

Bind the source, assumptions and evidence to each solved revision and invalidate unsupported reuse.

02

### Repeated work has no explicit operating policy.

Warm starts, theorem reuse and a live frontier are different forms of continuation.

HOW SPINFORGE HELPS

Use supported continuation where it fits and compare the whole cost with a fresh run.

03

### The recurring process has no accountable owner.

Scheduling, approval, retention and recovery need an operating contract.

HOW SPINFORGE HELPS

Agree those responsibilities and deliver the required integration and review controls.

WHAT YOU GET

## A usable deliverable.
Not just a score.

The written scope names the inputs, implementation, evidence and handover your team receives.

01

### Revision-aware model interface

Allowed mutations, input checks and source identities.

02

### Decision and evidence history

Candidates, flags, assumptions and customer review records for the agreed retention period.

03

### Reoptimization and regression workflow

Supported reuse, invalidation cases, baseline comparisons and repeatable execution.

04

### An operating handover

Scheduling, authorization, exports, recovery and support scope; no automatic production action.

AN ILLUSTRATIVE WORKFLOW

## See the work
in context.

Retain an accepted model and revise its inputs on a defined schedule. Recheck affected claims and present the current decision for approval. Illustrative, not a completed customer deployment.

### A weekly plan evolves without losing provenance.

Illustration of the engagement, not a live solver or a customer case study.

01 / 03

### Retain the baseline

Capture the approved model, required outputs and evidence policy.

QUALIFY THE FIT

## Your requirements.
An explicit scope.

The following inputs and measures guide the proposal and acceptance plan.

### What you bring

- Recurring model and update cadence
- Source and revision ownership
- Evidence, export and retention requirements
- Deployment and response responsibilities

### What we measure

- Current-source result validity
- Correct invalidation and review
- Complete cost of repeated runs
- Recovery and history reconstruction

THE BOUNDARY

The current engines provide scoped sessions and recovery. A complete multiuser decision workspace and customer operating service are integration deliverables, not implied by CLI/MCP availability. Reuse does not guarantee lower runtime.

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) [AgentForge](https://spin-forge.com/agentforge) [StateForge](https://spin-forge.com/stateforge)

HOW TO BUY

## One contract for the agreed work.

Use the existing $15,000 workload assessment or $30,000 focused sprint only when its bounded scope fits. A full program receives a written proposal covering implementation, acceptance, compute and continued software rights. No additional mandatory subscription or duplicate component fees.

[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 a new product?**No. It is a way to commission selected existing products and the customer-specific engineering needed to deliver one defined decision process. The portfolio remains 64 named catalog entries.

**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.

[12 / Customer-specific engineering

### Decision history & reoptimization

Retain the model, assumptions and result history so changed requirements can be checked and re-evaluated without losing their meaning.](https://spin-forge.com/solutions/decision-history) [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)

WHOLE-SYSTEM OPTIMIZATION

## The connection
can change the result.

Joint configuration, decision-sensitive computation, checked memory, useful future options, exact reformulation and evidence-led improvement. Explore the role of every product and agree a matched system evaluation.

[Explore all six connections](https://spin-forge.com/system-synergies) [64-entry interaction map](https://spin-forge.com/system-synergies/product-map)

Customer-specific integration opportunities—not added software entitlements or universal performance claims.
