When we started Vinova Lab, we were not trying to build another software company.

The world already has enough software. What it needs are better tools.

Artificial Intelligence represents one of the most significant technological transformations of our time. Yet many organisations still struggle to translate its potential into meaningful and measurable outcomes.

Too often, AI becomes a demonstration of technology rather than a practical solution to a real problem.

We founded Vinova Lab because we believe technology should progressively disappear into the background.

People should not need to notice the AI.

They should notice that their work has become easier.

They should notice that decisions have become faster, knowledge has become more accessible, and complexity has become manageable.

Every product we build should remove friction.

Every technology decision should contribute to meaningful value.

Every customer challenge should teach us something that improves the next solution and strengthens the next product.

We believe products create lasting value.

Consulting helps us understand real problems and finances innovation.

Research keeps us curious.

Innovation keeps us relevant.

Vinova Lab exists to build intelligent products that improve how people and organisations work, learn, decide, and manage complexity.

We are not interested in building technology for its own sake.

We are building practical tools that future generations may simply consider normal.

This is only the beginning.

The Vinova Lab Blueprint — Version 0.1 — Confidential Working Draft

Mission

Vinova Lab exists to transform Artificial Intelligence into practical solutions that automate complex work, augment human capabilities, and give people and businesses back their most valuable resource: time.

Vision

Most of what organisations know is locked inside documents.

Contracts, invoices, correspondence, reports — the operational memory of any business lives there. Yet to machines, documents remain opaque. They can be stored and retrieved, but not truly understood. Not contextualised. Not related to each other.

Databases solved this problem for structured data decades ago. Documents never had their equivalent.

We are building it.

An intelligence layer that reads documents the way databases read records — classifying them, extracting what is relevant, understanding the relationships between them, and placing every document in the context of everything it connects to.

The organisations and builders who work on top of this layer will not think of it as AI. They will think of it as infrastructure — the kind that, once it exists, makes you wonder how operational work was ever done without it.

Why Vinova Lab Exists

Technology is evolving faster than many organisations can adapt.

Artificial Intelligence offers extraordinary opportunities, but many businesses struggle to convert those opportunities into measurable operational value.

Vinova Lab exists to bridge that gap.

We believe AI should not remove human responsibility or value.

It should reduce complexity, automate repetitive work, improve access to knowledge, and allow people to focus on higher-value activities.

The Vinova Lab Blueprint — Version 0.1 — Confidential Working Draft

Vinova Lab is fundamentally a Product Company.

Products are our destination. Consulting is our engine. Research is our investment. Innovation is our culture.

Every strategic decision should strengthen at least one of these pillars without materially weakening the others.

Product First

Products represent the company's long-term source of value.

The engine is the foundation. Vertical products built on it are the expression. The platform exposed to builders is the multiplier.

Consulting projects should be selected and designed so that they contribute knowledge, reusable capabilities, domain understanding, or financial resources to the engine and the product portfolio.

Build Once, Reuse Intelligently

Every capability developed — whether for a consulting engagement or a vertical product — should be evaluated for its potential to strengthen the shared engine platform.

The engine is not a byproduct. It is the primary asset under construction.

Vertical products demonstrate the engine's value in specific domains. The platform exposes that value to builders who want to create their own.

Reuse must never compromise customer confidentiality, security, or contractual obligations.

Long-Term Thinking

Vinova Lab prioritises sustainable growth over short-term revenue.

Major decisions should be evaluated not only according to their immediate return, but also according to their impact on the company over the following five to ten years.

Engineering Excellence

Quality, reliability, security, and maintainability are core product attributes.

Technical debt may occasionally be accepted, but only when it is:

• consciously identified;
• documented;
• justified;
• assigned an owner;
• scheduled for remediation.

Technology Disappears

Users should not need to think about the engine.

They should notice that their documents have become useful, their obligations visible, their decisions faster.

