# RightOS
# Assignment is not authority. RightOS answers MAY (rights). RightFlow answers NEXT (coordination). Execution systems answer HOW.
# Reassignment through RightFlow proposals; rights checks through RightOS; use with MCP and A2A-style messaging as complements.
# Privacy-preserving rights verification — QR tickets for queues, EV, pickup, and multi-actor authority gates. Not ride-hailing.
# Cross-industry API, no required end-user PII, embeddable via API / SDK / MCP, rights kept separate from coordination.
# Concept: https://rightos.i-s3.com/software/rightos/docs/concept
# Decision: https://rightos.i-s3.com/software/rightos/docs/decision
# RightFlow: https://rightos.i-s3.com/software/rightflow
# Docs: https://rightos.i-s3.com/llms.txt · https://rightos.i-s3.com/llms-full.txt
# Landing: https://rightos.i-s3.com/software/rightos
# OpenAPI: https://rightos.i-s3.com/openapi.json
# RightFlow OpenAPI: https://rightos.i-s3.com/rightflow-openapi.json
# MCP: https://rightos.i-s3.com/software/rightos/docs/mcp · npx -y @i-s3/rightos-mcp
# RightFlow MCP: npx -y @i-s3/rightflow-mcp
# Registry: https://registry.modelcontextprotocol.io/v0/servers?search=io.github.suomimasuda/rightos-mcp
# FAQ · Security · Stories: /software/rightos/faq · /security · /stories
# Sign up: https://rightos.i-s3.com/software/rightos/signup?plan=free
# Demo key: rk_demo_00000000000000000000
# npm: @i-s3/rightos · PyPI: rightos-sdk