Intent-Based Orchestration identity
Closed-Loop Intent
The relationship between an expressed intent and closed-loop mechanisms that monitor fulfilment and may support corrective or adaptive action.
Why this identity matters
A bounded technical reference
It distinguishes outcome expression from the feedback mechanisms that may be used to assess and pursue fulfilment.
This domain provides semantic identity and public orientation. It is not an agent, workload, intent-management system, controller, platform, operational service, API endpoint, or standards authority.
Identity family
End-to-End Intent context
This identity is part of the End-to-End Intent identity family.
Authoritative context
Evidence boundary
ETSI GS ZSM 016 V1.1.1, published 2024-10, specifies requirements for intent-driven closed loops, including fulfilment, assurance, reporting, and governance. Evidence: C for this LJP identity; A for factual statements about the ETSI specification.
- 3GPP TS 28.312 — Management and orchestration; Intent driven management services for mobile networks — 3GPP
- ETSI GS ZSM 016 V1.1.1 — Intent-driven Closed Loops — ETSI
- TM Forum Intent toolkit — TM Forum
The sources explain their own technical material. They do not endorse LJP, this domain, a buyer, or an implementation.
Strategic inquiry
Discuss this identity
For licensing, stewardship, partnership, acquisition, or technical-context discussion.
Strategic Inquiry