Decisions

Decisions

43 of 43 decisions
Proposed 15
ADR-004 main
Plan Site Theme Resolution
ADR-006 main
Post-identity-transform hook for rune packages
ADR-010 main
Unified root-level refrakt config
ADR-020 main
Dual-mode asset resolution for site templates
ADR-021 main
Site templates are scaffold-copied, not live dependencies
ADR-025 main
Incremental rebuild: dependency-tracked invalidation with the registry as firewall
ADR-027 main
Represent scoped rune attributes as an object-valued bag
ADR-031 main
Site-level rune config overrides
ADR-032 main
Rune config keys are kebab-case
ADR-033 main
Measures are a named, typed vocabulary — not a new channel
ADR-034 main
Source location is a file-qualified range carried on the renderable
ADR-036 main
Name the pattern; do not open a language
ADR-037 main
Users author composed runes only
ADR-038 main
A behavior binds on a data contract, never a BEM class
ADR-039 main
Where a rune lives: three kinds of package, and one test
Accepted 28
ADR-001 main
Astro Readiness Investigation
ADR-002 main
Framework Readiness Investigation: Next.js, Eleventy, Nuxt
ADR-003 main
Markdoc Feature Gap Analysis for Refrakt
ADR-005 main
Replace the useSchema / Type class system with plain rune identifiers
ADR-007 main
Rune packages provide their own layouts
ADR-008 main
Framework-native component interface for rune overrides
ADR-009 main
Framework-agnostic theme packages
ADR-013 main
Bento levels — an author-defined heading→footprint ladder
ADR-014 main
Responsive surface sizing and project-definable frame presets
ADR-015 main
Project-tunable scale ramps as part of the token contract
ADR-016 main
Frontmatter-declared registry entities
ADR-017 main
Data-bound sandboxes: registry-fed visualizations
ADR-018 main
Canonical layout vocabulary
ADR-019 main
Bento belongs in core, not the marketing plugin
ADR-022 main
Rename the sandbox runtime directory from examples to sandboxes
ADR-023 main
Versioning and compatibility for distributed extensions
ADR-024 main
Themes are framework-agnostic by default; the framework component layer is opt-in
ADR-026 main
Promote crop-bleed to a universal frame-overflow facet
ADR-028 main
Attribute applicability is rune identity, not theme configuration
ADR-030 claude/value-primitives-and-grid
Arrangements name topologies; variants are modifiers; semantics are rune-locked
ADR-040 main
Stale exclusions are two project-config lists, not one ignore list
ADR-041 main
Compose content on section, not card
ADR-042 claude/value-primitives-and-grid
Metadata belongs to a rune's definition; themes override native runes only
ADR-043 claude/value-primitives-and-grid
A theme renders a vocabulary; it configures no rune
ADR-044 claude/value-primitives-and-grid
Plugin runes speak the vocabulary; novel parts bring token-only structure
ADR-045 claude/value-primitives-and-grid
A theme may arrange a composed rune, but not redefine it
ADR-046 claude/value-primitives-and-grid
Section's header grammar is anchored and explicit
ADR-047 claude/value-primitives-and-grid
A rune may take editorial runes as a narrative field