Open Core Boundary Map
This document defines which parts of LRAgent are open source (MIT) and which are enterprise (BSL 1.1).
Principle
Core = generic, reusable, framework-level. Any developer should be able to build their own AI agent system on top of the core.
Enterprise = domain-specific, industry-integrated, revenue-generating. These modules solve specific business problems that justify commercial licensing.
MIT (Open Source)
Server Core Engines
| Module | Description |
|---|
| intent-engine.js | L1/L2/L3 intent recognition and routing |
| rule-engine.js / rule-engine-core.js | Rule evaluation, 5-dimension scoring |
| capability-runtime.js | Identify → Inspect → Optimize → Repair pipeline |
| capability-dispatcher.js | Capability dispatch and parameter normalization |
| agent-state-machine.js | Agent lifecycle state management |
| circuit-breaker.js | Failure protection for agent calls |
| governance-middleware.js | Audit logging and compliance hooks |
| health-inspector.js / health-patrol.js / health-scanner.js | System health monitoring |
| safe-tools.js | Safe tool whitelist for auto-execute |
| unified-schema.js / unified-validator.js | Schema definition and validation |
| evolution-engine.js | Agent self-improvement loop |
| auto-loop-service.js | Automated goal-driven execution |
| swarm-orchestrator.js | Multi-agent coordination |
| hits-event-bus.js | Event bus for inter-agent communication |
| prompt-template-manager.js | LLM prompt management |
| knowledge-indexer.js / knowledge-search.js | Knowledge base indexing and retrieval |
| content-engine.js | Content generation framework |
| workflow-executor.js | Workflow execution engine |
| relationship-resolver.js | Generic relationship resolution |
Server Routes (Core)
| Route | Description |
|---|
| auth.js | Authentication |
| llm.js | LLM API proxy |
| rule-engine.js / rule-workbench-api.js | Rule engine endpoints |
| intent.js | Intent engine endpoints |
| capability-api.js / capability-pipeline.js | Capability API |
| digital-staff-routes.js | Staff CRUD and execution |
| staff-feedback-routes.js | Feedback and performance API |
| feedback-routes.js | General feedback |
| audit-log.js | Audit log API |
| ai-inspector.js | Data quality inspection |
| content-api.js / content-routes.js | Content management |
| open-platform.js | Open platform API |
| scheduler-routes.js | Task scheduling |
Digital Staff (Core)
| Staff ID | Name | Description |
|---|
| DS-BOSS-001 | Data Clerk | Generic data inspection and reporting |
| DS-BOSS-002 | System Health Monitor | System health checks |
| DS-DOC-001 | Document Validator | Document quality validation |
| DS-CONTENT-001 | Content Generator | Generic content creation |
Frontend (Core)
| Component | Description |
|---|
| AiWorkbench.vue | AI chat workbench |
| Dashboard.vue | System dashboard |
| DigitalStaff.vue | Staff management page |
| StaffFeedbackCard.vue | Execution feedback card |
| StaffResultCard.vue | Execution result display |
| InspectionResult.vue | Data quality inspection results |
| GovernanceTable.vue | Governance audit table |
| MetaModelBrowser.vue | Object type browser |
| BusinessObjectCreate.vue | Object creation dialog |
| All composables/use-capability-*.js | Capability hooks |
| use-exec-log.js, useWebSocket.js, useToast.js | Utility composables |
MiniApp (Core)
| Module | Description |
|---|
| pages/ai-chat/ | AI chat interface |
| pages/workbench/ | Workbench |
| pages/profile/ | Staff detail, run, config |
| api/digital-staff.js | API client |
| i18n/ | Internationalization |
BSL 1.1 (Enterprise)
PLM Integration
| Module | Description |
|---|
| aras-client.js | ARAS Innovator / SCSAI AML protocol client |
| aras-process-sync.js | Process synchronization with PLM |
| aras-quality-query.js | Quality data from PLM |
| aras-rule-sync.js | Rule synchronization with PLM |
| aml-asset-library.js / aml-generator.js | AML asset management |
| sciot-rules-bridge.js | Sciot rule bridge |
Industry-Specific
| Module | Description |
|---|
| bom-demo-builder.js / bom-process-linker.js | BOM structure management |
| change-chain-engine.js | ECR/ECO change management |
| enterprise-rules.js | Enterprise-specific rules |
| industry-profile-loader.js | Industry configuration |
| phosphorus-asset-service.js / phosphorus-kb-builder.js | Chemical industry |
| sccapp-design-engine.js / sccapp-optimize-engine.js | SCCAPP engineering |
| quality-process-bridge.js | Quality-process integration |
| llm-process-*.js | LLM-powered process engineering |
Enterprise Digital Staff
| Staff ID | Name | Description |
|---|
| DS-ECR-001 | ECR Reviewer | Engineering change review |
| DS-VEN-001 | Vendor Manager | Supplier management |
| DS-COST-001 | Cost Optimizer | Cost analysis and optimization |
| DS-PROC-001 | Procurement Agent | Purchase order management |
| DS-ARAS-001 | ARAS Creator | PLM object creation |
| DS-EQUIP-001 | Equipment Maintainer | Predictive maintenance |
Enterprise Routes
| Route | Description |
|---|
| change.js | ECR/ECO lifecycle |
| bom.js / bom-check.js / bom-import.js | BOM management |
| aml.js / aml-library.js | AML library |
| vendor.js | Vendor management |
| procurement.js / purchase-order.js | Procurement |
| quality.js | Quality management |
| industrial-asset.js | Industrial assets |
| phosphorus-asset.js | Chemical industry assets |
| sccapp.js | SCCAPP integration |
| chipwise-routes.js | Chip design |
Enterprise Frontend
| Component | Description |
|---|
| PartDetailPanel.vue | Part detail with PLM data |
| BomExplorer.vue / BomDetailModal.vue | BOM visualization |
| ImpactChart.vue | Change impact analysis chart |
| ProductList.vue | PLM product listing |
| ChangeManagement.vue | ECR/ECO management |
| VendorManagement.vue | Vendor management |
| QualityKpiBoard.vue | Quality KPI dashboard |
| IndustrialAssetOverview.vue | Industrial asset overview |
| SccappCenter.vue | SCCAPP center |
| ChipWiseEngine.vue | Chip design engine |
How to Determine Where New Code Belongs
Ask these questions:
- Does it require ARAS/SCSAI/PLM to function? → Enterprise
- Is it specific to an industry (chemical, manufacturing, chip)? → Enterprise
- Can a developer use it without any PLM backend? → Core
- Does it generate direct revenue? → Enterprise
- Is it a generic framework capability? → Core
When in doubt, open a GitHub issue with the license-question label.