What we publish and why
We publish two kinds of content: service pages describing what we build, and articles working through problems we hit repeatedly on client projects. Both are written to help someone make an architecture or vendor decision.
- Technical claims come from work we have done or remediated, not from summarising other articles.
- Where we are uncertain, the content says so rather than asserting confidently.
- We do not write content whose only purpose is to rank for a keyword we have nothing to say about.
- Service pages state what our software does not solve, because that is what buyers most need to know.
Review before publication
Drafting
Written by someone with direct experience of the subject, usually an engineer or architect on that kind of build.
Technical review
Checked by a second engineer for accuracy, particularly on security, custody and economic claims.
Compliance review
Anything touching regulation is checked so it reads as implementation experience rather than legal advice.
Editorial review
Checked for clarity and for claims that overstate what we can deliver.
Publication
Dated, with an owner recorded internally so corrections have someone accountable.
Sourcing and attribution
Corrections
Technical writing gets things wrong, and quietly editing a page after the fact is worse than the original error.
- Material corrections are noted on the page with a date rather than silently edited.
- Minor fixes such as typos and broken links are made without a note.
- If a claim turns out to be wrong, we correct it and say what changed.
- Corrections can be requested at [email protected] — confirm address and we respond within X business days.
Independence and disclosure
Use of AI assistance
State your position honestly and specifically. For example: whether AI tools assist with drafting or editing, what human review is mandatory before publication, and who is accountable for accuracy. A vague statement here is worse than none.
This section matters more than it used to. Readers and search engines both weigh a clear, specific AI disclosure over a generic one.