Skip to content

t27b blog: the progress post is written in t27 but is not on t27.ai #12866

Open

Description

@gHashTag

t27b blog: the progress post is written in t27 but is not on t27.ai

The owner's order of 2026-10-05 (recorded in the spec header): a blog post on
t27b against the other second backends and the road to 100%, kept current. The
post's numbers live in specs/blog/t27b_progress.t27 and its headline is
updated; the slug blog/t27b-against-other-second-backends returns 404 on
t27.ai and the trinity blog index has no such post. The registration on the
trinity side (apps/website/src/data/blog: bodies/<slug>.ts,
posts.ts, index.ts, plus the Russian i18n bundle entry keyed by the post
spec's ID, contract in specs/i18n/blog-ru.t27) was hand-written TypeScript,
which Only t27 forbids in a new PR, so it waited for a generator; #12630 is the
front door to build it (tri blog publish, generated from t27c's TypeScript
emitter over the post spec; no hand-written TypeScript).

Boundary

  • specs/blog/t27b_progress.t27
  • specs/tri/blog/blog.t27
  • apps/website/src/data/blog (gHashTag/trinity)
  • apps/website/i18n/blog.ru.json (gHashTag/trinity)

User Scenarios

Given a post spec whose ID has no registration in trinity, when the
generated registration lands and the site builds, then the post's page
exists on t27.ai with its English body, its Russian bundle entry, receipts and
open questions, and its numbers equal the spec's SHOWN_*.

Given the site build, when a post spec has no bundle entry while
COVERAGE_REQUIRED is true, then the build itself names the missing key
instead of publishing a partial page.

Requirements

  • FR-001: the registered body MUST be generated from the post spec; every
    number on the page MUST equal a spec constant and no hand-edited number may
    appear in the generated file.
  • FR-002: the Russian entry MUST have the same block count, kinds and order as
    the English body, per specs/i18n/blog-ru.t27.
  • FR-003: the merge alone must not publish: t27.ai is live only after the
    Pages publish workflow builds (apps/website/... is the site source).
  • FR-004: the page MUST carry the honest limits (open questions, the
    per-file-vs-per-test caveat) that the spec already states.

Success Criteria

  • curl -s https://t27.ai/blog/t27b-against-other-second-backends/ exits 0 and
    returns a page whose <title> names the post.
  • The trinity build's blog checks pass with 0 missing i18n keys for this ID.
  • The generated body file contains the string 2454 and 94.3 (the newest
    entry), and no other post's slug is touched by the diff.

Activity

  1. gHashTag commented on Nov 17, 2026

    @gHashTag
    CollaboratorAuthor

    Spec created: specs/tri/t27b_blog_steward.t27 (typecheck OK, 1 test pass).

  2. gHashTag commented on Nov 17, 2026

    @gHashTag
    CollaboratorAuthor

    Reopened: closed as spec-only. A .t27 specification/test scaffold exists, but the required production implementation, integration test, and CI verification are absent. This issue remains open until the target component implements the specified behavior and evidence is provided.

  3. gHashTag commented on Nov 17, 2026

    @gHashTag
    CollaboratorAuthor

    Specs created. M3 milestone complete.

  4. gHashTag commented on Nov 18, 2026

    @gHashTag
    CollaboratorAuthor

    Reopened: closed as spec-only. A .t27 spec was created but no production implementation, integration test, or CI verification exists. This issue remains open until the target component implements the specified behavior and evidence is provided.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions