This section is the public standards hub inside the Aegora site. It now brings together the current committee pack, the core draft, the schema package, the AI runtime guidance note, the starter kit shape, additional reference packages, and the emerging committee model.
The Execution Provider Framework adds four governed binding protocols: Native execution (default), A2A, vendor APIs, and MCP. A2A is preferred when supported, never mandatory. Tenant bindings preserve COR, explicit decisions, governance and outcome evidence.
Start with the committee pack or core draft for the standard itself, then move into the schema package, AI runtime guidance, starter kit, and reference packages to see the format reused across domains.
Preserve COR, decisions, governance and outcome evidence across Native, A2A, vendor API and MCP execution bindings.
Status: Opt-in execution-provider.v1alpha1 draft extension to core v0.3.1; bounded installed adapters, live tenant acceptance pending.
Read detail pageThe curated public-facing release bundle for the current Operating Specification draft, including the Word specification, schema package, AI runtime policy brief, TypeScript action annex, and upgraded reference operating paths.
Status: Current committee review pack for external circulation and standards discussion.
Read detail pageThe current core standard draft in Word form, covering runtime interpretation, conformance matrix, action-definition model, AI runtime policy, and committee-grade normative structure.
Status: Current canonical public draft for the Operating Specification Standard.
Read detail pageThe machine-validatable JSON Schema package aligned to the current standard, including controlled values, bounded action semantics, and AI runtime policy structure.
Status: Current schema package aligned to the committee draft.
Read detail pageA short committee brief that explains when a path should use `local_model_first`, `policy_routed_hybrid`, or a stricter high-risk hybrid posture for AI runtime participation.
Status: Current guidance note aligned to the v0.3.1 draft and reference paths.
Read detail pageThe public draft that explains the package model, conformance expectations, validator responsibilities, runtime requirements, and committee direction for the Operating Specification Standard.
Status: Draft revised for builder usability and external implementation.
Read detail pageThe first practical package for external builders. It includes a real schema, a real Operating Path, semantic, rules, and validation artifacts, plus example signals and validator guidance.
Status: Draft starter package with real repository-backed artifacts.
Read detail pageA second public reference package that proves the same path format works outside the original vulnerability-governance example and can validate cleanly in another domain.
Status: Lightweight reference package with validated primary path and schema.
Read detail pageThe lightweight operating model for evolving the standard in public: steering group, technical working group, governance and assurance review, and ecosystem advisory input.
Status: Initial stewardship model defined in the builder draft.
Read detail pageThe standards hub is meant to help a builder move in sequence: understand the standard, download the package, validate the path, and then map it into governed runtime behavior.
The public standard is meant to be downloaded, validated, adapted, and run. The visual below makes that artifact model explicit for first-time builders.
Use the standard hub to understand the package model, then move into examples, authoring, validation, and runtime import.