Core Developer

Documentation status: guide — see Maturity and evidence.

Core developers evolve the Runtime while protecting the stability of conceptual and public programming contracts.

Jump straight to the task

• Runtime internals map
• Contracts and evidence
• Native ABI bridge
• Tests and production

Responsibilities

• preserve semantic invariants across storage and execution backends;
• keep public ABI/binding contracts versioned and testable;
• add capability negotiation instead of platform assumptions;
• maintain local/remote behavioral parity where a capability is supported;
• provide deterministic failure and diagnostic boundaries;
• certify implementation maturity before documentation is promoted from architecture/roadmap to reference.

Source is not the API

A class, unit or kernel existing in the engine source does not make it public. Public exposure requires a deliberate contract, compatibility expectations, tests and documentation.