mecatl / engine
AGENTS.md308 starsChanged 37 days agoApache-2.0View on GitHub
engine/ is the separately published github.com/stacklok/mecatl/engine module. - Focused test: cd engine && go test ./<pkg>/ -run <Test>. - For isolated engine changes with no effect on other parts of the codebase, run targeted local tests (including relevant race, architecture, and API checks) and rely on CI for the full repository pass. Broaden local checks when changes affect shared behavior or cross-module integration. - task test:engine-standalone builds and tests with GOWORK=off. A new import must resolve from engine/go.mod alone, never…
In this repository12 other files it gives its agents.
- AGENTS.mdAGENTS.md
- internal/AGENTS.mdAGENTS.md
- user-docs/AGENTS.mdAGENTS.md
- website/AGENTS.mdAGENTS.md
- cut-releaseSkill
- mecak8s-kind-manual-verifySkill
- mecatl-learning-configSkill
- mecatl-model-router-configSkill
- panel-reviewSkill
- perf-mcp-interpretationSkill
- perf-optimizationSkill
- tech-writerSkill
The file
Files
AGENTS.md: engine module
engine/ is the separately published github.com/stacklok/mecatl/engine module.
Commands
- Focused test:
cd engine && go test ./<pkg>/ -run <Test>. - For isolated engine changes with no effect on other parts of the codebase, run targeted local tests (including relevant race, architecture, and API checks) and rely on CI for the full repository pass. Broaden local checks when changes affect shared behavior or cross-module integration.
task test:engine-standalonebuilds and tests withGOWORK=off. A new import must resolve fromengine/go.modalone, never from the root module.- The API snapshot tool lives in the root module (
internal/apicheck), so runtask api:updatefrom the repo root after changing an exported identifier in a package listed inarch.CorePackages. Commit theengine/api/*.txtchanges and add anengine/CHANGELOG.mdentry classified per COMPATIBILITY.md.
Layering is enforced twice
A new import between engine packages must be allowed in both places, or lint and tests fail independently:
- the package's strict depguard allowlist in the root
.golangci.yml; coreImportRulesinarch/layering_test.go(core packages only).
A new core package also goes in arch.CorePackages, which feeds the layering tests and
the API snapshot gate. Production code in engine/adapter/* never imports agent.
Invariants
FileSystem,Workspace, andEnvironmentbelong totool, notport:portimportstool, so the reverse would cycle.governancestays session-free and imports only the standard library;sessionmay carry governance values.- Mutate
Sessiononly through its aggregate methods, and keep tool-call/result pairing valid. - A
ReadOnly()tool whose call can write the parent workspace must implementMutatesParent, or dispatch batches it with concurrent reads; see the agent loop. port.LLMRequeststays provider-neutral and provider replay stateless. Re-derive provider- or model-dependent dependencies through factories, not clone-and-swap.
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.

