Infinote Intelligence technical guide

The page remains the reference

Infinote Intelligence™ connects captured notes with recognition, search, summaries and useful next steps. You can write in your notebook without using these features. Capture a page when you want a digital record, then choose how to recognise, organise or work with its content.

The system is designed around the original page. Recognised text and generated results are additional layers, rather than replacements for what you wrote. This guide explains those layers and their relationships. Available controls can differ by device, installed components, account and app version; use the options shown in your app.

What a captured note contains

A note can contain the captured page, a processed image, recognised text and organisation information. Depending on the workflows you use, it can also have summaries, extracted meetings, reminders, search information or export records. These parts serve different purposes.

The image records the visual page. Recognition makes text available for searching and other supported uses. A generated summary or action interprets that text. If two layers disagree, return to the original page and check the relevant wording, layout or drawing. A confident-looking answer does not establish that the source contained the same detail.

Find the right part of the app

The main navigation is Home, Spaces, Capture, Memory and You. Home gives you recent and starred notes. Spaces groups related material. Capture starts the digital record. Memory brings together summaries, Ask Notes, meetings and reminders. You contains preferences, processing choices, downloads, connections and support.

Start in the area that matches your task. For a missing page, check the library before changing intelligence settings. For recognised wording, inspect the image and text. For a failed external upload, check the destination separately. This keeps a problem in one part of the workflow from being mistaken for a failure of the whole note.

Capture before interpretation

Capture first performs document processing. Depending on the page and platform, this may include detecting edges, correcting perspective or orientation, cropping surroundings and improving readability. These operations prepare the image; they do not require a generative model to invent a transcription.

1. Place the page flat and use even light.
2. Keep the complete page in view and hold the camera steady.
3. Review the result for clipped text, blur, glare and missing edges.
4. Recapture if the image is unreadable before starting recognition or interpretation.

Core capture and local saving can operate without cloud intelligence. Choosing cloud processing later is a separate decision.

Original and Text

Original is the visual captured page. Text is its recognised, machine-readable content. Infinote can retain both, so you can move between what you wrote and what recognition produced. Original is useful for drawings, layout, uncertain handwriting and checking a detail in context.

Text can support searching, copying and intelligence workflows. Editing depends on the available app controls. Before using a name, amount, date or instruction, compare it with Original. Correct recognised text where editing is available, or recapture a clearer image. Improving a summary does not by itself repair an incorrect transcription.

Choose recognition for the page

OCR means Optical Character Recognition: converting captured writing into machine-readable text. In You, Text Recognition distinguishes On-Device Recognition from Cloud Recognition. The current settings describe the on-device option as free and offline; cloud recognition offers enhanced processing for complex pages and languages and uses credits.

Recognition availability can depend on platform, language, document type and settings. Check your current recognition allowance in the app. Capture preferences covers naming, save location, quality and format. Choose a processing option deliberately, then inspect the result before using it elsewhere.

Check recognition against the source

Handwriting style, contrast, abbreviations, lighting, camera angle and language can affect recognition. Tables, unusual layouts or drawings crossing text can make a page harder to represent accurately as plain text. Clear capture helps, but it does not guarantee a correct result.

The normal text workflow recognises the page before intelligence interprets the recognised information. Additional visual understanding may be available for structural content that ordinary OCR cannot adequately represent. Do not assume that every diagram or relationship is understood. Keep the original image and check important details, especially where a result will become a message, meeting or reminder.

Organise notes with context

A Space groups related notes around a project, subject, client or part of life. Give it a name that will still make sense when you return later. The current Spaces screen includes pinned Spaces, Create a space, Sort A–Z and management controls.

Spaces also provide a useful context for supported retrieval and intelligence workflows. Their role is broader than an exported folder: they help describe which notes belong together inside Infinote. Moving or organising a note in a Space should not be assumed to reorganise a copy previously sent to an external destination. Those are separate records.

Search by words or meaning

Keyword search looks for literal recognised words or phrases. Use it when you remember a name or term from the page. If a phrase is absent, inspect Text: recognition may have produced different wording, or processing may not yet be complete.

Semantic Search looks for related meaning. A note about revised supplier pricing might be relevant to a query about a cost discussion without containing that exact phrase. Local semantic features require their setup and indexing components. The current Semantic Search screen shows a model download. Complete the available setup before expecting that local option to work; relevance is not a guarantee that every useful note will be retrieved.

