2 commits

Author	SHA1	Message	Date
Scott Scoble	66ecdd69b9	whitepaper v2: Section 2 - SpeckDL language specification ... Full technical writeup covering: - Design philosophy (spec as source of truth, state machines, type-safe, emit) - Structure of a speck (types, state, init, invariant, action, next) - Type system (Bool, Nat, Int, String, Set, Map, List, Records, Optional) - Actions (require, assignments, let bindings, if, emit, return, forall) - Invariants (documentation + runtime verification, quantified, logical ops) - Action composition (next: non-deterministic interleaving) - Complete Two-Phase Commit example (48-line spec) - What SpeckDL deliberately omits (no functions, no loops, no concurrency, no I/O, no error handling) - ~2,000 words	2026-05-06 18:07:53 -07:00
Scott Scoble	2ed6c13026	whitepaper v2: Section 1 (The Spec-Code Gap) with executable specs framing ... Rewrites the whitepaper from the old 'Dark Provenance' concept to reflect what Speckl actually is now: specifications that compile to software. Section 1 covers: - The Archaeology Problem (specs that rot in docs) - The Formal Methods Gap (verified spec ≠ running system) - The SpeckDL Approach (compile spec directly to code + provenance) - Concrete ToggleSwitch example (14 lines → 5 artifacts) Whitepaper outline restructured around current compiler capabilities (TypeScript, WASM, PROV-O, CycloneDX, SPDX generators).	2026-05-06 17:07:50 -07:00