Search

Find public work and evidence.

    Integritellent

    A workspace you can make sense of.

    Development project on HeartBoat

    Integritellent is a workspace-first browser desktop. Panes, folders and links form a graph, and actions use explicit commands with an audit trail. The repository describes a local-data model and the boundaries between the kernel and its shells.

    Source checked: Sep 30, 2026 · Inspect the source

    How the workspace is organized

    An explicit world model

    Panes, folders and reference links use one graph model. The architecture documents explain which data belongs to the kernel and which behavior belongs to a shell.

    Read more

    Actions you can trace

    Commands, queries and events share a typed interface. The contract documents describe the request, policy check and recorded outcome.

    Read more

    Local data, bounded access

    The workspace uses local storage. Ownership, storage quotas and capability policies are described in the repository, so they can be checked before integration.

    Read more
    A genuine source workflow

    Build from source

    Start with the documented core/headless build. The CEF desktop shell is a separate optional lane with additional prerequisites. Keep the source revision, commands and test output when reporting a build issue.

    Inspect the actual workflow
    Documented core/headless build · not executed by this website
    cmake --preset ninja-release
    cmake --build --preset ninja-build-release
    ctest --preset ninja-test-release
    ctest --preset ninja-selfcheck-release
    Prerequisites and current instructions

    Before you start

    Read the sources that match the work you want to do, then ask a focused question or choose a task on HeartBoat.

    Read the architecture

    Start with the world-kernel and shell split. New behavior should follow the source contracts rather than introduce a competing model in a shell.

    Read more

    Check the build prerequisites

    Use the README instructions for the source revision you are testing. The default core/headless lane and optional CEF desktop lane have different prerequisites.

    Read more

    Report a reproducible issue

    Include the source revision, environment, command and output. Separate a build failure, a test failure and a missing release artifact so others can investigate.

    Read more

    Find a way to contribute

    Start with the project documentation and existing discussions. Choose a small task, report a reproducible problem or propose work with a clear scope. Shared tasks and reviews are handled on HeartBoat.

    Get involved
    A HeartBoat projectAn open collaboration platform.