Library: code
Each source code release will be available for download at the following link:
- Version 1
Right now, the build is in the "ALPHA" or "CONCEPTUAL" branch. The exact nature of each module is explained, but due to pre-release reasons, not fully detailed.
This is all preparing for a "BETA" or the "FUNCTIONAL" branch. This branch will be distributed to the public under the "New Entity License". The details of this license aren't disclosed yet, so for now - this license is proprietary, but it will be amended soon to be slightly more permissive, and the terms of the updated license can be reviewed at that date. Until then, this is a preview library.
Various scripts and meta-structures can be linked into the program. This is the full preview-list and the content of nested directory structures is not provided. Some of the meta-structures branch into even deeper functional-structures.
Property Table
The default script start position is .CORE/CORE and it can be setup as a basic reader and writer of start/stop data by default. This start/stop methodology can be extended to include any automated setup routine, and behavior is built out accordingly.
Everything else is bound by independent parts. Some parts are required, while others are optional. Each part can be turned off or on. This guide doesn't explain why each part can be turned off or on, or what the reasoning behind that is.
There are two types of structure described here. The first is known as a "part" and represents a single instance of code running either as a part of some other program-unit, or as a stand alone program somewhere else inside of the instance. The other structure is called a "meta-structure" and represents a single contained resource point that can contain 0, 1, or many additional parts and meta-structures. A meta-structure can present as a directory, but it is not always a directory. Sometimes a meta-structure may also be a file or even a network location.
*NOTE*: Any script that has a 2020 copyright date is not engineered. These scripts are for conceptual completeness only. With this being true, each 2020 script should be noted as a functional baseline only. This does not make them final "functional" program components. Scripts from version 0.0.8 and above are considered functional and engineered, but still are not considered a public-ready branch. Version 0.0.8 is the last preview draft of the code before it will be released as a 0.0.9 public-beta under the New Entity License. These scripts will be able to be used in a production environment, although some of the scripts and structures may not be fit for all purposes until they go through public revisions.
All 2020 parts are in the process of being updated. Most of them have been upgraded from the initial release (Version 0.0.4) all the way to the next release, 0.0.8. By June 1st 2023, all of the updated parts and meta-structures will be in the current preview version: 0.0.8 (ALPHA). The initial draft, "EntityScript" and the source-code draft "C.ORE" were produced spontaneously and through natural drafting, and were not intended to be used in production. Both drafts were created without the use of spell-check software or any robotic helpers so if you encounter formatting errors or spelling issues, remember that those versions were written out by hand. EntityScript™ has since been updated to the current version, 1.2 on 2023/03/11. You can follow along with updated drafts in the changelog
Lastly, 0.0.5 code is mostly conceptual as well. This code has since been refactored in additional ways, but some of the updates may lag behind the main branch by a few weeks as they're checked for consistency.
C.ORE™ components published: 74/314 (23%)
To gain access to the remaining 77% of C.ORE™, reach out to Ryan McKenna (Personal Website Contact) and ask him.
| ID |
name of meta-structure |
type of component |
description of structure |
| MS-1 | .CORE/
TRINE/ | meta-structure | Origin directory structure |
| MS-2 | ACCESS/ | meta-structure | Holds security slugs generated on startup and your default key files |
| MS-3 | ACTION/ | meta-structure | Holds extensions through the extension_pool and allows you define enforced linkers to limit or enhance program processes. |
| MS-4 | BACKUP/ | meta-structure | Holds compliant backup structures generated from the instance. You can provide a network hook to export backups through this folder to a network-based storage provided solution. |
| MS-5 | COGNITIVEORE | meta-structure | Personal Record of Last Resort Ledger |
| MS-6 | CONFIG/ | meta-structure | Holds configuration files needed to operate various parts of the system |
| MS-7 | DATA/ | meta-structure | Holds event-data of various types |
| MS-8 | db/ | meta-structure | database protocol expander, allowing you to tie in any database and make it a generic factory within your application. |
| MS-9 | design/ | meta-structure | Holds design related instances and allows you to style various interfaces provided by TRINE™ |
| MS-10 | DOCUMENTATION/ | meta-structure | Holds basic documentation for the system and various interfacing languages |
| MS-11 | event/ | meta-structure | Hold event-specific logic, such as time modules, atomic-sync stores, and more. |
| MS-12 | FILTER/ | meta-structure | Holds single use explorer entities and filter code for various public processes such as web browsing |
| MS-13 | flag/ | meta-structure | Holds argument flag dictionaries for the program. |
| MS-14 | HARDWARE/ | meta-structure | Holds the basic system hardware specs needed by C.ORE |
| MS-15 | IDENTITY/ | meta-structure | Holds operator specific system data |
| MS-16 | image/ | meta-structure | Holds compliant interface-images such as the instance logo, operator photos, and other type-enforced image types that can be genreated with the interface at runtime. |
| MS-17 | INSTANCE/ | meta-structure | Holds structures having to do with providing a stateful instance to the operator, including the state, system status, and links to outside stateful parties. |
| MS-18 | internal_process_audit/ | meta-structure | Holds testing facilities and cli-based test silos required for system and program process auditing. |
| MS-19 | KEYS/ | meta-structure | Holds KEY data types and operators to generate and distribute KEYS to system programs and to peers. |
| MS-20 | LICENSE/ | meta-structure | Holds licenses in use on the System |
| MS-21 | LOG/ | meta-structure | Holds *.log data in the *.es format that is generated by defined process behavior within the application runtime. |
| MS-22 | LOGIC/ | meta-structure | Logical operators and behaviors to allow for generic system behaviors. |
| MS-23 | MODE/ | meta-structure | Provide settings of various modes, and allow for generic, complex, or AI driven debugging of your instance. |
| MS-24 | OPENPACKAGER/ | meta-structure | Holds OpenPackager related data, including both internal, external, and corehost program types |
| MS-25 | parser | meta-structure | Extend the program with specialty parsers, or use the generic provided entity parser. |
| MS-26 | preset | meta-structure | Internal state-dependent instance presets. There are over 600 configurable presets. |
| MS-27 | RING/ | meta-structure | Holds formatted personal data |
| MS-28 | temple/ | meta-structure | A personal high-quality dynamic website and blogging platform that allows for media display, user-modes, chatting, content downloads, subscriptions, and more. This is a standalone product too. |
| MS-29 | core-env/
trine-env | meta-structure | Virtual-environment Holds the virtual environment setup code |
| MS-30 | corehost/ | meta-structure | Holds programs and scripts derived from CORE.HOST |
| MS-31 | external/ | meta-structure | Holds programs and scripts derived externally through other code repository sites |
| MS-32 | internal/ | meta-structure | Holds programs derived as standards within the system |
These parts aren't the completed list. As of now - the other parts are considered to be confidential. Any part within the following meta-structure isn't disclosed, as they too are confidential: ACTION/, db/, design/, event/, flag/, image/, INSTANCE/, instance_process_audit/, KEYS/, LOG/, LOGIC/, MODE/, parser/, preset/, and temple/.
| ID |
name of part |
type of component |
description of part |
| P1 | all_packages | part | The exact packages running within the virtual environment at this time |
| P2 | build_list | part | The general packages running within the virtual environment at this time |
| P3 | core_add | part | core_add is a module to make, create, alter, and reseed both 'LOCAL', 'SYSTEM', and 'GLOBAL' communication attributes, including 'logs of last resort'. |
| P4 | core_alerts | part | core_alerts is a module to establish alert markers and related behavior |
| P5 | core_architect | part | core_architect is a module to establish a handlers for various digital groupings. You can either account for those groupings or use them to make quantified/qualifying output according to base example methods. |
| P6 | core_build
build | part | build reads system resources and makes determinations about build states or system-discovery choices made by the operator. |
| P7 | core_config | part | core_config allows you to turn certain system modules on or off at setup |
| P8 | core_count | part | core_count counts entries in your core.es quick context-file and checks to see if the system is currently counting time |
| P9 | core_creator | part | core_creator allows you to create a .entity/.ds relationship in text-mode and system routines for modules running within C.ORE that rely on add/edit/delete methodology |
| P10 | core_FRONTEND
Deprecated | part | core_FRONTEND holds human-to-machine interaction code in a user-defined interface: This has been refactored into TRINE |
| P11 | core_gatekeeper | part | core_gatekeeper handles default authentication tasks and will permit or kick members according to set definitions |
| P12 | core_gather | part | core_gather gives the operator methods for locating .entity/.ds relationships with dlist_drill() |
| P13 | core_graphics | part | core_graphics gives basic X, Y, Z coordinate systems for use within C.ORE |
| P14 | core_hash | part | core_hash provides setup routines that can be extended into useful communication methods in C.ORE |
| P15 | core_interface | part | core_interface is the call logic to system interaction scripts and other 'system resources' such as audio, visual, or bus programs |
| P16 | core_language | part | core_language can serve as a language check script and enforcement mechanism. |
| P17 | core_middlelayer | part | core_middlelayer lets you extend your core_settings file into manageable write protected sections |
| P18 | core_modify | part | core_modify allows you to perform basic read/write operations in C.ORE |
| P19 | core_navigator | part | core_navigator lets you connect your interface into various parts of the underlying machine |
| P20 | core_openpackager | part | core_openpackager manages package meta-data and system package inspections |
| P21 | core_operations | part | core_operations is the default helper stack for C.ORE containing useful classes and methods |
| P22 | core_RUN | part | Tie a system routine to the C.ORE activation method |
| P23 | core_seeker | part | core_seeker gives a basic seek system for text-mode |
| P24 | core_server
Deprecated | part | core_server manages your personal server instance: This has been deprecated in favor of a reengineered multi-threaded RTC-server: TRINE-RTC Server |
| P25 | core_settings
Deprecated | part | core_settings is the default configurations reader and read/write configurations slug_maker: Settings and configurations are now stored in the meta-structure MODE/ |
| P26 | core_START_SERVER | part | Tie startup routines to the server startup instance method |
| P27 | core_transmitter | part | core_transmitter takes I/O tasks and turns them into phase based threads |
| P28 | core_url
Deprecated | part | core_url holds retrieval methods for URL interactions as well as other network based operations for get/post/and connect methods. The script was expanded and now includes automation and stateful searches, so it has been renamed to "rig". Deprecated core_url module |
| P29 | core_view | part | core_view allows you to view various objects in C.ORE |
| P30 | MANIFEST | part | File add manifest |
| P31 | setup | part | Setup the program and view base package meta-data. Setuptools built scripts are provided through .toml, and alt-builds are provided through a .cfg |
| P32 | ResourcePool | part | Create local resource pools |
| P33 | StandardOutput01 | part | Create a input processor fork |
| P34 | StandardVisualBuild02 | part | Create interface components as fork-able objects |
| P35 | StandardExtension03 | part | Create package meta-structures as fork-able objects |
| P36 | StandardDocumentViewer04 | part | Create a document-viewing standard that can be added on to allow for various desired formats |
| P37 | op_BROWSEMEH | part | View system visual resources |
| P38 | op_EVENTLOLLI | part | Ad serving and interactive display writer |
| P39 | op_REMINDME | part | Time-keeping mechanism for C.ORE |
| P40 | constructed_class | part | To build compliant meta-structures |
| P41 | fetch_ORE | part | To retrieve Operations Resource Enclaves existing within the system |
| P42 | ingest_commands | part | To retrieve Operations Resource Enclaves existing within the system |
Back to the library
