Changelog

Digital Karma Web Changelog

A public timeline of what changed, when it changed, and which version is current.

Current Version: v8.0 | Last Updated: 2026-07-29T00:00:00Z | Authority: specs/federation-spec-v8.md

Current Direction

Clear public files matter.

This principle remains part of the current Digital Karma direction.

Simple placement rules matter.

This principle remains part of the current Digital Karma direction.

Open scoring and upgrade paths matter.

This principle remains part of the current Digital Karma direction.

Portable file patterns matter.

This principle remains part of the current Digital Karma direction.

Release history should stay easy to trace.

This principle remains part of the current Digital Karma direction.

Website Audit

Apply the latest release to a real site

The changelog explains what changed. The website audit shows how those changes affect a live public implementation right now.

Public URLs only. Instant results. Exportable upgrade package.

Release Timeline

v8.0 Current 2026-07-29

Real architectural upgrade, not a terminology change: a shared, config-driven generation engine and schema graph replace per-site reinvention across the portfolio. Rolled out to 90 of ~99 properties the same day.

  • Every generated file now carries protocol_version plus a real supported_since/deprecated_after/removed_after lifecycle, instead of an implicit "probably still fine."
  • llm.json retired in favor of the same fields already in ai/manifest.json -- one identity document instead of two that can drift apart.
  • related_sites is now resolved from a single canonical constellations.json export, not hand-typed per site -- this closed real drift on six sites, most with only 1 of 8-16 real siblings actually listed.
  • robots.txt on NaturalHerbLibrary.com is now generated from endpoint visibility declarations, retiring a standing bug where the site's own manifest advertised a public API that robots.txt blocked.
  • A shared reference template (vps-scripts/build-federation-template.php) now backs the portfolio-wide rollout script; two long-protected "master template" hosts were safely unprotected and folded into normal rollout.
  • Constellation, as used elsewhere in this portfolio (krisada.com's directory groupings -- healthcare-ai-longevity, one-mouse-marketing, etc.), continues unchanged. This release does not touch that term or its meaning.
v8.0-terminology-draft Superseded, never rolled out 2026-05-11

Retired 2026-07-29. This was a proposed public-facing rename (Federation -> Constellation, Sites -> Stars, cross-site links -> Alignments, endpoints -> Signals) with no architecture change behind it. It was never actually implemented anywhere in the portfolio -- no site's code, docs, or copy adopted Stars/Alignments/Signals language. Superseded by the real v8.0 above; kept here only as a record of a direction that was considered and dropped, not a release that shipped.

  • Public copy transitions from Federation to Constellation terminology. (proposed only, never adopted)
  • Individual sites are Stars. Groups are Clusters. Cross-site links are Alignments. (proposed only, never adopted)
  • Machine-readable endpoints are Signals. The global index is the Constellation Map. (proposed only, never adopted)
  • The federated architecture powering the system remains fully intact.
v7.1 Superseded 2026-04-21

Portable installer release that tightened root discovery rules and made agent-led upgrades repeatable across the portfolio.

  • Formalized that robots.txt must live at /robots.txt.
  • Formalized that sitemap.xml must live at /sitemap.xml.
  • Clarified that root sitemap.xml is canonical and /ai/sitemap.json is optional only.
  • Established v7.1-DigitalKarma.md as the portable installer brief for repo-to-repo upgrades.
v7.0 Baseline 2026-04-13

Major constellation revision that expanded the required machine-readable surface and introduced structured topology patterns.

  • Expanded the required artifacts from 4 to 6 by adding federation.json and llm.txt.
  • Renamed the entry badge from Karma Bronze to Karma Certified.
  • Introduced formal Starter, Certified, Pro, and Elite compliance tiers.
  • Added the 4-stage constellation mapping pattern and entity file conventions.
v6.1 Legacy 2026-03-30

Pre-constellation structured AI endpoint baseline used across the early portfolio sites.

  • Established the original four-file endpoint pattern.
  • Used looser, less formal network relationship metadata.
  • Did not yet require llm.txt or constellation topology documents.

Public Ledger

A shorter public-facing changelog lives here. The fuller article version is also available in the resource library.

Release 2026-07-29

v8.0 architectural upgrade shipped portfolio-wide

Shared generation engine, protocol/lifecycle stamping, and single-sourced constellation membership rolled out to 90 of ~99 properties. Real drift found and fixed along the way on six sites (NaturalHerbLibrary.com, AgeBetterToday.com, RealSEOLife.com, krisada.com, and two AS400 IBM System sites), most with related_sites missing the majority of their real constellation siblings. See specs/federation-spec-v8.md for the full spec.

Correction 2026-07-29

v8.0-terminology-draft (2026-05-11) retired

The prior 'v8.0 Constellation terminology rollout' entry below described a Stars/Alignments/Signals renaming that was never actually implemented anywhere in the portfolio. Marked superseded rather than deleted, so the historical record shows a direction that was considered and dropped, not silently erased.

Role Assignment 2026-06-08

Krisada.com designated Galaxy Historian and Librarian

Krisada.com formally designated as the Galaxy Historian and Librarian of the Digital Karma Constellation network. As the oldest domain in the portfolio with the deepest SEO lineage, it preserves institutional memory, chronicles the federation's history across versions, and anchors authority signals for the wider galaxy. Documentation across the federation updated to reflect this role.

Release 2026-05-11

v8.0-terminology-draft: Constellation terminology proposed (superseded 2026-07-29, never rolled out)

A public wording shift was proposed, but it never shipped. The real v8.0 release was the later architecture update on 2026-07-29.

Maintenance 2026-04-22

Public-facing v7.1 compliance content refreshed

Aligned the public standards, developer docs, registry copy, and machine-readable indexes so the live site now consistently reflects the v7.1 root discovery rules and current constellation version.

Tooling 2026-04-22

Constellation audit application introduced on DigitalKarmaWeb.com

Added a public validator and upgrade planner that can audit remote public sites against the latest standard, generate action plans, and export upgrade packages.

Release 2026-04-21

v7.1 portable installer published

Published v7.1-DigitalKarma.md as the portable installer brief and aligned README and authority docs around the new root placement rules.

Spec 2026-04-21

Root discovery rule tightened

Clarified that robots.txt and sitemap.xml belong at the root and should not be relocated into /ai/.

Release 2026-04-13

v7.0 constellation baseline shipped

Introduced the 6 required artifacts, formal compliance tiers, constellation mapping, and the modern Digital Karma badge naming.

Spec 2026-04-13

Entity and diagnostics patterns documented

Added /entities/ JSON-LD conventions and /ai/diagnostics.json as part of the higher-tier maturity path.

Legacy 2026-03-30

v6.1 endpoint baseline stabilized

Four core AI endpoints formed the original structured baseline before the dedicated constellation layer existed.

Keep Reading