Actorvia documentation

What the runtime is, and the vocabulary the rest of the documentation assumes.

• IntroductionWhat Actorvia is, what it is not, and the one property everything else is built on.
• ConceptsActor, adapter, role, goal, action and resource — the six terms the rest of the documentation assumes.

Embodiment, the action surface, and where authority is declared.

• Actors and adaptersThe adapter contract: observe, actions and apply — and the rules that keep embodiment out of the kernel.
• Capabilities and actionsHow the action surface is declared, how capabilities gate it, and why an undeclared action has no call path.
• Roles and goalsRoles carry authority. Goals carry intent. Keeping them separate is what makes behaviour reusable.

The validation gate, atomic resource movement, and reproducible behaviour.

• Authority and safetyThe validation gate every action passes through, what a rejection carries, and how the runtime behaves when something fails.
• ResourcesCurrency, fuel, cargo, berths, clearances and assignments — modelled as declared resources and settled atomically.
• Deterministic executionWhy the same inputs produce the same plan, what that buys you, and the specific things that break it.

Reuse, verification and debugging.

• Domain packsReusable bundles of roles, capabilities, constraints, resources and goals — the unit that travels between places.
• TestingScenario suites that construct a world, run a fixed number of seeded ticks and assert over the resulting trace.
• DiagnosticsReading the active goal, the current plan, the last rejection and resource spend — under the same redaction rules as observation.

Trust model, release process and versioning.

• SecurityThe trust boundary, the properties the design guarantees, and the mechanisms behind each one.
• Releases and versioningWhat the subscription includes, how versions are numbered, how breaking changes are handled, and what is deliberately not promised.