A product succeeds when its technology is invisible. Every interface decision, every workflow, every output should reduce cognitive load — not expose technical complexity.

Intelligence Compounds

Every document processed by the engine generates structural signal.

That signal — stripped of all personal data, sensitive information, and identifying content — feeds a continuously improving model of how documents in a given domain are structured, classified, and related to each other.

Documents always remain at their source. No original document is retained. Only the structural and semantic patterns extracted from it, fully anonymised, become part of the engine's growing intelligence.

The consequence is asymmetric over time: the longer the engine operates across its domains, the more precise it becomes — in ways that no competitor starting from zero can replicate.

Continuous Learning

Every domain we enter teaches the engine something new.

Every vertical product surfaces new document types, new classification challenges, new relationship patterns.

Innovation is not limited to technology. It includes the discovery of new domains where operational knowledge is trapped in documents and waiting to be unlocked.

The Vinova Lab Blueprint — Version 0.1 — Confidential Working Draft

Vinova Lab aims to become an international software company recognised for building the intelligence layer that closes the gap between documents and structured data — and for the vertical products that make that layer valuable in the real world.

The Engine

At the centre of everything Vinova Lab builds is a document intelligence engine.

The engine reads documents the way databases read records. It classifies them, extracts what is relevant, understands the relationships between them, and places every document in the context of everything it connects to.

Over time, the engine becomes the company's primary strategic asset — the accumulated intelligence of every domain it has operated in, built from the ground up through real operational use.

The engine's core capabilities include:

• document classification and type recognition;
• structured data extraction;
• relationship and context mapping between documents;
• temporal awareness — expiry, renewal, version history;
• identity and access management;
• knowledge retrieval;
• security and governance;
• integration services;
• reusable interface components;
• monitoring and evaluation.

Vertical Products

Vertical products are how the engine creates value for end users.

Each vertical applies the engine to a specific domain — a defined set of document types, workflows, and operational problems that matter to a well-defined audience.

rAInty is the first. Future verticals will address other domains where operational knowledge is trapped in documents and where the engine's capabilities create meaningful, measurable outcomes.

Users of vertical products do not interact with the engine. They interact with a solution designed for their domain. The engine is invisible to them.

The Platform

The engine will also be made available as a platform — a subscription API for organisations and builders who want to create their own vertical products without rebuilding the underlying document intelligence from scratch.

This tier extends the engine's reach beyond Vinova Lab's own products and creates a new category of builder: one who can develop document-intelligent applications without needing to solve the hard problems of classification, extraction, and contextualisation.

Why the Portfolio Compounds

A portfolio of vertical products is not primarily a risk-management strategy.

It is an intelligence-amplification strategy.

Every new vertical exposes the engine to document types, classification challenges, and relationship patterns it has not encountered before. That exposure makes the engine more capable — and a more capable engine makes every existing and future vertical product better.

The compounding effect is asymmetric: a competitor entering a single vertical starts with an engine that has seen only that domain. Vinova Lab's engine has seen every domain it has ever operated in, and improves continuously across all of them.

Products share the engine while retaining independent branding, positioning, pricing, customer experience, and product roadmaps. Each vertical succeeds or fails on its own merits without threatening the engine or the broader portfolio.

Long-Term Value Drivers

Vinova Lab's long-term value should derive primarily from:

• the engine and its accumulated domain intelligence;
• proprietary training data generated through real operational use;
• vertical products with recurring revenue;
• the platform and its builder ecosystem;
• intellectual property;
• customer trust;
• specialist domain knowledge;
• scalable distribution.

The Vinova Lab Blueprint — Version 0.1 — Confidential Working Draft

Vinova Lab creates value through two complementary activities.

Document Intelligence Products

Vinova Lab develops proprietary software products built on its document intelligence engine, commercialised through models such as:

• subscription;
• software licensing;
• usage-based pricing;
• platform fees;
• enterprise agreements;
• selected professional services connected to product adoption.

