Learn how we use cookies and other tracking technologies on our website to improve user experience.
Last Updated: November 15, 2023
1. Introduction to Cookies
This website uses cookies and other browser storage. Analytics starts only after you accept the analytics category; chat has a separate choice. Simply opening or continuing to use the website does not change your choices.
A cookie is a small data file managed by the browser. Local storage (localStorage) and the offline cache are different browser features; this policy covers them as well.
2. Types of Cookies Used on the Site
The current website uses the following storage mechanisms and optional services:
Storage or service
Purpose and activation
mfl-consent — localStorage
Stores separate analytics (stats), marketing (mkt) and chat (chat) choices. This is not a cookie.
Google Analytics 4 — _ga, _ga_<id>
Analytics cookies for distinguishing visits and sessions. GA4 loads only after analytics consent.
Chatwoot — mfl.support
Support conversations. The external chat connection starts only after separate chat consent and use of the chat launch button.
PWA cache — Cache Storage
Local copies of public pages and presentation assets for offline use. Form submissions and PHP/API responses are excluded.
mfl.ide.layout.v1 — localStorage
Stores panel sizes, the selected sidebar, terminal view, layout, content zoom, interface density and theme in your own browser. It contains no form text or command history and is not sent to a server.
The marketing choice is stored separately. This alone does not mean a Google Ads or Meta Pixel tracking tag is installed; the current website code does not load a separate tag of either kind.
3. Managing and Disabling Cookies
Open your choices at any time with the Cookie settings button in the footer. Choose necessary-only operation, accept all categories, or select analytics, marketing and chat individually.
Withdrawal disables further operation of the affected services on this page and clears affected optional storage accessible to the website. The page may reload to stop an analytics or chat service that has already loaded.
To remove the preferences completely, clear the website's browser data as well: deleting only cookies does not necessarily remove localStorage. Clearing browser data does not automatically request deletion of data already held by an external service.
4. Third-Party Cookies
Google Analytics 4: website analytics, only after accepting the analytics category.
Chatwoot at mfl.support: support chat started separately. Choosing chat does not start analytics by itself.
Locally served fonts: font files load from our own website; the browser does not request a Google Fonts download.
See Google's documentation for GA4 cookie names and configurable expiry. A documented default does not establish this website property's actual configuration.
5. Cookie Storage Duration
The current implementation assigns no automatic expiry to mfl-consent. The choice remains in local storage until you change it, clear website data, or the browser removes that data.
The actual lifetime of GA4 cookies depends on Google tag and GA4 settings and browser restrictions. Chat storage depends on the chat service's configuration; we do not state an unverified expiry period here.
Website updates may replace or remove versioned offline cache contents. You can also remove local copies through your browser's website-data controls.
Workspace preferences have no automatic expiry. Reset layout saves the defaults; clearing website data in your browser removes the stored preferences completely.
6. Privacy Connections
This Cookie Policy supplements the MyForge Labs Privacy Policy. We recommend reading the Privacy Policy as well to get a complete picture of how we collect, use, and protect your data.
GDPR Compliance
Under the European General Data Protection Regulation (GDPR), we can only use non-essential cookies (e.g., for marketing or analytical purposes) with your explicit consent. Therefore, upon your first visit to our website, we ask for your consent via a cookie consent banner. You can modify or withdraw your consent at any time through the cookie settings panel or your browser settings.
Data Processing Information
For further information regarding the processing of data collected by cookies, as well as your rights and how to exercise them, please read our Privacy Policy.
7. Changes to the Cookie Policy
We reserve the right to update or modify this Cookie Policy from time to time to reflect changes in website practices, legal requirements, or for other reasons. The updated Cookie Policy will be published on our website, along with the modification date.
Please review this policy when it changes. Your optional-service choices remain controlled by the cookie settings panel.
Access to Previous Versions
If you would like to view previous versions of this Cookie Policy, please contact us using the details below.
8. Contact Us
If you have any questions about our use of cookies or this Cookie Policy, please contact us:
The complete system behind kisgepcentrum.hu: web shop, equipment rental, service intake, parts search and customer accounts — one platform shared with the in-store kiosk and staff workspaces.
A workplace wellbeing platform that grew out of the instruments of a doctoral research project: research questionnaires, management reports and the Balance module, which rewards healthy habits.
Automated processing of incoming supplier quotes, designed around a machine-parts distributor’s workflow: items extracted from e-mails, PDFs and spreadsheets feed a comparison matrix, with the original source behind every number.
Compare the demonstrated capabilities and current status. Each project was built for a different purpose.
Select two projects from the cards above.
Includes your filter and selected projects.
MYFORGE / DELIVERY LABINTERACTIVE STUDIO DEMO
Great software starts with better decisions.
We understand the business problem, design the system and build it in steps you can inspect. Step inside the studio: choose a project and explore how research, human decisions and AI-assisted development connect.
SELECTED WORK STAGEbrief.mdResearch and brief · manual steps available01 / 04
RESPONSIBILITY AND DELIVERABLEGemini + NotebookLM
Sources, open questions and an SSP brief.
WHAT DOES THIS GIVE YOU?
Clarity before commitment.
Clarifying the goal and constraints together helps decide what belongs in the first usable version.
⑂
Before the next stageWe agree which problem to solve and how we will know it has been solved.
SPECIALIST ROLES. SHARED CONTEXT.
The right tool for each part of the work.
Responsibilities follow the selected stage.
✦
Gemini + NotebookLM
Research and sources
role example
↳KGC-Bérlés
Which source supports each claim?
A single machine can be linked to a rental request, accessories, spare parts and a service case. The challenge was to preserve that context when a customer moves from the website to the store, or another team member takes over the conversation.
✳
BMAD + Claude
Planning and work breakdown
role example
↳KGC-Bérlés
How does the brief become a checkable plan?
Customer-facing and internal web application development: catalogues, request submission, customer records, case-based communication, and counter and service views. The scope also includes the parts-engine interface, kiosk interaction, and editing, publishing and scheduling display programmes. In September 2026 the system gained the web shop, the full service workflow and customer accounts, and went into production.
>_
Codex
Review and tests
role example
↳KGC-Bérlés
What evidence will verify the change?
Does the desktop parts diagram lead to the right part number and itemised enquiry?
SSPThe shared foundation for development
01 / Goal
The complete system behind kisgepcentrum.hu: web shop, equipment rental, service intake, parts search and customer accounts — one platform shared with the in-store kiosk and staff workspaces.
02 / Context
A single machine can be linked to a rental request, accessories, spare parts and a service case. The challenge was to preserve that context when a customer moves from the website to the store, or another team member takes over the conversation.
03 / Constraints
Customer-facing and internal web application development: catalogues, request submission, customer records, case-based communication, and counter and service views. The scope also includes the parts-engine interface, kiosk interaction, and editing, publishing and scheduling display programmes. In September 2026 the system gained the web shop, the full service workflow and customer accounts, and went into production. The platform has been running in production at kisgepcentrum.hu since September 2026, and development continues. Online rental requests require staff confirmation. Full ERP synchronisation, online card payments and automatic invoicing are separate workstreams; acceptance testing on the physical shop kiosk remains outstanding.
Does the desktop parts diagram lead to the right part number and itemised enquiry?
SAMPLE DOCUMENTS
M↓
PROJECT DOCUMENT · ILLUSTRATIVE SAMPLE
Defining the brief
The goal, context and acceptance criteria in one place.
# KGC-Bérlés / brief.md
> ILLUSTRATIVE SAMPLE · Based on public portfolio information. Not a client brief or approved project plan.
## Research · Gemini + NotebookLM
Reviewing the sources leads to a checkable brief. This example uses the portfolio and does not start live research.
## SSP / Goal
The complete system behind kisgepcentrum.hu: web shop, equipment rental, service intake, parts search and customer accounts — one platform shared with the in-store kiosk and staff workspaces.
## SSP / Context
A single machine can be linked to a rental request, accessories, spare parts and a service case. The challenge was to preserve that context when a customer moves from the website to the store, or another team member takes over the conversation.
## SSP / Constraints
Customer-facing and internal web application development: catalogues, request submission, customer records, case-based communication, and counter and service views. The scope also includes the parts-engine interface, kiosk interaction, and editing, publishing and scheduling display programmes. In September 2026 the system gained the web shop, the full service workflow and customer accounts, and went into production.
The platform has been running in production at kisgepcentrum.hu since September 2026, and development continues. Online rental requests require staff confirmation. Full ERP synchronisation, online card payments and automatic invoicing are separate workstreams; acceptance testing on the physical shop kiosk remains outstanding.
## SSP / Checkable outcome
Suggested acceptance question; verification pending:
- [ ] Does the desktop parts diagram lead to the right part number and itemised enquiry?
## Next handover · BMAD + Claude
- [ ] Separate sources, facts and open assumptions
- [ ] Review the SSP goal, constraints and acceptance criteria together
- [ ] Approve the implementation direction and verification approach
## Learning loop
Research may also start from previously approved lessons. A new finding needs a source, crystallization and an approved destination before propagation.
## Status and limits stated in the portfolio
The platform has been running in production at kisgepcentrum.hu since September 2026, and development continues. Online rental requests require staff confirmation. Full ERP synchronisation, online card payments and automatic invoicing are separate workstreams; acceptance testing on the physical shop kiosk remains outstanding.
Source: https://www.myforgelabs.com/en/case-studies/kgc-rental/
EXPERIENCE BECOMES AN ASSET
The project ends. The knowledge stays.
Research can also use lessons that have already been reviewed and approved.
◷
Outcome and test evidence
Record the actual result, environment and limits.
◇
Crystallization
Select and check the lasting lesson within the raw experience.
MyForge Superintelligence connects project context, specialised AI roles and developer decisions. A valuable lesson from one project becomes retrievable knowledge for the next.
Select a node for details. Drag to rearrange, or use arrow keys while focused. The list below also works on mobile.
Browse the nodes 13
capabilities / reusable methods
Methods selected for the work at hand.
02 / discord handoffs
From a client request to a reviewed solution.
LOCAL DEMO · NOT LIVE
Every handoff has an owner, a purpose and a tangible output. This scripted example illustrates Discord-based collaboration: follow the request through research and development to human approval.
# project-handoffReady to play
ClientClient bot
CURRENT HANDOFFAn idea starts a shared conversation
Outputclient-request.md
◉
Waiting for a human decision.
Approval continues only this local example.
The loop is complete.The next task can start from reviewed knowledge.
Local illustration, with no live connection. Human approval is a separate step.
MYFORGE / ERP In development · a closer look is coming soon
One business. Connected operations.
We have been developing an ERP that connects equipment rental, service, inventory and sales. Its purpose is to keep the history of an asset, partner or work order available at the next business step. A closer look at the development is coming soon.
KGC ERPSystem layersARCHITECTURE
WORKSPACE
The daily workspace
Staff interfaces suited to each role
React + Vite
BUSINESS LOGIC
Business workflows
Rental · service · inventory · sales
Node.js + NestJS
DATA & JOBS
The operational foundation
Related data and queued background work
PostgreSQL + Prisma · Redis + BullMQ
Shared foundation: roles, organisational separation and traceable operations.
BUSINESS MODULES / 01—05
Workflows connect across business functions.
MODULE / 01
Rental and equipment
The equipment journey from pricing through checkout and return to its related contract. Rental operations have their own business module.
MODULE / 02
Service and work orders
Repair tasks, work orders and warranty cases are organised as connected workflows in dedicated service modules.
MODULE / 03
Inventory and sales
Modules cover products and stock movements from goods receipt and stocktaking to sales operations.
MODULE / 04
Partners and documents
Partner records, business documents and related communication provide context for the same case.
MODULE / 05
Access and organisations
Roles, audit trails and separated organisational workspaces define who can access each part of the business data.
ENGINEERING / STACK
The engineering behind the operations.
A modular TypeScript monorepo with a Node.js and NestJS API, React–Vite workspaces, PostgreSQL–Prisma data handling and Redis–BullMQ background jobs. Dedicated access and tenant layers separate data belonging to different organisations.
↳ Node.js + NestJS
A modular server-side API and business services.
↳ TypeScript
Shared types and explicit data contracts across the monorepo.
↳ React + Vite
Browser-based staff workspaces.
↳ PostgreSQL + Prisma
Relational business data and typed database access.
↳ Redis + BullMQ
Queued background jobs and scheduled processing.
In development. More to share soon.
The ERP in development is a separate project from the KGC-Bérlés web application. Modules and integrations are progressing incrementally; a public demonstration and operational rollout are separate delivery steps.