How a question finds material

The documented Ask Notes design starts by identifying relevant notes and passages. It then provides selected context to the chosen intelligence option to produce an answer. This avoids treating every question as a request to interpret the entire library at once.

Semantic retrieval can compare compact representations of meaning, often called embeddings. The useful customer distinction is that finding material and generating an answer are separate stages. An answer can be incomplete if relevant passages were not retrieved, even when the model works normally. Check the question, scope and source text before assuming that a missing answer means the information was never written.

Choose the scope of Ask Notes

Ask Notes is designed for questions about your notes. A narrow question can be easier to check: ask what was decided, which follow-ups were recorded or how selected notes differ. It is not intended to fill a gap with unrelated internet information.

The documented architecture supports scopes such as the whole library, a Space or selected notes. Use the scope controls available in your version; this does not establish that every version exposes each control. If an answer seems unrelated, narrow the scope and identify the project or meeting clearly. Review the cited or linked source material where provided, and check important interpretations against the original page.

Summaries and source relationships

Memory is the workspace for reusable outputs from your notes. Create summary can begin with a new scan, an existing note or pasted text. A summary may help collect the main ideas, decisions and follow-ups, but it remains an interpretation of the chosen material.

Provenance means knowing where a result came from. Infinote is designed to preserve relationships between outputs and source notes where appropriate. When a source link is available, use it to verify the result. Regeneration depends on the available processing mode. It can produce another interpretation; it does not make an unverified detail authoritative or change what was written.

Review before creating a meeting

Meeting extraction can turn recognised note content into a draft with fields such as title, date, time, people, location or agenda. Extracting those details and creating an external event are separate actions. The documented workflow is designed around your review.

1. Open the meeting draft and return to its source where available.
2. Check the title, date, time and any participants or location.
3. Edit missing or incorrect details. A suggested duration may be a default, rather than a duration found in the note.
4. Choose an available calendar or meeting service and confirm the final action.

Do not treat a draft as evidence that an invitation was sent or an event created.

Meeting states and connections

The documented meeting library can distinguish Upcoming, Past and To Review. These states help separate extracted information from confirmed plans. Use the states shown in your app, and inspect an item requiring review before relying on it.

The current Calendars & meetings screen shows Apple Calendar, Google Calendar and Microsoft Teams. The supplied technical architecture also describes possible Outlook and Google Meet workflows; availability can depend on platform, account, permissions and service configuration. Follow the actual connection options in your version. Connecting a provider does not mean every detected date is automatically scheduled, or that all supported accounts allow the same actions.

Turn a task into a reminder

Reminders can structure tasks, dates and follow-ups found in recognised text. A draft may include a title, date, time, context and a relationship to the source note. Review ambiguous expressions such as tomorrow or next week rather than assuming they resolve to the date you intended.

The documented library can include Upcoming, Today, To Review and Completed views. An item in To Review needs checking before it is treated as final. Confirm the task and timing before saving. Where the originating note remains linked, return to it when a short reminder title no longer provides enough context.

Check notification delivery separately

A saved reminder and a delivered notification are different things. Alerts depend on the reminder configuration, app permission, operating-system settings and device background or battery policies. Saving an item inside Infinote does not bypass those controls.

1. Check the reminder's date and time.
2. Review Infinote's notification permission and system notification settings.
3. Check Focus or Do Not Disturb and relevant battery restrictions.
4. If an alert still fails, record the device, app version and expected timing for support.

Keep the source task available while troubleshooting rather than deleting and recreating unrelated library content.

Choose where intelligence runs

Infinote Intelligence™ is the platform; Aurelius is its private on-device intelligence experience for supported workflows. The current settings distinguish Private Intelligence, Built-in Intelligence and Cloud Intelligence. Default Intelligence sets a general preference, while Per-feature Intelligence allows different choices where supported.

A workflow can combine document processing, recognition, retrieval and intelligence. One local setting does not establish that every step or connected service stays offline.

Install and maintain Aurelius

Local intelligence needs model files on the device. Supported Aurelius operations can work offline after the required model is installed. Downloading and updating those files still requires connectivity. Use the current storage requirement shown in the app; package size can change with model version and device capability.