Vertical products apply the engine to specific document-intensive domains, serving end users with solutions tailored to their industry and workflows. rAInty is the first. Future verticals will address other domains where operational knowledge is trapped in documents and where the engine's capabilities create meaningful, measurable outcomes.

The platform makes the engine available as a subscription API for organisations and builders who want to develop their own document intelligence solutions without rebuilding the underlying engine from scratch.

Document Intelligence Products represent the company's primary long-term objective.

Document Intelligence Consulting

During its initial growth phase, Vinova Lab will perform selected tailor-made engagements focused on:

• document-driven process automation;
• document intelligence implementation;
• workflow automation;
• integration of document intelligence into existing systems and operations;
• knowledge management;
• customer-specific document intelligence solutions.

The first expected customer is an Italian holding company connected to one of the founders.

The initial work for this customer will involve document intelligence solutions aimed at automating document-driven internal business processes.

Revenue generated from these activities will help finance:

• product development;
• research and development;
• technology infrastructure;
• future employees and collaborators;
• commercialisation;
• market validation;
• new product experimentation.

Consulting is therefore not the company's final destination.

It is an innovation, learning, and funding engine — and a source of real-world document complexity that continuously strengthens the engine platform.

Strategic Balance

Vinova Lab must avoid becoming dependent on low-margin or non-strategic custom development.

A customer engagement should be evaluated according to:

• financial value;
• strategic relevance;
• learning potential and contribution to the engine;
• reusable technology potential;
• relationship value;
• impact on product development capacity;
• risk of distraction from the core roadmap.

Not every consulting opportunity should be accepted.

The Vinova Lab Blueprint — Version 0.1 — Confidential Working Draft

Vinova Lab's product strategy is built on a single organising principle: every product we build should make the engine smarter, and a smarter engine should make every product better.

Products are not independent initiatives. They are both the expression of the engine's capabilities and the source of its growth.

Domain Selection

Not every market is right for Vinova Lab.

The company focuses on domains that are document-intensive by nature — where a significant portion of operational work involves reading, classifying, extracting information from, or acting on documents.

A domain is a strong candidate when:

• people spend meaningful time processing, searching, or managing documents as part of their core work;
• documents in that domain have relationships to each other — a contract references a party, a bill references a supplier, a compliance document references a regulation;
• errors or missed obligations in document management carry real operational, financial, or legal consequences;
• the domain has recurring, predictable document types that can be learned and generalised;
• existing solutions are either too generic (spreadsheets, email, shared drives) or too expensive and rigid (large enterprise software);
• the audience is large enough to support a product with sustainable recurring revenue.

Product Discovery

Products may originate from three main sources.

Market Observation — identifying document-intensive domains where operational complexity is high and existing solutions are insufficient.

Customer Engagements — discovering patterns and recurring document challenges through consulting projects. Every engagement should be evaluated not only for its immediate value but for what it teaches the engine.

Internal Innovation — developing ideas through research, experimentation, and founder insight. As the engine matures, new vertical opportunities may emerge from capabilities the engine has already developed rather than from external observation alone.

The Bottom-Up Engine Model

Vinova Lab does not design the engine in the abstract and then build products on top of it.

The engine is built bottom-up — from real problems, in real domains, with real documents.

Each vertical product is a focused application of the engine to a specific domain. As the engine processes more documents in that domain, it develops deeper classification accuracy, richer relationship models, and more reliable extraction. Those improvements are then abstracted back into the engine platform and become available to every other product.

Product development and engine development are not separate activities. They are the same activity, approached from different angles.

Research Strategy

Vinova Lab's research strategy evolves with the company's resources and maturity.

In the founding phase, research is founder-led. It involves evaluating the landscape of available models, tools, and frameworks — identifying what can be adopted, adapted, or combined to build a first working vertical without requiring significant capital.

As products generate revenue and training data, the focus shifts to fine-tuning open-source models with domain-specific knowledge derived from real operational use. Document types, extraction patterns, and classification logic become increasingly specialised to the domains Vinova Lab operates in.

