Business-level permission and responsibility for what a person or organization may discover, read, contribute, reserve, configure, execute, stop, accept, release or administer.
A bounded function that can produce a defined result under declared conditions.
A lightweight human-readable description of what can be provided, where, when, by whom, under what conditions and with what evidence.
A versioned, more formal description of a Capability including inputs, outputs, interfaces, conditions and evidence.
The shared technical/business boundary used by different implementations to deliver the same function.
Evidence that an implementation satisfies a defined Profile or specification under the stated test conditions.
Responsibility for possession/handling of a physical object during a defined interval or handover.
Versioned record of what was observed, tested, delivered, accepted, rejected or recovered.
The explicit limit on what a piece of evidence proves and what it does not prove.
A state observation whose age and source satisfy the Work’s freshness requirement.
A real-world or business object such as person, place, machine, material, inventory position, service or capability.
In Model Context Protocol terminology, data/context exposed by a server for a client to read; distinct from an HSIMC Resource object.
A callable operation exposed by an MCP server.
HSIMC participation concept for a person represented with explicit identity/relationships and Work-specific Authority; not a claim that a digital representation replaces the person.
A Work-specific combination of people, models, software tools and local capabilities with explicit responsibility.
A request or action with a stable identity, especially important when physical side effects are possible.
Evidence about a specific operation; not automatically evidence of current state.
Evidence class for a delivered physical instance that has been bound and accepted at destination.
Evidence class for a specifically identified physical reference instance tested under controlled conditions.
A versioned description of capability/conditions; it does not by itself prove that every instance currently satisfies the profile.
A result and evidence pack used as a reproducible basis for comparison; not a standard by itself.
Generic word used contextually; the document distinguishes HSIMC Resource from MCP resource.
A deployed execution identity/configuration used by HSIMC projects; a Runtime identity is not by itself Authority to control a device.
Protocol behavior in which each request carries the context required for processing rather than relying on hidden transport-session state.
A specific accepted unit connecting demand, responsible parties, Resource, conditions, Authority, execution, acceptance and value evidence.
The versioned agreement/record that defines a Work’s inputs, outputs, conditions, roles, acceptance and recovery.