The complete guide to memodya
Learn how to orchestrate complex engineering workflows, manage strict semantic modeling, and collaborate with your team in real-time.
1. Organizing Your Work
memodya utilizes a clean, structured interface to keep your engineering initiatives organized without clutter. The Dashboard serves as your mission control for managing all your work.
Create a Memo: Quickly initiate a new memo using the primary action button. A memo is a kind of project holding together all the great workflows that are inside.
Pinning & Quick Access: Pin important memos to instantly access them from the Quick Access section, which also tracks recently modified files.
Spaces Organization: All memos live in the Default Space. You can create custom Spaces and organize your memos simply via drag-and-drop.
Context Tools: Right-click on a Space to physically rename, move, or delete it. Right-click on a Memo to remove it from a view or delete it permanently.
Global Search: Instantly locate specific deliverables across all spaces using the intelligent central search bar.
memodyaQuick Access
- Start
- Pinned
- Last modified
- Shared with me
Spaces
- Default Space
- Project Alpha
- Marketing Launch
Start
Pinned
Process Architecture v2
Last Modified
Circular Biomass Workflow
Supplier Sync Pipeline
Empty Slot
The Details Modal
Clicking a memo gracefully reveals a centered details modal. From here, you can seamlessly rename your memo, edit its description, or open the modeling editor to work on all the details.
memodyaQuick Access
- Start
- Pinned
- Last modified
- Shared with me
Spaces
- Default Space
- Project Alpha
- Marketing Launch
Start
Pinned
Process Architecture v2
Last Modified
Circular Biomass Workflow
Supplier Sync Pipeline
Empty Slot
2. The Canvas
When it's time to map out the detailed mechanics of your workflows, you enter the Canvas. This is where high-level plans turn into actionable, connected logic.
Modeling Tree: The left sidebar structured repository of all elements. Quickly browse and manage your Diagrams, Methods, I/Os (Documents, Models, Statements), and Slots (Processes, Tools, Roles).
Canvas Diagramming: The central workspace allows for visual composition of complex relationships. Elements from the modeling tree are dragged here to physically connect steps, inputs, and outputs.
Right Sidebar: Selecting an element—whether from the visual canvas or the structural left tree—instantly opens the right sidebar. This acts as the central interface for deeper specification. For instance, clicking a Method allows you to thoroughly configure its name, step-by-step descriptions, constraints, and attached file links without cluttering your core diagram workspace.
Guaranteed Consistency: Because everything is connected under the hood, updating an element's details instantly reflects everywhere it's used across all your diagrams.
memodyaSystem Spec
User Stories
Jira
Docs
Sarah
Tom
Method: Requirements
Detail: Gather insights and specifications
Arch Design
Draw.io
AWS
Elena
Marc
Method: Sys Architecture
Detail: High-level technical infrastructure
Component Spec
Figma
Alex
Method: UX/UI Design
Detail: Crafting the user journey
Release Candidate
IDE
GitHub
CI/CD
Floh
Antron
Stefe
Method: Build Factory
Detail: DevOps and Component implementation
2.1 Modeling Elements
Before you start building, it is crucial to understand the available semantic alphabet. memodya relies on a strict set of standardized elements that map directly to real-world engineering concepts.
Method Node
The core engine component. Methods define actions, algorithms, and transformations. They ingest inputs, process them using defined slots, and yield outputs.
I/Os (Inputs & Outputs)
Model
It's a simplified way to show how something looks, works, or behaves. (typically formal).
Document
A written file or specification (typically informal).
Statement
Verbal or explicit assertions.
Slots (Execution Context)
Process
The process to which the method is allocated to.
Tool
The (software) tool used to execute the method.
Role
The abstract role required.
Person
A specific person.
2.2 The Modeling Palette
When creating new logic, the floating Modeling Palette provides all your building blocks. Simply drag the items from the palette directly onto your canvas to instantly instantiate new elements.
Drag to Place: Pick up a method, new document, or any other element from the palette and drop it into the diagramming area to place an element on your workspace.
Direct Allocation: Special feature: Drag I/Os or Slots and drop them directly onto a Method node. They will automatically be allocated and connected, saving you clicks and repetitive linking.
2.3 Diagrams & Graphical Elements
There is the left sidebar which contains all the "real" elements a memo consists of. A memo can contain several diagrams (the modeling area) to create workflows by putting methods together.
When creating a new element on a diagram, an element is seamlessly created in the sidebar and placed on the diagram. The diagram provides the visual representation of the "real" structural element. A single element can be used several times across different diagrams simultaneously.
No Class Instance Principle: This means changing the name of an element in the sidebar automatically changes all the names of that same element across every diagram. The exact same synchronization happens when changing an element directly on a diagram.
Graphical Delete: Delete just the graphical representation on a selected diagram. The structural "real" element safely persists in the sidebar.
Total Delete: Deleting the "real" element directly from the sidebar structurally destroys it, automatically removing all graphical representations from any diagram.
2.4 Connecting
True architectural power comes from linking logical methods together. The created output of one method often serves directly as the required input for the next method. A single generated output document can be branched and connected to several different methods as inputs simultaneously.
memodya allows you to draw physical connections between the I/O nodes of your methods. Try connecting the Output of the first method to the Input of the second method dynamically in the diagram below to establish a process flow.
Connection Types
Strong Relations (I/O Connections): Explicitly linking the output of one method directly into the Input of another method signifies a rigid dependency and strong artifact relation.
Loose Relations (Direct Method Connections): Linking two methods directly to one another without using I/O slots simply illustrates that a sequential relation or conceptual handoff exists between them, without specifying strict data dependencies.
System Spec
Feedback
System Model
Jira Core
System Eng.
Analyze Requirements
Blueprints
Figma
Cloud Arch
Software Arch.
Design Architecture
Flow Connected!
The output model automatically routes into the next method process.
Ready to Start Modeling?
Dive into your workspace, invite your team members, and let memodya transform your chaotic engineering plans into structured daily execution.