Connections
with context.

Why this guide exists

Digital work crosses boundaries. A team needs access before it can use an application; an agent needs approved context before it can help; a business needs a reliable route from its first enquiry to a useful response. LLS makes these dependencies easier to see.

The directory connects relevant destinations by purpose. The playbooks turn that landscape into a starting brief. It is a practical way to explore the 42.uk universe and related commercial service destinations.

What the destination labels mean

Provider or established destination

A public service or product information site. Confirm its current offer and terms directly.

Project or service enquiry

A place to discuss a requirement. The website itself does not confirm capacity, price or an installed integration.

Agent concept

A proposition or demonstration for agent-enabled work. Connected capabilities require their own implementation and permissions.

Research archive or knowledge destination

Material to learn from. Check source dates, software versions and compatibility before applying it.

Bring a useful brief

Describe the outcome, the people involved, the systems already in use and where the work stalls. Add the geography, information boundary, responsible owner and what success would look like. A clear scope makes a specialist conversation more productive.

How to read the connections

Links identify relevant starting points. They do not establish legal group ownership, a common contract or a preconfigured integration. Service commitments belong in the agreement with the relevant operator.

Use the enquiry form to suggest a correction or a useful connection. Send a general explanation and the public page involved.