Files
Socrates/phase-0/seeds/06-eventstream.json
dtoro f1c4566576 Initial commit — design docs + Phase 0 validation harness
Sets up the Socrata project repo with:

docs/ — strategy and design documents
  - idea.md: full product vision
  - implementation-plan.md: Phase 0 + Phase 1 MVP plan
  - phase-0-validation.md: 2-week validation experiment strategy
  - phase-0-plan.md: concrete Phase 0 build plan
  - phase-0-results.md: Phase 0 gate outcome — GO for MVP
  - sysml-modeling.md: metamodel + SE discipline + validation rules
  - socrates.md: agent character, surfaces, modes, prompts, lifecycle
  - sync.md: bidirectional text↔diagram sync engineering
  - design-source/: HTML/CSS/JS handoff bundle from Claude Design

phase-0/ — validated harness (CLI, no UI, no DB)
  - LM Studio (local OpenAI-compatible) generation + detection + judge
  - PlantUML rendering for SysML model visualization
  - 10-seed corpus (8 working + 2 holdouts)
  - 5 corpus runs with iteration history in reports/
  - Final gate: 10/10 pass, mean 4.32/5, holdouts validated

Phase 1 MVP scope and milestones documented in implementation-plan.md.
2026-04-28 22:07:38 +02:00

19 lines
1.3 KiB
JSON
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
{
"id": "06-eventstream",
"title": "EventStream",
"problem": "Existing event-streaming systems (Kafka, Pulsar, Redpanda) treat backpressure as an afterthought — slow consumers either drop messages, lag indefinitely, or trigger broker-level fan-out failures. Modern application workloads (especially LLM-pipelined ones) need first-class backpressure semantics that the producer can observe in-band.",
"targetUser": "Platform engineers at companies running event-driven infrastructure at moderate scale (100k10M events/day) where consumer lag matters and Kafka's operational complexity is unwelcome.",
"desiredOutcome": "A Go-native streaming system where producers receive backpressure signals as a first-class part of the protocol, and consumer-driven flow control is the default.",
"initialHypothesis": "Teams will adopt a Kafka alternative if (a) operations are 10× simpler — single binary, no ZooKeeper, no Schema Registry — and (b) backpressure is a first-class protocol feature, not a config flag.",
"constraints": [
"Wire-compatible with Kafka producer protocol for migration safety",
"Single binary, single config file, runs on a single node up to 100k events/sec",
"Apache 2.0 license"
],
"meta": {
"isHoldout": false,
"expectedDifficulty": "hard",
"testsFor": ["technical", "infra", "metamodel-strain"]
}
}