Skip to content

docs: add design rationale documents for key architectural decisions#129

Merged
raffaelschneider merged 2 commits intozentinelproxy:mainfrom
raffaelschneider:docs/design-rationale-125
Mar 10, 2026
Merged

docs: add design rationale documents for key architectural decisions#129
raffaelschneider merged 2 commits intozentinelproxy:mainfrom
raffaelschneider:docs/design-rationale-125

Conversation

@raffaelschneider
Copy link
Contributor

Summary

  • Adds five design rationale documents under doc/design/ explaining why key architectural decisions were made, not just what they are
  • Each document covers: the decision, alternatives considered, trade-offs, when to revisit, and links to manifesto principles
  • Documents: why-pingora.md, why-external-agents.md, why-kdl.md, why-explicit-config.md, why-bounded-resources.md

Closes #125

Test plan

  • Review each document for factual accuracy against codebase and existing docs
  • Verify manifesto quotes match MANIFESTO.md
  • Check that alternatives and trade-offs are fair and complete

Add five documents under doc/design/ explaining why Zentinel made its
core architectural choices, what alternatives were considered, trade-offs
accepted, and when each decision might be revisited:

- why-pingora.md: Pingora as the proxy foundation
- why-external-agents.md: external processes over embedded plugins
- why-kdl.md: KDL over YAML/TOML/JSON for configuration
- why-explicit-config.md: explicit config with fail-closed defaults
- why-bounded-resources.md: hard limits on all resources

Closes zentinelproxy#125
Feature requests now require confirming that the proposal does not
conflict with existing architectural decisions documented in doc/design/.
PR template adds the same checkpoint to the checklist.
@raffaelschneider raffaelschneider merged commit d965b73 into zentinelproxy:main Mar 10, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

docs: add design rationale documents explaining key architectural decisions

1 participant