chore: rename cameleer3 to cameleer
Rename Java packages from com.cameleer3 to com.cameleer, module directories from cameleer3-* to cameleer-*, and all references throughout workflows, Dockerfiles, docs, migrations, and pom.xml. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -57,7 +57,7 @@ Agents (50+) Users / UI
|
||||
Agent POST /api/v1/ingest
|
||||
|
|
||||
v
|
||||
[IngestController] -- validates JWT, deserializes using cameleer3-common models
|
||||
[IngestController] -- validates JWT, deserializes using cameleer-common models
|
||||
|
|
||||
v
|
||||
[IngestionService.accept(batch)] -- accepts TransactionData/ActivityData
|
||||
@@ -126,7 +126,7 @@ Each registered SseEmitter sends event to connected agent
|
||||
Agent POST /api/v1/diagrams (on startup or route change)
|
||||
|
|
||||
v
|
||||
[DiagramController] -- receives route definition (XML/YAML/JSON from cameleer3-common)
|
||||
[DiagramController] -- receives route definition (XML/YAML/JSON from cameleer-common)
|
||||
|
|
||||
v
|
||||
[DiagramService.storeVersion(definition)]
|
||||
@@ -341,11 +341,11 @@ public record PageCursor(Instant timestamp, String id) {}
|
||||
|
||||
## Module Boundary Design
|
||||
|
||||
### Core Module (`cameleer3-server-core`)
|
||||
### Core Module (`cameleer-server-core`)
|
||||
|
||||
The core module is the domain layer. It contains:
|
||||
|
||||
- **Domain models** -- Transaction, Activity, Agent, DiagramVersion, etc. (may extend or complement cameleer3-common models)
|
||||
- **Domain models** -- Transaction, Activity, Agent, DiagramVersion, etc. (may extend or complement cameleer-common models)
|
||||
- **Service interfaces and implementations** -- TransactionService, AgentRegistryService, DiagramService, QueryEngine
|
||||
- **Repository interfaces** -- TransactionRepository, DiagramRepository, AgentRepository (interfaces only, no implementations)
|
||||
- **Ingestion logic** -- WriteBuffer, batch assembly, backpressure signaling
|
||||
@@ -356,7 +356,7 @@ The core module is the domain layer. It contains:
|
||||
|
||||
**No Spring Boot dependencies.** Jackson is acceptable (already present). JUnit for tests.
|
||||
|
||||
### App Module (`cameleer3-server-app`)
|
||||
### App Module (`cameleer-server-app`)
|
||||
|
||||
The app module is the infrastructure/adapter layer. It contains:
|
||||
|
||||
@@ -376,8 +376,8 @@ The app module is the infrastructure/adapter layer. It contains:
|
||||
```
|
||||
app --> core (allowed)
|
||||
core --> app (NEVER)
|
||||
core --> cameleer3-common (allowed)
|
||||
app --> cameleer3-common (transitively via core)
|
||||
core --> cameleer-common (allowed)
|
||||
app --> cameleer-common (transitively via core)
|
||||
```
|
||||
|
||||
## Ingestion Pipeline Detail
|
||||
@@ -393,7 +393,7 @@ Use a two-stage approach:
|
||||
|
||||
- WriteBuffer has a bounded capacity (configurable, default 50,000 items).
|
||||
- When buffer is >80% full, respond with HTTP 429 + `Retry-After` header.
|
||||
- Agents (cameleer3) should implement exponential backoff on 429.
|
||||
- Agents (cameleer) should implement exponential backoff on 429.
|
||||
- Monitor buffer fill level as a metric.
|
||||
|
||||
### Batch Size Tuning
|
||||
|
||||
Reference in New Issue
Block a user