e.g.

    "@extends": {
        "vortex.default": "/pinf.genesis/01-genesis.pinf.org/.pgs/vortex.default/*.proto.json"
    },

https://github.com/gocircuit/circuit

https://github.com/gruntjs/grunt-cli/tree/master/completion

Port the bash and nodejs logic require to boot to Rust. Use NodeJS only where needed.

Once this is done, port the Rust logic to Pure JavaScript and an adapter for NodeJS.

• Preserve line order (i.e. object property indexes)
• Allow multi-line strings with auto-pad-stripping
• Use @context to define properties & schema (json-ld based)
• Use @extends to pull in outside descriptors
• Use @translocate to copy config sections from other descriptors into same place in this descriptor

Something creates an etc folder at the root of the project. Stop this from happening. Likely need to set home dir of some command call to a different path?

For now install pinf.genesis using a submodule. Once sm.genesis is working we can publish npm package.

Use http://json-ld.org/ to model the pinf-it normalized descriptors:

• e.g. https://github.com/pinf-it/pinf-it-package-insight/blob/master/test/assets/descriptors/npm/q.package.insight.json#L84
• e.g. https://github.com/pinf-it/pinf-it-program-insight/blob/master/test/assets/descriptors/boot-package.program.insight.json#L14

cc @kriskowal I am going to try and use JSON-LD to hold configs in the virtual system and write converters to and from this format. It should be trivial to integrate the JSON-LD model into the layered filesystem and feed properties on the prototype chain of an object. I am going to explore some minimal extensions to JSON-LD + JSON-SCHEMA that will add support for mapping to JS code bundles that can be executed when processing schemas or when data passes through it ... This will be the foundation of the meta system that maps in every aspect used within a given context and can attach tooling components to API responses.

None of these words communicate. I suspect each of them would require a paragraph of explanation.

Perhaps you mean:

Tool(s) for sharing software development workflows that involve flexible dependency management and the orchestration of virtual machines.

Create github.com/pinf/pg.expand in the like of pg.condense and use in genesis.pinf.org.

This will make the expansion process modular and runnable from outside using pg.expand which will not only run sm.expand but also resolve configurations and setup the system ready for booting using boot or other referenced bootstrapper.

PINF.Genesis being an implementation of some logical primitives that are highly applicable to many problems; the terminology used to describe PINF.Genesis must be as applicable as possible.

i.e. The terminology must be consumable by many audiences allowing them to apply the concepts and implementation to many problems as easily as possible.

i.e. The terminology must be IMMEDIATELY COMPREHENSIBLE.

All docs must only use specific terms to describe what something is and what it does and NEVER USE GENERAL TERMS.

Generality for a specific domain is presented ONLY IN SYSTEMS built using PINF.Genesis! The first such system acting as the first reference implementation is https://github.com/devcomp/devcomp.org

$context: #4