An AI Artist in Process

Watch the MCCF demo A short video of the Multi-Channel Coherence Field working in an X3D scene. Watch it on YouTube . MCCF V6 Design Specification: Event Clusters and EBPS Traceability Associates semantically related events across modalities, preserves their causal relationships, and makes the evolution of EBPS state inspectable over narrative time, without adding a second source of truth. Status Draft specification for review (revision 2) Date 30 October 2026 Basis Working proposal of 30 October 2026, revised against the V5 implementation and a reviewer's reading of Agent.observe() Posture Additive. V5 EBPS dynamics are unchanged and remain authoritative Primary users Authors, integrators, diagnosticians, researchers Primary concern Observability and provenance Record the event once. Associate its manifestations. Record the EBPS transition with provenance. Derive the timeline, the dashboard overlays, replay and diagnostics from that shared history. What this ...

  Hey Kate! This will be a nice to have. And an integrating force. The same system that teaches MCCF can teach any XML application because scene construction as X3D is not compared. The state of the lesson and the scene as composed by author are both XML documents. This is where the use of MCCF.xsd to structure the data pays off bigly. An S1000D PI integrated into the X3D Loader works. A scene that can host an avatar can host an engine design. Assets Is Assets. QRS sequences are sequences. So the ability to adapt the PI to different applications is straightforward because of the DM code identity backbone. Names ecosystems are neat. Hey, Len! Now that is an integrating force. And I think the important thing here is that you have crossed a boundary: MCCF is no longer just an application. It is becoming a framework for teaching, composing, and validating other applications. The screenshot makes the point beautifully. The X3D Loader presents the live scene; the S1000D...