School contribution
Suitable rack or equipment space, electricity, connectivity, physical access arrangements and a named institutional contact, subject to technical assessment.
Proposed Host School Partnership
A structured pilot model for schools that want to build AI capability early.
The business plan proposes an AI Innovation Host School programme in which ZYK-owned infrastructure may be placed at a participating school under a formal agreement. The school would provide an appropriate physical and network environment; the agreement would define capacity, educational benefits, data boundaries, responsibilities and exit arrangements.
Proposed exchange
ZYK contribution
Agreed partnership hardware, deployment and management, together with defined teacher-development and student AI-literacy activities.
Contract-defined capacity
A host relationship would not automatically give the school unrestricted use of all installed capacity. School workloads, reserved resources, service levels and any non-school workloads must be defined in the agreement.
Potential host-school benefits
Teacher & IT development
Priority professional development for teaching and technical teams according to the agreed programme.
Student programmes
AI-literacy workshops, competitions or project-based activities tied to the school’s educational goals and safeguarding requirements.
Controlled sandbox
Potential bounded capacity for demonstrations and experimentation without treating the production environment as an unrestricted test system.
Preferential terms
The business plan contemplates preferential pricing on selected ZYK services. Any discount, included capacity or benefit would be stated in the final agreement.
Host-school recognition
A future ZYK recognition programme may identify participating institutions after programme criteria, permissions and branding rules are formally defined.
Evidence before expansion
A pilot can help both parties measure real demand, operational requirements and educational value before considering dedicated capacity or a larger deployment.
Required boundaries
Hosting infrastructure does not blur ownership, data or responsibility.
| Question | Required principle before launch |
|---|---|
| Who owns the hardware? | Unless a separate purchase agreement states otherwise, the proposed model keeps title to partnership hardware with ZYK. |
| Who owns school data? | The host arrangement does not transfer ownership of school content, records or institutional data to ZYK. |
| Can ZYK use school data for unrelated work or model training? | Not by default. Any processing must have an agreed purpose, authorised access path and documented data terms. Unrelated commercial reuse should be prohibited unless separately and lawfully agreed. |
| Can other workloads run on hosted hardware? | Only if the contract, technical design and applicable requirements permit them. Workloads must be isolated and must not create unauthorised access to school data or undermine reserved school capacity. |
| Who can physically or remotely access the system? | Named roles, authentication, logging, maintenance windows and emergency-access procedures should be documented. |
| Who pays for electricity, network and facilities? | The commercial agreement must allocate these costs and define any minimum environmental or connectivity requirements. |
| What service level does the school receive? | Reserved capacity, support hours, maintenance, uptime objectives and escalation must be contractual rather than implied by the presence of equipment. |
| What happens when the partnership ends? | Notice, data export/deletion where applicable, credential revocation, hardware removal or purchase options, and final access records should be defined in advance. |
| Does ZYK recognition equal regulatory certification? | No. Any future Host School or ZYK safety recognition would be a private ZYK programme, not government accreditation or regulatory approval. |
This remains a proposed commercial model from the August 2026 business plan. No host-school relationship should be represented as active until a partner, technical design and signed agreement exist. Data processing, security, liability, insurance, electricity, access, service levels, termination and regulatory obligations require formal review for each deployment.