New product iteration
Workforce conversation
Conversation Lab: facts, perspectives and next moves
15 model calls · 5 artifact versions · 1 scenario challenge
Agentic learning engineering · Problems → Products
A flower-based experiment studio and a collection of preserved agent runs on fictional problems. Configure team contributions, examine the original journals and candidate tools, and identify the observations still needed with real learners and practitioners.
The flower makes complementary expertise and shared understanding explicit across a learning engineering cycle. LENS connects Human flourishing, Learning sciences, and Systems engineering; the simulation asks how contributions enter decisions and executable designs. Output alone does not demonstrate human capability or learning impact.
Configure complementary expertise around the learning engineering flower. Follow how shared understanding, contributions, and operating conditions shape a candidate design, then inspect the evidence behind it.
Eight starting expertise domains surround shared understanding. Learners and other stakeholders remain connected to the whole team. Assign one or several domains to a member, share responsibilities, and select the expertise the challenge needs.
Open dynamic design conversations Understand the five comparisons
Use two phases: dynamic Design / Develop conversations, then Deploy / Test under easy, medium, and hard conditions. Specialists have bounded responsibilities; the generalist has introductory cross-domain knowledge. An expert evaluator examines the complete conversation and observed result separately. Edit and export a case here, run it locally, then import the retained record. Earlier fixed-workflow results remain available below.
Preserved agent execution on fictional problems, using the original team configurations. These replays are historical examples, not new flower study results. Each refinement keeps its original run available; human pilot approval and field evidence remain pending.
New product iteration
Workforce conversation
15 model calls · 5 artifact versions · 1 scenario challenge
New product iteration
School science investigation
24 model calls · 8 artifact versions · 1 scenario challenge
New product iteration
Library access journey
16 model calls · 5 artifact versions · 1 scenario challenge
Shared understanding means integrating domain concerns into requirements, decisions, implementation, and evaluation. Every team member has responsibility for the learners and stakeholders affected by the design.
Explore the flower domains and shared responsibilities. The guide also preserves the original role contracts for interpreting historical replays.
The scorecard examines human flourishing support, system performance, and learning separately. Ratings concern the design and available evidence. Claims about learning or impact require suitable evaluation with people.
Inspect the earlier fixed-workflow study and its original evidence
Read the dynamic study paper: Exploring the learning engineering flower with agentic simulation
Conversation Lab: facts, perspectives and next moves lets a new team lead compare authored openings, separate facts from explanations, and reconsider a proposal when protected time and coverage are withdrawn. Access, authority, capacity and agreement remain independent. Its reflection is descriptive; it does not assess employees.
The handoff contains executable HTML, requirements, versioned artifacts, the project journal and a source-linked manifest. It is a candidate product requiring affected-person review and field validation.
The saved fictional workforce project contains 29 model requests, including a rejected correction, and 14 artifact versions. Scenarios changed interruption privacy and reviewer-conflict requirements. An actual missing-code finding reopened Build.
The replay preserves original drafts, dissent, prompts, provider metadata, failed validation and the corrected candidate. Recorded browser checks support only the behavior exercised in that environment.
Inspect the source journal · Follow the original workforce revisions
Understand → Map → Design → Build → Instrument → Experiment → Evaluate → Refine is a revisitable cycle. Build produces the executable candidate; refinement can return to any invalidated requirement. The learning engineer integrates the work and keeps human and system requirements visible.
Real use needs accountable ownership, affected-person review, appropriate data handling, accessible operation, a meaningful comparison and stopping rules. Learning, workplace transfer and flourishing remain claims to investigate. Inadequate conditions can justify changing the product, changing the work system, or stopping.
The hosted site serves saved products and replay. New model runs use the local runner in this repository; hosted model access and a shared job queue remain future work.
Return to project seeds · Runner source · Specification and operating documentation