semantic-web-writelisted

# Semantic Web Write Create HTML whose meaning is declared, not merely implied. The output should be useful to a human reader as an HTML artifact and useful to a semantic reader as raw HTML plus a profile. ## Core Contract Every semantic HTML artifact has two coordinated outputs: 1. **HTML document**: readable, navigable, static HTML suited to the source data. 2. **Profile document**: an ALPS profile, or another declared vocabulary when explicitly requested, that defines the meaning of the document's important elements. The HTML must declare the profile with `rel="profile"` and bind meaningful elements to descriptor IDs. Do not rely on headings, labels, color, or visual position as the sole source of meaning. When creating or substantially revising an ALPS profile, use the `alps` skill from `alps-asd/alps-skills` as the ALPS authoring authority when it is available. This skill owns the HTML artifact contract; ALPS profile design, validation, and improvement should follow `alps-skills` rather than duplicating its full guidance here. Validate ALPS profiles with `asd --validate <profile>` before finalizing whenever `asd` is available. ## When To Use HTML Use HTML when the result benefits from layout, visual hierarchy, tables, diagrams, anchors, collapsible sections, lightweight interaction, or sharing as a static page. Stay in Markdown for short conversational replies, code-only answers, terminal instructions, or content that is only a few bullets. For HTML artifact