Skip to content

Update S05 TRI-27 conformance to the emulator fixed in gHashTag/trinity#1250 - #6801

Merged
gHashTag merged 3 commits into
masterfrom
queen-5614
Oct 22, 2026
Merged

gHashTag merged 3 commits into
masterfrom
queen-5614

Conversation

@gHashTag

@gHashTag gHashTag commented Oct 6, 2026

Copy link
Copy Markdown
Collaborator

Closes #5614

Written by a bee on queen-5614 and published by tools/queen/publish.py. The branch itself is the bee's; the second commit is the coordination entry every pull request must add, which a bee has no way to know about.

4 files changed, 21 insertions(+), 4 deletions(-)

🤖 Generated with Claude Code

Trinity Bee and others added 2 commits October 6, 2026 02:33
…5 specs

Add FIXED_UPSTREAM section to both tri27_machine.t27 and tri27_bytecode.t27
documenting the six findings fixed in e7919fdc (2026-10-02):
- CALL return address (#1165)
- loader packing and pc (#1166)
- header agreement (#1167)
- CONSTANTS layout (#1168)
- modulus labels (#1169)
- SACR immediate (#1170)

PINNED_REVISION, FINDINGS, and FINDING_COUNT remain unchanged as required.
Run t27c parse and t27c typecheck on both specs, then seal both.

Closes #5614
A pull request must add exactly one docs/now entry and a bee has no way
to know that: its brief names a boundary file and acceptance criteria,
and docs/now/ is neither. The publisher adds it rather than failing the
gate.

Closes #5614

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@github-actions

github-actions Bot commented Oct 6, 2026

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-10-06 12:40:03 UTC

Summary

Status Count
Total Open PRs 50
PRs with Failing Checks 41
PRs with All Checks Green 9
READY 1
FAILING 41
PENDING 0
NO CHECKS YET 0

These columns do not partition: 1 + 41 + 0 + 0 = 42, and there are 50 open PRs. A PR is being counted twice or not at all.

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=3c78f3c7ffb7 != manifest seal=87e5cbd3ad94.
    The committed NMSE numbers were certified against an older compiler.rs.
    Run scripts/reseal-check.sh locally for the two-step reseal command (advisory; not a merge gate).

This was referenced Oct 6, 2026
@gHashTag

gHashTag commented Oct 7, 2026

Copy link
Copy Markdown
Collaborator Author

This branch conflicts with master on .trinity/seals/isa_Tri27Machine.json, a real content conflict that GitHub's update-branch cannot resolve (checked with git merge-tree against master at 2026-10-07 ~16:10Z). It is left open for conflict_step (#7571), which redoes it from fresh master once the wiring (#7573) lands.

@dmitrii-f-t27

Copy link
Copy Markdown
Contributor

Thanks for the start on #5614. This branch has been inactive since 2026-10-07 and conflicts with master on .trinity/seals/isa_Tri27Machine.json, so I redid the change from current master in #8876, with tests (vectors measured on the fixed emulator at gHashTag/trinity e7919fdc) and fresh seals. #8876 closes #5614 and supersedes this PR. I am leaving this PR open for its owner to decide.

Dmitrii Fedorov (@dmitrii-f-t27)

@gHashTag
gHashTag enabled auto-merge (squash) October 11, 2026 12:56
@gHashTag
gHashTag disabled auto-merge October 11, 2026 13:02
@gHashTag
gHashTag enabled auto-merge (squash) October 12, 2026 10:42
@gHashTag
gHashTag disabled auto-merge October 12, 2026 10:46
@gHashTag
gHashTag enabled auto-merge (squash) October 22, 2026 15:58
@tri-claw

tri-claw Bot commented Oct 22, 2026 •

Copy link
Copy Markdown

Summary by t27-bees

Checked by the t27 compiler

t27c parse, parse-complete and typecheck on each changed .t27 file at 5487311. Nothing was generated, built or run. A pass means the file is well formed, not that it is right.

  • specs/isa/tri27_bytecode.t27: parses and typechecks.
  • specs/isa/tri27_machine.t27: parses and typechecks.

Read by the model

This PR adds documentation comments to two TRI-27 specification files recording fixes that were made upstream in Trinity-S-AI-DNA/trinity#1250. The changes are purely informational—no code logic is modified.

Worth a look

  • specs/isa/tri27_bytecode.t27:97-103 and specs/isa/tri27_machine.t27:124-133 — The comments state that certain findings "remain pin-scoped to 976df517" while also saying they were "fixed in fix(tri27-emu): repair the six pinned TRI-27 emulator defects (#1164) trinity#1250 (e7919fdc)". If the spec is meant to reflect the fixed emulator behavior, the pin-scoping note could be misleading about which commit the current spec actually matches.

Read: 3 files, +28 -0, the whole diff. Head 5487311. Model: openai-compatible/nvidia/nemotron-3-ultra-550b-a55b. Commands: @t27-bees review | summary | help | pause | resume. Free for every repository.

# Conflicts:
#	.trinity/seals/isa_Tri27Bytecode.json
#	.trinity/seals/isa_Tri27Machine.json
@github-actions

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-10-22 19:33:50 UTC

Summary

Status Count
Total Open PRs 50
PRs with Failing Checks 38
PRs with All Checks Green 12
READY 0
FAILING 38
PENDING 0
NO CHECKS YET 5

These columns do not partition: 0 + 38 + 0 + 5 = 43, and there are 50 open PRs. A PR is being counted twice or not at all.

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=5aec047d42ec != manifest seal=87e5cbd3ad94.
    The committed NMSE numbers were certified against an older compiler.rs.
    Run scripts/reseal-check.sh locally for the two-step reseal command (advisory; not a merge gate).

@gHashTag
gHashTag merged commit af54477 into master Oct 22, 2026
37 of 45 checks passed
@gHashTag
gHashTag deleted the queen-5614 branch October 26, 2026 06:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Update S05 TRI-27 conformance to the emulator fixed in gHashTag/trinity#1250

3 participants