Skip to content

Releases

Munimentum v14.7.0

Choose a tag to compare

@github-actions github-actions released this 24 Oct 16:01

New in 14.7.0

  • The organization as CSV: CSV… in Organization downloads the people
    of a version – the whole tenant, the part below a person or the list shown
    – or the changes over a span of versions, ready for Excel. Every file names
    each person's company; mail addresses come along only when you tick them.

Upgrading

Nothing happens once after this update.

Skipping releases is fine: whatever an older release does once after an
update, the first run does too. What changes for scripts against the
HTTP interface is in the notes of the release that changed it – see
all releases.
Coming from far back? A quick look through the notes you skipped shows
whether any of them asks something of you.

Which file?

File For
Munimentum-macos-arm64.dmg Mac with Apple Silicon (M1 or newer)
Munimentum-windows-x64.zip Windows 10/11 (64-bit)
Munimentum-linux-x64.tar.gz Linux (64-bit, glibc 2.35+)
Munimentum-skill-research.zip, …-case.zip, …-evidence.zip the three skills for MCP clients, to install by hand – the same files Download skills gives

Getting started

macOS — double-click the DMG, drag Munimentum.app onto the
Applications folder shown next to it, close (eject) the window, and start the
app from Applications.

Windows — unpack the ZIP (right-click → Extract All, not just looking
inside), then double-click Munimentum.exe in the extracted folder.

Linux — tar -xzf Munimentum-linux-x64.tar.gz, then run
./Munimentum/Munimentum.

The interface then opens by itself in your default browser. Everything else —
fetching a token, exporting, searching — is explained there.

“Windows protected your PC”

macOS is signed and notarized by Apple — it opens on a double-click, with
no warning and nothing to click past.

Windows is not code-signed. A certificate costs considerably more there, and
SmartScreen additionally wants to see a download count before it goes quiet. So
on first launch you get the blue window: click “More info”, then “Run
anyway”
. It happens once.

If you would rather not, run it from source instead (python3 app.py, see the
README) — the function and the result are identical.

Checksums

SHA256SUMS.txt is attached. Verify with shasum -a 256 -c SHA256SUMS.txt
(macOS/Linux) or Get-FileHash file.zip (PowerShell).

What comes next is in ROADMAP.md.

Munimentum v14.6.0

Choose a tag to compare

@github-actions github-actions released this 20 Oct 13:36

New in 14.6.0

  • The organization's changes as a chart: a closed Overview fold at the
    top of Organization draws the people and the changes per version.
  • Its seniority by title: a second fold shows the pyramid of the titles,
    read by a role model you can edit, and the organization's health in
    figures – spans of control, people per leader, layers.
  • Its health for MCP clients: org_health hands the same figures,
    numbers only, and four prepared questions ask how healthy the organization
    is, where spans run wide, which parts are top-heavy and what changed since
    a day.

Upgrading

The first organization run after this update counts the overview's numbers
once for the versions already in the archive.

Skipping releases is fine: whatever an older release does once after an
update, the first run does too. What changes for scripts against the
HTTP interface is in the notes of the release that changed it – see
all releases.
Coming from far back? A quick look through the notes you skipped shows
whether any of them asks something of you.

Which file?

File For
Munimentum-macos-arm64.dmg Mac with Apple Silicon (M1 or newer)
Munimentum-windows-x64.zip Windows 10/11 (64-bit)
Munimentum-linux-x64.tar.gz Linux (64-bit, glibc 2.35+)
Munimentum-skill-research.zip, …-case.zip, …-evidence.zip the three skills for MCP clients, to install by hand – the same files Download skills gives

Getting started

macOS — double-click the DMG, drag Munimentum.app onto the
Applications folder shown next to it, close (eject) the window, and start the
app from Applications.

Windows — unpack the ZIP (right-click → Extract All, not just looking
inside), then double-click Munimentum.exe in the extracted folder.

Linux — tar -xzf Munimentum-linux-x64.tar.gz, then run
./Munimentum/Munimentum.

The interface then opens by itself in your default browser. Everything else —
fetching a token, exporting, searching — is explained there.

