Mirror Neuron Documents

Choose a Blueprint

Select a checked-in OtterDesk blueprint by task, data sensitivity, and runtime requirements.

Choose a Blueprint

Use this guide after you have installed MirrorNeuron and understand the Core Concepts. Each checked-in blueprint has its own input, model, service, and safety requirements; none is a universal installation test.

Before you begin

  • Run mn runtime health and resolve failed required components.
  • Read the blueprint folder's README.md, SPEC.md, manifest.json, and default configuration.
  • Confirm that you can safely provide the required inputs and operate the required local or external services.
  • Start with sample, mock, quick-test, or dry-run settings when the blueprint provides them.

Local blueprint catalog

Blueprint folderBest forImportant boundary
drug_discovery_research_assistantEarly discovery research and candidate-review packets.Review-only scientific research; use approved inputs and human review.
financial_advisorHousehold-finance, tax, and portfolio review packets.It does not file returns, trade, move money, or approve actions.
generic_customer_service_voice_coworkerA local voice customer-service experience.Requires an eligible NVIDIA GPU and the declared ASR, TTS, and model services.
medical_deid_record_intake_assistantPHI/PII detection and de-identification review.Keep real health records local and require privacy-officer review before release.
personal_legal_assistantInvoice, bill, and contract review packets.It does not provide legal advice, sign documents, or send payment instructions.
property_deal_research_assistantReal-estate opportunity research and comparison.Outputs are review material, not acquisition decisions.
safety_video_analyserBatch analysis of local workplace video.Requires NVIDIA CUDA placement for visual analysis; reports do not certify safety.
vc_assistantStartup-document research and score-only reports.It does not make investment decisions; public research can encounter access limits.
video_watch_assistantMonitoring an approved local or mapped video stream.Requires NVIDIA CUDA placement and a reviewed stream/alert configuration.

Validate before you run

From the workspace root, replace <blueprint_folder> with a folder in the table:

mn blueprint validate otterdesk-blueprints/<blueprint_folder>

Verification: validation must complete successfully. A missing-model, missing-service, or input-contract error identifies a prerequisite to resolve before launch.

Run a local folder

Start the runtime, then submit the validated folder:

mn runtime start
mn blueprint run --folder otterdesk-blueprints/<blueprint_folder>

Record the job ID and run ID printed by the CLI. Verify the launch with:

mn job status <job_id>
mn blueprint logs <run_id>

Run a configured catalog blueprint

The runtime can also use a configured Git or local blueprint catalog. List the available IDs before launching one:

mn blueprint list
mn blueprint run <blueprint_id>

MN_BLUEPRINT_SOURCE, MN_BLUEPRINT_REPO, and MN_BLUEPRINT_LOCAL determine the catalog source. See Environment Variables for the exact configuration contract.

Safety and cleanup

Warning: a blueprint may execute code, read local files, use selected environment variables, call model providers, or start services. Review its manifest.json, payloads, runner, and pass_env before launch.

Cancel a service or unfinished workflow when you finish evaluating it:

mn job cancel <job_id>

Related pages: Quickstart, Blueprint Standard, Model Runtime, and Security Model.

On this page