AsiBackbone API Terminology Map
This page maps the terminology taught in ASI Backbone Learning to the concrete AsiBackbone.* product surface.
For canonical educational definitions, use the ASI Backbone Learning Architecture Glossary. For terminology lineage and comparisons with ABAC, least privilege, authorization, provenance, workflow, reference-monitor patterns, and AI tool calling, use Terminology and Established Architecture Concepts.
This repository does not maintain a second organization-level teaching glossary.
Important
AsiBackbone/AsiBackbone is authoritative for exact package IDs, namespaces, public types, members, defaults, reason codes, runtime semantics, security posture, provider behavior, compatibility, and releases. Learning is authoritative for architecture teaching and terminology lineage.
Authority boundary
| Question | Canonical source |
|---|---|
| What does this architecture term mean for teaching and comparison? | ASI Backbone Learning |
| Which established concept is it related to? | ASI Backbone Learning |
| Which package or type implements it today? | AsiBackbone product documentation and API reference |
| What exact outcomes, fields, defaults, or runtime invariants exist? | AsiBackbone product documentation and source |
| Does a Learning sample redefine a released API contract? | No |
| Can a product page redefine the organization-level teaching vocabulary independently? | No; product pages should map the concept to implementation semantics. |
Learning concept to product surface
| Learning concept | Concrete AsiBackbone realization | Primary package / reference | Implementation note |
|---|---|---|---|
| Policy decision pipeline | Composition of constraints, evaluator, decision, audit, acknowledgment/capability surfaces, and host execution boundaries | AsiBackbone.Core; Policy Evaluator Pipeline |
“Governance spine” remains architectural positioning, not a required implementation term or public type. |
| Intent / request | Proposed operation data carried into evaluation | GovernanceEvaluationContext |
No universal Intent base type is required. |
| Policy context | Host-supplied evaluation facts | IGovernanceEvaluationContext |
Host integrations remain responsible for authoritative identity/resource/context data. |
| Constraint | Independently evaluated product rule | IGovernanceConstraint<TContext> |
Constraint evaluation is separated from side-effect execution. |
| Policy evaluation | Constraint composition into a governance decision | IGovernancePolicyEvaluator<TContext> |
Evaluator output is decision data, not execution. |
| Decision outcome | Product decision plus enum outcome | GovernanceDecision, GovernanceDecisionOutcome |
Product includes the Warning outcome in addition to the foundational Learning set. |
| Acknowledgment | Confirmation plus host challenge integration | AcknowledgmentRequest, AcknowledgmentResponse |
The retained API names describe the multi-step request/response protocol; documentation does not claim legal protection. |
| Decision receipt | Structured product decision evidence | DecisionReceipt |
Storage and integrity guarantees depend on the configured host/provider path. |
| Decision provenance | Correlated decision, audit, acknowledgment, capability, lifecycle, and execution records | Audit/lifecycle/outbox APIs | Provenance is a relationship across records, not one universal type. |
| Scoped capability | Bounded grant plus validation | CapabilityGrant, CapabilityGrantValidator |
The implementation uses a grant/token vocabulary; scope and validation semantics matter more than token format. |
| Host-owned execution | Application or gateway performs the real side effect | Host-Owned Execution Enforcement | Core intentionally does not own a universal executor. |
| Operational gateway | Host mediation before an external tool/API/device/workflow side effect | AI Agent Gateway Scenario | Pattern-level mapping; no mandatory universal gateway base type. |
| Policy version | Readable policy generation | GovernanceDecision.PolicyVersion |
Version is a label, not exact content identity. |
| Policy fingerprint | Effective-policy fingerprint | GovernanceDecision.PolicyHash |
Current product property name is PolicyHash. |
| Correlation | Request/decision/audit linkage | GovernanceHttpRequestCorrelation and Core record fields |
Correlation is diagnostic/provenance metadata, not authority. |
| Outbox | Durable pending records for reliable governance-event delivery | AsiBackbone.EntityFrameworkCore integration and outbox guides |
GovernanceOutbox* API names identify the specialized records; production persistence and concurrency semantics are product-owned. |
| Governance emission | Projection to downstream observability or governance systems | AsiBackbone.OpenTelemetry and provider boundaries |
Emission is optional and should not replace required local audit/outbox handling. |
| Signing / verification | Product signing-ready records and configured signing providers | AsiBackbone.Signing.LocalDevelopment, AsiBackbone.Signing.ManagedKey |
Key custody, verification policy, and production trust remain host responsibilities. |
Decision-outcome mapping
Learning commonly teaches the core workflow with five outcomes. The released product currently has six:
| Learning workflow term | Current product enum |
|---|---|
| Allow | GovernanceDecisionOutcome.Allowed |
| Deny | GovernanceDecisionOutcome.Denied |
| Defer | GovernanceDecisionOutcome.Deferred |
| Require acknowledgment | GovernanceDecisionOutcome.AcknowledgmentRequired |
| Escalate | GovernanceDecisionOutcome.EscalationRecommended |
| Product-specific continuation-with-warning state | GovernanceDecisionOutcome.Warning |
The presence of Warning is an implementation fact. It does not require Learning to expand every foundational teaching example to six states.
Package ownership map
| Need | Product package / documentation |
|---|---|
| Framework-neutral policy decisions, constraints, audit primitives, acknowledgment, and capability grants | AsiBackbone.Core |
| Registration and package-family composition | AsiBackbone.DependencyInjection |
| ASP.NET Core request correlation, endpoint metadata, result mapping, and acknowledgment challenge seams | AsiBackbone.AspNetCore |
| Local sample/test audit storage | AsiBackbone.Storage.InMemory |
| Host-owned EF Core persistence and outbox integration | AsiBackbone.EntityFrameworkCore |
| Provider-neutral governance emission through .NET diagnostics | AsiBackbone.OpenTelemetry |
| Development signing proof paths | AsiBackbone.Signing.LocalDevelopment |
| Managed-key signing adapter boundary | AsiBackbone.Signing.ManagedKey |
| Static-analysis guidance | AsiBackbone.Analyzers |
Product-specific distinctions
These distinctions are enforced by the product documentation even when Learning explains the broader architecture:
GovernanceDecisionis a policy result; it does not perform the side effect.OperationResultreports package operation success/failure and is not a governance outcome.AcknowledgmentResponserecords acknowledgment and does not override authorization.CapabilityGrantrepresents bounded authority but still requires execution-boundary validation.DecisionReceiptdoes not promise durable, immutable, signed, or tamper-evident storage by itself.GovernanceDecision.PolicyVersionandGovernanceDecision.PolicyHashare separate fields.- Host-owned execution and operational gateway are architectural relationships rather than one required class hierarchy.
Reading path
For architecture learning, continue in Learning:
For implementation work, continue here: