Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -648,3 +648,9 @@ hosted service.
Task-authority/delegation and reader-safe summaries are available in Sidecar.
See [compatibility and ownership boundaries](docs/sidecar-0.9.md). Existing
native decisions/correlation stay compatible; no new normative schema is claimed.

## AIOS v0.6 examples and extension guidance

See [AIOS v0.6 compatibility](docs/aios-v0.6.md) for canonical examples,
namespace rules and native contract boundaries. AIOS artifacts remain
`0.4-draft`; no runtime dependency bump or package release is required.
Comment on lines +652 to +656

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Synchronize the org profile with the AIOS v0.6 story

This section introduces AIOS v0.6 as a new public ecosystem release story, but the change only updates this repository. Without the corresponding .github/profile/README.md and, where relevant, profile/ROADMAP.md updates, the organization-level documentation will continue presenting stale compatibility information; coordinate those profile changes with this documentation update.

AGENTS.md reference: AGENTS.md:L158-L160

Useful? React with 👍 / 👎.

6 changes: 6 additions & 0 deletions ROADMAP.md
Original file line number Diff line number Diff line change
Expand Up @@ -823,3 +823,9 @@ hosted service.
Task-authority/delegation and reader-safe summaries are available in Sidecar.
See [compatibility and ownership boundaries](docs/sidecar-0.9.md). Existing
native decisions/correlation stay compatible; no new normative schema is claimed.

## AIOS v0.6 examples and extension guidance

See [AIOS v0.6 compatibility](docs/aios-v0.6.md) for canonical examples,
namespace rules and native contract boundaries. AIOS artifacts remain
`0.4-draft`; no runtime dependency bump or package release is required.
26 changes: 26 additions & 0 deletions docs/aios-v0.6.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,26 @@
# AIOS v0.6 compatibility

AI Operations Specification repository v0.6.0 delivers the exploratory
[canonical examples and extension model](https://github.com/DeepAgentLabs/ai-operations-spec/tree/v0.6.0/specification/v0.6).
Comment on lines +3 to +4

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Resolved by release ordering: AIOS PR #31 has merged and v0.6.0 is now published, including both referenced documents. This documentation PR will merge after that release. No second review requested.

Artifacts still declare `spec_version: "0.4-draft"`; the existing schemas,
conformance rules and compatibility catalog are unchanged. Independent review
remains pending; the repository release does not establish stable conformance.

Continue routing by artifact spec_version through the existing compatibility catalog. The newest specification directory is not a schema version. Unified reports remain MCP-local.

## Dependencies and examples

No runtime dependency floor changes or package patch release is needed for this
documentation alignment. The AIOS layer adds no Python runtime API.

To inspect the canonical artifacts, check out AIOS `v0.6.0`, run
`uv sync --extra dev` and `make check` there, then read
`specification/v0.6/examples/manifest.json`. It distinguishes valid fixtures
from schema-invalid and semantic-invalid controls. These checks need no sibling
package and do not constitute independent implementation evidence.

Producer metadata belongs only in permitted `attributes` or reverse-domain
`extensions` entries; it cannot redefine core vocabulary. Consumers that
re-emit an artifact must preserve unknown extension JSON values. Extension
contract validation is separate from core validation. A namespace does not
certify the payload, safety, authority or successful execution.
Loading