feat(acms): add ACMS v1 context pipeline #188

Closed
opened 2026-02-22 23:39:57 +00:00 by freemo · 2 comments
Owner

Metadata

  • Commit Message: feat(acms): add ACMS v1 context pipeline
  • Branch: feature/m5-acms-context

Background

The ACMS v1 context assembly pipeline is implemented in local mode, integrating UKO and CRP components with fusion strategies. The pipeline assembles context fragments into a budget-constrained payload for actor consumption.

Acceptance Criteria

  • Implement ACMS v1 context assembly pipeline (UKO + CRP + fusion strategies) in local mode.
  • Update docs/reference/acms.md with ACMS v1 pipeline overview.

Definition of Done

This issue is complete when:

  • All subtasks below are completed and checked off.
  • A Git commit is created where the first line of the commit message matches
    the Commit Message in Metadata exactly, followed by a blank line, then
    additional lines providing relevant details about the implementation. The
    commit body should be appropriate in size for a commit message and relatively
    complete in describing what was done.
  • The commit is pushed to the remote on the branch matching the Branch in
    Metadata exactly.
  • The commit is submitted as a pull request to master, reviewed, and
    merged before this issue is marked done.

Subtasks

  • Implement ACMS v1 context assembly pipeline (UKO + CRP + fusion strategies) in local mode.
  • Update docs/reference/acms.md with ACMS v1 pipeline overview.
  • Tests (Behave): Add scenarios for ACMS pipeline assembly and context output.
  • Tests (Robot): Add Robot tests validating ACMS pipeline in a sample project.
  • Tests (ASV): Add benchmarks/acms_pipeline_bench.py for pipeline overhead.
  • Verify coverage >=97% via nox -s coverage_report. If coverage is <97% then review the current unit test coverage report at build/coverage.xml and use it to write new Behave based unit tests to improve code coverage. Specifically, write Behave style unit tests that are descriptively named and specifically improves coverage on whichever file has the most uncovered lines by writing tests that will target the uncovered lines in the report. Once that is done rerun nox -s coverage_report to verify all tests pass and coverage is above >=97%. Only mark this as complete once coverage is >=97%, if not repeat this task as many times as is needed until coverage reaches >=97%.
  • Run nox (all default sessions, including benchmark), fix any errors if needed ensuring nox passes across entire code base, do not ignore any failure even if it seems unrelated to this commit, fix it.

Section: #### M5: ACMS v1 + Context Scaling (Day 26)
Status: Open

## Metadata - **Commit Message**: `feat(acms): add ACMS v1 context pipeline` - **Branch**: `feature/m5-acms-context` ## Background The ACMS v1 context assembly pipeline is implemented in local mode, integrating UKO and CRP components with fusion strategies. The pipeline assembles context fragments into a budget-constrained payload for actor consumption. ## Acceptance Criteria - [ ] Implement ACMS v1 context assembly pipeline (UKO + CRP + fusion strategies) in local mode. - [ ] Update `docs/reference/acms.md` with ACMS v1 pipeline overview. ## Definition of Done This issue is complete when: - All subtasks below are completed and checked off. - A Git commit is created where the **first line** of the commit message matches the Commit Message in Metadata exactly, followed by a blank line, then additional lines providing relevant details about the implementation. The commit body should be appropriate in size for a commit message and relatively complete in describing what was done. - The commit is pushed to the remote on the branch matching the **Branch** in Metadata exactly. - The commit is submitted as a **pull request** to `master`, reviewed, and **merged** before this issue is marked done. ## Subtasks - [ ] Implement ACMS v1 context assembly pipeline (UKO + CRP + fusion strategies) in local mode. - [ ] Update `docs/reference/acms.md` with ACMS v1 pipeline overview. - [ ] Tests (Behave): Add scenarios for ACMS pipeline assembly and context output. - [ ] Tests (Robot): Add Robot tests validating ACMS pipeline in a sample project. - [ ] Tests (ASV): Add `benchmarks/acms_pipeline_bench.py` for pipeline overhead. - [ ] Verify coverage >=97% via `nox -s coverage_report`. If coverage is <97% then review the current unit test coverage report at `build/coverage.xml` and use it to write new Behave based unit tests to improve code coverage. Specifically, write Behave style unit tests that are descriptively named and specifically improves coverage on whichever file has the most uncovered lines by writing tests that will target the uncovered lines in the report. Once that is done rerun `nox -s coverage_report` to verify all tests pass and coverage is above >=97%. Only mark this as complete once coverage is >=97%, if not repeat this task as many times as is needed until coverage reaches >=97%. - [ ] Run `nox` (all default sessions, including benchmark), fix any errors if needed ensuring nox passes across **entire** code base, do not ignore any failure even if it seems unrelated to this commit, fix it. **Section**: #### M5: ACMS v1 + Context Scaling (Day 26) **Status**: Open
freemo added this to the v3.4.0 milestone 2026-02-22 23:39:57 +00:00
Author
Owner

Expected completion updated (Day 15 rebaseline): Day 33 / 2026-03-13 (previously Day 28 / 2026-03-08)

**Expected completion updated (Day 15 rebaseline):** Day 33 / 2026-03-13 (previously Day 28 / 2026-03-08)
freemo added the due date 2026-03-06 2026-02-23 18:41:38 +00:00
Author
Owner

Merged in with PR #465

Merged in with PR #465
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

2026-03-06

Reference
cleveragents/cleveragents-core#188
No description provided.