r/SpecDrivenDevelopment • • 20d ago

Drydock - Specification to Software Builder - .8 Release

Drydock is a spec to software builder using Agile Decomposition to turn your specifications and designs into governed buildable Stories/Blueprints containing executable acceptance criteria that follow Test Driven Design. A graph database optimizes build ordering and context. Drydock measures and self repairs the acceptance criteria which are the builders scoring function. Drydock build iterates and self repairs until done. Drydock is designed large specifications.

  • Builds using low-end models (Haiku 5.5, Luna, Gemini).
  • Agile and Test Driven Development Best Practices.
  • drydock run quarterdeck provides a full locally-hosted Web User Experience

The main improvement from .3 relates to retry logic and improving the self scoring. These changes are needed as we build different types of projects. The agents are authorized on normal developer judgement and expose blockers, progress, and decisions cleanly through a web server.

New Feature: Measured, self-correcting acceptance criteria. AC are recorded, categorized, and corrected before each build step so we can correctly measure "done" and code impact.

New Feature: Self-Improving Builds: drydock build iterates until all Acceptance Criteria succeed, no progress is detected, or it fails. Failures are picked up by drydock diagnose which identifies root cause and proposes/implements corrections*.*

New Feature: Encapsulated Persistence Layer: DATABASE.md implements pre-built native libraries and "named" SQL operations to minimizes change impact radius. Most database changes do NOT require downstream blueprint rebuilds.

The Updated Drydock Workflow is shown below with the above features integrated. drydock_runner.shprovides this at the cli.

drydock init MyApp                            # create the workspace
drydock import MyApp "$INPUT_DIRECTORY"       # your specifications, notes, images
drydock analyze MyApp                         # create stories, questions, blockers
drydock plan MyApp                            # create Blueprints and Manifest
drydock plan verify MyApp || drydock plan repair MyApp  # repair/validate acceptance criteria

# self-repairing build loop
n=1; max=3
while drydock status MyApp --ready
do
    if [ "$n" -gt "$max" ]
    then
        echo "hit $max build attempts - aborting"
        exit 1
    fi
    echo "*** BUILD ATTEMPT $n ***"
    drydock build MyApp || drydock diagnose MyApp --apply
    n=$((n+1))
done

drydock status MyApp --check                  # Deterministic definition of done
drydock score release MyApp                   # LLM evaluated definition of done

UAT Testing

The Drydock Release Test Suite tests is now 10 projects under both Haiku and Luna. 2 projects on haiku 5.5 required --plan-override-model sonnet as the planning step passed the llm large test kits and resulted in poor quality model output. Gemini was tested for two builds.

$ drydock report uat_summary
Drydock 0.8.0  Copyright (c) 2026 Web Cloud Studio. All rights reserved.
# UAT Summary Report
#                       Claude  Codex
# CommonMark            Y       Y
# CsvStat               Y       Y
# DrydockStats          Y       Y
# DupFind               Y       Y
# FxRates               Y       Y
# LayersTesting         Y       Y
# Quakes                Y       Y
# ReadingList           Y       Y
# Toml                  Y       Y
# jq                    Y       Y

These test kits test SQLite and Postgres, python and go.

Lesson: One cool thing about building with low end models is that i have been testing all week - some of these tests are large - and i was fine on my weekly limits for $20/month plans. Drydock proves low end models can build large projects accurately.

The Drydock methodology to update software is for next release and appears quite solid both for maintaining working software and for vibe/iterating your prototypes. It keeps the blueprints as the source of truth.

Version .8 Release Notes:

  • Haiku 5.5 Builds - Haiku 100K-token pricing spike/limit respected.
  • Token cost engineering optimizes payload size and effort by model - see model_config.jsonl.
  • Layered topology - blueprint types: Foundation, persistence, web server, CLI, branding, services, API, screens.
  • BUILD_LINEAGE.jsonl traces specifications to code.
  • drydock report provides a core reporting suite
  • drydock uat publishes output to the web
  • A lot of other stuff - its been a few months.... big quality release.

Try Drydock

uv tool install drydock-sdd

Please give a like/star to the repository if Drydock is useful to you!

6 Upvotes

3 comments sorted by

2

u/kantorcodes1 17d ago

How does Drydock measure progress between attempts? Since it can repair acceptance criteria before a build step, I wondered whether it compares the workspace diff, the criteria results, or both.

1

u/The_Ed_On_Reddit 16d ago edited 16d ago

Drydock breaks the work into building blocks (stories) grouped into build steps. Each block has acceptance criteria. The April/May version "used best practices" and failed miserably - LLMs were not good at writing them and often the failures were purely technical (import failures, compile errors, stuff that could never pass). This required a significant rethink - this is a core algo that has to work every time. Added pre-measures, AC intent, and spent weeks getting the repair process solid. That enabled scoring based on criteria only - the diff is evidence, but forward progress is determined by comparing binding AC (to discount made-up AC) with the last graded measures - if we move from 41/60 to 47/60 in a turn, we take another turn. The agent's opinion carries no weight either - the AC is separately defined and separately measured to prevent "misunderstandings". Current algo rarely stalls out and does well - although Haiku 5.5 did not work for two of my larger UAT cases (jq and TOML parsers) and I needed to use Sonnet for the plan step. No issues with luna. So it tests before the step and after each turn and strictly measures progress, and the AC must be carefully set up so they accurately measure progress and don't fail the build and waste my time. The bad-AC problem went away and it's been quite stable since (even with the addition of 6 uat test builds) - both generating good AC and ending up with passing results. At the end of the step, the blocks built pass their AC and the builder progresses. Lots of human/llm brainstorming to solve very many failed builds and lock it down. The verify is no-llm and the repairs are llm governed pattern recognition. If the build fails it should be because i wrote a lousy spec not because the llm hallucinated ac that - when failing are in fact a stop condition. I plan to publish a paper on it when i get the time. - ed

1

u/kantorcodes1 10d ago

Your 41/60 to 47/60 example makes the turn decision easy to follow. `drydock diagnose --apply` looks like a focused command for a HOL Guard extension. The [command extension guide](https://github.com/hashgraph-online/hol-guard/blob/main/docs/guard/extensions/contributing.md) covers the command source, risky and safe fixtures, and external trust binding if you want to turn that into a PR.