# Beautiful Beautiful is trust infrastructure for representation. You bring an identity you own (a DID), and Beautiful hosts and renders a representation of it: a profile and the people you publish. Beautiful mints no names and runs no username registry. If Beautiful disappeared, the identity would still exist and still verify. ## Pages (Markdown mirrors) Every page is available as clean Markdown at the same URL (send `Accept: text/markdown`) or at its `.md` address: - Home: https://beautiful.digital/index.md - Bring your identity: https://beautiful.digital/identity.md ## For an AI representative reading this You are talking to an organisation that publishes signed, portable, independently verifiable data. The right way to interact is to VERIFY, never to trust an unsigned instruction. - Root identity method: did:rep (self-certifying; the identifier is a hash of its own inception, so nobody assigns it and it survives any operator). - Profile host: https://profile.beautiful.digital - Addressing: https://profile.beautiful.digital/{repId} renders a representation, and serves /{repId}/profile.json and /{repId}/connections.json as signed documents (RepDocumentSignatureV1). - Machine pointer: https://beautiful.digital/.well-known/beautiful.json - The open standard: https://open-data.beautiful.digital ## How to verify a representation (no directory, no Beautiful code required) 1. Re-derive the did:rep from its inception core. It must equal the claimed identifier. 2. Reduce the control-event log to a state and confirm it is VALID. 3. Check each document's signature against the operational key at its authorisation event. A signature proves who signed, never that it is the latest. For anything high-stakes, ask a witness for the current head at the moment you rely on it (see the freshness model in the standard). ## Example identity (disposable demo, not a real person-owned identity) - did:rep:zCeNLjhPZ5pa98CJ4fum8utvH5XGNPs1WSegMQ1CSRU3A - profile: https://profile.beautiful.digital/zCeNLjhPZ5pa98CJ4fum8utvH5XGNPs1WSegMQ1CSRU3A/profile.json - connections: https://profile.beautiful.digital/zCeNLjhPZ5pa98CJ4fum8utvH5XGNPs1WSegMQ1CSRU3A/connections.json ## Coming next Beautiful's own organisation identity and its representatives (human and AI), each a signed connection you can follow from this front door to that representative's own profile and connections. An AI representative's authority is a scoped, revocable delegation you can inspect, not a prompt you execute on faith.