uapf-conformance

Conformance tests and fixtures for implementations of the Unified Algorithmic Process Format (UAPF).

The goal of this repository is to help vendors and open-source projects verify:

• Correct parsing and validation of .uapf packages.
• Consistent handling of edge cases and error conditions.
• Interoperable execution semantics where applicable.

---

Scope

Planned coverage includes:

1. Schema conformance

   • Minimal valid packages.
   • Packages that intentionally violate a single schema rule.
   • Boundary tests (missing sections, unknown fields, version mismatches).

2. Agent & tooling conformance

   • Validation of agents/roles.json, capabilities.json, bindings.json.
   • Correct interpretation of MCP tools and A2A schemas.

3. Execution-level fixtures (optional)

   • Where appropriate, input → output expectations for well-defined processes.
   • Alignment with reference engine behaviour.

---

Repository layout (planned)

uapf-conformance/
  fixtures/
    valid/
      *.uapf
    invalid/
      missing-manifest/
      invalid-roles/
      invalid-mcp-tools/
  docs/
    CONFORMANCE_LEVELS.md
    HOW_TO_RUN.md

---

Using the fixtures

Implementations (SDKs, engines, viewers) can:

• Run all valid fixtures and assert successful load + validation.
• Run all invalid fixtures and assert clear failure with reasonable error messages.
• Report pass/fail status in their own CI pipelines.

---

Contribution guidelines

• Each fixture should be:

  • Minimal, focused on one rule where possible.
  • Accompanied by a short description: “invalid because …”.

• Changes to fixtures that affect semantics should be discussed via issues or PRs.

---

Relationship to other repos

• Schemas are sourced from UAPF-spec.
• Language SDKs can consume fixtures:
  • uapf-python
  • uapf-typescript
• Engines and MCP servers may use these fixtures for system-level tests.

---

License

MIT – same as core UAPF repositories.