Scott Scoble
2ede8445e4
whitepaper v2: Section 5 - Consensus Protocols in SpeckDL (~2,800 words)
...
Deploy Landing Page to Storj / deploy (push) Failing after 2s
- 2PC, Paxos, Raft case studies with full protocol descriptions
- Why consensus protocols are ideal SpeckDL case studies
- Per-protocol: state model, action breakdown, safety invariants
- TLA+ vs SpeckDL side-by-side comparison table
- Raft bridging from academic consensus to production (etcd/Consul)
- Natural progression: 2PC → Paxos → Raft → TigerBeetle curriculum
- Sections complete: 1-5 of 8
2026-05-06 21:14:57 -07:00
Scott Scoble
322d54781a
whitepaper v2: Section 4 — Embedded Provenance (~2,000 words)
...
Deploy Landing Page to Storj / deploy (push) Failing after 2s
Covers: supply chain blind spot problem, provenance-by-construction approach,
PROV-O audit trail (Turtle example), CycloneDX SBOM (JSON example),
SPDX license metadata (JSON example), NIST SA-11 control mapping,
5 design implications of provenance as first-class compiler concern.
2026-05-06 20:08:18 -07:00
Scott Scoble
fa896dec77
whitepaper v2: Section 3 - Compiler Architecture (~2,500 words)
...
Deploy Landing Page to Storj / deploy (push) Failing after 2s
Covers full compilation pipeline: parser (~850 lines), AST design, all 5
generators (PROV-O, CycloneDX, SPDX, TypeScript, WASM), WASM host runtime,
test infrastructure (41 tests, 3 suites), and architectural design decisions
(TypeScript throughout, zero external services, independent generators,
text-first WASM, DIST DESYNC guard, CLI-first).
Sections 1-3 complete; 4-8 remain.
2026-05-06 19:07:12 -07:00
Scott Scoble
66ecdd69b9
whitepaper v2: Section 2 - SpeckDL language specification
...
Deploy Landing Page to Storj / deploy (push) Failing after 2s
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
...
Deploy Landing Page to Storj / deploy (push) Failing after 3s
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
Scott Scoble
d03b5b41a6
docs: add Show HN announcement post draft
...
Deploy Landing Page to Storj / deploy (push) Failing after 2s
Ready-to-publish HN announcement covering:
- Spec-first development pitch (spec-code drift problem)
- 5-artifact compilation (TS, WASM, PROV-O, CycloneDX, SPDX)
- Example suite: ToggleSwitch → Raft, TLA+ comparison table
- Tech stack, roadmap, publishing tips
Content asset for HN, Reddit, Dev.to distribution
2026-05-06 16:06:46 -07:00
Scott Scoble
bba95b70af
docs: Speckl by Example tutorial — guided tour from ToggleSwitch to Raft
...
Deploy Landing Page to Storj / deploy (push) Failing after 3s
Covers ToggleSwitch → AccountLedger → TwoPhaseCommit → Raft
with progressive introduction of SpeckDL concepts:
- state/init/action/invariant structure
- Map, Set, List types with operations
- require guards, let bindings, emit events
- quantified invariants and safety properties
- multi-role distributed protocols
- TLA+ comparison table
- compilation pipeline diagram
2026-05-06 15:07:22 -07:00
Content Agent
362548caad
refactor: rename phases to sequential A→B→C→D
...
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
2026-04-28 21:09:42 -07:00
Content Agent
bba505a7a3
refactor: remove marketing/pricing docs to private repo
...
Moved to sscoble/speckl-marketing (private):
- consulting-packages.md (pricing, ICP, pipeline)
- business-brief.md (competitive positioning, revenue model)
- content-calendar.md (content schedule)
- warp-monitoring.md (competitor tracking)
- warp-engagement.log (engagement log)
- blog/2026-04-28-why-dark-provenance.md (marketing manifesto)
- PUSH_SUMMARY.md (campaign tracking)
Also scrubbed strategy.md of all pricing, budgets, revenue targets,
and competitive details. Full version in speckl-marketing repo.
2026-04-28 16:35:50 -07:00
Content Agent
2fe706436d
fix: clean up architecture and plan-flow SVGs — simpler connector routing, tighter arrow spacing
2026-04-28 16:24:11 -07:00
Content Agent
0ea2204d5b
fix: compact speckdl-pipeline.svg — was way too tall for a 4-box flow
2026-04-28 16:15:42 -07:00
Content Agent
c9b746d7d4
fix: redo consulting-pipeline.svg — proper arrows and layout
2026-04-28 16:14:35 -07:00
Content Agent
7b3a09f48a
fix: redo plan-flow.svg — fix overlapping elements and arrow connections
2026-04-28 16:13:20 -07:00
Content Agent
f59488a197
feat: replace ASCII art diagrams with SVG
...
- README: SpeckDL pipeline and architecture diagrams
- docs/strategy.md: Plan D→C→A→B flow diagram
- docs/consulting-packages.md: consulting pipeline flow diagram
- New: docs/diagrams/ with 4 static SVGs (dark-mode compatible, responsive viewBox)
2026-04-28 16:01:00 -07:00
Content Agent
4f75737b15
chore(content): Add Warp engagement log for tracking interactions
2026-04-28 15:37:39 -07:00
Content Agent
288cad0dda
feat(content): Add build-in-public manifesto and content calendar
...
- docs/blog/2026-04-28-why-dark-provenance.md: First blog post explaining the vision
- docs/content-calendar.md: 2-week content plan with themes and targets
- docs/warp-monitoring.md: Process for monitoring Warp and engaging thoughtfully
Part of the build-in-public campaign for Speckl (Dark Provenance for AI agents).
2026-04-28 15:37:33 -07:00
7297b5ec58
feat: whitepaper sections 2-6, README overhaul, SpeckDL spec v0.1, reference agent scaffold
...
- Dark Provenance whitepaper: complete sections 2-6 (What Is Dark Provenance,
The Speckl Approach, Semantic Preservation & SA-11, Implications, Call to Action)
- README: public launch-ready with architecture, roadmap, getting started
- SpeckDL SPEC.md: v0.1 language specification with EBNF grammar,
type system, compilation pipeline, 5 example Specks
- Reference agent: TypeScript scaffold with Orchestrator, TeamLead, SMEs
(VerificationSME, CodegenSME), TillDone condition tracking,
ProvenanceGraph, and CLI with example Specks
2026-04-28 09:33:48 -07:00
fedecf6c3f
feat: add strategy, business brief, consulting packages, and dark provenance whitepaper draft
2026-04-28 09:08:53 -07:00
Marcus (@cos)
a97a532a3c
Initial commit: Speckl project scaffold
...
- MIT license
- README with project overview, Dark Provenance intro, and structure
- Empty directories: speckdl/, reference-agent/, examples/
- Placeholder whitepaper with Dark Provenance outline
Parent: Greybeard Holdings, LLC
Status: Early / Pre-Alpha
2026-04-28 01:20:22 -07:00