---
id: KONT-WP-0011
type: workplan
title: "CMIS Compliance Assessment And Test Foundation"
domain: markitect
repo: kontextual-engine
status: completed
owner: codex
topic_slug: markitect
planning_priority: high
planning_order: 11
created: "2026-05-06"
updated: "2026-05-06"
state_hub_workstream_id: "c14d232c-cf80-443b-b5e0-76b51baf6676"
---

# KONT-WP-0011: CMIS Compliance Assessment And Test Foundation

## Purpose

Establish the CMIS compliance baseline before implementation. This workplan
maps OASIS CMIS 1.1 capabilities to current engine functionality, organizes
example fixtures by capability, and prepares internal and optional external
compliance tests.

## References

- `docs/cmis-compliance-assessment.md`
- `docs/cmis-compliance-test-foundation.md`
- `docs/cmis-readiness-gate.md`
- `examples/cmis/capability-fixtures.json`
- `tests/cmis/test_cmis_contract_examples.py`
- OASIS CMIS 1.1 standard and errata.
- Apache Chemistry OpenCMIS TCK 1.1.0 and CMIS Workbench as optional external
  validation tools.

## Boundary

This workplan does not implement CMIS access points. It creates the assessment,
fixtures, profile matrix, and test harness that will govern implementation in
`KONT-WP-0012`.

## C11.1 - Freeze CMIS target version and reusable validation strategy

```task
id: KONT-WP-0011-T001
status: done
priority: high
state_hub_task_id: "1f4ed133-74f7-46df-9266-277813b5399a"
```

Acceptance:

- CMIS target version, bindings, and errata posture are documented.
- OpenCMIS TCK/Workbench reuse strategy is documented.
- External harness is optional and does not block default Python tests.

## C11.2 - Build capability assessment and demand estimate

```task
id: KONT-WP-0011-T002
status: done
priority: high
state_hub_task_id: "02651630-16e6-4c5f-879d-988a55fb7227"
```

Acceptance:

- Capability-by-capability availability is documented.
- Each CMIS area has a gap statement and implementation demand estimate.
- High-risk areas are called out before implementation begins.

## C11.3 - Create CMIS example fixture catalog grouped by capability

```task
id: KONT-WP-0011-T003
status: done
priority: high
state_hub_task_id: "a895218c-61b1-4944-8774-fd21c5416580"
```

Acceptance:

- Example fixture groups cover repository/type, navigation, object/content,
  versioning, discovery, relationships, ACL/policy, change log, renditions,
  retention/hold, and bulk operations.
- Fixtures declare expected behavior per profile.
- Fixtures can seed both internal tests and external TCK preparations.

## C11.4 - Add internal CMIS contract test skeleton

```task
id: KONT-WP-0011-T004
status: done
priority: high
state_hub_task_id: "710da9b6-2034-4948-8bc7-16230cc839cf"
```

Acceptance:

- Internal tests validate CMIS mapper outputs independent of OpenCMIS.
- Tests are organized by capability.
- Unsupported capabilities assert explicit CMIS capability flags and structured
  diagnostics.

## C11.5 - Add optional OpenCMIS TCK harness plan

```task
id: KONT-WP-0011-T005
status: done
priority: medium
state_hub_task_id: "85b321a1-b9b5-469e-bc45-b207dc39ad7a"
```

Acceptance:

- Optional Java/Maven harness configuration is documented.
- TCK group selection is mapped to access-point profiles.
- CI/default test suite skips TCK unless explicitly enabled.

## C11.6 - Produce readiness gate for implementation

```task
id: KONT-WP-0011-T006
status: done
priority: medium
state_hub_task_id: "604e2f06-fde5-4d88-a13e-f3b725177696"
```

Acceptance:

- A readiness checklist determines when `KONT-WP-0012` can start.
- The checklist includes capability profile scope, fixture coverage, TCK
  strategy, and known unsupported features.

## Definition Of Done

- CMIS capability assessment exists and is reviewed.
- Example fixtures and internal test skeleton are organized by capability.
- Optional OpenCMIS TCK strategy is ready.
- Implementation proceeds only through the profile plan in `KONT-WP-0012`.