kontextual-engine/docs/cmis-readiness-gate.md

CMIS Implementation Readiness Gate

Date: 2026-05-06

Status: ready for KONT-WP-0012 implementation planning.

Required Before Implementation

• CMIS target version is fixed at OASIS CMIS 1.1.
• Browser Binding is the first implementation target.
• AtomPub and Web Services bindings are explicitly deferred.
• Capability examples are grouped in examples/cmis/capability-fixtures.json.
• Internal fixture contract tests validate profile expectations.
• OpenCMIS TCK is documented as an optional external harness.
• The first implementation profile is constrained to profile-scoped Browser Binding behavior rather than full CMIS certification claims.

First Implementation Slice

Implement the profile and mapper layer before routes:

1. Profile model and access-point configuration.
2. CMIS object/type/capability projection over existing engine services.
3. Profile-scoped visibility denial and mutation policy.
4. Browser Binding read routes.
5. Governed mutation routes.
6. Optional OpenCMIS TCK compatibility profile.

Non-Goals For The First Slice

• Full AtomPub support.
• Full SOAP/Web Services support.
• Full CMIS SQL grammar.
• Full private-working-copy versioning semantics.
• Legal hold or retention mutation semantics.
• General-purpose CMIS certification claim.