Skip to content

docs(m2-11): M2 exit review - #39

Merged
teo1747 merged 2 commits into
test/m2-10-campaignfrom
docs/m2-11-exit
Oct 30, 2026
Merged

teo1747 merged 2 commits into
test/m2-10-campaignfrom
docs/m2-11-exit

Conversation

@teo1747

@teo1747 teo1747 commented Oct 30, 2026 •

Copy link
Copy Markdown
Member

Stacked on #38. This completes the M2-11 checklist item, and with it every M2 checklist box.

Problem and result

M2-11 asks for the delivered scope to be reconciled with the docs, configuration, model, complexity annotations and requirement cards, and for the exit and the remaining M3a work to be recorded.

  • docs/engineering/m2-exit-review.md records:
  • STATUS is reviewed as of the exit:
    • binding sources (semaphores, event flags, message queues), object lists for every type, trace IDs 31–44 and model coverage are brought up to date;
    • coverage reports no longer count as unimplemented.
  • Roadmap. The M2 entry now says what was delivered for review and what was not.
  • Configuration guide. Lists the native-coverage preset and every new kernel object option with its per-profile defaults.
  • Checklist and changelog. The last three checklist boxes are ticked, and the changelog has an entry.

All M2 contract changes stay open for the project owner's review: amendments A29–A61, and ADR-045 to ADR-048 plus ADR-050.

Validation

Review checklist

  • Each authored commit has my matching Signed-off-by trailer (git commit -s); DCO is separate from cryptographic signing.
  • Scope and implementation limits are reflected in the user/API documentation and Project status where applicable.
  • Contract changes update requirements/specifications; architecture decisions have an ADR. (None new; the review lists the open ones.)
  • Kernel semantics changes update the reference model and conformance evidence in the same PR. (No kernel change.)
  • User-visible changes have an Unreleased changelog entry, or Validation explains why none is needed.
  • Required checks pass, review conversations are resolved, and known failures are disclosed before merge.

docs/engineering/m2-exit-review.md records:
- every M2 checklist item with its pull requests (#21 to #39) and its
  evidence;
- the reconciliation of the public API, annotations, complexity,
  configuration, model and requirement cards;
- the five defects M2 found and where each is fixed;
- the CI state;
- the limits carried out of M2 (hardware, the tiny profile, primitives
  not built);
- the remaining M3a work.

The remaining checklist boxes are ticked. STATUS is reviewed as of the
exit: binding sources, object lists, trace records and model coverage
are brought up to date, and coverage reports no longer count as
unimplemented. The roadmap's M2 entry says what was delivered and what
was not, and the configuration guide lists the coverage preset and the
kernel object options with their per-profile defaults.

Signed-off-by: teo1747 <motsoujunior17@gmail.com>
Signed-off-by: teo1747 <motsoujunior17@gmail.com>
@teo1747
teo1747 merged commit f2efb87 into test/m2-10-campaign Oct 30, 2026
26 checks passed
teo1747 added a commit that referenced this pull request Oct 31, 2026
M2: bring the merged stack (#22–#39) into main
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant