shoney/writeonce
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
writeonce/docs/stories/language-runtime-database/25-http-service.md
shoney.arickathil 5521d21a84 docs: pending iterations renumbered by dependency + priority 
- developer directive: pending iteration IDs now ARE the priority order;
  LANDED iterations keep historical numbers (code comments and commit
  history cite them — records, not a queue); 8/11 (the half-landed
  arc), 17 (parked, artifacts on a branch), 18 (next, artifacts named)
  also frozen
- mapping (recorded in 00-story): 19<-20 Float+Bytes, 20<-9c attach,
  21<-9d keypair, 22<-9e benchmarks, 23<-9f io_uring WAL, 24<-19 chat,
  25<-10 services, 26<-12 blue-green, 27<-9g query corpus,
  28<-14 skillhost, 29<-13 metaprogramming
- 11 story files renamed; every doc reference re-numbered (word-boundary
  sweep for the lettered 9x ids, phrase-level for numeric ones); the
  iterations table rewritten with Seq == priority and "(was N)" notes;
  story-scoped link check: zero broken
- merge-recovery folded in: the partial master merge had dropped the
  chat story, the fibers exploration note, the arc spec+plan, the
  framework-v2 plan, and the iteration-17 spec+plan — all restored from
  their branches and renumbered consistently

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-08-20 14:31:09 +02:00

2.1 KiB
Raw Blame History

Iteration 25 — HTTP service layer

Format: product/story-iteration-template. Part of Story — one language, one runtime, one database, one binary.

Goals

  • The single binary serves: service rest blocks compile to routes and the runtime answers HTTP from its shards — hand-rolled HTTP and JSON, zero libraries, per the dependency doctrine.
  • The new stack reaches feature parity with the Rust runtime's Stage 2 REST surface — the concrete bar the retirement decision measures against.

Acceptance Criteria

  • What to achieve?
    • Given the blog sample's service declarations,
    • when the compiled binary boots and reference/rest/blog.rest runs against it,
    • then every request in the smoke file answers as documented — including the intentional 501/405/404 responses.
  • What to achieve?
    • Given a method call arriving over REST that traps (borrow violation, abort, unique violation),
    • when the response returns,
    • then exactly one trap-to-HTTP table governs the mapping (e.g. conflict-shaped 409s) and the structured error body carries the trap record — the same trap surface everywhere, now over the wire.
  • What to achieve?
    • Given transports declared at boot,
    • when the runtime starts under systemd socket activation or with zero listeners,
    • then both boot correctly — a runtime is not tied to a port.

Out Of Scope

  • WebSocket/live subscriptions and UI (the parked ##ui story).
  • The management plane endpoints (iteration 11 builds them on this machinery).

Info

  • Route declarations ride the .wob format as a versioned section — a coordinated format bump, the pattern later sections follow.
  • The C reference's phase-C HTTP machine is the porting source.

Proposed Solution

  • Execute the existing plan: docs/superpowers/plans/2026-08-01-http-service-layer.md (per-shard http module, hand-rolled JSON codec, service-block route section, Stage-2-parity CRUD, method RPC with the trap table, blog.rest smoke).