“Windows protected your PC”

macOS is signed and notarized by Apple — it opens on a double-click, with
no warning and nothing to click past.

Windows is not code-signed. A certificate costs considerably more there, and
SmartScreen additionally wants to see a download count before it goes quiet. So
on first launch you get the blue window: click “More info”, then “Run
anyway”
. It happens once.

If you would rather not, run it from source instead (python3 app.py, see the
README) — the function and the result are identical.

Checksums

SHA256SUMS.txt is attached. Verify with shasum -a 256 -c SHA256SUMS.txt
(macOS/Linux) or Get-FileHash file.zip (PowerShell).

What comes next is in ROADMAP.md.

Munimentum v14.5.1

Choose a tag to compare

@github-actions github-actions released this 12 Oct 20:13

New in 14.5.1

  • A SharePoint address that matches nothing now says what the site has:
    after the skipped line the log names the site’s document libraries by
    URL segment, with the display name where it differs – or says that
    Graph lists no library there at all. The three spellings of one
    library in issue #3 would have been settled by that one line.
  • The problem report names nothing of yours: your organisation’s mail
    domains, your own name, paths and the rules lists appear only as counts
    or as “set”, like the folder rules did before.
  • An empty archive no longer fails the index: with nothing exported
    yet, the index step ends with a note instead of an error.

Upgrading

Nothing happens once after this update.

Skipping releases is fine: whatever an older release does once after an
update, the first run does too. What changes for scripts against the
HTTP interface is in the notes of the release that changed it – see
all releases.
Coming from far back? A quick look through the notes you skipped shows
whether any of them asks something of you.

Which file?

File For
Munimentum-macos-arm64.dmg Mac with Apple Silicon (M1 or newer)
Munimentum-windows-x64.zip Windows 10/11 (64-bit)
Munimentum-linux-x64.tar.gz Linux (64-bit, glibc 2.35+)
Munimentum-skill-research.zip, …-case.zip, …-evidence.zip the three skills for MCP clients, to install by hand – the same files Download skills gives

Getting started

macOS — double-click the DMG, drag Munimentum.app onto the
Applications folder shown next to it, close (eject) the window, and start the
app from Applications.

Windows — unpack the ZIP (right-click → Extract All, not just looking
inside), then double-click Munimentum.exe in the extracted folder.

Linux — tar -xzf Munimentum-linux-x64.tar.gz, then run
./Munimentum/Munimentum.

The interface then opens by itself in your default browser. Everything else —
fetching a token, exporting, searching — is explained there.

“Windows protected your PC”

macOS is signed and notarized by Apple — it opens on a double-click, with
no warning and nothing to click past.

Windows is not code-signed. A certificate costs considerably more there, and
SmartScreen additionally wants to see a download count before it goes quiet. So
on first launch you get the blue window: click “More info”, then “Run
anyway”
. It happens once.

If you would rather not, run it from source instead (python3 app.py, see the
README) — the function and the result are identical.

Checksums

SHA256SUMS.txt is attached. Verify with shasum -a 256 -c SHA256SUMS.txt
(macOS/Linux) or Get-FileHash file.zip (PowerShell).

What comes next is in ROADMAP.md.

Munimentum v14.5.0

Choose a tag to compare

@github-actions github-actions released this 08 Oct 12:39

New in 14.5.0

  • MCP clients, not Claude: the settings room is MCP clients, the
    switch MCP clients may change cases, the tour chapter Connect an MCP
    client
    ; Claude stays where a format is its own – the two snippets, the
    skills’ install paths. Any MCP client was always meant; the words now
    say so.
  • Skills to install by hand: Download skills under Settings › MCP
    clients
    gives the three skills as ZIP files, one per skill, for Claude
    Code’s ~/.claude/skills/ or an upload under Customize › Skills; every
    release carries the same three files. A copy installed by hand does not
    change with the app: each guide names the version it belongs to, and the
    new MCP tool get_version lets the client notice an outdated one and
    read the current guide instead.
  • A message shown on its own carries its link: the guides, the prompts
    and the server’s instructions now say that an item quoted, summarised
    or described as one message was read with get_document and carries
    its link; a list of hits carries labels only.
  • A newer release is announced at start: with “Look for updates at
    startup” on, a window shows the release’s notes with Download and
    Dismiss; Disable update check in it switches the check off. Dismiss
    keeps that version quiet, the next release asks again.
  • The link finds a running app sooner: a busy app no longer counts as
    closed, and a missed one is found on the next call rather than half a
    minute later.

