Skip to main content

Crate services

Crate services 

Source
Expand description

Ultron’s local services, served to the Python kernel as host operations (RLM-first: the model’s only tool stays rlm; these are kernel APIs reached through refinements.*, gates.* and rlm.host_request):

  • local: refinements (lessons, instruction / skill / agent changes) with proposal, approval, activation, rejection and rollback over one event ledger anchored to the conversation branch, and the experiment history (ultron/local-services.ts);
  • validation: the worker’s activation checks for skill proposals and instructions (ultron/refinement-validation.ts);
  • gates: release gates, frozen definitions and recorded baseline-versus-candidate comparisons (ultron/release-gate.ts);
  • session_values: these documents (and the task journal, definitions, usage ledger and memory journal) as values of the session, so resume and fork restore matching state.

The host enforces the guarantees (protected targets, capability non-escalation, evidence, versions, frozen gate definitions, append-only history); nothing here prompts the user or calls a model.

Re-exports§

pub use gates::ReleaseGateModule;
pub use local::Branch;
pub use local::BranchSource;
pub use local::LocalOptions;
pub use local::LocalServices;
pub use local::LocalServicesModule;
pub use local::instruction_hook;
pub use local::refinement_view;
pub use session_values::SessionDocument;
pub use session_values::SessionValues;
pub use validation::validate_refinement_content;

Modules§

gates
gates.* (port of ultron/release-gate.ts): frozen release-gate definitions plus a recorded baseline-versus- candidate comparison. A gate definition is immutable once defined and is the only source of which checks exist and which are required; a run cannot introduce its own checks. Every comparison attempt, blocked or passed, is recorded before it is returned, with the digest of the definition it was judged against. A required check that regressed, or is not passed in the candidate, blocks; an optional regression is reported and does not block; a run on another fixture blocks. This module only records and decides; it never prompts.
local
refinements.* and experiments.* of ultron/local-services.ts (NativeLocalServices): versioned refinements (lessons, instruction and skill changes) with their proposal, approval, activation, rejection and rollback flow over one append-only event ledger, and the experiment history of recorded runs.
session_values
Ultron session values: the documents of the local services, host modules, task journal, definition registry, usage ledger and memory journal kept as values of the session itself (format-4 session journal), as the TypeScript worker keeps them (createSessionTaskStore at ultron.tasks/root, createSessionModuleStore at ultron.module/<name>, createSessionDefinitionStore at ultron.definitions/root, createSessionUsageStore at ultron.usage/root, the memory journal at ultron.memory.state/root, the local services at ultron.local/<key>).
validation
ultron/refinement-validation.ts: the content checks the worker’s refinement service runs when a refinement is activated (A32). A skill must be a loadable SKILL.md: YAML frontmatter with a kebab-case name and a description, then a nonempty body. An instruction is bounded plain text. Capability requests are refused separately by the refinement service itself.