Technical reference · Lacefield Research
Systems engineers & ed-tech developers

Dynamic Profile Architecture

By Gregory Stuart Lacefield Lacefield Research · May 2026 See also: Accessible version →

Overview

The Dynamic Profile is the single most important data structure in the Lacefield Adaptive Learning System. It is non-collapsible by design. It consists of two permanently separate components: the Dynamic Learning Profile (DLP), which tracks the student's cognitive state, and the Student Context Profile (SCP), which tracks real-world life context for problem framing. These are never averaged, merged, or weighted together. The rule is repeated throughout the technical specification because it is load-bearing — collapsing them destroys the precision the entire system is built on.

The DLP tells the system where the student is. The SCP tells the system how to reach them. Merging them makes both answers wrong.

DLP — Dynamic Learning Profile

Tracks the student's actual cognitive state across all concept branches. Updated after every session from observed performance data. Core fields:

{
  "schema_floor": {
    "branch_name": {
      "tier": 2,
      "confidence": 0.82,
      "last_assessed": "2026-05-19"
    }
  },
  "wrong_schema_flags": [
    {
      "branch": "algebra_equality",
      "corrupted_tier": 1,
      "apparent_tier": 3,
      "misconception_id": "MIS-EQ-01",
      "resolution_status": "active"
    }
  ],
  "fluency_bottlenecks": [
    {"operation": "fraction_division", "severity": "slow_correct"}
  ],
  "language_ceiling": {
    "general_comprehension": 3,
    "lexical_ambiguity_flags": ["product", "rational"]
  },
  "adjacent_concept_signals": [],
  "calibration_state": {
    "target_accuracy": 0.80,
    "current_tier": 2,
    "direction": "hold"
  }
}

SCP — Student Context Profile

Tracks real-world context used exclusively for problem framing. Never influences diagnostic assessment. Core fields:

{
  "career_context": "Construction — residential framing",
  "hobbies": ["fishing", "auto mechanics"],
  "goals": "GED for electrician apprenticeship program",
  "available_materials": "phone, pencil, paper — no calculator",
  "language_preferences": "plain language, concrete examples",
  "framing_anchors": ["board footage", "wire gauge", "voltage ratios"]
}

Why separation is enforced at database level

Application-level separation can be violated by a developer adding a field to the wrong object. Database-level separation — separate tables or top-level document keys — makes the violation structurally impossible. Schema floor and career context are not related quantities. There is no valid operation that combines them. Storing them in the same structure creates the illusion that such operations are meaningful.

The DLP updates independently of the SCP. A student's schema floor can change in a single session. Their career context may not change for months. If these are stored in a merged structure, every DLP update requires carefully avoiding SCP contamination. Structural separation eliminates that requirement entirely.

Cross-domain application

The same architecture — Dynamic Profile + Context Profile, permanently separate — is used in the fitness, recovery, and trading engines. In each domain the DLP equivalent tracks the learner's actual state (fitness capacity, recovery stage, trading schema floor). The SCP equivalent tracks context for framing (lifestyle constraints, support system, risk tolerance). The engine is the same. The domain-specific fields differ.

Author: Gregory Stuart Lacefield — independent systems engineer. Creator of the Lacefield Adaptive Learning System. Las Vegas, NV.

Full author record · Available for work