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™


core_graphics is meant to operate as a backend/frontend operator.

The Frontend can be deployed in something like JavaScript. In this case, we'll call that script XYZObjects.js. XYZObjects will give you the following:

There is one part of the frontend that is for traditional browsers and is in a preview stage currently. It's called New Entity™ and you can find it at https://NewEntity.io

The other default/provided _FRONTEND implementation runs on a lower level and is able to be locked down as a solid 1-demensional state on your machine. It's fairly simple and allows for interfacing with most of the other scripts in some way. There are also a couple of special frontend features available too. A special license is needed to view this part of the software at this stage, but we'll eventually be releasing most things under an appropriate open source license. Talks are on about what the best way to do that is. The link to the lower level library provided with the default package is core_FRONTEND and there will be more details about it soon.

XYZObjects.js has three parts.

The first is a 'canvasMain'. This instance provides a background for the frame.

The second is a 'inceptionObject', that provides a frame to be used as an overlay to the main frame, or subsequently stacked frames.

The third is a 'pointObject'. This instance provides a scalable point to be used as an overlay to the main frame, or subsequently stacked frames.

When you start to move the elements around you can see how powerful each abstraction of cubes and shapes could become if you continued onward, but the point is a very limited and basic set of elements to start.

There is also emulated 3D graphics in 2D space. Here, we can draw lines, or connect faces together to form shapes. If you wanted to spend a lot of time... you could also connect points and lines.


Each pixel on screen can be mapped into a coordinate system in many lower-level system graphics extensions. The purpose of this project isn't to provide thos, but to enable ways of implementing one or many of them at the same time in both a low-level interface and a default/traditional interface for browsers. Typically, in a web browser these pixels will take up roughly 4 bytes of data per pixel but the ideas of grouping them can be fairly simple. You're able to augment pixels before they arrive using a backend or as they arrive using something to manipulate them as they're loaded. This backend could technically format pixels with a GPU instead of rendering them as pixel values and then amplifying them to meet a screen size. This would reduce pixel quality.

Copyright (C) 2020 New Entity Operations Inc.


core_graphics gives basic X,Y,Z coordinate systems for use within C.ORE

matrix_setup = 100
# Setup a compositor object with set X, Y, Z values that can be
# searched for an located depending on programatic need
x = []
y = []
z = []

for i in range(matrix_setup):
    Setup function that takes the empty lists x, y, z and sets them up
    with the matrix_setup number 'standard is 100'

# Setup the Matrix based off of the standard matrix_setup
print('----- X-AXIS -----')
print('----- Y-AXIS -----')
print('----- Z-AXIS -----')

## X, Y, Z Graph
#             (Z)
#              |
#              |
#              |
#              |
#              |
#              |
#              |
#              |
#              |__
#              /_ /|____________________________(x)
#             |__|/
#            /
#           /
#          /
#         /
#        /
#       /
#      /
#     /
#(y) /
# Pin the InceptionBlock to the axix between X, Y, Z is set here
pin = x[0],y[0],z[0]

# Setup the X, Y, Z demensions of the block in standard input form
# Block Lengths X, Y, Z
scope = (1, 1, 1)

# Suface Colors
# [F]
# [A][B][C][D]
# [E]
A = 'black'
B = 'black'
C = 'black'
D = 'black'
E = 'black'
F = 'black'

# Setup the Empty FillInceptionBlock object to put visual form
# to a Binary type object
FillInceptionBlock = []

def fill():
    Fill the InceptionBlock with the colors defined based off of the
    A-E graph specifications

def clear_block():
    Clear the fill color of the InceptionBlock

# Block Altering Turns
# FORWARD: A becomes F
max_forward = 3

# BACKWARD: A becomes E
max_backward = 3

# LEFT: A becomes D
max_left = 3

# RIGHT: A becomes B
max_right = 3

# Confirm the pin location

# clear_block()
# Render the visual version of the Matrix-defined points