# MOT Persona Feedback v0.1

Date: 2026-06-17

Purpose: simulate the first advisory room for MOT / Machine Autonomy Research, then fold useful critique into the launch page.

## Quantum optics professor

Top needs:

- Keep the Kyoto University quantum optics origin credible.
- Do not make MOT look like a generic robotics startup page.
- Show how PHY and MOT differ.
- Treat measurement, falsification, and protocol quality as first-class.

Warnings:

- A strong physics origin can confuse the MOT scope if everything becomes static research.
- Public claims should not outrun experimental evidence.

Site changes made:

- Added the PHY/MOT thesis section.
- Added bench proof, field receipt, and falsification language.
- Kept optical-table imagery as origin context, not the whole story.

## Robotics graduate student

Top needs:

- Concrete challenge cards.
- Reproducible protocols.
- Public metrics that fit a semester or thesis chapter.
- Failure cases and logs, not just wins.

Warnings:

- "Robotics for everything" is too broad.
- Students will bounce if there is no measurable entry point.

Site changes made:

- Added challenge exchange with drone, robot, safety, and energy tracks.
- Added metrics and needs to each challenge.
- Added machine-readable challenge JSON.

## Corporate R&D lab

Top needs:

- Pilot-ready safety cases.
- Procurement-realistic use cases.
- A way to share non-confidential constraints.
- A field receipt format that can survive internal review.

Warnings:

- Corporate labs cannot expose private R&D or customer data.
- Demo videos without safety cases do not pass serious review.

Site changes made:

- Added TempleMirror proof packet concept.
- Added corporate R&D role.
- Added safety and privacy guardrails in `llms.txt`.

## University lab director

Top needs:

- Credit for labs, students, and methods.
- Collaboration format compatible with publications and grants.
- Clear boundary before investor pressure enters the room.

Warnings:

- Too much token talk can scare serious labs.
- Student work needs supervision and credit structure.

Site changes made:

- Framed MOT as research-first.
- Added university lab role.
- Made investor participation observer/patient-capital only.

## AI agent reviewer

Top needs:

- `llms.txt` and endpoint index.
- Structured challenge, claim, and entity packets.
- Clear rule that AI cannot command hardware alone.
- Machine-readable proof receipt examples.

Warnings:

- Agents will summarize incorrectly if claims are not scoped.
- Hardware autonomy requires explicit human authority.

Site changes made:

- Added `llms.txt`, `claims.json`, `entities.json`, `feed.json`, `stream.json`, and `/api/v1/`.
- Added the AI-agent hardware guardrail.
- Added proof packet JSON in the page.

## Investor observer

Top needs:

- Technical gates before fundraising narrative.
- Non-promotional token framing.
- First fundable units: equipment time, compute, bounties, review, and pilots.

Warnings:

- Speculative language can damage university and corporate credibility.
- MOT should not feel like a token pitch.

Site changes made:

- Added coordination ticker language.
- Added token guardrails.
- Kept investor role secondary.

## Concrete MOT ideas worth testing first

1. Drone gust recovery benchmark for urban inspection.
2. Cluttered bench robot handoff under human supervision.
3. Battery truth schema for field robots measured per useful task.
4. Autonomy kill-chain receipt: who can authorize, stop, and review physical action.
5. TempleMirror-verified contributor graph for labs, agents, operators, and reviewers.

## Reviewer council pass 2

Agents used:

- Scientific founder / quantum optics reviewer.
- Robotics graduate student / field operator.
- Corporate R&D and university lab collaboration reviewer.
- AI governance and token-risk reviewer.

Key critique incorporated:

- Token framing was too prominent for serious labs, so MOT is now framed first as measurement-grade physical AI infrastructure.
- The Kyoto origin needed an evidence boundary, so `data/origin-kyoto-physics-v0.1.yml` now states what transfers from quantum optics and what does not.
- The challenge board needed builder-grade work orders, so `data/challenge-work-orders.json` and the richer API fields now include hardware, sensors, protocol, telemetry, thresholds, and submission artifacts.
- The safety layer needed operator-grade gates, so `data/safety-proof-template-v0.1.yml` and `data/field-receipt-kit-v0.1.yml` were added.
- AI guardrails needed to be machine-readable, so `data/ai-autonomy-policy.json` was added.
- Lab collaboration needed redaction, IP, publication, and student-credit boundaries, so `data/collaboration-intake-boundary-v0.1.yml` was added.