From 362548caad651e9440a1ba219ff74027c772a1c5 Mon Sep 17 00:00:00 2001 From: Content Agent Date: Tue, 28 Apr 2026 21:09:42 -0700 Subject: [PATCH] =?UTF-8?q?refactor:=20rename=20phases=20to=20sequential?= =?UTF-8?q?=20A=E2=86=92B=E2=86=92C=E2=86=92D?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Old: D (Open Standard) → C (Consulting) → A (SaaS) → B (Compliance) New: A (Open Standard) → B (Consulting) → C (SaaS) → D (Compliance) Updated: README.md, strategy.md, plan-flow.svg, landing page --- README.md | 8 ++++---- docs/diagrams/plan-flow.svg | 28 +++++++++++++-------------- docs/strategy.md | 38 ++++++++++++++++++------------------- landing/index.html | 8 ++++---- 4 files changed, 41 insertions(+), 41 deletions(-) diff --git a/README.md b/README.md index 79090cc..a9d63b2 100644 --- a/README.md +++ b/README.md @@ -66,10 +66,10 @@ Speckl follows a phased strategy — the open standard fuels everything else: | Phase | Focus | Timeline | |-------|-------|----------| -| **D — Open Standard** | SpeckDL language, Dark Provenance methodology, reference implementations | Now → 3mo | -| **C — Consulting** | Hands-on engagements with regulated-industry teams, validating the methodology | Now → 3mo (funds D) | -| **A — Developer Tool (SaaS)** | Self-serve platform: spec editor, live Z3 verification, provenance graph browser | 3 → 9mo | -| **B — Compliance API** | Enterprise provenance engine: audit reports, traceability matrices, compliance packs | 9 → 18mo | +| **A — Open Standard** | SpeckDL language, Dark Provenance methodology, reference implementations | Now → 3mo | +| **B — Consulting** | Hands-on engagements with regulated-industry teams, validating the methodology | Now → 3mo (funds A) | +| **C — Developer Tool (SaaS)** | Self-serve platform: spec editor, live Z3 verification, provenance graph browser | 3 → 9mo | +| **D — Compliance API** | Enterprise provenance engine: audit reports, traceability matrices, compliance packs | 9 → 18mo | The standard comes first. Adoption creates the market. The products follow. diff --git a/docs/diagrams/plan-flow.svg b/docs/diagrams/plan-flow.svg index 8727649..a4f265c 100644 --- a/docs/diagrams/plan-flow.svg +++ b/docs/diagrams/plan-flow.svg @@ -8,41 +8,41 @@ - + - PLAN D - Speckl Open Standard + Foundation + PHASE A + Open Standard + Foundation SpeckDL · Dark Provenance · Reference agents · Certification - + - + - + - PLAN C + PHASE B Consulting + Services Validates · Funds early · Builds case studies - + - PLAN A + PHASE C Developer Tool (SaaS) Self-serve PLG · Provenance data - + - + - + - PLAN B + PHASE D Compliance Infra (API) Feeds on SaaS data · Highest margin · Enterprise sticky - D → C → A → B: Standard builds credibility, consulting validates, SaaS scales, compliance monetizes + A → B → C → D: Standard builds credibility, consulting validates, SaaS scales, compliance monetizes \ No newline at end of file diff --git a/docs/strategy.md b/docs/strategy.md index ea04548..83a57db 100644 --- a/docs/strategy.md +++ b/docs/strategy.md @@ -6,19 +6,19 @@ ## Core Thesis -Plan D (open standard + foundation) is the **engine**. All revenue flies by on the credibility, adoption, and ecosystem that the open standard builds. +Phase A (open standard + foundation) is the **engine**. All revenue flies by on the credibility, adoption, and ecosystem that the open standard builds. -![Plan D → C → A → B flow](diagrams/plan-flow.svg) +![Phase A → B → C → D flow](diagrams/plan-flow.svg) -**The flow:** Open standard (D) builds the language and community → hands-on consulting (C) validates the methodology → SaaS (A) scales it to more teams → compliance API (B) serves enterprise needs. +**The flow:** Open standard (A) builds the language and community → hands-on consulting (B) validates the methodology → SaaS (C) scales it to more teams → compliance API (D) serves enterprise needs. --- -## Phase 1 — Establish the Standard (D + C) +## Phase 1 — Establish the Standard (A + B) **Goal:** SpeckDL is real, public, and proven in at least one real system. -### Plan D Actions +### Phase A Actions - **Open-source SpeckDL** under Apache 2.0 or MIT - Publish the language spec, a minimal reference compiler, and Z3 verification example @@ -29,7 +29,7 @@ Plan D (open standard + foundation) is the **engine**. All revenue flies by on t - **Create a Speckl playground** — browser-based spec editor with compiled output + provenance graph - **Register domains**, set up minimal site -### Plan C Actions +### Phase B Actions - **Sign consulting engagements** with regulated-industry companies - Deliverable: a functioning Speckl system + trained team + full compliance traceability @@ -40,11 +40,11 @@ Plan D (open standard + foundation) is the **engine**. All revenue flies by on t --- -## Phase 2 — Build the SaaS (A, fed by D + C) +## Phase 2 — Build the SaaS (C, fed by A + B) **Goal:** Self-serve Speckl dev tool with paying users. -### Plan A Launch +### Phase C Launch - **Speckl SaaS** — hosted platform where teams write Specks, the agent harness verifies them, and the platform maintains the provenance graph - **Features:** @@ -53,14 +53,14 @@ Plan D (open standard + foundation) is the **engine**. All revenue flies by on t - TillDone condition tracking - Provenance graph browser -### How D feeds A +### How A feeds C - Open-source SpeckDL means new users arrive already familiar with the DSL - Community contributors find bugs, suggest features, write integrations - The playground converts browsers → SaaS signups - Certification program creates a pipeline of "Speckl Certified" engineers -### How C feeds A +### How B feeds C - Consulting case studies validate the product for prospects - Consulting engagements expose real-world requirements that shape the roadmap @@ -68,28 +68,28 @@ Plan D (open standard + foundation) is the **engine**. All revenue flies by on t --- -## Phase 3 — The Compliance API (B, fed by A) +## Phase 3 — The Compliance API (D, fed by C) **Goal:** Enterprise compliance product with real provenance graph data. -### Plan B Launch +### Phase D Launch - **Speckl Compliance API** — a standalone API that plugs into existing CI/CD - Ingest: spec documents, requirements, code - Output: compliance evidence bundles, traceability matrices, audit-ready reports - Compliance packs for regulated domains (DO-178C, IEC 62304, SOC 2, ISO 26262) -### How A feeds B +### How C feeds D - SaaS users generate real provenance graph data at scale - SaaS feature requests reveal what compliance officers need -- SaaS revenue funds B development during long enterprise sales cycles +- SaaS revenue funds D development during long enterprise sales cycles -### How D continues feeding +### How A continues feeding - The open standard is the market's trust signal - Standards bodies adopt Dark Provenance methodology -- Speckl certification becomes a credential, and B product becomes the tool certified teams use +- Speckl certification becomes a credential, and D product becomes the tool certified teams use --- @@ -108,9 +108,9 @@ Plan D (open standard + foundation) is the **engine**. All revenue flies by on t | Phase | North Star Metric | |-------|------------------| -| **1 (D+C)** | Specks written on the open standard | -| **2 (A)** | Provenance graphs created (SaaS) | -| **3 (B)** | Compliance reports exported | +| **1 (A+B)** | Specks written on the open standard | +| **2 (C)** | Provenance graphs created (SaaS) | +| **3 (D)** | Compliance reports exported | --- diff --git a/landing/index.html b/landing/index.html index 3932772..647b566 100644 --- a/landing/index.html +++ b/landing/index.html @@ -245,19 +245,19 @@
-

Phase D — Now

+

Phase A — Now

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

-

Phase C — Parallel

+

Phase B — Parallel

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

-

Phase A — 3-9mo

+

Phase C — 3-9mo

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

-

Phase B — 9-18mo

+

Phase D — 9-18mo

Compliance API: Audit reports, traceability matrices.