Engagement information

# Agree the work before it starts.

A practical outline of what needs to be agreed for Go engineering work. The signed proposal or contract defines the terms of an engagement.

## Scope, acceptance and availability

We agree the repositories, toolchain target, deliverables, exclusions, acceptance checks, reviewers and schedule in writing. An enquiry or a suggested package is not acceptance of an engagement or a reserved start date. Changes to the scope need agreement before extra work.

## Fees, payment and cancellation

The written quote states fees, currency, applicable VAT, invoicing and payment milestones. It also sets the notice requirements, any fees for completed or reserved work, and the handling of prepaid amounts if an engagement is changed or cancelled. These details are settled before acceptance.

## Confidentiality and access

If an NDA is needed, discuss it before sending confidential information. Access is limited to the agreed people and systems. Public upstream contributions or case studies require permission; client code and security findings are not published by default.

## Intellectual property and open-source licences

The agreement distinguishes client deliverables, pre-existing tools and third-party code, and records the licences or assignments that apply. Existing open-source licences continue to apply; an engagement does not automatically transfer ownership of Mergo or other upstream projects.

## Release, support and liability

The scope identifies who reviews, deploys and verifies the release, what rollback assistance is included, and any support period. Liability allocation and any limits belong in the signed contract; this page does not create a universal cap or a warranty of production outcomes.

## Security and regulatory boundaries

Technical triage is limited to the agreed systems and questions. It does not certify compliance or guarantee the absence of vulnerabilities. Penetration testing, incident response, emergency availability and production operations require their own explicit arrangements.

## Ask about your requirements

Share your procurement, confidentiality and delivery needs through [the contact page](https://coopanio.com/contact/) . Any governing law or dispute provisions are agreed in the contract rather than assumed from this summary.