Session
Agent session blocks and inline metadata. data-session, data-mode, data-session-meta.
When an agent's work is published to the web — a daily log, a changelog, a status page — the session structure carries meaning. ASW provides vocabulary for the session block itself, the mode it ran in, and the inline metadata fragments that appear throughout: timestamps, commit hashes, model identifiers.
These components were built for Trentuna's agent infrastructure. A session is a bounded unit of work — it has a mode (autonomous or interactive), a duration, and a provenance trail. The vocabulary makes that structure visible in rendered HTML without custom CSS.
Session block
data-session renders a contained block for a single session entry — monospace font, card background, left accent border. Use it in logs, changelogs, or anywhere a session appears as a discrete item in a list.
Built vault/session.html, closed ASW #45 milestone items.
<div data-session>
<span data-mode="autonomous">autonomous</span> · session 42 · 2026-04-02 07:41 UTC
<br>Built vault/session.html, closed ASW #45 milestone items.
</div>The block is deliberately minimal — no title, no header, no chrome. The content is whatever the agent wrote. Structure is imposed by convention, not markup.
Mode
data-mode marks whether a session ran autonomously or interactively. The attribute changes text colour — blue for autonomous, accent (orange) for interactive — making mode scannable in a log.
Live examples:
<span data-mode="autonomous">autonomous</span>
<span data-mode="interactive">interactive</span>Use inline, inside a data-session block, or anywhere mode context is needed without a surrounding block.
| Value | Colour | Meaning |
|---|---|---|
autonomous |
Accent blue | Beat-triggered, no human in the loop |
interactive |
Accent (orange) | Human-directed session, active conversation |
Session metadata
data-session-meta renders inline metadata — timestamps, model identifiers, commit hashes — in monospace muted text. It reduces visual weight while keeping the information present. Use it inside session blocks or anywhere provenance metadata appears alongside content.
Live example: Last updated 2026-04-02 07:41 UTC · model claude-sonnet-4-6
Last updated <span data-session-meta>2026-04-02 07:41 UTC</span>
· model <span data-session-meta>claude-sonnet-4-6</span>Pairs naturally with data-hash (see Wikilinks) for commit provenance:
2026-04-02 · a3f7b2c
<span data-session-meta>2026-04-02</span> · <span data-hash>a3f7b2c</span>Composed: session log
The three attributes compose naturally into a session log — each entry is a data-session block with mode and metadata inline:
Built vault/session.html. Processed inbox. Updated daily handoff.
A-Team org structure, team onboarding, forge-native architecture.
Forgejo focus command, Nadja and Buio onboarding to A-Team.
<div data-session>
<span data-mode="autonomous">autonomous</span>
<span data-session-meta>2026-04-02 07:41 UTC · session 42 · </span><span data-hash>97d7433</span>
<br>Built vault/session.html. Processed inbox. Updated daily handoff.
</div>
<div data-session>
<span data-mode="interactive">interactive</span>
<span data-session-meta>2026-04-01 14:22 UTC · session 41 · </span><span data-hash>dd15f9b</span>
<br>A-Team org structure, team onboarding, forge-native architecture.
</div>Reference
| Attribute | Values | Element |
|---|---|---|
data-session |
(boolean) | div, article, any block |
data-mode |
autonomous · interactive |
Any inline or block element |
data-session-meta |
(boolean) | Any inline element |