SDDFW. v0.1 in development
SPECIFICATION → VERIFICATION

Build with intent.
Ship with evidence.

A clear line from what you asked for to what you can verify. SDDFW connects requirements, checks, and evidence for your next AI-built change.

See it in action Meet the first version
Start small. Make every change count.
01 / THE ACCEPTANCE REPORT+
acceptance.reportINTERACTIVE SAMPLE

CHANGE / RESERVATIONS

Cancellation window

Allow cancellations at least 24 hours before a reservation.

2 / 4 criteria passed
Needs attention
CR-003 / SAMPLE EVIDENCELOCAL

cancellation.test.js:42

Expected rejectedReceived accepted

A reservation 12 hours away can still be cancelled.

Illustrative results · 3 checked, 1 unverified
Every result has a reason. Every gap stays visible.

A framework for the way
you already build.

Your specs+</> Your agent+ Your checks

First target: OpenSpec + JavaScript tests.
Planned for v0.1.

THE WORKFLOW

Make intent
traceable.

Keep the behavior you want connected to the work you review. One focused change at a time.

01

Define the behavior.

Describe what should happen, the boundaries that matter, and what a good result looks like.

A clear specification
02

Connect the checks.

Link acceptance criteria to tests and observable outcomes. Keep the scope of each check explicit.

Evidence you can inspect
03

Review with clarity.

See what passed, what failed, and what still needs checking. Give your agent a precise next step.

A reviewable change

THE PRINCIPLE

A checkmark should
tell a story.

The first version is built around a simple idea: make the evidence as easy to review as the change itself.

A result for every criterion.

Passed, failed, or still unverified. An incomplete check stays visible in the report.

A source for every result.

Follow the connection from the expected behavior to the check and its recorded output.

Context for every change.

Know which version and environment were checked, and when evidence needs refreshing.

SMALL STEPS. A CLEAR DIRECTION.

The first chapter.

Start with acceptance. Grow through real use.
Here’s where we’re heading.

v0.1 NOW BUILDING

Acceptance,
made visible.

A focused loop from existing specs to checks, evidence, and a clear review.

  • OpenSpec + a minimal native format
  • Criteria mapped to JavaScript tests
  • Local results and reviewable reports
THE INITIAL SCOPE
NextEXPLORING

Context that
carries forward.

Keep the link between intent and evidence useful as the project evolves.

  • Spec Kit reader
  • Evidence freshness and change impact
  • Continuity between agent sessions
GUIDED BY THE FIRST USERS
LaterON THE HORIZON

A framework
that grows with you.

Expand the same clear acceptance loop to more tools, stacks, and teams.

  • More test runners and adapters
  • Shared review workflows
  • Reusable behavior scenarios
ONE USEFUL ADDITION AT A TIME

A LITTLE MORE CONTEXT

Good questions.

Can I install SDDFW yet?

The framework is in early development. This landing includes a working interactive sample of the acceptance report. The v0.1 roadmap shows what we plan to implement first.

Will I need to change my coding agent?

The goal is to fit your existing workflow. SDDFW will provide the specification and acceptance loop while your coding agent handles implementation. We’ll start with a focused integration and expand through real use.

What does a passed check actually mean?

A specific check succeeded for the recorded version and environment. The report should make that scope explicit. Missing checks remain unverified, and local results are identified as local results.

BUILD THE NEXT CHANGE WITH CLARITY.

Intent in.
Evidence out.

A small first version.
A foundation for better development with AI.

Explore the sample report