note
This rune is part of @refrakt-md/plan. Install with npm install @refrakt-md/plan and add "@refrakt-md/plan" to the plugins array in your refrakt.config.json.
Decision Log
An aggregation rune that renders a chronological list of architecture decision records from the entity registry. Supports filtering by status and sorting by date or ID. The rune produces a sentinel that the pipeline resolves with real decision data.
All decisions (newest first)
{% decision-log sort="date" /%}<section data-rune="collection">
<meta data-field="collection-type" content="decision">
<meta data-field="collection-filter" content="">
<meta data-field="collection-sort" content="-date">
<meta data-field="collection-group" content="">
<meta data-field="collection-limit" content="">
<meta data-field="collection-fields" content="">
<meta data-field="collection-layout" content="table">
<meta data-field="collection-group-display" content="headings">
<meta data-field="collection-empty" content="">
<meta data-field="__collection-sentinel" content="true">
<meta data-field="collection-body" content="# Decision
{% link href=$item.url %}**{% $item.id %}** — {% $item.data.title %}{% /link %}
# Status
{% humanize($item.data.status) %}
# Date
{% date($item.data.date) %}
">
<div data-name="items"></div>
</section>| Decision | Status | Date |
|---|---|---|
| Accepted | Jun 11, 2026 | |
| Accepted | Jun 11, 2026 | |
| Proposed | Jun 11, 2026 | |
| Accepted | Jun 11, 2026 | |
ADR-014 — Responsive surface sizing and project-definable frame presets | Accepted | Jun 10, 2026 |
ADR-013 — Bento levels — an author-defined heading→footprint ladder | Accepted | Jun 7, 2026 |
ADR-011 — Compose plan aggregation at the template level, not via postProcess injection | Proposed | May 26, 2026 |
| Proposed | May 26, 2026 | |
| Proposed | May 1, 2026 | |
| Accepted | Apr 5, 2026 | |
ADR-008 — Framework-native component interface for rune overrides | Accepted | Apr 4, 2026 |
| Proposed | Apr 3, 2026 | |
ADR-005 — Replace the useSchema / Type class system with plain rune identifiers | Accepted | Apr 2, 2026 |
| Proposed | Mar 25, 2026 | |
| Proposed | Mar 18, 2026 | |
ADR-007 — Use CSS custom properties for tint token injection | Accepted | Mar 11, 2026 |
| Accepted | Feb 15, 2026 | |
| Accepted | Jan 20, 2026 | |
| Accepted | ||
ADR-002 — Framework Readiness Investigation: Next.js, Eleventy, Nuxt | Accepted | |
| Accepted | ||
| Proposed |
<section class="rf-collection" data-type="decision" data-layout="table" data-rune="collection" data-density="full">
<div data-name="items" class="rf-collection__items rf-collection__items">
<table class="rf-collection__table">
<thead>
<tr>
<th>Decision</th>
<th>Status</th>
<th>Date</th>
</tr>
</thead>
<tbody>
<tr data-entity-id="ADR-016">
<td>
<p>
<a href="">
<strong marker="**">ADR-016</strong>
—
Frontmatter-declared registry entities
</a>
</p>
</td>
<td>Accepted</td>
<td>Jun 11, 2026</td>
</tr>
<tr data-entity-id="ADR-017">
<td>
<p>
<a href="">
<strong marker="**">ADR-017</strong>
—
Data-bound sandboxes: registry-fed visualizations
</a>
</p>
</td>
<td>Accepted</td>
<td>Jun 11, 2026</td>
</tr>
<tr data-entity-id="ADR-018">
<td>
<p>
<a href="">
<strong marker="**">ADR-018</strong>
—
Canonical layout vocabulary
</a>
</p>
</td>
<td>Proposed</td>
<td>Jun 11, 2026</td>
</tr>
<tr data-entity-id="ADR-019">
<td>
<p>
<a href="">
<strong marker="**">ADR-019</strong>
—
Bento belongs in core, not the marketing plugin
</a>
</p>
</td>
<td>Accepted</td>
<td>Jun 11, 2026</td>
</tr>
<tr data-entity-id="ADR-014">
<td>
<p>
<a href="">
<strong marker="**">ADR-014</strong>
—
Responsive surface sizing and project-definable frame presets
</a>
</p>
</td>
<td>Accepted</td>
<td>Jun 10, 2026</td>
</tr>
<tr data-entity-id="ADR-013">
<td>
<p>
<a href="">
<strong marker="**">ADR-013</strong>
—
Bento levels — an author-defined heading→footprint ladder
</a>
</p>
</td>
<td>Accepted</td>
<td>Jun 7, 2026</td>
</tr>
<tr data-entity-id="ADR-011">
<td>
<p>
<a href="">
<strong marker="**">ADR-011</strong>
—
Compose plan aggregation at the template level, not via postProcess injection
</a>
</p>
</td>
<td>Proposed</td>
<td>May 26, 2026</td>
</tr>
<tr data-entity-id="ADR-012">
<td>
<p>
<a href="">
<strong marker="**">ADR-012</strong>
—
Collapse backlog and decision-log onto collection
</a>
</p>
</td>
<td>Proposed</td>
<td>May 26, 2026</td>
</tr>
<tr data-entity-id="ADR-010">
<td>
<p>
<a href="">
<strong marker="**">ADR-010</strong>
—
Unified root-level refrakt config
</a>
</p>
</td>
<td>Proposed</td>
<td>May 1, 2026</td>
</tr>
<tr data-entity-id="ADR-009">
<td>
<p>
<a href="">
<strong marker="**">ADR-009</strong>
—
Framework-agnostic theme packages
</a>
</p>
</td>
<td>Accepted</td>
<td>Apr 5, 2026</td>
</tr>
<tr data-entity-id="ADR-008">
<td>
<p>
<a href="">
<strong marker="**">ADR-008</strong>
—
Framework-native component interface for rune overrides
</a>
</p>
</td>
<td>Accepted</td>
<td>Apr 4, 2026</td>
</tr>
<tr data-entity-id="ADR-006">
<td>
<p>
<a href="">
<strong marker="**">ADR-006</strong>
—
Post-identity-transform hook for rune packages
</a>
</p>
</td>
<td>Proposed</td>
<td>Apr 3, 2026</td>
</tr>
<tr data-entity-id="ADR-005">
<td>
<p>
<a href="">
<strong marker="**">ADR-005</strong>
—
Replace the useSchema / Type class system with plain rune identifiers
</a>
</p>
</td>
<td>Accepted</td>
<td>Apr 2, 2026</td>
</tr>
<tr data-entity-id="ADR-103">
<td>
<p>
<a href="/runes/plan/examples">
<strong marker="**">ADR-103</strong>
—
Lazy entity registration for large sites
</a>
</p>
</td>
<td>Proposed</td>
<td>Mar 25, 2026</td>
</tr>
<tr data-entity-id="ADR-015">
<td>
<p>
<a href="/runes/plan/decision">
<strong marker="**">ADR-015</strong>
—
Adopt content model validation at parse time
</a>
</p>
</td>
<td>Proposed</td>
<td>Mar 18, 2026</td>
</tr>
<tr data-entity-id="ADR-007">
<td>
<p>
<a href="/runes/plan/decision">
<strong marker="**">ADR-007</strong>
—
Use CSS custom properties for tint token injection
</a>
</p>
</td>
<td>Accepted</td>
<td>Mar 11, 2026</td>
</tr>
<tr data-entity-id="ADR-101">
<td>
<p>
<a href="/runes/plan/examples">
<strong marker="**">ADR-101</strong>
—
Use pipeline hooks instead of plugin system
</a>
</p>
</td>
<td>Accepted</td>
<td>Feb 15, 2026</td>
</tr>
<tr data-entity-id="ADR-102">
<td>
<p>
<a href="/runes/plan/examples">
<strong marker="**">ADR-102</strong>
—
BEM naming convention for identity transform
</a>
</p>
</td>
<td>Accepted</td>
<td>Jan 20, 2026</td>
</tr>
<tr data-entity-id="ADR-001">
<td>
<p>
<a href="">
<strong marker="**">ADR-001</strong>
—
Astro Readiness Investigation
</a>
</p>
</td>
<td>Accepted</td>
<td></td>
</tr>
<tr data-entity-id="ADR-002">
<td>
<p>
<a href="">
<strong marker="**">ADR-002</strong>
—
Framework Readiness Investigation: Next.js, Eleventy, Nuxt
</a>
</p>
</td>
<td>Accepted</td>
<td></td>
</tr>
<tr data-entity-id="ADR-003">
<td>
<p>
<a href="">
<strong marker="**">ADR-003</strong>
—
Markdoc Feature Gap Analysis for Refrakt
</a>
</p>
</td>
<td>Accepted</td>
<td></td>
</tr>
<tr data-entity-id="ADR-004">
<td>
<p>
<a href="">
<strong marker="**">ADR-004</strong>
—
Plan Site Theme Resolution
</a>
</p>
</td>
<td>Proposed</td>
<td></td>
</tr>
</tbody>
</table>
</div>
</section>Accepted decisions only
{% decision-log filter="status:accepted" sort="date" /%}<section data-rune="collection">
<meta data-field="collection-type" content="decision">
<meta data-field="collection-filter" content="status:accepted">
<meta data-field="collection-sort" content="-date">
<meta data-field="collection-group" content="">
<meta data-field="collection-limit" content="">
<meta data-field="collection-fields" content="">
<meta data-field="collection-layout" content="table">
<meta data-field="collection-group-display" content="headings">
<meta data-field="collection-empty" content="">
<meta data-field="__collection-sentinel" content="true">
<meta data-field="collection-body" content="# Decision
{% link href=$item.url %}**{% $item.id %}** — {% $item.data.title %}{% /link %}
# Status
{% humanize($item.data.status) %}
# Date
{% date($item.data.date) %}
">
<div data-name="items"></div>
</section>| Decision | Status | Date |
|---|---|---|
| Accepted | Jun 11, 2026 | |
| Accepted | Jun 11, 2026 | |
| Accepted | Jun 11, 2026 | |
ADR-014 — Responsive surface sizing and project-definable frame presets | Accepted | Jun 10, 2026 |
ADR-013 — Bento levels — an author-defined heading→footprint ladder | Accepted | Jun 7, 2026 |
| Accepted | Apr 5, 2026 | |
ADR-008 — Framework-native component interface for rune overrides | Accepted | Apr 4, 2026 |
ADR-005 — Replace the useSchema / Type class system with plain rune identifiers | Accepted | Apr 2, 2026 |
ADR-007 — Use CSS custom properties for tint token injection | Accepted | Mar 11, 2026 |
| Accepted | Feb 15, 2026 | |
| Accepted | Jan 20, 2026 | |
| Accepted | ||
ADR-002 — Framework Readiness Investigation: Next.js, Eleventy, Nuxt | Accepted | |
| Accepted |
<section class="rf-collection" data-type="decision" data-layout="table" data-rune="collection" data-density="full">
<div data-name="items" class="rf-collection__items rf-collection__items">
<table class="rf-collection__table">
<thead>
<tr>
<th>Decision</th>
<th>Status</th>
<th>Date</th>
</tr>
</thead>
<tbody>
<tr data-entity-id="ADR-016">
<td>
<p>
<a href="">
<strong marker="**">ADR-016</strong>
—
Frontmatter-declared registry entities
</a>
</p>
</td>
<td>Accepted</td>
<td>Jun 11, 2026</td>
</tr>
<tr data-entity-id="ADR-017">
<td>
<p>
<a href="">
<strong marker="**">ADR-017</strong>
—
Data-bound sandboxes: registry-fed visualizations
</a>
</p>
</td>
<td>Accepted</td>
<td>Jun 11, 2026</td>
</tr>
<tr data-entity-id="ADR-019">
<td>
<p>
<a href="">
<strong marker="**">ADR-019</strong>
—
Bento belongs in core, not the marketing plugin
</a>
</p>
</td>
<td>Accepted</td>
<td>Jun 11, 2026</td>
</tr>
<tr data-entity-id="ADR-014">
<td>
<p>
<a href="">
<strong marker="**">ADR-014</strong>
—
Responsive surface sizing and project-definable frame presets
</a>
</p>
</td>
<td>Accepted</td>
<td>Jun 10, 2026</td>
</tr>
<tr data-entity-id="ADR-013">
<td>
<p>
<a href="">
<strong marker="**">ADR-013</strong>
—
Bento levels — an author-defined heading→footprint ladder
</a>
</p>
</td>
<td>Accepted</td>
<td>Jun 7, 2026</td>
</tr>
<tr data-entity-id="ADR-009">
<td>
<p>
<a href="">
<strong marker="**">ADR-009</strong>
—
Framework-agnostic theme packages
</a>
</p>
</td>
<td>Accepted</td>
<td>Apr 5, 2026</td>
</tr>
<tr data-entity-id="ADR-008">
<td>
<p>
<a href="">
<strong marker="**">ADR-008</strong>
—
Framework-native component interface for rune overrides
</a>
</p>
</td>
<td>Accepted</td>
<td>Apr 4, 2026</td>
</tr>
<tr data-entity-id="ADR-005">
<td>
<p>
<a href="">
<strong marker="**">ADR-005</strong>
—
Replace the useSchema / Type class system with plain rune identifiers
</a>
</p>
</td>
<td>Accepted</td>
<td>Apr 2, 2026</td>
</tr>
<tr data-entity-id="ADR-007">
<td>
<p>
<a href="/runes/plan/decision">
<strong marker="**">ADR-007</strong>
—
Use CSS custom properties for tint token injection
</a>
</p>
</td>
<td>Accepted</td>
<td>Mar 11, 2026</td>
</tr>
<tr data-entity-id="ADR-101">
<td>
<p>
<a href="/runes/plan/examples">
<strong marker="**">ADR-101</strong>
—
Use pipeline hooks instead of plugin system
</a>
</p>
</td>
<td>Accepted</td>
<td>Feb 15, 2026</td>
</tr>
<tr data-entity-id="ADR-102">
<td>
<p>
<a href="/runes/plan/examples">
<strong marker="**">ADR-102</strong>
—
BEM naming convention for identity transform
</a>
</p>
</td>
<td>Accepted</td>
<td>Jan 20, 2026</td>
</tr>
<tr data-entity-id="ADR-001">
<td>
<p>
<a href="">
<strong marker="**">ADR-001</strong>
—
Astro Readiness Investigation
</a>
</p>
</td>
<td>Accepted</td>
<td></td>
</tr>
<tr data-entity-id="ADR-002">
<td>
<p>
<a href="">
<strong marker="**">ADR-002</strong>
—
Framework Readiness Investigation: Next.js, Eleventy, Nuxt
</a>
</p>
</td>
<td>Accepted</td>
<td></td>
</tr>
<tr data-entity-id="ADR-003">
<td>
<p>
<a href="">
<strong marker="**">ADR-003</strong>
—
Markdoc Feature Gap Analysis for Refrakt
</a>
</p>
</td>
<td>Accepted</td>
<td></td>
</tr>
</tbody>
</table>
</div>
</section>Sorted by ID
{% decision-log sort="id" /%}<section data-rune="collection">
<meta data-field="collection-type" content="decision">
<meta data-field="collection-filter" content="">
<meta data-field="collection-sort" content="id">
<meta data-field="collection-group" content="">
<meta data-field="collection-limit" content="">
<meta data-field="collection-fields" content="">
<meta data-field="collection-layout" content="table">
<meta data-field="collection-group-display" content="headings">
<meta data-field="collection-empty" content="">
<meta data-field="__collection-sentinel" content="true">
<meta data-field="collection-body" content="# Decision
{% link href=$item.url %}**{% $item.id %}** — {% $item.data.title %}{% /link %}
# Status
{% humanize($item.data.status) %}
# Date
{% date($item.data.date) %}
">
<div data-name="items"></div>
</section>| Decision | Status | Date |
|---|---|---|
| Accepted | ||
ADR-002 — Framework Readiness Investigation: Next.js, Eleventy, Nuxt | Accepted | |
| Accepted | ||
| Proposed | ||
ADR-005 — Replace the useSchema / Type class system with plain rune identifiers | Accepted | Apr 2, 2026 |
| Proposed | Apr 3, 2026 | |
ADR-007 — Use CSS custom properties for tint token injection | Accepted | Mar 11, 2026 |
ADR-008 — Framework-native component interface for rune overrides | Accepted | Apr 4, 2026 |
| Accepted | Apr 5, 2026 | |
| Proposed | May 1, 2026 | |
ADR-011 — Compose plan aggregation at the template level, not via postProcess injection | Proposed | May 26, 2026 |
| Proposed | May 26, 2026 | |
ADR-013 — Bento levels — an author-defined heading→footprint ladder | Accepted | Jun 7, 2026 |
ADR-014 — Responsive surface sizing and project-definable frame presets | Accepted | Jun 10, 2026 |
| Proposed | Mar 18, 2026 | |
| Accepted | Jun 11, 2026 | |
| Accepted | Jun 11, 2026 | |
| Proposed | Jun 11, 2026 | |
| Accepted | Jun 11, 2026 | |
| Accepted | Feb 15, 2026 | |
| Accepted | Jan 20, 2026 | |
| Proposed | Mar 25, 2026 |
<section class="rf-collection" data-type="decision" data-layout="table" data-rune="collection" data-density="full">
<div data-name="items" class="rf-collection__items rf-collection__items">
<table class="rf-collection__table">
<thead>
<tr>
<th>Decision</th>
<th>Status</th>
<th>Date</th>
</tr>
</thead>
<tbody>
<tr data-entity-id="ADR-001">
<td>
<p>
<a href="">
<strong marker="**">ADR-001</strong>
—
Astro Readiness Investigation
</a>
</p>
</td>
<td>Accepted</td>
<td></td>
</tr>
<tr data-entity-id="ADR-002">
<td>
<p>
<a href="">
<strong marker="**">ADR-002</strong>
—
Framework Readiness Investigation: Next.js, Eleventy, Nuxt
</a>
</p>
</td>
<td>Accepted</td>
<td></td>
</tr>
<tr data-entity-id="ADR-003">
<td>
<p>
<a href="">
<strong marker="**">ADR-003</strong>
—
Markdoc Feature Gap Analysis for Refrakt
</a>
</p>
</td>
<td>Accepted</td>
<td></td>
</tr>
<tr data-entity-id="ADR-004">
<td>
<p>
<a href="">
<strong marker="**">ADR-004</strong>
—
Plan Site Theme Resolution
</a>
</p>
</td>
<td>Proposed</td>
<td></td>
</tr>
<tr data-entity-id="ADR-005">
<td>
<p>
<a href="">
<strong marker="**">ADR-005</strong>
—
Replace the useSchema / Type class system with plain rune identifiers
</a>
</p>
</td>
<td>Accepted</td>
<td>Apr 2, 2026</td>
</tr>
<tr data-entity-id="ADR-006">
<td>
<p>
<a href="">
<strong marker="**">ADR-006</strong>
—
Post-identity-transform hook for rune packages
</a>
</p>
</td>
<td>Proposed</td>
<td>Apr 3, 2026</td>
</tr>
<tr data-entity-id="ADR-007">
<td>
<p>
<a href="/runes/plan/decision">
<strong marker="**">ADR-007</strong>
—
Use CSS custom properties for tint token injection
</a>
</p>
</td>
<td>Accepted</td>
<td>Mar 11, 2026</td>
</tr>
<tr data-entity-id="ADR-008">
<td>
<p>
<a href="">
<strong marker="**">ADR-008</strong>
—
Framework-native component interface for rune overrides
</a>
</p>
</td>
<td>Accepted</td>
<td>Apr 4, 2026</td>
</tr>
<tr data-entity-id="ADR-009">
<td>
<p>
<a href="">
<strong marker="**">ADR-009</strong>
—
Framework-agnostic theme packages
</a>
</p>
</td>
<td>Accepted</td>
<td>Apr 5, 2026</td>
</tr>
<tr data-entity-id="ADR-010">
<td>
<p>
<a href="">
<strong marker="**">ADR-010</strong>
—
Unified root-level refrakt config
</a>
</p>
</td>
<td>Proposed</td>
<td>May 1, 2026</td>
</tr>
<tr data-entity-id="ADR-011">
<td>
<p>
<a href="">
<strong marker="**">ADR-011</strong>
—
Compose plan aggregation at the template level, not via postProcess injection
</a>
</p>
</td>
<td>Proposed</td>
<td>May 26, 2026</td>
</tr>
<tr data-entity-id="ADR-012">
<td>
<p>
<a href="">
<strong marker="**">ADR-012</strong>
—
Collapse backlog and decision-log onto collection
</a>
</p>
</td>
<td>Proposed</td>
<td>May 26, 2026</td>
</tr>
<tr data-entity-id="ADR-013">
<td>
<p>
<a href="">
<strong marker="**">ADR-013</strong>
—
Bento levels — an author-defined heading→footprint ladder
</a>
</p>
</td>
<td>Accepted</td>
<td>Jun 7, 2026</td>
</tr>
<tr data-entity-id="ADR-014">
<td>
<p>
<a href="">
<strong marker="**">ADR-014</strong>
—
Responsive surface sizing and project-definable frame presets
</a>
</p>
</td>
<td>Accepted</td>
<td>Jun 10, 2026</td>
</tr>
<tr data-entity-id="ADR-015">
<td>
<p>
<a href="/runes/plan/decision">
<strong marker="**">ADR-015</strong>
—
Adopt content model validation at parse time
</a>
</p>
</td>
<td>Proposed</td>
<td>Mar 18, 2026</td>
</tr>
<tr data-entity-id="ADR-016">
<td>
<p>
<a href="">
<strong marker="**">ADR-016</strong>
—
Frontmatter-declared registry entities
</a>
</p>
</td>
<td>Accepted</td>
<td>Jun 11, 2026</td>
</tr>
<tr data-entity-id="ADR-017">
<td>
<p>
<a href="">
<strong marker="**">ADR-017</strong>
—
Data-bound sandboxes: registry-fed visualizations
</a>
</p>
</td>
<td>Accepted</td>
<td>Jun 11, 2026</td>
</tr>
<tr data-entity-id="ADR-018">
<td>
<p>
<a href="">
<strong marker="**">ADR-018</strong>
—
Canonical layout vocabulary
</a>
</p>
</td>
<td>Proposed</td>
<td>Jun 11, 2026</td>
</tr>
<tr data-entity-id="ADR-019">
<td>
<p>
<a href="">
<strong marker="**">ADR-019</strong>
—
Bento belongs in core, not the marketing plugin
</a>
</p>
</td>
<td>Accepted</td>
<td>Jun 11, 2026</td>
</tr>
<tr data-entity-id="ADR-101">
<td>
<p>
<a href="/runes/plan/examples">
<strong marker="**">ADR-101</strong>
—
Use pipeline hooks instead of plugin system
</a>
</p>
</td>
<td>Accepted</td>
<td>Feb 15, 2026</td>
</tr>
<tr data-entity-id="ADR-102">
<td>
<p>
<a href="/runes/plan/examples">
<strong marker="**">ADR-102</strong>
—
BEM naming convention for identity transform
</a>
</p>
</td>
<td>Accepted</td>
<td>Jan 20, 2026</td>
</tr>
<tr data-entity-id="ADR-103">
<td>
<p>
<a href="/runes/plan/examples">
<strong marker="**">ADR-103</strong>
—
Lazy entity registration for large sites
</a>
</p>
</td>
<td>Proposed</td>
<td>Mar 25, 2026</td>
</tr>
</tbody>
</table>
</div>
</section>Attributes
| Attribute | Type | Default | Description |
|---|---|---|---|
filter | string | — | Space-separated field:value pairs. Fields: status, date, tags |
sort | string | date | Sort field: date (reverse chronological) or id |
Output structure
Renders as an ordered list (ol.rf-decision-log__list) where each entry (li.rf-decision-log__entry) contains:
- Date (
<time>element) - Status badge (color-coded via
[data-status]) - Decision ID
- Title