[ Edit this to tell people what they can do here. ]
[ Edit this to tell people what they can do here. ]
| Topics, recently active first | Category | Users | Replies | Activity |
|---|---|---|---|---|
Allow shared access to Categories 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... | Talkyard | I | 1 | 2026-03-13 17:34:37.488Z |
Auto-Update Topic lists 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 ... | Talkyard | I | 0 | 2026-03-13 17:03:44.758Z |
Clicking REPLY in another browser tab brings entries from other tab. 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 ... | Talkyard | I | 0 | 2026-03-13 16:58:33.894Z |
What does permissions actually limit? need to investigate and experiment with user permissions to see what it can limit hide categories? | Talkyard | I | 0 | 2026-03-13 16:54:38.250Z |
Delay in updates 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... | Talkyard Concerns | I | 0 | 2026-03-13 16:21:56.457Z |
Category description is truncated. 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 ... ![]() ![]() | Talkyard Concerns | I | 1 | 2026-03-13 16:15:30.081Z |
IvanTheGeek Origin Story Right now, just gathering thoughts. Will compose this into an actual story later. | General | I | 1 | 2026-03-13 15:50:45.402Z |
Event Modeling Examples Replies have links to examples I have found | NEXUS | I | 1 | 2026-03-13 14:52:51.042Z |
App Ideas A collection of ideas for apps. Feel free to suggest and define. | APPs | I | 1 | 2026-03-13 14:51:55.856Z |
Nexus Ontology 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... | NEXUS | I | 0 | 2026-03-12 21:03:06.388Z |
| Explain icons... | ||||
Discovery: The Fundamental Cell Types of the Nexus Model 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... | NEXUS | I | 0 | 2026-03-12 17:54:22.605Z |
DISCOVERY-019ce328-9263-7996-a2d6-5f68a88257ba: Distinguishing Domain Ontology vs Concept DNA in the Nexus Model 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... | NEXUS | I | 0 | 2026-03-12 17:48:26.580Z |
https://checkmate.so Good software to look at being useful Is open source https://checkmate.so/sponsored-features#top as a way generate $ and improve the product. | DATA DUMP | I | 0 | 2026-03-04 20:03:14.471Z |
Event Modeling and open source projects 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... | Insights | I | 0 | 2026-03-02 19:33:25.251Z |
Reverse engineering existing software with Event Modeling 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 ... | Insights | I | 0 | 2026-03-02 19:23:43.293Z |
README README: Tool Evaluations Category | Geek Toolbox | I | 0 | 2026-03-02 16:51:08.278Z |
MP4 to GIF Converter - cap.so Evaluation 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... | Geek Toolbox | I | 0 | 2026-03-02 16:45:25.607Z |
Evaluating Claude (Anthropic 4.x Series) 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... | AI Evaluations | I | 0 | 2026-03-02 15:45:34.900Z |
AI Model Evaluations Overview and Comparisons 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. ... | AI Evaluations | I | 0 | 2026-03-02 15:38:20.345Z |
README This category captures insights — observations and connections discovered through actively thinking about, using, and extending NEXUS. | Insights | I | 0 | 2026-03-02 12:27:03.526Z |
Language-agnostic design — one model, many implementations 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... | NEXUS | I | 0 | 2026-03-02 02:44:14.919Z |
Penpot as dual source of truth — Event Model and UI 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 | I | 0 | 2026-03-02 02:36:32.516Z |
Tools and how they fit 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... | NEXUS | I | 0 | 2026-03-02 02:31:39.950Z |
The knowledge accumulation principle 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 ... | NEXUS | I | 0 | 2026-03-02 02:10:39.861Z |
AI-assisted implementation 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... | NEXUS | I | 0 | 2026-03-02 02:02:08.475Z |
Specs and the design-before-implementation discipline 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... | NEXUS | I | 0 | 2026-03-02 01:28:25.760Z |
Paths as first-class artifacts 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 ... | NEXUS | I | 0 | 2026-03-02 01:17:45.499Z |
Swim lanes — actor boundaries and system boundaries 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... | NEXUS | I | 0 | 2026-03-02 01:03:31.186Z |
Slice patterns — the two fundamentals and how they compose 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... | NEXUS | I | 0 | 2026-03-02 00:57:56.978Z |
The UI/IO boundary layer 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... | NEXUS | I | 0 | 2026-03-02 00:53:11.541Z |
The Command / Event / Projection triad 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... | NEXUS | I | 0 | 2026-03-01 23:06:49.289Z |
Event Modeling as the design foundation 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... | NEXUS | I | 0 | 2026-03-01 22:51:50.292Z |
The problem NEXUS solves 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 ... | NEXUS | I | 0 | 2026-03-01 20:53:46.501Z |
Refinements can be sourced from anywhere, not only discovered limitations 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'... | Refinements | I | 0 | 2026-03-01 19:22:20.860Z |
README This category is where the NEXUS methodology refines itself. | Refinements | I | 0 | 2026-03-01 19:19:15.059Z |
README This category is where the Chat Import Pipeline gets designed and understood. | Chat Import Pipeline | I | 0 | 2026-03-01 18:17:29.077Z |
Accepted as a distinct terminal status LOGOS must distinguish between two fundamentally different terminal states for any topic with a workflow: Done, meaning the issue is resolved, and Accepted, meaning the constraint is consciously acknowledged and will be lived with. These are not the ... | REQUIREMENTS | I | 0 | 2026-03-01 18:12:05.097Z |
Arbitrary import pipeline support with full metadata preservation LOGOS must accept imports from external sources with full metadata preservation. The import pipeline is a first-class architectural concern, not a utility feature bolted on after the fact. Why It's Needed A significant portion of the knowledge and re... | REQUIREMENTS | I | 0 | 2026-03-01 18:07:12.819Z |
Full data export — no lock-in Every piece of data in LOGOS must be fully exportable in standard formats. The event log, current state, metadata, attachments, and cross-references — all of it. LOGOS does not own your data. Why It's Needed Lock-in is a structural risk for any syste... | REQUIREMENTS | I | 0 | 2026-03-01 18:02:19.649Z |
Dual audience architecture — humans and AI from the same data LOGOS must serve humans through the UI and AI systems through the API with equal fidelity from a single source of truth. No separate data stores, no sync problems, no second-class access for either audience. Why It's Needed Most knowledge systems are... | REQUIREMENTS | I | 0 | 2026-03-01 17:58:15.114Z |