← back

Legal // terms of collaboration

Terms & Conditions

These terms govern collaboration, delivery of services, products, prototypes, authored outputs, software, hardware, edible objects, consultations, and operational systems provided under the brands crystOS, HELiPORT, Pusinkárna, and related projects.

This is not an anonymous industrial service.

This is authored work, systems thinking, proprietary know-how, development, taste, software, hardware, text, design, operational analytics, and solutions built on the reality of a specific person, business, or project.

Collaboration only exists where it makes sense to both parties.

01Core Principle

I reserve the right to decline, terminate, or discontinue collaboration if I don't sense trust, respect, alignment, safety, purpose, or healthy communication from the other party.

This principle does not mean discrimination based on legally protected grounds. It means the right to protect my own capacity, creative process, mental safety, output quality, and the direction of projects that carry my name.

Collaboration is not a service you can demand.
It's a conscious agreement.

02Who the System Is For

These terms apply primarily to:

  • operational and analytical consultations
  • software development, prototypes, interfaces, and internal systems
  • hardware, firmware, and experimental devices
  • licenses for using authored software
  • HELiPORT and related operational systems
  • Pusinkárna and authored gastronomic products
  • concepts, branding, design, and other creative outputs
  • prototypes, test versions, non-public systems, and authored solutions

Each project may have its own individual terms. When negotiated individually, they take precedence over these general terms.

03Collaboration Isn't Off-the-Shelf

Outputs are not anonymous commodities.

Every project is authored, developmental, or operationally specific. This means the result may not be a universal product for everyone. It's designed for a specific purpose, a specific reality, and a specific use.

The goal is to deliver a functional shape.

04Starting Collaboration

Collaboration begins upon confirmation of an order, contract, offer, brief, verbal agreement, written agreement, payment of a deposit, or any other clear consent from both parties.

Confirmation of collaboration also occurs when the client begins using the delivered output, software, design, prototype, consultation, system, text, design, or other authored output.

For software, interfaces, systems, text, design, know-how, or other authored works, collaboration is concluded as an author/license agreement granting permission to use the output — not as a transfer of intellectual property ownership.

05Creative License Instead of Ownership

Unless agreed otherwise in writing, the client does not acquire ownership of the authored work, source code, know-how, concept, methodology, system, or internal logic of the solution.

The client receives only a license to use the agreed output within the scope specified in the offer, order, or individual agreement.

The license, unless otherwise agreed, is:

  • non-exclusive
  • non-transferable
  • time-limited per specific agreement
  • for the agreed purpose only
  • for the client or specific operation only
  • without the right to provide the output to third parties
  • without the right to copy, sell, sublicense, or publicly distribute the solution beyond the agreed purpose

Software, interfaces, firmware, texts, design, documentation, methodologies, and system logic remain the authored output of the author.

The client isn't buying my thinking.
They're buying the right to use a specific result within a specific scope.

06Source Code, Know-How, and Internal Logic

Source code, internal system structure, firmware, database designs, algorithms, documentation, working notes, prototypes, development versions, internal know-how, and non-public parts of the system are not included in the license unless explicitly agreed.

Access to source code or internal documentation can only be agreed individually and under separate terms.

Not permitted:

  • reverse engineer the system
  • copy the internal logic of the solution
  • transfer the system to third parties
  • create derivative products without consent
  • imitate the architecture, interface, or operational logic for competitive use

The system may be used.
Not dismantled and stolen.

07Payment

Payment is primarily in cash. For payments where legal regulations require non-cash payment, payment will be made electronically.

For HELiPORT system license subscriptions, payment will be made electronically, on the regular date specified at the time of order or per individual agreement.

Unless otherwise agreed, a deposit may be required before work begins. The deposit reserves time, capacity, materials, development, or a production slot. Work may only begin after the deposit is paid.

08Pricing

Price is set individually based on scope, complexity, time, risk, development, materials, authored value, license, and operational impact.

Price isn't just for time.
Price is for the ability to create a result that has shape, meaning, and function.

For development, software, analytical, and authored projects, pricing may be broken into: initial audit, solution design, prototype, implementation, license, service, further development, consultations, or operational support.

For Pusinkárna, pricing may be based on the product, size, ingredients, time requirements, availability, recipe development, individual requests, and production risk.

09Changes to Brief

Any change to the brief may change the price, scope, and deadline. If the client changes requirements after work has begun — adds features, changes the concept, requests a different scope, different use, different number of locations, or different output format — this constitutes a change to the brief.

A change to the brief isn't automatically covered by the original price.
A new request means a new calculation.
The system isn't an infinite vessel for additional wishes.

10Prototypes and Experimental Products

Some outputs may be in the nature of a prototype, beta version, test system, experimental interface, or development concept. Such outputs may not be a final commercial product. They may contain limitations, developmental shortcomings, and a need for testing, adjustments, calibration, or further development.

A prototype isn't a promise of perfection.
A prototype is the first functional shape of reality.

