SESecureEdge AdvisoryBetaCustomer loginRequest portal access
Products › ChangeEdge

ChangeEdge ◐ Development

Change governance where the gate is enforced by the database, not remembered by a person.

Walk the simulation →Feature sheet →Request access, at launchProduct website, at launch
Enforced byThe database
FlowPublish, gate, approve
On rewriteProof is voided
RecordWrite once
OverviewCapabilitiesRelease planAssessment fit

What it is

ChangeEdge governs change across products and projects: an author publishes, a reviewer gates, an approver decides. The distinguishing property is that the gate is enforced by the database rather than remembered by a person.

It governs itself, and that was not a slogan until it had been tested. Its own schema was gated four times and failed the first three, each failure the same shape: a guard fired on the door being watched and left the one beside it open.

Key capabilities

State is a one way machineGoverned on insert and on update, so a change is authored rather than born already proven.
The gate is derived, never writtenGate status is recomputed from the reviews on every write, and a written value is discarded. Forging it is not blocked, it is impossible.
A rewrite voids the proofRewrite the content and the commit, the note and the approver are cleared. A rewritten change is an unreviewed change.
The recorder cannot edit the recordThe application connects as a non owner role that cannot disable the write once triggers.

What it supports

Change controlSegregation of dutiesAudit trailISO 27001SOC 2

Release plan · Design → Development → Live

DesignDevelopmentLive
FeatureMilestoneScope
Author, review, approve with a derived gatev1.0In MVP v1.0
Write once record with a non owner connectionv1.0In MVP v1.0
Rewrite voids the prior approvalv1.0In MVP v1.0
Change calendar and release windowsv1.1Planned
Emergency change path with retrospective reviewv1.2Planned

Milestones are roadmap targets, not shipped dates. Target for MVP v1.0: Q4 2026. Provisioning is white-glove, never self-serve.

What this establishes. These products prepare you for certification and audit. They do not award either. Every figure is derived from what your organisation reports, and is a documented position rather than an independent verification.

Two ways to see it

The simulation

Walk the workspace before anything is provisioned. Start an assessment first and the simulation is populated with your own position rather than a demonstration dataset.

The live productat launch

Once this product reaches Live it is provisioned to your organisation and configured to your environment, and its own product website opens. It is not there yet, and we would rather say so.

Provisioning is white-glove rather than self-serve, and scope follows the due diligence review. The stage above is the honest position today, not a target.