Governed on insert and on update, so a change is authored rather than born already proven.
Change governance where the gate is enforced by the database, not remembered by a person.
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.
This section is being written for ChangeEdge. It names who the product suits and, more usefully, who it does not. We would rather leave it blank than fill it with something generic.
Governed on insert and on update, so a change is authored rather than born already proven.
Gate status is recomputed from the reviews on every write, and a written value is discarded. Forging it is not blocked, it is impossible.
Rewrite the content and the commit, the note and the approver are cleared. A rewritten change is an unreviewed change.
The application connects as a non owner role that cannot disable the write once triggers.
| Feature | Milestone | Scope |
|---|---|---|
| Author, review, approve with a derived gate | v1.0 | In MVP v1.0 |
| Write once record with a non owner connection | v1.0 | In MVP v1.0 |
| Rewrite voids the prior approval | v1.0 | In MVP v1.0 |
| Change calendar and release windows | v1.1 | Planned |
| Emergency change path with retrospective review | v1.2 | Planned |
Milestones are roadmap targets rather than shipped dates. Target for MVP v1.0: Q4 2026. Provisioning is white-glove, never self-serve.
Every SecureEdge Advisory product prepares you for a certification, an audit or an assessment. None of them awards one. A certificate is issued by an accredited certification body, an attestation opinion by an independent auditor, and a regulatory finding by a regulator. We prepare the position and facilitate the process; the affirmation is made by someone else, and we do not blur that line.
Everything a product reports is derived from information supplied by your organisation, or by the person representing it. Ratings, maturity levels, readiness figures, mappings between frameworks and any monetary exposure are calculated from those inputs. Where an input is incomplete, out of date or optimistic, the output carries that forward faithfully. A result is therefore a structured statement of the position you have described, not an independent verification that the position is true.
An assessment is a documented position at a point in time. It is useful precisely because it is explicit about what it rests on, and it should be read that way rather than as a proof. Nothing here is a substitute for an audit, and no output should be presented to a regulator, a customer or a board as one.
Part of a family of ten products sharing one governed control library. Provisioning is white-glove and scope follows a due diligence review.