No company facts are currently approved for display
Drafts and records that have not passed every publication gate remain inside the operating system.
TRUST—REGISTER
Trust starts with facts and visible boundaries.
The site does not fill gaps about legal identity, insurance, clients, experience, credentials, or metrics. Company facts are stored with provenance, an accountable owner, validity, and publication state.
01
Company-facts registry
A fact leaves the registry only after its source, owner, and validity are verified, publication is explicitly enabled, and the exact value is approved. Any edit invalidates the prior approval.
02
Assessment data
Client identity, findings, and sensitive evidence are encrypted with record context. Access is role- and engagement-bound, and sensitive reveals are logged. Retention and deletion must be configured per engagement; full automation remains a production gate.
03
Partners and subcontractors
Client information is revealed to a partner only after a valid assignment. The open-work board exposes a minimal structured preview, without client identity, targets, or free-text scope.
04
AI boundaries
A client-bound AI request is blocked unless a stored, current authorization allows the engagement, data class, and provider. Output is schema-validated, stored as a draft, and left for human review. There is no automatic sending path.
05
No autonomous outbound
Proposals, messages, invitations, and reports remain in an approval queue. Approval is bound to the exact content, recipient, attachments, and facts, and still performs no send.
NEXT DECISION
Inspect the report standard
The report standard sets out the structure, evidence, and limitations expected in the deliverable.
View the report standard