Neurosymbolic AI

Architectures combining neural networks with deterministic symbolic logic — argued to be the real substrate of working agent products like Claude Code.

Also known as: Neurosymbolic AI, neurosymbolic, nevrosymbolsk AI (neurosymbolic AI), nevrosymbolsk AI, classical symbolic AI, deterministisk vs probabilistisk

How authors use it

Oldest first (extraction date when no publication date is known).

Documents (4)

• Presentation: Decision Models in Agentic Architectures: From Production to Agent Skills Alex Porcelli · 2026-09-14 Reader 🖥️
  High-stakes decisions inside agentic AI systems need a deterministic, auditable decision-model layer (DMN, executed by a rule engine like Drools) sitting beneath the non-deterministic LLM and exposed to it as a skill or guardrail — generated from and owned by business domain experts rather than engineers — because what enterprise AI actually lacks is not mere consistency but full accountability: reproducibility, explainability, and governance together.
• Tony Seale's Post Tony Seale · 2026-07-05 source ↗ Reader 🖥️
  Durable agent memory should fuse the two kinds of human memory — a markdown wiki for the episodic (what happened) and a formal ontology for the semantic (what things mean) — in one layered file format, Vault-LD (markdown plus optional YAML-LD frontmatter), so that any note can progressively acquire structure and meaning and a private vault can scale, unchanged in substrate, from a personal second brain up to an open, decentralised agentic web.
• 16) Inga Strümke om hvor AI er på vei, den outsourcede problemløsningen og datamanifolden Truls Jørgensen og Audun Fauchald Strand — Heis Podcast · 2026-05-04 source ↗ Reader 🖥️
  Norway's understanding of AI has been hijacked by the chatbot — both as the dominant interface and as the dominant mental model — and this collapses our maturation path: we substitute buying foreign LLM products for the slower, harder work of in-house machine-learning, problem framing, and explainability, even though the technical theory (data manifolds, approximation, neurosymbolic combinations) and the geopolitics both demand that we develop our own capability rather than outsource our problem-solving.
• The biggest advance in AI since the LLM Gary Marcus · 2026-04-11 source ↗ Reader 🖥️
  Claude Code's leaked source code reveals a neurosymbolic architecture — classical symbolic pattern-matching at its core rather than pure LLM — which Marcus argues is the single biggest advance in AI since the LLM and vindicates the neurosymbolic research programme he and others have long advocated.

Propositions touching this concept (7)

By publication month, oldest first (extraction month when no publication date is known).

2026-04

• explicitcorroboratedClaude Code is not a pure LLM or pure deep learning system; it is neurosymbolic.
  The biggest advance in AI since the LLM · p2
• explicitThe print.ts file (3,167 lines, 486 IF-THEN branches, 12 levels of nesting) constitutes classical symbolic AI at Claude Code's core.
  The biggest advance in AI since the LLM · p3
• explicitThe success of neurosymbolic approaches (Claude Code, AlphaFold, AlphaEvolve, etc.) means the pure-scaling paradigm has ended.
  The biggest advance in AI since the LLM · p5
• explicitAnthropic has not publicly acknowledged the significance of its own shift away from pure scaling toward neurosymbolic methods.
  The biggest advance in AI since the LLM · p6
• implicitA deterministic IF-THEN conditional in a rendering file is equivalent to 'classical symbolic AI' in a theoretically meaningful sense.
  The biggest advance in AI since the LLM · p7
• explicitNeurosymbolic AI is necessary but not sufficient; knowledge, reasoning, and world models are also needed for trustworthy AI.
  The biggest advance in AI since the LLM · p8

2026-05

• explicitClaude Code's use of a regex to detect literal 'continue' rather than routing to the LLM is a frontier-product proof that neurosymbolic AI has already won in practice, regardless of the academic debate.
  16) Inga Strümke om hvor AI er på vei, den outsourcede problemløsningen og datamanifolden · p5

Open gaps (17)

• incompleteThe 'outsourcet problemløsning' framing is sharp but Strümke does not develop the policy mechanics: what counts as 'building it yourself' on a continuum? OSS-finetuned-from-an-open-base, Norway-hosted closed-weight, fully in-house from scratch — the framing presupposes a binary that procurement policy would have to operationalize.
  16) Inga Strümke om hvor AI er på vei, den outsourcede problemløsningen og datamanifolden — read next: Cuijpers / EU AI Act interpretation on capability sovereignty; Anu Bradford on Brussels effect; OpenEuroLLM / Silo AI literature on sovereign-capability tiers; recent NSM/Nkom positions on cloud sovereignty thresholds.