Over time, as proprietary training data accumulates, Vinova Lab may develop or retrain models purpose-built for specific document intelligence tasks — achieving levels of domain precision that general-purpose models cannot match.

At every phase, products are designed from day zero to generate structural training signal. Personal data and sensitive information are never retained. The signal that feeds future model improvement is always anonymised, structural, and derived — not a copy of the original document.

Product Qualification

An initiative should become a product only when it:

• operates in a document-intensive domain with recurring, predictable document types;
• solves a meaningful operational problem for a well-defined audience;
• can be offered to multiple customers;
• can scale operationally and technically;
• has a plausible commercial model;
• contributes document types and patterns that strengthen the engine;
• generates structural training signal through normal use;
• aligns with Vinova Lab's mission;
• can be supported sustainably.

Not every reusable component is a product.

Not every successful customer project should become a product.

Product decisions must be based on evidence, domain fit, and commercial potential — not on technical possibility alone.

Current Portfolio

rAInty is the first Vinova Lab product. It addresses the property management domain — a document-intensive vertical where landlords and property owners manage contracts, bills, correspondence, and compliance obligations across their portfolio.

Tender intelligence is the second vertical in development. It addresses the evaluation of public and private procurement bids — a process where organisations must analyse large volumes of technical documents, requirements, and compliance specifications to decide whether and how to respond. The document complexity, the recurring nature of the process, and the high cost of errors make it a strong fit for the engine.

Each product is built on the shared engine while retaining independent branding, positioning, pricing, customer experience, market strategy, and product roadmap.

Portfolio Growth

The portfolio should grow steadily — led by evidence of domain fit and commercial viability, not by ambition alone.

New verticals will be added when a domain meets the selection criteria, when the engine has sufficient capability to address it, and when the company has the resources to support it sustainably.

The Vinova Lab Blueprint — Version 0.1 — Confidential Working Draft

All intellectual property developed for Vinova Lab and its products should belong to Vinova Lab, subject to applicable law and properly executed agreements.

The document intelligence engine and the domain knowledge accumulated within it represent the company's primary and most strategically significant intellectual property. Unlike code — which can be rewritten — the engine's accumulated domain intelligence, classification models, and training data are the product of real operational use and cannot be replicated by a competitor starting from zero.

This includes:

• the document intelligence engine and its architecture;
• domain intelligence models, classification schemas, and extraction patterns;
• anonymised training datasets and the pipeline that generates them;
• document type taxonomies built through real-world processing;
• software and source code;
• models, configurations, and fine-tuned components;
• processing pipeline and orchestration logic;
• APIs and database schemas;
• designs and user-interface components;
• documentation;
• brands and trademarks;
• internal frameworks;
• knowledge bases;
• reusable integration components.

Open-Source and Third-Party Components

Vinova Lab's products are built in part on open-source models, frameworks, and libraries.

The use of open-source components must be managed carefully:

• the licence terms of every open-source component must be evaluated before adoption;
• licences that impose obligations on derivative works — including copyleft licences and model-specific licences common in the open-source model ecosystem — must be reviewed before fine-tuning or integration into proprietary products;
• open-source components must be tracked, documented, and attributed appropriately;
• the boundary between open-source components and Vinova Lab's proprietary additions must be clearly maintained.

Proprietary improvements, fine-tuning, and domain-specific adaptations built on open-source foundations remain the intellectual property of Vinova Lab, subject to the licence terms of the underlying component.

Customer Projects

Customer contracts should distinguish among:

• customer-owned data and documents;
• customer confidential information;
• deliverables created exclusively for the customer;
• Vinova Lab background intellectual property;
• third-party and open-source intellectual property;
• generic and reusable Vinova Lab engine capabilities.

Customer data, confidential information, or proprietary business logic must never be reused improperly.

Generic engine capabilities developed or improved during a customer project may remain part of the Vinova Lab platform only where this is legally, ethically, and contractually permitted.

