One verified record behind every project
Lumiare captures what a project knows, checks it against your rulebook, has the people who own it verify it, and writes the documents from the result.

OVERVIEW
What Lumiare is
Lumiare is the System of Context for regulated enterprises, a Contextual Intelligence Platform built by maiven s.r.o. It turns project requests, documents, meetings, transcripts, spreadsheets and notes into a verified record of each project: what was agreed, why, by whom, where it came from and which regulations and policies it was checked against.
Systems of record hold the what, who and when. A portfolio tool knows which projects exist and what they cost. A ticketing tool knows which tasks are open. Neither holds the reasoning behind a project or checks it against the rules that apply. Lumiare is where that lives, with an owner, a score, a policy check and a trail on every item.
THE STANDARD
Verified means four things
01
Complete
The test
Does the information satisfy the description of what is needed?
Where you see it
A completeness score on every item and a plain list of what would take it to 100 percent
02
Consistent
The test
Do any two sources disagree, and was every disagreement resolved by the team?
Where you see it
Contradictions raised on every upload, resolved by the people who own the items
03
Owned
The test
Is a named person accountable?
Where you see it
An owner and reviewers on every item, row, memo, task and document
04
Traceable
The test
Can every fact be followed back to its source, history and discussion?
Where you see it
Version history, source labels, related objects and an activity feed on every item
HOW IT WORKS
How Lumiare works
01
Intake
A project request, its business case and the documents, recordings and notes behind it go into one project.

02
Check
Lumiare scores each item against what it must contain, tests it against everything already known and checks it against your regulations and policies.

03
Resolve and approve
Gaps become questions to the people responsible. Contradictions go to their owners. The request goes through approval, and each decision is recorded.
04
Govern
The portfolio dashboard shows health and approval status for each project. The charter, scope or audit report is written from what was verified.

platform capabilities
Capabilities, grouped by what they make true
Everything below is in the product today.
Complete
Project Requests created from a template or with the assistant, and evaluated against what a request of that type must contain
One item per thing the project must know, each with a description of what good looks like, a completeness score and a list of what is missing
Requests for information: one drafted question per gap, sent to the person responsible
Project templates that define items, Sheets and recommended documents
A personal queue on each person's homepage showing what they still owe
✦
⌃
80%
✦
To reach 100%
Consistent
Knowledge Hub verification: each project compared with your regulations and policies, findings sorted into contradictions, conflicts and gaps with a severity and a proposed resolution
Contradictions between sources raised on every upload, shown side by side with their sources
Upload of PDF, DOCX, XLSX, TXT and MD files and MP3, MP4 and WEBM recordings, transcribed on upload; typed notes and voice memos
Knowledge Graph of entities and claims, including risks, constraints, assumptions and decisions
Add files, transcripts and notes about the project
Files
Supported formats: PDF, DOCX, XLSX, TXT, MD, MP3, MP4, WEBM
Write a note or drag and drop a file
Upload files
Smart upload
Legacy
A
B
Or
Record a voice memo ●
Cancel
Submit
Owned
An owner on every item, row, memo, task and document; reviewers separate from the owner
Verified, unverified and rejected states recorded against a version
Approval workflow for Project Requests, with status shown across the portfolio
Tasks, threaded comments, notifications and live co-editing
One-click owner assignment and tagging
‹
Core information
› Technology stack
⋮ ✕
Technology stack
V4
Sep 19, 2026, 04:02 AM by
P
Project lead
Owner
H
Head of IT
Status
! Unverified
Context
Manual update
Updated · Sep 19, 2026
Comments
H
Head of IT
now
I'm checking whether we've covered all of this.
👍 1
⌃ Hide reply
S
Security reviewer
now
Done.
Traceable
A policy says recovery takes four hours. A runbook uploaded a week later says twenty-four. Lumiare raises the contradiction when the runbook is processed, shows both statements with their sources and hands it to the people who own the item. They decide which holds.
! Contradictions
4
H
H
OUTPUT
Documents Lumiare writes
Project request
Project charter
Scope description
Requirements specification
RFI, RFQ and RFP
Vendor comparison
Audit report
Project summary
Each document starts from your own template or the structure of a document you already use. Every section is linked to verified context, then opened for the team to edit together and export. Lumiare also builds the registers behind them, such as requirements, asset and control registers, as Sheets with an owner on every row.
INTEGRATIONS
Works with the tools you run
Lumiare works with Jira, Google Workspace and Microsoft Teams. ServiceNow is next. Notifications reach people where they work, and tasks can move into Jira.
FAQ
Questions people ask
Plain answers, including where the answer is that you don't need Lumiare.
Is Lumiare a project management tool?
No. Project management tools hold tasks, status and dates. Lumiare holds what was agreed and why, checked and traceable. It has tasks so context turns into accountable work, and tasks can move into Jira.
Is Lumiare a document management system?
What happens to my source files after upload?

Make your next project decision with the full picture
Bring your project information together, understand what is missing and give your team the context to make better-informed decisions.

