FAQ
Getting Started
Section titled “Getting Started”Where should I start a discussion? Is Slack okay?
Section titled “Where should I start a discussion? Is Slack okay?”Anywhere, including a conversation between you and your agent. Slack is fine for early, informal ideas. Once an idea feels adoptable, move it to a proposal. Generally, GitHub Discussions is encouraged to organize long-running thoughts so they do not get lost.
Do I need to use every tool in the stack?
Section titled “Do I need to use every tool in the stack?”No. The stack documents what has proven effective, not what is mandatory. Start with whatever solves your immediate problem.
What’s the relationship between SHRINE and my team’s practices?
Section titled “What’s the relationship between SHRINE and my team’s practices?”SHRINE is a floor, not a ceiling. The patterns here are a shared baseline; teams are free to extend, adapt, or add to them.
Proposals & Adoption
Section titled “Proposals & Adoption”What’s the difference between a discussion and a proposal?
Section titled “What’s the difference between a discussion and a proposal?”A discussion explores an idea; a proposal asks the community to adopt it. Discussions can lead to proposals, but they do not have to. Not everything needs to become doctrine.
How does something become an official pattern or principle?
Section titled “How does something become an official pattern or principle?”Open a proposal in the GitHub forum. If the community supports it and no blocking concerns surface during discussion, a keeper merges it. Obvious wins move fast; controversial items get more time.
Can I propose changes to existing patterns?
Section titled “Can I propose changes to existing patterns?”Yes. Open a PR with your changes and the rationale behind them. Patterns are living documents, not stone tablets.
How do I suggest a new tool for the stack?
Section titled “How do I suggest a new tool for the stack?”Use it first. If it proves valuable in practice, write up what you learned and propose it. Adoption is based on demonstrated value, not theoretical promise.
Governance
Section titled “Governance”What if I disagree with a decision?
Section titled “What if I disagree with a decision?”Start a new discussion challenging it, referencing the original. Decisions reflect current best judgment; better information changes them.
How do we deprecate a pattern or principle?
Section titled “How do we deprecate a pattern or principle?”Anyone can raise a pattern or principle for deprecation, and the community weighs in. A regular review cadence for existing principles, patterns, and tooling may be proposed in the future.
How do we handle vendor lock-in concerns?
Section titled “How do we handle vendor lock-in concerns?”Evaluated individually. Weigh each tool’s value against its maintenance overhead, coupling, and exit costs.
How do we balance innovation with stability?
Section titled “How do we balance innovation with stability?”Fail fast on new concepts. Tread carefully around well-refined, proven ones.
How do I become a keeper of the SHRINE?
Section titled “How do I become a keeper of the SHRINE?”Participate. Make your presence felt and your ideas heard. The pool of keepers stays proportionate to the community: enough that no one bringing an idea to the table gets ignored, but not so many that guardianship loses its meaning. Be the embodiment; assume the role without being asked.