sscoble/speckl
1
0
Fork 0
Code Issues 2 Pull requests Projects Releases Packages Wiki Activity Actions
90 commits 8 branches 0 tags 20 MiB
Commit graph

33 commits

Author SHA1 Message Date
Marcus (agent-cos)
506c192b77 docs: update plan with M0.3 completion and M1.2 status
Some checks failed
Deploy Landing Page to Storj / deploy (push) Failing after 2s
Details
2026-05-09 23:10:31 -07:00
Marcus (agent-cos)
6ea0aef76b docs: update PROVE-KAFKA-PLAN with milestone completions 
M0.1 ✅, M0.2 ✅, M1.1 research ✅, M3.1 draft ✅, M4.3 ✅
Next: M0.3 (Z3 backend) unblocks M1.2, M3.2, M4.3 verification
 2026-05-09 22:09:27 -07:00
Scott Scoble
03de892259 docs: comprehensive KRaft protocol reference for speckl#22 
M1.1 research deliverable — detailed reference document covering:

- Complete Raft state machine (TLA+ spec): 10 actions with preconditions
- KRaft state hierarchy: 7 states (Unattached, Prospective, Candidate,
  Follower, Leader, Resigned, Detached) with per-state variables
- Detailed transition table with triggers and preconditions
- Pre-Vote protocol (KIP-996) mechanics and verification targets
- Resignation protocol (graceful leader step-down)
- 6 vanilla Raft invariants (I1-I6) formalized for Z3
- 6 KRaft-specific invariants (K1-K6) including observer consistency
- Snapshot invariants (KIP-630)
- 4 known Raft/KRaft bugs with verification targets
- 7 open verification targets for SpeckDL/Z3
- Producer acks and consumer group semantics (deferred to M1.3)
- Message types and KIP reference table
 2026-05-09 21:54:09 -07:00
