From 6a53b8fdf704e83f999f80a989188ef3327563bf Mon Sep 17 00:00:00 2001 From: Scott Scoble Date: Wed, 29 Apr 2026 16:58:04 -0700 Subject: [PATCH] Fix: correct 'What is Speckl?' positioning from multi-agent system to open standard - Removed inaccurate multi-agent system description and architecture SVG - Replaced with honest framing: Speckl is an open standard (methodology + language spec) - Removed Discord CTA button per Scott's request - Removed stale favicon.svg from landing dir - General polish: hero layout, mobile breakpoints --- landing/index.html | 214 +++++++++++++++------------------------------ 1 file changed, 70 insertions(+), 144 deletions(-) diff --git a/landing/index.html b/landing/index.html index bcaf3d3..1c7b9d3 100644 --- a/landing/index.html +++ b/landing/index.html @@ -4,14 +4,14 @@ Speckl — Spec-First Development with Dark Provenance - + - + @@ -237,69 +199,33 @@
Source Code Read the Whitepaper +

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

- - - - - - - - - Orchestrator - Accepts Specks, decomposes tasks - - - - - - - Team Lead - Verification - - - Team Lead - Codegen - - - - - - - Z3 SME - (verify) - - - TypeScript SME - (emit) - -
- +

Speckl is an open standard for specification-first development with dark provenance. It defines how to write what a system should do — in a machine-verifiable format — before any code is written. Every behavior traces back to its source of intent.

+ +

Speckl is not a product or a platform. It is a methodology and language specification, published freely under MIT. The SpeckDL language, the Dark Provenance methodology, and the reference implementations define the standard. Products built on it — compilers, verification tools, compliance APIs — will come as the ecosystem grows.

+
-

🎯 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.

+

📝 SpeckDL Language

+

A constraint-based specification language that defines what a system does, not how. Specs are small, stable, and machine-verifiable — the audit surface for regulated systems.

🔗 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.

+

A methodology where every behavior traces back to its source — a regulation, a design decision, a conversation. The provenance graph is always present, materialized on demand for audits or debugging.

-

🤖 Multi-Agent System

-

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

+

🧩 Reference Implementations

+

Minimal reference tools for SpeckDL parsing, Z3 constraint verification, and provenance graph generation. The building blocks for tooling, not a production system.

-

🛡️ Regulated by Design

-

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

+

🏗️ Ecosystem-First

+

The standard is the foundation. Consulting, SaaS tooling, and compliance APIs will build on it — validated through real-world use before they ship.

@@ -327,7 +253,7 @@

Why Specifications?

- +
📦
@@ -349,7 +275,7 @@

Roadmap

- +

Phase A — Now

@@ -360,11 +286,11 @@

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

-

Phase C — 3–9mo

+

Phase C — 3-9mo

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

-

Phase D — 9–18mo

+

Phase D — 9-18mo

Compliance API: Audit reports, traceability matrices.

@@ -376,4 +302,4 @@ - \ No newline at end of file +