Theme: Reliance & Boundaries — what a principal can rely on an AGET to provide at a release, and where an always-on node's artifacts live, both made checkable.
Added
- R-BND-001 — Boundary & Reliance Requirements (
specs/requirements/): a cross-boundary reliance is a principal-owned, externally-verifiable requirement with a single source of truth — version-pinned, verified meets-declared-minimum (not parity-to-template), drift-detectable. - Skill-reliance manifest framework feature: a release-pinned
{S}core /{O}optional /{D}domain reliance contract any AGET can declare and self-check — governed schema + generic validator. - AGET_HOST_RUNTIME_SPEC v1.0.0: host-runtime filesystem-layout standard (lifecycle-class separation, record/exhaust tier boundary, bounded-growth rotation, deployed-copy decoupling). Conformance checks activate at first node deployment (ADR-007 honest-testability).
Notes
Theme framed honestly as advanced, not fulfilled — the reliance and boundary contracts land; friction-handling triage and host-node deployment continue in following cycles.