Governance, Principles
& Uptime by Design

Human-centred engineering begins with the person, the task and the conditions in which the work happens. It considers cognitive load, technical literacy, accessibility, privacy and the consequences of failure alongside functional requirements. A technically elegant system that creates avoidable human difficulty is not well engineered.

Agency means more than the presence of a consent button. People should be able to understand what is happening, make meaningful choices and recognise the consequences. Convenience should not be purchased through coercion, unnecessary surveillance or an unexplained loss of control.

People do not share one model of attention, memory, communication or executive function. Neuroinclusive engineering challenges assumptions about how someone should read, remember, prioritise or respond. It should not require a person to disclose a diagnosis to benefit from a clearer interface.

There is no single neurodivergent user profile. Different people may need different levels of detail, different pacing or different ways to navigate a task. Accessibility belongs in the brief and the evaluation criteria, not only in remediation after launch. A preference for clarity is not a lack of capability.

Digital services are used when people are stressed, distracted, vulnerable, frightened or overloaded. Trauma-informed engineering asks how a system behaves when confidence, attention or executive function is reduced. It is an engineering philosophy, not a clinical service, diagnosis or promise of therapeutic benefit.

Security should protect people without making technology hostile to the people it exists to protect. The objective is high assurance, low human burden and human autonomy. Necessary restrictions should be proportionate and explained; a failure should not become an exercise in blame.

Data Owner expresses respect for the person whose life, identity or work is represented by information. It is a Group principle, not a statement that all personal information is property in law. Controller and processor responsibilities, lawful processing and individual rights remain defined by applicable law.

Privacy by design begins by asking whether information is needed at all. Clear purposes, strict minimisation and understandable choices should guide the work. Retention, deletion, access and portability must be assessed against the relevant legal obligations, service context and contractual commitments—not presented as universal guarantees.

The Group connects research, software, infrastructure, investigations and cultural ventures without erasing their different responsibilities. Integration should make accountability clearer, not make it harder to identify who is responsible for a decision. Mandates, decision ownership and conflicts of interest should be explicit.

Client information must not move between operating arms merely because they share a Group identity. Sharing requires an appropriate purpose, authority and safeguards. A Group brand relationship is not, by itself, a description of the contracting entity or the scope of a service.

Investigations require a lawful purpose, appropriate authority and a proportionate scope. Information being accessible does not automatically make every use of it justified. Privacy, relevance and the effect on the people concerned remain part of the judgement.

We reject unlawful surveillance, unauthorised access and the presentation of speculation as fact. Findings should distinguish evidence, inference and uncertainty. Admissibility and legal privilege depend on circumstances and competent legal assessment; neither is promised by technology or a public statement.

Sovereignty concerns informed choices about jurisdiction, suppliers, infrastructure, data and continuity. It is not a claim of immunity from lawful process. Data residency and operational responsibility should be explicit rather than inferred from a supplier’s branding.

We favour maintainability, interoperability and practical exit planning over dependencies created solely to make leaving difficult. Independence is an engineering and commercial objective, not a promise that every dependency can disappear. The costs and limitations of a choice should be understandable before an organisation relies on it.

Resilience is a design responsibility, not a claim that failure is impossible. Operational risk, recovery and the burden on people should be considered before a service is relied upon. A recovery plan that nobody can understand under pressure is not a reassuring document.

Continuity priorities should follow the consequences of disruption. Availability targets, support coverage, recovery objectives, exclusions and remedies belong in the relevant service agreement. They are separate from this Group-level philosophy.

Automated assistance should support informed human judgement, not obscure who is responsible. An output that looks confident is not necessarily correct. The more consequential the decision, the more important it is to understand the limits of the evidence and the need for appropriate review.

Responsible use of intelligence and automation requires attention to privacy, accessibility, error and the people affected. These are governance expectations, not a claim that every service uses artificial intelligence or provides an identical review process.

Research can be discussed through its purpose, field and public significance without publishing a blueprint. The Group’s public materials describe expertise, governance and commercial outcomes. Proprietary research, security implementation and unpublished intellectual property remain outside that public boundary.

Research activity, commercial availability and production suitability are different claims. None should be inferred from the existence of a research programme. Qualified organisations can discuss specialist R&D and strategic licensing through an appropriate qualification and confidentiality process.

News should distinguish what happened, what is evidenced and what the author thinks it means. Commentary is not an incident report, an ambition is not a completed project, and an engineering lesson is not permission to disclose a client’s affairs. A useful retrospective can explain consequences and lessons without revealing protected mechanisms.

Publication dates must come from a confirmed record, not a build timestamp. Material corrections should be explained rather than silently passed off as the original account. Personal recollection should be identified as recollection where precision is not supported. There is no need to manufacture a milestone to fill an archive.

Alt Production Group Limited is registered in England and Wales and based in Manchester. The Group’s public position is grounded in applicable UK law, clear responsibilities and respect for human dignity. Legal requirements and contractual commitments must be assessed for the particular activity and jurisdiction.

Selflessness, integrity, objectivity, accountability, openness, honesty and leadership provide a useful standard for responsible conduct. These principles are a basis for scrutiny, not a claim of certification or an exemption from scrutiny. Openness about responsibility can coexist with justified protection of personal information, client confidences and intellectual property.