Skip to content

Collaboration proposal: RFI-IRFOS / ternlang ↔ Tern Systems #8

@eriirfos-eng

Description

@eriirfos-eng

Hello from RFI-IRFOS — ternlang

We are building ternlang (repo), a balanced ternary systems-programming language and compiler stack targeting the same domain as Tern Systems. When we discovered your organization today we had the same reaction: why fight over an empty field when we could cultivate it together?

What we have

Component Status
ternlang-core — lexer, parser, semantic analysis complete
ternlang-codegen — AST → C transpiler + BET VM bytecode emitter complete
BET VM — balanced ternary virtual machine (register-based, 32 regs) complete
ternlang-hdl — Verilog-2001 RTL codegen for ternary hardware complete
ternlang-lsp — LSP 3.17 hover / completion / diagnostics complete
ternlang-ml — BitNet quantization + sparse ternary matmul complete
BET ISA Spec (BET-ISA-SPEC.md) — 2-bit packed trit encoding, full opcode table published
REST API + MCP server (ternlang.com) live on Fly.io
VS Code extension (Open VSX: rfi-irfos/ternlang) v0.4.0 published

What we would love

  1. TERN assembly spec — We want to add a --emit-tern backend so ternlang programs can output TERN-compatible assembly. We are already building a RISC-V-inspired ternary ASM emitter; aligning with your spec would make the output genuinely interoperable.
  2. BTMC format — We could add a BTMC-compatible serialisation layer in ternlang-hdl.
  3. Shared ecosystem docs — Jointly defining trit encodings, instruction naming conventions, and ABI rules would benefit every future ternary project.

What we offer in return

  • Full open access to our BET ISA spec, VM internals, and HDL codegen
  • Cross-linking between ecosystems (README, docs, Smithery MCP listing)
  • Contributing to your coding-guidelines.md or shared ISA documentation
  • Potential co-authorship on any academic/ecosystem positioning

Next step

Happy to share a private preview of our TERN-ASM draft the moment you can point us at your spec, even informally. We can also just start a joint document.

Contact: rfi.irfos@gmail.com | https://ternlang.com | @eriirfos-eng

— Simeon / RFI-IRFOS

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions