kami
06c225e3bd
The task tools were registered but had only mechanical descriptions and no standing policy, so agents knew the tools existed but not when to reach for them. Lead each of the five descriptions with its trigger (when to use, when not to) and add a task-tracking convention to .correx/project.toml, which is rendered into every stage's L0 context. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
16 lines
1.0 KiB
TOML
16 lines
1.0 KiB
TOML
about = "CORREX — local-first, event-sourced orchestration kernel for LLM workflows. Kotlin 2.0 / JVM 21, Gradle multi-module, kotlinx.serialization, Ktor."
|
|
|
|
conventions = [
|
|
"Event log is the only source of truth; projections are disposable and rebuilt from events",
|
|
"Dependency direction: apps -> core -> infrastructure; no cross-core imports",
|
|
"No bare try-catch; use runCatching and sealed domain error types",
|
|
"Every new EventPayload must be registered in the eventModule polymorphic block (Serialization.kt)",
|
|
"Track multi-session or handoff work as native tasks: search before creating to avoid duplicates (task_search), task_context before starting, claim before working, submit_for_review when ready, complete after review. Don't open a task for a single self-contained edit you finish now.",
|
|
]
|
|
|
|
[commands]
|
|
test-all = "./gradlew check --rerun-tasks"
|
|
test-module = "./gradlew :core:<module>:test --rerun-tasks"
|
|
context-lookup = "python scripts/ctx.py <query>"
|
|
epic-status = "bash scripts/epic-status.sh"
|