ID:WORK-535Status:ready
Report a rune's actual universal attributes in refrakt reference
refrakt reference card prints:
Priority:highComplexity:simpleMilestone:v0.32.0Source:SPEC-125
refrakt reference card prints:
Tracking started Sep 6 — check back for trends.
127194f--format json reports the same narrowed set, so machine consumers agree with the human outputrefrakt reference list and refrakt reference dump are consistent with the single-rune outputAGENTS.md (or whatever dump --check guards) is regenerated if its content shiftsnpm run build and the full repo suite passWorth deciding rather than defaulting: does an inapplicable attribute vanish from the output entirely, or appear marked as unavailable?
Vanishing is simplest and matches the schema. But the structure contract already records why an axis is unavailable on a rune ("this rune declares no body section"), and surfacing that is more useful to someone wondering why reading is missing from card when it is on textblock. Reference output is a teaching surface, so the reason is probably worth showing — but it should be a choice, not an accident of implementation.