11HELiPORT and Operational Systems

HELiPORT is a system combining hardware, software, firmware, operational analytics, records, and physical measurement of reality. The system can work with weighing, inventory records, stocktaking, transfers, discrepancies, operational data, and other signals.

HELiPORT does not replace accounting, legal auditing, security services, or human resources management.

HELiPORT helps measure reality.
The client is responsible for decisions they make based on the data.

12Pusinkárna

Pusinkárna is an authored gastronomic project. Products are made according to capacity, ingredient availability, technical capabilities, the author's decision, and a specific agreement.

Gluten-free products are created with maximum care regarding composition and process, but the client must disclose allergies, intolerances, health restrictions, and other essential information in advance.

Individually made, perishable, or personalized gastronomic products cannot be returned after delivery simply because the client changed their mind about the order.

13Dream Pro and the Lucid Interface

Dream Pro is an experimental concept of a lucid interface. The system is intended for development, testing, conceptual use, or future prototyping.

Dream Pro is not a medical device, diagnostic tool, therapeutic method, or substitute for professional care unless explicitly certified and stated otherwise.

Any use of the device, concept, or prototype in relation to sleep, the body, consciousness, the REM phase, or biofeedback occurs only under conditions that are safe and appropriate to the stage of development.

14Confidentiality

The client may not, without consent, disclose non-public information, designs, prototypes, approaches, internal documents, system logic, pricing, working notes, source code, non-public procedures, or other confidential information.

Likewise, the author undertakes to protect the client's confidential information if it has been communicated as confidential or if it is clear from the nature of the matter that it is.

Trust is the infrastructure of collaboration.

15Communication

Communication should be substantive, clear, and respectful of both parties' capacity.

Not tolerated: pressure, threats, unclear briefing, chaotic changes to the brief without agreement, or attempts to force work outside the agreed scope.

If communication begins to destroy the process, collaboration may be suspended or terminated.

16Right to Refuse a Party

I reserve the right to refuse or terminate collaboration with a person, business, or entity that acts dishonestly, toxically, aggressively, opaquely, manipulatively, dangerously, unreliably, or fundamentally contrary to the project's values.

This right serves to protect the quality, safety, creative process, and integrity of the system.

17Timelines

Timelines are indicative unless marked as binding in writing.

For authored, developmental, gastronomic, hardware, or prototype work, timelines may be affected by: changes to the brief, component availability, ingredient availability, testing, calibration, illness, technical complications, missing materials from the client, force majeure, or other unexpected circumstances.

A quality result sometimes needs time.

18Acceptance of Output

The client is required to check the output upon delivery or within the agreed timeframe.

If the client begins using, publishes, installs, deploys, tastes, accepts, makes available to third parties, or otherwise uses the output, it is considered accepted unless an apparent defect is reported without undue delay.

For software, hardware, and prototypes, acceptance may be linked to testing, calibration, or remediation of identified defects.

19Claims and Repairs

Required information: what exactly isn't working, where the problem manifests, when it occurs, what its impact is, what the conditions of use were, and whether the problem recurs.

For software and hardware, the following are not considered defects: a change in the client's wishes, misuse, third-party interference, operation outside recommended conditions, or expectations not included in the brief.

For authored and creative outputs, a purely subjective change in taste after completion is not considered a defect.

20Liability

Liability is limited to direct damage caused by a demonstrable defect in the delivered output, up to a maximum of the price of the specific order or license, unless legal regulations require otherwise.

The author is not liable for: misuse of the system, third-party interference, decisions the client makes based on their own interpretation of data, outages of external services, failure of internet, hosting, suppliers, or equipment outside the author's control, expected profit not explicitly guaranteed, or problems caused by incomplete or inaccurate information from the client.

21Termination of Collaboration

Collaboration may be terminated by agreement, completion of the output, exhaustion of the license, expiration of the term, material breach of terms, or loss of trust.

Upon termination of collaboration, the author is entitled to payment for work already performed, materials used, development, preparation, reserved capacity, and licenses provided.

Deposits are non-refundable if work has already begun, capacity has been reserved, materials purchased, output created, or a date blocked — unless otherwise agreed.

22References and Portfolio

The author reserves the right to reference completed work as a portfolio piece, provided it doesn't violate confidentiality, client security, or individual agreement.

For non-public, sensitive, or internal projects, the scope of reference may be limited. If the client does not want to be referenced, this must be agreed in advance.

23Ethics Filter

I do not provide work, licenses, products, or systems where the result would serve to knowingly harm people, exploit vulnerability, manipulate, engage in illegal activity, steal, circumvent security, or serve any other purpose contrary to the project's values.

I am not a person without limits.

24Final Provision

These terms are an attempt to set a clean interface.

For the work.

For the trust.

For the creative process.

Rules aren't invented by higher intelligence.

They're invented by people.

And when rules don't work, they can be designed better.

That's why these terms exist.

As a custom architecture of collaboration.