NAESTROLet’s talk

NAESTRO / DOCUMENTATION

Start with the boundary you need to understand.

The fastest way to understand NAESTRO is to follow one real question through the system. These public entry points explain the architecture, the language/runtime, persistent memory and evidence without requiring a private deployment.

Documentation mapA clear path into the system

  • Start with a workflow

    See how a trajectory holds continuing work.

  • Follow the interfaces

    Trace component roles and their public references.

  • Check the boundaries

    Distinguish supported behavior from the roadmap.

A practical reading path

01ArchitectureHow goals, planning, tools, policy, state and evidence connect.02Intent contractsHow MIND-Intent, MIND establishment and 512-MIND authorization divide responsibility.03Ecosystem rolesWhere MIND-Intent, 512-MIND and Arch-MIND fit, with their maturity boundaries.04CapabilitiesWhat the operating layer coordinates and where each claim stops.05EvaluationHow to compare paths and retain the evidence a reviewer needs.

Public technical sources

MIND / DOCUMENTATION

Language and runtime

Read the public MIND documentation for the Core v1 surface, compiler/runtime boundaries and current roadmap.

Open mindlang.dev
MIND / SPECIFICATION

Normative interfaces

The language repository and Core specification are the source of truth for behavior that an integration depends on.

Open the Core specification
MIND / INTENT

Contract boundary

Follow the proposed IntentSpec to Contract IR boundary and its explicit refusal path in the architecture model.

Read the MIND-Intent role
512-MIND / GOVERNANCE

Authorization boundary

See how governance and invariant checks are positioned after establishment and before an admitted action.

Read the 512-MIND role
Arch-MIND / STRUCTURE

Structural review

Use the ecosystem map to distinguish repository and component structure from semantic proof or runtime evidence.

Read the Arch-MIND role
MIND-MEM / MEMORY

Persistent context

Inspect the public memory project for setup, usage, governance and the limits of its retrieval and evidence claims.

Open MIND-Mem

A clear next step

Bring a workflow, its constraints and the decision that deserves review. The next step is a scoped conversation, then a small inspectable trajectory.

Discuss your workflow

Sample records & compiled artifacts

The website explorer exposes an illustrative trajectory as a readable JSON sample record. It describes the example’s steps and outcomes for inspection.

MIND’s compiled representation is mic@3, a canonical binary encoding of compiler IR. Its optional MAP (Metadata Attachment Partner) section carries metadata, including evidence when emitted. The proposed mic@4 successor remains roadmap work.

A sample trajectory record and a compiled MIND artifact serve different purposes. Artifact verification applies to the actual compiler output and the evidence it contains.

Read the canonical IR specification

Bring a real workflow. Start with a bounded question.

Discuss an evaluation