AI system, agent and execution
AI system in its context of use, agent configuration, tools, execution and endpoint. The subject of authority remains a defined operator, not automatically a new person.
Research draft, second pass
A second pass drafted this model: the structure a model of this thing needs, and what is known about it in the world. The line under this one says how the second half was obtained - researched against sources, or recalled without web access, in which case nothing here was read anywhere and every claim is a lead to verify. Unreviewed either way.
Bundle → Layer → Finding → Questions Missing, in the backlog
Not described yet. This gap is in the card backlog.
Note: Research contour: bundles not designed yet; questions are listed as open questions.
Classifiers Filled
- Family
- Enterprise profiles
- Category
- Enterprise subject
- Entry kind
- subject
- Domain
- EnterpriseAI
- Industry
- Cross-industry
- Tags
- EM-AI-01W2subjectAISystemAgentConfigurationToolBindingAgentRunInferenceEndpoint
What it is Filled
AI system in its context of use, agent configuration, tools, execution and endpoint. The subject of authority remains a defined operator, not automatically a new person.
Why it exists Filled
AI system in its context of use, agent configuration, tools, execution and endpoint. The subject of authority remains a defined operator, not automatically a new person.
Distinguishing features Derived, awaiting review
- The configuration and the run have different IDs
- Delegation is limited to the original rights
- An ai-subject is not created as a human or legal subject
What robots and AI may and may not do Derived, awaiting review
Must not
- Negative case: An LLM model receives unlimited authority solely because of the field role=agent.
Note: Negative case of the research brief, not yet a rule for agents.
Moral aspects Missing, in the backlog
Not described yet. This gap is in the card backlog.
Owners Filled
Steward
Руководитель AI / исследований
Master systems
- Model registry
- experiment tracker
- eval store
Links to other meta-models Filled
neighbor
- EM-AI-02
- EM-AI-03
- EM-FIN-05
references
- WM-AI-001 - conceptual-candidate
- WM-AI-002 - conceptual-candidate
- WM-AI-005 - conceptual-candidate
- WM-AI-004 - conceptual-candidate
What else AI and robots need to interact with it Incomplete
Identity and identifiers required Derived, awaiting review
- AISystem
- AgentConfiguration
- ToolBinding
- AgentRun
- InferenceEndpoint
Direct properties not applicable Not applicable
Not applicable
Enterprise record contour: physical properties belong to referenced world models.
Recognition required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Capabilities and actions required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Hazards and failure modes required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Standards and interfaces required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Context of use required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Sources Filled
- NIST AI RMF: context, evaluation and risk management
- PROV/SPDX: provenance of data, artifacts and actions
- Model registry/evaluation tooling practice; map system, artifact, run and endpoint
Open questions
- How does a system differ from a model and a product?
- How are agent actions and delegation restricted?
- How to reproduce an execution when the model and tools change?
- Установить границу и решение reuse/extend/new по действующим спецификациям.
- Подтвердить semantic crosswalk, права и source mastership.
- Выбрать immutable refs; провести проверки fixtures до заявления о публикационной готовности.
Machine files
Provenance
enterprise research programme · published-partial
Built from: enterprise/models/em-ai-01/brief.json
Still in Russian: suggested owner, blocking decisions, vercy candidates. Translate in research/enterprise/i18n/units.en.json.