The following words & phrased are used in the Gordian architecture. Also see Gordian Architexture Roles.
- Airgap. A Partition between two Services such that they are not Networked on the same network. (Often, at least one Service is not Networked at all). See Airgap (Wikpedia).
- Animated QRs. An animation of a QR made up of several frames. Used for transmitting data larger than the max possible with Quick Response (QR) Codes. See Animated QRs.
- ByteWords. An Encoding Specification that represents binary data as English words. Used in the by Blockchain Commons specifications primarily to represent CBOR in URs. See ByteWords.
- CBOR. A Data Format: it represents data in a binary format. See RFC 8949.
- Closely Held Device. A hardware device such as a phone or a hardware wallet that is privately held by an individual, that has a small attack surface due to careful and consistent sandboxing, and that is not constantly Networked in the way that a full computer tends to be.
- Collaborative Key Management (CKM). A Seed Recovery Service for the collaborative generation and usage of keys. See CKM.
- Collaborative Seed Recovery (CSR). A Seed Recovery Service to improve Resilience by storing Shares of keys or seeds that are created by Sharding. See CSR.
- Data Format. A Specification for a structure to store data. See Data Formats.
- Encoding. A conversion of data into a specific form. See Encoding (Techopedia).
- Encoding Specification. A Specification for Encoding. See Data Formats.
- Envelope. A communication Specification for a Smart Document that supports the storage, backup, encryption & authentication of data, with explicit support for Merkle-based selective disclosure. See Envelope.
- Functional Partition. The philosophy of separating different functions as different parts of an interoperable ecosystem, and also dividing data up into different locations, all to improve Resilience. This is done with Partitions and could include Airgaps or Torgaps.
- Gordian Architecture. A suggested design for a data-asset ecosystem that supports the Gordian Principles. It’s built upon a foundational idea of Functional Partition. See Gordian Architecture.
- Gordian Principles. Four fundamental precepts at the heart of
the Blockchain Commons’ work: Independence, Privacy, Resilience,
and Openness. See Gordian Principles.
- Independence. The ability to work in a self-sovereign way without centralization. A Gordian Principle.
- Privacy. Protection of personal data and usage against correlation and censorship. A Gordian Principle.
- Resilience. The ability to prevent loss of assets or data, including resilience against theft and resilience against accidental loss. A Gordian Principle.
- Openness. Interoperability of systems and easy portability of data. A Gordian Principle.
- Lifehash. A UX Design that creates a visual hash as part of an OIB to allow for visual identification of data. See Lifehash.
- Microservice. A Service that provides a capability which is very specific and/or infrequently used. See Gordian Architecture.
- Networked. Directly connected to an online network.
- Object Identity Block (OIB). A UX Design for an array of data that can together allow a user to easily and uniquely identify data. Can include a Lifehash. See OIB.
- Partition. A division between two or more Services. A partition could be as simple as ensuring those Services are on different machines, but can also include an Airgap or Torgap.
- Progressive Trust. The concept of gradually building trust over time. See Musings of a Trust Architect: Progressive Trust.
- Quick Connect. A Data Format for a URI or QR Code that can be used to securely connect together two devices that are separated by a Partition. See Quick Connect.
- Quick Response (QR) Code. An Encoding Specification that represents data in a graphical format. URs are built to allow for efficient encoding as a QR Code. With them, Gordian Animated QRs support animation of larger data sets using foundation codes. See QR Code (Wikipedia) & URs.
- Reference App. An application that shows an example of the usage of a Specification, usually built with a Reference Library. See Gordian Reference Apps.
- Reference Library. A library that provides an API for using a Specification. See Libraries.
- Seed Recovery. A method for recovering a seed that has been lost, thanks to proactive backups. Uses Sharding or other similar techniques. See Seed Recovery.
- Service. An application providing a specific capability as part of the Functional Partition of a digital-asset ecosystem. Includes Microservices.
- Share. A fraction of a seed or a key created by an algorithm such as Shamir’s Secret Sharing or VSS. Intended to improve Resilience of data and enable Seed Recovery. See SSKR.
- Sharding. The process of creating Shares from seeds or keys. See SSKR.
- SmartCustody. Documents, instructions, and Specifications intended to improve the Resilience of digital assets, either at the personal or the ecosystem level. See SmartCustody.
- Specification. A specific design intended to support communication, data, or backup Encoding and backup, to ensure the Openness of interoperability, to support UX Design, or to ensure other Gordian Principles. Part of the Gordian System. See Gordian Specifications in Blockchain Commons Research Repo and of course, the whole developer website.
- Torgap. A Partition between two Services, created to ensure that they are anonymous to each other. See Torgap.
- Uniform Resources (URs). An Encoding Specification of a URI for data. It is created by representating data as CBOR and then encoding it with minimal Bytewords. URs are also built to allow efficient Encoding as QR Codes. URs allow for interoperable communication. See URs.
- Uniform Resource Identifier (URI). A unique sequence for identifying a resource. A UR is a URI. See URI (Wikipedia).
- UX Design. A methodology for presenting data to a user. See UX Design.