Skip to content
HoldField

StandardsOps

Standards status you can trust — evidence, not unsupported claims

See every supported standard with an honest status — held with a real certificate, evidence-ready, mapped, in progress, or not claimed — mapped to real clause evidence, with gaps exposed and redacted packets an auditor can review. No unsupported certification claims.

Certification status

Five honest statuses. Held means a real certificate.

  • HeldA real certificate is registered, active, unexpired, in scope, and evidence-backed.
  • Evidence-readyHoldField can collect and organize the evidence for this framework — no certification is claimed.
  • MappedThe framework is mapped to controls and evidence, but not yet fully implemented.
  • In progressImplementation exists with known gaps that are surfaced, not hidden.
  • Not claimedShown only for transparency. No claim is made for this framework.

Step 01

Standards registry

Each standard HoldField supports shows one status — held with a real certificate, evidence-ready, mapped, in progress, or not claimed — so a buyer sees exactly what is proven and what is not.

Inputs

  • Standard code and category
  • Quality, aerospace, medical, security, and AI governance frameworks
  • Support status
  • Certificate requirement
  • Clause-evidence requirement
  • Public-safe label

Proof generated

  • Standards registry receipt
  • Per-standard status
  • Certificate-required marker
  • Clause-evidence-required marker
  • Registry hash

Where it appears in the app

  • StandardsOps
  • Capabilities
  • Trust

AI Sense support

  • Flags a standard shown as held without a backing certificate
  • Flags a status that outruns its evidence
  • Explains what each status honestly means

Safety boundary

  • A registry status is not a certification. It describes what is evidenced, never what is approved.

Step 02

Certificate register

A standard reads as held only when a real certificate is registered, active, unexpired, unsuspended, and in scope — an expired, suspended, withdrawn, or out-of-scope certificate can never present as held.

Inputs

  • Certificate number and issuing body
  • Scope by site, station, and product family
  • Issued and expiry dates
  • Lifecycle state
  • Evidence references

Proof generated

  • Certificate register receipt
  • Validity result
  • Scope-match result
  • Expiry timeline
  • Certificate hash

Where it appears in the app

  • StandardsOps
  • Trust
  • CustomerTrust

AI Sense support

  • Flags an expired or suspended certificate still shown as held
  • Flags a scope mismatch for an out-of-scope site or station
  • Flags an expiry approaching review

Safety boundary

  • A registered certificate is an administrative record of a customer credential — it grants no authority in the cell.

Step 03

Clause evidence map

Every clause maps to the specific evidence it needs — inspection, calibration, first-article, training, audit, and supplier records — with an owner and a review status, so readiness reflects true clause evidence rather than a count of unrelated records.

Inputs

  • Clause reference and requirement
  • Required evidence types
  • Acceptance criteria
  • Current evidence references
  • Owner role

Proof generated

  • Clause evidence map receipt
  • Per-clause review status
  • Gap references
  • Owner assignment
  • Requirement hash

Where it appears in the app

  • StandardsOps
  • EvidenceWorks
  • Trust

AI Sense support

  • Flags a clause with missing or thin evidence
  • Flags evidence that does not meet the acceptance criteria
  • Ranks the clauses closest to ready for review

Safety boundary

  • A clause mapped to evidence is prepared for review. It is not a finding of conformance or a certification.

Step 04

Audit readiness

Audit readiness is shown as clause completeness, open gaps, and owners — a working picture a quality team drives before a real audit, not a self-issued pass or fail.

Inputs

  • Clause evidence map
  • Certificate register
  • Open gaps
  • Corrective-action linkage
  • Owner assignments

Proof generated

  • Audit readiness receipt
  • Clause completeness by area
  • Open-gap count
  • Owner coverage
  • Readiness hash

Where it appears in the app

  • StandardsOps
  • Trust
  • EnterpriseGuard

AI Sense support

  • Summarizes where evidence is thin before an audit
  • Ranks the gaps most likely to be raised as findings
  • Prepares the questions an auditor is likely to ask

Safety boundary

  • Audit readiness is a working view. It cannot decide a QC disposition, close a finding, or approve production.

Step 05

Open gaps

Missing evidence, unproven capability, expired certificates, scope mismatches, and unsupported claims are surfaced as open gaps with an owner and a severity — so the honest work left is visible, not papered over.

Inputs

  • Missing clause evidence
  • Expired or suspended certificates
  • Scope mismatches
  • Unsupported-claim flags
  • Severity and owner

Proof generated

  • Open gaps receipt
  • Gap list by severity
  • Owner assignment
  • Corrective-action linkage
  • Gap hash

Where it appears in the app

  • StandardsOps
  • ImprovementWorks
  • Trust

AI Sense support

  • Finds a gap not yet recorded
  • Flags an unsupported certification claim
  • Ranks gaps by likely audit impact

Safety boundary

  • A gap can be recorded and assigned but never closed by StandardsOps — closure is a human corrective-action decision.

Step 06

Support packet

Support teams assemble a redacted evidence bundle — supported standards, clause status, open gaps, and references — with raw evidence, secrets, and identities withheld and an explicit omissions list.

Inputs

  • Standards status
  • Clause evidence references
  • Open gaps
  • Held certificates
  • Redaction policy

Proof generated

  • Support packet receipt
  • Included sections
  • Omissions list
  • Redaction markers
  • Packet hash

Where it appears in the app

  • StandardsOps
  • Support
  • Trust

AI Sense support

  • Finds a section missing from the packet
  • Flags a reference that would leak raw content
  • Prepares the incomplete requirements before sharing

Safety boundary

  • A support packet is redacted evidence for review. It never contains raw evidence, secrets, keys, or PLC data.

Step 07

Customer review packet

Customer quality and IT/OT reviewers receive a scoped, redacted review packet — standards status, clause evidence, certificate validity, open gaps, and known limitations — with an omissions list, through the existing CustomerTrust boundary.

Inputs

  • Scoped standards status
  • Clause evidence references
  • Certificate validity
  • Open gaps
  • Known limitations

Proof generated

  • Customer review packet receipt
  • Scoped sections
  • Known limitations
  • Omissions list
  • Packet hash

Where it appears in the app

  • StandardsOps
  • CustomerTrust
  • Trust

AI Sense support

  • Finds missing review evidence
  • Flags an unsupported claim before it reaches a customer
  • Prepares the questions a customer auditor may raise

Safety boundary

  • A customer review packet is review evidence. It is not certification, an audit result, or station control.

Step 08

AI Sense compliance insights

AI Sense reads the registry, certificates, clause evidence, and gaps and returns observations — missing evidence, expired certificates, scope mismatches, and unsupported claims — each with the human checks it recommends next.

Inputs

  • Standards registry
  • Certificate register
  • Clause evidence map
  • Open gaps
  • Support and review packets

Proof generated

  • Compliance insight references
  • Severity and confidence
  • Recommended human checks
  • Unsupported-claim flags
  • Insight hash

Where it appears in the app

  • StandardsOps
  • Trust

AI Sense support

  • Observes missing clause evidence
  • Observes expired certificates and scope mismatches
  • Recommends the human checks that close each gap

Safety boundary

  • AI Sense observes and explains. It cannot certify, approve, close a finding, accept risk, force PASS, or write a PLC output.

Step 09

Known limitations

The last section states the boundary in the open — HoldField organizes evidence against selected standards and shows certifications only when a real certificate is active and in scope; it is not a registrar and issues no certification of its own.

Inputs

  • Not-certification boundary
  • Evidence-support scope
  • Standards shown as mapped or in progress
  • What still needs customer evidence

Proof generated

  • Known limitations receipt
  • Boundary statement
  • Evidence-support scope
  • Customer-evidence requirements
  • Boundary hash

Where it appears in the app

  • StandardsOps
  • Trust

AI Sense support

  • Flags copy that reads as an unsupported certification claim
  • Flags a standard shown stronger than its evidence
  • Prepares the honest caveats for a review

Safety boundary

  • HoldField assembles evidence and shows honest status. It never grants or implies certification of its own.

AI Sense finds the missing proof, never certifies

AI Sense

One reading layer across every StandardsOps step

Observes evidence, finds missing proof, explains uncertainty, ranks human checks, and prepares handoffs — it never commands hardware.

Reads

  • Evidence bundles
  • Review events
  • QA decisions
  • Vision Twin drift
  • Commissioning blockers
  • Governance decisions
  • Station registry
  • Ops metrics

Produces

  • Findings
  • Evidence-gap warnings
  • Work-package hints
  • Commissioning questions
  • Support summaries

Never

  • No PLC writes
  • No force PASS
  • No recovery clear
  • No robot commands
  • No camera/light commands
  • No production approval
  • No evidence mutation
  • No QA decision mutation

AI Sense observes evidence and guides humans — it records nothing and changes nothing. It does not command a station, write a PLC, clear recovery, reset safety, force a pass, approve production, sign off, or mutate any review, QA decision, commissioning, governance, evidence, or runtime state. Every recommendation is a suggestion for a human to carry out; the PLC and safety circuit remain authoritative.

What HoldField does not claim

The boundary, stated in the open

  • HoldField does not claim ISO, AS9100, NADCAP, SOC 2, FDA, or IEC certification unless an active certificate is registered and in scope.
  • HoldField does not replace a certification body, external auditor, quality manager, notified body, customer approval, PLC safety authority, or legal counsel.
  • A standard reads as held only when a real certificate is active and in scope — otherwise it reads as evidence-ready, mapped, in progress, or not claimed.
  • Standard editions are version-watched, not hardcoded — a stale edition label is itself an unsupported claim, so each framework carries a review cadence.
  • HoldField organizes evidence, enforces workflow boundaries, and exposes gaps instead of hiding them.

Customer review packet

Review evidence by reference, never certification

The redacted review packet carries the standards status, certificate validity, clause evidence references, audit readiness, open gaps, known limitations, and an explicit omissions list — so a customer quality or IT/OT team can review the evidence without any station ever handing over raw internals, and without HoldField claiming a certification it does not hold.

standards_status
per-standard status: held, evidence-ready, mapped, in progress, or not claimed
certificate_validity
certificate number, scope, and validity — active, expired, suspended, or out of scope
clause_evidence
per-clause review status and evidence references — never raw evidence content
audit_readiness
clause completeness by area with owners and open-gap counts
open_gaps
the honest work left, by severity, with an owner on each
known_limitations
what the standards view does not claim and what still needs customer evidence
omissions
explicit list of what was withheld
packet_hash
integrity fingerprint of the redacted review packet

The packet never contains raw evidence files or inspection frames, raw PLC coils or registers, private keys or signing secrets, authority tokens, operator personal identity or local file paths, customer names outside the review scope.

Signed-in teams run this operationally in the HoldField app, under StandardsOps — where the standards registry, certificate register, clause evidence map, audit readiness, open gaps, support packets, and the redacted customer review packet are recorded as administrative proof, and where every station stays the local authority: nothing here certifies a facility, marks a standard met without clause evidence, hides a gap, or commands a station. Open the workspace →