Upgrading

Nothing happens once after this update. A client reads the changed guides
after it reconnects to the MCP server – Claude Desktop after a restart; a
conversation holding an older guide token is handed the guide once more.
Skills you installed by hand are from an earlier version now: download
them again.

Skipping releases is fine: whatever an older release does once after an
update, the first run does too. What changes for scripts against the
HTTP interface is in the notes of the release that changed it – see
all releases.
Coming from far back? A quick look through the notes you skipped shows
whether any of them asks something of you.

Which file?

File For
Munimentum-macos-arm64.dmg Mac with Apple Silicon (M1 or newer)
Munimentum-windows-x64.zip Windows 10/11 (64-bit)
Munimentum-linux-x64.tar.gz Linux (64-bit, glibc 2.35+)
Munimentum-skill-research.zip, …-case.zip, …-evidence.zip the three skills for MCP clients, to install by hand – the same files Download skills gives

Getting started

macOS — double-click the DMG, drag Munimentum.app onto the
Applications folder shown next to it, close (eject) the window, and start the
app from Applications.

Windows — unpack the ZIP (right-click → Extract All, not just looking
inside), then double-click Munimentum.exe in the extracted folder.

Linux — tar -xzf Munimentum-linux-x64.tar.gz, then run
./Munimentum/Munimentum.

The interface then opens by itself in your default browser. Everything else —
fetching a token, exporting, searching — is explained there.

“Windows protected your PC”

macOS is signed and notarized by Apple — it opens on a double-click, with
no warning and nothing to click past.

Windows is not code-signed. A certificate costs considerably more there, and
SmartScreen additionally wants to see a download count before it goes quiet. So
on first launch you get the blue window: click “More info”, then “Run
anyway”
. It happens once.

If you would rather not, run it from source instead (python3 app.py, see the
README) — the function and the result are identical.

Checksums

SHA256SUMS.txt is attached. Verify with shasum -a 256 -c SHA256SUMS.txt
(macOS/Linux) or Get-FileHash file.zip (PowerShell).

What comes next is in ROADMAP.md.

Munimentum v14.4.1

Choose a tag to compare

@github-actions github-actions released this 07 Oct 21:19

New in 14.4.1

  • A client’s attach menu says what each entry is: the prompts read
    “Ask: …”, the case pages “Cases: All” and “Case: ”, the skills
    “Skill: Case”, “Skill: Evidence”, “Skill: Research” – cases before skills.

Upgrading

Nothing happens once after this update. A client shows the new names after
it reconnects to the MCP server – Claude Desktop after a restart.

Skipping releases is fine: whatever an older release does once after an
update, the first run does too. What changes for scripts against the
HTTP interface is in the notes of the release that changed it – see
all releases.
Coming from far back? A quick look through the notes you skipped shows
whether any of them asks something of you.

Which file?

File For
Munimentum-macos-arm64.dmg Mac with Apple Silicon (M1 or newer)
Munimentum-windows-x64.zip Windows 10/11 (64-bit)
Munimentum-linux-x64.tar.gz Linux (64-bit, glibc 2.35+)

Getting started

macOS — double-click the DMG, drag Munimentum.app onto the
Applications folder shown next to it, close (eject) the window, and start the
app from Applications.

Windows — unpack the ZIP (right-click → Extract All, not just looking
inside), then double-click Munimentum.exe in the extracted folder.

Linux — tar -xzf Munimentum-linux-x64.tar.gz, then run
./Munimentum/Munimentum.

The interface then opens by itself in your default browser. Everything else —
fetching a token, exporting, searching — is explained there.

“Windows protected your PC”

