British Noble, British Noble AI and British Noble Press have united, because half the stack was never enough. Learn about the merger →
For Authors · British Noble Press
Pricing & Editions
Instant Site Search
Sign In · Publishing Cloud
Sign In · Author Studio
Free 14-Day Author Studio Sandbox
Start Publisher Sandbox Book a 45-Min Demo
System & Data Architecture

How the Single Title Record powers every publishing workflow.

Inspect the relational schema, isolated compute workers, sales ingestion engine, and regional KMS vaults underneath British Noble.

Four-Tier Cloud Topology

Engineered for ACID ledger integrity and zero-drift production

Layer A · Canonical Relational Core

Normalised Single Title Record Schema

Links Work, Format ISBNs, Contributors, Territorial SalesRights, Production Masters, ONIX SupplyDetails, and Royalty Ledger Entries with ACID transactional integrity.

Layer B · Isolated Compute Workers

Typesetting, 42-Rule Preflight & ONIX Pipeline

Stateless containerised workers run PDF/X-1a ink checks, EPUBCheck 5.0 validation, LUFS audio analysis, and EDItEUR ONIX 3.1.2 compilation in ephemeral sandboxes.

Layer C · Asynchronous Ingestion Engine

Multi-Cadence Sales & FX Normaliser

Idempotent parsers ingest daily retail JSON feeds, weekly EDI wholesale files, and monthly distributor statements with deduplication and period FX rate locks.

Layer D · Open Extensibility

OpenAPI 3.1, Webhooks & Snowflake Share

Every domain object exposes REST endpoints, cursor pagination, idempotency keys, and HMAC-signed webhooks across 42 native enterprise integrations.

Canonical Data Model

Core relational entities inside the Single Title Record

Domain EntityPrimary Key / IdentifierGoverned AttributesDownstream Consumers
Work MasterBN-WRK-UUID + ISWC/ISTCCanonical title, series hierarchy, Thema 1.5, BISAC, imprint partitionAll 7 Platform Capabilities
Edition ManifestationISBN-13 + Crossref DOITrim size, GSM caliper, spine mm, publication date, Codelist 196 tagsProduction Studio & ONIX 3.1.2
Rights & ContractBN-CTR-UUIDISO 3166 territories, advance tranches, sliding escalators, reserve %SalesRights Gate & Royalty Engine
Preflight ArtefactSHA-256 Content DigestPDF/X-1a interior, cover mechanical, EPUB 3.3, 24-bit WAV master108 Retail & POD Channels
Royalty Sub-LedgerBN-JRN-UUID (Immutable)Normalised units, ECB/BoE FX rate, recoupment offset, ERP journal IDNetSuite, SAP, Xero & Author Portal
99.95% Uptime

Multi-AZ High Availability

Active-active web and API nodes across three availability zones with zero-downtime rolling schema migrations.

15m RPO / 2h RTO

Point-in-Time Continuity

Continuous write-ahead log shipping and encrypted cross-AZ snapshots tested semi-annually under CISO supervision.

Zero Lock-In

Open Standards Throughout

Native EDItEUR ONIX 3.1.2, ISO PDF/X-1a, Adobe IDML, W3C EPUB 3.3, MARC21, and OpenAPI 3.1 JSON schemas.

The Single Title Record is our canonical relational schema linking Work, Format ISBN-13s, Contributors, Rights Territories, Production Masters, ONIX 3.1.2 SupplyDetails, and Royalty Ledgers with ACID transactional integrity.

Format editions inherit shared work-level contributors, Thema/BISAC classifications, and territorial locks from the parent Work entity while maintaining format-specific trim, caliper, and pricing attributes.

Every preflight validation job executes inside a stateless, network-isolated container sandbox that mounts the manuscript read-only and destroys ephemeral memory immediately upon completion.

Inbound EDI 852, SFTP CSV, and Apple/Kobo feeds pass through cryptographic file-hash and line-level idempotency keys before posting to immutable period sub-ledgers.

Yes. Enterprise tenants can enable zero-ETL Snowflake Data Share or read-only analytical replicas scoped strictly to their tenant KMS partition.

Every tenant operates under strict row-level security policies paired with dedicated AWS KMS envelope encryption keys for object storage and sensitive financial columns.

Delta-aware XML compilers build partner-specific ONIX 3.1.2 and 3.0 feeds concurrently across distributed queues, sustaining 50,000+ ISBN updates per hour without UI degradation.

Yes. All mutating OpenAPI 3.1 endpoints accept Idempotency-Key headers, return structured RFC 7807 problem details, and expose deterministic X-RateLimit telemetry headers.

Primary transactional stores replicate synchronously across three availability zones within your chosen residency region, delivering a 15-minute RPO, 2-hour RTO, and 99.95% monthly uptime SLA.

Yes. Self-serve bulk export tools output full EDItEUR ONIX 3.1.2 XML, PDF/X-1a/IDML/EPUB/WAV masters, and CSV/JSON royalty ledgers at any time with zero exit fees.

Inspect the Single Title Record live across 11 workspaces.

Launch an authenticated 40-title sandbox or book a technical architecture deep dive with our engineering team.

Publishing an individual flagship book? Explore British Noble Press →
✓ Single Title Record ✓ Zero AI Training on Manuscripts ✓ ONIX 3.1.2 & 108 Global Channels