# SCHEDULE A — RESERVED FUNCTIONALITY DOMAINS

**To the ENCY Extension Store Publishing Policy**
**Version 1.0 — Effective 1 November 2026**

---

## A.1 How to read this Schedule

| Column | Meaning |
|---|---|
| **Domain** | The capability area reserved under Section 4 of the Policy |
| **Gating Entitlement** | The ENCY licence an end user must hold for a Gated Extension in this Domain to install and run |
| **Class** | **Core** — integral to the Platform, not separately licensed. **SLM** — Separately Licensed Module |
| **Gated publication** | Whether third-party Extensions may be published in this Domain under Policy para 4.3 |

**Gated publication = Yes** means: you may publish here, provided your Extension verifies the end user's Entitlement through the SDK and refuses to run without it.

**Gated publication = No** means: this Domain concerns licensing integrity, safety enforcement or output verification, where a third-party implementation would defeat the control itself. These are closed to substitution but open to complementary Extensions under Policy para 4.4.

---

## A.2 Reserved Functionality Domains

### Machining strategy and toolpath generation

> **Tiered Domains.** Milling is licensed in tiers of increasing capability. Per Policy para 4.2, a Gated Extension must verify the Entitlement for the tier **at which the capability is licensed**, not a lower tier. An end user holding 3-Axis Mill does not thereby qualify for a multi-axis Extension.

| # | Domain | Gating Entitlement | Class | Gated publication |
|---|---|---|---|---|
| A-01a | 2.5D and 3-axis milling toolpath generation | ENCY Mill (3-Axis) | SLM | **Yes** |
| A-01b | 3+2 / positional (indexed) multi-axis milling | ENCY Mill 3+2 | SLM | **Yes** |
| A-01c | Simultaneous 4- and 5-axis milling toolpath generation | **ENCY 5-Axis Mill** | SLM | **Yes** |
| A-03 | Turning and mill-turn toolpath generation | ENCY Turn / Mill-Turn | SLM | **Yes** |
| A-04 | Wire and die-sink EDM toolpath generation | ENCY EDM | SLM | **Yes** |
| A-05 | Nesting and material-utilisation optimisation | ENCY Nesting | SLM | **Yes** |
| A-06 | Additive and hybrid deposition path generation | ENCY Additive | SLM | **Yes** |
| A-07 | Feature recognition driving automated strategy selection | *bundled with the relevant strategy Entitlement* | Core | **Yes** |

### Robotics

| # | Domain | Gating Entitlement | Class | Gated publication |
|---|---|---|---|---|
| A-08 | Robot offline programming, reach and singularity handling | ENCY Robot | SLM | **Yes** |
| A-09 | Robot kinematic solving and axis-configuration optimisation | ENCY Robot | SLM | **Yes** |
| A-10 | External axis and positioner coordination | ENCY Robot | SLM | **Yes** |

### Machine model, post-processing and output

| # | Domain | Gating Entitlement | Class | Gated publication |
|---|---|---|---|---|
| A-11 | Machine kinematic model definition and digital twin construction | MachineMaker | SLM | **Yes** |
| A-12 | Post-processor generation engine and controller output formatting | *bundled with the relevant strategy Entitlement* | Core | **Yes** — see note A.3(a) |
| A-13 | Machining simulation, material removal and collision detection | ENCY Simulation | SLM | **No** — see note A.3(b) |
| A-14 | NC output verification and safety validation pipeline | — | Core | **No** |

### Platform, licensing and cloud

| # | Domain | Gating Entitlement | Class | Gated publication |
|---|---|---|---|---|
| A-15 | Licensing, activation, entitlement enforcement and anti-tamper | — | Core | **No** |
| A-16 | Extension Store distribution, payment and update mechanism | — | Core | **No** |
| A-17 | ENCY Clouds account, tenancy and data-synchronisation services | ENCY Clouds | SLM | **No** |
| A-18 | ENCY Tuner machining-parameter optimisation | ENCY Tuner | SLM | **Yes** |
| A-19 | ENCY Hyper high-performance computation services | ENCY Hyper | SLM | **Yes** |
| A-20 | Core geometry kernel, modelling and CAD import/translation | *bundled with Platform licence* | Core | **Yes** |

---

## A.3 Domain notes

**(a) A-12 — Post-processors.** Individual post-processors for specific machines and controllers are **expressly open** to third-party development and publication, gated on the relevant strategy Entitlement. What is reserved is the post-processor *generation engine* and its integration with the output-verification pipeline, not the writing of posts. Post-processor development is a category we actively encourage.

**(b) A-13 — Simulation.** Extensions that *consume* simulation results, that visualise, report or analyse them, or that add simulation of additional physical phenomena are permitted under Policy para 4.4. What is reserved is the collision-detection and material-removal engine on which end-user safety decisions are made, because ENCY carries safety responsibility for that determination toward the end user and the machine tool builder.

