Proposal for discussion; not an executed agreement, invoice or customer-system authorization. The price and buying motion remain commercial hypotheses. Customer-specific scope, parties and legal terms require written agreement before work begins.
Scope and commercial structure
One kubernetes.deployment.rollback_image.v1 operation family: one enrolled Deployment container in one named nonproduction environment, restoring an explicitly permitted immutable prior image tied to an earlier committed operation. Establishing the controlled prior image operation is part of the test fixture, not a license for general cluster mutation.
| Item | Proposed term |
|---|---|
| Duration | Four weeks after written scope, prerequisites and owners are confirmed. |
| Fee | US$15,000; tax treatment and invoice deadlines agreed in the signed order. |
| Signing installment | US$7,500. |
| Acceptance installment | US$7,500 at the milestone agreed before work starts. |
| Annual credit | Fees actually paid, up to US$15,000, credited to the first annual subscription signed within 90 calendar days of recorded evaluation completion. |
Annual scope and price are separate. The proposed credit is not a cash refund, automatic renewal or obligation to purchase. Access delays and scope changes require a recorded schedule decision; no unlimited extension or engineering is implied.
Delivery and responsibilities
| Week | Joint outcome |
|---|---|
| 1 | Confirm blocked workflow, current controls, native baseline, access, security reviewer and decision criteria. |
| 2 | Install the bounded operation, identity/grant/review integration and operator path. |
| 3 | Run stale-state, duplicate, crash and response-loss cases on both approaches; record recovery burden. |
| 4 | Customer engineer runs acceptance; deliver findings, evidence and a dated continuation/native-stack decision. |
Nikxius, led by Nikhil Sood, supplies installation/integration assistance, the agreed test procedure, documented findings and operator handover. Support channel, working hours, escalation owner and response expectations are recorded in the order; 24/7 coverage and an SLA are not included by implication.
The customer supplies a platform owner, technical operator, security reviewer, approved nonproduction environment, identity/secret/database setup, current-stack configuration and operational evidence. Secrets remain in approved channels. The customer retains change authority, backups and emergency responsibility.
Acceptance and end state
Before signing, name the milestone owner, ten-case acceptance contract, evidence and any measured improvement threshold. An honest unresolved outcome can be technically correct; it must still be operationally acceptable. Disputed/unmet criteria, remedies and termination follow the signed agreement, not assumptions in this offer.
Close with one dated choice: annual/production scoping, additional bounded evaluation, native stack sufficient, or no continuation. Production access, new operations, bespoke integrations, compliance certification and public customer references require separate approval. No endorsement or right to publish customer data is implied.
Contracting identity, authorized signatories, license, confidentiality, data handling, IP, liability, tax, termination and governing law remain to be confirmed through appropriate legal review. This scope supersedes the older image-change starting offer for new evaluations while retaining its proposed price and credit structure.