tomevault-io Router Service Platform Change
Trigger
- Change router-side API, service, storage, provider, or support modules outside config, decision, selection, and extproc plugin chains
- Change apiserver, authz, rate-limit, memory, response API, storage, or provider-adapter behavior
Workflow
- Read change surfaces and module boundaries for the affected service layer
- Modify the router-side service or API seam and identify whether profile-owned behavior changed
- Run
make agent-report ENV=cpu CHANGED_FILES="..."to verify surface alignment - Run
make agent-ci-gate CHANGED_FILES="..."to validate the affected constraints - Update any impacted local or CI E2E expectation when the changed module is profile-owned
Gotchas
- These modules are not generic fallback territory anymore; if the change is in this surface, keep the service contract explicit instead of hand-waving it as cross-stack glue.
- Storage, authz, and API seams often look local in code but still change E2E behavior through response-api, memory, or authz-rbac profiles.
Must Read
Standard Commands
make agent-report ENV=cpu CHANGED_FILES="..."make agent-ci-gate CHANGED_FILES="..."make agent-feature-gate ENV=cpu CHANGED_FILES="..."
Acceptance
- Router-side service modules, API seams, and affected validation paths stay aligned
- Profile-owned behavior changes update the relevant local or CI E2E expectation
Source: vllm-project/semantic-router — distributed by TomeVault.