macOS is signed and notarized by Apple — it opens on a double-click, with
no warning and nothing to click past.

Windows is not code-signed. A certificate costs considerably more there, and
SmartScreen additionally wants to see a download count before it goes quiet. So
on first launch you get the blue window: click “More info”, then “Run
anyway”
. It happens once.

If you would rather not, run it from source instead (python3 app.py, see the
README) — the function and the result are identical.

Checksums

SHA256SUMS.txt is attached. Verify with shasum -a 256 -c SHA256SUMS.txt
(macOS/Linux) or Get-FileHash file.zip (PowerShell).

What comes next is in ROADMAP.md.

Munimentum v14.4.0

Choose a tag to compare

@github-actions github-actions released this 07 Oct 20:27

New in 14.4.0

  • Three skills for Claude – researching the archive, working a case,
    building evidence – carry the prompts’ know-how to every MCP client: as
    skills a host loads from the server, or through the new tool get_guide
    for one that sees only tools.
  • Searching, changing a case and verifying an item want the guide first:
    called without its token they answer with the guide instead of a result,
    once per conversation.

Upgrading

Nothing happens once after this update. A client that already talks to the
MCP server gets the guide on its first search, case write or verification
of a conversation and the token with it; nothing else changes for it.

Skipping releases is fine: whatever an older release does once after an
update, the first run does too. What changes for scripts against the
HTTP interface is in the notes of the release that changed it – see
all releases.
Coming from far back? A quick look through the notes you skipped shows
whether any of them asks something of you.

Which file?

File For
Munimentum-macos-arm64.dmg Mac with Apple Silicon (M1 or newer)
Munimentum-windows-x64.zip Windows 10/11 (64-bit)
Munimentum-linux-x64.tar.gz Linux (64-bit, glibc 2.35+)

Getting started

macOS — double-click the DMG, drag Munimentum.app onto the
Applications folder shown next to it, close (eject) the window, and start the
app from Applications.

Windows — unpack the ZIP (right-click → Extract All, not just looking
inside), then double-click Munimentum.exe in the extracted folder.

Linux — tar -xzf Munimentum-linux-x64.tar.gz, then run
./Munimentum/Munimentum.

The interface then opens by itself in your default browser. Everything else —
fetching a token, exporting, searching — is explained there.

“Windows protected your PC”

macOS is signed and notarized by Apple — it opens on a double-click, with
no warning and nothing to click past.

Windows is not code-signed. A certificate costs considerably more there, and
SmartScreen additionally wants to see a download count before it goes quiet. So
on first launch you get the blue window: click “More info”, then “Run
anyway”
. It happens once.

If you would rather not, run it from source instead (python3 app.py, see the
README) — the function and the result are identical.

Checksums

SHA256SUMS.txt is attached. Verify with shasum -a 256 -c SHA256SUMS.txt
(macOS/Linux) or Get-FileHash file.zip (PowerShell).

What comes next is in ROADMAP.md.

Munimentum v14.3.0

Choose a tag to compare

@github-actions github-actions released this 05 Oct 11:53

New in 14.3.0

  • A series of appointments is one file with its exceptions – every date
    it makes stands in the calendar, on the series’ own clock across the
    clock change, and the month the calendar hands to the search finds the
    series by any of them; a date moved, renamed, cancelled or taken out
    shows as such.
  • An appointment deleted at Microsoft is marked – in the calendar and
    behind the search’s no longer at Microsoft filter; the file stays, as
    every file does.

Upgrading

The first run after this update reads every selected calendar once in full,
so each series gets its dates, its exceptions and the dates taken out – the
run says so in its log. Nothing else happens once.

Skipping releases is fine: whatever an older release does once after an
update, the first run does too. What changes for scripts against the
HTTP interface is in the notes of the release that changed it – see
all releases.
Coming from far back? A quick look through the notes you skipped shows
whether any of them asks something of you.

Which file?

File For
Munimentum-macos-arm64.dmg Mac with Apple Silicon (M1 or newer)
Munimentum-windows-x64.zip Windows 10/11 (64-bit)
Munimentum-linux-x64.tar.gz Linux (64-bit, glibc 2.35+)

Getting started

macOS — double-click the DMG, drag Munimentum.app onto the
Applications folder shown next to it, close (eject) the window, and start the
app from Applications.

Windows — unpack the ZIP (right-click → Extract All, not just looking
inside), then double-click Munimentum.exe in the extracted folder.

Linux — tar -xzf Munimentum-linux-x64.tar.gz, then run
./Munimentum/Munimentum.

The interface then opens by itself in your default browser. Everything else —
fetching a token, exporting, searching — is explained there.

“Windows protected your PC”

macOS is signed and notarized by Apple — it opens on a double-click, with
no warning and nothing to click past.

Windows is not code-signed. A certificate costs considerably more there, and
SmartScreen additionally wants to see a download count before it goes quiet. So
on first launch you get the blue window: click “More info”, then “Run
anyway”
. It happens once.

If you would rather not, run it from source instead (python3 app.py, see the
README) — the function and the result are identical.

Checksums

SHA256SUMS.txt is attached. Verify with shasum -a 256 -c SHA256SUMS.txt
(macOS/Linux) or Get-FileHash file.zip (PowerShell).

What comes next is in ROADMAP.md.

Munimentum v14.2.1

Choose a tag to compare

@github-actions github-actions released this 04 Oct 13:41

New in 14.2.1

  • A changed file can be recorded as it lies – the evidence findings
    offer it, with a question first: the chain gets a line per file naming
    the checksum before and after, on your word.
  • A re-download with the same size and date reaches the chain – it
    used to slip past the evidence step, and the check reported the file
    changed from then on, whatever you fetched.
  • Logs: one person asked for a manager is “1 person”.

Upgrading

Nothing happens once after this update. A file the check has been
reporting changed since a re-download is settled once with the new
Record as it lies in its findings window.

Skipping releases is fine: whatever an older release does once after an
update, the first run does too. What changes for scripts against the
HTTP interface is in the notes of the release that changed it – see
all releases.
Coming from far back? A quick look through the notes you skipped shows
whether any of them asks something of you.

Which file?

File For
Munimentum-macos-arm64.dmg Mac with Apple Silicon (M1 or newer)
Munimentum-windows-x64.zip Windows 10/11 (64-bit)
Munimentum-linux-x64.tar.gz Linux (64-bit, glibc 2.35+)

Getting started

macOS — double-click the DMG, drag Munimentum.app onto the
Applications folder shown next to it, close (eject) the window, and start the
app from Applications.

Windows — unpack the ZIP (right-click → Extract All, not just looking
inside), then double-click Munimentum.exe in the extracted folder.

Linux — tar -xzf Munimentum-linux-x64.tar.gz, then run
./Munimentum/Munimentum.

The interface then opens by itself in your default browser. Everything else —
fetching a token, exporting, searching — is explained there.

“Windows protected your PC”

macOS is signed and notarized by Apple — it opens on a double-click, with
no warning and nothing to click past.

Windows is not code-signed. A certificate costs considerably more there, and
SmartScreen additionally wants to see a download count before it goes quiet. So
on first launch you get the blue window: click “More info”, then “Run
anyway”
. It happens once.

If you would rather not, run it from source instead (python3 app.py, see the
README) — the function and the result are identical.

Checksums

SHA256SUMS.txt is attached. Verify with shasum -a 256 -c SHA256SUMS.txt
(macOS/Linux) or Get-FileHash file.zip (PowerShell).

What comes next is in ROADMAP.md.

Munimentum v14.2.0

Choose a tag to compare

@github-actions github-actions released this 04 Oct 11:28

New in 14.2.0

  • SharePoint addresses as a tree – paste a site, a subsite, a library
    or a folder in one, and it files itself under its site and library.
    Every address keeps its own cadence and Sync now, and a library named
    only through folders is never mirrored whole by accident.
  • A conversation without words is read once – a chat of pictures,
    files or cards alone used to be read again by every index run.

Upgrading

The first index run after this update reads every file once, because the
readers changed; what it computed before is reused.