• incompleteThe data-manifold frame is presented as Strümke's primary lens but she explicitly says 'we don't have access to either manifold' — so the entire empirical apparatus that would let us know how close approximation has gotten remains undeveloped in the conversation. The host doesn't push on what an operational proxy would even look like.
  16) Inga Strümke om hvor AI er på vei, den outsourcede problemløsningen og datamanifolden — read next: Yamins & DiCarlo on neural-net-vs-cortex representational geometry; Bengio on the manifold hypothesis as ML's organizing assumption; recent interpretability work (Anthropic's circuit-tracing, sparse autoencoders) as one empirical handle on the model side of the question.
• incompleteStrümke argues for neurosymbolic AI and points at Claude Code's regex as proof, but doesn't address the harder question: where does the symbolic boundary go? Claude Code's choice is for a single literal token; the production design pattern (when LLM, when regex, when AST, when proof) is unexplored.
  16) Inga Strümke om hvor AI er på vei, den outsourcede problemløsningen og datamanifolden — read next: Gary Marcus's neurosymbolic writings; DeepMind's AlphaProof/AlphaGeometry as advanced symbolic-neural hybrids; the harness-engineering literature already in the user's library (Anthropic, Boris Cherny) for production-design patterns.
• incompleteThe conversation reaches the 'cover your ass' diagnosis of Norwegian public-sector risk-aversion but does not investigate the structural causes — why has the last ~10 years been 'feigere'? Datatilsynet stance is named, the Nikolai Tangen episode is named, but the institutional feedback loop producing the pattern is not unpacked.
  16) Inga Strümke om hvor AI er på vei, den outsourcede problemløsningen og datamanifolden — read next: John Cutler on institutional overload and accountability culture (already in the user's reading); recent NSM/Nkom assessments on resilience; Norwegian public-administration literature (NIBR / NIFU) on risk-distribution between politikere and direktorater; Annie Duke / Daniel Kahneman on outcome-bias driving risk-aversion.
• incompleteStrümke names two interesting categories — 'avklaringsspørsmål' (we have the methods, we just need agreement) and 'forskningsspørsmål' (genuinely open) — but doesn't extend the taxonomy. The third missing category is presumably 'capability-building-spørsmål' (we know what we need to build but lack the people / infra to build it) — which is arguably the dominant Norwegian bottleneck.
  16) Inga Strümke om hvor AI er på vei, den outsourcede problemløsningen og datamanifolden — read next: Donella Meadows on system leverage points (where in this taxonomy is the highest leverage); KI Norge mandate documents from Digdir; recent NTNU/SimulaMet hiring and capacity reports.
• uninformedStrümke is open about her own production-coding skepticism ('jeg merker når jeg sitter og koder med agentene, så er sånn tulleprosjektet'), and the hosts (Audun from NAV) push back gently with the more developed practitioner view that high-stakes work warrants Vim while front-end can be agent-led. Strümke's reading of agentic coding may underweight what's currently possible with proper harness, evals, and sandboxing — though she does flag the macOS sandbox feature.
  16) Inga Strümke om hvor AI er på vei, den outsourcede problemløsningen og datamanifolden — read next: User's existing thread on harness engineering (Anthropic videos, Boris Cherny, Bockeler/Fowler static sensors); Beane on Precision Proactivity; the user's earlier Heis Anders Sveen / Vilde Opsal extractions; Greger Wedel; concrete production-engineering reports from Builder.io, Cursor, and Claude Code teams.
• incompleteThe closing 'undetectable backdoors' research preview is fascinating but isolated from the rest of the conversation. If undetectable backdoors are plantable, the entire 'outsource problem-solving to Copilot' diagnosis acquires a much sharper national-security dimension that the conversation does not draw.
  16) Inga Strümke om hvor AI er på vei, den outsourcede problemløsningen og datamanifolden — read next: Goldwasser et al. on undetectable backdoors (the foundational paper); recent NeurIPS / ICML papers on neural-net backdoor detection; supply-chain security literature (SLSA, sigstore) extended to ML model artifacts.
• evidentiaryMarcus does not explain what print.ts actually does within Claude Code's architecture. The file name suggests it is a rendering/output-formatting module, not a 'kernel' in the computational sense. Calling it the system's 'center' and equating its IF-THEN logic with 'classical symbolic AI' is a significant interpretive leap that goes undefended.
  The biggest advance in AI since the LLM — read next: Examine the actual Claude Code source to determine whether print.ts is architecturally central or peripheral; read Simon Willison's and other technical analyses of the leak.
• logicalThe argument conflates 'contains deterministic code' with 'is neurosymbolic in the research-programme sense.' Almost all software systems contain IF-THEN logic; the neurosymbolic research programme means something more specific — structured knowledge representations, formal reasoning, compositionality. Marcus does not show that Claude Code has these properties.
  The biggest advance in AI since the LLM — read next: Read the neurosymbolic AI literature (e.g., Garcez & Lamb 2023) to clarify what the term requires; compare with Marcus's own prior definitions.
• rhetoricalThe essay is structured as personal vindication rather than neutral analysis. The framing ('massive vindication for me personally') may lead readers to accept the argument on ethos rather than evaluating the evidence independently.
  The biggest advance in AI since the LLM — read next: Seek independent technical assessments of Claude Code's architecture that do not have a stake in the neurosymbolic debate.
