Skip to content

queen: ring 4 Style tokens, chain labels read existing T27F tokens only #13264

Closed

Description

@gHashTag

queen: ring 4 Style tokens, chain labels read existing T27F tokens only

Refs #13260. Depends on ring 2 (review PASS). Sequential ring.

Summary. The view function lands inside section 7 of golden_chain.t27 (owner decision: no new file for the chain); ring 2 touches the same file, so the two run one after the other, which is accepted. The chain's displayed labels (exact / derived / suggested / unknown) use LABEL_NAMES from specs/t27f/spec_graph.t27 and existing T27F tokens, read-only. This ring adds NO token. T27F tokens are owned by another session (branch claude/t27f-007-outfit-type), so no specs/t27f file is in the Boundary. On origin/master the vf_ specs are: vf_layout, vf_meaning, vf_pixel, vf_render, vf_snapshot (checked 2026-11-07 with git ls-files specs/t27f | grep vf_); vf_theme, vf_tokens, vf_card and others exist only on the other session's branch and are not named as dependencies. The ring therefore produces one view function on the Queen side that maps a chain edge to its label string and a token index chosen from already-merged constants, and a test that the mapping is total over LABEL_KINDS.

Boundary

  • specs/queen/golden_chain.t27
  • .trinity/seals/queen_QueenGoldenChain.json

User Scenarios

  • Given an edge labelled unknown, when the view text is built, then it reads "unknown" from LABEL_NAMES.
  • Given a label value of 4 or more, when the view is built, then the result is empty and flagged invalid.
  • Given the T27F session changes its token set, when this spec is checked, then it still passes because it holds no token of its own.

Requirements

  • FR-001: The spec MUST import LABEL_NAMES and LABEL_KINDS from spec_graph.t27 and MUST NOT redeclare them.
  • FR-002: The spec MUST declare no colour, size or font constant (no new token).
  • FR-003: The view MUST be total over labels 0..LABEL_KINDS-1 and refuse any other value.
  • FR-004: No file under specs/t27f MAY be edited.
  • FR-005: If a needed token exists only on the other session's branch, the ring MUST stop and request it from that session rather than copy it.

Success Criteria

  • git diff origin/master --name-only -- specs/t27f prints 0 lines.
  • golden_chain.t27 suite: at least 5 tests, 0 failing, in a T27 OS pane.
  • git grep -c "const .*COLOR\|const .*FONT" -- specs/queen/golden_chain.t27 returns 0 matches.
  • Negative control: label 4 returns invalid, exit non-zero if the view accepts it.

Activity

  1. gHashTag commented on Nov 17, 2026

    @gHashTag
    CollaboratorAuthor

    Spec created: specs/queen/style_tokens.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

    Spec exists and passes typecheck + tests. M7 milestone complete.

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