Design doc gaps and boundary violations in cleveractors-core #4
Labels
No labels
auto/blocked-by-deps
auto/ci-timeout
auto/claimed-implementer
auto/claimed-merge
auto/claimed-reviewer
auto/driver-down
auto/invariant-violation
auto/last-attempt-tier-0
auto/last-attempt-tier-1
auto/last-attempt-tier-2
auto/last-attempt-tier-min
Automation Tracking
auto/needs-conflict-resolution
auto/needs-implementer
auto/postmortem
auto/ready-to-merge
auto/restart-throttled
auto/revert
auto/sentinel
auto/stale-inactivity
auto/unstable
Blocked
Bounty
$100
Bounty
$1000
Bounty
$10000
Bounty
$20
Bounty
$2000
Bounty
$250
Bounty
$50
Bounty
$500
Bounty
$5000
Bounty
$750
MoSCoW
Could have
MoSCoW
Must have
MoSCoW
Should have
Needs Feedback
Points
1
Points
13
Points
2
Points
21
Points
3
Points
34
Points
5
Points
55
Points
8
Points
88
Priority
Backlog
Priority
CI Blocker
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Signed-off: Owner
Signed-off: Scrum Master
Signed-off: Tech Lead
Spike
State
Completed
State
Duplicate
State
In Progress
State
In Review
State
Paused
State
Unverified
State
Verified
State
Wont Do
Type
Automation
Type
Bug
Type
Discussion
Type
Documentation
Type
Epic
Type
Feature
Type
Legendary
Type
Refactor
Type
Support
Type
Task
Type
Testing
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Depends on
#5 fix: sync doc with extraction scope, remove boundary violation, add ProviderRegistryPort
cleveragents/cleveractors-core
Reference
cleveragents/cleveractors-core#4
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Background
cleveractors-corewas extracted fromcleveragents-coreto provide a pure-domain library (actor YAML parsing, validation, Jinja2 preprocessing, and LangGraph compilation) shared by bothcleveragents-coreandcleverrouter. The extraction was done by an LLM and the result has several documentation gaps and at least one code boundary violation relative to the decisions recorded in ADR-001 and ADR-002.This issue tracks everything that needs to be fixed or added before the library can be considered properly documented and internally consistent.
1. Boundary violation —
acms/index.pymust not be in this librarySeverity: high (code + doc inconsistency)
ADR-001 explicitly states:
The file
src/cleveractors/acms/index.pyimplements exactly the prohibited "indexer":ACMSIndex(storage + query engine),FileTraversalEngine(filesystem traversal), and supporting data models (IndexEntry,FileType,TierLevel). This implementation is bound to the CLI use case ofcleveragents-coreand has no relationship to actor YAML parsing or LangGraph compilation. The library's role is to provide building blocks (basic data types, interfaces, etc.); the actual indexer implementation depends on the host's use case.Action required:
src/cleveractors/acms/index.pyback tocleveragents-coreunder its ACMS subsystem.src/cleveractors/acms/__init__.pyto remove any re-export of these symbols.cleveractorsimports fromacms.index.2. Missing port —
cleveractors.ports.provider_registrySeverity: high (incomplete public surface)
docs/index.mdreferencescleveractors.ports.provider_registrybut the file does not exist. Without a pluggable provider mechanism, consumers cannot make actual LLM calls through the library — the library would be unusable as a standalone compile-and-run unit.A
ProviderRegistryPortProtocol (analogous toToolRegistryPortin ADR-002) should be introduced so that hosts (cleveragents-core,cleverrouter, or third-party consumers) can supply their own LangChain provider configurationwithout the library hardcoding a dependency on any particular provider registry.
Action required:
src/cleveractors/ports/provider_registry.pywith aProviderRegistryPortProtocol exposing the minimum surface the library needs (e.g.get(provider: str, model: str) -> BaseChatModel | None).docs/specification.mdto list the new port in the "Extension points (Protocols)" table.docs/index.mdto remove the dangling "or supply via ..." note and replace it with the correct reference once the port exists.3. Missing ADR — Actor Abstraction Definition
Severity: medium (missing design doc)
cleveractorsis the canonical home for actor parsing and compilation, yet it has no document formally defining what an actor is. The foundational definition lives only incleveragents-core/docs/adr/ADR-031. Consumers of this library need to understand:Action required:
Add
docs/adr/ADR-003-actor-abstraction-definition.mdderived fromcleveragents-coreADR-031, scoped to what the library implements (parsing, schema, compilation) and cross-referencing the host for runtime concerns (plan lifecycle, invariant reconciliation, etc.).4. Missing ADR — Jinja2 YAML Template Preprocessing
Severity: medium (missing design doc)
The two-phase preprocessing pipeline is a significant design decision implemented here (
templates/secure_renderer.py,actor/yaml_template_engine.py) but has no ADR in this repo. Relevant decisions include:SandboxedEnvironment) — security constraintsystem_promptfields (deferred rendering with sentinel markers)${VAR}env-var interpolationyaml,indent,sum,selectattr) and built-in exposure (range,len, etc.)Action required:
Add
docs/adr/ADR-004-jinja2-yaml-template-preprocessing.mdderived fromcleveragents-coreADR-032.5. Missing reference docs — Actor YAML schema, compiler, config guide, hierarchy extensions, and examples
Severity: medium (missing documentation)
The library owns the actor YAML format and compiler but ships only a single trivial example (
docs/my-actor.yaml). Consumers have no reference for:docs/reference/actors_schema.mdllm,tool,graph), node type schemas, edge schema, validation rules, error messagesdocs/reference/actor_compiler.mddocs/reference/actor_config.mddocs/reference/actor_hierarchy.mdskill/mcp/builtin), subgraph actor references, actor-levelskills/lsp/lsp_capabilitiesfieldsdocs/reference/actors_examples.mdAction required:
Port and adapt the five reference docs listed above from
cleveragents-core. Scope each doc to what the library provides (schema + compile); strip references to host-only concerns (plan lifecycle, CLI commands, actor registry, reactive routing).6. Missing API reference — public surface
Severity: low (missing documentation)
No API reference documents the public classes and functions:
ActorConfigSchema— Pydantic model fields and validatorsActorLoader—discover(),load(),validate()methods and their parameterscompile_actor()/CompiledActor— inputs, outputs, whatCompilationMetadatacontainsActorCompilationError,MissingNodeError,InvalidEntryExitError,SubgraphCycleErrorLspBinding,VocabularyRegistry,ToolRegistryPort,ProviderRegistryPort— data shapes and usageAction required:
Add
docs/api/actor.mddocumenting the above. Can be derived from cleveragents-core/docs/api/actor.md, removing theInvariantReconciliationActorsection (host-only) and updating import paths tocleveractors.*`.7. Undocumented internal modules not mentioned in spec
Severity: low (documentation clarity)
docs/specification.mdlists the public API surface but is silent on several modules that exist in the source tree. Consumers cannot tell if these are part of the public API or internal implementation details:cleveractors.actor.role_validationcleveractors.actor.utilscleveractors.actor.yaml_template_enginecleveractors.langgraph.dynamic_routercleveractors.langgraph.message_routercleveractors.langgraph.pure_graphcleveractors.langgraph.routing_adapterAction required:
Add a section to
docs/specification.mdtitled "Internal modules (not public API)" listing the above with a one-line description of each, or promote any that are intentionally public into the public surface table.Checklist
src/cleveractors/acms/index.pyback tocleveragents-core(item 1)src/cleveractors/ports/provider_registry.pywithProviderRegistryPortProtocol (item 2)docs/adr/ADR-003-actor-abstraction-definition.md(item 3)docs/adr/ADR-004-jinja2-yaml-template-preprocessing.md(item 4)docs/reference/actors_schema.md(item 5)docs/reference/actor_compiler.md(item 5)docs/reference/actor_config.md(item 5)docs/reference/actor_hierarchy.md(item 5)docs/reference/actors_examples.md(item 5)docs/api/actor.md(item 6)docs/specification.md(item 7)Post-review fixes applied (commit
6d24090)The following issues identified during multi-agent review of PR #5 have been addressed:
1.
providerfield missing from reference docs (Major)Files:
docs/reference/actors_schema.md,docs/reference/actor_config.mdAdded
provideras a required field to LLM Actor and GRAPH Actor sections inactors_schema.md. Added fullproviderfield definition with description, common values, and cross-reference to ADR-005. Addedproviderto all four major YAML examples. Added missingprovidervalidation error message. Updatedactor_config.mdwithproviderin basic structure and hierarchical graph examples, and added the missingprovidererror case.2. Missing
ISSUES CLOSED: #4footer in commits (Major)Both commits squashed into a single commit with proper
ISSUES CLOSED: #4footer, per the project's Conventional Changelog standard. The single-commit structure also resolves the branch hygiene violation (two commits for one issue).3. Prohibited
# type: ignorein new file smoke_steps.py (Major)File:
features/steps/smoke_steps.pyRemoved
# type: ignore[import-untyped]from thebehaveimport. Sincefeatures/is excluded from pyright's scope inpyrightconfig.json, no suppression is needed.4. Weak BDD assertion (Major)
Files:
features/smoke.feature,features/steps/smoke_steps.pyChanged
then_has_assistant_messagetothen_has_stub_assistant_messagewhich verifies the precise content"stub response"rather than just checking forrole == "assistant". This ensures the registry was actually resolved and the agent invoked, not that the graceful fallback path triggered.5. Fallback message format now matches ADR-005 (Minor)
File:
src/cleveractors/langgraph/nodes.pyFixed
_execute_agentfallback to produce"Agent {provider}/{model} not found"when bothproviderandmodelare available in metadata, matching the ADR-005 specification. Previously it emitted"Agent {model} not found".6. Three new BDD scenarios added (Minor)
File:
features/smoke.featureAdded BDD scenarios for:
provider_registry.get()returnsNoneprovider_registryis suppliedTotal: 7 scenarios, 30 steps. All pass.
7. PR title "WIP:" prefix removed (Minor)
PR title changed from
"WIP: Sync doc..."to"fix: sync doc with extraction scope, remove boundary violation, add ProviderRegistryPort".8.
Type/Documentationlabel added to PRQuality gates (all passing)
Deferred items
# type: ignorecomments insrc/cleveractors/langgraph/nodes.py(lines 17, 20) were not removed — they are pre-existing and fixing them requires a stub file forcleveractors.agents.tool, which is out of scope for this PR.features/mocks/directory not created — this repo does not have afeatures/mocks/convention in its project configuration.acms/index.pyback intocleveragents-core— the file already exists there atcleveragents/acms/index.py. Any updates needed are tracked separately.