yukta / core
CLAUDE.md1 starsChanged 20 days agoApache-2.0View on GitHub
In this repository21 other files it gives its agents.
- architecture/CLAUDE.mdCLAUDE.md
- boot/CLAUDE.mdCLAUDE.md
- build-logic/CLAUDE.mdCLAUDE.md
- .claude/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- cli/CLAUDE.mdCLAUDE.md
- mcp/CLAUDE.mdCLAUDE.md
- messaging/CLAUDE.mdCLAUDE.md
- plugin-api/CLAUDE.mdCLAUDE.md
- plugins/CLAUDE.mdCLAUDE.md
- plus/CLAUDE.mdCLAUDE.md
- ui/CLAUDE.mdCLAUDE.md
- web/CLAUDE.mdCLAUDE.md
- ide-index-mcpSkill
- pickupSkill
- playwrightSkill
- testsSkill
- ticketSkill
- yuktaSkill
- yukta-supervisorSkill
- yukta-workflowsSkill
The file
We split this CLAUDE.md into the rules it gives an agent
4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 18
All service logic uses Project Reactor (Mono, Flux).
- Very specific: line 35
Use Java records for data models (preferred) or Lombok (@RequiredArgsConstructor, @Getter) for immutable objects.
- Distinctive: line 39
Use Jakarta Bean Validation.
- Very specific: line 70
Follow the tiered "Test Execution Policy (speed)" in the root CLAUDE.md: run --tests for the classes you changed first.
≈ “Common” is an estimate: at least 1 in 5 of the 27,641 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Core Module CLAUDE.md
Overview
Core service layer and workflow orchestration engine.
Build & Development Commands
# Run tests for core module
yk gradle :core:test
# Run a single test class
yk gradle :core:test --tests com.infenia.yukta.service.orchestrator.WorkflowOrchestratorTestKey Architecture & Patterns
Reactive Streams (Core Pattern)
All service logic uses Project Reactor (Mono, Flux).
- Services use
Monofor single operations,Fluxfor streams. - Avoid blocking operations.
Workflow Orchestration
com.infenia.yukta.service.orchestrator.WorkflowOrchestrator: DAG orchestration logic, split acrossassembly/,compiler/,preparator/,strategy/,stream/,tracker/, andvalidator/subpackages.tracker/keeps the queue and the lookup maps inDefaultTaskTrackerService, one run's state inWorkflowState, the spans and meters inRunTelemetry, applying queued events inTrackerEventApplier, the live log and status streams inExecutionStreamsand the remembered finished runs inExecutionHistory.DefaultControlBusGatewaydelegates starting (admission, shared prepare, idempotency) toWorkflowStarter. It also delegates node commands toNodeCommands, restarts toRestartCoordinatorand read-only views toExecutionQueries(ControlDispatchis their shared base).com.infenia.yukta.service.plugin.PluginRegistry: Plugin registration.- Executes a Directed Acyclic Graph (DAG) of nodes and edges.
Immutability & Records
Use Java records for data models (preferred) or Lombok (@RequiredArgsConstructor, @Getter) for immutable objects.
Validation
- Custom validators in
com.infenia.yukta.validation. - Use Jakarta Bean Validation.
Plugin logging
- A plugin writes live log lines through the
PluginLogSinkthat the engine puts in the Reactor context (WorkflowContext); the lines go toTaskTrackerService.appendLogand from there toPluginLogStore(InMemoryPluginLogStore, fed byLogStoreSubscriber).webandmcpread the store throughPluginLogStoreandNodeOutputPager.
Reference rules (load on demand)
The detailed reference that used to live here is in path-scoped rules: each loads when you read, write or edit a matching file (a rule's
paths are relative to the folder that holds its .claude). To read one without touching its files, open it.
| Topic | Rule | Loads for |
Node engine policy (retry, onError, trigger, timeouts, edgeBuffer), node status, node timeouts, breakpoints and tracing | core/.claude/rules/engine-node-policy.md | service/orchestrator/**, model/workflow/**, service/control/valve/** |
| Restart archive, checkpoints, resume, execution log, Plus split, feature gates | core/.claude/rules/restart-and-execution-log.md | service/archive, service/log, service/store, ExecutionResumer, config/** |
| Scheduler limits, idempotent starts, control audit, stop modes, gateway commands, signals and approvals | core/.claude/rules/execution-limits-and-control.md | service/control/**, model/control/** |
| Definition stores and versions | core/.claude/rules/definitions-and-versions.md | service/workflow/**, service/session/**, model/session/** |
| Remote workers, high availability (leader lease) | core/.claude/rules/workers-and-ha.md | service/worker/**, service/leader/** |
Supervisors, ControlReviewer, the event feed | core/.claude/rules/supervisors.md | service/supervisor/**, service/control/directive/** |
Input requests, InputBroker, redaction | core/.claude/rules/input-requests.md | service/input/**, service/redact/** |
| Tracker queue, execution results, validation limits, metrics | core/.claude/rules/tracker-results-and-metrics.md | service/orchestrator/tracker, .../validator, service/result, service/streaming |
| PostgreSQL stores | plus/.claude/rules/postgres-stores.md | plus/persistence-postgres/** |
SUB_WORKFLOW | plugins/.claude/rules/sub-workflows.md | plugins/processors/internal/** |
| LLM and MCP-tool budgets | plugins/.claude/rules/llm-budgets.md | llm-call, mcp-tool-call |
${env.X}, expression safety, script and process limits | plugin-api/.claude/rules/expressions-and-environment.md | plugin-api/src/main/java/**/util/** |
Key File Locations
- Services:
src/main/java/com/infenia/yukta/service/ - Validation:
src/main/java/com/infenia/yukta/validation/ - Module reference (architecture, feature catalog, settings, metrics):
../docs/contributing/core-reference.mdx. When you add, change or remove a core feature, setting or meter, update it and runcore/scripts/check-core-reference.sh(then--stamp); the page's "Maintaining this document" section says what to edit. - Module guide (components, scenarios, ADRs):
../docs/contributing/modules/core.mdx; open risks, bugs and features: GitHub issues labelledcore(gh issue list -l core); assessment and plans:../design/assessments/core.md,../design/plans/
Testing speed
Follow the tiered "Test Execution Policy (speed)" in the root CLAUDE.md: run --tests for the classes you changed first; full :core:test only when many files changed.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