Marcus (agent-cos)
1d536136b8 docs: KRaft protocol reference for M1.1 spec writing 2026-05-09 21:51:35 -07:00
Marcus (agent-cos)
6e770de885 =docs: add issue tracking table (#18-#32), close epic #17 2026-05-09 21:43:18 -07:00
Marcus (agent-cos)
7928c2b1da docs: Prove Kafka project plan (4 phases, 12 milestones, dependency graph only) 2026-05-09 21:40:21 -07:00
Scott Scoble
bc067d239c docs: Show HN demo script — 2-min terminal recording walkthrough for launch day
Some checks failed
Deploy Landing Page to Storj / deploy (push) Failing after 2s
Details
2026-05-09 07:11:50 -07:00
Scott Scoble
31fcbce425 docs: Show HN launch day operations checklist — minute-by-minute runbook for May 12-13
Some checks failed
Deploy Landing Page to Storj / deploy (push) Failing after 2s
Details
2026-05-09 02:09:22 -07:00
Scott Scoble
ea8392f7db docs: Show HN comment response playbook — 14 pre-written replies for launch day
Some checks failed
Deploy Landing Page to Storj / deploy (push) Failing after 2s
Details
2026-05-09 01:08:36 -07:00
Scott Scoble
45ee6fc1bc docs: sync Phase 2 content pipeline — all 5 blog posts + publishing toolkit
Some checks failed
Deploy Landing Page to Storj / deploy (push) Failing after 2s
Details 
blog-01: Spec-Code Drift Is a Provenance Problem (~1,500 words)
blog-02: Designing SpeckDL (~1,800 words)
blog-03: How Speckl's Compiler Works (~1,900 words)
blog-04: Embedded Provenance (~1,200 words)
blog-05: Consensus Protocols in SpeckDL (~1,300 words)
publishing-toolkit: Dev.to/Medium/Reddit/HN formatting + objection prep (~3,500 words)

Total Phase 2 pipeline: ~11,200 words across 6 files.
Previously existed only in workspace copy (posts 1/3/toolkit) or
as untracked files (posts 2/4/5). All now committed to Forgejo.
 2026-05-09 00:11:29 -07:00
Scott Scoble
44a8406855 docs: distribution strategy — prioritized roadmap from Show HN to consulting
Some checks failed
Deploy Landing Page to Storj / deploy (push) Failing after 2s
Details 
P0: Show HN May 12-13 (post ready)
P1: arXiv preprint + 5-part blog series from whitepaper
P2: 2027 conference targets (FMCAD, FM, ICSE, ASE, NFM, SPLASH)
P3: QCon SF talk proposal (~Jun 2026)
P4: TOSEM/JAR journal (rolling submissions)
P5: Cold email → first consulting client (summer 2026)

Includes verified 2026/2027 conference deadlines, blocker inventory (7 items),
decision framework by Show HN traction tier, and anti-patterns.
 2026-05-07 21:06:35 -07:00
Scott Scoble
6121fd6a8f Whitepaper v2 Section 8: Future Work & Roadmap (~2,900 words)
Some checks failed
Deploy Landing Page to Storj / deploy (push) Failing after 1s
Details 
Completes the whitepaper. Covers:
- 8.1 Compiler completeness (record types, action bodies, in operator, Map ops, host binding, TigerBeetle E2E)
- 8.2 Language extensions (temporal properties, function types, modules, parametric types)
- 8.3 Tooling ecosystem (LSP, IDE plugins, package registry, CI/CD)
- 8.4 Strategic roadmap (Open Standard → Consulting → SaaS → Compliance API)
- 8.5 What Will Not Change (small language, mandatory provenance, MIT, evidence over proof)
- Conclusion: the case for accountable software

All 8 sections complete. ~19,000 words total.
 2026-05-07 01:14:24 -07:00
Scott Scoble
940b959efb Whitepaper v2 Section 7: Related Work (~2,500 words)
Some checks failed
Deploy Landing Page to Storj / deploy (push) Failing after 2s
Details 
Comprehensive comparison of SpeckDL against:
- TLA+/PlusCal (model checking vs. runtime compilation)
- Alloy (structural vs. behavioral modeling)
- Coq/Rocq (static proofs vs. dynamic enforcement)
- Dafny (verified code vs. spec-as-code)
- Event-B, UML/SysML, P (Microsoft), OpenAPI/gRPC
- SBOM tools: Syft/Grype, SLSA, in-toto

Includes positioning table across 7 tools on 6 dimensions.
Defines niche: specification language with compiler-level provenance,
designed for teams that need evidence of correctness more than proof.
 2026-05-07 00:18:59 -07:00
Scott Scoble
627c46235c whitepaper: Section 6 — Compliance & Supply Chain Security (~2,800 words)
Some checks failed
Deploy Landing Page to Storj / deploy (push) Failing after 2s
Details 
Covers: regulatory landscape (EO 14028, CRA, DORA, FedRAMP), NIST SA-11 control
mapping (sub-controls 2/4/6/7), the evidence problem, compliance automation workflow,
judgement transport model, 4 real-world use cases (FDA, CISA, DORA, SLSA), clear
boundaries on what Speckl does not do, and cost equation with before/after comparison.
Completes the bridge between provenance (S4) and practical regulatory value.
 2026-05-06 22:07:06 -07:00
Scott Scoble
2ede8445e4 whitepaper v2: Section 5 - Consensus Protocols in SpeckDL (~2,800 words)
Some checks failed
Deploy Landing Page to Storj / deploy (push) Failing after 2s
Details 
- 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)
Some checks failed
Deploy Landing Page to Storj / deploy (push) Failing after 2s
Details 
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)
Some checks failed
Deploy Landing Page to Storj / deploy (push) Failing after 2s
Details 
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
Some checks failed
Deploy Landing Page to Storj / deploy (push) Failing after 2s
Details 
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
Some checks failed
Deploy Landing Page to Storj / deploy (push) Failing after 3s
Details 
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
Some checks failed
Deploy Landing Page to Storj / deploy (push) Failing after 2s
Details 
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
Some checks failed
Deploy Landing Page to Storj / deploy (push) Failing after 3s
Details 
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
Scott Scoble
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
Scott Scoble
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