Nage AI OS · Operating environment

Carry the record
across the handoff.

A source-aware answer is more useful when its record remains available to the next application, reviewer and assurance tool.

Explore component rolesDeveloper materials
Operating environment

The record crosses a boundary. Its meaning should survive.

Explore component roles, then inspect a conceptual record handoff.

Component responsibilitiesRuntime: nage-api

Knowledge

Substrate

Delivery

Contract

Knowledge

SEDIM

Responsibility
Source-aware inference architecture
Record / boundary
Answer and accompanying record
Implementation status
Current grounding service; weight path in development
Illustrative contract test

Same record.
Next recipient.

Follow the fixture ID across conceptual boundaries. Then remove a field and inspect what the recipient loses.

AT PRODUCERreq_conference_demo_en_0001
source_freshness: null
reason: No source date is available

The missing value retains its explanation.

The component map is not a verified service-call graph. The handoff demo makes no API calls. MAGMA is a contract stub; CONDUIT production Ed25519 integration remains open.

Explicit responsibilities

Names describe roles. Readiness belongs to each boundary.

GroupComponentsRole
KnowledgeSEDIM · CONFLUX · BEDROCKInference, knowledge flow and source foundations.
SubstrateNUCLEUS · RILLSupporting infrastructure and record flow.
Delivery & observationSTRATUM · CONDUIT · OUTCROPApplication interfaces, transport and visibility.
Designed contractMAGMAContract/reference stub. The actual runtime is nage-api.
Integration sequence

Design the handoff before scaling it.

Begin by choosing the record producer, the consuming application and the reviewer. Specify which fields travel, which are transformed and how missing information is disclosed.

  1. 01

    Name the boundary.

    Identify the service responsible for source identity, record creation and delivery.

  2. 02

    Preserve the disclosure.

    Keep formula identifiers, signal status and missing values alongside the output.

  3. 03

    Define the check.

    Agree how the recipient recomputes integrity and obtains a trusted key.

  4. 04

    Test lifecycle events.

    Evaluate version changes, source retirement and unavailable evidence.

Boundary note. Production Ed25519 integration in CONDUIT remains open. A signed demonstration fixture must not be presented as evidence of universal production signing.

For partners

Explore the record from the responsibility you own.

Choose a partnership path →Inspect developer materials →Read the KLM candidate standard →