Skip to content

Enoch v0.5.0

Choose a tag to compare

@peking2 peking2 released this 31 Jul 09:14
279f6a6

Enoch v0.5.0

Enoch v0.5.0 makes Enoch an extensible application kernel for descendant
agents. A descendant can now compose its own identity, presentation, providers,
profile, extensions, authorization policy, and workflow while Enoch remains the
single owner of polling, recovery, task execution, publication, delivery, and
shutdown.

Highlights

  • Added the versioned ApplicationComposition API and run_application()
    launcher. Descendants configure bounded startup inputs without subclassing
    EnochApplication or taking ownership of its lifecycle.
  • Added descendant-owned identity loading and mutable identity paths. /mission,
    prompt memory, and persistent runtime sessions now use the composed identity,
    and mission updates survive process restarts.
  • Added application-level presentation, provider, profile, extension,
    authorization, and workflow selection with explicit precedence and
    fail-before-polling validation.
  • Added ApplicationCompositionConformanceMixin and expanded the offline wheel
    E2E to exercise an independently packaged composition with provider, profile,
    extension, and fenced-workflow dependencies.
  • Added typed ExtensionCommandResult responses so extension commands can
    report success or failure, durable task identities, and structured metadata
    while remaining compatible with existing string responses.
  • Added extension-scoped task inspection, cancellation, retry, and approval
    controls without exposing the unrestricted core workflow engine.
  • Made explicit instance roots authoritative across CLI, storage, and
    application startup paths.
  • Validated the composition boundary with Noah as a real descendant: Noah
    injects its identity, presentation, providers, and required Manager extension
    through Enoch's public application API.

Validation

  • The 792-test Enoch body suite passes.
  • All 72 reference provider and library tests pass independently.
  • The Genesis cross-artifact gate creates and validates a fresh descendant from
    the v0.5.0 release candidate.
  • Noah's Enoch-backed launcher, Manager extension, installed wheel, and
    Genesis-to-Noah descendant gates pass against this release body.
  • GitHub Actions covers Python 3.11, 3.12, 3.13, and 3.14.

Compatibility

  • Python 3.11 or newer.
  • genesis.toml schema version 1.
  • Application Composition API version 1.
  • Agent Extension API version 1.
  • Extension Command Result API version 1.
  • Workflow API version 3.
  • Profile API version 5.
  • Provider-kit 0.7.0.
  • Genesis v0.2.0 or a later compatible build.
  • Existing Enoch launchers use the default composition and retain their current
    behavior.
  • Existing extension commands returning strings remain supported.
  • Extension packages and composition factories are trusted Python code rather
    than sandbox boundaries.
  • Durable task-event delivery remains at least once. Consumers must apply
    stable event IDs idempotently because a crash can occur after an extension
    changes its state but before Enoch records the success receipt.

Credentials, memories, logs, chat identifiers, task state, extension state,
and instance configuration remain outside both the public source archive and
the inheritable software body.