A SharePoint line that reaches no library – a typo, a name the address does
not carry – used to bring the whole site along; now the run skips it and
says so in the log, and names any library in the archive that no line
reaches any more. A site address and an address on one of its libraries:
the library's own cadence now wins over the site's.

Skipping releases is fine: whatever an older release does once after an
update, the first run does too. What changes for scripts against the
HTTP interface is in the notes of the release that changed it – see
all releases.
Coming from far back? A quick look through the notes you skipped shows
whether any of them asks something of you.

Which file?

File For
Munimentum-macos-arm64.dmg Mac with Apple Silicon (M1 or newer)
Munimentum-windows-x64.zip Windows 10/11 (64-bit)
Munimentum-linux-x64.tar.gz Linux (64-bit, glibc 2.35+)

Getting started

macOS — double-click the DMG, drag Munimentum.app onto the
Applications folder shown next to it, close (eject) the window, and start the
app from Applications.

Windows — unpack the ZIP (right-click → Extract All, not just looking
inside), then double-click Munimentum.exe in the extracted folder.

Linux — tar -xzf Munimentum-linux-x64.tar.gz, then run
./Munimentum/Munimentum.

The interface then opens by itself in your default browser. Everything else —
fetching a token, exporting, searching — is explained there.

“Windows protected your PC”

macOS is signed and notarized by Apple — it opens on a double-click, with
no warning and nothing to click past.

Windows is not code-signed. A certificate costs considerably more there, and
SmartScreen additionally wants to see a download count before it goes quiet. So
on first launch you get the blue window: click “More info”, then “Run
anyway”
. It happens once.

If you would rather not, run it from source instead (python3 app.py, see the
README) — the function and the result are identical.

Checksums

SHA256SUMS.txt is attached. Verify with shasum -a 256 -c SHA256SUMS.txt
(macOS/Linux) or Get-FileHash file.zip (PowerShell).

What comes next is in ROADMAP.md.

Munimentum v14.1.1

Choose a tag to compare

@github-actions github-actions released this 02 Oct 14:09

New in 14.1.1

  • A run's log reads more easily – counts are grouped like the result
    lines, one item is named in the singular, and what did not happen
    (“0 changed”, “moved 0”) is left out. A mail folder or a calendar with
    changes gets one line, a SharePoint site reached by many addresses too.
  • The index says what it read again – beside the number of files it
    read, a line names the sources they came from.

Upgrading

Nothing happens once after this update; runs logged before it read as
they did.

Skipping releases is fine: whatever an older release does once after an
update, the first run does too. What changes for scripts against the
HTTP interface is in the notes of the release that changed it – see
all releases.
Coming from far back? A quick look through the notes you skipped shows
whether any of them asks something of you.

Which file?

File For
Munimentum-macos-arm64.dmg Mac with Apple Silicon (M1 or newer)
Munimentum-windows-x64.zip Windows 10/11 (64-bit)
Munimentum-linux-x64.tar.gz Linux (64-bit, glibc 2.35+)

Getting started

macOS — double-click the DMG, drag Munimentum.app onto the
Applications folder shown next to it, close (eject) the window, and start the
app from Applications.

Windows — unpack the ZIP (right-click → Extract All, not just looking
inside), then double-click Munimentum.exe in the extracted folder.

Linux — tar -xzf Munimentum-linux-x64.tar.gz, then run
./Munimentum/Munimentum.

The interface then opens by itself in your default browser. Everything else —
fetching a token, exporting, searching — is explained there.

“Windows protected your PC”

macOS is signed and notarized by Apple — it opens on a double-click, with
no warning and nothing to click past.

Windows is not code-signed. A certificate costs considerably more there, and
SmartScreen additionally wants to see a download count before it goes quiet. So
on first launch you get the blue window: click “More info”, then “Run
anyway”
. It happens once.

If you would rather not, run it from source instead (python3 app.py, see the
README) — the function and the result are identical.

Checksums

SHA256SUMS.txt is attached. Verify with shasum -a 256 -c SHA256SUMS.txt
(macOS/Linux) or Get-FileHash file.zip (PowerShell).

What comes next is in ROADMAP.md.