Anonymised structural signal. When documents are processed as part of a customer engagement, structural and semantic patterns may be extracted in fully anonymised form — stripped of all personal data, sensitive information, and customer-identifiable content. These anonymised patterns, which bear no resemblance to the original documents or their specific content, may be used to improve the engine. Customer contracts must address this explicitly, making clear what is extracted, how it is anonymised, and what it is used for.

Contributors

Founders, employees, contractors, and external collaborators contributing to Vinova Lab products should execute appropriate confidentiality and intellectual-property assignment agreements.

Final legal provisions must be prepared and reviewed by qualified legal professionals in the applicable jurisdiction.

The Vinova Lab Blueprint — Version 0.1 — Confidential Working Draft

Vinova Lab is founded on two complementary leadership profiles.

Product, Technology and Innovation Leadership

This area is responsible for:

• company and product vision;
• product strategy;
• technology strategy;
• engine architecture and development;
• platform strategy;
• architecture;
• product roadmap;
• research and development;
• innovation priorities;
• platform evolution;
• product quality;
• strategic intellectual-property development.

Corporate and Operational Leadership

This area is responsible for:

• corporate administration;
• legal representation;
• operational management;
• financial management;
• contracts;
• commercial development;
• partnerships;
• relationships with banks and professional advisors;
• company compliance;
• business operations.

Neither area can independently create a successful company.

Vinova Lab depends on continuous alignment between product leadership and operational leadership.

Strategic and Operational Decisions

The future shareholders' agreement should distinguish among:

• ordinary operational decisions;
• strategic decisions;
• reserved matters;
• decisions requiring founder consultation;
• decisions requiring supermajority or unanimous approval.

Reserved matters may include:

• issuing new shares;
• admitting new shareholders;
• changing the company's principal business;
• selling the company;
• selling or exclusively licensing core intellectual property;
• taking debt above an agreed threshold;
• approving major investments outside the agreed plan;
• entering related-party transactions;
• closing a product line;
• changing founder control rights;
• approving a merger, acquisition, or liquidation.

The precise voting thresholds must be defined in formal legal documents.

The Vinova Lab Blueprint — Version 0.1 — Confidential Working Draft

Equity represents long-term ownership, responsibility, risk, and value creation.

It should not be considered compensation for isolated short-term tasks.

Ownership should reflect factors such as:

• original vision;
• intellectual contribution;
• engine and platform development;
• capital and financial risk;
• leadership responsibility;
• operational responsibility;
• commercial contribution;
• access to customers and markets;
• execution;
• long-term commitment;
• value created for the company.

Vinova Lab expects shareholders to contribute actively to the company's success.

Shareholders' Agreement Topics

The future shareholders' agreement should address:

• initial ownership;
• founder vesting where appropriate;
• transfer restrictions;
• rights of first refusal;
• good-leaver and bad-leaver scenarios;
• share buyback mechanisms;
• valuation mechanisms;
• tag-along rights;
• drag-along rights;
• treatment of inactive shareholders;
• admission of investors;
• employee equity plans;
• founder departure;
• death or permanent incapacity.

Initial Ownership Intent

The initial intention is for the product and technology founder to retain majority ownership while the operational founder holds a meaningful minority interest.

Exact percentages are confidential and remain to be agreed between the founders.

All equity matters must be reviewed and formalised by qualified legal professionals in the applicable jurisdiction.

The Vinova Lab Blueprint — Version 0.1 — Confidential Working Draft

During Vinova Lab's growth phase, financial resources should primarily support long-term company value.

Priority Uses of Capital

• engine development and research;
• product development;
• infrastructure;
• security;
• legal and regulatory compliance;
• recruitment;
• specialist contractors;
• marketing;
• sales development;
• market expansion;
• protection of intellectual property;
• financial reserves.

Dividend distribution should remain secondary while the company is still building the engine, products, recurring revenue, and market position.

