IvanTheGeek

IvanTheGeek.com is a personal domain that I will use to record and organize my thoughts, ideas, receive feedback, and anything else that comes up that it will be good to use it for.

History seems missing. allows others to change it? can have replies? can a reply be made a wiki? if so, does it show first?

WIKI to be curated.

as part of my data ingestion and integrations, the idea would be to have Discord or X or Facebook and pull in these streams to LOGOS. for discord, channels could be used in Talkyard Chats or as discussion topics. it would give a local copy of the dat...

NARRATIVE: I have one board that is my main board. It has all different areas I am using Talkyard for like Software Development, research, networking, NeighborNet, personal, Homesteading, Accounting, etc. I would like to be able to have "sub-sites" w...

Adding topic in one tab is not seen in another tab until navigation or refresh is hit. I might not want it to keep scrolling on new topics as that might be rather jarring, but an indicator comes up that says there are new topics and clicking it then ...

I had 2 tabs open both on the forum. I was creating a reply in the first to one topic. I wanted to search for something in another tab and then wanted to record an idea in a different post. When I clicked Create Topic, it pulled in all the text from ...

need to investigate and experiment with user permissions to see what it can limit hide categories?

The scenario is that I want to grant admin permissions to a user for all things related to a category. EXAMPLE: grant admin to talkyard dev for the Talkyard category.

When I have been doing updates like category description updates when i flip to another tab with Talkyard open, even clicking around is sometimes not showing the updated text. I am sure it is related to caching, just wondering if that can be improved...

I have a category description set that is a bit longer. Edit the description of the Talkyard category: The place where I record my Talkyard "forum" investigations, experiments, questions, experiences. Being done here to eventually be used to improve ...

Most basic slice (which is a column): SLICE-NAME-INTENT UI COMMAND/VIEW EVENT Basic CommandSlice: COMMAND-SLICE-NAME-INTENT UI COMMAND EVENT The naming for Slices is likely omitted from the graph as the command is usuaully the intent. Markdown is cau...

Right now, just gathering thoughts. Will compose this into an actual story later.

Replies have links to examples I have found

A collection of ideas for apps. Feel free to suggest and define.

