blurst
a

Go · private repository

blurst/backend

Graded deterministically by blurst against a publicly documented standard for Go architecture. This code is private, so only the grade is shown.

Holding steady at a

Checked 10 November 2026 · blurst standard v1

Record

Graded since October 2026, without a gap

  1. aOct 2026
  2. aNov 2026

Meets the blurst standard for

  • Consistent structure

    Every domain laid out the same way, wired in one place

  • Dependency direction

    Layers and domains import only what they may

  • Thin entry points

    Handlers translate and delegate; mapping stays in mappers

  • Simple business logic

    Pipelines stay small, pure, and readable

  • Data access in one place

    SQL, drivers, and transactions only in the repository layer

  • Side effects at the edges

    Configuration, files, and output only where they belong

  • Typed errors

    Every error is classified and keeps its cause

  • No swallowed errors

    Every error is returned, wrapped, or handled

  • Deliberate panics

    A panic is typed, classified, and never logged twice

  • Structured logging

    Every log carries its context and is actually emitted

  • Type-safe enums

    Enums mapped exhaustively, never cast to bare strings

  • Context passed properly

    context.Context first, never renamed or hidden

  • No duplicated code

    No repeated function bodies or near-duplicates

  • Honest names

    Names say what the code is, not where it came from

An a meets all fourteen rule families of the standard, checked on the date above. A measurement, not a guarantee about the code.

What blurst does for your repository

blurst provides one consistent, enforced standard that serves as the foundation for every line your agents, engineers, and contractors write.
Starting where your code is, set each rule to off, warning, or error, and promote it as your codebase improves.

  • Keep bad code out

    Every keystroke, yours or your agent's, is checked against the standard. Every merge is graded or blocked. Code quality is back, and enforced.

    Install for VS CodeAdd to GitHub Actions

  • Pay down the debt

    See which rules your codebase is closest to meeting. Clear the remaining findings, then promote each rule so violations can't return. Your codebase climbs one rule at a time.

    See your next promotions

  • Review code, not style

    blurst checks the conventions a machine can enforce. Reviewers spend their time on business logic, design, and correctness.

    Pre-grade pull requests

  • Prove your engineering discipline

    Your badge shows anyone at a glance. Your signed report shows auditors, customers, and acquirers the detail. All without exposing your code.

    Get your badgeGet your signed report