Skip to main content
FaPost Core is developed with AI coding agents — Claude Code and Codex — working through Jig, an open framework that gives an agent a process to follow and a place to keep what the project knows. You do not need an agent to contribute; a pull request written by hand is reviewed the same way. If you do use one, this page is how it fits in.

​
What lives in the repository

An agent does not read all of .ai/knowledge/ up front. It asks Jig for what the files it is about to change require:

​
How a change is sized

Jig classifies every task by risk before any code is written, and the class decides the route: Risk sets the floor: a one-line change to authentication is not trivial. Every route ends by deciding what the task leaves in .ai/knowledge/ — or that it leaves nothing.

​
What this means for a pull request

  • Knowledge travels with the code. A change that alters a rule, a boundary or a domain’s behaviour updates the document in .ai/knowledge/ that owns it, in the same pull request.
  • Knowledge is proposed, then accepted. Anything an agent infers about the codebase enters as proposed and reaches other agents only after a human accepts it (.ai/scripts/jig knowledge proposed lists what is waiting).
  • Checks are the same. composer test, composer run test:arch and Pint decide, whoever wrote the code.
Shows active tasks, knowledge awaiting a decision and anything out of date. How to install Jig and connect your agent to it: jig.fapost.in.