Method and trust
Build Pearls separates what a source establishes from the project action we suggest. Each Pearl shows where the lesson came from, which reviews have been completed, its limitations, and how a correction can be raised.
Knowledge boundaries
Lessons developed from an exact version and location in published investigations, standards, or official guidance.
Never described as field-tested, client-approved, or expert-reviewed unless those reviews have actually been completed.
De-identified project experience contributed by a practitioner, with separate attribution, verification, and publication checks.
A field story does not become a public-source rule and is not silently merged with one.
Client-specific project context, required proof, and role assignments used inside that client's workflow.
Kept out of public results, public counts, published source material, and other clients' results.
How a Pearl is published
Every published Pearl is generated from a reviewed version and stored with a content hash. Editing creates a new version, so its source and review history remain traceable.
Review is not one badge
A Pearl can be source-checked without being reviewed for operational usefulness. It can also be published without independent expert review when the publication rules permit it. The interface never compresses those distinctions into an unexplained “verified” label.
| Review check | Possible results | What it tells you |
|---|---|---|
| Publication | Draft · in review · published · rejected · superseded | Whether the revision may appear publicly |
| Source check | Not checked · checked · failed | Whether the cited source and operational proposition were checked |
| Operational review | Not reviewed · reviewed · changes requested | Whether a commissioning practitioner reviewed operational usefulness |
| Independent expert review | Not reviewed · reviewed · changes requested | A separate expert review; never inferred from other states |
| Freshness | Current · review due · stale · superseded · withdrawn · unknown | Whether source and review dates still permit use |
What the source establishes
The source statement stays close to the cited text and shows its jurisdiction, document status, and limitations. Protected standards are referenced, not reproduced.
Build Pearls operational translation
The relevant situation, required proof, responsible role, warning sign, agenda prompt, and return-to-normal check are original project guidance—not a quotation from the source.
Correction mechanism
The current preview explains the correction process but does not promise a response time until production ownership and service levels are approved.