# Ship a working system with a defined boundary.

> Production delivery should be a controlled commitment around real requirements, not a promise that every unknown will disappear during development.

Canonical URL: https://marmation.com/engagements/production-implementation/

## The decision

Where does the production commitment begin and end?

A milestone needs real requirements, accessible dependencies and acceptance evidence. Define deployment, change and handover responsibilities alongside the software boundary.

## The situation behind the request

A prototype has shown value and the client needs it integrated with actual applications. Data sources, access controls, user workflows and releases now become the dominant work.

## Where the obvious solution falls short

When scope is vague, teams either absorb unplanned changes or fight over acceptance. A system can be technically impressive yet fail operationally if the handover and support plan are missing.

## How we would approach the work

Break the work into agreed milestones with requirements, dependencies, architecture, acceptance tests, deployment responsibility and change control. Use a qualified project team according to complexity.

## What the engagement may include

- Implementation backlog and architecture decision records.
- Product engineering, integrations and quality assurance.
- Security/AI evaluation and operational observability as scoped.
- UAT, deployment, documentation, handover and warranty boundaries.

## The choices worth making explicitly

Fixed-price work suits sufficiently specified outcomes. Evolving products may need a reserved-capacity model. We should not confuse contract type with overall delivery maturity.

## What we would test before calling it ready

Check functional, negative and permission cases; rollback, rate/cost controls and the actual release path. Contractual acceptance must correspond to evidence, not a polished demo.

## A sensible first step

Bring the current specifications and architecture constraints so the first production milestone can be scoped responsibly.

## Related reading

- [Clarity before code. Accountability through delivery.](https://marmation.com/approach/)
- [A reliable system is designed for more than the ideal case.](https://marmation.com/approach/engineering-quality/)
- [Build the capability. Keep control of what belongs to you.](https://marmation.com/approach/client-ownership/)