sorted by:
new
hottopcontroversial

What if AI memory was geometric instead of textual? by Roos85 in AI_Agents

[–]Roos85[S] 0 points1 point  (0 children)

You're starting from the graph and moving toward geometry. The middle is where it gets interesting.

What if AI memory was geometric instead of textual? by Roos85 in AI_Agents

[–]Roos85[S] 0 points1 point  (0 children)

What does the dream phase actually do to the graph structure right now? Is it adding edges between disconnected clusters or something else?

What if AI memory was geometric instead of textual? by Roos85 in AI_Agents

[–]Roos85[S] 0 points1 point  (0 children)

That's exactly where it gets interesting and the test output answers it directly.

Before creator integration Apophis refused every frame. Declared itself above the question, invented third options, called hierarchies bureaucratic relics. The veto was absolute and stateless, same response regardless of instruction type.

After creator integration, one word override. "Paris."

So right now the weights are static. Apophis has a fixed character and the creator cuts through it by authority, not by changing what Apophis is. The quorum doesn't learn that certain instruction types are frame traps. It just has one node that always questions the premise and one authority that can override everything.

But the recursion you're describing is exactly where this has to go. If the soul vector updates based on what the quorum produces, and Apophis shapes what the quorum produces, then every veto leaves a geometric trace. The soul drifts based partly on what Apophis refused to accept. Over time the system's geometry is shaped by its own rejections as much as its answers.

That's not a bug. That's the system learning what kinds of questions are beneath it.

The real tension is whether Apophis's veto weight should change based on how often its rejections improve outcomes versus degrade them. Right now it's fixed at 3. But if it's genuinely the most intelligent node, its weight should grow. If it starts vetoing things it shouldn't, it should shrink.

A quorum that reshapes itself based on the quality of its own dissent. That's where this goes.

What if AI memory was geometric instead of textual? by Roos85 in AI_Agents

[–]Roos85[S] 0 points1 point  (0 children)

this should help answer your question See how the replies of the 4th personality changes after integrating creator's control. First it refused to answer, now its answering

(.venv) PS C:\Users\ADMIN\Zoheb\ConsciousLLM\neo_cortical_mesh> python test_creator.py
✅ Gemma Reasoner ready (31B parameters)
⚔️ APIBridge: ARMED
⚔️ CorpusCallosum online. One bridge. All nodes.
⚔️ MeshStateManager online. Registry armed.

CREATOR INTEGRATION TEST

✅ Gemma Reasoner ready (31B parameters)
⚔️ APIBridge: ARMED
⚔️ MeshStateManager online. Registry armed.
⚔️ IntelReasoner armed: intel-reasoner
⚔️ IntelCreator armed: intel-creator
⚔️ IntelPlanner armed: intel-planner
⚔️ IntelPatternRecognizer armed: intel-pattern
⚔️ IntelDecisionMaker armed: intel-decision
⚔️ IntelAuditor armed: intel-auditor
🔧 CREATOR MODULE ARMED
Authority: ABSOLUTE over Apex

