Try the design before any code exists.
Try design options against your lenses in the rkito UI. Shift left now covers design, not just the IDE.
| Level | Option | Result |
|---|---|---|
| Option A | Add a second payment provider behind the vault API | Conforms |
| Option B | Call the provider directly from the ledger service | Strains |
| Pillar | Data Stewardship | Option B |
Explore, describe, import.
Three ways to get oriented, and to start the design conversation with your architect from context, not guesswork.
Read the current approved state of the Architecture Ledger before touching a domain.
Say what you intend in plain language. rkito suggests the affected entities and lenses.
Bring in existing designs, diagrams and work items as a starting point.
From an idea to a CHI with context.
Find the systems and components your feature will touch, and the active CHIs on them.
rkito analyses your description against the Ledger and suggests what is affected.
Check which lenses will evaluate the work and which pillar an option strains.
The architect refines and approves, starting from your intent.
Checked while you design.
Try options against your lenses before any code exists.
Agents read the same lenses while they write, so fewer findings reach review.