Birdor Blog Editorial Bar

Purpose

Birdor Blog is a Builder Notes Repository.

It exists to document real engineering decisions, product trade-offs, and system-level reasoning.
It is not a platform for opinions, trends, or content marketing.

Any article that does not originate from an actual build, decision, or constraint must not be published.

Allowed Content Types

Every article must clearly belong to one of the following categories.

1. Builder Notes

Records from real development work.

Includes:

  • Technical or architectural decisions
  • Trade-offs made under real constraints
  • Failed or reversed decisions
  • Assumptions proven wrong through implementation

Requirements:

  • At least one concrete decision
  • At least one real-world constraint

2. Tool Essays

Design rationale and boundaries of tools.

Includes:

  • Why a tool exists
  • Why certain features are intentionally excluded
  • Design philosophy and scope control

Excludes:

  • Tutorials
  • Feature lists
  • Usage guides (these belong in Docs)

3. System Thinking

System-level reasoning grounded in engineering reality.

Includes:

  • Structural limitations of developer tools
  • Cost, complexity, and adoption trade-offs
  • Constraints of solo or small-team systems

Requirement:

  • Must connect back to real engineering or product constraints

Disallowed Content

The following content is not permitted.

Traffic-Driven Content

  • Trends, hype, “opportunities”
  • Monetization, income claims, growth shortcuts

Pure Ideation

  • Abstract ideas without execution paths
  • No constraints, costs, or trade-offs

Rule:
If the article could have been written five years ago without change, it is rejected.

Motivation or Opinion Pieces

  • Personal beliefs
  • Inspirational narratives
  • Founder stories without engineering substance

Hard Editorial Gates

All articles must pass every gate below.

1. Real Trigger

  • The article states the specific problem or decision that triggered it
  • Context and timing are clear

2. Explicit Constraints

  • At least two concrete constraints are stated
    • Time, cost, performance, maintenance, security, scale

3. Clear Trade-offs

  • What was chosen
  • What was explicitly not chosen, and why

4. Transferable Insight

  • At least one reusable decision rule or reasoning framework
  • Not dependent on Birdor-specific context

5. Tone Alignment

  • Calm, precise, non-promotional
  • Birdor appears as context, not as the subject

Articles should cover the following elements:

  1. Context and trigger
  2. Initial assumptions
  3. Constraints
  4. Decision and trade-offs
  5. Outcome or current state
  6. Reusable reasoning

Starting with opinions or conclusions is discouraged.

Quality Veto

An article may be removed if it:

  • Lacks concrete examples
  • Can be reduced to a short social media post
  • Prioritizes opinion over evidence
  • Breaks tone or scope alignment

Publishing Principles

  • No publishing quotas
  • Low frequency, high signal
  • Gaps in publishing are acceptable

Quality overrides consistency.

Article Lifecycle (Optional)

  • Exploration
  • Stable
  • Deprecated

Deprecated articles remain visible for historical accuracy.

Editorial Rule

If an article does not demonstrate that Birdor is actively building and making real decisions, it does not belong here.