The agreement, in plain sentences.

Read it, quote it with attribution, link to it. The words, illustrations and code on these pages belong to FeynCode; reproducing a page wholesale as your own is the one use we ask you to skip.

Work begins from a statement of work naming the phases, the deliverables, the fee per phase and the dates. Scope changes are agreed in writing before the work happens, with any effect on dates stated at the same time.

Either side may end an engagement with two weeks’ notice. You pay for work completed; we hand over everything produced to that point.

On payment, the client owns the source code, the infrastructure definitions, the design source and any model weights trained specifically for them. We keep the right to reuse general knowledge, patterns and open-source libraries we wrote along the way.

Kaeonix, Avatar and the tooling around them remain ours and are licensed, not transferred.

Phases are invoiced on completion unless the statement of work says otherwise. Terms are fifteen days.

Anything you tell us about your business stays between us, for three years after the engagement ends and indefinitely for trade secrets and personal data. We publish a case note only with your written agreement, and you approve the numbers in it.

We fix defects in delivered work free of charge for ninety days after each phase. Beyond that, software is warranted to perform as described in the statement of work, and our liability is limited to the fees paid for the phase concerned.

Model outputs are probabilistic. Where a decision carries legal or financial weight, the system is designed to place a person in the path, and that design is part of what you are buying.

Indian law applies, with the courts of Pune, Maharashtra holding jurisdiction. Before either side files anything, we agree to spend thirty days trying to settle the matter in conversation.