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™

System Audits

Audit Tags

System Audits can be as simple or custom as you need. They can replace the need for traditional introspection tools if designed into your extensions properly.

A Use this tag when logging a generic audit block

E Use this tag when logging an `event` block as described in the standard EntityScript™ library

S Use this tag when logging a `search` block

P Use this tag when logging and identifying a parsed behavior

K Use this tag when logging and identifying a new `main` or `active` function call

System Audits: Extended file auto-checks

The main .CORE/ directory performs very little. It does however perform audit_home checks. Essentially, it looks for a status queue. If the queue exists the system starts and stays running. If it doesn't exist it can start but won't run.

.audit_home/STATUS.X will tell the operator and the machine upon startup that the system and all tracked/known files from the last session are still there and in working order. The goal is to take anything that makes this hit to '.ERROR' and to isolate it for later processing.

This folder will produce the following file if everything is okay:

produce in-> .CORE/


If there was a syncing error or startup problem, the following will be true.



You can check out more about generating manual scripting-based processes and extending system audits with packages available through the implementation language: Scripting