coulomb/kontextual-engine
2
0
Fork 0
generated from coulomb/repo-seed
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Workplan reorg for queries, acl, rel envelopes

Browse Source
This commit is contained in:
Bernd Worsch
2026-05-14 01:32:35 +02:00
parent b3501b1ef1
commit b8ec86bcf7
4 changed files with 289 additions and 60 deletions
Download Patch File Download Diff File Expand all files Collapse all files

24
docs/first-release-readiness.md
View File

@@ -29,6 +29,7 @@ Out of scope for `0.1.0`:
| Area | Gate | Current state |
| --- | --- | --- |
| CMIS read-side contract | Query, navigation, relationship, ACL, and change-token contracts are release-stable or explicitly waived. | `KONT-WP-0016` created as a pre-release dependency. |
| Tests | Full suite passes in the project venv. | `.venv/bin/python -m pytest -q` passed: `166 passed`, `14 skipped`; advisory performance drift warnings recorded. |
| CMIS evidence | OpenCMIS selected baseline completes with no unexpected findings. | `run-20260513T223537Z` completed; only local HTTP warning remains. |
| Transport | Released CMIS access points are served behind HTTPS. | Required deployment gate; local loopback warning is accepted only for harness runs. |
@@ -53,20 +54,23 @@ Out of scope for `0.1.0`:
## Release Procedure
1. Run `.venv/bin/python -m pytest -q`.
2. Run the OpenCMIS selected baseline through `guide-board` and persist the
1. Complete or explicitly waive `KONT-WP-0016`.
2. Run `.venv/bin/python -m pytest -q`.
3. Run the OpenCMIS selected baseline through `guide-board` and persist the
evidence document.
3. Run State Hub consistency check and ensure workplans are registered.
4. Run packaging smoke: build wheel/sdist and import `kontextual_engine` from a
4. Run State Hub consistency check and ensure workplans are registered.
5. Run packaging smoke: build wheel/sdist and import `kontextual_engine` from a
clean install.
5. Review security/configuration: HTTPS termination, profile exposure, secrets,
6. Review security/configuration: HTTPS termination, profile exposure, secrets,
local/S3 blob backend settings, and dependency licenses.
6. Update `CHANGELOG.md` or release notes with capabilities, known limitations,
7. Update `CHANGELOG.md` or release notes with capabilities, known limitations,
and accepted warnings.
7. Tag the release only after the gates above are green or explicitly waived.
8. Tag the release only after the gates above are green or explicitly waived.
## Release Decision
The current foundation is close to a controlled `0.1.0` preview. The main
remaining release work is not feature depth; it is discipline around repeatable
verification, packaging, deployment posture, and clearly documented limits.
The current foundation is close to a controlled `0.1.0` preview, but CMIS
read-side contracts should be settled before release if external projects will
build on the engine. After `KONT-WP-0016`, the remaining release work is mainly
discipline around repeatable verification, packaging, deployment posture, and
clearly documented limits.