agentleFS
Sign inStart free
apacheapache/streampipes/streampipes-pipeline-management/AGENTS.md

streampipes / streampipes-pipeline-management

AGENTS.md756 starsChanged 52 days agoApache-2.0View on GitHub

Applies to streampipes-pipeline-management/. Root AGENTS.md applies as well; build and validation commands live there. Core pipeline domain behaviour: element matching, pipeline verification, graph construction, execution orchestration, pipeline-element migrations, setup tasks, permission handling. - Verification and matching (manager/verification, manager/matching, manager/matching/v2). Keep these deterministic and side-effect free. - Graph construction and output schemas (manager/data/PipelineGraph*). Output schema behaviour is user-visible in the pipeline editor; keep it backward compatible. - Execution tasks and status updates (manager/execution). - Pipeline-element migrations (manager/migration). Surface partial failures; do…

We split this AGENTS.md into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 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.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Keep these deterministic and side-effect free.

    line 16

≈ “Common” is an estimate: at least 1 in 5 of the 36,368 AGENTS.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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

AGENTS Guide (Pipeline Management)

Scope

Applies to streampipes-pipeline-management/. Root AGENTS.md applies as well; build and validation commands live there.

Module intent

Core pipeline domain behaviour: element matching, pipeline verification, graph construction, execution orchestration, pipeline-element migrations, setup tasks, permission handling.

High-risk areas

  • Verification and matching (manager/verification, manager/matching, manager/matching/v2). Keep these deterministic and side-effect free.
  • Graph construction and output schemas (manager/data/PipelineGraph*). Output schema behaviour is user-visible in the pipeline editor; keep it backward compatible.
  • Execution tasks and status updates (manager/execution).
  • Pipeline-element migrations (manager/migration). Surface partial failures; do not leave a pipeline in an unknown migration state.

Rules

  • Creating, updating and deleting pipelines must keep the permission and ownership behaviour that already exists; permissions are created and removed alongside the entity.

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.

Reviews can't be read right now.

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.

Check your setup, free