• causalEven granting that Claude Code contains symbolic components, Marcus does not establish that these components (rather than, say, the agentic loop, tool-use design, context management, or the underlying LLM quality) are what make it effective. The causal claim is asserted, not argued.
  The biggest advance in AI since the LLM — read next: Look for ablation studies or engineering post-mortems that isolate the contribution of symbolic vs. neural components in agentic coding systems.
• incompleteThe central operational claim (20M transactions, 18,000 tx/sec) and all three live demos run entirely on the presenter's own company's stack (Aletyx/Drools), with no independent benchmark and no comparison to alternative deterministic-layer approaches for the same class of problem — e.g., lightweight classical ML classifiers, which elsewhere in this corpus are argued to be cheaper and equally explainable for comparable tiered-classification decisions.
  Presentation: Decision Models in Agentic Architectures: From Production to Agent Skills — read next: extract-heis-16-inga-strumke-hvor-ai-er-paa-vei-datamanifolden — argues classical regression/classification ML models are tiny, deterministic, cheap, and explainable for exactly this kind of tiering problem, and criticizes organizations for skipping them in favor of heavier AI tooling.
• incompleteOntology maintenance and curation cost is entirely unaddressed. The post treats the ontology as a layer that 'supplies' semantic memory, but says nothing about who authors the shared formal vocabulary, how it is governed as many notes link into it, or that this is scarce knowledge-engineering labour. If maintaining the ontology is the hard part, the bottleneck moves from markdown convenience to specialist curation — undercutting the linked 'simplest thing that could possibly work' framing.
  Tony Seale's Post — read next: Read the historical adoption record of formal ontologies and the Semantic Web (OWL/RDF, schema.org governance) for why ontology upkeep, not authoring notes, is the recurring failure point. Compare with this repo's own knowledge/ layer, which runs the same episodic+semantic split but deliberately diverges from Vault-LD: it keeps the ontology in an external, human-curated registry (concepts.yaml) rather than inline YAML-LD, and uses positional refs (slug#p3) rather than linked-data URIs. That a working instance of the pattern chose an external registry is direct evidence that inline 'one file, each layer optional' is not the only viable architecture — and that someone still has to own the semantic layer by hand.
• incompleteThe inference payoff is asserted but never demonstrated. 'Project into a graph, where inference, validation, query and integration are already waiting' names four benefits without a single worked example of what an agent can now answer, or what a validation constraint would catch, that a plain markdown wiki could not. The most consequential claim in the piece — that the ontology overhead buys real capability — is left as a promise.
  Tony Seale's Post — read next: Seek the linked Vault-LD spec for a concrete example, then pressure-test it against the counter-claim in the corpus (Karpathy: an LLM-maintained markdown index is sufficient for complex Q&A at ~100-article scale without any graph). Ask specifically: what query, inference or validation justifies the ontology, and at what vault size does flat markdown actually break?
• incompleteThe net-positive assumption skips the sync/drift ledger. Keeping typed fields and ontology links in agreement with prose as the prose evolves is ongoing cost, and 'each layer optional until you need it' in practice tends to mean 'skipped' — which leaves the graph sparse exactly where semantics were supposed to add value, and leaves the annotated minority prone to silent divergence from the text it describes.
  Tony Seale's Post — read next: Read on documentation drift / doc-rot and on the divergence between described and enforced structure over time (cf. the static-sensors debate on markdown guides vs enforcement rules). Consider whether YAML-LD frontmatter has the same rot dynamics as any duplicated metadata, and what would keep it honest.
• incompleteThe JSON-LD-on-HTML analogy imports an inevitability it has not earned. The web's structured-data adoption was driven by a concrete incentive — search engines reward JSON-LD with ranking — and is itself uneven and gamed. The post identifies no equivalent forcing function for private or team vaults, yet treats 'the same move' as a settled outcome rather than a hopeful one.
  Tony Seale's Post — read next: Examine schema.org adoption data and its SEO dynamics — how much of the web's 'knowledge graph' is genuine semantics versus ranking-driven boilerplate — and ask what a vault-world analogue of search-ranking pressure would even be. If none exists, the adoption story needs a different engine than the analogy provides.
• incompleteNo treatment of the trustworthiness of the memory itself. Agent memory is largely LLM-written; a hallucinated or drifting note, once given typed fields and ontology links, inherits machine-queryable false authority. The semantic layer is presented purely as validation upside, with no acknowledgement that it propagates bad facts as readily as it structures good ones, or that memory poisoning becomes more consequential once memory is formally queried.
  Tony Seale's Post — read next: Read on agent-memory poisoning and knowledge-base trust (how errors propagate through an LLM-maintained base over time). Distinguish validation that catches contradictions from structure that merely launders unverified claims into confident graph facts.