Build Log
Accountability Should Have One Address
Trust pages help only when their claims agree with the metadata carried by the rest of the site. The v4 accountability release made one identity reusable everywhere.
One entity, many pages
All pages carry the same Schema.org Person entity anchored at #publisher. Editorial nodes refer to that entity by identifier instead of repeating slightly different author descriptions. The name, public website, LinkedIn profile, role, credentials, and corrections contact therefore have one canonical representation.
A generated identity block is safer than hand-editing dozens of JSON-LD fragments. The release applied it to every page, then checked that the character-level representation stayed consistent and that editorial nodes pointed to the correct identifier.
Visible responsibility still matters
Structured data is not a substitute for a human-readable route. The About page explains the editorial approach, the Contact page provides the domain-based address [email protected], and the Editorial Standards describe sources, AI assistance, and corrections.
The site does not turn credentials into a claim of employment-law expertise. Its authority is narrower: transparent data handling, reproducible computation, clear editorial limits, and an identifiable person responsible for fixing errors.
What became standard
Accountability is strongest when public pages, contact routes, author metadata, and off-site profiles reinforce one another. A single generated publisher entity is now the portfolio pattern, with per-domain editorial email and no invented biographical expansion.
This approach can be checked on the About, Contact, and Editorial Standards pages.