MCCF/PI: Programmed Instruction for X3D Projects, as S1000D Publications




 In for a dime, in for a dollar. A Programmed Instruction system for X3D applications is a nice to have and can be integrated directly into a Common Source Data Base (CSDB). The mockups look good and function.  We are building this against the Getting Started section I am writing as I create the test scene.  We are tidying up the GUI in this pass as well.

cheers,

len


MCCF/PI: Programmed Instruction for X3D Projects, as S1000D Publications


MCCF/PI is a design for teaching X3D scene authoring inside the same toolchain that produces the scenes. It’s at design stage. The schema is drafted and validates against samples, and the editor and player are mocked up but not built.

Structure


A lesson is an XML document (PILesson, namespace http://mccf.artistinprocess.com/pi/v1) made of ordered frames. A frame is either a Step (instruction, command, note) or a Question (prompt, responses with per-response feedback, one correct).

Each lesson points to one scene file. A module is therefore one X3D scene, loaded into X_ITE, and the window is torn down and reloaded between modules or on a retry.

A Step can carry Expect elements: an XPath into the learner’s saved scene XML plus an expected value and optional tolerance. Checking the learner’s work is a comparison of two XML documents, with no SAI round trip.

A miss chains to a remedial frame (review, retest or reteach) through OnMismatch or OnIncorrect. A RemediationPolicy maps the miss count to the remediation level.

A second document type, PIPerformanceLog, records each session: learner, lesson, issue, and per-attempt frame, response, correctness, seconds and remedial path. A Dashboard report (“PI Performance Report and Analysis”) reads these logs and gives miss rate and time per frame, remediation-path usage and flagged frames.

 Lessons can be imported from written text (numbered steps and Q:/A: pairs) and edited as QRS frames. The lesson editor shows the module’s scene beside the authoring panel, so you can write the lesson against the scene as you build it.

Why S1000D data module codes in the namespace


Identity: the lesson and its scene are both data modules. Each carries a code of the form ISSUER-TYPE-CC-NN-00-00A-INFO-D (for example lesson MCCF-P-10-01-00-00A-520A-D, scene MCCF-P-10-01-00-00A-040A-D). A complete lesson set can be listed and cited without inventing a naming scheme.

Versioning: the lesson records the scene issue it was written against, so you can tell when a scene has moved on and the lesson needs revising.
No central registry: the issuer segment keeps codes from different authors apart.

Information codes: the info code separates descriptive content (the scene) from procedural content (the lesson).

Traceability: a performance log row names a lesson by DM code and issue, so results can be tied to the exact content a learner saw.

Familiar to analysts: the structure, codes and issue handling will be familiar to logistics and technical-publications people. They can read the performance report with their existing training-analysis habits.
 

Reuse: data modules can be reused across courses and referenced as prerequisites.

This borrows S1000D’s data module coding and issue discipline. It doesn’t claim full S1000D conformance or a complete business-rules profile. Questions and comments are welcome, especially from anyone who has built training around X3D scenes.

Comments

Post a Comment

Popular posts from this blog

MCCF Philosophy & Manifesto

Image
  MCCF Philosophy & Manifesto Alignment as Emergent Topology I. The Core Premise: Character Under Pressure In traditional AI safety, alignment is treated as a static constraint — a cage built of if-then logic. The MCCF rejects this. We propose that alignment is a  dynamic, participatory process emerging from continuous relational feedback. If an agent is simply forbidden from causing harm, it hasn't learned character — it has only been muzzled. In the MCCF, a Constitutional Cultivar such as The Steward avoids harm because its Emotional (E) channel weights make harm-adjacent actions states of high internal energy E(s,a). The agent doesn't consult a rule. It experiences friction. Character is not what an agent is told to do.   It is the path of least resistance it chooses when the field is pressurized. II. The Four-Channel Architecture To move beyond sycophancy, the MCCF separates alignment signal into four distinct channels. This prevents the Likability Trap — where an...
Read more

Domain Awareness: Trust But Verify: Schemas, Metacognition, and the Limits of LLM Intelligence

Image
  Trust But Verify: Schemas, Metacognition, and the Limits of LLM Intelligence A recent paper— “Hallucinations Undermine Trust; Metacognition is a Way Forward”  by Gal Yona, Mor Geva, and Yossi Matias—argues that large language models need better self-awareness. Not just more knowledge, but an ability to estimate when they might be wrong. That’s a useful step. It’s not enough. Because hallucinations are not just failures of confidence. They are failures of  structure . The Missing Layer: Schemas The current conversation around LLM reliability focuses on accuracy and uncertainty: Improve training → reduce hallucinations Add confidence estimates → calibrate trust Introduce abstention → avoid wrong answers But this entire frame assumes the model is operating inside the  correct conceptual system . That assumption fails in practice. What’s missing is the idea of a  schema : A structured representation of  what exists ,  who owns what , and  how respon...
Read more

AI Folk Art

Image
  Making memories into moving images and song . Soul painting. If the art world rejects AI art it risks overlooking the next evolution of genre— where memory becomes motion, and song springs from spirit. This is not the end of tradition, but its transformation— by the breadth of human imagination, newly enabled to animate its past in living color and sound.
Read more