Consulting Revenue

Revenue from tailor-made projects should not automatically be treated as distributable profit.

A significant portion should be reinvested into the engine and the company's product portfolio.

Consulting engagements that deepen the engine's domain intelligence — by exposing it to new document types, classification challenges, or relationship patterns — should be prioritised for reinvestment, as they generate strategic value beyond their immediate financial return.

Financial Discipline

Vinova Lab should maintain:

• reliable accounting;
• transparent reporting;
• approved budgets;
• documented expenses;
• cash-flow monitoring;
• clear approval thresholds;
• appropriate financial reserves;
• separation between company and personal expenses.

Transactions with founders, shareholders, their companies, or related parties must be transparent, documented, and conducted under appropriate commercial terms.

The Vinova Lab Blueprint — Version 0.1 — Confidential Working Draft

Vinova Lab builds technology that operates on documents — some of the most sensitive artefacts an organisation or individual can possess. Contracts, financial records, correspondence, and compliance documents carry obligations, relationships, and confidential information.

The principles below govern how the engine and every product built on it should be designed, operated, and evaluated.

Human-Centred Design

The engine and the products built on it should support people and organisations — not obscure responsibility or replace necessary human judgement.

Automation should reduce complexity and cognitive load. It should not remove the human from decisions that carry meaningful consequences.

Accountability

Responsibility for significant business decisions cannot be delegated to an automated system.

Where the engine produces outputs that inform a decision — a classification, an extraction, a relationship mapping — the person or organisation acting on that output remains responsible for the outcome.

Transparency

Users should understand what the engine has done and, where relevant, the confidence and limitations of its outputs.

Extractions, classifications, and relationship inferences should be presented in ways that allow users to verify, correct, or override them.

Privacy by Design

Products should minimise unnecessary data collection.

Documents always remain at their source. No original document is retained by Vinova Lab beyond what is strictly required for processing, and copies are deleted immediately after processing is complete.

Personal data and sensitive information are never used for training or improvement purposes. Only anonymised structural and semantic patterns — fully stripped of identifiable content — may feed the engine's learning pipeline.

Training Data Integrity

The signal used to improve the engine must be clean, anonymised, and derived — not a copy of any original document.

No personal data, no sensitive business information, and no customer-identifiable content may be retained or used as training material.

The anonymisation and derivation process must be verifiable, documented, and consistent with customer agreements and applicable data protection law.

Security

The engine, data pipelines, integrations, and all product components must be designed with appropriate security controls from the first day of development.

Security is not a feature added after the fact. It is a constraint that shapes architecture, access design, and operational practice.

Reliability

Products must communicate uncertainty clearly and avoid presenting outputs as facts when the engine's confidence does not support that level of certainty.

A document that is probably a utility bill should be presented as such — not asserted as one without qualification.

Human in the Loop

Human review should be available or required when the risk, uncertainty, or potential impact of an automated output justifies it.

The appropriate level of human involvement depends on the domain, the decision, and the consequences of error.

Continuous Evaluation

Engine and product quality must be monitored over time using suitable tests, feedback mechanisms, and evaluation criteria.

Accuracy, reliability, and behaviour must be assessed continuously — not only at the point of release.

Responsible Data Use

Data must be used lawfully, ethically, and consistently with customer expectations and contractual obligations.

What the engine learns from one customer's documents must never benefit a competitor or be used in ways the customer has not agreed to.

The Vinova Lab Blueprint — Version 0.1 — Confidential Working Draft

Vinova Lab values:

• curiosity;
• ownership;
• excellence;
• humility;
• pragmatism;
• continuous learning;
• trust;
• direct communication;
• respect;
• accountability.

Curiosity

We explore new ideas, new domains, and new document challenges without confusing novelty with value.

Ownership

People are expected to take responsibility for outcomes, not merely complete assigned tasks.

Excellence

We aim for high standards in products, operations, customer relationships, and internal work.

