Skip to content

t27b as an application host: the server and storage specs it rejects today (measured) #8944

Open

Description

@gHashTag

Measured 2026-10-11 on master 3733ff1 (arm64 macOS), t27b test <spec>. Context: gHashTag/turbobaby-user-bot#77 / #78 plans an app (HTTP + Postgres + Telegram webhook + S3) whose rules run from .t27; this is what stands between t27b and hosting it.

Spec First rejection Lane in #6063
specs/server/http.t27 type mismatch at 447: expected [16]u8, found a string memory lane (strings)
specs/server/sse.t27 type mismatch at 574: expected []u8, found a string memory lane (strings, slices)
specs/server/routes.t27 == on HttpMethod and a scalar (line 26) scalar lane (enums)
specs/server/session.t27 [ToolCall{};8] array of structs (line 259) memory lane (fixed arrays) + #6044
specs/storage/kv.t27 call to exists, whose declaration was rejected (153) follows from the above
specs/storage/migrate.t27 call to set_version, declaration rejected (284) follows from the above
specs/tri/net/http.t27 @ptrFromNull builtin (309) builtins
specs/network/mvp.t27 undeclared fn placements_needed (1181) spec defect, not t27b

Passing for contrast: queen/actors.t27 37/37, queen/keyed.t27 8/8, queen/dispatch.t27 6/6.

Done when: each row above is either passing under t27b test or names the PR/issue that will make it pass. Two host duties have no lane at all and are filed separately: ELF output and an I/O boundary.

Refs #6063

User Scenarios

  • Given a developer runs t27b test specs/server/http.t27, When the compiler processes the spec, Then it must pass without type mismatch errors on string literals at line 447.
  • Given a developer runs t27b test specs/server/routes.t27, When the compiler processes enum comparisons, Then it must accept == between HttpMethod and scalar values at line 26.
  • Given a developer runs t27b test specs/storage/kv.t27, When the compiler resolves declarations, Then it must accept calls to exists and set_version whose declarations previously failed.

Requirements

FR-001: The compiler MUST accept string literals where [16]u8 or []u8 are expected in server specs.
FR-002: The compiler MUST allow == comparison between enum types (HttpMethod) and scalar values.
FR-003: The compiler MUST support fixed-size arrays of struct literals (e.g., [ToolCall{};8]).
FR-004: The compiler MUST implement the @ptrFromNull builtin for specs/tri/net/http.t27.
FR-005: The compiler MUST resolve forward declarations so that exists and set_version calls compile in storage specs.
FR-006: The spec defect in specs/network/mvp.t27 (undeclared placements_needed) MUST be fixed in the spec itself.

Success Criteria

  • t27b test specs/server/http.t27 exits 0
  • t27b test specs/server/sse.t27 exits 0
  • t27b test specs/server/routes.t27 exits 0
  • t27b test specs/server/session.t27 exits 0
  • t27b test specs/storage/kv.t27 exits 0
  • t27b test specs/storage/migrate.t27 exits 0
  • t27b test specs/tri/net/http.t27 exits 0
  • t27b test specs/network/mvp.t27 exits 0
  • 8 specs passing under t27b test that previously rejected

Boundary

  • specs/server/http.t27
  • specs/server/sse.t27
  • specs/server/routes.t27
  • specs/server/session.t27
  • specs/storage/kv.t27
  • specs/storage/migrate.t27
  • specs/tri/net/http.t27
  • specs/network/mvp.t27
  • scripts/tri_loop/t27b.py
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions