Assessment
Map authority and evidence gaps for one bounded system or workflow.
Begin with the authority and evidence question. Each later stage receives its own scope, acceptance criteria, commercial terms and explicit permission to proceed.
For an existing or proposed AI system where the authority to act must be visible and defensible.
Can your AI system prove who has authority to execute what?
One agreed system or workflow, accountable owners, intended actions and excluded authority.
Review the available policy, execution and decision records; identify what is missing or cannot support the claim.
Describe human approval points, uncertainty handling, stop conditions and evidence obligations.
An authority-boundary map, evidence-gap register and a bounded next-gate recommendation, as fixed in the statement of work.
The assessment diagnoses the boundary. Testing, pilot execution and deployment are separately scoped stages; an assessment does not confer execution authority or certify a system.
Map authority and evidence gaps for one bounded system or workflow.
Execute the agreed test contract and retain results, exceptions and limits.
Implement a bounded use case with human approval and stop/go criteria.
Integrate only within accepted permissions, environment and evidence obligations.
Revalidate changes and maintain evidence; expansion requires a new gate.
P5R: Validate → Pilot → Licence → Assure → Expand. Assessment and sprint sit inside Validate. Any expansion creates a new boundary and acceptance gate.
Fees and timing depend on the agreed boundary and evidence access. No price, delivery date or service level is implied by this website.
Provide a non-confidential brief: mission, system, authority owner, evidence question, budget or funding status, timeline and procurement constraints.
Confirm fit, deliverables, acceptance criteria, exclusions, contracting party, fee and the invoicing or procurement route in writing.
Private scheduling and payment instructions follow acceptance. Work proceeds under the agreed scope, data boundary and human decision rights.
State vendor onboarding, purchase-order or institutional agreement requirements in the brief. The applicable legal contracting and invoicing route is confirmed case by case.
HMH-GRA has closed its defined scope. Major next-stage R&D, including proposed HMH-GFA fleet and authority validation, proceeds only under funded or co-funded agreements.
Institutional and research routes →The site creates a browser-local enquiry brief. It does not host a lead database, expose an unrestricted calendar, collect payment credentials or activate a public payment processor.
Qualification determines the appropriate first scope. A request does not guarantee a booking, pilot or licence.