The catalog assigns 5 packages to this responsibility boundary. This page derives its vocabulary, topology, publication state, and maturity profile directly from those audited records.
Counts expose what the catalog actually contains. They do not convert package metadata into production-readiness or quality claims.
7 package-specific limitation entries remain visible across this domain.
17 unique capability statements are attached to packages in this domain. The language below is catalog evidence, preserved without expanding the claim.
load and validate configuration
redact sensitive fields
plan atomic config application
versioned wire-visible artifacts
shared IDs, reports, schemas, and draft/final forms
duplicate-type prevention
append JSONL receipt records
persist canonical schemas without redefining semantics
label AiDENs-owned reports
generate canonical JSON Schemas
verify committed schemas
cover the supported contract lane
internal release tooling
opaque ID newtypes
scope partition keys
W3C-compatible trace context
canonical BLAKE3 content digests
Edges are derived from sibling dependency declarations. Cross-domain traffic describes manifest topology, not runtime call direction, frequency, or activation.
Each record has a stable URL with its complete catalog scope, capabilities, targets, features, relationships, registry evidence, update trail, and known limits.
Configuration loading, validation, redaction, and atomic apply planning.
Versioned shared wire contracts and artifact shapes for AiDENs.
Thin JSONL persistence wiring for canonical receipts and clearly labeled AiDENs reports.
Canonical JSON Schema generator and committed-schema verifier for supported contract surfaces.
Shared identity, scope, and trace primitives for the local-first AI systems stack
This route reorganizes audited package metadata. It does not add implementation claims or expose access-controlled source.
p32-schema-compat / 011027f77fc7a53c6ecb05300d5c34144370fa3b