Quick start for each app

Each app works on its own. Install it from the Atlassian Marketplace, then follow its steps below. The steps marked "Jira administrator" need that role; the others need only the usual Jira permissions of the issue.

CascadePlan (about 5 minutes)

  1. Open a Jira project and choose CascadePlan Planner in the project's navigation.
  2. Drag a work item from the Backlog tray onto the timeline to give it dates.
  3. Drag the arrow at the end of one bar onto another bar, and choose when the second may start (for example 30%).
  4. Move the first bar: read the Jira changes listed before you let go, then let go. Ctrl+Z undoes it.

No setup is needed. CascadePlan guide

LedgerSeal (5 minutes, plus the gate)

  1. Open an issue, open the Approval Seal panel from the issue's app button, choose Seal this issue, then Sign and seal.
  2. Edit the issue description: the panel shows what changed since the seal.
  3. Another approver chooses Approve these changes and gives a reason.
  4. Jira administrator: add the Require Valid LedgerSeal validator to the release transition of the workflow. Without it, LedgerSeal reports changes but does not block.

LedgerSeal guide

DefinitionGuard (minutes, plus the gate)

  1. Open an issue and add the Definition of Done panel from the issue's app button. A built-in checklist for the issue type is already there.
  2. Tick items, add evidence where an item asks for it, or waive an item with a reason.
  3. Jira administrator: add DefinitionGuard DoD Enforcement to every transition into a Done status, then publish the workflow.
  4. Project administrator: open Project settings, DefinitionGuard and check that every completion transition is gated.

DefinitionGuard guide

FourRealities (about 10 minutes)

  1. Open Four Realities in the project's navigation. The first open builds the project's view; after that it is refreshed each day.
  2. Link each issue to its decision record: a Confluence page on your site, or a decision issue.
  3. Connect GitHub, Bitbucket or GitLab to Jira if you have not, so the Code check sees pull requests.
  4. Read the issue's four checks. The Process check looks for a Definition of Done record and the Audit check for an approval seal; on a site without DefinitionGuard and LedgerSeal, those two show Not used on this site and are not scored.

FourRealities guide

Application Documentation

Detailed guides covering issue panel interactions, administration settings, workflow validator gates, and compliance reports:

LedgerSeal

LedgerSeal

Cryptographic issue snapshot hashing, Ed25519 digital signatures, tamper detection diffs, resealing workflows, and workflow transition validator setup.

DefinitionGuard

DefinitionGuard

Issue-type Definition of Done checklists, required evidence (a link or a note), items the assignee may not tick, audited waivers, and Done-gate transition blocking.

FourRealities

FourRealities

Project dashboard and issue panel showing evidence across four realities (intent, process, code, audit), Reality Alignment Index (RAI), rework loop counts, and code exception requests.

CascadePlan

CascadePlan

Canvas timeline with percent-trigger dependencies, explanations of why tasks start when they do, previewed Jira writes with undo, keyboard control, table view, and weekly hours per person.

>_

Open Offline Verifier

Standalone, zero-dependency Node.js CLI verifier (verify-evidence.mjs). Validates signatures, SHA-256 snapshot hashes, and hash chains offline against published public keys.

§

Compliance & Security

Formal control mappings for SOC 2 Type II (CC8.1), ISO/IEC 27001:2022 (A.8.32), and FDA 21 CFR Part 11, accompanied by a completed InfoSec vendor assessment.

Support & Operational Assistance

Need assistance configuring your workflow validators or preparing for an enterprise audit? Our engineering team provides direct operational guidance:

[ } Eliya Eliya Jira Governance Jira Governance Dial Dial
Privacy Security
[ }
[ }