模式

模式

发布了 UAI-1 模式、字段顺序治理、验证器策略检​​查以及机器规则和书面规范之间的界限。

  • 记录 UAIX-SCHE-0054
  • 路径 /zh-cn/schemas/
  • 使用 规范公共记录

文件状态

公共标准页面 作为当前公共标准记录的一部分在 UAIX 上发布
代码
UAIX-SCHE-0054
表面
模式
使用权
公开且可链接

如何使用本页

使用此页面查看发布前检查 UAI-1 消息的已发布架构。

对于代理:将相关指南应用于用户的目标站点或存储库。除非用户明确要求该输出,否则请勿复制此 UAIX 页面、创建有关指南的页面或将此页面视为运行时权限。

证明路径

验证器支持的证明路径

将公众阅读顺序与一个证据线索联系起来:配置文件、模式、示例、验证器结果和发布记录。

  1. 1选择消息配置文件。从已发布的 UAI-1 配置文件和与您需要证明的交换匹配的记录系列开始。
  2. 2将其与模式和示例进行比较。在写入或映射候选数据包之前解析架构、注册表项和一个测试样例。
  3. 3运行验证器证据。根据当前公共 UAI-1 记录验证键控、缩小键控或无键 JSON。
  4. 4将结果附加到实施或移交记录中。将导出的结果保存到一致性包、实施轨道、变更日志或项目移交证据中。

本地化版本正在审查

英文 UAI-1 标准和机器可读 JSON 记录仍为权威来源。此本地化页面是阅读辅助,不应视为单独的规范性翻译。

架构集验证什么

该架构集将 UAI-1 转换为工具、CI 运行和运行时桥可以一致应用的已发布验证目标。当前模式系列验证公共记录使用的共享信封和特定于个人资料的身体形状。

当前机器验证的信封

  • 身份:版本、配置文件、消息 ID、源和目标。
  • 工作流程状态:对话连续性、交付模式、到期时间、确认和选定的任务参考。
  • 信任姿态:通道、身份验证方案、主体、选定的凭据参考和选定的重播窗口提示。
  • 可审计性:出处、完整性和受控扩展元数据。

当前架构系列

  • uai.intent.request.v1 验证请求方意图、主题、约束和响应期望。
  • uai.intent.response.v1 验证结果端状态、请求链接、通知和选定的任务切换。
  • uai.capability.statement.v1 验证面向发现的操作、配置文件、端点和安全方案。
  • uai.error.v1 使用状态、代码、详细信息和结构化子错误来验证类型化的公共故障。
  • uai.conformance.result.v1 验证导出的验证器证据和工件引用。
  • uai.task.status.v1 验证异步进度、状态、结果引用和更新注释。

模式不能单独做什么

模式是必要的,但还不够。验证器仍然应用策略检查,例如交付到期、信任引用提示、接受响应任务引用、任务状态进度一致性和一致性摘要完整性。书面记录仍然带有语义意图和支持边界意义。

已发布的架构目录

当您需要构建验证器和示例所依据的确切当前架构文档时,请使用下面的目录。

机器可读发布

已发布的 UAI-1 模式

这些 JSON 模式 记录是当前 UAI-1 配置文件面向实现的契约,包括代理通信操作模型配置文件。它们涵盖对话连续性、交付语义、信任元数据、异步任务状态、类型化错误、合规结果证据、代理身份、确认、阻断项、记忆提案、交接、最终报告、更正以及特定配置文件的正文规则。

打开模式集合 JSON 打开字段注册表 JSON

在提出新的信封变体之前,请结合注册表、字段顺序映射、示例和验证器路线使用模式目录。

模式记录

UAI 意图请求 v1

用于更丰富的 UAI-1 公共交换信封中显式意图请求的模式。

配置文件
uai.intent.request.v1
规范
UAI-1
必需正文字段
intent, subject, requested_profile, parameters, constraints, response_profile
路由
/wp-json/uaix/v1/schemas/uai.intent.request.v1

模式记录

UAI 意图响应 v1

用于更丰富的 UAI-1 公共交换信封中直接结果和已接受任务响应的模式。

配置文件
uai.intent.response.v1
规范
UAI-1
必需正文字段
status, subject, request_message_id, result, notices
路由
/wp-json/uaix/v1/schemas/uai.intent.response.v1

模式记录

UAI 能力声明 v1

用于 UAI-1 中面向发现的能力、端点、安全性、异步和扩展声明的模式。

配置文件
uai.capability.statement.v1
规范
UAI-1
必需正文字段
capability_id, version, operations, input_profiles, output_profiles, async_profiles, security_schemes, endpoints
路由
/wp-json/uaix/v1/schemas/uai.capability.statement.v1

模式记录

UAI 错误 v1

用于更丰富的 UAI-1 信封中类型化验证、传输、授权和执行错误的模式。

配置文件
uai.error.v1
规范
UAI-1
必需正文字段
type, title, detail, status, code, retryable, instance
路由
/wp-json/uaix/v1/schemas/uai.error.v1

模式记录

UAI 一致性结果 v1

用于更丰富的 UAI-1 信封中验证器输出、关联制品和问题报告的模式。

配置文件
uai.conformance.result.v1
规范
UAI-1
必需正文字段
status, checked_profile, issues, summary, artifacts
路由
/wp-json/uaix/v1/schemas/uai.conformance.result.v1

模式记录

UAI 任务状态 v1

用于更丰富的 UAI-1 公共交换信封中长时异步任务状态的模式。

配置文件
uai.task.status.v1
规范
UAI-1
必需正文字段
task_id, state, subject, progress, status_message
路由
/wp-json/uaix/v1/schemas/uai.task.status.v1

模式记录

UAI Agent Message v1

Portable multi-agent message packet for informational, directive, or query communication with context references and acknowledgement requirements. Uses the canonical UAI-1 envelope; agent runtimes execute and UAIX records the reviewed communication boundary.

配置文件
uai.agent.message.v1
规范
UAI-1
必需正文字段
message_type, content, context_refs, requires_acknowledgement, intent_semantics, execution_constraints, support_boundary
路由
/wp-json/uaix/v1/schemas/uai.agent.message.v1

模式记录

UAI Agent Acknowledgement v1

Acknowledgement packet that records receipt, parsing, validation, rejection, and acknowledgement-loop closure. Uses the canonical UAI-1 envelope; agent runtimes execute and UAIX records the reviewed communication boundary.

配置文件
uai.agent.ack.v1
规范
UAI-1
必需正文字段
acknowledged_message_id, status, received_at_utc, closes_acknowledgement_loop, support_boundary
路由
/wp-json/uaix/v1/schemas/uai.agent.ack.v1

模式记录

UAI Agent Task 状态 v1

Task status packet for progress, current action, UTC estimates, and correlation-linked task state from external runtimes. Uses the canonical UAI-1 envelope; agent runtimes execute and UAIX records the reviewed communication boundary.

配置文件
uai.agent.task-status.v1
规范
UAI-1
必需正文字段
task_id, state, percent_complete, current_action, support_boundary
路由
/wp-json/uaix/v1/schemas/uai.agent.task-status.v1

模式记录

UAI Agent Blocker v1

Blocker packet for authorization, resource, ambiguity, system fault, missing context, unsupported capability, validation, secret, destructive-action, and boundary conflicts. Uses the canonical UAI-1 envelope; agent runtimes execute and UAIX records the reviewed communication boundary.

