Post
40
✅ Article highlight: *Programming SI-Core* (art-60-043, v0.1)
TL;DR:
What do developers actually write on an SI-Core stack?
This note sketches the programming model: **SIL** for goal-native code, **DPIR** as a typed decision IR, **CPU/GSPU backends** for execution, and **SIR** for structural traces. The point is to move from prompt surgery + log spelunking toward something closer to normal, testable, compilable software engineering.
Read:
kanaria007/agi-structural-intelligence-protocols
What’s inside:
• why SI-Core programming differs from “LLM wrapper microservices”
• the mental model: **OBS → SIL → DPIR → backend → RML → SIR**
• SIL examples, DPIR sketches, and backend execution shape
• local dev loop: sandbox SIRs,
• testing strategy: unit tests, structural property tests, GCS regression, Genius Replay
• tooling: LSP, ETH/capability lints, timeline and what-if visualizers
• migration path: from plain LLM wrappers to SI-native stacks in stages
Key idea:
Treat decisions as **programs** with explicit goals, ETH checks, and structured effects — not as opaque model samples hidden behind prompts.
Related specs (/spec):
si-core-spec-v0.1.md, si-nos-design-v0.1.md, sil-compiler-spec-bundle-v0.1.md, sil-compiler-conformance-kit-v0.1.md
TL;DR:
What do developers actually write on an SI-Core stack?
This note sketches the programming model: **SIL** for goal-native code, **DPIR** as a typed decision IR, **CPU/GSPU backends** for execution, and **SIR** for structural traces. The point is to move from prompt surgery + log spelunking toward something closer to normal, testable, compilable software engineering.
Read:
kanaria007/agi-structural-intelligence-protocols
What’s inside:
• why SI-Core programming differs from “LLM wrapper microservices”
• the mental model: **OBS → SIL → DPIR → backend → RML → SIR**
• SIL examples, DPIR sketches, and backend execution shape
• local dev loop: sandbox SIRs,
si build, si test, replay, inspection• testing strategy: unit tests, structural property tests, GCS regression, Genius Replay
• tooling: LSP, ETH/capability lints, timeline and what-if visualizers
• migration path: from plain LLM wrappers to SI-native stacks in stages
Key idea:
Treat decisions as **programs** with explicit goals, ETH checks, and structured effects — not as opaque model samples hidden behind prompts.
Related specs (/spec):
si-core-spec-v0.1.md, si-nos-design-v0.1.md, sil-compiler-spec-bundle-v0.1.md, sil-compiler-conformance-kit-v0.1.md