Skip to main content

Key Concepts

Subbasis vocabulary is intentionally stable. This page gives practical definitions and how they connect in execution.

Overview​

Use this page as a map before diving deeper sections.

Why it matters​

Most implementation mistakes come from mixing terms (for example, confusing workflow definition with workflow execution). Shared vocabulary improves architecture quality and team alignment.

Core concepts in plain language​

  • Runtime Core: deterministic distributed runtime for execution, coordination, and persistence.
  • Workflow: durable business execution flow.
  • Agent: governed participant with roles, skills, limits, and permissions.
  • Context Intelligence: operational state attached to workflow execution.
  • Evidence: reviewable execution records.
  • ACC: contract proposal for governed connector usage.
  • ARIN: local execution environment for sensitive or environment-dependent flows.

How they work together in Subbasis​

Typical chain:

  1. Workflow defines intent and progression.
  2. Runtime Core enforces deterministic execution boundaries.
  3. Agents perform role-bound tasks.
  4. ACC-governed connectors execute external actions.
  5. Context Intelligence preserves operational continuity.
  6. Evidence records reviewable outcomes.

Example scenario​

Client onboarding:

  • Workflow defines stages and gates.
  • Agent roles manage collection, validation, and communication.
  • Approval gate protects high-impact external actions.
  • Connector writes to internal systems.
  • Evidence supports handoff and review.

Read Runtime Core and Context Intelligence.