Design Partner Pack · September 2026
A bounded pilot, with a defined exit.
Endstop is a pre-product, uncertified hardware gate for model-driven machines. This brief states who fits, what each team contributes, what is delivered, how acceptance works and what a successful pilot can become.
1. Fit, architecture and effort
Page 1 of 2Good pilot fit
- A model or planner genuinely proposes machine commands.
- A concrete physical effect must be bounded.
- A non-production command path can be accessed and modified.
- Recorded commands or a representative bench are available first.
- An engineering owner and risk owner can join the work.
Likely no-fit today
- The only usable boundary is EtherCAT, CANopen or a proprietary bus.
- The failure lies outside authority the gate can observe or refuse.
- Production deployment or a certified safety function is required now.
- No independent stop path or safe-state design is available.
- Machine access or command-path ownership cannot be provided.
Written fit/no-fit decision and draft envelope brief
Recorded or live command stream against agreed cases
Non-production integration and measured latency
Replayable package, limitations and closeout decision
Partner effort by role
| Role | Phase 1 | Paid phases | Owns |
|---|---|---|---|
| Technical sponsor | 60-minute fit call; approve the failure to bound | 30-minute phase gates | Business purpose, budget and stop/go decisions |
| Controls / integration | 2-4 hours; command-path diagram and traces | 0.5-1 day/week during integration | Machine access, wiring change and rollback |
| Safety / risk owner | 2-3 hours; hazard, limits and safe state | Acceptance review and residual-risk record | Risk assessment and application envelope |
| IT / security | Optional 30-minute review | Access and data-transfer approval as needed | Site controls and partner data policy |
| Endstop | Fit analysis and interception proposal | Named technical lead; weekly working session | Gate configuration, implementation and evidence package |
2. Deliverables, acceptance and terms
Page 2 of 2What you receive
- Written fit/no-fit memo and reference architecture for your machine.
- Draft then final machine-specific envelope configuration.
- Evaluation gate for the scoped bench/in-loop period, when hardware fit is confirmed.
- Test matrix, raw captures, latency results and replay instructions.
- Limitations register and assessor-facing evidence summary.
- Written disposition of product requirements raised during the pilot.
Acceptance tests
- Agreed allowed proposals pass without modification.
- Position, rate and timeout challenge cases are refused as specified.
- Reset, stale-input and loss-of-command behavior reaches the agreed state.
- Capture-to-output latency is measured on the partner setup against the SOW budget.
- Each observed decision can be replayed from the retained evidence.
- Useful output and engineering hours are compared with existing controls against agreed acceptance criteria.
Security posture
- No general-purpose OS or network stack on the gate.
- Machine work begins on traces or bench hardware, then moves on-site only by agreement.
- Partner architecture, traces and results remain confidential.
- Data collection is limited to the scoped command, state and verdict record.
- Public disclosure requires written approval.
- Physical attack, side channels and product certification remain outside the pilot claim.
Indicative commercial and IP position - final SOW controls
| Topic | Proposed pilot position |
|---|---|
| Price and commitment | Phase 1 is free. Proposed evaluation pricing is $25,000-$75,000 for agreed work. Physical integration is separately agreed. Each phase may stop independently. |
| Partner IP and data | The partner retains its pre-existing IP, machine architecture, traces, risk assessment and machine-specific envelope inputs. |
| Endstop IP | Endstop retains its pre-existing platform, tools and generalized improvements. Monitor-source access, if required, is governed by a separate evaluation agreement. |
| Pilot deliverables | The partner receives the reports, test data, replay instructions and an internal evaluation right to the delivered configuration; production use is not included. |
| Hardware | Evaluation hardware is loaned for the scoped period unless the SOW states otherwise. It remains pre-product and uncertified. |
| Publication / exclusivity | No partner name, data or result is published without written approval. No field-of-use exclusivity is included unless separately negotiated and paid for. |
After a successful pilot
The closeout names one of three outcomes:
- Stop: return evaluation hardware; retain agreed reports and test data.
- Extend: scope another boundary, machine state or evidence requirement.
- Product path: carry accepted configurations and tests into a follow-on SOW, include one migration workshop, and receive priority access to the next compatible evaluation revision, subject to availability.
Success creates evidence and an integration baseline. It does not silently convert the pilot into production approval or exclusivity.
Procurement starter set
- This pack and the phase plan on the pilot page.
- SOW scope block: boundary, interfaces, dependencies, deliverables, acceptance matrix, schedule, fees and stop condition.
- Mutual NDA and, if needed, monitor evaluation agreement.
- Security / architecture review against the public source, proof record and vulnerability policy.
- Insurance, liability, data handling and site-access terms before machine integration.
The design-partner and monitor evaluation agreements are completed before paid work begins.
Illustrative end-to-end path: a partner supplies a recorded PWM command stream and a “never exceed” joint boundary; Endstop reproduces it on a bench, demonstrates allowed passes and specified refusals, integrates one non-production axis, measures capture-to-output timing, and delivers the configuration, raw traces, replay results and limitations. This is a representative workflow, not a customer case study.
Start with the free fit assessment: machine, model decision, command interface and the physical effect to bound.
Frequently asked questions
What does the free first phase deliver?
Phase 1 produces a written fit or no-fit decision, an interception proposal and draft limits for the selected machine. It establishes whether there is a suitable command interface and a worthwhile problem to evaluate. Later paid phases are separately scoped. See the phase plan.
Does the proposed price include physical integration?
Physical integration is separately agreed. The proposed $25,000–75,000 evaluation range covers the work named in the statement of work, with defined deliverables, acceptance criteria and a stop condition. Each phase may stop independently. The final statement of work controls scope and terms. Review the pricing and phase boundaries.
Who owns the partner data and pilot results?
Under the proposed terms, the partner retains its pre-existing IP, architecture, traces, risk assessment and machine-specific envelope inputs. Endstop retains its platform, tools and generalized improvements. The partner receives agreed reports, test data, replay instructions and an internal evaluation right to the delivered configuration. Public disclosure requires written approval; final agreements govern these terms.
Does a successful pilot authorize production use?
No. The pilot delivers evidence and an integration baseline. Its closeout recommends stopping, extending the evaluation or agreeing a follow-on product path. Production use is not included, and evaluation hardware remains pre-product and uncertified. A successful pilot does not provide production approval or exclusivity. Review the pilot responsibilities and limitations.