Finalize DAW 2.x runtime contracts #2

New issue

Open

opened 2026-08-10 08:34:24 +02:00 by michael · 0 comments

michael commented

2026-08-10 08:34:24 +02:00

Owner

Goal

Complete the DAW 2.x public runtime-contract set in daw-contracts and keep the published contracts internally consistent before dependent modules are migrated.

Session rationale

The session established daw-contracts as the public source for versioned, language-neutral runtime contracts. Seven draft contracts now exist: mainjan/v1, daw_error/v1, daw_error_report/v1, daw_event/v1, daw_event_response/v1, daw_channel_log/v1, and daw_content_syslog/v1. The decision for 2.x is to keep concrete, binding representations and finish this generation before exploring more dynamic 3.x negotiation ideas.

Scope

Review the seven DAW 2.x draft contracts for consistency with the repository TEMPLATE.md and GLOSSARY.md.
Ensure each contract has the agreed artifact set: contract.json, specification.md, CHANGELOG.md, and valid/invalid examples where applicable.
Preserve the decided error semantics: structured immutable daw_error/v1, embedded cause, separate daw_error_report/v1 for following errors.
Preserve event identity/correlation semantics: event_id, operation_id, immutable events, separate daw_event_response/v1.
Preserve the current logging split for 2.x: daw_channel_log/v1 as the channel contract and daw_content_syslog/v1 as an independent content contract.
Do not add the speculative 3.x stem-cell/self-negotiating-contract model to the 2.x contracts.

Acceptance criteria

All seven draft contract directories contain the agreed normative and machine-readable artifacts.
contract.json and specification.md agree for every contract.
Examples cover the invariants already decided in the session, including valid open-vocabulary cases where applicable.
TEMPLATE.md and GLOSSARY.md match the contract naming/role rules actually used by the 2.x contracts.
No 3.x self-negotiation/stem-cell design is made normative for 2.x.
Repository checks/tests, if present, pass.

Cross-repository context

This issue is the contract-side prerequisite for the daw-lua-common, daw-lua-net, and later daw-modul-log-file migrations.

## Goal Complete the DAW 2.x public runtime-contract set in `daw-contracts` and keep the published contracts internally consistent before dependent modules are migrated. ## Session rationale The session established `daw-contracts` as the public source for versioned, language-neutral runtime contracts. Seven draft contracts now exist: `mainjan/v1`, `daw_error/v1`, `daw_error_report/v1`, `daw_event/v1`, `daw_event_response/v1`, `daw_channel_log/v1`, and `daw_content_syslog/v1`. The decision for 2.x is to keep concrete, binding representations and finish this generation before exploring more dynamic 3.x negotiation ideas. ## Scope - Review the seven DAW 2.x draft contracts for consistency with the repository `TEMPLATE.md` and `GLOSSARY.md`. - Ensure each contract has the agreed artifact set: `contract.json`, `specification.md`, `CHANGELOG.md`, and valid/invalid examples where applicable. - Preserve the decided error semantics: structured immutable `daw_error/v1`, embedded `cause`, separate `daw_error_report/v1` for `following` errors. - Preserve event identity/correlation semantics: `event_id`, `operation_id`, immutable events, separate `daw_event_response/v1`. - Preserve the current logging split for 2.x: `daw_channel_log/v1` as the channel contract and `daw_content_syslog/v1` as an independent content contract. - Do not add the speculative 3.x stem-cell/self-negotiating-contract model to the 2.x contracts. ## Acceptance criteria - [ ] All seven draft contract directories contain the agreed normative and machine-readable artifacts. - [ ] `contract.json` and `specification.md` agree for every contract. - [ ] Examples cover the invariants already decided in the session, including valid open-vocabulary cases where applicable. - [ ] `TEMPLATE.md` and `GLOSSARY.md` match the contract naming/role rules actually used by the 2.x contracts. - [ ] No 3.x self-negotiation/stem-cell design is made normative for 2.x. - [ ] Repository checks/tests, if present, pass. ## Cross-repository context This issue is the contract-side prerequisite for the `daw-lua-common`, `daw-lua-net`, and later `daw-modul-log-file` migrations.

michael added the

coordination/cross-repo

labels