EA Principles Register

Make sure your technology standards are actually followed.

Most organisations have technology principles written down somewhere. Few can prove those principles actually govern their technology decisions. HelixGate links every principle to the decisions and services it applies to — creating a traceable, auditable chain from standard to implementation.

100%
Traceability
Full
Version history
Any
Framework-agnostic
0
Audit records modifiable
Foundation

What is an EA Principles Register?

An EA Principles Register is a structured record of the guiding standards that govern an organisation's technology decisions. A well-written principle has three components: a clear statement, a rationale explaining why it exists, and implications that tell decision-makers what it means for their choices. Without a governed register, principles exist as a forgotten slide deck — invoked selectively, ignored when inconvenient, and impossible to enforce.

The problem with unconnected principles

  • Principles buried in Confluence pages no one reads during decision reviews
  • No way to know which decisions applied or deviated from a principle
  • No audit trail of who approved a principle or when it was last reviewed
  • Framework mapping is manual and quickly out of date

HelixGate's connected register

  • Surfaced in ADR workflow — relevant principles shown during every review
  • Bidirectional links — from principle to ADRs, and vice versa
  • Versioning — full change history with actor, date, and rationale
  • Lifecycle management — Active, Draft, and Deprecated with governed transitions
Principle Record

A structured record for every principle

Every principle is written with a statement, rationale, and implications — making it actionable, not aspirational.

EAP-012 Technology Domain Active TOGAF
Principle Name
Prefer Open Standards Over Proprietary Lock-in
Statement
"Technology choices shall prefer open, interoperable standards. Proprietary technology may only be adopted where it provides material, documented capability advantage that cannot be achieved through standards-based alternatives."
Rationale
Proprietary technology creates commercial dependency, limits supplier options, and increases long-term migration costs. Open standards reduce exit risk, enable competitive procurement, and support technology portfolio resilience — particularly important in the context of multi-year digital programmes where technology continuity cannot be assumed.
Implications
Architecture Review Board submissions must document whether proposed technologies use open standards. ADRs that adopt proprietary technology must include an exit strategy. Procurement must assess lock-in risk as part of the supplier evaluation. Existing proprietary dependencies must be tracked in the service catalogue with a risk rating.
Owning Architect
Head of Enterprise Architecture
Linked ADRs
Last Reviewed
14 January 2026 — v3
Traceability

From principle to decision to service

HelixGate's cross-module links create a demonstrable chain from written principle to technology decision to running service — auditable from any direction.

Navigate the chain in any direction

From a principle, see every ADR that applied or deviated from it. From an ADR, see which principles it was assessed against. From a service, see which principles govern it via the decisions that shaped its design.

Deliberate deviation is visible too

When an ADR deliberately deviates from a principle with sound rationale, that deviation is captured and linked. Auditors see both the principle, the deviation, and the reasoning.

EA Principle
Prefer Open Standards (EAP-012)
ADR-0008
API Gateway — Applied
ADR-0019
Data Platform — Applied
ADR-0034
Legacy DB — Deviated
Services Governed
API Gateway
Event Bus
Data Warehouse

Illustrative traceability chain — principle to ADRs (applied and deviated) to governed services.

Framework Support

Works with the frameworks your organisation uses

Tag principles to any framework and view them through that framework's lens — or define your own taxonomy.

TOGAF
The Open Group Architecture Framework
Organise principles across the four TOGAF architecture domains: Business, Data, Application, and Technology.
Zach
Zachman Framework
Map principles to the Zachman Framework's six perspectives — Contextual, Conceptual, Logical, Physical, Component, and Operational.
FEAF
Federal Enterprise Architecture Framework
FEAF reference model categories available as framework tags for government and public-sector organisations.
Custom
Your own framework
Define fully custom framework categories, domain labels, and taxonomy levels using the schema editor.
Version Control

Principles evolve — HelixGate tracks every change

Every version of every principle is preserved with who changed it, when, and why. No version can be deleted.

Version Changed by Date Change summary
v3 (current) Head of EA 14 Jan 2026 Expanded implications section to address cloud-native deployments. No change to statement or rationale.
v2 Principal Architect 22 Sep 2025 Updated rationale to reflect multi-cloud procurement strategy. Added reference to supplier concentration risk.
v1 CTO 03 Apr 2025 Initial principle created. Approved by Architecture Review Board at ADB session 2025-Q1.
Who It Serves

Built for teams that set and enforce technology standards

Head of Enterprise Architecture

Own the principles register

Define, version, and govern the organisation's EA principles. Produce traceability reports that demonstrate how principles govern technology decisions across the estate.

Architecture Review Board

Assess decisions against active principles

HelixGate surfaces relevant principles during every ADR review. Panel members assess alignment or deviation and record their notes within the governed workflow.

CTO's Office

Board-level governance evidence

Demonstrate to the board and to auditors that technology decisions are governed by a coherent set of principles — with full traceability from principle to decision to service.

Compliance-ready

Principles governance for regulated organisations.

  • TOGAF ADM — Architecture Principles phase and Architecture Change Management
  • ISO 27001 A.6.1 — Information security roles and responsibilities
  • SOC 2 CC1.1 — Control environment and commitment to governance principles
  • Government Technology Code of Practice — Open standards and interoperability
  • NHS Digital Architecture Standards — Architecture assurance requirements
SOC 2 Type II ISO 27001 Immutable audit log Database-enforced
Technical detail

For architecture teams that want the full picture.

TOGAF architecture domains in HelixGate

For organisations using TOGAF, HelixGate maps principles to the four architecture domains defined by the Architecture Development Method. Each domain acts as a lens for filtering and reviewing principles during ADR and ADB sessions.

🏢

Business Architecture

Principles governing how technology supports business processes, capabilities, and strategic objectives. Includes business agility, process automation, and customer experience.

💾

Data Architecture

Principles governing how data is managed, shared, and protected. Includes data ownership, master data management, privacy-by-design, and data lifecycle governance.

⚙️

Application Architecture

Principles governing how applications are designed, integrated, and maintained. Includes API-first design, modularity, and application lifecycle standards.

🖥️

Technology Architecture

Principles governing infrastructure, platform, and technology choices. Includes cloud-first mandates, open standards, security architecture, and infrastructure as code.

TOGAF ADM integration

TOGAF's Architecture Development Method requires organisations to maintain a governed principles repository as a foundation for architecture work. Without traceable links from principles to decisions, an organisation cannot claim to be practising governed enterprise architecture. HelixGate's traceability chain — from written principle to ARB-approved decision to production service — satisfies this requirement as an automatic byproduct of the governance process rather than a retrospective documentation exercise.

Compliance detail

For regulated industries, the traceability chain satisfies requirements across multiple frameworks. ISO 27001 Annex A.6.1 requires defined roles and responsibilities for information security — HelixGate's principle ownership model maps directly. SOC 2 CC1.1 requires demonstrable commitment to governance principles — the immutable audit trail provides that evidence. For UK government organisations, the Government Technology Code of Practice mandates open standards and interoperability principles that HelixGate can track and enforce through the ADR workflow.

Related Modules

EA Principles connects to everything

EA Principles is most powerful when combined with the ADR workflow and service catalogue — creating the full cross-module traceability chain.

Get Started

Connect your principles to the decisions they govern.

See how HelixGate transforms a static principles document into a live, traceable governance layer — linked to every decision, every service, and every compliance requirement that matters.