Operating Specification Starter Kit
The 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.
Audience: Developers, integration engineers, and teams evaluating how to author or import packages.
Status: Draft starter package with real repository-backed artifacts.
Included artifacts
The starter kit is designed to be inspectable and immediately reusable. It demonstrates how a public package should be structured when published outside Aegora.
- Primary Operating Path artifact
- Primary schema
- Semantic model
- Rules artifact
- Validation artifact
- Demo manifest and sample signals
- Quickstart, compatibility, and validator docs
Recommended package layout
A downloadable Operating Package should have a stable shape so validators, registries, and runtimes can all reason about the same artifact model.
operating-package/
README.md
package.yaml
schema/
operating-path.schema.json
paths/
critical-vulnerability-governance.yaml
semantic/
critical-vulnerability.semantic.json
rules/
critical-vulnerability.rules.json
validation/
critical-vulnerability.validation.json
examples/
sample-signals/
sample-outcomes/
docs/
quickstart.md
compatibility.mdMake the artifact model visible.
The standard becomes easier to trust when builders can see the package shape and the motion from download to governed execution.
Use the public standard to shape governed runtime behavior.
The point of the standard is not documentation for its own sake. It is to make packages authorable, reviewable, validatable, and portable enough to drive governed execution.