Repository navigation
Update S05 TRI-27 conformance to the emulator fixed in gHashTag/trinity#1250 - #6801
Conversation
…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>
|
This branch conflicts with master on |
|
Thanks for the start on #5614. This branch has been inactive since 2026-10-07 and conflicts with master on Dmitrii Fedorov (@dmitrii-f-t27) |
Summary by t27-beesChecked by the t27 compilert27c parse, parse-complete and typecheck on each changed .t27 file at
Read by the modelThis 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
Read: 3 files, +28 -0, the whole diff. Head |
# Conflicts: # .trinity/seals/isa_Tri27Bytecode.json # .trinity/seals/isa_Tri27Machine.json
PR DashboardGenerated at: 2026-10-22 19:33:50 UTC
Summary
Seal Status
|
Closes #5614
Written by a bee on
queen-5614and published bytools/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.🤖 Generated with Claude Code