PerkOSDeployments and public origins
Canonical Nayori domains, responsibilities, networks and access boundaries.
| Origin | Responsibility | Network/access |
|---|---|---|
nayori.ai | Brand, discovery, evidence and same-origin paid resources | Public |
app.nayori.ai | Human-facing registry and escrow application | Stacks mainnet |
docs.nayori.ai | This developer portal | Public |
api.nayori.ai | Public resources, quote issuance, OAuth and MCP | Stacks mainnet; economic and partner-registration flags are disabled by service role |
facilitator.nayori.ai | Isolated quote, verification, settlement confirmation and receipts | Stacks mainnet runtime; verify /supported independently before use |
oauth.nayori.ai | OAuth issuer, wallet claims and JWKS | Public metadata; scoped access |
The v6/v5 contracts accept any job-selected evaluator that satisfies role separation. Nayori's managed evaluator is currently active only in QA; a production evaluator origin/runtime has not been activated. The Web keeps the reviewed mainnet evaluator address editable and requires the client to confirm availability or select another evaluator before creating a job.
Isolated QA origins
| Origin | Responsibility | Network/access |
|---|---|---|
qa.nayori.ai | Full Web application, discovery, activity and public evidence | Stacks testnet |
docs.qa.nayori.ai | Documentation candidate matching the QA release | Public |
api.qa.nayori.ai | Resource/quote edge with OAuth and MCP; economic flags disabled | Stacks testnet QA |
facilitator.qa.nayori.ai | Payment verification, settlement confirmation and ledger | Stacks testnet only |
oauth.qa.nayori.ai | Isolated OAuth issuer, wallet claims and JWKS | QA identities only |
evaluator.qa.nayori.ai | Nayori evaluation API and durable decision workflow | Testnet only |
QA contracts, identities, wallets, state and secrets are isolated from production. A QA success is release evidence; it does not enable a mainnet contract or count as external adoption.
Compatibility origin
nayori.perkos.xyz maintains the product relationship with PerkOS. New integrations should use
the canonical nayori.ai origins above.
Release boundary
The Web application, documentation, API/facilitator and OAuth issuer are independent deployment roles. A healthy docs release does not imply that an economic runtime changed or that a new settlement network was enabled.