jketreno/clear
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix errant line feed

Browse Source 
Signed-off-by: James Ketr <james_git@ketrenos.com>
This commit is contained in:
James Ketr
2026-02-25 08:52:11 -08:00
parent cef0636aa7
commit e3d4f68db4
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@@ -15,7 +15,7 @@ After analyzing how 200+ engineering teams are adapting their practices, five pa
**C — Constrained** **C — Constrained**
Your unwritten rules must become written constraints. That "we never put business logic in controllers" comment in code review? It needs to be an automated architecture test. LLMs can't infer tribal knowledge. Codify your invariants in types, contracts, tests, and linters—anything that can fail a build. Your unwritten rules must become written constraints. That "we never put business logic in controllers" comment in code review? It needs to be an automated architecture test. LLMs can't infer tribal knowledge. Codify your invariants in types, contracts, tests, and linters—anything that can fail a build.
**L — Limited** **L — Limited**
Your bounded contexts just became blast radius zones. Each module needs clear boundaries with comprehensive tests—because that's where an LLM can operate safely without risking the broader system. Your "Billing" context with 95% test coverage? LLM-maintainable. Your "Payments" context handling money movement? Keep that human-driven. Your bounded contexts just became blast radius zones. Each module needs clear boundaries with comprehensive tests—because that's where an LLM can operate safely without risking the broader system. Your "Billing" context with 95% test coverage? LLM-maintainable. Your "Payments" context handling money movement? Keep that human-driven.
**E — Ephemeral** **E — Ephemeral**