Digital Karma Web Changelog

Rendered HTML is now a required federation surface. Every canonical sitemap page must expose the site's DataCatalog and complete catalog Dataset graph, and a generated full-sitemap receipt must prove the coverage before the site can claim v8.2.

• /ai/rendered-schema.json is the seventh required public artifact.
• Every canonical sitemap page must render one stable DataCatalog and every Dataset declared in /ai/catalog.json.
• The primary page entity must connect to the relevant Dataset layer through subjectOf, isPartOf, or an equally explicit relationship.
• The rendered audit records current sitemap and catalog hashes, page counts, expected Dataset count, coverage, failures, and validator identity.
• The manifest advertises the receipt and health reports a passing rendered_schema check only after the full crawl succeeds.
• Nightly enforcement now fails closed when endpoint generation, rendered coverage, inventory reconciliation, or federation conformance fails.

Small, backward-compatible revision. llm.json is back: AI crawlers kept requesting it after v8.0 retired it, so it is now generated from each site's manifest on every build instead of kept by hand. Sibling URLs now use each site's own declared origin. Rolled out to all 155 portfolio properties the same day.

• /llm.json and /ai/llm.json restored as a standard endpoint, derived from /ai/manifest.json, /ai/catalog.json and /ai/health.json in the same build. One portfolio builder writes it for every site, so about twenty different generator implementations publish one shape.
• Generators that deleted llm.json or reported it as retired were corrected; the manifest's endpoints map now lists llm_json and llm_json_ai.
• related_sites now names every member of a site's constellation. The shared rollout had only ever seeded three siblings, so most sites listed 3 or 4 of their real peers.
• Sibling URLs resolve to the origin each site declares (canonical_origins). v8.0 assumed https://www. for every bare domain, which was wrong for 11 of 160 members.
• A site still declaring 8.0 remains a valid, compatible member. The public audit now reports it as a warning, not a failure.
• Amended 2026-09-22: /llms.txt (the llmstxt.org markdown convention) is generated by the same builder on every site. Logs showed it requested 2,116 times in 35 days with roughly 960 answered 404. The protocol version stays 8.1.

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. (Reversed in 8.1: crawlers kept requesting it, so it is now generated from the manifest.)
• 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.

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.

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.

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.

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.

v8.2: rendered Dataset coverage became mandatory

Endpoint files could pass while the HTML pages exposed no Dataset graph. v8.2 closed that gap by requiring every canonical sitemap page to render the site's DataCatalog and complete catalog Dataset inventory, plus a generated /ai/rendered-schema.json receipt from a passing full-sitemap crawl. The manifest, health endpoint, nightly runner, inventory audit, and federation audit now carry that proof through the release process.

v8.1 amended: llms.txt, documentation, download kit builder

The same builder that writes llm.json now writes /llms.txt in the llmstxt.org format on every site, leaving any site-owned llms.txt alone; 160 sites serve one. Warehouse logs for 2026-08-18 to 2026-09-22 showed classified AI crawlers requesting llm.json 205 times against 115 manifest requests, and /llms.txt requested 2,116 times with roughly 960 answered 404. New knowledge-base article explains the decision and its limits. The download kit now ships tools/build-llm-json.php, and the nightly conformance audit checks llms.txt on every site.

v8.1: llm.json restored, full constellation peers

llm.json returned as a generated endpoint because AI crawlers kept requesting it after v8.0 retired it. One builder (build-llm-json.php) now derives /llm.json and /ai/llm.json from each site's manifest nightly. The same release gave every site its full constellation peer list (most had 3 or 4 of 5 to 36 real siblings) and resolved sibling URLs to each site's declared origin. 1,085 endpoint files across 155 sites (plus midlandinfosys.net on its own account) carry protocol_version 8.1, checked nightly by audit-federation.php. See specs/federation-spec-v8.md.

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.

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.

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.

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.

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.

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.

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.

Root discovery rule tightened

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

v7.0 constellation baseline shipped

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

Entity and diagnostics patterns documented

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

v6.1 endpoint baseline stabilized

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