XiteAI

XiteAI Company Policy.

The XiteAI Code, our working practices and published company policies.

Updated 21 October 2026

About this document

The XiteAI Code and our working practices set out how we make decisions, take responsibility and communicate. Employment agreements and approval processes continue to define spending, access and signing authority.

Product and website policies retain their own scope and terms. Leave, pay, benefits and employment procedures are governed by the applicable agreements and policies.

How we work

The XiteAI Code

The standards we follow in our work.

Raise risks, blockers and mistakes early. Report urgent safety, security, privacy, legal, customer or reliability concerns immediately, even if you do not know the cause or the solution. Say what you know, what remains uncertain and who may be affected. A complete report, proof or ranked list of alternatives is never a condition for raising the alarm. Escalate to another responsible leader if an urgent concern is not acknowledged. Develop options together after the issue is visible.

Question assumptions and test unfamiliar approaches, while respecting real limits. Measurements, logs, reproducible failures, provider documentation, hardware capacity and reasonable engineering judgement can establish a constraint. Mathematical or legal proof is not required for everyday engineering decisions, and no word, including impossible, is banned. Agree a time limit for investigation with the responsible lead. Describe the limits of the evidence and revisit conclusions when facts change. Alternatives must remain lawful and within authorised safety, privacy and security boundaries.

The person who reports a problem helps provide context; reporting does not automatically make them the sole recovery owner. The responsible manager must agree a named owner, bring in the right people, provide time and resources, and explicitly reprioritise other work. An owner coordinates progress and asks for help rather than carrying every task alone. A handover needs an accepting owner and a clear record of what remains. Raise an unsafe workload or missing support promptly.

Give an honest account of progress, uncertainty, failures and customer impact. Do not hide a failing project behind a green status, obscure a defect, blame a vendor without evidence or conceal changes made to repair a mistake. Follow the approved change process; urgent containment uses the authorised incident process, with changes recorded promptly. Review incidents to understand decisions and system conditions, improve the process and prevent recurrence. Distinguish honest mistakes from deliberate misconduct.

The CEO and every manager must welcome good-faith reports, questions, disagreement and admissions of mistakes. Thank people for flagging an issue even when their proposed solution is weak or the concern later proves unfounded. No one may be humiliated, retaliated against or penalised for raising a concern in good faith, including a concern about leadership. Recognise early reporting publicly when appropriate without exposing confidential details or identifying a reporter without permission. Share the recovery burden, resolve resource and priority conflicts, and tell the reporter what happens next. Concerns about a manager may go directly to HR, another responsible leader or the published grievance contact.

Working practices

Decisions, responsibility
and communication.

These practices guide our daily work: making decisions within our responsibilities, keeping people informed and raising concerns early.

  1. Report first; develop options together.

    Describe the issue, its possible impact and what is still unknown. Report urgent concerns immediately. Suggest alternatives when you can, but never delay a report to prepare solutions, a ranking or proof. The responsible lead helps evaluate the next steps.

  2. Decide within your authority.

    Make decisions within the scope agreed with your manager. Record the reason and keep affected people informed. Spending, access, contracts and commitments still follow their approval process; this page sets no financial limit.

  3. Match the review to the risk.

    An internal experiment can be small and unfinished if its limitations are clear. Work reaching customers needs the checks appropriate to its impact. Speed is not a reason to skip privacy, security or required approvals.

  4. Write down repeatable work.

    When a task becomes a process, document the steps, the owner and how to check the result. Make the record usable by the next person and update it when the work changes.

  5. Explain the decision.

    Updates should say what was decided, why, what happens next and where help is needed. Separate decisions already within your authority from requests that still need approval.

  6. Raise problems early.

    Report customer harm, security or privacy incidents, legal risks and serious reliability problems immediately to the responsible lead. Uncertainty is a reason to label what is unknown, not to stay silent. Escalate further if an urgent report is not acknowledged.

  7. Assign ownership and support together.

    Reporting a problem does not assign the reporter every recovery task. The manager agrees an accountable owner, supporting people, resources and time, and reprioritises existing work. The owner coordinates the response. A handover needs an accepting owner and a record of unfinished work.

  8. Make mistakes visible and repair them together.

    Thank the person who reports the issue, contain its impact through the authorised process and share the recovery work. Keep an honest status and record changes; do not conceal patches, obscure failures or blame others without evidence. Review causes and conditions fairly, distinguishing honest mistakes from deliberate misconduct.

  9. Ask when the consequences are unclear.

    A familiar decision can be made within an agreed mandate. If its consequences, permissions or effect on other people are uncertain, ask. Disagreement and raising a concern should be treated on their merits, including when the concern is about leadership.

  10. Match the evidence to the decision.

    Use logs, measurements, reproducible failures, documented service limits and engineering judgement. Agree a time limit for investigation and state uncertainty. A mathematical thesis is not required to raise a practical constraint or recommend stopping an unworkable approach.

  11. Make speaking up safe.

    The CEO and managers must welcome bad news, thank good-faith reporters even when their solution is weak, and provide help and follow-up. Humiliation, retaliation or penalties for good-faith reporting, questions or disagreement are prohibited. Recognise useful reporting without exposing confidential information or identifying a reporter without permission. Concerns about a manager can go directly to HR, another responsible leader or the grievance contact.

Policy documents

Read each policy in full.

Read our published policies for information about privacy, security, product use and support.

Questions and concerns

Use the published contact routes for a policy question, a privacy request, a security report or a support issue. Report urgent problems before a complete explanation is ready. Do not include passwords or unrelated personal information in a report.