Expand description
ONT-4: the orchestration doors, in one implementation.
harness.v1.orchestration.load|save|compile|decompile|import|export and
supercode orchestration <verb> are two transports over the functions here, which
are themselves a thin wrapper over the ONT-3 codecs
(supercode_interchange::orchestration::codec). Nothing in this module decides
anything a codec does not: it picks the codec the caller named, keeps the
io bookkeeping a decompile needs, and shapes the answer for the wire.
One rule the wire adds: a vault VALUE never leaves. A load or a compile
answers with the vault’s KEY NAMES only — the caller that needs a value
reads the home’s own .env. That rule is why import and export exist
as verbs of their own: a migration moves credentials between homes, and
composed from the value-level verbs by a client it could not — the
credential would have to cross the wire. Here it stays in this process.
Structs§
- Orchestration
Decompiled - What a decompile did.
- Orchestration
Imported - What an import did: the orchestration as saved, the vault’s key names, and the unmodeled files carried by path.
- Orchestration
Read - What a load or a compile answers: the orchestration, and the vault’s key names.
- Orchestration
Saved - What a save answers.
- Refusal
Row - A refused write, on the wire.
Enums§
- Home
Flavor - Which layout a folder is read as (
harness.v1.orchestration.load’sflavor). - Orchestration
Harness - Which source harness an orchestration is compiled from or decompiled back to.
- Source
Flavor - What kind of home
decompile’ssourceis.
Functions§
- compile
harness.v1.orchestration.compile: read another harness’s home as one orchestration value.- decompile
harness.v1.orchestration.decompile: write an orchestration back as the source harness’s home.- export
harness.v1.orchestration.export: our folder becomes another harness’s home.- import
harness.v1.orchestration.import: another harness’s home becomes our folder.- load
harness.v1.orchestration.load: read a home folder as one orchestration value.- save
harness.v1.orchestration.save: write an orchestration into our own folder.