**(c) A-07, A-12, A-20 — Core with bundled gating.** These Domains are integral to the Platform rather than separately priced. A Gated Extension in these Domains is gated on the Entitlement for the strategy or Platform licence to which the capability belongs, as identified at pre-submission determination under Policy para 4.6.

---

## A.4 Not reserved — expressly open

For the avoidance of doubt, the following are **not** Reserved Functionality and require no gating:

- Individual post-processors for specific machine and controller combinations
- Tool libraries, cutting-data libraries, material databases and tool-holder catalogues
- Fixture, workholding and clamping component libraries
- Machine-tool and robot model definitions for specific machines
- Import, export and translation of third-party file formats
- Integration with ERP, MES, PLM, PDM, tool-management, measurement and inspection systems
- Reporting, documentation, setup-sheet, costing and quotation generation
- Workflow automation, batch processing, scripting and job orchestration
- Third-party slicer integrations
- User-interface customisation, localisation and accessibility tooling
- Training, tutorial, template and sample-project content
- Analytics, dashboards and shop-floor monitoring
- Probing, measurement and in-process inspection routines that consume Platform output

---

## A.5 Worked examples

The following illustrate the operation of Section 4 of the Policy. They are indicative and do not override a determination given under para 4.6.

| Proposed Extension | Outcome | Basis |
|---|---|---|
| Third-party 5-axis toolpath engine from an established CAM technology vendor, sold separately, requiring an ENCY 5-Axis Mill licence to run | **Permitted as Gated Extension** | Domain A-01c, gated on ENCY 5-Axis Mill. Extends choice for licensed users; base licence still required |
| **The same engine, gated on ENCY Mill (3-Axis) so that a 3-axis customer obtains 5-axis capability** | **Refused** | Policy para 4.2, capability tiers — gating must be on A-01c, the tier at which the capability is licensed |
| Extension gated on 3-Axis Mill that outputs simultaneous multi-axis toolpaths under a "surface finishing" description | **Refused** | Policy para 4.5(a)+(b); substance over description. Capability determines the tier, not the listing title |
| Extension gated correctly on 5-Axis Mill, but shipped with a configuration option, licence key or documented procedure enabling multi-axis output on a 3-axis Entitlement | **Refused; treated as licensing-system circumvention** | Policy paras 3(c), 4.2; Agreement cl. 5.3 |
| **Compliant 3-axis Extension on the Store, with the 5-axis engine supplied to the same customer directly by the Developer as a Platform plug-in** | **Breach of Policy para 4.9** | Anti-circumvention. Component relies on the Platform SDK to deliver A-01c output without the Entitlement |
| Developer's standalone CAM product, sold independently, not integrating with the Platform | **Permitted; outside the Policy** | Policy para 4.9, scope limitation. Competition outside the Platform is unrestricted |
| Nesting engine requiring an ENCY Nesting licence, offering a different optimisation approach | **Permitted as Gated Extension** | Domain A-05 |
| Nesting engine running on a base Platform licence, marketed as "no need for the ENCY Nesting module" | **Refused** | Policy para 4.5(a)+(b)+(c) |
| Extension that prepares sheet layouts for import into ENCY Nesting | **Permitted, no gating** | Policy para 4.4(a) |
| Post-processor for a specific Fanuc-controlled 5-axis machine | **Permitted, no gating** | Schedule A.4; note A.3(a) |
| Post-processor that reconstructs simultaneous multi-axis motion from 3-axis toolpath data at output stage | **Refused** | Substance falls within A-01c; the capability, not the component type, determines the Domain |
| Extension that replaces the ENCY licence check with its own key server | **Refused; immediate action** | Policy paras 3(c), A-15, 6.3(a) |
| Extension adding thermal-distortion simulation on top of ENCY Simulation output | **Permitted, no gating** | Policy para 4.4(b); note A.3(b) |
| Extension providing an independent collision-detection engine presented as the basis for run/no-run decisions | **Refused** | Domain A-13, gated publication No |
| ERP connector pushing job data into ENCY and returning cycle-time estimates | **Permitted, no gating** | Policy para 4.4(d) |

---

## A.6 Amendment

This Schedule may be amended in accordance with Policy para 4.7, which sets the applicable notice period by reference to the effect of the amendment:

| Type of amendment | Notice |
|---|---|
| Clarifying — renaming, restructuring or subdividing an existing Domain by capability tier, without extending scope | **15 days** |
| Recording a capability for which a distinct Entitlement was already being issued | **15 days** |
| Extending scope to a capability not previously reserved and not separately licensed | **30 days** |

Amendments remain subject to the transition protections in Policy para 4.7 and to any determination given under Policy para 4.6.

**Version history**

| Version | Date | Change |
|---|---|---|
| 1.0 | 1 November 2026 | Initial publication |

---

*End of Schedule A v1.0*