[AzielEliab]

Summary

Adds the AZ triad as a design relationship on the Person JSON-LD and the machine files. Visible HTML is unchanged. This PR is not merged.

The triad is one system with three sides:

• AZ-OS, operating-system side: https://github.com/AzielEliab/azos (local ethical overlay; not a kernel)
• Aziel Runtime, MCP side: https://github.com/AzielEliab/aziel-runtime, worker https://aziel-runtime.vibelock.workers.dev/, Glama https://glama.ai/mcp/servers/AzielEliab/aziel-runtime
• The AZInterface, UI-software side: https://github.com/AzielEliab/azinterface, white paper https://www.azielcorpuslibrary.net/record/AZDOC-EB7454682E74

The copy states the design relationship only. It does not claim a mesh-node, a one-click install, or that the integration is live.

Where it lands

• Home and About JSON-LD, plus /person.jsonld: CreativeWork @id https://www.azieleliab.com/#az-triad, named “AZ triad: AZ-OS, Aziel Runtime, The AZInterface”, with hasPart for the three sides and author / creator pointing at https://www.azieleliab.com/#aziel. It is the first workExample.
• The existing AZ-OS, Aziel Runtime, and AZInterface work rows (and the interface white paper) get a short side note and isPartOf that triad id.
• The same note is on /llms.txt, /ai.txt (same brief), /cite.json (az_triad), and /works.json. GitHub crawl aids docs/llms.txt, docs/ai.txt, and docs/cite.json match. /llms-full.txt is still absent.

Other HTML pages do not embed the works list. personNode() without works stays free of the triad.

Checks

• workers/godlock-uk: 266 pass
• tests/test_github_seo.py: pass
• Rendered <body> HTML matches main on /, /AzielEliab, /who, /software, /reason, /donate, and /receipts. /verify differs only by verified_utc.