Post
194
✅ New Guide: *Writing Your First SIL Program (v0.1)*
Title:
✍️ Writing Your First SIL Program for SI‑Core
🔗 https://huggingface.co/blog/kanaria007/writing-your-first-sil-program
---
Summary:
You can write logic in Go/Rust/Python — but *SIL* is built for something extra:
making SI-Core able to answer *“Was this deterministic?”*, *“Which constraints fired?”*, and *“Can we replay/roll back this decision?”* *without guessing*.
This guide walks a tiny, real example end-to-end: a
> “Hello, Structured World” isn’t a print statement —
> it’s a decision you can audit, replay, and reason about.
---
Why It Matters:
• Learn the *layered mental model*: deterministic core vs constraints vs goals vs adaptive glue
• Understand what SIR /
• See the *practical toolchain*: compiler output, diagnostics JSONL, golden diff, SCover checks
• Get an engineer-friendly workflow that fits CI, not a research demo
---
What’s Inside:
*Build a tiny feature in SIL* (floodgate offset example)
•
•
•
*Compile artifacts*
•
•
•
*How CI proves you didn’t break structure*
• Golden SIR diff
• Structural coverage (SCover) checks
• Practical debugging patterns for early compiler/toolchain bring-up
---
📖 Structured Intelligence Engineering Series
Normative details live in the compiler spec + conformance kit; this one is the *hands-on* path.
Title:
✍️ Writing Your First SIL Program for SI‑Core
🔗 https://huggingface.co/blog/kanaria007/writing-your-first-sil-program
---
Summary:
You can write logic in Go/Rust/Python — but *SIL* is built for something extra:
making SI-Core able to answer *“Was this deterministic?”*, *“Which constraints fired?”*, and *“Can we replay/roll back this decision?”* *without guessing*.
This guide walks a tiny, real example end-to-end: a
.sil file, compiled into *SIR* + *.sirrev*, then called from a minimal runtime wrapper.> “Hello, Structured World” isn’t a print statement —
> it’s a decision you can audit, replay, and reason about.
---
Why It Matters:
• Learn the *layered mental model*: deterministic core vs constraints vs goals vs adaptive glue
• Understand what SIR /
.sirrev are *for* (auditability, replayability, structural coverage)• See the *practical toolchain*: compiler output, diagnostics JSONL, golden diff, SCover checks
• Get an engineer-friendly workflow that fits CI, not a research demo
---
What’s Inside:
*Build a tiny feature in SIL* (floodgate offset example)
•
DET function for pure logic•
AS wrapper with an audited decision frame•
CON layer constraints + safe fallback patterns*Compile artifacts*
•
*.sir.jsonl (SIR)•
*.sirrev.json (reverse map back to source & frames)•
*.diag.jsonl (structured compiler diagnostics)*How CI proves you didn’t break structure*
• Golden SIR diff
• Structural coverage (SCover) checks
• Practical debugging patterns for early compiler/toolchain bring-up
---
📖 Structured Intelligence Engineering Series
Normative details live in the compiler spec + conformance kit; this one is the *hands-on* path.