agentleFS
Sign inStart free
apacheapache/fineract/AGENTS.md

fineract

AGENTS.md2.6k starsChanged 13 days agoApache-2.0View on GitHub

This file is read by automated agents (security scanners, code analyzers, AI assistants) operating on this repository. It points them at the human-authored references they should consult before producing output. Security model: SECURITY.md Agents that scan this repository should consult SECURITY.md for the project's threat model, in-scope / out-of-scope declarations, and known non-findings before reporting issues. Write requests are being moved from the legacy command pipeline to the typed command infrastructure in fineract-command (FSIP-5). Both styles exist in the code…

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

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Write requests are being moved from the legacy command pipeline to the typed command infrastructure in fineract-command (FSIP-5).

    line 18

≈ “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

Agent guidance

This file is read by automated agents (security scanners, code analyzers, AI assistants) operating on this repository. It points them at the human-authored references they should consult before producing output.

Security

Security model: SECURITY.md

Agents that scan this repository should consult SECURITY.md for the project's threat model, in-scope / out-of-scope declarations, and known non-findings before reporting issues.

Command processing (write requests)

Write requests are being moved from the legacy command pipeline to the typed command infrastructure in fineract-command (FSIP-5). Both styles exist in the code today and the legacy one is still far more common. In a feature whose write requests already go through CommandDispatcher, keep to that style and do not add legacy handlers next to it.

The new style uses:

  • request and response DTOs in the feature's data package
  • a Command<Request> subclass in its command package
  • a CommandHandler<Request, Response> in its handler package
  • a REST resource that injects CommandDispatcher, sets the request as the command payload and returns dispatcher.dispatch(command).get()
  • business services that take the typed request, never a JsonCommand

It does not use the legacy API: NewCommandSourceHandler, @CommandType, CommandWrapper, CommandWrapperBuilder, PortfolioCommandSourceWritePlatformService, JsonCommand or FromJsonHelper.

Reference implementations (copy the annotations on their handlers as well):

  • payment types: fineract-core/src/main/java/org/apache/fineract/portfolio/paymenttype/
  • documents and images: fineract-document/src/main/java/org/apache/fineract/infrastructure/documentmanagement/

Background and instructions:

  • fineract-command/REFACTORING.md: how to migrate a feature
  • fineract-command/README.md: why the new infrastructure exists
  • fineract-doc/src/docs/en/chapters/command/: architecture, dispatcher and handlers
  • FSIP-5 on the project wiki

Where the documentation and the reference implementations disagree, follow the reference implementations.

Download now (ZIP)

Trending

More talk lately.about the whole repository

Dec 2025: 0 mentionsJan 2026: 1 mentionFeb 2026: 1 mentionMar 2026: 1 mentionApr 2026: 0 mentionsMay 2026: 3 mentionsJun 2026: 2 mentionsJul 2026: 3 mentionsAug 2026: 6 mentionsSep 2026: 3 mentionsOct 2026: 13 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the apache/fineract repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about apache/fineract

The biggest 5 of 54 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 54

Talked about on GitHub, Hacker News and Stack Overflow (54 times).

On GitHub · 50

45 more on GitHub

On Hacker News · 2

On Stack Overflow · 2

  • Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.

    Of the AGENTS.md files we read, the 28,693 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

  • In this repositoryOne other file it gives its agents.

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.

Check your setup, free