One governed action. A measurable manual bottleneck.
The Nikxius design-partner evaluation tests whether connecting a governance decision to an exact external action reduces costly manual work. Deployment is one part of the evaluation. The result must include a measured comparison of the work before and after Nikxius.
Proposed evaluation: US$15,000, one supported Kubernetes Deployment rollback, one named nonproduction environment, up to four weeks. Establish the workflow baseline, technical acceptance criteria and economic measurement before installation. Fees, access, support and exit terms require a separate written agreement.
A useful partner has a recurring agent action, a platform owner, an accountable reviewer and enough comparable events to measure approval, investigation, exception or evidence work. Frequent deployments alone do not establish that governance reconstruction is the bottleneck.
What we will test
Register a remediation agent and its exact version. Attach relevant evaluation evidence. An accountable reviewer approves defined limits, from which an administrator issues bounded Runtime authority. The agent requests the supported rollback, the Runtime applies its exact operation and approval checks, and the observed outcome remains connected to the original decision.
Then introduce a material version change. The unapproved version must not inherit earlier authority. Attach relevant evidence, review the change and issue a new decision before permitting a new operation.
The rollback references an earlier committed Nikxius operation on the same tenant, target and native Deployment UID. It reverses the permitted before-and-after image relationship with a new root task, grant, operation and outcome. A committed image change does not restore databases or establish application health.
Read the governance and Runtime architecture, exact rollback scope and security boundary.
Measure active work, including the work added
| Measure | Baseline and Nikxius-assisted workflow |
|---|---|
| Comparable event | Workflow type, trigger, date, outcome and evidence sources |
| People and steps | Participants, approvals, manual evidence gathering, investigations and exceptions |
| Active human effort | Person-minutes spent on each event; separate elapsed duration |
| Workflow change | Steps removed, automated, preserved and newly added |
| Ongoing burden | Integration, operation, maintenance and repeated work |
| Volume and costs | Customer-supplied event volume and, when available, explicit cost assumptions |
Relevant events × active minutes removed per event = human work released. Compare like-for-like events and preserve their source records. Label measurements as observed, customer supplied, calculated or illustrative. Released time is not automatically cash savings; do not monetize it without explicit customer assumptions or omit added operating cost.
The study tests a hypothesis. Nikxius has no measured customer savings to claim.
Keep the strongest current workflow in the comparison
Inventory, identity, evaluations, source control, incident systems and existing governance products retain their responsibilities. Document how the current stack connects the decision to the action and resolves uncertainty. If GitOps owns desired state, establish the correct writer before introducing another one.
Compare both approaches on the same resources, permission boundaries and failure cases. Nikxius must justify its integration and operating burden through an observed improvement. If the existing stack meets the contract economically, retain it.
Technical acceptance
| Scenario | Required result |
|---|---|
| Missing, expired or revoked decision/authority | Refuse new eligible dispatch |
| Unapproved changed agent version | Require its own review and decision; no inherited grant |
| Wrong operation, resource or native state | Refuse the altered action rather than silently rebasing approval |
| Required review or expired required exception | Prevent new eligible dispatch until appropriately addressed |
| Duplicate or lost response | Preserve exact operation identity and explicit uncertainty |
| Crash around dispatch | Retain the original attempt and distinguish unclaimed from possibly dispatched work |
| Missing causal history | Keep UNKNOWN instead of inferring success from the current image |
| Evidence inspection | Connect system, version, evaluation, reviewer, authority, action and outcome |
Reconciliation reads retained native evidence. UNKNOWN can remain indefinitely. A new governance decision does not erase uncertain execution history. Direct writes through other credentials remain outside Nikxius; the evaluation must inspect the actual credential boundary.
What has been exercised locally
The 25 September 2026 combined suite passed 581 tests, zero failed and zero skipped. The governed native demo used real disposable Kubernetes and PostgreSQL, fixture identities and fixture evaluations. It exercised rollback, lost-response recovery, changed-version refusal, reapproval and signed export.
Read the public verification summary. These are local engineering results, not customer installation, security certification, production acceptance or proof of economic value. Vendor-specific live ingestion connectors and remote workload version attestation are not implemented.
Four weeks to a decision
| Stage | Work and evidence |
|---|---|
| Scope and baseline | Name the action, owners, governance decision, manual bottleneck, comparison workflow and measurement method |
| Install and connect | Deploy the customer-controlled Node/PostgreSQL, integrate identity and enroll the exact operation; record integration effort |
| Exercise and measure | Run comparable events and failure cases; retain active person-minutes, outcomes, exceptions and evidence |
| Decide | Assess technical behavior and net work removed; continue under separate terms, scope another evaluation or stop |
Customer administrators own installation, network/TLS, secret custody, native controls and emergency access. Nikxius provides scoped integration support and a written result. The first enquiry needs descriptions, not credentials or private production manifests.
Dated installation references
The online Runtime guide, 20-page PDF and optional document ZIP describe the September 15–16 Runtime evaluation. They remain useful background; they predate the governance layer and do not constitute the current governed installation package.
Governance-aware source and setup instructions are supplied separately for an agreed evaluation. Downloading a guide creates no agreement and does not authorize production use.
Bring the action and the manual work
Describe the recurring operation, the current write path, the decision that permits it, the people involved and the step you want to remove. Name a technical owner and a decision date.
Show us the action, or email founder@nikxius.com. An enquiry creates no commitment.