Humility

We recognise uncertainty, admit mistakes, and change direction when evidence shows a better path.

Pragmatism

We value solutions that work in the real world. A product that handles real documents well is worth more than one that works perfectly on curated examples.

Continuous Learning

The domains we operate in, the document types we encounter, and the problems our customers face will evolve continuously. Learning is part of every role.

Open Communication

Disagreement is acceptable and often useful.

Hidden concerns, unclear responsibilities, and unresolved assumptions are not.

Trust and Accountability

Trust enables autonomy.

Accountability protects trust.

The Vinova Lab Blueprint — Version 0.1 — Confidential Working Draft

Over time, Vinova Lab aims to become:

• an internationally recognised document intelligence company;
• the owner of a document intelligence engine that sets the standard for domain-specific document understanding;
• the creator of multiple successful vertical products serving distinct industries and audiences;
• a trusted innovation partner for selected organisations operating in document-intensive domains;
• a company whose value derives primarily from its engine, its accumulated domain intelligence, and recurring product revenue;
• an employer capable of attracting exceptional people;
• a platform for builders who want to create document-intelligent applications without rebuilding the underlying intelligence layer;
• an organisation capable of serving customers across Europe, the Middle East, and other international markets.

Measuring Success

Long-term success should not be measured only through revenue or valuation.

It should also include:

• engine capability and domain coverage;
• quality and accuracy of document intelligence across supported domains;
• product quality;
• customer outcomes;
• recurring adoption;
• employee development;
• ethical conduct;
• operational resilience;
• reputation;
• durable intellectual property.

The Vinova Lab Blueprint — Version 0.1 — Confidential Working Draft

The founders commit to acting in the long-term interests of Vinova Lab.

They recognise that they bring different experiences, responsibilities, and forms of value to the company.

They commit to:

• communicate openly;
• raise concerns early;
• document important decisions;
• separate personal interests from company interests;
• protect company assets;
• respect agreed areas of responsibility;
• collaborate on strategic decisions;
• manage disagreements professionally;
• preserve customer trust;
• protect confidential information;
• support the mission of Vinova Lab.

On Disagreement

Disagreement should not be treated as disloyalty.

Constructive challenge is part of responsible company building.

On Trust and Documentation

The founders recognise that trust alone is not a substitute for clear agreements.

Roles, rights, responsibilities, decision processes, and exit mechanisms should be documented while relationships are positive and interests are aligned.

The success and continuity of Vinova Lab should take precedence over individual pride, informal assumptions, or short-term personal advantage.

The Vinova Lab Blueprint — Version 0.1 — Confidential Working Draft

The Vinova Lab Blueprint is a strategic and organisational working document. It does not constitute legal, tax, accounting, or investment advice. Corporate governance, shareholder rights, intellectual property provisions, and other legally binding matters must be reviewed and formalised by qualified professionals in the jurisdiction where Vinova Lab is incorporated.

Status

What This Document Is

The Blueprint is:

• a strategic and organisational framework;
• a guide for founders, future employees, and partners;
• a foundation for governance discussions and decision-making;
• a description of the company's intended direction, values, and principles;
• a living document intended to evolve with the company.

What This Document Is Not

The Blueprint is not:

• a shareholders' agreement or binding corporate document;
• legal advice;
• tax advice;
• accounting advice;
• investment advice;
• an offer of securities;
• a final statement of ownership, rights, or obligations.

Required Actions

The following matters must be reviewed and formalised by qualified professionals:

• company incorporation and corporate structure;
• shareholders' agreement;
• intellectual property assignment agreements;
• open-source licence compliance for all components used in the engine and products;
• training data usage policies and customer data agreements;
• employment and contractor agreements;
• customer contracts, including provisions related to document processing, anonymised signal extraction, and engine improvement;
• any provisions related to equity, ownership, or financial obligations.

The Vinova Lab Blueprint — Version 0.1 — Confidential Working Draft