agentleFS
stacklokstacklok/mecatl/internal/AGENTS.md

mecatl / internal

AGENTS.md308 starsChanged 37 days agoApache-2.0View on GitHub

- A settings.yaml key is a field on a *Section struct in adapter/permconfig/schema.go. Its doc comment becomes the row in the configuration reference; the generator reads comments from that file only. A new top-level section also needs a subtree with a pinned Tier in configgen/build.go. Regenerate with task docs:configref. - Service.appendEvent in adapter/server/service.go is the only place that stamps session.Event.Actor, from the verified caller in the request context, not from ownership. Engine emit sites leave Actor nil; do not add…

The file

Files
AGENTS.md

AGENTS.md: internal

Where to change what

  • A settings.yaml key is a field on a *Section struct in adapter/permconfig/schema.go. Its doc comment becomes the row in the configuration reference; the generator reads comments from that file only. A new top-level section also needs a subtree with a pinned Tier in configgen/build.go. Regenerate with task docs:configref.
  • Service.appendEvent in adapter/server/service.go is the only place that stamps session.Event.Actor, from the verified caller in the request context, not from ownership. Engine emit sites leave Actor nil; do not add a second stamping path.

Invariants

  • Placement is server-owned (app/placement.go): exact EnvironmentRef{Kind, ID, Revision}, fail-closed reattachment, no public paths or cwd-based inference. A binding's governance root (the host checkout) is not its execution root; see placement.
  • Operator command_runner.environment.inherit grants reach built-in main runners and direct-write children, not hardened children or internal Git. Reserved harness credential names stay scrubbed even when listed.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.