Governance / Pro
pi-change-reason
The agent must justify every edit before it runs. No silent drift - each file mutation requires a concrete, one-line reason recorded in the audit trail.
What it does.
- Justify-before-edit gate - every edit, write, and hashline_edit requires a set_change_reason call first.
- One-line reasons: quick to write, slow to skip - the cost of opacity.
- Reasons are emitted as governance events and land in the local event log.
Put it to work.
Use the Pro archive from your purchase. The Pro or Team bundle includes its Pi extensions. An individual module archive uses the same installer.
Choose a file to build your exact command.
Run this command from the folder containing the archive. Selecting a file here does not install or execute anything.
Activate your license with /bastille-license refresh inside Pi. Activation and periodic entitlement validation contact Polar. Your workload is not uploaded to Bastille-C3.
Full installation & activation guide →In use.
Inside Pi
/change-reasonInside Pi
/change-reason statusWhen the requirement is on, the agent must call set_change_reason with a one-line reason before each edit, write, or hashline_edit. Turn it off with the same command.
Worth knowing.
- Independent of pi-change-review - install either, both, or neither. Together they require both a reason and your approval before any change lands.
- Requires a valid Polar license.
Remove this module
Uninstall this extension
pi uninstall npm:@bastilleworks/pi-change-reasonRemoving an extension does not cancel your subscription. Manage renewal separately.
On the same ground