Draft 1.01:

Sections: Status -> Approved

1.) EntityScript™ Overview - Overview of the project

2.) .entity/.ds Lookups - Overview of basic .entity and .ds file relationships. An overview of each file.

3.) Special File Types - Overview of special types of methods, files, and types in C.ORE™

4.) Log File Types - Overview of Logging within C.ORE™

5.) Using OpenPackager™ - Overview of the OpenPackager™ project and details regarding using the sub-system for organizing the base system and addons.

6.) Locations - Overview of various parts of the IPDVC™ file system

7.) System Audits - Overview of various audit mechanisms present in C.ORE™ and how to use them.

8.) C.ORE™ Scripts - Overview of scripts that run in C.ORE™, the purpose they have, overview of some scripting philosophy, and some usage examples.

9.) Startup - Step-by-step process of startup routines and how to extend them

10.) C.ORE™: AirEP™ file system (Access Identity Ring Entertainment Platform: AirEP™ - Understand more about the Access, Identity, Ring

11.) Keys: Each of the built-in keys that can be used to retrieve meta-information in C.ORE™

12.) How-to: Additional Notes

13.) Moderation: Basic moderation principles

14.) Social Pledge: Basic social-pledge for your interface and who you interact with

15.) Disclaimers: Basic recommendations for your interface and dealing with various types of commerce

16.) Additional Resources: Dig deeper into the technical stack, program methods, variables, and other happenings within CORE.HOST™



This holds documentation in HTML index pages.

It also contains documentation for any allowed programming language or extension on the system. This includes the documentation for EntityScript™

Replace with your desired path location


Each allowed programming language that can function inside of C.ORE™ Any language you choose to allow can also have the documented for it stored here. Plain HTML/Index form is preferred for package distribution and documentation.


This has the evolution of the IPDVC™ development. It will be updated over the years to show how the system came together.


The RING handles 5 elements of the system that together comprise the total range of control methods available to the operator. They are the following:

sub-Location: /RING/BACKUP/ for storing binary method-driven backups of your /ENTITY directory and one master .gz archive in a location of your choosing.

sub-Location: /RING/DOCUMENTS/ for storing documents in a .ds format that can be incorporated into forms for user input or into other documents as a general component later on. Essentially it provides a template library for other common component tasks like "music theory component" would contain a .ds document formatted to be used to re-discover some music theory information that is stored. All documents are meant to be used later on. A 'document' in general should go in ORE/. The preset template types are A.) PROCESSES, B.) AGREEMENTS, C.) TEMPLATES, D.) BACKGROUND and E.) INFORMATION. This summarizes the available standardized templates for specific user or machine-generated tasks.

sub-Location: /RING/ENTITY/ the default structure for storing .entity to .ds file relationships inside of CORE.HOST™

sub-Location: /RING/PROGRAMS/ allows you to extend the use of your system without installing anything into the 'root' position of your underlying machine. The default installation comes with the system program environment set, and AIREP™ (ACCESS, IDENTITY, RING, ENTERTAINMENT PLATFORM) and COLLECTIONS. AIREP™ runs new programs safely or not at all. This is done by using thread protections on the underlying system when possible. COLLECTIONS allows you to store code-like concepts as a work journal and run riskier stuff but it's unable to be directly linked into the main AIREP™ thread, thus missing out on certain log functionality.

sub-Location: /RING/VAULT_CODE/ holds encrypted entities in the 'MEMORY_FORM' that can be unlocked either by access methods later on. If you're using some specific method, you would be responsible for maintaining your own system keys for those files. A physical two step if you will.

Configuration mapping

You can find the following configuration files in .CORE/CONFIG/ and modify each according to your needs. A brief description of what each file does is also provided.

ID location configuration description
1 archive.ini Set archive values
2 browsemeh.ini Set up visual resources
3 config.ini Standard program variables
4 core.ini Standard system variables
5 design_basics.ini Basic output strings to aid with text-mode visual output
6 eventlolli.ini Create event-driven notifications, alerts, and audio visual routines
7 gatekeeper.ini Define access control values
8 interface.ini Set available interface and system variables
9 lockerlinks.ini Set location resources for your machine
10 network.ini Configure network values
11 openpackager.ini Authenticate and enforce meta-check behavior
12 remindme.ini Build time-based variable pools
13 ring.ini Set program enforcement values
14 special.ini Create reusable special resources
15 testing.ini Define testing variables
16 VCN.ini Create a key-based authentication mechanism
17 XYZObjects.ini Set visual parameters

These locations benefit from consistent System Audits and logging. More about System Audits can be found HERE