extra-languages-core

name	extra-languages-core
description	Shared reference for the extra-languages cluster: the one decision every niche stack turns on — write the platform's native, current idiom and contain any foreign/legacy runtime behind an adapter boundary — plus version-pinning conventions, a stack × layer matrix, and the trust-boundary guardrails its spokes share. USE WHEN choosing a niche-stack idiom or default dependency, deciding where a legacy/compat layer goes, pinning a toolchain, or scoping whether work belongs here versus a major-language cluster.
cluster	extra-languages
version	1.0.0

Extra Languages Core

Shared model for the extra-languages cluster — the deferred-tier home for niche, platform- specific language and runtime specialists. The spokes are independent stacks, so the value here is the one cross-cutting discipline they all obey and the rules for keeping the cluster from drifting into a junk drawer.

1. The decision everything turns on: native idiom + contained boundary

A niche stack fails not on algorithms but on fighting the platform. The rule:

Write the platform's current, native idiom. When you must touch a foreign or legacy runtime, isolate it behind an adapter — never let its types leak across the app.

This has two halves:

• Native + current. Use the stack's present-day blessed toolkit, not the one your muscle memory or last year's tutorial reaches for. For Solana that means for client/RPC/transaction code and ( + ) for UI — by default.