SENTRYSchedule a demo

Working prototype · Private beta

Find the defence requirements that apply to what you build.

SENTRY reads defence and engineering standards with your team. It shows which standards apply to a product, what each one requires, and the exact clause and page every requirement comes from.

Built for defence manufacturers and their engineering teams.

QuestionVehicle-mounted radio enclosure. Which environmental requirements apply?

  • EXAMPLE-STD-100 Rev CShall

    §5.2.4 · p. 37Applicable · vehicle use

    Open source page →
  • EXAMPLE-STD-205Should

    §3.1 · p. 12Applicable · normative reference

  • EXAMPLE-STD-410Unresolved

    Referenced, not held · access status shown

  • EXAMPLE-STD-300Excluded

    Reason: shipborne equipment only

Illustrative layout with fictional documents. Not real SENTRY output.

One missed clause can stop a production run.

Defence products must meet requirements spread across many standards. Those standards reference other standards, use their own vocabulary, and change by edition.

Keyword search misses what it cannot name. A general AI chat answer cannot show where a requirement comes from. Engineers need both: wide discovery, and a source they can check.

Capabilities

From an engineering question to the source page.

01

Standards discovery

Describe the product in plain engineering language. SENTRY searches by meaning, so it still finds the right documents when you do not know the designation, the acronym or the exact wording. It follows references from one standard to the next.

02

Applicability

Each candidate standard gets a proposed disposition: applicable, excluded with a reason, or unresolved. SENTRY shows the evidence for each one. Your engineer makes the final call on anything disputed.

03

Requirement tracing

Requirements come out with their standard, edition, clause and page, and with their obligation level: shall, should, may or informative. Related and referenced requirements stay linked.

04

Source provenance

Every quoted passage links to the original page of the source document. The AI summary is never the authority. The standard is. Engineering inference is labelled as inference.

Workflow

Five steps, one traceable result.

  1. Describe

    State the product, its configuration and its intended use.

  2. Discover

    SENTRY finds candidate standards and follows their references.

  3. Decide

    Review each proposed disposition and the evidence behind it.

  4. Trace

    Get each requirement with clause, page and obligation level.

  5. Verify

    Open the original page and check the exact wording.

The result is an applicability register and a requirements register your team can review, challenge and keep.

Technical principles

Built so an engineer can trust it, and check it.

It says when it does not know

When the held sources do not support an answer, SENTRY says so. A standard that may apply but is not held is shown as unresolved, never left out.

Rights are checked before evidence is shown

Clause-level text comes only from documents that are public or that your organisation is entitled to use. SENTRY does not supply licensed standards.

Your documents stay yours

Documents your team brings stay in a separate, private collection. They are never pooled with other customers or shared.

Relevance is not applicability

A document that mentions your topic is not automatically a requirement. SENTRY keeps related, applicable and mandatory as separate, visible states.

QuestionStandard and editionClausePageOriginal source

Who it is for

Teams that design, build and qualify defence equipment.

Private beta

The prototype works today. Access is by invitation.

We are opening SENTRY to a small number of engineering teams. In a demo we walk through a real engineering question, from discovery to the source page, and discuss the standards your team works with.

The beta works over public standards and over documents your organisation is entitled to use. You keep control of what you bring.