This is a good moment to freeze the ontologies, because you now have enough clarity to separate three layers: Nexus Universal Ontology (domain-agnostic primitives) Adam’s Event Modeling Ontology (method primitives) Event Modeling Extended (EMext) (yo...

DISCOVERY-019ce328-ea67-77ce-8b0a-ed422fa1bdd3: 019ce328-ea67-77ce-8b0a-ed422fa1bdd3 Following the distinction between Domain Ontology, Concept DNA, and Cells, the next question is: What are the fundamental cell types that implement behavior inside a...

Discovery Log: Distinguishing Domain Ontology vs Concept DNA in the Nexus Model After a large amount of exploration and iteration, an important conceptual distinction emerged in the Nexus model between Domain Ontology and Concept DNA. This distinctio...

https://docs.ghost.org/hosting

Good software to look at being useful Is open source https://checkmate.so/sponsored-features#top as a way generate $ and improve the product.

Open source projects die from knowledge loss, not lack of interest. A contributor arrives, finds working code, and discovers that the reasoning behind it is gone. The original authors moved on. The architecture decisions were never recorded. The cont...

A NEXUS Event Model describes what a system does at a semantic level — independent of any implementation language or existing codebase. This property runs in both directions. A system can be designed forward from an Event Model. A system can also be ...

README: Tool Evaluations Category

Tool Name: Cap.so MP4 to GIF Converter Link: https://cap.so/tools/convert/mp4-to-gif Category/Type: Video Conversion Utility Description: This is an online tool for converting MP4 videos to animated GIFs. It supports file uploads, editing options lik...

Overview Claude's strengths in reasoning make it a candidate for CORTEX's design phase, but refusals and metadata issues in exports challenge LOGOS integration. Abilities Excellent multi-step logic for NEXUS (e.g., refining slice patterns). Compactio...

Purpose This wiki centralizes evaluations of AI models against CORTEX needs: personalization, NEXUS methodology support (e.g., design-before-code, event modeling), LOGOS compatibility (e.g., metadata-rich exports), and general abilities/limitations. ...

This category captures insights — observations and connections discovered through actively thinking about, using, and extending NEXUS.

A well-formed NEXUS design produces artifacts that describe what a system does, not how any particular language implements it. The target language is a parameter passed to the rendering layer — not a constraint baked into the design. This is not an a...

Penpot serves two distinct roles in NEXUS, and understanding both is essential to understanding why it was chosen and what it enables. In both roles, Penpot is not a reference artifact — it is the authoritative source of truth. Role One — Event Model...

NEXUS is methodology, not tooling. The tools that support NEXUS are chosen because they align with the methodology's principles — they can be replaced if better alternatives emerge. What cannot be replaced are the principles they serve. This wiki des...

Knowledge accumulation is a first-class design requirement in NEXUS — as important as the software being built. This is not a documentation policy or a cultural expectation. It is an architectural principle that shapes every tool, every process, and ...

AI plays two distinct roles in NEXUS. Conflating them misrepresents both. Understanding the distinction is essential to understanding how NEXUS works. The Two AI Roles AI as design collaborator — works alongside the human during the design phase. Hel...

A Spec is a typed design artifact that describes a specific slice of the Event Model in enough detail to implement from. Specs are written before code. This is not a preference — it is the discipline that makes NEXUS work. What a Spec Is A Spec takes...

A path is a named, purposeful journey through the Event Model from a specific actor's perspective. Paths are not informal descriptions or user stories — they are typed design artifacts that exist in LOGOS, are linked to the Event Model elements they ...

Swim lanes are horizontal lanes within a layer of the Event Model timeline that separate different actors or systems. They appear in two layers and mean different things in each. Swim Lanes at the UI/IO Layer At the UI/IO boundary layer, swim lanes s...

A slice is a vertical cut through the Event Model timeline that connects the layers. Every interaction the system supports is expressed as one or more slices. There are exactly two fundamental slice types. All more complex patterns are compositions o...

The UI/IO boundary layer is the outermost layer of an Event Model. It is where external signals originate and where projections are consumed. It is the boundary between the system and everything outside it. What This Layer Actually Is Colloquially th...

The three core elements of an Event Model are Command, Event, and Projection. The names are deliberate. Each describes the mechanism of the thing, not just its purpose. Understanding why the names were chosen is part of understanding how the system w...

Event Modeling is the design methodology at the heart of NEXUS. Before any code is written, the system is modeled as a sequence of events on a timeline. This is not optional overhead — it is the foundation from which everything else is built. What Ev...

Most software development loses knowledge. This is the problem NEXUS exists to solve. How Knowledge Gets Lost Design decisions get made in meetings that aren't recorded. Architecture choices get buried in chat threads that expire or get deleted. The ...

The NEXUS methodology must not imply or prescribe that refinements and requirements are only generated by discovered limitations. Insights that drive methodology evolution can originate from any source, and NEXUS must reflect that explicitly. Why It'...

This category is where the NEXUS methodology refines itself.

This category is where the Chat Import Pipeline gets designed and understood.

This category is where the CORTEX personal AI system gets defined.

This category is where the LOGOS software gets defined.

This category is a record of facts.

This is where software gets designed, built, and understood. Not just coded — understood. The distinction matters.

NEXUS is the methodology and framework that governs how software gets designed, built, and understood here. It is not a product — it is the approach. The discipline. The set of principles that makes everything else coherent.

CORTEX is the private AI system being built to know you — your codebase, your methodology, your decisions, your history, your way of thinking. Not a generic assistant. Not a shared model trained on the internet. A personal intelligence that accumulat...

LOGOS is the knowledge and communication system at the center of the NEXUS framework. It is simultaneously the concept and the software — the seeking, accumulating, reasoning layer that serves humans and AI simultaneously from the same living record.

A key component of my software development framework is a forum that provides multiple benefits. It is likely that I will end up building my own using my framework and methodology, but that is a ways off. I need something to glean ideas from and use ...

I'm a truck driver. Laundry happens on the road, at truck stops and travel centers, and it costs real money. Those expenses are deductible, but only if you actually track them. By the time I'm back in the cab, the receipt is gone, there is likely NOT...