Masthead · Vol. 2

The desk that signs every page.

Every piece on Explore Agentic is written and reviewed by named practitioners — split across an editorial chair, a technical desk for implementation depth, and a strategy desk for procurement and GTM context.

13
Named contributors
5
Technical desk
7
Strategy & GTM desk
81/81
Pieces written / reviewed
Desk

Strategy & GTM desk

7 contributors
How we publish

Every page is signed and reviewed.

Writers and reviewers are listed on every article. Pages that mention Jarvis open with a disclosure banner — Jarvis is built by the same ASCENDING team that publishes Explore Agentic, and we say so on the page, in the footer, and in our editorial policy.

How this works

Frequently asked

  1. Who writes and reviews the work on this site?

    Practitioners on the ASCENDING team, listed above with the coverage area each one actually works in. Every article carries a named author; technical and regulated-industry pieces also carry a named reviewer, shown in the byline. Contributor pages link each person's public profile so the attribution is checkable rather than decorative.

  2. What does the reviewer byline actually mean?

    That a second named person with working knowledge of the subject read the piece against its sources before publication and could defend its claims. It is not a rubber stamp: reviewers send pieces back, and several articles on this site changed materially in review — including one whose central vendor scoring was rebuilt after a reviewer found the comparison had been unfair to competitors.

  3. Do contributors write about products ASCENDING sells?

    Yes, and those pages say so. ASCENDING builds Jarvis AI, so any article touching Jarvis or a direct competitor carries a disclosure banner and flags the Jarvis row in comparison tables. Contributors are expected to publish findings that do not favour our product, and the site contains several that do not.

  4. How are contributors assigned to a piece?

    By working territory rather than availability. Someone who runs AWS agent infrastructure writes the Bedrock and AgentCore material; someone who works on evaluation programs writes the eval material. Where a piece crosses two territories, the second person becomes the reviewer. Each contributor page lists the specific systems, standards, and vendors behind that assignment.