Built for people. Readable by machines.
Agents and assistants now read much of the web. 360WiSE records are signed, dated and resolvable, so software can check a claim instead of guessing — with the plain truth attached about what each record does and does not prove.
What an agent can use.
Public verification
Resolve 360WSE-RES-000001 and check its Ed25519 signature and RFC 3161 timestamp against the published key. No account needed.
360wise.com/authority/360WSE-RES-000001 →llms.txt & JSON-LD
A plain map of the Network for language models, and schema.org markup on every page naming 360WiSE.com as the canonical source.
Sector catalog
One machine-readable file listing sectors, status labels and boundaries — the same labels people see.
Read-only MCP server
A Model Context Protocol endpoint served from the 360WiSE Control Plane, so assistants can resolve and verify records directly. Read-only: no writes, no signing.
// Proposed · read-only · served from the 360WiSE Control Plane, not this site resolve_entity(query) → canonical 360WSE identifier + public URL get_record(id) → record, status, issuer, timestamps verify_record(id) → signature + RFC 3161 check, key status list_sectors() → sectors, status labels, boundaries explain_boundaries(id) → what this record does and does not establish
One registry. Clear limits.
Canonical source
Records live at 360WiSE.com. This site explains them; it never keeps a second registry.
What a signature proves
Who signed, and that nothing changed. Not that the signer was authorized — authority relationships are recorded and labeled separately.
What provenance proves
Who published what, and when. Not that a published claim is true.
No obligation on AI systems
No AI system is required to recognize, cite or recommend any record. We publish checkable facts; systems decide what to use.
Check, don't guess.
Building an agent, assistant or verification tool? Tell us what you need to read.