Speckl — Spec-First Development with Dark Provenance

What is Speckl?

Speckl is a multi-agent software development system where the primary artifact is the specification, not the code. Every behavior traces back to its source of intent — automatically.

System Architecture

🎯 Specification-First

Write what your system should do in SpeckDL, a constraint-based specification language. Z3 proves your specs are consistent before any code exists.

🔗 Dark Provenance

Every function, every branch, every side effect links back to its source — a regulation, a design decision, a conversation. Invisible until needed, always complete.

🤖 Multi-Agent System

Orchestrator, team leads, and SMEs collaborate on specs. The harness scales automatically under load. No human coordination required.

🛡️ Regulated by Design

Speckl targets DO-178C, IEC 62304, ISO 26262, FDA 21 CFR 820. Compliance is structural, not bolted-on.

SpeckDL: A Specification Language

SpeckDL defines what a system does, not how. The compiler produces deterministic output: Z3 → Decision Structure → WASM. Same input, same output — every time. Every spec includes provenance: traceability to regulations, design decisions, and source conversations — embedded in the spec, not added later.

speck RetryHandler {
  input: { operation: Operation, maxRetries: Nat }
  output: Result
  // Constraints the compiler proves via Z3
  constraint: maxRetries <= 5
  constraint: backoff(delay(n)) == delay(n-1) * 2
  constraint: totalDelay < 30s
  // Always-verified properties
  verify: always(implies(attempt > 1, delay > 0))
  // Dark provenance: where did this intent come from?
  provenance: { regulation: "DO-178C 6.4.2.2" }
  provenance: { design_decision: "ADR-0042" }
  source: conversation ref "slack://C123/456"
  review: manual
}

Why Specifications?

📦

Small and Stable

Specs are orders of magnitude smaller than the code they generate. They change less often. The audit surface stays tractable.

🔍

Review the Boundary

If Speck→WASM compilation preserves semantics, human review at the spec boundary satisfies assurance requirements.

🤖

AI-Generated, Human-Owned

Agents generate code. Humans own specifications. The chain of custody for intent stays intact.

Roadmap

Phase A — Now

Open Standard: SpeckDL language, Dark Provenance methodology, reference implementations.

Phase B — Parallel

Consulting: Hands-on engagements with regulated-industry teams.

Phase C — 3-9mo

SaaS: Spec editor, live Z3 verification, provenance graph browser.

Phase D — 9-18mo

Compliance API: Audit reports, traceability matrices.