The Three-Entity Architecture: Author, Publisher, Company

Why Three Entities?

Most independent authors operate as a single entity: their name covers everything — the writing, the publishing, the business. This is simple but limiting.

We separated into three entities for structural reasons:

1. atharvainamdar.com — The Author

Purpose: Personal brand and creative identity. Contains: 68 readable books, editorial content (27 articles), daily archive (204+ pages), first lines, revision theater, emotional map, living bibliography, reading guides. Schema type: Person with sameAs linking to all platforms.

The author entity owns the creative output. Everything on this site is authored content — books, editorial articles, archive material.

2. thebooknexus.com — The Publisher

Purpose: Publishing operations and catalog. Contains: 1,194-book catalog with search and filter, author profiles, editorial blog (8 articles), submission portal, services, news. Schema type: Organization (Publisher) with @id linking.

The publisher entity manages the commercial catalog. It acquires rights, assigns ISBNs, manages metadata, and maintains the public catalog. Separating publisher from author allows The Book Nexus to potentially publish other authors in the future.

3. bogadoga.com — The Company

Purpose: International business infrastructure. Contains: Company information, publishing division overview, founder profile, vision, blog (company articles). Schema type: Organization (Corporation) with parentOrganization linking.

The company entity provides the business structure — UK incorporation, international presence, and the infrastructure that supports both the author and the publisher.

How Schema Linking Works

The three entities are connected through Schema.org markup:

• Person (Atharva Inamdar) has `worksFor` → BogaDoga Ltd
• Person has `affiliation` → The Book Nexus
• Organization (The Book Nexus) has `parentOrganization` → BogaDoga Ltd
• Organization (BogaDoga) has `founder` → Person
• All three share cross-linked `sameAs` and `@id` references

This creates a knowledge graph that Google, Bing, and AI systems can parse to understand the relationships between all three entities.

The Result

Three professional websites. Three distinct identities. One connected knowledge graph. Zero confusion about who does what.

This is not complexity for its own sake. This is structure that enables scale.

— BogaDoga Strategic Operations