Show Menu
Cheatography
  1. Home >
  2. Programming >

RBA Git Commit Taxonomy Cheat Sheet (DRAFT) by

Customized Commits (following Conventional Commits) for Refraction-Based Architectural (RBA) projects in Git

This is a draft cheat sheet. It is a work in progress and is not finished yet.

Format

Pattern
Example
type(s­cope): summary
frame(­pro­gram): redefine current problem state for AI-era redesign

Commit Types

Type
Use When
Typical Examples
 
frame
The governing unders­tanding changes
problem reframing, scope clarif­ica­tion, correcting a higher­-order assumption
 
build
Creating substa­ntial new work
new artifacts, new sections, new matrices, new progra­m/c­ourse content
 
refactor
Structure improves without major change to core intent
reorga­nizing documents, tightening structure, improving sequence or alignment
 
synth
Combining multiple artifacts into a higher­-order output
merging sections into a full draft, combining several artifacts into one summary
 
review
A change is driven mainly by feedback or inspection
supervisor revisions, advisory revisions, review­-re­sponse changes
 
meta
Process or repo guidance changes
workflow notes, commit taxonomy, README­/pr­ocess guidance
 
chore
Light mainte­nance only
renaming, moving files, formatting cleanup

Default Scopes

Scope
Use For
 
program
program design, transition models, bridge­/su­ccessor work
 
course
course­-level artifacts and redesign work
 
whitepaper
white paper sections, append­ices, full draft work
 
case-study
case studies and reflec­tions
 
workflow
process conven­tions, commit taxonomy, operat­ional guidance
 
repo
repo-level organi­zation and mainte­nance
Other scopes are allowed. Consis­tency is the key point.

Sample Commits

Situation
Sample Commit
redefine the core problem
 
frame(­pro­gram): redefine bridge and successor relati­onship
add new course artifact work
 
build(­cou­rse): add Python bridge implem­ent­ation patterns
tighten existing program structure
 
refact­or(­pro­gram): tighten semest­er-­by-­sem­ester bridge structure
merge paper sections into one draft
 
synth(­whi­tep­aper): merge sections and appendices into full draft
revise after supervisor feedback
 
review­(wh­ite­paper): revise framing for supervisor readab­ility
update the commit system itself
 
meta(w­ork­flow): simplify commit taxonomy for artifact ecosystems
rename or reorganize files
 
chore(­repo): rename and reorganize support files

Keep It Simple

Rule
Reminder
1
Prefer consis­tency over perfect precision
2
Use broad scopes, not overly specific ones
3
Avoid inventing new types unless needed repeatedly
4
If a commit spans multiple artifacts, classify by the dominant action

Quick Decision Rule

If the main move is ...
Use
changing the governing meaning
 
frame
creating substa­ntial new material
 
build
reorga­nizing existing structure
 
refactor
combining multiple strands
 
synth
revising from feedback
 
review
updating proces­s/repo guidance
 
meta
doing minor mainte­nance only
 
chore

RBA Definition

RBA (Refra­cti­on-­Based Archit­ecture) is a way of using AI to develop complex work through structured refraction rather than one-shot genera­tion, so that meaning, archit­ecture, and artifact coherence are preserved as the work evolves.

It is a governed human-AI collab­orative process in which intent is progre­ssively refracted across multiple artifact layers while preserving coherence, allowing lower-­level work to inform and refactor higher­-level unders­tanding when reality reveals hidden constr­aints, opport­uni­ties, or structural mismat­ches.

(Collab­oration was intent­ionally deferred because it semant­ically suggests two sentient beings working together, which risks anthro­pom­orp­hizing AI in ways that are concep­tually mislea­ding. Refraction is more approp­riate because, like light passing through a medium and changing direction or separating into visible compon­ents, it captures how human intent is perceived, transf­ormed, decomp­osed, and delegated across different layers of artifacts, constr­aints, and AI-med­iated proces­ses.)