VAB and Genesis

Role

VAB is a boot orchestrator and conversational Surface, not another runtime and not necessarily the permanent assistant after boot. Its task is to turn first intent into an inspectable proposal, secure assent to the exact declarative plan, and invoke runtime-owned creation paths.

Current path

The repository implements conversation sessions, cognitive state composition, heuristic fallback and configured model invocation, streaming output, speech affordances, extension selection, Founding Actor admission, restart reconciliation and a web boot Surface. A boot plan carries an assentedPlanHash; changing the plan after assent invalidates the seal.

The working sequence is:

conversation → interpreted needs → graph and extension proposal
→ explicit assent seal → governed creation → living System Surface

Internal E2E validation continues from a born System to .vast export, fresh import and stable package identity.

Founding Actor

The Founding Actor is the first admitted human identity for the born System. This does not make the Actor universally omnipotent. Credentials, session admission, capabilities and graph governance remain separate runtime checks.

Genesis versus implementation

Genesis names the governed birth of a useful System. Electronic Artefacts Genesis would additionally require organizational root data, governance, registries, operational Surfaces, durable recovery and an approved handover into a candidate Environment. The repository provides important pieces but does not yet demonstrate that complete operational loop.

Remaining thresholds

• durable and reviewable provisioning across failures;
• explicit rollback and recovery behavior;
• local credential and authority rebinding after import;
• security review of model, extension and package trust boundaries;
• one real EA graph operated, exported, revalidated and handed over without authority bypass.