Standards & Methodology
Standards & Methodology
This page explains how Decision Insights produces its coverage: where it comes from, what qualifies, how it's summarized, and the standards we hold to.
Oversight and accountability
Decision Insights coverage is produced under processes designed and monitored by Wiretap Labs. Matthew Palmer, founder and CEO, is accountable for the prompts, the sourcing rules, and the standards described on this page.
The methodology draws on thirteen years of enterprise technology publishing at SDxCentral, where the same editorial questions were answered by human reporters. That archive is used to calibrate and quality check what these desks publish: what counts as a source, when a claim needs attribution, and which developments matter to an enterprise buyer rather than to a vendor.
The same calibration governs the glossary. A term is admitted when it is already in use in the markets this site covers, in vendor announcements, security advisories, standards documents and the coverage we already hold, rather than because one vendor has coined it for one product. Each definition is written from how the term is used across those sources, describes what the term means rather than what any one vendor sells, and is reviewed under the oversight above before it is published.
Each term is connected to the organizations, open source projects and records that use it, so a definition can be read against the material it was drawn from. A definition is editorial work, not a verified fact and not a standard: where a standards body has defined a term, the entry points at that body rather than restating it. Corrections to a definition follow the same route as any other record, described under Data accuracy and corrections below.
Sourcing
Every brief starts from a primary source: company and vendor announcements, official security advisories, and newswire releases. We attribute each brief to its source and link back to it so you can read the original.
When we describe this record set as authoritative, that is precisely what we mean by it: every item traces to the organization that published it. A record here is built from the original announcement, advisory or release, and links back to that document.
On every brief:
- The original source is named and linked, so any statement can be checked where it was first made.
- The original author is credited whenever the source provides one.
- The kind of source is labelled. A newswire press release and a company blog post carry different weight, and each record says which one it came from.
What qualifies
We cover enterprise technology developments in four markets: cybersecurity, data centers, network operators, and AI infrastructure. Items are filtered for relevance and de-duplicated so each development appears once, and financial disclosures (earnings, restatements) are treated as data rather than editorial coverage.
How summaries are generated
Summaries are generated with AI assistance into a consistent, structured format and linked into the Decision Insights knowledge graph, connecting each development to the organizations, open-source projects, and technologies it involves. Our standards prioritize accuracy and faithful attribution to the source. Wiretap Labs spot-checks published coverage on an ongoing basis.
What inclusion means
Every organization, open-source project and glossary term is reviewed before it appears. We assess each one as a real and relevant entity in enterprise technology, and admit it on that basis.
A listing is free. It records what an entity is and keeps that record current. Judgements about the quality of a company or its products are for buyers to make.
Data accuracy & corrections
Listing and knowledge-graph data (companies, projects, technologies) is compiled from multiple sources and may contain inaccuracies. To report an error in a brief or a Listing, email [email protected]. Reports are reviewed and corrected under the oversight described above.
What a record carries
Every page is published as schema.org structured data. Not a plugin, and not an export. Read the JSON-LD on any page and you get:
| Page | Schema type | Provenance properties |
|---|---|---|
| Company | Organization or Corporation, in a ProfilePage | sameAs, subjectOf |
| Open source project | SoftwareSourceCode | author, subjectOf |
| Technology term | DefinedTerm, in a CollectionPage | inDefinedTermSet, termCode |
| Record or brief | NewsArticle or BlogPosting | isBasedOn, about, author, datePublished |
isBasedOn carries the source a record was written from. sameAs ties a company record to the company's own canonical properties, so you can resolve the entity rather than guess at it. subjectOf points from a company to the coverage about it.
Check any of this with view-source. That is the point of publishing it this way.
See what an agent sees puts a company's listing and the JSON-LD an agent receives for it side by side.
What connects to what
A record is not stored on its own. Each one is linked to the organizations, open source projects, and technology terms it refers to, so it can be reached from any of them.
In practice: ask for Netskope and you can reach the technology terms its coverage is filed under, the other companies publishing on those same terms, and every dated record that names it, without issuing a second search.
One thing worth encoding in how you use it. Company-to-company links normally come from the curated peer set on the company's own record, the same list that record publishes as Similar organizations, so the two surfaces agree and can be joined on each peer's id. That set is built from the organization's own topic profile over the listed directory and excludes its parent and subsidiaries. For a company with no curated peers, the response falls back to topical overlap between the articles we publish about each company, which measures our coverage rather than the companies. The method field on every response names which of the two produced it. Neither is an assertion that two companies compete, and neither is an alternatives list.
How something gets in here
Every organization, open source project, and term is reviewed before it is admitted, and checked against the rest of the graph rather than taken on its own: whether the entity is real, whether it belongs in these four markets, and whether what we hold about it agrees with what the other records say.
Every record and brief is written from a primary source, links back to it, and labels what kind of source that was. A newswire release and a company blog post carry different weight, so each record says which one it came from. The original author is credited whenever the source provides one.
What we do not do is fact-check the underlying claims. A vendor announcement summarized here is a faithful summary of that announcement, not a finding that the announcement is true. Follow isBasedOn and read the original where the claim matters.