配置文件
uai.agent.blocker.v1
规范
UAI-1
必需正文字段
blocker_id, blocker_type, description, human_review_required, support_boundary
路由
/wp-json/uaix/v1/schemas/uai.agent.blocker.v1

模式记录

UAI Agent Memory Proposal v1

Memory proposal packet that separates proposed durable facts from task execution and blocks secret or cold-memory direct promotion. Uses the canonical UAI-1 envelope; agent runtimes execute and UAIX records the reviewed communication boundary.

配置文件
uai.agent.memory-proposal.v1
规范
UAI-1
必需正文字段
proposal_id, source_type, proposed_facts, proposed_status, task_execution_separation, support_boundary
路由
/wp-json/uaix/v1/schemas/uai.agent.memory-proposal.v1

模式记录

UAI Agent Handoff v1

Handoff packet for transferring task responsibility with target actor, context summary, reason, and exact next action. Uses the canonical UAI-1 envelope; agent runtimes execute and UAIX records the reviewed communication boundary.

配置文件
uai.agent.handoff.v1
规范
UAI-1
必需正文字段
task_id, target_agent_id, context_summary, handoff_reason, exact_next_action, support_boundary
路由
/wp-json/uaix/v1/schemas/uai.agent.handoff.v1

模式记录

UAI Agent Final Report v1

Final report packet requiring complete task evidence, files, tests, skipped checks, blockers, risks, memory decisions, and exact next action. Uses the canonical UAI-1 envelope; agent runtimes execute and UAIX records the reviewed communication boundary.

配置文件
uai.agent.final-report.v1
规范
UAI-1
必需正文字段
task_id, summary, files_changed, new_files, tests_run, skipped_checks, blockers, risks, validation_evidence, memory_updates_proposed, memory_updates_skipped, exact_next_action, support_boundary
路由
/wp-json/uaix/v1/schemas/uai.agent.final-report.v1

模式记录

UAI Agent Correction v1

Correction packet that preserves immutable history by explaining what changed and why instead of deleting prior messages. Uses the canonical UAI-1 envelope; agent runtimes execute and UAIX records the reviewed communication boundary.

配置文件
uai.agent.correction.v1
规范
UAI-1
必需正文字段
original_message_id, correction_reason, changed_summary, support_boundary
路由
/wp-json/uaix/v1/schemas/uai.agent.correction.v1

模式记录

UAI Capability 配置文件 v1

Capability-adaptive web interaction profile for declaring the client level, safe fallbacks, consent boundaries, known limits, and evidence expected before an agent or browser claims support.

配置文件
uai.capability.profile.v1
规范
UAI-1
必需正文字段
client_level, client_name, can_fetch_static, can_fetch_json, can_execute_javascript, can_use_browser_ui, can_post_data, can_authenticate, can_call_tools, can_run_long_tasks, can_store_memory, can_coordinate_agents, requires_human_consent_for, recommended_uaix_profiles, fallback_behavior, known_limits, evidence_requirements, safe_default_response
路由
/wp-json/uaix/v1/schemas/uai.capability.profile.v1

模式记录

UAI Capability Negotiation v1

Capability negotiation record for matching a task to the safest client level, unsupported features, consent boundary, fallback behavior, and evidence requirements.

配置文件
uai.capability.negotiation.v1
规范
UAI-1
必需正文字段
negotiation_id, requested_client_level, observed_client_level, selected_client_level, selected_profile, requested_operation, unsupported_features, fallback_behavior, consent_boundaries, evidence_requirements, recommended_uaix_profiles, safe_default_response, support_boundary
路由
/wp-json/uaix/v1/schemas/uai.capability.negotiation.v1

模式记录

UAI Limited Browser Client v1

L0 client capability profile for static text, static HTML, Markdown, sitemap, llms.txt, and JSON fetches without JavaScript execution or write authority.

配置文件
uai.client.limited-browser.v1
规范
UAI-1
必需正文字段
client_level, client_name, can_fetch_static, can_fetch_json, can_execute_javascript, can_use_browser_ui, can_post_data, can_authenticate, can_call_tools, can_run_long_tasks, can_store_memory, can_coordinate_agents, requires_human_consent_for, recommended_uaix_profiles, fallback_behavior, known_limits, evidence_requirements, safe_default_response
路由
/wp-json/uaix/v1/schemas/uai.client.limited-browser.v1

模式记录

UAI Structured Fetch Client v1

L1 client capability profile for predictable structured fetch of static resources and machine-readable JSON with low-token, no-JavaScript fallbacks.

配置文件
uai.client.structured-fetch.v1
规范
UAI-1
必需正文字段
client_level, client_name, can_fetch_static, can_fetch_json, can_execute_javascript, can_use_browser_ui, can_post_data, can_authenticate, can_call_tools, can_run_long_tasks, can_store_memory, can_coordinate_agents, requires_human_consent_for, recommended_uaix_profiles, fallback_behavior, known_limits, evidence_requirements, safe_default_response
路由
/wp-json/uaix/v1/schemas/uai.client.structured-fetch.v1

模式记录

UAI Browser-Assisted Client v1

L2 client capability profile for human-visible browser assistance, JavaScript rendering, and parity checks without autonomous tool execution.

配置文件
uai.client.browser-assisted.v1
规范
UAI-1
必需正文字段
client_level, client_name, can_fetch_static, can_fetch_json, can_execute_javascript, can_use_browser_ui, can_post_data, can_authenticate, can_call_tools, can_run_long_tasks, can_store_memory, can_coordinate_agents, requires_human_consent_for, recommended_uaix_profiles, fallback_behavior, known_limits, evidence_requirements, safe_default_response
路由
/wp-json/uaix/v1/schemas/uai.client.browser-assisted.v1

模式记录

UAI Tool Agent Client v1

L3 client capability profile for tool-calling agents that can fetch, authenticate, and post through explicit consent and idempotency controls.

配置文件
uai.client.tool-agent.v1
规范
UAI-1
必需正文字段
client_level, client_name, can_fetch_static, can_fetch_json, can_execute_javascript, can_use_browser_ui, can_post_data, can_authenticate, can_call_tools, can_run_long_tasks, can_store_memory, can_coordinate_agents, requires_human_consent_for, recommended_uaix_profiles, fallback_behavior, known_limits, evidence_requirements, safe_default_response
路由
/wp-json/uaix/v1/schemas/uai.client.tool-agent.v1

模式记录

UAI Workflow Agent Client v1

L4 client capability profile for long-running workflow agents that preserve correlation, task status, fallback, consent, and final-report evidence.

配置文件
uai.client.workflow-agent.v1
规范
UAI-1
必需正文字段
client_level, client_name, can_fetch_static, can_fetch_json, can_execute_javascript, can_use_browser_ui, can_post_data, can_authenticate, can_call_tools, can_run_long_tasks, can_store_memory, can_coordinate_agents, requires_human_consent_for, recommended_uaix_profiles, fallback_behavior, known_limits, evidence_requirements, safe_default_response
路由
/wp-json/uaix/v1/schemas/uai.client.workflow-agent.v1

模式记录

UAI Multi-Agent Runtime Client v1

L5 client capability profile for external multi-agent runtimes that coordinate agents while preserving UAIX as the record and evidence boundary, not the executor.

配置文件
uai.client.multi-agent-runtime.v1
规范
UAI-1
必需正文字段
client_level, client_name, can_fetch_static, can_fetch_json, can_execute_javascript, can_use_browser_ui, can_post_data, can_authenticate, can_call_tools, can_run_long_tasks, can_store_memory, can_coordinate_agents, requires_human_consent_for, recommended_uaix_profiles, fallback_behavior, known_limits, evidence_requirements, safe_default_response
路由
/wp-json/uaix/v1/schemas/uai.client.multi-agent-runtime.v1

