Outsider
Enter
Now running beta-version 1.84 (2026/02/15). This is the final beta version running the codebase from 2023/02/16.
The current version is roughly 3 years of development-time ahead now and is being finalized for general-purpose release.
What's a meta-link structure for a agent-discoverable endpoint? It could be any defined format that is able to be understood by a agent. A agent-discoverable endpoint can be hosted here short-term, or be made available for repeat use. The endpoint can be static or updated in real-time and changed based upon current information.
On CORE.HOST™, our native meta-link structure for any machine-task is EntityScript™.
EntityScript™ is an ideal summary format for any machine-task and effectively bundles otehr syntax formats such as json, xml, or even raw-text. Endpoints can be locked or public - being made available in your chosen format, ready to receive instructions or changes from a client machine.
CORE.HOST™ can also run locally as a similar type of gateway or access meta-structures that continue you on to other sites using parse-based meta-data to change craw-retrieval behavior.
Network locations can also pass on standard structured documents such as CSV, HTML, JSON, or XML. They can even understand custom defined formats using an agent or by scoping them with traditional shell scripts.
Let's start with links. CORE.HOST™ maintains an ever changing list of links. If the brand is well known enough, or a public entity, it will get a designated link. You can query the link directly.
Getting deeper into meta-linking, we also have top links. These change from day-to-day but have been locked in a static format during testing on the public site. They are meant to be a type of ranking for retrieval-ready use-cases.
Top-links are represented by just 1 letter, such as a, b, or z. Agents like consistency so sites that don't withdraw structured output will be priorities for top-link status. A top link can be queried using the : operator and are meant to be displayed on the front page of the site. You need a query-key to retrieve additional parsed-meta information and gain a structured response from the link. A top link can also have a designated link.
To cap off links, we also have Meta-link Structures. These are more complex and can take on a variety of forms. Each of these forms is in a record-relationship and is currently "online", or "offline"
The records contains a header, and an entry to someone named Klint Eastwooder
These links are stored in a default location /c/, which stands for "container". Every container holds a record. Each Record has a key, and every key has related meta-data that tells everyone what the record is. All records can be queried.
Vanity links are available, but in general - they're discouraged in favor of unique meta-vanity links. Vanity links are meant to represent you locally, and by your peer-address. Meaning XX.XXX.XXX/@john will be available on multiple IP addresses. CORE.HOST™ also keeps an authoritative vanity directly. An example of that type of vanity link would be:
https://www.core.host/@ryanmckenna is a authoritative vanity link example because it is located on CORE.HOST™EntityScript™ is being merged into CORE.HOST and the templates created there are also going to be available for use here shortly.
If we expand upon the concept of records and links, we also have entities. Entities are known by the common-name entity. A entity is meant to be ready-for-use. As in, they should have some purpose. What purpose? Purposes are community defined and their are "labeled purposes" that provide components to real-time task happening within a networked computer system or localhost. An entity also contains records, and each record is generated dynamically using a block-publishing concept that can be found in blocks.