Draft 1.2:

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 and ask him.

ID name of meta-structure type of component description of structure
meta-structureOrigin directory structure
MS-2ACCESS/meta-structureHolds security slugs generated on startup and your default key files
MS-3ACTION/meta-structureHolds extensions through the extension_pool and allows you define enforced linkers to limit or enhance program processes.
MS-4BACKUP/meta-structureHolds 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-5COGNITIVEOREmeta-structurePersonal Record of Last Resort Ledger
MS-6CONFIG/meta-structureHolds configuration files needed to operate various parts of the system
MS-7DATA/meta-structureHolds event-data of various types
MS-8db/meta-structuredatabase protocol expander, allowing you to tie in any database and make it a generic factory within your application.
MS-9design/meta-structureHolds design related instances and allows you to style various interfaces provided by TRINE™
MS-10DOCUMENTATION/meta-structureHolds basic documentation for the system and various interfacing languages
MS-11event/meta-structureHold event-specific logic, such as time modules, atomic-sync stores, and more.
MS-12FILTER/meta-structureHolds single use explorer entities and filter code for various public processes such as web browsing
MS-13flag/meta-structureHolds argument flag dictionaries for the program.
MS-14HARDWARE/meta-structureHolds the basic system hardware specs needed by C.ORE
MS-15IDENTITY/meta-structureHolds operator specific system data
MS-16image/meta-structureHolds 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-17INSTANCE/meta-structureHolds structures having to do with providing a stateful instance to the operator, including the state, system status, and links to outside stateful parties.
MS-18internal_process_audit/meta-structureHolds testing facilities and cli-based test silos required for system and program process auditing.
MS-19KEYS/meta-structureHolds KEY data types and operators to generate and distribute KEYS to system programs and to peers.
MS-20LICENSE/meta-structureHolds licenses in use on the System
MS-21LOG/meta-structureHolds *.log data in the *.es format that is generated by defined process behavior within the application runtime.
MS-22LOGIC/meta-structureLogical operators and behaviors to allow for generic system behaviors.
MS-23MODE/meta-structureProvide settings of various modes, and allow for generic, complex, or AI driven debugging of your instance.
MS-24OPENPACKAGER/meta-structureHolds OpenPackager related data, including both internal, external, and corehost program types
MS-25parsermeta-structureExtend the program with specialty parsers, or use the generic provided entity parser.
MS-26presetmeta-structureInternal state-dependent instance presets. There are over 600 configurable presets.
MS-27RING/meta-structureHolds formatted personal data
MS-28temple/meta-structureA 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.
meta-structureVirtual-environment Holds the virtual environment setup code
MS-30corehost/meta-structureHolds programs and scripts derived from CORE.HOST
MS-31external/meta-structureHolds programs and scripts derived externally through other code repository sites
MS-32internal/meta-structureHolds 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
P1all_packagespartThe exact packages running within the virtual environment at this time
P2build_listpartThe general packages running within the virtual environment at this time
P3core_addpartcore_add is a module to make, create, alter, and reseed both 'LOCAL', 'SYSTEM', and 'GLOBAL' communication attributes, including 'logs of last resort'.
P4core_alertspartcore_alerts is a module to establish alert markers and related behavior
P5core_architectpartcore_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.
partbuild reads system resources and makes determinations about build states or system-discovery choices made by the operator.
P7core_configpartcore_config allows you to turn certain system modules on or off at setup
P8core_countpartcore_count counts entries in your core.es quick context-file and checks to see if the system is currently counting time
P9core_creatorpartcore_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
partcore_FRONTEND holds human-to-machine interaction code in a user-defined interface: This has been refactored into TRINE
P11core_gatekeeperpartcore_gatekeeper handles default authentication tasks and will permit or kick members according to set definitions
P12core_gatherpartcore_gather gives the operator methods for locating .entity/.ds relationships with dlist_drill()
P13core_graphicspartcore_graphics gives basic X, Y, Z coordinate systems for use within C.ORE
P14core_hashpartcore_hash provides setup routines that can be extended into useful communication methods in C.ORE
P15core_interfacepartcore_interface is the call logic to system interaction scripts and other 'system resources' such as audio, visual, or bus programs
P16core_languagepartcore_language can serve as a language check script and enforcement mechanism.
P17core_middlelayerpartcore_middlelayer lets you extend your core_settings file into manageable write protected sections
P18core_modifypartcore_modify allows you to perform basic read/write operations in C.ORE
P19core_navigatorpartcore_navigator lets you connect your interface into various parts of the underlying machine
P20core_openpackagerpartcore_openpackager manages package meta-data and system package inspections
P21core_operationspartcore_operations is the default helper stack for C.ORE containing useful classes and methods
P22core_RUNpartTie a system routine to the C.ORE activation method
P23core_seekerpartcore_seeker gives a basic seek system for text-mode
partcore_server manages your personal server instance: This has been deprecated in favor of a reengineered multi-threaded RTC-server: TRINE-RTC Server
partcore_settings is the default configurations reader and read/write configurations slug_maker: Settings and configurations are now stored in the meta-structure MODE/
P26core_START_SERVERpartTie startup routines to the server startup instance method
P27core_transmitterpartcore_transmitter takes I/O tasks and turns them into phase based threads
partcore_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
P29core_viewpartcore_view allows you to view various objects in C.ORE
P30MANIFESTpartFile add manifest
P31setuppartSetup the program and view base package meta-data. Setuptools built scripts are provided through .toml, and alt-builds are provided through a .cfg
P32ResourcePoolpartCreate local resource pools
P33StandardOutput01partCreate a input processor fork
P34StandardVisualBuild02partCreate interface components as fork-able objects
P35StandardExtension03partCreate package meta-structures as fork-able objects
P36StandardDocumentViewer04partCreate a document-viewing standard that can be added on to allow for various desired formats
P37op_BROWSEMEHpartView system visual resources
P38op_EVENTLOLLIpartAd serving and interactive display writer
P39op_REMINDMEpartTime-keeping mechanism for C.ORE
P40constructed_classpartTo build compliant meta-structures
P41fetch_OREpartTo retrieve Operations Resource Enclaves existing within the system
P42ingest_commandspartTo retrieve Operations Resource Enclaves existing within the system

Back to the library