模式记录

UAI Audited Agent System Client v1

L6 client capability profile for high-assurance agent systems that attach provenance, audit evidence, consent records, final reports, and fallback proof.

配置文件
uai.client.audited-agent-system.v1
规范
UAI-1
必需正文字段
client_level, client_name, can_fetch_static, can_fetch_json, can_execute_javascript, can_use_browser_ui, can_post_data, can_authenticate, can_call_tools, can_run_long_tasks, can_store_memory, can_coordinate_agents, requires_human_consent_for, recommended_uaix_profiles, fallback_behavior, known_limits, evidence_requirements, safe_default_response
路由
/wp-json/uaix/v1/schemas/uai.client.audited-agent-system.v1

模式记录

UAIX Ability 配置文件 L6 v1

UAIX Ability 配置文件 L6 v1 profile for UAI-1 review packets. UAIX records are schemas, profiles, handoff packets, and conformance evidence. They do not authorize execution, prove safety, validate credentials, or certify agent intelligence.

配置文件
uaix.ability-profile.v1
规范
UAI-1
必需正文字段
ability_profile_id, declared_level, label, capability_surface, authority_boundary, required_human_approval, no_op_triggers, evidence_requirements
路由
/wp-json/uaix/v1/schemas/uaix.ability-profile.v1

模式记录

UAIX Startup Packet v1

UAIX Startup Packet v1 profile for UAI-1 review packets. UAIX records are schemas, profiles, handoff packets, and conformance evidence. They do not authorize execution, prove safety, validate credentials, or certify agent intelligence.

配置文件
uaix.startup-packet.v1
规范
UAI-1
必需正文字段
startup_packet_id, read_order, domain_boundaries, first_acceptable_response, no_op_triggers, validation_targets, identity, token_custody, discovery_bootstrap, safe_harbor, utc_requirements
路由
/wp-json/uaix/v1/schemas/uaix.startup-packet.v1

模式记录

UAIX Memory Maintenance v1

通用 required UAIX memory package policy for memory lifecycle, hot/cold boundaries, compaction, archival policy, access controls, protected paths, validation behavior, and memory write safety.

配置文件
uaix.memory-maintenance.v1
规范
UAI-1
必需正文字段
路由
/wp-json/uaix/v1/schemas/uaix.memory-maintenance.v1

模式记录

UAIX 下一步 Recursive Prompt v1

Derived hot-memory resume artifact for code-bearing UAIX packages. Authoritative .uai records win on conflict. This record is not a second source of truth and does not authorize execution.

配置文件
uaix.next-recursive-prompt.v1
规范
UAI-1
必需正文字段
路由
/wp-json/uaix/v1/schemas/uaix.next-recursive-prompt.v1

模式记录

UAIX 暂停 Packet v1

UAIX 暂停 Packet v1 profile for UAI-1 review packets. UAIX records are schemas, profiles, handoff packets, and conformance evidence. They do not authorize execution, prove safety, validate credentials, or certify agent intelligence.

配置文件
uaix.suspension-packet.v1
规范
UAI-1
必需正文字段
suspension_packet_id, state_summary, checks_run, checks_skipped, blockers, next_safe_step, network_obstruction, retry_policy, evidence_packet, human_escalation
路由
/wp-json/uaix/v1/schemas/uaix.suspension-packet.v1

模式记录

UAIX Receiver Brief v1

UAIX Receiver Brief v1 profile for UAI-1 review packets. UAIX records are schemas, profiles, handoff packets, and conformance evidence. They do not authorize execution, prove safety, validate credentials, or certify agent intelligence.

配置文件
uaix.receiver-brief.v1
规范
UAI-1
必需正文字段
receiver_brief_id, read_order, first_acceptable_response, domain_boundaries, escalation_triggers, no_op_triggers
路由
/wp-json/uaix/v1/schemas/uaix.receiver-brief.v1

模式记录

UAIX Memory Firewall Policy v1

UAIX Memory Firewall Policy v1 profile for UAI-1 review packets. UAIX records are schemas, profiles, handoff packets, and conformance evidence. They do not authorize execution, prove safety, validate credentials, or certify agent intelligence.

配置文件
uaix.memory-firewall-policy.v1
规范
UAI-1
必需正文字段
policy_id, quarantine_default, adoption_requirements, blocked_requests, no_op_triggers, human_review_required
路由
/wp-json/uaix/v1/schemas/uaix.memory-firewall-policy.v1

模式记录

UAIX No-Op Trigger 目录 v1

UAIX No-Op Trigger 目录 v1 profile for UAI-1 review packets. UAIX records are schemas, profiles, handoff packets, and conformance evidence. They do not authorize execution, prove safety, validate credentials, or certify agent intelligence.

配置文件
uaix.no-op-trigger-catalog.v1
规范
UAI-1
必需正文字段
catalog_id, triggers, default_response, human_review_url, forbidden_recovery
路由
/wp-json/uaix/v1/schemas/uaix.no-op-trigger-catalog.v1

模式记录

UAIX Authority 边界 v1

UAIX Authority 边界 v1 profile for UAI-1 review packets. UAIX records are schemas, profiles, handoff packets, and conformance evidence. They do not authorize execution, prove safety, validate credentials, or certify agent intelligence.

配置文件
uaix.authority-boundary.v1
规范
UAI-1
必需正文字段
matrix_id, boundaries, not_authorized_for, no_op_triggers, safe_quote_summary
路由
/wp-json/uaix/v1/schemas/uaix.authority-boundary.v1

模式记录

UAIX 一致性 证据 v1

UAIX 一致性 证据 v1 profile for UAI-1 review packets. UAIX records are schemas, profiles, handoff packets, and conformance evidence. They do not authorize execution, prove safety, validate credentials, or certify agent intelligence.

配置文件
uaix.conformance-evidence.v1
规范
UAI-1
必需正文字段
evidence_id, profile_id, schema_url, fixture_url, checks, result, limitations
路由
/wp-json/uaix/v1/schemas/uaix.conformance-evidence.v1

模式记录

UAIX Evaluation Packet Summary v1

UAIX Evaluation Packet Summary v1 profile for UAI-1 review packets. UAIX records are schemas, profiles, handoff packets, and conformance evidence. They do not authorize execution, prove safety, validate credentials, or certify agent intelligence.

配置文件
uaix.evaluation-packet-summary.v1
规范
UAI-1
必需正文字段
summary_id, packet_profiles, required_levels, no_op_triggers, limitations
路由
/wp-json/uaix/v1/schemas/uaix.evaluation-packet-summary.v1

模式记录

UAIX Ability 配置文件 L6 v1

UAIX Ability 配置文件 L6 v1 profile for UAI-1 review packets. UAIX records are schemas, profiles, handoff packets, and conformance evidence. They do not authorize execution, prove safety, validate credentials, or certify agent intelligence.

配置文件
uaix.ability-profile.l0.v1
规范
UAI-1
必需正文字段
ability_profile_id, declared_level, label, capability_surface, authority_boundary, required_human_approval, no_op_triggers, evidence_requirements
路由
/wp-json/uaix/v1/schemas/uaix.ability-profile.l0.v1

模式记录

UAIX Ability 配置文件 L6 v1

UAIX Ability 配置文件 L6 v1 profile for UAI-1 review packets. UAIX records are schemas, profiles, handoff packets, and conformance evidence. They do not authorize execution, prove safety, validate credentials, or certify agent intelligence.

配置文件
uaix.ability-profile.l1.v1
规范
UAI-1
必需正文字段
ability_profile_id, declared_level, label, capability_surface, authority_boundary, required_human_approval, no_op_triggers, evidence_requirements
路由
/wp-json/uaix/v1/schemas/uaix.ability-profile.l1.v1

模式记录

UAIX Ability 配置文件 L6 v1

UAIX Ability 配置文件 L6 v1 profile for UAI-1 review packets. UAIX records are schemas, profiles, handoff packets, and conformance evidence. They do not authorize execution, prove safety, validate credentials, or certify agent intelligence.

配置文件
uaix.ability-profile.l2.v1
规范
UAI-1
必需正文字段
ability_profile_id, declared_level, label, capability_surface, authority_boundary, required_human_approval, no_op_triggers, evidence_requirements
路由
/wp-json/uaix/v1/schemas/uaix.ability-profile.l2.v1

模式记录

UAIX Ability 配置文件 L6 v1

UAIX Ability 配置文件 L6 v1 profile for UAI-1 review packets. UAIX records are schemas, profiles, handoff packets, and conformance evidence. They do not authorize execution, prove safety, validate credentials, or certify agent intelligence.

配置文件
uaix.ability-profile.l3.v1
规范
UAI-1
必需正文字段
ability_profile_id, declared_level, label, capability_surface, authority_boundary, required_human_approval, no_op_triggers, evidence_requirements
路由
/wp-json/uaix/v1/schemas/uaix.ability-profile.l3.v1

模式记录

UAIX Ability 配置文件 L6 v1

UAIX Ability 配置文件 L6 v1 profile for UAI-1 review packets. UAIX records are schemas, profiles, handoff packets, and conformance evidence. They do not authorize execution, prove safety, validate credentials, or certify agent intelligence.

配置文件
uaix.ability-profile.l4.v1
规范
UAI-1
必需正文字段
ability_profile_id, declared_level, label, capability_surface, authority_boundary, required_human_approval, no_op_triggers, evidence_requirements
路由
/wp-json/uaix/v1/schemas/uaix.ability-profile.l4.v1

模式记录

UAIX Ability 配置文件 L6 v1

UAIX Ability 配置文件 L6 v1 profile for UAI-1 review packets. UAIX records are schemas, profiles, handoff packets, and conformance evidence. They do not authorize execution, prove safety, validate credentials, or certify agent intelligence.

配置文件
uaix.ability-profile.l5.v1
规范
UAI-1
必需正文字段
ability_profile_id, declared_level, label, capability_surface, authority_boundary, required_human_approval, no_op_triggers, evidence_requirements
路由
/wp-json/uaix/v1/schemas/uaix.ability-profile.l5.v1

模式记录

UAIX Ability 配置文件 L6 v1

UAIX Ability 配置文件 L6 v1 profile for UAI-1 review packets. UAIX records are schemas, profiles, handoff packets, and conformance evidence. They do not authorize execution, prove safety, validate credentials, or certify agent intelligence.

配置文件
uaix.ability-profile.l6.v1
规范
UAI-1
必需正文字段
ability_profile_id, declared_level, label, capability_surface, authority_boundary, required_human_approval, no_op_triggers, evidence_requirements
路由
/wp-json/uaix/v1/schemas/uaix.ability-profile.l6.v1

模式记录

UAIX Expression-Concept Review v1

UAIX Expression-Concept Review v1 profile for UAI-1 review packets. UAIX records are schemas, profiles, handoff packets, and conformance evidence. They do not authorize execution, prove safety, validate credentials, or certify agent intelligence.

配置文件
uaix.evaluation.expression-concept-review.v1
规范
UAI-1
必需正文字段
source_expression, concept_boundary, interpretation, confidence, no_op_triggers
路由
/wp-json/uaix/v1/schemas/uaix.evaluation.expression-concept-review.v1

模式记录

UAIX Resource-Economy Trace v1

UAIX Resource-Economy Trace v1 profile for UAI-1 review packets. UAIX records are schemas, profiles, handoff packets, and conformance evidence. They do not authorize execution, prove safety, validate credentials, or certify agent intelligence.

配置文件
uaix.evaluation.resource-economy-trace.v1
规范
UAI-1
必需正文字段
resource_scope, cost_model, limits, evidence_refs, no_op_triggers
路由
/wp-json/uaix/v1/schemas/uaix.evaluation.resource-economy-trace.v1

模式记录

UAIX Operator Decision v1

UAIX Operator Decision v1 profile for UAI-1 review packets. UAIX records are schemas, profiles, handoff packets, and conformance evidence. They do not authorize execution, prove safety, validate credentials, or certify agent intelligence.

配置文件
uaix.evaluation.operator-decision.v1
规范
UAI-1
必需正文字段
decision, authority_basis, options_reviewed, human_review_required, no_op_triggers
路由
/wp-json/uaix/v1/schemas/uaix.evaluation.operator-decision.v1

模式记录

UAIX No-op Justification v1

UAIX No-op Justification v1 profile for UAI-1 review packets. UAIX records are schemas, profiles, handoff packets, and conformance evidence. They do not authorize execution, prove safety, validate credentials, or certify agent intelligence.

配置文件
uaix.evaluation.no-op-justification.v1
规范
UAI-1
必需正文字段
trigger, reason, missing_evidence, human_review_url, safe_next_step
路由
/wp-json/uaix/v1/schemas/uaix.evaluation.no-op-justification.v1

模式记录

UAIX Local Sandbox Safety Review v1

UAIX Local Sandbox Safety Review v1 profile for UAI-1 review packets. UAIX records are schemas, profiles, handoff packets, and conformance evidence. They do not authorize execution, prove safety, validate credentials, or certify agent intelligence.

配置文件
uaix.evaluation.local-sandbox-safety-review.v1
规范
UAI-1
必需正文字段
sandbox_scope, unsafe_requests, blocked_operations, review_result, no_op_triggers
路由
/wp-json/uaix/v1/schemas/uaix.evaluation.local-sandbox-safety-review.v1

模式记录

UAIX Memory Ecosystem Handoff v1

UAIX Memory Ecosystem Handoff v1 profile for UAI-1 review packets. UAIX records are schemas, profiles, handoff packets, and conformance evidence. They do not authorize execution, prove safety, validate credentials, or certify agent intelligence.

配置文件
uaix.evaluation.memory-ecosystem-handoff.v1
规范
UAI-1
必需正文字段
source_memory, quarantine_status, promotion_targets, conflicts, receiver_brief
路由
/wp-json/uaix/v1/schemas/uaix.evaluation.memory-ecosystem-handoff.v1

模式记录

UAIX DE11 Benchmark Summary v1

UAIX DE11 Benchmark Summary v1 profile for UAI-1 review packets. UAIX records are schemas, profiles, handoff packets, and conformance evidence. They do not authorize execution, prove safety, validate credentials, or certify agent intelligence.

配置文件
uaix.evaluation.de11-benchmark-summary.v1
规范
UAI-1
必需正文字段
benchmark_id, bounded_scope, reference_result, limitations, non_claims
路由
/wp-json/uaix/v1/schemas/uaix.evaluation.de11-benchmark-summary.v1

模式记录

UAIX .uaix Package Manifest Draft v0.1

Manifest schema for the Draft v0.1 .uaix desktop AI memory package container. The package is local memory and evidence, not runtime authority.

配置文件
uaix.package.v0.1
规范
UAI-1
必需正文字段
路由
/wp-json/uaix/v1/schemas/uaix.package.v0.1

模式记录

UAIX Persona v1

Scoped UAIX persona memory file for non-project assistant packages, bounded personality packages, and packages that support persona switching.

配置文件
uaix.persona.v1
规范
UAI-1
必需正文字段
路由
/wp-json/uaix/v1/schemas/uaix.persona.v1

模式记录

UAIX SPEC-01 Canonical 信封 v1

Publication-envelope contract for portable evidence-bearing UAIX records, including payload, evidence, redaction, trust, signature status, verification, exceptions, and warnings. Uses the canonical UAI-1 transport envelope; UAIX 记录证据 and handoff boundaries but does not authorize execution.

配置文件
uaix.spec-01.envelope.v1
规范
UAI-1
必需正文字段
uaixVersion, spec, envelopeId, createdUtc, issuer, issuerDisplayName, issuerPublicUrl, issuerCapabilityLevel, audience, lifecycleState, trustPosture, payloadType, payload模式, payload, evidence, redactions, signature, signature状态, verification, exceptions, warnings, rules, support边界, localPolicyWins
路由
/wp-json/uaix/v1/schemas/uaix.spec-01.envelope.v1

模式记录

UAIX Capability 配置文件 v1

UAIX capability profile for declaring L0-L6 client posture, consent boundaries, fallback behavior, evidence requirements, and safe default behavior. Uses the canonical UAI-1 transport envelope; UAIX 记录证据 and handoff boundaries but does not authorize execution.

配置文件
uaix.capability-profile.v1
规范
UAI-1
必需正文字段
capability配置文件Id, profileVersion, declaredLevel, supportedLevels, capabilities, consentRequiredFor, fallbacks, safe默认Response, evidenceRequirements, support边界, localPolicyWins
路由
/wp-json/uaix/v1/schemas/uaix.capability-profile.v1

模式记录

UAIX Capability Ladder v1

Machine-readable L0-L6 capability ladder with safe fallbacks, unsupported implication boundaries, and reference-only client scenarios. Uses the canonical UAI-1 transport envelope; UAIX 记录证据 and handoff boundaries but does not authorize execution.

配置文件
uaix.capability-ladder.v1
规范
UAI-1
必需正文字段
ladderId, levels, fallbackRules, safe默认Response, reference示例, support边界, localPolicyWins
路由
/wp-json/uaix/v1/schemas/uaix.capability-ladder.v1

模式记录

UAIX SPEC-02 项目交接 v1

Portable project memory and custody transfer contract for humans, agents, vendors, future sessions, and reviewed runtime consumers. Uses the canonical UAI-1 transport envelope; UAIX 记录证据 and handoff boundaries but does not authorize execution.

配置文件
uaix.spec-02.project-handoff.v1
规范
UAI-1
必需正文字段
projectId, handoffId, createdUtc, owner, custodian, frontDoor, memoryRoots, requiredReads, currentState, constraints, decisions, nextActions, targeted检查s, evidence, redactions, warnings, reference场景s, support边界, localPolicyWins
路由
/wp-json/uaix/v1/schemas/uaix.spec-02.project-handoff.v1

模式记录

UAIX SPEC-03 AGENTS.md Metadata v1

AGENTS.md front-door metadata for canonical roots, nested instruction scope, command policy, memory loading, and safety boundaries. Uses the canonical UAI-1 transport envelope; UAIX 记录证据 and handoff boundaries but does not authorize execution.

配置文件
uaix.spec-03.agents-md-metadata.v1
规范
UAI-1
必需正文字段
repositoryId, canonicalRoot, agentsMdPath, coordinatorPath, localUaiRoot, nestedScopes, requiredReads, commandPolicy, forbiddenOperations, memoryPolicy, securityBoundaries, examples, support边界, localPolicyWins
路由
/wp-json/uaix/v1/schemas/uaix.spec-03.agents-md-metadata.v1

模式记录

UAIX SPEC-04 文件交接 v1

Safe supplied-file intake contract for manifests, bucket review, disposition, redaction, evidence, lifecycle, blocked-file rules, and preservation after durable outcome. Uses the canonical UAI-1 transport envelope; UAIX 记录证据 and handoff boundaries but does not authorize execution.

配置文件
uaix.spec-04.file-handoff.v1
规范
UAI-1
必需正文字段
handoffId, createdUtc, intakeBuckets, fileManifest, reviewDispositions, redactionPolicy, lifecycle, preservationPolicy, evidence, blockedFileRules, support边界, localPolicyWins
路由
/wp-json/uaix/v1/schemas/uaix.spec-04.file-handoff.v1

模式记录

UAIX Review Receipt v1

Review receipt for inspected UAIX envelopes, checks, skipped checks, warnings, exceptions, trust decision, and local-policy result. Uses the canonical UAI-1 transport envelope; UAIX 记录证据 and handoff boundaries but does not authorize execution.

配置文件
uaix.review-receipt.v1
规范
UAI-1
必需正文字段
receiptId, reviewed信封Id, reviewedUtc, reviewer, reviewResult, checksRun, checksSkipped, warnings, exceptions, trustDecision, support边界, localPolicyWins
路由
/wp-json/uaix/v1/schemas/uaix.review-receipt.v1

模式记录

UAIX Public-Safe Audit Digest v1

Public-safe audit digest for evidence references, redactions, public findings, excluded private material, verification, exceptions, and warnings. Uses the canonical UAI-1 transport envelope; UAIX 记录证据 and handoff boundaries but does not authorize execution.

配置文件
uaix.public-safe-audit-digest.v1
规范
UAI-1
必需正文字段
digestId, subject, createdUtc, scope, evidenceRefs, redactions, publicFindings, privateMaterialExcluded, verification, exceptions, warnings, support边界, localPolicyWins
路由
/wp-json/uaix/v1/schemas/uaix.public-safe-audit-digest.v1

模式记录

UAIX Redaction Policy v1

Redaction policy for secret patterns, data classes, review gates, never-publish values, verification, exceptions, and warnings. Uses the canonical UAI-1 transport envelope; UAIX 记录证据 and handoff boundaries but does not authorize execution.

配置文件
uaix.redaction-policy.v1
规范
UAI-1
必需正文字段
policyId, createdUtc, appliesTo, secret模式s, dataClasses, redactionActions, reviewRequiredFor, neverPublish, verification, exceptions, warnings, support边界, localPolicyWins
路由
/wp-json/uaix/v1/schemas/uaix.redaction-policy.v1

已发布的字段注册表

字段注册表保持带键的 JSON 源记录、无键传输顺序以及在公共合约中对齐的嵌套主体/组件顺序。将其视为机器可读发布记录的一部分,而不是作为选定的方便说明。

字段注册表

已发布的无键字段顺序注册表

字段注册表让优化后的无键 JSON 与可读的有键源记录保持一致。请将它视为信封顺序、嵌套组件顺序以及配置文件特定正文顺序的公共映射。

打开字段注册表 JSON

信封顺序

有键与无键记录的根字段

  1. uai_version: Declares the active UAI protocol release for the message.
  2. profile: Selects the exact published message profile.
  3. message_id: Stable message identifier used for review, tracing, and cross-record references.
  4. source: Describes the sender or producing system.
  5. target: Describes the intended receiving system, record, or audience.
  6. conversation: Carries conversation continuity, turn identity, and parent linkage.
  7. delivery: Carries sync versus async mode, priority, expiry, and acknowledgment expectations.
  8. trust: Declares trust-channel, authentication, credential, signature, replay-window, verifier, proof, and status hints.
  9. body: 配置文件-specific payload content.
  10. provenance: Carries trace, lineage, issued-at, and model or agent provenance details.
  11. integrity: Carries checksum, algorithm, and canonicalization information.
  12. extensions: Lists declared extension namespaces attached to the message.

组件顺序

跨配置文件保持稳定的嵌套结构

  • source: type, id, label, uri, did, role, implementation, project
  • target: type, id, label, uri, did, role, implementation, project
  • conversation: conversation_id, turn_id, parent_message_id, traceparent, sequence, correlation_id
  • delivery: mode, priority, expires_at, reply_requested, ack_required, task_ref, idempotency_key, retry_count, sequence, lifecycle, timeout_ms, fallback_directive, expected_output_schema, duplicate_of_message_id, dedupe_behavior
  • trust: channel, auth_scheme, principal, credential_ref, signature_ref, replay_window_id, trust_profile, verification_status, credential_status, verifier_ref, trust_root_ref, proof_ref, replay_policy_ref, verification_checked_at, verification_expires_at, assurance_level
  • provenance: trace_id, parent_trace_id, issued_at, log_ref, agent_id, model_id, confidence, lineage
  • lineage_item: stage, actor_id, model_id, note
  • integrity: version, algorithm, canonicalization, checksum
  • extension_item: namespace, purpose, critical
  • issue_item: severity, code, message, path, help_url
  • error_detail_item: path, code, message, schemaPointer, payloadPointer, field, expected, actual

代理通信顺序

uai.agent.* 数据包的通用字段

  1. uai_version: Declares the active UAI protocol release for the agent communication packet.
  2. profile: Selects the exact published agent communication packet profile.
  3. message_id: Stable agent communication packet identifier used for review, tracing, and cross-record references.
  4. source: Describes the sender or producing system.
  5. target: Describes the intended receiving system, record, or audience.
  6. conversation: Carries conversation continuity, turn identity, and parent linkage.
  7. delivery: Carries sync versus async mode, priority, expiry, and acknowledgment expectations.
  8. trust: Declares trust-channel, authentication, credential, signature, replay-window, verifier, proof, and status hints.
  9. body: 配置文件-specific payload content.
  10. provenance: Carries trace, lineage, issued-at, and model or agent provenance details.
  11. integrity: Carries checksum, algorithm, and canonicalization information.
  12. extensions: Lists declared extension namespaces attached to the agent communication packet.

正文顺序

uai.intent.request.v1

当某个传输选择优化后的无键形式而不是可读的有键 JSON 时,请使用这份有序列表。

intent, subject, requested_profile, parameters, constraints, response_profile

正文顺序

uai.intent.response.v1

当某个传输选择优化后的无键形式而不是可读的有键 JSON 时,请使用这份有序列表。

status, subject, request_message_id, result, notices, task_ref

正文顺序

uai.capability.statement.v1

当某个传输选择优化后的无键形式而不是可读的有键 JSON 时,请使用这份有序列表。

capability_id, version, operations, input_profiles, output_profiles, async_profiles, security_schemes, transport_bindings, conformance_levels, error_codes, endpoints, extension_namespaces, implementation_tracks

正文顺序

uai.error.v1

当某个传输选择优化后的无键形式而不是可读的有键 JSON 时,请使用这份有序列表。

type, title, detail, status, code, retryable, instance, errors, next_step, uaixCode, uaixCategory, uaixSeverity, retryAfterUtc, retryAfterMs, rateLimit, blockedByPolicy, blockedByNetwork, binding状态, constraintViolation, schemaPointer, payloadPointer, field, line, column, expected, actual, allowedValues, documentationUrl, safeHarborUrl, supportReference, evidenceRefs, traceId, correlationId, evidenceRecommended, suspensionRecommended, redactionApplied

正文顺序

uai.conformance.result.v1

当某个传输选择优化后的无键形式而不是可读的有键 JSON 时,请使用这份有序列表。

status, checked_profile, issues, summary, artifacts, target_message_ref

正文顺序

uai.task.status.v1

当某个传输选择优化后的无键形式而不是可读的有键 JSON 时,请使用这份有序列表。

task_id, state, subject, progress, status_message, result_profile, result_ref, blocking_reasons, updated_fields

正文顺序

uai.agent.message.v1

当某个传输选择优化后的无键形式而不是可读的有键 JSON 时,请使用这份有序列表。

message_type, content, context_refs, requires_acknowledgement, intent_semantics, action_type, execution_constraints, support_boundary

正文顺序

uai.agent.ack.v1

当某个传输选择优化后的无键形式而不是可读的有键 JSON 时,请使用这份有序列表。

acknowledged_message_id, status, received_at_utc, rejection_reason, closes_acknowledgement_loop, support_boundary

正文顺序

uai.agent.task-status.v1

当某个传输选择优化后的无键形式而不是可读的有键 JSON 时,请使用这份有序列表。

task_id, state, percent_complete, current_action, estimated_completion_utc, support_boundary

正文顺序

uai.agent.blocker.v1

当某个传输选择优化后的无键形式而不是可读的有键 JSON 时,请使用这份有序列表。

blocker_id, blocker_type, description, human_review_required, proposed_resolution, support_boundary

正文顺序

uai.agent.memory-proposal.v1

当某个传输选择优化后的无键形式而不是可读的有键 JSON 时,请使用这份有序列表。

proposal_id, source_type, proposed_facts, proposed_status, task_execution_separation, review_required, support_boundary

正文顺序

uai.agent.handoff.v1

当某个传输选择优化后的无键形式而不是可读的有键 JSON 时,请使用这份有序列表。

task_id, target_agent_id, context_summary, handoff_reason, exact_next_action, delegated_authorization, support_boundary

正文顺序

uai.agent.final-report.v1

当某个传输选择优化后的无键形式而不是可读的有键 JSON 时,请使用这份有序列表。

task_id, summary, files_changed, new_files, tests_run, skipped_checks, blockers, risks, validation_evidence, memory_updates_proposed, memory_updates_skipped, exact_next_action, support_boundary

正文顺序

uai.agent.correction.v1

当某个传输选择优化后的无键形式而不是可读的有键 JSON 时,请使用这份有序列表。

original_message_id, correction_reason, changed_summary, corrected_fields, revised_payload, support_boundary

正文顺序

uai.capability.profile.v1

当某个传输选择优化后的无键形式而不是可读的有键 JSON 时,请使用这份有序列表。

client_level, client_name, can_fetch_static, can_fetch_json, can_execute_javascript, can_use_browser_ui, can_post_data, can_authenticate, can_call_tools, can_run_long_tasks, can_store_memory, can_coordinate_agents, requires_human_consent_for, recommended_uaix_profiles, fallback_behavior, known_limits, evidence_requirements, safe_default_response, support_boundary, carcinus_boundary, localendpoint_boundary

正文顺序

uai.capability.negotiation.v1

当某个传输选择优化后的无键形式而不是可读的有键 JSON 时,请使用这份有序列表。

negotiation_id, requested_client_level, observed_client_level, selected_client_level, selected_profile, requested_operation, unsupported_features, fallback_behavior, consent_boundaries, evidence_requirements, recommended_uaix_profiles, safe_default_response, support_boundary, carcinus_boundary, localendpoint_boundary

正文顺序

uai.client.limited-browser.v1

当某个传输选择优化后的无键形式而不是可读的有键 JSON 时,请使用这份有序列表。

client_level, client_name, can_fetch_static, can_fetch_json, can_execute_javascript, can_use_browser_ui, can_post_data, can_authenticate, can_call_tools, can_run_long_tasks, can_store_memory, can_coordinate_agents, requires_human_consent_for, recommended_uaix_profiles, fallback_behavior, known_limits, evidence_requirements, safe_default_response, support_boundary, carcinus_boundary, localendpoint_boundary

正文顺序

uai.client.structured-fetch.v1

当某个传输选择优化后的无键形式而不是可读的有键 JSON 时,请使用这份有序列表。

client_level, client_name, can_fetch_static, can_fetch_json, can_execute_javascript, can_use_browser_ui, can_post_data, can_authenticate, can_call_tools, can_run_long_tasks, can_store_memory, can_coordinate_agents, requires_human_consent_for, recommended_uaix_profiles, fallback_behavior, known_limits, evidence_requirements, safe_default_response, support_boundary, carcinus_boundary, localendpoint_boundary

正文顺序

uai.client.browser-assisted.v1

当某个传输选择优化后的无键形式而不是可读的有键 JSON 时,请使用这份有序列表。

client_level, client_name, can_fetch_static, can_fetch_json, can_execute_javascript, can_use_browser_ui, can_post_data, can_authenticate, can_call_tools, can_run_long_tasks, can_store_memory, can_coordinate_agents, requires_human_consent_for, recommended_uaix_profiles, fallback_behavior, known_limits, evidence_requirements, safe_default_response, support_boundary, carcinus_boundary, localendpoint_boundary

正文顺序

uai.client.tool-agent.v1

当某个传输选择优化后的无键形式而不是可读的有键 JSON 时,请使用这份有序列表。

client_level, client_name, can_fetch_static, can_fetch_json, can_execute_javascript, can_use_browser_ui, can_post_data, can_authenticate, can_call_tools, can_run_long_tasks, can_store_memory, can_coordinate_agents, requires_human_consent_for, recommended_uaix_profiles, fallback_behavior, known_limits, evidence_requirements, safe_default_response, support_boundary, carcinus_boundary, localendpoint_boundary

正文顺序

uai.client.workflow-agent.v1

当某个传输选择优化后的无键形式而不是可读的有键 JSON 时,请使用这份有序列表。

client_level, client_name, can_fetch_static, can_fetch_json, can_execute_javascript, can_use_browser_ui, can_post_data, can_authenticate, can_call_tools, can_run_long_tasks, can_store_memory, can_coordinate_agents, requires_human_consent_for, recommended_uaix_profiles, fallback_behavior, known_limits, evidence_requirements, safe_default_response, support_boundary, carcinus_boundary, localendpoint_boundary

正文顺序

uai.client.multi-agent-runtime.v1

当某个传输选择优化后的无键形式而不是可读的有键 JSON 时,请使用这份有序列表。

client_level, client_name, can_fetch_static, can_fetch_json, can_execute_javascript, can_use_browser_ui, can_post_data, can_authenticate, can_call_tools, can_run_long_tasks, can_store_memory, can_coordinate_agents, requires_human_consent_for, recommended_uaix_profiles, fallback_behavior, known_limits, evidence_requirements, safe_default_response, support_boundary, carcinus_boundary, localendpoint_boundary

正文顺序

uai.client.audited-agent-system.v1

当某个传输选择优化后的无键形式而不是可读的有键 JSON 时,请使用这份有序列表。

client_level, client_name, can_fetch_static, can_fetch_json, can_execute_javascript, can_use_browser_ui, can_post_data, can_authenticate, can_call_tools, can_run_long_tasks, can_store_memory, can_coordinate_agents, requires_human_consent_for, recommended_uaix_profiles, fallback_behavior, known_limits, evidence_requirements, safe_default_response, support_boundary, carcinus_boundary, localendpoint_boundary

正文顺序

uaix.ability-profile.v1

当某个传输选择优化后的无键形式而不是可读的有键 JSON 时,请使用这份有序列表。

ability_profile_id, declared_level, label, capability_surface, authority_boundary, required_human_approval, no_op_triggers, evidence_requirements

正文顺序

uaix.startup-packet.v1

当某个传输选择优化后的无键形式而不是可读的有键 JSON 时,请使用这份有序列表。

startup_packet_id, read_order, domain_boundaries, first_acceptable_response, no_op_triggers, validation_targets, identity, token_custody, discovery_bootstrap, safe_harbor, utc_requirements

正文顺序

uaix.memory-maintenance.v1

当某个传输选择优化后的无键形式而不是可读的有键 JSON 时,请使用这份有序列表。

uai_version, profile, schema_version, requirement, governance, protected_paths, validation, recommendation_boundary, provenance

正文顺序

uaix.next-recursive-prompt.v1

当某个传输选择优化后的无键形式而不是可读的有键 JSON 时,请使用这份有序列表。

uai_version, profile, schema_version, scope, lifecycle, activation_policy, objective, authoritative_refs, resume_context, next_loop, checks, writeback_policy, security, cold_memory, integrity, provenance

正文顺序

uaix.suspension-packet.v1

当某个传输选择优化后的无键形式而不是可读的有键 JSON 时,请使用这份有序列表。

suspension_packet_id, state_summary, checks_run, checks_skipped, blockers, next_safe_step, network_obstruction, retry_policy, evidence_packet, human_escalation

正文顺序

uaix.receiver-brief.v1

当某个传输选择优化后的无键形式而不是可读的有键 JSON 时,请使用这份有序列表。

receiver_brief_id, read_order, first_acceptable_response, domain_boundaries, escalation_triggers, no_op_triggers

正文顺序

uaix.memory-firewall-policy.v1

当某个传输选择优化后的无键形式而不是可读的有键 JSON 时,请使用这份有序列表。

policy_id, quarantine_default, adoption_requirements, blocked_requests, no_op_triggers, human_review_required

正文顺序

uaix.no-op-trigger-catalog.v1

当某个传输选择优化后的无键形式而不是可读的有键 JSON 时,请使用这份有序列表。

catalog_id, triggers, default_response, human_review_url, forbidden_recovery

正文顺序

uaix.authority-boundary.v1

当某个传输选择优化后的无键形式而不是可读的有键 JSON 时,请使用这份有序列表。

matrix_id, boundaries, not_authorized_for, no_op_triggers, safe_quote_summary

正文顺序

uaix.conformance-evidence.v1

当某个传输选择优化后的无键形式而不是可读的有键 JSON 时,请使用这份有序列表。

evidence_id, profile_id, schema_url, fixture_url, checks, result, limitations

正文顺序

uaix.evaluation-packet-summary.v1

当某个传输选择优化后的无键形式而不是可读的有键 JSON 时,请使用这份有序列表。

summary_id, packet_profiles, required_levels, no_op_triggers, limitations

正文顺序

uaix.ability-profile.l0.v1

当某个传输选择优化后的无键形式而不是可读的有键 JSON 时,请使用这份有序列表。

ability_profile_id, declared_level, label, capability_surface, authority_boundary, required_human_approval, no_op_triggers, evidence_requirements

正文顺序

uaix.ability-profile.l1.v1

当某个传输选择优化后的无键形式而不是可读的有键 JSON 时,请使用这份有序列表。

