DOMAIN PRODUCT EXAMPLE / LIE

LIELearning engine

LIE is a product example for the learning domain. It gives enterprise applications task processing, process checking, next-action and performance-recording capabilities, independently or in combination.

Capability directory, API workspace and integration documentation.

Four independently integrable modules

Integrate, deploy, call and validate each module independently. Enterprises may supply the required upstream inputs under the interface contract. Full Suite offers optional composition, with no mandatory sequence.

01

Task understanding

Help applications process and review task content, organise conditions and goals, and obtain available task results.

What you provide
A task and locatable materials, with necessary conditions and requested goals.
What you receive
Goals, conditions, available results and solution explanations; what is missing when incomplete.

Discuss access

View details
02

Process checking

Help learning applications review actual responses and link findings to positions in the original input.

What you provide
The user’s actual steps or final response, plus the corresponding task materials.
What you receive
Input positions to review, explanations and check scope; missing observations remain unknown.

Discuss access

View details
03

Learning actions

Help applications arrange next learning actions from observed performance and authorised enterprise content.

What you provide
A defined performance goal, observed performance facts and authorised enterprise questions or materials.
What you receive
Next learning actions, material references or retest arrangements; the content interface must be connected first.

Discuss access

View details
04

Learning state

Help applications track actual performance, distinguishing independent work, missing observations and uncovered scope.

What you provide
Sourced performance records, whether work was independent and the assessed scope.
What you receive
Supported performance-state changes and coverage summaries; reading alone does not establish mastery.

Discuss access

View details

Work capability directory

Choose by task and expected result. Inclusion, dependencies and access permissions are defined by the formal delivery materials.

N01

Fact summary

Summarise counts, distributions and sources of selected records, with the statistical scope.

Discuss accessView details
N02

Task progression

Review current progress, continuation conditions and recovery points.

Discuss accessView details
N03

Goal exploration

Explore possible results within supplied objects and constraints.

Discuss accessView details
N04

Access and presentation

Present content and actions that each role is authorised to access.

Discuss accessView details
N05

Continuous task workspace

Connect related operations in one workspace and review each stage’s results.

Discuss accessView details
N06

Source correction and content management

Correct materials against sources and manage authorised content.

Discuss accessView details
N07

Supplement and review

Add specified information and review another check; further assessment requires an authorised enterprise question bank or materials interface.

Discuss accessView details
N08

Question generation

Generate questions to agreed requirements and review validation and adoption scope.

Discuss accessView details

01 / LIE

LIE · Inputs, results and checks, together

The following example from the mathematics edition illustrates inputs and results.

What you provide

Question: A has 18 books, 6 more than B. After A gives B 3 books, how many does each have?

What you receive

Task goals: determine the book counts for A and B after the transfer. The paired response lists two target objects.

How to check it

Match A, B and “how many does each have” to the question. Scope: task goals of this example question only.

View user guideProduct examples

Start with a concrete use case

Define the task, available inputs, expected results and acceptance criteria, then confirm capability access, interface versions and delivery scope. A directory entry or example does not grant access. Further assessment and content adoption require an authorised enterprise question bank or materials interface.

Business needs

Review workflows, use cases and the problems to address.

Inputs and outputs

Define the format and content of input data, along with the expected outputs.

Integration and validation

Assess the integration environment, scope of use and validation conditions.

CONTACT

Contact us

Contact us for technical discussions, product applications and collaboration.

Product enquiries

  • What task should be completed?
  • What inputs are available?
  • What result should be validated?
Discuss integration