Repo Strategy¶
Fabric4L should be maintained through behavior-first engineering.
Principle¶
If behavior is outside the intended behavior, it fails.
Troubleshooting should not be the primary quality system. The repo should rely on:
- Behavior contracts
- Regression tests
- Security gates
- CI validation
- Explicit ADRs
- Documented runbooks
Documentation expectation¶
Every major production behavior should be traceable from:
- Documentation
- Test
- Gate
- Runtime implementation