Agent protocol spec
The ./agentpacks family owns portable agentpack declarations and deterministic generation-trace and AI-audit receipt validation. Original digest, integration SHA, changed-path, redaction and Connect evidence checks remain intact. Legacy ContractSpec paths forward the same schema and function identities. These validators do not generate guidance, approve changes or execute agent tools.
Provider-neutral durable help/uncertainty/escalation/common protocol definitions extracted unchanged from ContractSpec compatibility. Root, help and common are intentional public groups; evidence-pointer is a shared private closure file. The package uses Zod and its declared Foundation model dependencies.
The ./agent/constants, ./acp/constants and ./agent/graph-conversation
leaves own the existing vocabulary and readonly conversation records. SchemaModel-based agent and ACP declarations, task execution and explicit registry registration live in AI Agent so their schema supplier does not enter this package's strict model closure. Compatibility imports retain canonical singleton identities and existing readonly types.
This pure platform-spec owns complete existing strict wire/inferred models and deterministic structural, expiry, scope, evidence-binding and DAG checks. It does not execute agents, dispatch providers, make/cache live authorization decisions, register products, sign approvals or promote learning changes. Existing step review/improvement/policy validators remain with their owners. Skills and protocol records do not grant authority.
Old ContractSpec leaves forward to these schema/type singletons. Preserve every field, brand, optionality, message/refinement and default; qualify frozen schemas/types, old/new identity and real communication/AI-agent/agent-host fixture behavior plus actual packed boundaries. Focused source tests alone are not integration or release acceptance.
The ./runtime-adapters leaf owns the complete original four adapter identities, eleven capability identities and diagnostic contracts. Tuple literals and readonly diagnostic evidence references remain exact; historical runtime-adapter imports forward to this same source. These declarations perform no runtime adapter execution, capability admission or authority decision.
The complete existing portable agent specification and protocol closure lives in ./agent/spec, ./context/agent-context and the protocol leaves. This includes planning, execution records, budget bounds, delegation and task graphs, memory proposal/governance records, application/signature contracts and model route, selection/fallback binding validators. All original schema wire shapes, brands, refinements, default values, inferred types and readonly namespace modifiers remain intact. Structural validators consume supplied records and never issue authority, call providers, execute tools, persist memory or promote learning. Original compatibility paths preserve their complete existing public signatures. The V2 canonical validation APIs require an explicitly supplied Date. The original optional-now convenience and lazy ambient clock remain in the AI runtime owner through typed validation phases; full issue order and getter read timing must remain unchanged. AgentSpec remains the complete original model split into private knowledge, policy and tool declaration helpers; KnowledgeCategory comes from its genuine Core contract owner. Existing runtime-adapter identities remain the separately qualified complete family; this cut does not duplicate them. The two original model-routing test-fixture leaves retain their historical public intent; no scaffold or narrower DTO replaces the existing model bodies. Clean producers, NodeNext/Bundler declarations, readonly namespace parity, original tests and affected AI/Host/Communication consumers remain mandatory.
The original V2 plan and operation binding helper bodies live in a private module to preserve the package file-size bound; its export is null and the catalog excludes it. This adds no public family or narrower replacement.
@lssm-tech/lib.agent-protocol-spec/agent-platform and ./agent-platform/<leaf>
(baseline-suites, digest, types, validation, validation-v2) own the provider-neutral agent platform plan declarations and their pure structural validation. Legacy @lssm-tech/lib.contracts-spec/agent-platform imports forward to the same instances.
Agentic interaction vocabulary
The agentic-interaction subpath owns the portable blocked-signal tuple and deny-only AIP mapping; agentic-interaction/constants owns their metadata vocabulary. They contain supplied static declarations without runtime authorization or registration. Schema-based query/capability contracts and registration helpers live in ai-agent/agentic-interaction. Communication consumes this narrow vocabulary without an AI runtime dependency. The ./context/agent-context-validation leaf owns deterministic projection, required-context and compaction validation alongside the canonical context models. Legacy context validation imports preserve the same functions and diagnostics.
The /protocol/model-routing-migration entry owns the existing deterministic V1-to-V2 migration plan. It parses supplied models and reports required requalification bindings; it grants no execution or qualification authority.
The /protocol/markdown-migration entry also exports
agentMarkdownMigrationMaterialV1Schema, the strict host-supplied input for
createAgentMarkdownMigrationArchiveV1. Hosts parse untrusted archive material with it instead of re-declaring the field rules.
The /protocol/application-lifecycle entry owns the application installation state machine (install_disabled -> configured -> qualified -> active, with
paused, revoked and uninstalled), its frozen transition table, the revision-CAS store port type and the exact-key record and move validators. Persistence adapters implement the port; hosts keep activation authority.
The /protocol/application-qualification entry owns the digest-bound application qualification record (agentApplicationQualificationV1Schema, policy bindings), the qualification port and materialized-application types, and the configuration/qualification digest materials.
/protocol/application-qualification-validation holds the pure checks:
parseAgentApplicationArtifactsV1 (manifest and permission-summary digests and matching ref sets) and validateAgentApplicationQualificationV1 (sorted issue codes for signature, time, identity, artifact, policy, digest and lifecycle bindings). Hosts keep the bounded lifecycle reads and the verification port.
