Structural review cycle
In force on publication. Last reviewed 2026-08-18. First full review due 2027-08-18.
1. What gets reviewed
Every document in this pack, plus the customer data commitments, the Regen Pool commitment, and the reserved matters list. Not the product, not pricing, not strategy. Those change constantly and should.
The question a structural review asks is narrow: is each of these still true, and is any of them now describing a company that no longer exists?
2. Cadence
| Cycle | When | Depth |
|---|---|---|
| Quarterly check | Mar 31, Jun 30, Sep 30, Dec 31 | Publish the figures in document 07. Confirm each document is still accurate. Note anything that has drifted. |
| Annual review | Each August | Full review of every document. Test the continuity plan. Re-confirm the Steward. Publish what changed and why. |
| Triggered review | On any event in section 3 | Only the documents the event touches, within 30 days. |
3. Triggering events
Any of these starts a review within 30 days, regardless of where the calendar sits:
- The first employee.
- The first outside capital, of any form.
- Any single customer passing 25% of revenue.
- Any single funding source passing 25%.
- A Steward vacancy, resignation, or refusal that the founder disputes.
- A conflict reaching stage 4 under document 04.
- Continuity plan activation, or a failed annual escrow test.
- Formation of the entity, and again on issuing the Steward Interest.
- A security incident affecting customer data.
- Any drift metric crossing its threshold in document 07.
4. What the annual review must produce
- A statement per document: unchanged, amended, or no longer true. “No longer true” is a valid and important outcome and must not be quietly converted into an amendment.
- A tested continuity plan. Request escrow release, confirm the Steward can reach what section 5 of document 02 lists, then cancel. An untested escrow is a guess.
- A Steward confirmation. The Steward states in writing that they are still willing, still independent, and still reachable.
- A published diff. What changed, when, and why. Not a new version silently replacing the old.
- The unfixed list. Everything a document admits it does not fix, restated, with whether it is closer to fixed than last year.
5. Who can trigger a review
- The founder, at any time.
- The Steward, at any time, and the founder cannot decline.
- Any customer or partner, by written request. Saberra must respond within 30 days saying whether a review will run and why. A refusal is published as a count in the quarterly figures.
6. Amending a document in this pack
- Documents 00 boundaries 3, 4, 5 and 7, and documents 01, 03 and 08 in the parts named as reserved matters, require the Steward's consent.
- Everything else may be amended by the founder, with the change published in the next quarterly figures.
- Prior versions are preserved. These documents are version controlled and the history is public, so an amendment is visible as an amendment rather than appearing as though the text always read that way.
- No document in this pack may be amended retroactively. A change takes effect from its publication date, never before.
7. What this does not fix
A review cycle a single person runs on documents that same person wrote, checked by a Steward with a narrow veto, is not independent review. It catches drift and staleness. It would not catch a founder who has decided to be dishonest, and no internal process would.
The honest version of what this provides: the documents will not quietly rot, and when they stop being true, that will be published rather than concealed.