Skip to content

πŸ“– Ch.12 β€” Hardware Bridge (KOSCHEI ISA + FPGA prototype, academic-tone, deferred v3.0)Β #393

@gHashTag

Description

@gHashTag

Ch.12 β€” Hardware Bridge (FPGA / KOSCHEI)

Master: trios#380 GOLDEN SUNFLOWERS Book
Priority: βšͺ P2 defer Β· Word target: 500 Β· Owner: defer post-hackathon

🎯 Scope (FROZEN)

FPGA iCE40 GF16 ALU implementation (existing in t27/gen/). KOSCHEI opcode 0xD6 (TEMPORALTRITQUERY). Power/area numbers vs IEEE/MX. Why this matters for edge inference.

πŸ”‘ Key claims / formulas

  • iCE40 GF16 ALU LUT count vs FP16 ALU
  • KOSCHEI 0xD6 single-cycle TEMPORALTRITQUERY
  • Power: estimated mW per op
  • Area: gates per format

πŸ“¦ Deliverables

  • paper/sections/12_hardware_bridge_fpga__koschei.tex
  • Defer for hackathon submission (not in 16MB scope)
  • Reserve for arXiv v2 paper post-hackathon

πŸ”— Dependencies

  • Ch.4 GoldenFloat

πŸ“ Draft (Markdown β€” paste here when ready)

Operator types Π½Π°ΠΏΠΎΠ»Π½ΠΈ Ch.12 β†’ General fills this section with research-backed Markdown.

βœ… Definition of Done (NeurIPS checklist aligned)

  • Word count 500 Β±10%
  • All claims cited (primary literature, not just our repos)
  • No AI as author (Acknowledgments only)
  • Compiles in main.tex via tectonic, no warnings
  • Limitations stated (where applicable)
  • Reproducibility info present (where applicable)
  • PR with Closes #<this> + green CI
  • L1 (no .sh) Β· L3 (clippy zero) Β· L4 (tests pass) Β· L8 (PUSH FIRST)

πŸ€– ONE-SHOT directive (ΠΊΠΎΠ³Π΄Π° operator typed ONE SHOT Ch.12)

A CHAPTER-AGENT: take Markdown draft from this issue body Β§"Draft", convert to LaTeX,
place in paper/sections/12_<slug>.tex, ensure compile via tectonic with main.tex,
open PR linked to #, run cargo clippy/test, push, request review.
Hard deadline per priority (P0 β†’ T-3h, P1 β†’ T-1h, P2 β†’ defer).

phi^2 + phi^-2 = 3 Β· TRINITY Β· NEVER STOP

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions