Skip to content

Release 0.9.0

Choose a tag to compare

View all tags
@cdcavell cdcavell released this 24 Aug 19:21
· 97 commits to main since this release
v0.9.0
afe291e
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Version 0.9.0 substantially expands the Architecture learning surface with a new series of practical comparisons showing how governed execution relates to established authorization, infrastructure, workflow, policy, agent, audit, and application-architecture patterns.

The central theme of this release is architectural boundary clarity: use the smallest mechanism that correctly represents the authority, trust, lifecycle, and execution boundary the application actually needs.

Highlights

Seven New Architecture Comparisons

This release adds seven substantial Alternative Pattern articles:

  • Role-Based, Claims-Based, and Capability-Based Authorization

    • Separates standing authority from scoped continuation authority.
    • Explains when ordinary roles or claims are sufficient and when short-lived capabilities provide a clearer execution boundary.

  • API Gateways, Service Meshes, Zero Trust, and Governed Execution

    • Distinguishes transport controls, workload identity, zero-trust verification, application policy, and execution ownership.
    • Shows how these layers can complement rather than replace one another.

  • Workflow Engines, Human Approval Systems, and Governed Execution

    • Separates orchestration, approval, acknowledgment, governance decisions, and execution authority.
    • Includes AI-originated actions requiring acknowledgment, policy evaluation, and narrowly scoped host-owned execution authority.

  • Policy Engines, Rules Engines, and Distributed Policy Enforcement

    • Distinguishes domain rules, policy decision points, policy enforcement points, and broader governance lifecycle responsibilities.
    • Covers policy distribution, freshness, caching, degraded operation, revocation, and distributed enforcement.

  • Agent and Tool Authorization Models and Host-Owned Execution

    • Examines tool registration, model-visible tools, authorization, capability-scoped execution, credentials, and execution ownership.

    • Reinforces the core boundary:

    The model may propose. The host retains execution authority.

  • Event Sourcing, Audit Trails, and Governance Decision Provenance

    • Separates operational logging, traditional audit history, event-sourced state, and governance decision evidence.
    • Explains why an event log does not automatically provide governance provenance—and why durable decision evidence does not require event sourcing.

  • CQRS, Command/Query Separation, and Governed Execution

    • Shows where command handlers naturally serve as execution boundaries and where additional governance separation is justified.
    • Covers delayed execution, scoped authority, retries, idempotency, concurrency, and mediator pipelines.

Together, these additions bring the Architecture roadmap to nine published alternative-pattern comparisons.

Architectural Guidance

Across the new material, v0.9.0 reinforces several recurring principles:

  • Canonical does not mean universal.
  • Prefer ordinary authorization, workflow, infrastructure, or application patterns when they already satisfy the requirement.
  • Introduce a separate governance boundary only when it protects a real distinction in policy ownership, authority, acknowledgment, delay, provenance, or execution.
  • Authentication is not approval.
  • Approval is not automatically transferable execution authority.
  • Infrastructure identity and transport security are not substitutes for application-level policy decisions.
  • Durable governance evidence and application state history are different concerns.
  • AI and agent frameworks may propose actions, but consequential side effects remain owned by the host execution boundary.

Navigation and Cross-References

Architecture, Governance, and AI Integration navigation have been expanded to make the new comparisons easier to discover and to connect them with the existing Learning material.

ROADMAP.md has also been updated as each Alternative Pattern topic was completed.

Learning Brand Refresh

Version 0.9.0 also strengthens the repository's visual identity:

  • Adds the established Learning social image to the repository README.
  • Replaces the site icon with a Learning-specific connected-node/open-book design.
  • Adds a matching multi-resolution favicon.
  • Adds a dedicated 1280×640 GitHub social-preview asset.

These changes distinguish Learning visually from the main ASI Backbone repository while keeping the broader organization identity consistent.

Release Metadata

  • Updates CITATION.cff to version 0.9.0.
  • Sets the citation release date to 2026-08-24.
  • Updates .zenodo.json to version 0.9.0.
  • Keeps GitHub citation and Zenodo archival metadata synchronized.

Scope

This release is primarily an architecture education and documentation release. It does not introduce runtime changes to ASI Backbone packages or alter the behavior of executable Learning samples.

Upgrade Notes

No migration or compatibility work is required.

Users of v0.8.0 can move directly to v0.9.0 and use the expanded Architecture material as additional guidance for selecting, composing, or deliberately avoiding governance boundaries in real systems.

Assets 2
Loading