diff --git a/landing/index.html b/landing/index.html new file mode 100644 index 0000000..3932772 --- /dev/null +++ b/landing/index.html @@ -0,0 +1,272 @@ + + + + + + Speckl โ€” Spec-First Development with Dark Provenance + + + + + +
+
+

Speckl

+

Spec-first development with dark provenance.
Write what your system should do. Prove it. Ship with full traceability.

+ +
+
+ +
+

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.

+ +
+
+

๐ŸŽฏ 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.

+ +
+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 D โ€” Now

+

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

+
+
+

Phase C โ€” Parallel

+

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

+
+
+

Phase A โ€” 3-9mo

+

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

+
+
+

Phase B โ€” 9-18mo

+

Compliance API: Audit reports, traceability matrices.

+
+
+
+ + + + +