Ledger Governance

approved

by DosanjhLabs

Governance for Obsidian: a document status lifecycle (draft to published), owner and review tracking, a governance dashboard, and an in-vault audit log. 100% local - no account, no network. - This plugin has not been manually reviewed by Obsidian staff.

104 downloadsUpdated 2mo agoMIT

Ledger Governance

An Obsidian community plugin that turns a personal vault into a governed, company-grade one — without leaving your editor and without an account.

Ledger is 100% local: no login, no tokens, no network, no servers. Governance lives in standard frontmatter (owner, status, reviewed_on), so your notes stay portable plain markdown. Free and open source (MIT).

What you get

  • Governed-document templateNew governed document scaffolds a note with the governance frontmatter (owner, status, review cadence) already in place.
  • Status lifecycleSet document status moves a doc through draft → in-review → approved → published.
  • OwnershipSet document owner assigns an owner (name or email).
  • Review trackingMark current note reviewed stamps reviewed_on; docs past their cadence (default 90 days, or a per-note review_cadence_days) show as stale.
  • Governance dashboardGovernance dashboard (also the ribbon icon) shows the status mix, review freshness (never / stale / fresh), and which docs are ungoverned (missing an owner or a status). Click any row to open it. The status bar keeps a live N docs · X stale · Y ungoverned summary.
  • In-vault audit log — every governance action is appended to _ledger/audit.md, a plain-markdown audit trail you own. Open governance audit log jumps to it.

All commands are in the Command Palette (Ctrl/Cmd-P, type "Ledger").

Install (manual, until listed in Community Plugins)

  1. Copy this folder to your vault: <vault>/.obsidian/plugins/ledger-governance/ (it must contain manifest.json and main.js).
  2. Settings → Community plugins → enable Ledger Governance.

No build step — the plugin loads main.js directly. No setup, no sign-in.

Privacy

Nothing leaves your machine. The plugin makes no network calls and stores no account or token. Governance metadata is written into your own notes' frontmatter and the audit log lives in your vault. Settings (review-stale threshold, whether an owner/status is required) are stored in the vault's local plugin data.

Verify

node verify.js

Static checks: manifest shape, main.js parses and exports a Plugin subclass, all six commands present, the local-only guarantee (no fetch / requestUrl / auth token / http URLs anywhere), and the governance layer (status lifecycle, frontmatter writes, audit log).

License

MIT — see LICENSE.

For plugin developers

Search results and similarity scores are powered by semantic analysis of your plugin's README. If your plugin isn't appearing for searches you'd expect, try updating your README to clearly describe your plugin's purpose, features, and use cases.