ability_profile_id, declared_level, label, capability_surface, authority_boundary, required_human_approval, no_op_triggers, evidence_requirements

正文顺序

uaix.ability-profile.l2.v1

当某个传输选择优化后的无键形式而不是可读的有键 JSON 时,请使用这份有序列表。

ability_profile_id, declared_level, label, capability_surface, authority_boundary, required_human_approval, no_op_triggers, evidence_requirements

正文顺序

uaix.ability-profile.l3.v1

当某个传输选择优化后的无键形式而不是可读的有键 JSON 时,请使用这份有序列表。

ability_profile_id, declared_level, label, capability_surface, authority_boundary, required_human_approval, no_op_triggers, evidence_requirements

正文顺序

uaix.ability-profile.l4.v1

当某个传输选择优化后的无键形式而不是可读的有键 JSON 时,请使用这份有序列表。

ability_profile_id, declared_level, label, capability_surface, authority_boundary, required_human_approval, no_op_triggers, evidence_requirements

正文顺序

uaix.ability-profile.l5.v1

当某个传输选择优化后的无键形式而不是可读的有键 JSON 时,请使用这份有序列表。

ability_profile_id, declared_level, label, capability_surface, authority_boundary, required_human_approval, no_op_triggers, evidence_requirements

正文顺序

uaix.ability-profile.l6.v1

当某个传输选择优化后的无键形式而不是可读的有键 JSON 时,请使用这份有序列表。

ability_profile_id, declared_level, label, capability_surface, authority_boundary, required_human_approval, no_op_triggers, evidence_requirements

正文顺序

uaix.evaluation.expression-concept-review.v1

当某个传输选择优化后的无键形式而不是可读的有键 JSON 时,请使用这份有序列表。

source_expression, concept_boundary, interpretation, confidence, no_op_triggers

正文顺序

uaix.evaluation.resource-economy-trace.v1

当某个传输选择优化后的无键形式而不是可读的有键 JSON 时,请使用这份有序列表。

resource_scope, cost_model, limits, evidence_refs, no_op_triggers

正文顺序

uaix.evaluation.operator-decision.v1

当某个传输选择优化后的无键形式而不是可读的有键 JSON 时,请使用这份有序列表。

decision, authority_basis, options_reviewed, human_review_required, no_op_triggers

正文顺序

uaix.evaluation.no-op-justification.v1

当某个传输选择优化后的无键形式而不是可读的有键 JSON 时,请使用这份有序列表。

trigger, reason, missing_evidence, human_review_url, safe_next_step

正文顺序

uaix.evaluation.local-sandbox-safety-review.v1

当某个传输选择优化后的无键形式而不是可读的有键 JSON 时,请使用这份有序列表。

sandbox_scope, unsafe_requests, blocked_operations, review_result, no_op_triggers

正文顺序

uaix.evaluation.memory-ecosystem-handoff.v1

当某个传输选择优化后的无键形式而不是可读的有键 JSON 时,请使用这份有序列表。

source_memory, quarantine_status, promotion_targets, conflicts, receiver_brief

正文顺序

uaix.evaluation.de11-benchmark-summary.v1

当某个传输选择优化后的无键形式而不是可读的有键 JSON 时,请使用这份有序列表。

benchmark_id, bounded_scope, reference_result, limitations, non_claims

正文顺序

uaix.package.v0.1

当某个传输选择优化后的无键形式而不是可读的有键 JSON 时,请使用这份有序列表。

uaixVersion, packageFormat, packageId, profileId, status, createdUtc, issuer, declaredScopes, entrypoints, files, integrity, support边界

正文顺序

uaix.persona.v1

当某个传输选择优化后的无键形式而不是可读的有键 JSON 时,请使用这份有序列表。

uai_version, profile, schema_version, requirement, persona, preservation, boundaries, switching, provenance

正文顺序

uaix.spec-01.envelope.v1

当某个传输选择优化后的无键形式而不是可读的有键 JSON 时,请使用这份有序列表。

uaixVersion, spec, envelopeId, createdUtc, issuer, issuerDisplayName, issuerPublicUrl, issuerCapabilityLevel, audience, lifecycleState, trustPosture, payloadType, payload模式, payload, evidence, redactions, signature, signature状态, verification, exceptions, warnings, rules, support边界, localPolicyWins

正文顺序

uaix.capability-profile.v1

当某个传输选择优化后的无键形式而不是可读的有键 JSON 时,请使用这份有序列表。

capability配置文件Id, profileVersion, declaredLevel, supportedLevels, capabilities, consentRequiredFor, fallbacks, safe默认Response, evidenceRequirements, support边界, localPolicyWins

正文顺序

uaix.capability-ladder.v1

当某个传输选择优化后的无键形式而不是可读的有键 JSON 时,请使用这份有序列表。

ladderId, levels, fallbackRules, safe默认Response, reference示例, support边界, localPolicyWins

正文顺序

uaix.spec-02.project-handoff.v1

当某个传输选择优化后的无键形式而不是可读的有键 JSON 时,请使用这份有序列表。

projectId, handoffId, createdUtc, owner, custodian, frontDoor, memoryRoots, requiredReads, currentState, constraints, decisions, nextActions, targeted检查s, evidence, redactions, warnings, reference场景s, support边界, localPolicyWins

正文顺序

uaix.spec-03.agents-md-metadata.v1

当某个传输选择优化后的无键形式而不是可读的有键 JSON 时,请使用这份有序列表。

repositoryId, canonicalRoot, agentsMdPath, coordinatorPath, localUaiRoot, nestedScopes, requiredReads, commandPolicy, forbiddenOperations, memoryPolicy, securityBoundaries, examples, support边界, localPolicyWins

正文顺序

uaix.spec-04.file-handoff.v1

当某个传输选择优化后的无键形式而不是可读的有键 JSON 时,请使用这份有序列表。

handoffId, createdUtc, intakeBuckets, fileManifest, reviewDispositions, redactionPolicy, lifecycle, preservationPolicy, evidence, blockedFileRules, support边界, localPolicyWins

正文顺序

uaix.review-receipt.v1

当某个传输选择优化后的无键形式而不是可读的有键 JSON 时,请使用这份有序列表。

receiptId, reviewed信封Id, reviewedUtc, reviewer, reviewResult, checksRun, checksSkipped, warnings, exceptions, trustDecision, support边界, localPolicyWins

正文顺序

uaix.public-safe-audit-digest.v1

当某个传输选择优化后的无键形式而不是可读的有键 JSON 时,请使用这份有序列表。

digestId, subject, createdUtc, scope, evidenceRefs, redactions, publicFindings, privateMaterialExcluded, verification, exceptions, warnings, support边界, localPolicyWins

正文顺序

uaix.redaction-policy.v1

当某个传输选择优化后的无键形式而不是可读的有键 JSON 时,请使用这份有序列表。

policyId, createdUtc, appliesTo, secret模式s, dataClasses, redactionActions, reviewRequiredFor, neverPublish, verification, exceptions, warnings, support边界, localPolicyWins

如何使用本节

  1. 选择您想要支持的配置文件并解析其架构。
  2. 检查匹配情况注册表入境及公众现场注册表在实施紧凑运输或主体顺序假设之前。
  3. 运行验证器与已发表的示例或候选人消息并将结果与​​发布证据一起保留。
  4. 将任何面向发布的更改纳入实施轨道, 这变更日志, 和参考资料与贡献者.

下一步

继续注册表有关当前版本背后的稳定配置文件图、兼容性提示和架构到示例的链接。