You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Humanize now uses a shared config hierarchy instead of scattering defaults across scripts.
61
76
@@ -67,27 +82,14 @@ Priority is:
67
82
68
83
This keeps RLCR, PR loop, and `ask-codex` aligned on the same Codex defaults, while still letting each project pin its own behavior. The current config surface covers shared review settings such as `codex_model` and `codex_effort`, plus workflow toggles like `bitlesson_model`, `agent_teams`, and plan-generation preferences.
69
84
70
-
## BitLesson System
85
+
###BitLesson System
71
86
72
87
Humanize also includes a BitLesson system, which is the repository's Bitter Lesson-style knowledge capture workflow.
73
88
74
89
Each project keeps a local knowledge base at `.humanize/bitlesson.md`. The RLCR setup initializes that file from a strict template when it is missing. During each round, the loop reads the knowledge base, runs a selector for every task or sub-task, and requires the round summary to include a `## BitLesson Delta` section describing whether a reusable lesson was added, updated, or intentionally left unchanged.
75
90
76
91
The goal is to turn repeated failure-and-fix cycles into explicit project memory instead of rediscovering the same operational lessons every round.
0 commit comments