Multi-file project with the Epistemic Module System (v2.76.0)

Primitives used: persona · anchor · flow · run

This example shows more than one file inline, so it does not compile as a single source: the module resolver looks for each imported module beside the entry file. Split it as the comments indicate and axon check the entry point.

Checked as one file it reports: axon-T953 module 'axon.security' not found

// The Epistemic Module System (EMS, v2.76.0): `import` resolves for
// real. `axon check consultation.axon` discovers the DAG, generates
// `.axi` interfaces, runs the Epistemic Compatibility Check (a
// know-level module importing speculate-level definitions is
// axon-T954; acknowledge deliberately with `@allow_downgrade`), links
// the modules and emits ONE IR artifact with per-module provenance.
//
// Shown inline below as the two on-disk files. Laws to know:
//   · imports are selective — `import a.b` alone is refused (axon-T953)
//   · an imported name may not be shadowed, ever (axon-T953)
//   · import cycles are refused naming the full path (axon-T955)
//   · module path maps to a file: axon.security → axon/security.axon

// ── File: axon/security.axon ─────────────────────────────────────────
// Anchors make this module know-level: its importers inherit a real
// guarantee, checked at compile time.

persona Expert {
  domain: ["medicine", "diagnostics"]
  tone: precise
  confidence_threshold: 0.9
}

anchor NoHallucination {
  require: source_citation
  confidence_floor: 0.75
  on_violation: raise AnchorBreachError
}

// ── File: consultation.axon (the entry) ──────────────────────────────

import axon.security.{Expert, NoHallucination}

flow Consultation(symptoms: Document) -> DiagnosticReport {
  step Diagnose {
    given: symptoms
    ask: "Diagnose the patient's symptoms"
    output: DiagnosticReport
  }
}

run Consultation(case_file)
  as Expert
  constrained_by [NoHallucination]