RISE Framework
Reverse-engineer, Intent-extract, Specify, Export — a creative-oriented methodology for understanding and generating code architectures through structural tension dynamics.
Foundation: Specifications as Prose Code
RISE builds on SpecLang’s core insight: specifications are “prose code” — natural language representations of computation that still require you to think like a programmer.
SpecLang Principles
- Spec as Source of Truth — the specification is what you maintain; executable code is secondary
- Variable Detail Levels — offhand remarks may generate dozens of boilerplate lines; exact steps when precision matters
- Creating and Adjusting — start simple, refine against running output, stop when reality matches vision
- Bi-directional Ideation — the model “yes-ands” your intent, extending ideas naturally
- Intent-based Expression — focus on behavior; toolchain handles plumbing
The Four Phases
Phase 1: Reverse-engineer (R)
Creative Archaeology — extracting what exists with respect for what was created.
- Map the existing system’s structure without importing preconceptions
- Identify what users love about the current prototype
- Use Structural Thinking — start with nothing, picture what is said, ask questions
Uncovering creative vision — what the creator wanted to bring into being.
- Distinguish between what the code does and what the creator intended
- Extract the structural tension: desired outcome vs. current reality of the codebase
- Preserve the “beloved qualities” that make prototypes valuable
Phase 3: Specify (S)
SpecLang prose-code generation — writing specifications that capture desired outcomes.
- Specifications focus on what you want to create, not problems to fix
- Detail varies: broad strokes for obvious patterns, precision for critical behavior
- Each spec is a structural tension chart: desired behavior + current state + action plan
Phase 4: Export (E)
Manifesting the creation — generating implementation from specification.
- Code generation follows the spec as source of truth
- Git-log-driven methodology maintains specs as code evolves
- The creation advances toward the desired outcome through iterative refinement
RISE and the Creative Orientation
RISE transforms how reverse engineering is practiced:
| Reactive Approach |
RISE Approach |
| Find bugs and fix them |
Discover creative intent and honor it |
| Document what’s broken |
Specify what’s desired |
| Patch problems |
Advance toward the vision |
| Technical debt analysis |
Creative archaeology |
Key Sources