Xylora Studios discloses all artificial intelligence tools, generative models, and automated assistance directly within our project handover documentation. Every commercial delivery itemises precisely where synthetic generation, code assistants, or procedural automation were utilised versus human-authored execution.
Studio policy across departments
Xylora Groups LTD operates across three defined departments: Technology, Creative, and Operations & Client Services. Tooling across these departments is audited to ensure clear boundaries between manual craft and automated assistance.
Within the Creative department, generative tools may be deployed for early conceptual ideation, initial mood boards, or texture sampling. Final brand marks, key vector assets, and bespoke typography remain manually crafted to protect client ownership and intellectual property registration. Any synthetic visual elements retained in final artwork are explicitly tagged in the asset ledger.
Within the Technology department, code-assistance models and automated scaffolding tools are used to accelerate boilerplate generation, unit testing, and documentation formatting. Proprietary logic, data architecture, security rules, and production deployment scripts are authored, reviewed, and tested directly by studio engineers.
Operations & Client Services maintains the central record of tools used on every account. They ensure that production methods honour any explicit intellectual property restrictions established during the briefing process.
Sequence of disclosure across project phases
Transparency occurs throughout the project lifecycle rather than as an afterthought at delivery:
1. Briefing and scoping: You define any operational restrictions during the intake phase. When preparing bespoke quotes (delivered within 48 hours of receiving a complete brief), we record agreed technical constraints directly into the scope of work. 2. In-progress reviews: Concept presentations and prototype demonstrations indicate whether draft assets contain synthetic generation. This prevents miscommunication regarding visual or structural direction before final refinement. 3. Final delivery and handover: The delivery package contains a production manifest. This document outlines the toolchain used, specific asset provenance, and notes on whether code or visual assets were produced with machine assistance.
Client opt-outs and restrictions
Certain commercial clients, publishers, and regulated industries operate under strict compliance rules that forbid the use of generative technologies. We accommodate strict zero-AI requirements upon request.
If your organisation requires complete exclusion of generative or machine-assisted tools across both Creative and Technology streams, this must be specified in the initial brief before pricing is confirmed. Excluding standard assistive tools changes production timelines and resource requirements, which will be detailed in your bespoke quote. Package work purchased directly from the packages page utilizes our standard operational toolchain unless an agreement is established prior to commencement.
Deposits are non-refundable once your production slot is held. Before work begins, sums not yet earned are refunded pro rata; after work begins, completed work and booked time are charged. Defects are fixed free of charge within the acceptance window. The full terms are on the Refund Policy page of the main site.
Provenance logs and documentation
The handover manifest delivered at project sign-off provides operational clarity. This record contains:
- The department responsible for the deliverable (Technology or Creative).
- A list of primary software platforms and assistive models utilised during production.
- Clear demarcations of which layers, scripts, or components had machine assistance.
- Attribution and licensing confirmations verifying that no client data was exposed to public training sets.
Failure cases and variances
If an assistive tool is deployed contrary to an agreed zero-AI brief, Operations & Client Services initiates a production variance review. The affected component is quarantined immediately, removed from the release branch or design deck, and remade manually by our personnel during standard working hours (Monday to Thursday, 09:00 to 17:00 GMT).
If a third-party asset or open-source dependency introduced into your build contains undisclosed generative elements, we flag the dependency, assess the intellectual property risk, and provide a replacement path. Operational queries regarding delivery manifests or toolchain permissions can be submitted directly via the Ask Xylo chat on this portal, where our team adheres to a 24-hour first reply target.
Verification checklist
Before completing final milestone sign-off, verify the following:
- Your intake brief recorded any specific bans or limitations on automated or generative tools.
- The delivered production manifest itemises all toolchains used across Creative and Technology.
- Intermediate visual sketches or code drafts match the agreed provenance standards.
- Core intellectual property assets (such as identity marks or core business logic) are marked as human-authored.
- Any residual questions regarding asset authorship have been resolved through the Ask Xylo chat.