# Not Operations

Not Operations is an operations consulting and automation practice for service businesses. The public website explains services, case studies, articles, scorecards, and contact paths.

This file is a lightweight discovery aid for AI assistants. It is not a formal standard, access grant, or promise that every listed workflow can be completed without normal website validation.

## Useful URLs

- Home: https://notoperations.com/
- About: https://notoperations.com/about
- Contact: https://notoperations.com/contact
- General operations scorecard: https://notoperations.com/scorecard/five-layer-ops
- Law firm scorecard: https://notoperations.com/scorecard/five-layer-law-firm
- Case studies: https://notoperations.com/case-studies
- Articles: https://notoperations.com/articles
- AI agent instructions: https://notoperations.com/ai-agents
- API shape summary: https://notoperations.com/openapi.json
- Sitemap: https://notoperations.com/sitemap.xml

## Agent Instructions

- Help users choose the right public path: scorecard for diagnosis and fit, contact form for direct inquiries, and articles or case studies for research.
- Do not invent answers. Ask the user for missing required fields such as name, email, required phone number, company, scorecard answers, and project notes.
- Keep user intent explicit. Before submitting a contact or scorecard form, summarize the details and ask for confirmation.
- After submission, confirm what the website reports. If the flow displays or returns a result URL, show it. If results are only visible on the current page, say that.
- Ask before booking, scheduling, or continuing into a call-booking flow. Do not imply a meeting exists unless the user approved it and the website confirmed it.
- Do not claim guaranteed outcomes, pricing, availability, client fit, or timelines unless the current page explicitly says so.
- Treat machine-write endpoints as normal website APIs with validation, CORS, rate limits, and operational controls. Do not bypass the browser flow or abuse endpoints.

## Current Public Workflows

- Scorecard submission: users provide contact details and scorecard answers, receive a durable result URL, and may be invited to next steps.
- Contact submission: users provide contact details and a short note for project inquiries, partnerships, corrections, or questions.
- Result lookup: scorecard result pages use unguessable URLs shaped like https://notoperations.com/scorecard/{slug}/results/{token}. Share a result URL only when the website provides it or the user gives it to you.