Skip to main content
These are hard exclusions for the current doctrine.
  1. Not domain-locked: openboa is not a vertical-specific product.
  2. Not feature-count driven: feature volume or demo flair is not a primary success metric.
  3. Not one-sided: we do not sacrifice autonomy for process, or process for autonomy.
  4. Not person/tool-first: we do not prioritize convenience over Business continuity.
  5. Not trend-reactive doctrine: core doctrine does not change for short-term hype.

​
Why this exists

Sharp non-goals reduce drift. They keep product, architecture, and contributor decisions aligned with BOA-0.