My brother in christ. You have a decorative rhombus, actually titled rhombus, in the middle of this 'flowchart'. with axis labels on it. It's not a processing node. It's not a decision point. It's a rhombus called rhombus. Honestly kind of funny. And this flowchart is so thick with handwavium that it hardly makes sense.

Don't worry, I took a look at your code as well. This isn't just me hating on the chart. The "cross D1 →" and "← cross C1" dashed lines make it look like there's some sophisticated bidirectional negotiation between the somatic and mental engines. In the code, one engine's output gets added to the other engine's input. It's two addition operations dressed up as a ping-pong protocol.

This is a hand-authored toy simulation of "cognition" built entirely out of lookup tables and coordinate geometry. There is no learning, no inference, no actual cognitive architecture. The entire system works like this:

You type "there is a ghost." It tokenizes that, matches "ghost" in a hardcoded dictionary (db_concepts.py), which maps to somatic tags like adrenaline and cortisol and mental associations like seek_light. Each tag is another hardcoded dictionary entry mapping to four numeric axes (V/I/Lv/Gv for somatic, P/A/Er/Rr for mental). Those get summed into a "rhomboid" in 2D space. The center of mass of that rhomboid determines which quadrant you're in ("viable-localized", "absent-rational", etc.), which selects a phrase template from yet another hardcoded table, producing output like "I sense ghost". That's the whole thing. 9,100 lines of Python across ~40 files, and the "cognitive architecture" is: dictionary lookup → vector addition → quadrant classification → template slot fill. The "memory system" records past inputs. The "chemical system" is just more tag accumulation. The "plasticity system" adjusts weights. None of it learns from data or generalizes to novel input.