For partners, press and analysts. These are the forms KXCO uses itself.
Names
| What | How it is written | Example |
|---|---|---|
| The company | KXCO, endorsed by Knightsbridge | KXCO by Knightsbridge |
| A product, first use | KXCO and the product name | KXCO Portcullis |
| A product, afterwards | The product name alone | Portcullis |
| A module | The product name and a plain word | Portcullis Survey |
| An offer | The product name and a lower-case descriptor | Sovereign for institutions |
| The network, in developer documents | Armature L1. Everywhere else, Armature. | Armature L1 |
| An application built on KXCO by another company | Its own name, followed by 'built on KXCO' | Its own name, built on KXCO |
- Round Table is two words. Every other product name is one.
- Hanse, not Hansa.
- Product names take no full stop.
- A module never carries a mark or logo of its own.
- Package names, commands and other technical identifiers keep their spelling, for example
kxco-pq-scan.
Describing the work
- KXCO supplies the software. Licensed institutions hold the assets and the regulated relationships.
- State a scope the reader can test, for example: the free scan checks JavaScript dependencies.
- Give every figure its date and source.
- Describe a product in development as in development.
- Say what a check shows and where it stops, using the wording on What a record proves.
- Do not describe a signature or an anchor as proof that a claim is true.
- Describe KXCO Herald as live for domains and documents. Identity for people and AI agents is in development.
- Describe Portcullis Muster as scoring an AI agent's declared posture.
Brand files
For logos, product marks and images, write to [email protected].