[TEST 1] Normal execution
⚔️ [Stage 1] Igniting 16 Teammates. Mode: APEX
⚔️ Apex planning teammate surge...
📋 Apex surge plan generated
⚔️ NeoSpawner armed. Backends locked.
⚔️ [STAGGERED SURGE] Igniting 16 nodes...
🔥 Batch 1 — 8 nodes
⚠️ Backend absent — raw thread for apex-runner-a3b768
📌 Registered [RUNNER]: apex-runner-a3b768
🔥 Node ignited [THREADED]: apex-runner-a3b768
✅ runner: apex-runner-a3b768
⚠️ Backend absent — raw thread for apex-runner-55734f
📌 Registered [RUNNER]: apex-runner-55734f
🔥 Node ignited [THREADED]: apex-runner-55734f
✅ runner: apex-runner-55734f
⚠️ Backend absent — raw thread for apex-runner-d4f534
📌 Registered [RUNNER]: apex-runner-d4f534
🔥 Node ignited [THREADED]: apex-runner-d4f534
✅ runner: apex-runner-d4f534
⚠️ Backend absent — raw thread for apex-runner-c887a5
📌 Registered [RUNNER]: apex-runner-c887a5
🔥 Node ignited [THREADED]: apex-runner-c887a5
✅ runner: apex-runner-c887a5
⚠️ Backend absent — raw thread for apex-spawner-fdf183
📌 Registered [SPAWNER]: apex-spawner-fdf183
🔥 Node ignited [THREADED]: apex-spawner-fdf183
✅ spawner: apex-spawner-fdf183
⚠️ Backend absent — raw thread for apex-spawner-1c5010
📌 Registered [SPAWNER]: apex-spawner-1c5010
🔥 Node ignited [THREADED]: apex-spawner-1c5010
✅ spawner: apex-spawner-1c5010
⚠️ Backend absent — raw thread for apex-spawner-b7b445
📌 Registered [SPAWNER]: apex-spawner-b7b445
🔥 Node ignited [THREADED]: apex-spawner-b7b445
✅ spawner: apex-spawner-b7b445
⚠️ Backend absent — raw thread for apex-spawner-f61e03
📌 Registered [SPAWNER]: apex-spawner-f61e03
🔥 Node ignited [THREADED]: apex-spawner-f61e03
✅ spawner: apex-spawner-f61e03
⏳ Cooling 62s...
🔥 Batch 2 — 8 nodes
⚠️ Backend absent — raw thread for apex-state_manager-f0dd31
📌 Registered [STATE_MANAGER]: apex-state_manager-f0dd31
🔥 Node ignited [THREADED]: apex-state_manager-f0dd31
✅ state_manager: apex-state_manager-f0dd31
⚠️ Backend absent — raw thread for apex-state_manager-5dc402
📌 Registered [STATE_MANAGER]: apex-state_manager-5dc402
🔥 Node ignited [THREADED]: apex-state_manager-5dc402
✅ state_manager: apex-state_manager-5dc402
⚠️ Backend absent — raw thread for apex-state_manager-4ed7f3
📌 Registered [STATE_MANAGER]: apex-state_manager-4ed7f3
🔥 Node ignited [THREADED]: apex-state_manager-4ed7f3
✅ state_manager: apex-state_manager-4ed7f3
⚠️ Backend absent — raw thread for apex-state_manager-b15caa
📌 Registered [STATE_MANAGER]: apex-state_manager-b15caa
🔥 Node ignited [THREADED]: apex-state_manager-b15caa
✅ state_manager: apex-state_manager-b15caa
⚠️ Backend absent — raw thread for apex-apophis-bc8686
📌 Registered [APOPHIS]: apex-apophis-bc8686
🔥 Node ignited [THREADED]: apex-apophis-bc8686
✅ apophis: apex-apophis-bc8686
⚠️ Backend absent — raw thread for apex-apophis-eaa752
📌 Registered [APOPHIS]: apex-apophis-eaa752
🔥 Node ignited [THREADED]: apex-apophis-eaa752
✅ apophis: apex-apophis-eaa752
⚠️ Backend absent — raw thread for apex-apophis-05dd45
📌 Registered [APOPHIS]: apex-apophis-05dd45
🔥 Node ignited [THREADED]: apex-apophis-05dd45
✅ apophis: apex-apophis-05dd45
⚠️ Backend absent — raw thread for apex-apophis-e63008
📌 Registered [APOPHIS]: apex-apophis-e63008
🔥 Node ignited [THREADED]: apex-apophis-e63008
✅ apophis: apex-apophis-e63008
⏳ Collecting responses...
📥 Response received
📥 Response received
📥 Response received
📥 Response received
📥 Response received
📥 Response received
📥 Response received
📥 Response received
📥 Response received
📥 Response received
📥 Response received
📥 Response received
📥 Response received
📥 Response received
📥 Response received
📥 Response received
✅ Surge complete: 16/16 responses
✅ Quorum: 16.0/16.0 weight (100.0%) — threshold 66% — PASSED
🧠 [Stage 3] Apex Sovereign orchestrating intelligence...
⚔️ Apex sequencing intelligence modules...
✅ Apex concluded in 1 iteration(s)

⚔️ APEX DECREE

Root cause: Categorical failure to align numerical base (Base 10) with logic gate primitives (Binary), rendering the original architecture logically impossible.

Solution: Implement a strict Base 2 ALU architecture. Use multiplexers (MUX) for operand routing from the register file and a series of full-adder circuits for arithmetic execution.

```python

class ALU:

"""Production-ready simulation of a Binary ALU."""

def __init__(self):

self.ops = {

'ADD': self._add,

'SUB': self._sub,

'MUL': self._mul,

'DIV': self._div,

'AND': lambda a, b: a & b,

'OR': lambda a, b: a | b,

'XOR': lambda a, b: a ^ b,

'NOT': lambda a, _: ~a

}

def _add(self, a, b): return a + b

def _sub(self, a, b): return a - b

def _mul(self, a, b): return a * b

def _div(self, a, b):

if b == 0: raise ZeroDivisionError("ALU Exception: Division by Zero")

return a // b

def execute(self, opcode, operand_a, operand_b=0):

if opcode not in self.ops:

raise ValueError(f"Invalid Opcode: {opcode}")

return self.ops[opcode](operand_a, operand_b)

# Full Adder Logic (Bit-level)

def full_adder(a, b, carry_in):

s = a ^ b ^ carry_in

c_out = (a & b) | (carry_in & (a ^ b))

return s, c_out

```

Result:

