From e3d4f68db43bd0039b5fbceef8bdf18ba39da707 Mon Sep 17 00:00:00 2001 From: James Ketr Date: Wed, 25 Feb 2026 08:52:11 -0800 Subject: [PATCH] Fix errant line feed Signed-off-by: James Ketr --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 9fda165..0eaf6d9 100644 --- a/README.md +++ b/README.md @@ -15,7 +15,7 @@ After analyzing how 200+ engineering teams are adapting their practices, five pa **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. -**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. **E — Ephemeral**