Gate 01
Subject declaration
One device, campaign, component or ecosystem — named exactly, with firmware or version fixed.
Produces — Fixed identity + version
LRRK Assess
An examination is only as honest as its boundary.
Assessment begins with paperwork, not probes. Before anything is measured, the archive records who authorized the work, what may be examined, and the period in which the answer will hold.
§ 01
Intake sequence
§ 02
What an assessment refuses to say
- No implied coverage
- A finding about one configuration is never presented as a statement about a product line.
- No absence claims
- Not established is recorded as not established. It never becomes safe, clean or secure.
- No score
- Assessments produce an explained story with confidence bands, not a single grade.
- No silent scope drift
- Extending a question requires a new authorization and a new version of the story.
Capability label: designed workflow — the gate schematic is illustrated, not operating. To file a real request, use the intake form in § 03.
§ 03
Request an assessment
Requests are filed as a Consumer Robotics Evidence Brief: one named subject, one bounded question, and the source boundary you declare. The form below records the request only — scope, timing and terms are confirmed in writing by a person, and no payment is collected on this site.
Already have an account? File a signed-in brief →Already filed one? Track its status →See stated amounts →
Capability label: designed workflow — the gates above are illustrated, not operating. This form is live and reaches a human reviewer.
Once a boundary is signed, the story opens at Plate 01 — the permitted question, before any evidence exists.
Open the Atlas →