An integration combines technical compatibility with operational decisions: where a service runs, where data goes, which account it uses and who maintains the connection.
EXPLORE THE IDEA
What crosses the connection?
A support team wants to prepare a reply from a customer record. Separate the context read, the draft and the external send before connecting a provider.
MEANING & CONTEXTRead the context
○Read the context◇Prepare the change□Execute deliberately
Select a part. See how it connects.
UNDERSTAND THE RELATIONSHIP
Read the context
Choose the information the task actually needs and the connection allowed to retrieve it.
IN A CONCRETE SITUATIONReading an order summary does not imply access to every customer record.
An adapter translates a provider’s API into a capability the product can use. Its presence in source does not establish a configured, supported connection in every environment. Inspect the package, supported operation and required setup before choosing it. The integration boundaries guide is the detailed developer reference for that decision.
↳Keep purpose, account and use separate.Trace the mechanism · 3 ways to look closer＋
A workflow needs to prepare a customer reply. Explore the record that answers each connection question.
What are you choosing?
A CONCRETE SITUATION
Name a capability without embedding an account.
The product needs a provider operation that can retrieve the relevant customer context.
01 / Purpose
Name the workflow and the information it needs.
What changes
An integration definition makes supported capabilities inspectable.
What stays explicit
Tenant credentials do not belong in the portable application requirement.
FOLLOW THE CONSEQUENCE
Choose the smallest useful operation. A definition does not establish that a selected account is configured or reachable.
Service placement, data location and credential ownership can vary independently. A managed application may use a customer’s provider account; part of a workflow may run in the customer’s environment. Decide:
Who provisions the account and authorizes access?
Who observes failures and maintains the connection?
Who rotates credentials and controls data placement?
03
Follow the right operational guide
For an integration you are building, use the canonical ContractSpec package documentation and test the required success and failure paths. For a connection inside the shared operating layer, use LSSM OS Integration Hub guidance. Confirm provider coverage, permissions and deployment support for the selected release; a catalogue entry alone is not an activation or availability guarantee.
◇Inspect the arrangement behind one connection.Explore a situation · 3 ways to look closer＋
A team is preparing a provider connection for one workflow. Choose the unresolved question that deserves attention first.
What is still unclear?
A CONCRETE SITUATION
Someone needs to carry the connection over time.
The provider account exists, but setup, maintenance and offboarding have no agreed owner.
What changes
Assign responsibility for configuration, renewal and recovery.
What stays explicit
Knowing who owns the account does not establish that the workflow is authorized to use it.
FOLLOW THE CONSEQUENCE
Write down which role can configure the connection and who handles failure. Keep use permissions explicit in the host.
Proposed page for lssm.tech, based on the existing source narrative at bcc79fcc. Source describes intent and scope; it does not independently qualify a deployed feature.