§01 · The problem
When a large portion of implementation is generated, hours spent no longer correlate with the difficulty or the value of what was produced.
Output volume is close to free. Counting files, commits, or screens rewards generation rather than judgement.
What remains scarce is specification quality, review, taste, integration, and accountability for the result. Those are the things worth appraising.
Without a shared frame, teams and clients end up negotiating from anecdote. Raise exists to give that conversation a consistent structure.
§02 · The system
The model is being developed. The dimensions below describe the intended structure, not a finished specification.
§03 · Limits and disclaimers
§04 · Website