The documented installation lifecycle can include waiting for Wi-Fi, downloading, paused, verifying, installing, installed, update available, failed or unsupported states. Not every version must show identical labels. Check Intelligence and Manage Downloads for the actual status. An incomplete download or failed verification is different from a model being installed but unavailable for a particular feature.

Device capability and local models

On-device generative intelligence uses the phone's storage, memory and processing resources. Devices may therefore support different model configurations and performance. If Aurelius is unavailable, check the device requirements, free storage, installation status and any update shown in the app.

Follow the model configurations offered on your device. Other supported workflows, such as capture, local notes, recognition, search and organisation, can remain useful when a particular generative model is unavailable. Availability of one model is not the same as availability of the whole app.

Plan an offline workflow

Offline capability depends on device support and installed components. Complete required downloads before travelling, and test the workflow you intend to use with the saved notes you need.

Reviewing a draft offline does not establish that an external action completed.

Understand the privacy choices

For a request processed entirely through supported on-device intelligence, the generative operation occurs on the device. Cloud recognition, cloud intelligence and connected destinations involve remote services. Check both the feature's processing selection and any external connection.

The intended privacy model keeps private and cloud processing separate: choosing private intelligence should not silently authorise remote generative processing of the same request. If a local feature is unavailable, review the displayed processing information before selecting another mode.

Do not read local-first as a promise that all information always stays on the device. Exports, calendars, authentication and other online actions have their own data flows.

Destinations send a copy

A Destination is an external location for a copy of your note. The current connection screen shows Google Drive, Dropbox, Microsoft OneDrive, OneNote and Box. Other destination types described in the architecture, such as email, depend on the workflow and version.

Save Locally keeps the note in Infinote. An export keeps that note and sends a copy elsewhere. Destinations are an export and routing system, rather than permanent two-way document synchronisation. Editing or reorganising your Infinote note does not necessarily update a previously exported file. Check the external copy independently when the exact version matters.

Choose and verify an export

Export choices can include PDF and JPEG, depending on the destination and workflow. Multi-page captures can be combined into one document where supported. Quality settings and inclusion of recognised text can also vary; use the options displayed in your version.

1. Choose the note or document and review all pages.
2. Select the available format, destination and account.
3. Send the copy, then open the resulting file at the destination.
4. Check readability, page order and completeness before relying on it.

Share uses the device's sharing options; Send uses a configured destination. A successful local save is not proof that either external route finished.

Failed uploads, disconnection and backup

If an export fails, check connectivity, authorisation, account, selected folder access and available destination storage. The source note is intended to remain available locally; verify that it is saved before retrying or choosing another route. Do not delete app data to solve an external upload problem.

Disconnecting a destination stops use of that connection for future exports. Previously sent files normally remain under the external provider's control, and must be managed there. They are separate from the Infinote library, including when an account is deleted.

An exported PDF or JPEG is not a complete library backup. It may not preserve source relationships, Spaces, reminders or other information needed to restore the working library.

Permissions for the action

Permissions belong to the action you choose. Camera access supports capture; Photos or Files may be needed for imports and exports; notifications support alerts; calendar permission or provider authorisation supports connected events. Review the external provider's requested access before connecting. Permission experiences differ between iOS and Android.

Focus and priorities

For work after reviewing a note, the Eisenhower Matrix separates urgency from importance. Pomodoro structures focused intervals, Stopwatch times an open-ended session, and Countdown keeps an upcoming date visible. These tools support your judgement; they do not establish that a task was completed, a reminder delivered or a meeting scheduled.

Troubleshoot with the source in view

For incorrect recognition, check Original, lighting and framing, then recapture or correct Text where editing is available. For a missing search result, check the recognised wording, processing and indexing, then try the appropriate search method. For unavailable Aurelius, inspect download status, requirements and storage. For a destination failure, investigate the external connection separately.

If a note appears missing, check Home, Starred, its Space and the expected account before clearing data or reinstalling. Contact support with the device, operating system, app version, failed step and a redacted error. Remove private writing and account details from screenshots.

Return to the original page whenever accuracy matters. The notebook remains a place to write; the digital layers help you use what you have written.

Terms used in this guide

OCR

Recognition that produces machine-readable text from a captured page.

Semantic retrieval

Finding related information by meaning.

Provenance

The relationship between a result and its source.

Derived output

A summary, answer or action created from source material.

Local-first

A design centred on the device library, with separate online extensions.

Destination

An external service receiving a copy.