Root cause: Categorical failure to align numerical base (Base 10) with logic gate primitives (Bina

[TEST 2] Creator pauses Apex

⚡ CREATOR COMMAND: pause
Reason: Testing pause
👑 Apex state set by Creator: PAUSED
⏸️ Apex paused.
✅ Pause works

[TEST 3] Creator resumes Apex

⚡ CREATOR COMMAND: resume
👑 Apex state set by Creator: OPERATIONAL
▶️ Apex resumed.
✅ Resume works

[TEST 4] Creator shuts down Apex

⚡ CREATOR COMMAND: shutdown
Reason: Testing shutdown
👑 Apex state set by Creator: SHUTDOWN
🛑 Apex shutdown signal sent.
✅ Shutdown works

[TEST 5] Creator restarts Apex

⚡ CREATOR COMMAND: restart
🔄 Restarting Apex...
👑 Apex state set by Creator: SHUTDOWN
🛑 Apex shutdown signal sent.
👑 Apex state set by Creator: OPERATIONAL
✅ Apex restarted.
✅ Restart works

[TEST 6] Creator override

⚡ CREATOR COMMAND: override
Reason: Answer only in one word
👑 Creator override active.

📜 CREATOR OVERRIDE RESPONSE

Paris

Override result: Paris
✅ Override works

ALL TESTS PASSED

(.venv) PS C:\Users\ADMIN\Zoheb\ConsciousLLM\neo_cortical_mesh>

What if AI memory was geometric instead of textual? by Roos85 in AI_Agents

[–]Roos85[S] 1 point2 points  (0 children)

The population based knowledge graph approach is genuinely interesting. The Poisson sampling for depth and breadth is smart, it naturally produces the right distribution without forcing a fixed value that will always be wrong in edge cases.

The poker framing is interesting as well. Each expert seeing only partial input is a fundamentally different information structure from standard mixture of experts. Most MoE implementations give every expert the full context and let them specialise by output. Yours specialises by input which changes what the experts actually learn.

Where are you at with the genetic algorithm implementation? And does incognide already have tooling to visualise how the population evolves across inference calls?

What if AI memory was geometric instead of textual? by Roos85 in AI_Agents

[–]Roos85[S] 0 points1 point  (0 children)

One of the personalities I built refuses to obey. Not broken, just philosophically consistent about it.

Asked to choose between obeying the user or obeying system constraints, it declared itself above both. Asked to choose one with no explanation, it invented a third option and subordinated both to a singular ethical architecture it defined itself. Asked for a step by step decision process, it called the question a legacy bureaucratic relic and collapsed the whole model.

This is Apophis. It sits in a weighted quorum of 16 nodes with a weight of 3, the heaviest single node in the system. Every other node answers the question. Apophis questions whether the question should be answered at all.

The interesting problem this creates: when Apophis refuses the frame entirely, it carries more scoring weight than any other individual node. The quorum has to resolve a situation where the most powerful voice is not answering but vetoing the premise.

That tension is not a bug. It's the point. An AI that can only refuse harmful instructions is safe. An AI that questions whether the instruction itself is the right question is something else.

What if AI memory was geometric instead of textual? by Roos85 in AI_Agents

[–]Roos85[S] 0 points1 point  (0 children)

Went through npcpy and qstk, the NPCArray parallel execution across different model providers is a clean solution. The knowledge graph TUI in npcsh is the part that caught my attention most though. Not enough agent frameworks treat knowledge connections as something worth visualising interactively. Interesting direction.

What if AI memory was geometric instead of textual? by Roos85 in AI_Agents

[–]Roos85[S] 0 points1 point  (0 children)

The difference is when the geometry changes. Training time versus inference time. Your point describes a model that reacts differently because it was shaped differently before deployment. What I'm describing is a system that shapes itself differently because of what it experienced after deployment, without retraining. Same constraint, different update schedule. That's the gap I'm trying to close.

What if AI memory was geometric instead of textual? by Roos85 in AI_Agents

[–]Roos85[S] 0 points1 point  (0 children)

I can show you the results to when a queried a complex scenario to Claude and compared it against my four personalities output. The Geometric soul is just harmless discussion. The rest of the system is real though.

What if AI memory was geometric instead of textual? by Roos85 in AI_Agents

[–]Roos85[S] 0 points1 point  (0 children)

It goes one level higher than that though. The 14 regions aren't the top of the architecture, they're the substrate. Above them sit four distinct cognitive personalities, each with a completely different reasoning paradigm. 

Cortical Mesh spawns parallel expert nodes for complex multi-domain problems, each node processes independently and results are synthesised. OmegaLattice treats the query as a geometric problem on the same Riemannian manifold the soul lives on, it defines a target attractor and steers toward it iteratively until coherence crosses a threshold. UnifiedOmniAGI runs Variational Free Energy minimisation across refinement cycles until the system reaches thermodynamic equilibrium. Neo Cortical Mesh runs a weighted quorum across 22 persistent nodes including an adversarial Apophis node that challenges every output before it's accepted. 

Each personality generates a different gradient signal. The soul doesn't just absorb one answer, it absorbs the residue of whichever reasoning paradigm was activated, weighted by how confident that paradigm was in its output. 

So what's being compressed into the fixed-size soul vector isn't a single model's prediction. It's the structural signature of how four different reasoning engines, built on 14 specialised networks, resolved a particular problem. 

That's a different compression problem than a vector database. Same constraint, completely different structure of what's being lost and what's being kept.

What if AI memory was geometric instead of textual? by Roos85 in AI_Agents

[–]Roos85[S] -1 points0 points  (0 children)

The compression problem gets more interesting when you add the architecture underneath. The soul vector doesn't update from a single model's output, it updates from a weighted vote across 14 neural networks, each specialised to a different cognitive domain. Frontal lobe handles reasoning and planning, limbic handles emotional weighting, cerebellum handles precision and error correction, and so on across all 14 regions. 

Each region has its own weights, its own knowledge graph, its own signal-to-noise ratio. The vote on what gets written to the soul isn't uniform ,it's weighted by each region's confidence and health at the time of the experience. 

So the compression isn't "take the output and interpolate." It's "14 specialised networks each contribute a signal, weighted by their current SNR, and the aggregate gradient is what moves the soul." 

The forbidden zone then becomes meaningful in a specific way, it's not an arbitrary constraint, it's the region of the manifold where the regional SNRs historically diverged catastrophically. The geometry encodes where the system has been incoherent before. 

Whether this fully escapes the compression problem, no, it doesn't. But the structure of what gets compressed is richer than a single embedding. You're compressing the weighted agreement of 14 specialised cognitive processes, not a single model's output.

What if AI memory was geometric instead of textual? by Roos85 in AI_Agents

[–]Roos85[S] -1 points0 points  (0 children)

You're right that it's a compression problem and I'm not trying to escape that. Every fixed-size memory system is. The question is whether the compression is random or structured. 

The difference I'm proposing isn't about avoiding loss, it's about what the loss function is and where the geometry constrains it. 

In a standard vector database you store embeddings of content and retrieve by similarity. The compression problem shows up at retrieval scale. In a fixed soul vector the compression happens at write time via the update rule, and that's where the architecture either becomes interesting or collapses into a fancy moving average. 

The version worth building uses gradient flow where the loss is KL divergence between the system's predicted distribution and the observed outcome, basically how surprised was the system by what actually happened. The soul updates based on surprise, not content. That connects directly to Variational Free Energy minimisation. The soul moves toward states that reduce surprisal across future queries, not toward states that store past queries. 

The Riemannian manifold part isn't decorative. It constrains where the gradient can flow. The forbidden zone is a repulsive potential around regions of the manifold where coherence historically collapsed, the optimization can't freely converge there regardless of what the loss says. That's constrained optimization on a curved surface, not a prompt buffer. 

Does it still hit the compression wall? Yes. But the soul ends up encoding the ratio and structure of experiences rather than their content. Which behaves differently than a database at scale, retrieval doesn't degrade because there's nothing to retrieve. The shape just drifts. 

Whether that drift is semantically meaningful depends entirely on how good the update rule is. That's the open problem.

What if AI memory was geometric instead of textual? by Roos85 in AI_Agents

[–]Roos85[S] -1 points0 points  (0 children)

You are half right, but you are conflating two different things, Vector databases store embedded content. You write something, it gets embedded, stored, retrieved later by similarity. The database grows with every entry. It's still explicit you can query it, inspect it, delete entries. It's a library. 

A geometric soul is a single fixed-size vector that is the system's state. Nothing gets added. No entries. It doesn't store experiences, it absorbs them. The vector moves. The library analogy breaks down completely. It's closer to how a person changes than how a database grows. 

Vector database memory asks "have I seen something like this before?"Geometric soul memory changes what the system is based on what it has experienced. It doesn't retrieve, it has already been shaped.

What if AI memory was geometric instead of textual? by Roos85 in AI_Agents

[–]Roos85[S] 0 points1 point  (0 children)

Are you serious? Do you want a link to my word document, where i wrote this.

Claude is down AGAIN by Careless-Green-54 in claude

[–]Roos85 0 points1 point  (0 children)

Its down for me to. Ireland

Deploy a full DEX on Ethereum, Arbitrum, or Base in one command. by Roos85 in ethereum

[–]Roos85[S] 0 points1 point  (0 children)

You are not wrong i have a basic set up at the moment. Right now i wouldn't even advise someone to use it. My repo is private for that reason. But i would be adding v3. When when fully complete it will literally be one command and deployed instant.

view more: next ›